|
Ronald Mak
Department of Computer Engineering
|
||||||
|
Mission Control, Jet Propulsion Laboratory (JPL) NASA Mars Exploration Rover Mission |
| # | Assigned | Due | Assignment |
|---|---|---|---|
| 1 | Aug 31 | Sep 8 |
Functional Specification
Use case form: UseCaseForm.docx Formal report rubrics: FormalReportRubrics.pdf |
| 2 | Sep 7 | Sep 15 | Design Specification |
| Date | Content |
|---|---|
| Aug 24 | Slides: Course objectives; project teams; postmortem report; grading; good applications; change and complexity; how to achieve good design; iterative process; poor design not a failure; Rick's Guitars; problems |
| Aug 29 |
Slides:
Continued iterations: (#2) remove string fields and
return multiple matches, (#3) encapsulate what changes,
(#4) new characteristics, (#5) refactored code, delegate
matching
Example programs: RicksGuitar-1.zip RicksGuitar-2.zip RicksGuitar-3.zip RicksGuitar-4.zip RicksGuitar-5.zip |
| Aug 31 | Slides: Summary; OOA&D is about satisfaction; requirements elicitation; functional and nonfunctional; requirements of requirements; how to get requirements; use cases; use case descriptions; Functional Specification; Assignment #1 |
| Sep 5 |
Slides:
Key points for good design; iterative development;
solutions to adding a new mandolin instrument;
Instrument and InstrumentSpec classes; abstract classes;
revised Inventory class; Guitar, GuitarSpec, Mandolin,
MandolinSpec classes; red flags; more instruments; design
doesn't scale well; encapsulation to the rescue;
re-revised InventorySpec and Inventory classes;
conclusions
Example programs: RicksMusic-1.zip RicksMusic-2.zip |
| Sep 7 | Slides: Analysis precedes design; key points for success; change; paralysis by analysis; where do classes come from; categories of classes; class responsibilities; class relationships: dependency, aggregation, inheritance; UML diagrams; class diagrams; sequence diagram; Assignment #2 |
| Sep 12 | Slides: Textual analysis; CRC cards; UML class diagrams: dependency, association, examples; UML state diagram; proposed C++ Date class; code to the interface; factory method design pattern; Day class |
| Sep 14 | Slides: Day class implementations; importance of encapsulation; principles; accessors and mutators; dangerous setter; no surprises; immutable classes; sharing references to immutable objects; const fields; separate accessors and mutators |
| Sep 19 | Slides: Side effects; Law of Demeter; how good is an interface?; cohesion; completeness; convenience; clarity; consistency; programming by contract; preconditions; circular queue example; Assignment #3 |
For SE Majors: CS 046B, or for others: CMPE 126
