18-649 Project 9
Advanced Elevator and Smart Dispatcher Design
Check the course webpage for due
Please submit all
project-related correspondence to
- Dated entries will appear here if the assignment changes after it
A Recommendation About
Runtime monitoring was introduces in Project 7. In Project 11,
will use runtime monitoring to verify that your design meets the new
high-level requirements. Although you are not required to do so,
should look ahead at the monitoring requirements and think about how
you can use monitoring to verify your improved design. We
recommend that you start using a monitor for verification as soon as
you have a complete design. Dispatcher algorithms are very
have many corner cases. You probably won't find all the problems
without runtime monitoring. You should also consider generating
additional acceptance tests to further exercise your design.
these are not requirements, but remember that the sooner you identify
problems in your design, the easier they are to fix!
Now that you've finished the
sequence diagrams and requirements for your elevator
system, you'll make the design changes through the rest of your design
- Update statecharts - You
will update your statecharts based on
the changes and additions made to your requirements in Project 8.
Your statecharts must continue to be pure time-triggered design.
You should refresh your memory by rereading the time-triggered design
guidelines in Project 4.
- Update unit tests - You
will update your unit tests so that they
correspond to the changes made in your statecharts.
Update implementation (code) -
have created. You must
continue to follow the controller guidelines outlined in Project 5.
Complete End-to-End Traceability
- Since your design update will be completed by the
time you turn in this project, you must also have update and complete
end-to-end traceability, including:
- Your tests must be syntactically valid (must execute without
causing any runtime exceptions in the simulator), but you are not required to pass unit tests this
week (OK to have failed assertions). You will be required to pass
them next week, so don't blow
off the creation of unit tests.
- Your Unit Test Log
must be complete and up-to-date, including describing the issues
related to any controllers that are not passing all their unit tests.
- Make sure your Unit Test
Summary File is up-to-date, as this will be used to automate the
grading of your portfolio.
Peer Review -
- Sequence Diagrams to Requirements traceability
- Requirements to Constraints traceability
- Requirements to Statecharts traceability (tables in the Requirements II document).
- Statecharts to Code traceability
- Complete and correct state and arc traceability comments in
your unit tests, as described in Project
- You shall conduct a peer review for the following:
- Dispatcher Statechart
- DriveControl Statechart
- Dispatcher Code Implementation
- DriveControl Code Implementation
- You should peer review
any unit tests you revise.
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
guidelines. You are going to update
portfolio every week, so be sure to keep an up to date working
Ensure your design portfolio is complete and consistent.
The following is a partial list of the characteristics your portfolio
- Changes requested by the TAs in previous projects have been
- All required documents are complete and up-to-date to the extent
required by the projects (you do not need to update files or links
related to future projects).
- All documents include group # and member names at the top of the
document. (This includes code, where this information should
appear in the header field)
- Individual documents have a uniform appearance (i.e., don't look
like they were written by 4 individual people and then pieced together)
- The issue log is up to date and detailed enough to track changes
to the project.
Handing In Results
- Each team shall submit exactly one copy of the
- Follow the handin instructions detailed in the
Project FAQ to submit your portfolio into the afs handin directory (/afs/ece/class/ece649/Public/handin/project9/group#/ontime/).
- Be sure you
follow the required format for the directory structure of the portfolio
and its location in the handin directories.
- Be sure to follow ALL
portfolio guidelines detailed in the Portfolio Layout page.
- Any submission that contains files with modification dates
after the project deadline will be considered late and subject to a
grade deduction (see course
policy page for more information).
This assignment counts as one team grade. If you choose to divide
the work, remember that you will be graded on the whole assignment. A detailed grading
rubric is available here.
Project 9 is worth 145 points:
In addition to points
explicitly allocated to traceability and portfolio formatting, we may
random checks and deduct points if we find that you do not submit a
complete and consistent design package.
- 20 points for updated
- 20 points for updated
- 20 points for updated
- 60 points for complete
- 20 points for peer
- 5 points for an entry in
the Improvements Log that
tells us what
can be improved about this project. If you
encountered any minor bugs that we haven't already addressed, please
mention them so we can fix them. If you have no suggestions, say so in
your entry for this project.
If you choose to work ahead and go beyond the requirements for this
project, that is fine. As with previous project phases, you must
meet all the
project requirements for this phase regardless of how much extra work
Back to course home page