Answer to Question #288939 in Mechanical Engineering for sten

Question

You asked to prepare a software code/ design report on mobile robot programming to implement the functions described in the previous part for the application. Following your hardware selection, pin assignments and interfacing requirements in Part above, you need to develop the produce a software interface / code to perform the operation of the mobile robot. Produce the following

·  written code so the engineering design fully functions

·  a simulation run to test and debug the written code

·  a critical evaluation of the written code in terms of functional success.

Answer 1

A mobile robot is a machine controlled by software that uses sensors and other technology to identify its surroundings and move around its environment. Mobile robots function using a combination of artificial intelligence (AI) and physical robotic elements, such as wheels, tracks, and legs. 

Testing

Your test result grade will be based on our tests. Each project has several tests, each of which has a name beginning with tests. To completely test your submission, invoke make check from the project build directory. This will build and run each test and print a "pass" or "fail" message for each one. When a test fails, make check also prints some details of the reason for failure. After running all the tests, make check also prints a summary of the test results.

Debugging versus Testing

When you're debugging code, it's useful to be able to run a program twice and have it do exactly the same thing. On second and later runs, you can make new observations without having to discard or verify your old observations. This property is called "reproducibility." One of the simulators that Pintos supports, Bochs, can be set up for reproducibility, and that's the way that pintos invokes it by default.

Critical evaluation of the written code in terms of functional success.

1. Review fewer than 400 lines of code at a time

2. Take your time. Inspection rates should be under 500 LOC per hour

3. Do not review for more than 60 minutes at a time.

4. Set goals and capture metrics.

5. Authors should annotate source code before the review

6. Use checklists

7. Establish a process for fixing defects found

8. Foster a positive code review culture

9. Embrace the subconscious implications of peer review

10. Practice lightweight code reviews