1 / 17

DCR Architecture Workshop

DCR Architecture Workshop. Pongtip Aroonvatanaporn CSCI577a Fall 2011 November 18, 2011. Outline. Common Mistakes in FCP Current Stage ARB Expectations Example Model. Average Scores. AA = 13.3/15 NDI = 6.7 /10. UML Structure. Organization of components

yoko
Télécharger la présentation

DCR Architecture Workshop

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. DCR ArchitectureWorkshop PongtipAroonvatanaporn CSCI577a Fall 2011 November 18, 2011 USC-CSSE

  2. Outline • Common Mistakes in FCP • Current Stage • ARB Expectations • Example Model USC-CSSE

  3. Average Scores • AA = 13.3/15 • NDI = 6.7/10 USC-CSSE

  4. UML Structure • Organization of components • All components in one level is not acceptable • One unified model • System Analysis + Design = Architecture • Design realizes system analysis • Do not duplicate components • Significance • Readability and understandability • Organization of thoughts USC-CSSE

  5. System Context • A different view of OCD’s system boundary • Understanding of system scope • Operations done by your system or manual • Types of users involved • For AA • External actor vs. supporting infrastructure (i.e. NDI) • For NDI/NCS • NDI or set of NDIs is your system USC-CSSE

  6. Artifacts and Information • Level of detail of attributes • Attributes represent properties of artifact • Sophisticated properties should probably be its own artifact • Relations between artifacts • User is not the center of everything • Sharing of information between artifacts • Duplicated artifacts • Same artifact with different name USC-CSSE

  7. Behavior • System’s scope • Maintenance is not part of your system’s capability • Manual vs. (semi) automated • Use of <<extend>> and <<include>> • Inconsistencies between description and diagram • Must map directly • Development risks vs. Operation risks • What could prevent you from implementing the use-case? • Not what causes system to crash • Missing use-cases • Consider all operational scenarios • Must tell the whole story of the system USC-CSSE

  8. Pre/Post Conditions • Pre-condition • What is required for use-case to execute successfully • Does not concern pages • Post-condition • What happens after use-case executes • What is modified, updated, deleted • Be specific!! USC-CSSE

  9. Outline • Common Mistakes in FCP • Current Stage • ARB Expectations • Example Model USC-CSSE

  10. Current Stage • Develop technology-specific design model • Include all technologies, NDI, platforms, etc. • Realizes the system analysis • Specific designs that enables the use-cases • Focus on significant use-cases • Not all use-cases need to be realized • Identify the risky ones • Blue-print of system • Can be used by developers • Understandable by others, not just you USC-CSSE

  11. Must Have: AA • Deployment model • Hardware components • Software components • Software on to hardware • Design classes • Boundary, controller, and entities • All the logical components • Sequence diagrams • Logical sequence of system • Realizes specific use-cases USC-CSSE

  12. Must Have: NDI/NCS • Use-case/behavior • Serves as a checklist for capabilities • What you’re looking for in NDI/NCS products • Deployment model • Hardware • Software • Software on to hardware • NDI/NCS components • Usage of web hosting or web application USC-CSSE

  13. Outline • Common Mistakes in FCP • Current Stage • ARB Expectations • Example Model USC-CSSE

  14. ARB Expectations: AA • Present a feasible architecture design • A stable architecture • Implementable • Understandable • Overview of system analysis • Overview of deployment • Focus on design • Pick significant sequence diagrams • Show integration of NDIs and frameworks USC-CSSE

  15. ARB Expectations: NDI/NCS • Not as significant as AA • Architecture is determined by NDI/NCS • Overview of system analysis • Overview of deployment • Focus on use-case/behavior • Must cover all required capabilities USC-CSSE

  16. Outline • Common Mistakes in FCP • Current Stage • ARB Expectations • Example Model USC-CSSE

  17. Example • Volunteer Tracking System USC-CSSE

More Related