1 / 18

Project X

Project X. Group Y Presenters: (indicate roles). Part I: Project Overview. System provides functionality X Motivation for project Address problem with… Facilitates what…. Overview of Features. Feature 1 Feature 2 Feature 3 Feature 4 Feature 5. Project Domain.

quade
Download Presentation

Project X

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project X Group Y Presenters: (indicate roles)

  2. Part I: Project Overview • System provides functionality X • Motivation for project • Address problem with… • Facilitates what…

  3. Overview of Features • Feature 1 • Feature 2 • Feature 3 • Feature 4 • Feature 5

  4. Project Domain • Investigated domain/area X • Needed to apply domain knowledge on topic Y • Project Constraints • Constraint 1 • Constraint 2 • Constraint 3

  5. Special Constraint Analysis (e.g., Security) • Identify security factors affecting project • … • How did you mitigate security risks? • Add more slides if you needed to handle any other constraints

  6. Part II: Model-based View of System • Explain the main functions through (choose): • Give us use case diagram • Explain key use cases • Walk us through scenarios • Walk us through class diagram • Give us a few representative scenarios in terms of sequence diagrams • Walk us through the state diagram of a few key objects

  7. Description of Scenarios • Give and describe an illustration • Briefly describe key scenarios • Take one scenario and give details

  8. Description of Use Case Diagram • Give and describe use case diagram • Briefly describe key use cases • Take one use case and give details

  9. Description of Class Diagram • General layout of class model • Why model is constructed this way • Identify the design patterns used for system (use color or other means to distinguish design patterns). • Explain the rationale for the design patterns used • Identify the cross-cutting concern(s) • How did you use aspect-oriented programming?

  10. Behavior Model: Sequence Diagrams • Give 1 normal scenario in terms of sequence diagram • Give a scenario describing exceptional situation in terms of sequence diagram

  11. Behavior Model: State Diagrams • Give state diagram for at least two key (interacting) classes. • Explain interaction

  12. Description of Architectural Design • Show us the original (without components) and final (using components) designs • Show the “new” integrated deign • Explain the choice of design selected • Explain key differences in new design • Tell us about the major challenges with reusing components

  13. Related Work • Mention any related work (similar systems) • How are they similar? • How are they different?

  14. Lessons Learned • Describe the lessons learned from the process • Describe key design decisions that made it easier/faster to build • Describe a few things that you would do differently in retrospect • Explain the project extensions/open areas for future work

  15. Part III: Demo • Live demo • Video demo (e.g., Camtasia video illustrating how to use your system) • Etc. • Should include demonstration of key features

  16. Live Demo I • Prose description of scenario illustrating prototype functionality • Give live planned demonstration

  17. Live Demonstration II • Solicit input from audience to walk through a few more scenarios • Alternatively let someone from audience try out the system.

  18. Q & A • Provide some time for questions and answers

More Related