1. CSE Senior Design I Architecture Design Review/Final Exam Template CSE 4316 Final Exam

2. 1 CSE 4317 2 Instructions [Delete this slide from your presentation]  Each team will prepare a 20-minute (maximum) presentation that follows this template  Submit your presentation via email to odell@uta.edu by 8:00 am on Monday, 5/10/2014 (exam date)odell@uta.edu  Presentations will be made from the slides you submit, no updates after submission  Late submissions is a 20% penalty, no exceptions  Order of presentations will be determined on exam day  Instructor will ask questions based on your presentation and your draft ADS.  Questions will be directed by name covering any part of the presentation that I choose  I.e., everyone on the team should be very familiar with the entire contents of presentation

3. 1 CSE 4317 3 Guiding Principles  [Principle 1]  [Description of this principle relative to your system’s design]  [Describe how you will ensure that you follow this principle in your design]

4. 1 CSE 4317 4 Guiding Principles  [Principle 2]  [Description of this principle relative to your system’s design]  [Describe how you will ensure that you follow this principle in your design]

5. 1 CSE 4317 5 Top 3 Guiding Principles  [Principle 3]  [Description of this principle relative to your system’s design]  [Describe how you will ensure that you follow this principle in your design]

6. 1 CSE 4317 6 Layer Structure Overview  [This is a diagram of your layer relationships]  It should show “layer boxes” with layer names  NO dataflow arrows, layer relationships only

7. 1 CSE 4317 7 [Layer 1 Name] Description  [Brief description of what this layer does within your system]  [Brief description on the services this layer provides to any other layer that it interfaces with.]  [Brief description of the services this layer expects from any layer that it interfaces with.]

8. 1 CSE 4317 8 [Layer 2 Name] Description  [Brief description of what this layer does within your system]  [Brief description on the services this layer provides to any other layer that it interfaces with.]  [Brief description of the services this layer expects from any layer that it interfaces with.]

9. 1 CSE 4317 9 [Layer 3 Name] Description  [Brief description of what this layer does within your system]  [Brief description on the services this layer provides to any other layer that it interfaces with.]  [Brief description of the services this layer expects from any layer that it interfaces with.]

10. 1 CSE 4317 10 [Layer n Name] Description  [Brief description of what this layer does within your system]  [Brief description on the services this layer provides to any other layer that it interfaces with.]  [Brief description of the services this layer expects from any layer that it interfaces with.]

11. 1 CSE 4317 11 [Layer 1 Name] Subsystems  [Name] Subsystem: [brief description of what this subsystem does within the layer]  …

12. 1 CSE 4317 12 [Layer 2 Name] Subsystems  [Name] Subsystem: [brief description of what this subsystem does within the layer]  …

13. 1 CSE 4317 13 [Layer 3 Name] Subsystems  [Name] Subsystem: [brief description of what this subsystem does within the layer]  …

14. 1 CSE 4317 14 [Layer n Name] Subsystems  [Name] Subsystem: [brief description of what this subsystem does within the layer]  …

15. 1 Data Flow Descriptions  [This is a table that lists all internal and external data flows]  Recommend labeling data flows based on provider subsystem  Ensure each description is clear and complete CSE 4317 15

16. 1 Subsystem Data Flow Diagram  [This is a diagram of your layers and subsystems]  It should include all subsystems defined above  Show dataflow arrows between subsystems  [Be prepared to discuss TWO substantial user stories using this diagram] CSE 4317 16