-
Notifications
You must be signed in to change notification settings - Fork 2
Project Milestone 3
Work through the checklist to decide how to address your system's quality attribute of Availability. Select appropriate architectural tactics to ensure availability based on your decisions. Your architecture should use at least five architectural availability tactics. Implement the code for these five architectural tactics in your project. On your Wiki, create a section "Architecture Tactics - Availability" where you (1) include your checklist or set of questions/criteria to assess and evaluate architecture tactic, (2) the architecture tactic you selected, (3) how this tactic is manifested in your design, and (4) how you plan to test whether your quality attribute objective will be met.
For your project, identify and plan at least five design patterns in your design and system. It should be a pattern that you implement. On your Wiki, create a section, "Design Patterns," where you describe each design pattern in general and how they manifest in your design and system. Implement the code for these five design patterns in your project.
LIAM PUT COPILOT HERE:
ERICH PUT STATE PATTERN HERE:
Update all the previous UML Diagrams and the System Description according to feasibility and changed requirements. This should be in detail as to why they were changed and not feasible.
Summarize the contributions made by each team member. (Point out the sections/parts each group member was "most responsible" for.)