18-649 Project 7
Design Process Cleanup and Midterm Acceptance Testing
Due Thursday March 5, 2009 at
11:59 PM
Please submit all project-related correspondence to 
Change Log:
- Dated entries will be added here if the project is modified after
it is released.
Assignment:
Throughout this semester your group has designed, implemented, and
(partially tested) a basic elevator system. Before you proceed
with optimization, you will make sure the entire design package is 1)
organized well and 2) consistent with your current
implementation. Your design will also need to pass all
previous acceptance tests and additional tests provided for this
project.
If you have been following the process in the prior design stages, this
project should be pretty straightforward.
What you need to do:
1) Download
the latest version of the simulation framework from the download page.
A note about control periods (READ
THIS!): For this project, we have
assigned the following control periods to controllers (see Control.Java
in the simulator):
- HallButtonControl: 100ms
- CarButtonControl: 100ms
- LanternControl: 200ms
- CarPositionControl: 50ms
- Dispatcher: 50ms
- DoorControl: 10ms
- DriveControl: 10ms
We believe these control periods are reasonable. If you wish to
change
the control period used by any controller, you MUST obtain the approval
of one of the course TAs. In order to convince us, you will need
to
make an argument based the timing of the physical system.
"Because it
makes my elevator work" is not a valid argument!
If you obtain TA approval, you must write up
the justification for the change and include it in the description of
the relevant control object(s) in the Elevator Control package (elevatorcontrol/package.html)
in your portfolio. You should also record the name of the TA
that approved the change. If you either a) do not obtain TA
approval or
b) do not note the changes and the justification for the changes in
your portfolio, significant
points will be deducted.
2) Organize your design portfolio.
Make sure that your portfolio documents
conform to the structure and guidelines described in the projects and
the portfolio page.
If you have been using the portfolio template and following the project
guidelines, you should have very little work to do here.
3) Ensure your design portfolio is
complete and consistent. If you have been keeping up with
updates in the previous project stages, most of this work will already
be done. The following is a partial list of the characteristics your
portfolio should exhibit:
- Changes requested by the TAs in previous projects have been
applied.
- All documents are complete and up-to-date with latest
time-triggered implementation (i.e., code matches statecharts,
requirements, sequence diagrams, and all traceability is complete and
up to date)
- 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)
- Code is commented sufficiently and reflects code-statechart
traceability.
- Issue log is up-to-date and detailed enough to
track changes to the project.
- etc.
4) Pass acceptance tests. Your
elevator must pass all previously supplied acceptance tests from
projects 6 and 7 as well as the new acceptance tests for project
7. If you develop and run additional acceptance tests, you may
include those in your portfolio as well. Be sure to update your
testing logs to reflect the latest test results.
- Project 5
- Project 6
- the additional acceptance test you wrote for project 6.
- Project 7
Handing In Results
Each team shall submit exactly one copy of the
assignment.
Follow the handin instructions detailed in the
Project FAQ to submit your portfolio into the afs handin directory (/afs/ece/class/ece649/Public/handin/project7/group#/ontime/).
Be sure to follow ALL the
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).
Grading Criteria:
This assignment counts as one team grade. If you choose to divide
the work, remember that you will be graded on the whole assignment.
145 Points Total.
- Acceptance tests (27 points)
- 3 points each for passing the 9 acceptance tests
- Portfolio structure (13 points)
- Correctly follow the portfolio structure and guidelines
- Design process conformance (100
points) - This part will be graded based on how consistent your
design is and how much your portfolio
reflects adherence to the design process.
- Improvments Log (5 points) -
Add 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.
Back to course home page