Use Case RealizationClass Diagram Related to Specific Use CaseInteraction DiagramsFlow of EventsSpecial RequirementsAnalysis PackageArchitecture View of Analysis ModelArchitectural Analysis WorkflowI/O of Architectural AnalysisIdentifying Analysis PackagesExampleUse Case Realization•Describes a collaboration among analysis classes that shows how a specific use case is realized•Consists of flow-of-events analysis, class diagrams, interaction diagrams, special requirementsClass Diagram Related to Specific Use CaseInteraction DiagramsFlow of Events •Additional description and explanation of collaborating objects (modeled via interaction diagrams•Example: page 189•Compared to flow of events description in use case model–internal v.s. external viewsSpecial Requirements•Example–When the buyer asks to view received invoices, it should not take more than 0.5 sec to show the invoice on screen–Invoice should be paid using the SET standardAnalysis Package•Mechanism to group elements of the analysis model into larger blocks•Basic principle: strong cohesion, loose coupling•Represent a separation of analysis concerns–to be able to analyzed separately–to be used as the basis for subsystem design–should be created based on functional requirements and on the problem domain•Service Package–Package of functionality that provides supporting function to enable the execution of use cases or to support system operationArchitecture View of Analysis Model•Consists of architecturally significant artifacts in the analysis model–decomposition of analysis model into analysis packages and their dependencies–key analysis classes–use case realization that realize some important and critical functionality, involve many analysis classes, possibly across several analysis packagesArchitectural Analysis WorkflowI/O of Architectural AnalysisIdentifying Analysis Packages•Common practices–use cases required to support a specific business process–use cases required to support a specific actor of the system–use cases that are related via generalization and extends relationships (strong cohesion) –extract common elements between different packages to form “shared” packages•Use cases are usually not local to one packageExample•First thought: Pay Invoice, Send Reminder, Invoice Buyer all involved in the same business process - Sales: from order to delivery•Second thought: different customers have different needs, e.g. some as buyers