18-649 Project 12

Check the course webpage for due dates

Please submit all project-related correspondence to


Changelog:

Assignment:

At this point, you have completed most of the design and testing of your fast elevator.  In this project, you will have to make a single design change and continue testing on the updated elevator.

1. High Speed Drive Modification

1.1 Update to High Speed Drive
Consider this scenario: at your most recent project meeting your boss informs you that the marketing department has decided to change the target audience for your elevator product (didn't you get the memo?).  Now, the elevator has to exhibit even better passenger delivery performance.  In order for you to meet your new performance requirements, your boss has gotten approval to use new, top-of-the-line drive motors which accelerate at the same rate, but have a much higher maximum speed.

Modify your design to work with the new drive speed parameters:

To make the simulator run at the fast speed, you will need to add a "-fs 5.0" command to your simulator invocations.  This raises the fast speed in the drive control to 5 m/s.  Make sure you run all acceptance tests from this point forward using the -fs 5.0 option.  Note that you do not need to use this option with unit and integration tests, since the DriveObject is not instantiated in those tests.  However, you may need to change the messages that are injected in your tests to simulate the correct fast speed.

Pay special attention to how this change affects your elevator.  In particular, you may want to consider:
You should add a single entry to the issue log that describes the customer's change in requirements and documents the design artifacts that this change causes.  If you find bugs after the initial design change is complete (e.g. through testing), you should log those as separate issues.

1.2 Peer Review
Have someone other than the module author complete a peer review of the updated modules and update the Peer Review section of your portfolio. Peer reviews that result in unfixed issues should be added to the Issue Log.

Four peer reviews need to be conducted. If you change fewer than four modules, then you shall review other artifacts that have not yet been previously reviewed.

2.  Complete Testing of Your Elevator Design

You must run all tests on your latest design:
We will execute these tests with an arbitrary random seed which we will not divulge ahead of time.  Passing these tests constitutes "having a working elevator".  Note:  You must pass all acceptance tests in order to receive a grade in this course.

Team Design Portfolio

The portfolio you submit should contain the most up-to-date design package for your elevator system organized and formatted according to the portfolio guidelines.  You are going to update your portfolio every week, so be sure to keep an up to date working copy. 

Ensure your design portfolio is complete and consistent.

The following is a partial list of the characteristics your portfolio should exhibit:

Handing In Results


Grading:

This project counts as one team grade. Points are assigned as follows.  A detailed grading rubric is available here.

This project assignment is worth 105 points:

Each team member must satisfy the minimum stated per-member requirements. Team members who omit any required per-member activity will receive a zero contribution grade.

Back to course home page