Team Assignment 2-2239

Fundamentals of Systems Engineering for Engineering Management — Steven H. Richman 1 Team Assignment 2: Developing a System Model ( Label all answers and complete in this order.) Team Project 5 – Functional Architecture: 1st Level Decomposition A. Create in Core the first level functional decomposition for the Smartphone System. Hint : Use the function requirements in Section 4.1.4 of the Smartphone Case Study. B. Develop the 1 st -level architecture Use Case Sequence Diagram (UCSD) directly in PowerPoint (PPT) (so I can easily show comments on it) for the first User Scenario (Power-On System). -Relate the given external inputs/outputs to the first level functional architecture. -Add the necessary internal inputs/outputs to resolve any tunnels and complete the scenario C. Add this new 1 st -Level UCSD to your Core file (which already contains the given System UCSD-Level for the 7 Uses Case in the Case Study). D. Create Functional Architecture Diagrams, from Core, which describe your Smartphone model to this point. Place these into your PPT presentation. Note : Do not use screen shots or JPEGs in your PPT presentation for these and any following Core diagrams. Directly use the saved diagrams from Core. E. Name your Core file “Project_5” and submit it with your PPT presentation. F. Save another copy of your Core file and name the copy “Project 6” for use in the next project. Note : Follow this naming and copying procedure, at the end of each project for the current and next Core file. This will help you avoid the loss of your Core model. Team Project 6 – Functional Architecture: Adding Use Cases and Deriving Requirements A. Copy the external input and output operational requirements in the RU-Smart Case Study from the given Word document, Smartphone partial Operational Requirements Document (ORD), into your PPT document. These represent the system level requirements for requirements the 7 given Use Cases in the RU-Smart Case Study. Now, develop and show the new 1st level requirements for the Power On System Use Case. Add them in capital letters (CAPS) and color to the requirements in your PPT presentation, NOT in Core. Your requirements in the PPT file now include the system and 1 st -level requirements . Also, anytime you modify an existing requirement, show that modification, in capital letters (CAPS) and color, in your PPT presentation. B. Identify and describe two new Use Cases in PPT for your Smartphone. Each Use Case must have at least one new external input or output that is not already used in the case study. First create the system level UCSDs on paper for both, to ensure that you understand how each Use Case would operate. (It’s easy to erase and make changes on paper.) C. Add the new external input and output requirements, in CAPS and color, for only one of your new use case scenarios to the requirements in your PPT presentation, NOT in Core. D. When you are satisfied with your paper UCSD for the same one new use case scenario as in Part C, develop that UCSD directly in PowerPoint relating the external inputs/outputs to the first level functional architecture and adding the necessary internal inputs/outputs to resolve any tunnels and to complete the scenario.

Fundamentals of Systems Engineering for Engineering Management — Steven H. Richman 2 E. Add only this Use Case to your Core model (at the system and first level), including all new external and internal inputs/outputs. DO NOT add the new system requirements to the Core model. -Be sure to trace all functions and items F. Create only the new Functional Architecture Diagrams from Core which describe your Smartphone model to this point. Place the new diagrams into your PPT presentation. Team Project 7 – Functional Architecture: Adding Use Cases to Core Model A. Develop the Use Case Sequence Diagram directly in PowerPoint for Use Case 6 - Initiate Navigation App-GPS is Off, relating the external inputs/outputs to the first level functional architecture and adding the necessary internal items to resolve any tunnels and to complete the scenario. NOTE: Use all given system-level external inputs and outputs exactly as given. Do not create any new external inputs or outputs. That would (inadvertently) change the given Use Case at the system-level. B. Add the given system level and this 1 st -level UCSD to your Core model including all new external and internal items. DO NOT add any new requirements into Core. -Be sure to trace only the functions and items C. Create the new Functional Architecture Diagrams from Core which describe your Smartphone model to this point and place them into your PPT file. D. Then p hysically trace Use Cases 1, 6 and your one New Use Case on separate IDEF0 diagrams and place these 3 in your PPT presentation. Note: Tracing is done by coloring each item and item name in a color other than the default black and adding the sequence number from your Use Case Sequence Diagram afterwards. Team Project 8 – Functional Architecture: Partial 2 nd -Level Decomposition A. Decompose (in Core) one more level, only one first-level function that is used in the Use Cases 1-Power On and 2-Initiate Navigation and your team’s one n ew Use Case. This creates a partial 2 nd -level functional architecture. B. Create the new Functional Hierarchy Diagram from Core which describes your partial second-level Smartphone model and place it into your PPT presentation. (You may need to change the number of levels parameter so that these new functions show in the hierarchy diagram.) C. Develop the 2 nd -level UCSD first in PowerPoint for only the team ’s one new Use Case, relating the external inputs/outputs to the partial 2 nd -level functional architecture and adding the necessary internal items to resolve any tunnels and to complete the scenario. D. Add this 2 nd -level UCSD to your Core model including all new items; DO NOT add any new requirements into Core. -Be sure to trace only the functions and items E. Create the 2 nd -level functional architecture IDEF0 Diagram from Core which describes your Smartphone model, showing the system, 1 st - and 2 nd -levels, and place it into your PPT presentation. F. Physically trace the Use Case described above and place the traced IDEF0 diagram into your PPT presentation.

Fundamentals of Systems Engineering for Engineering Management — Steven H. Richman 4 3. The team leader should email me that the assignment has been submitted. 4. Your completed PPT presentation is essentially the material for the System Architecture Review (SAR) Gate. You will not be making this presentation. 5. The team leader provides me with feedback regarding team member participation.