Overview

• Each group will have 4-6 students. 
• Each group must write a paper and give an oral presentation addressing the operational phase of the life cycle for the a system design problem of the group's choosing.
• Each group must develop a statement of need, operational concept, objectives hierarchy, originating requirements, and an external systems diagram. Each group must also develop functional, physical, allocated and interface architectures and an evaluation plan for the operational system. 
  
• Each group must also develop a management plan and produce a management report.
• Each group must a project notebook which will  be evaluated periodically by the instructor.  At the end of the semester, all the parts of the project will be integrated into a final report, which will be handed in along with an executable model of the group's system architecture in CORE, optionally containing some MagicDraw diagrams.  The final report must conform to the standard GMU System Description Document (GMU-SDD) format. 
  
• Each student must submit midterm and final self and peer evaluations describing progress on the project.
  

Topic

• Elevator case study

• Your system must be complex enough to make an interesting semester project.
• Your system must have interfaces to both external systems and human users/operators.
• Your functional decomposition should go at least three levels deep.
• Your system design should include at least four subsystems.

Deliverables

1. 14 September, 2020 - Description, references, project plan.  You must hand in a brief (1 page or less) description of your topic and at least three reference sources containing information relevant to your topic.   Your project plan should say how you are dividing up the tasks and how you are coordinating your efforts.  The plan may be in the form of a table.  The first column of the table is a list of tasks to be performed.  The second column is the responsible team member.  Each team member must be responsible for some tasks.  The third column is a list of tasks on which this task depends.  The fourth column is an expected completion date.  The fifth column is the actual completion date.  Most entries in the last column will be blank, but you must hand in an updated version at the end of the semester with the actual completion dates filled in.  If you wish to use an alternate format (e.g., a work breakdown structure and GANTT chart), you may do so.  You will probably want to have at least one task for each deliverable, along with a coordination task. The coordination task is ongoing throughout the semester -- it won't be completed till the end of the semester.  The coordinator is responsible for making sure that all tasks are on track, that everyone knows about meetings, that someone takes minutes at every meeting, etc.
2. 24 September, 2020 - Draft Statement of Need, Stakeholders, Operational Concept, and External Systems Diagram
3. 20 October, 2020 - Draft Objectives Hierarchy and Originating Requirements
4. 10 November, 2020 - Draft Functional, Physical, Allocated Architectures
   
5. 24 November, 2020 - Draft Final Report
6. 13 December, 2020 - Project Final Report

• Introduction, Statement of Need and Stakeholder Analysis
• This section gives a brief introduction to your problem, describes the need your project addresses, lists the major stakeholders, and describes what stake each has in the system.
  
• Operational concept
• This section must include a vision statement, mission requirements, and a set of operational scenarios covering the main usage conditions for your system. Each operational scenario must have a verbal description and a sequence diagram.
  
• Objectives hierarchy
• You must include an objectives hierarchy and a verbal explanation of your objectives hierarchy. Your bottom-level objectives must have measures and units. It is not necessary to have weights.
  
• External systems diagram
• This section must contain an external systems diagram representing your system. An IDEF0 diagram is required. A SysML use case diagram is recommended. The IDEF0 diagram should show your system and the external systems, with item flows depicting the interactions with external systems. You must also include a verbal explanation of the external systems diagram.
  
• Originating requirements
• This section contains a hierarchically organized and hierarchically numbered set of originating requirements. It also includes derived requirements as necessary to define the allocated and interface architectures. These should be a reasonably comprehensive set of requirements, from the stakeholder's perspective, for the operational phase of the system.
  
• Functional architecture
• This section contains a functional hierarchy diagram and a data model, shown as a hierarchy diagram and a set of hierarchically organized IDEF0 diagrams showing inputs and outputs of the functions. There should also be a verbal description of the functional hierarchy and data model. Traceability information is also captured when developing the functional architecture. In the report, the traceability information may be included in the functional architecture section or in the requirements section.
  
• Physical architecture
• This section includes a hierarchy diagram for the generic physical architecture, a morphological box listing alternatives for at least four components, a selection of at least two instantiations, and a verbal explanation of your physical architecture.
  
• Allocated architecture
• This section includes an allocation table showing allocations of physical components to functions, a set of function flow block diagrams (or activity diagrams) showing activation and control structure, and traceability information.  You must include a verbal description of the activation and control structure.  For traceability, as before, you may refer to the originating requirements section which includes the traceability relationships.
  
• Interface architecture
• This section describes the main interfaces of your system with external systems, and interfaces of subsystems with each other. For each interface, briefly describe what flows across the interface, and state the interface standards to which it will conform, if applicable.  
  
• Qualification plan
• This section describes how you will evaluate your system.  Your plan can be shown in the form of a requirements verification matrix (RVM). 
  
• Management report - This section includes your revised and updated project plan, including projected and actual completion dates for all tasks.  It also includes a group consensus evaluation of each group member.  The evaluation contains a brief description of what that group member contributed to the project and an assessment, on a scale of 0 to 100, of the team member's contribution to the overall effort.  A score of 100 means this team member was a full participant,  contributed significantly to the overall effort, performed work the other team members considered valuable, delivered products promptly, and interacted with group members in a professional manner. Scores lower than 100 indicate the degree to which a team member's contribution fell short of this exemplary standard.
  

Grading

1. Deliverables 1-5 - Maximum of 25 points total (5 for each deliverable).  This is a completion grade. Full score will be awarded if deliverable is handed in on time and reflects a serious attempt at the objective of the deliverable.  Points will be taken off if deliverable is not part of a complete and professional project notebook. Points will be taken off if notebook does not include meeting minutes section with up-to-date minutes.
2. Self and peer evaluations - There will be midterm and final self and peer evaulations, worth 2.5 points each.
   
3. Presentation - Maximum of 25  points total.  Group presentation grade (15 points) covers overall organization, content, and professionalism of presentation.  Individual grade (10 points) covers each student's individual contribution to the presentation.
   
4. Final report  - Maximum of 45 points total.  Final report should be done using a word processor and CORE.  Final report will be graded according to content and professionalism (includes writing and format).  Report must use  GMU System Description Document (GMU-SDD) format.

1. Group grade: Maximum of 85 points total: 25 for deliverables, 15 for group presentation and 45 for project report.  This part of your grade is based on your group grade adjusted by how your peers evaluate you.  If the group functions well and everyone contributes equally, each of you will receive your group grade.  Your individual grade will be adjusted up or down if self and peer evaluations indicate some students contributed more than others. 
   
2. Individual grade: Maximum of 15 points total: 10 points for presentation and 5 points for self and peer evaluations according to instructions. This is an individual grade based on your presentation to the class and turning in your self and peer evaluations according to instructions.