. . . . . . . . . ( end of section Front sheet) <<Contents | End>>
. . . . . . . . . ( end of section Second Sheet) <<Contents | End>>
. . . . . . . . . ( end of section Executive Summary) <<Contents | End>>
You must include level 1 DFD expanding any level 0 process that is too big to be a single program. [ a4.html ]
You may include narratives, activity diagrams/flowcharts, ... describing any complex and/or interesting processes.
All data (flows and stores) should be named with names from the ERD. There must not be a store called "Data Base"!
Entity Relationship diagram -- -- --(ERD)
[ d3.html ]
Brief descriptions of two or three most interesting use cases.
You can include casual use cases for any interesting use cases.
You should include at least one fully-dressed uses cases for really critical use cases (one that needs to be done first to mitigate risks, for example). This should follow the fully dressed template [ r2.html#Fully Dressed format ]
In what sequence are the various use cases to be programmed? Why? How? When? Who?
. . . . . . . . . ( end of section Project 5 Deliverable -- Systems Design Specification) <<Contents | End>>
Notes -- Analysis [ a1.html ] [ a2.html ] [ a3.html ] [ a4.html ] [ a5.html ] -- Choices [ c1.html ] [ c2.html ] [ c3.html ] -- Data [ d1.html ] [ d2.html ] [ d3.html ] [ d4.html ] -- Rules [ r1.html ] [ r2.html ] [ r3.html ]
Projects [ project0.html ] [ project1.html ] [ project2.html ] [ project3.html ] [ project4.html ] [ project5.html ] [ projects.html ]
Field Trips [ F1.html ] [ F2.html ] [ F3.html ]
Metadata [ about.html ] [ index.html ] [ schedule.html ] [ syllabus.html ] [ readings.html ] [ review.html ] [ glossary.html ] [ contact.html ] [ grading/ ]