Case 6: Application Controller Pattern and Reflection

Think-Design-Test-Create

• Description

You have proposed, and the team has accepted, using QuickConnect upon which to base your application.  You now need to design and create the business and view modules that will make your application truly interesting to use and easy to maintain.

You have decided to implement the use of databases to retain information between instances of running the application.  This will mean that if a user accidentally closes the application that the data already entered is still available and viewable when they restart the application.

• Deliverables
  1. A modification of your prototype that uses the QuickConnect framework to do database interaction
  2. A full series of UML diagrams for the data storage activity including a Use Case diagram, a Detailed Use Case Description, a State Diagram, and a Sequence Diagram.
  3. A presentation of your solution.
  4. An assessment case
• Resourses:
  1. UML State Diagrams
  2. UML Use Case Diagrams
  3. Detailed use case description template
  4. UML Sequence Diagrams
  5. Diagram Descriptions
     

     Document Type	Description	Level of Detail
     Use Case Diagram	What can the user do?	low
     Detailed Use Case Description	How does the user do it?	medium
     State Diagram	How does the system change as the user uses it?	low
     Sequence Diagram	What objects, methods, and parameters does the system need to do it?	high

  6. 

     An example of a use case diagram for a bathroom shower

  7. 

     A state diagram showing the iterative nature of washing hair

  8. 

     A State diagram showing detailed actions within each state

  9. 

     An example of an iterative sequence diagram.