Document: Reviewed UML_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&V Date Reviewed: October 19, 2008 Exit Criteria 1. A Structure Diagram that shows the context in which the system is expected to operate (e.g. operational stakeholders, devices that they system interacts with, the hardware the software is expected to execute on) 2. A Domain/System Information & Artifacts Class Model This class model should include: Classes that represent the artifact and information elements identified in section 3.3 of the OCD. o In general, each artifact and information element is represented by 1 class, but there are exceptions. An entity may be represented by multiple classes (e.g. the entity is a general concept and there are specializations that are important to differentiate in the implementation (e.g. aircraft)). Multiple entities may be represented by 1 class (e.g. some entities may be so tightly related or your system be may unconcern with some details so sufficient to define a class that represents multiple entities (e.g. the system may control the filing of containers that are different sizes and shapes, but all it needs to know is the containers volume); Any additional class identified while describing process use-cases; Any classes identified in the prototype; Any classes needed to define attributes of class defined in previous 3 bullets.
3. A System Process Model (Use-case Diagram & text description of each process suitable for non-technical client without des...