1. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Chapter 7 Analysis

2. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Introduction Objectives: –To produce the first approximation of the shape of the solution and to lay the groundwork for design Primary Artifacts –Design model  contains: –the key elements of the software solution and their organizations –Use-case realizations –User-Experience Model Provides an abstraction of the user interface elements and the user’s interaction with the system Contains: –Screens –Use-Case Storyboards –Navigation Map

3. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analysis and Design Iterative Development

4. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analysis Overview Two workflow details: 1.Define an Initial Architecture –Focusing on sketching out the software architecture 2.Analyze behavior –Focus on: –Identifying Screens and use-Case Storyboards –Identifying the Analysis Classes, their responsibilities and their interactions

5. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analysis and Design Overview Diagram

6. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Workflow detail: Define an Initial Architecture Objectives: –To create an initial “sketch” of the system architecture that leverages any existing Reference Architectures or architectural framework –The “sketch” includes: Overall structure of the system Its key abstractions, and Its mechanism

7. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Define an Initial Architecture Workflow Detail Overview Diagram

8. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Architectural Analysis Overview: –To propose an initial architecture for the system, based on experience gained from similar systems or similar problem domain Input Artifacts: –Design guidelines –Glossary –Reference Architecture –Supplementary specification –Use-case Model –Vision

9. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Architectural Analysis (2) Resulting Artifacts: –Deployment Model –Design Guidelines –Design Model –Software Architecture Document Steps: –Develop Architecture Overview –Survey Available Assets –Define the Initial Deployment Model –Structure the Design Model –Identify key Abstraction –Identify Analysis Mechanism

10. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Architecture Overview

11. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 The Design Model Layers

12. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Key Abstractions

13. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Review the Initial Architecture Overview: –To review the initial architecture and supporting guidelines Input Artifacts: –Design guidelines –Glossary –Risk List –Software Architecture Document –Supplementary specification –Use-case Model Resulting Artifacts: –Change Request –Review Record Steps: –Conduct the Review

14. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Workflow detail: Analyze Behavior Objectives: –Adding analysis-level system elements that realize the Use Cases to this initial structure –Two “streams” of activities Model the User Experience –Considers how each use Case is realized in terms of Screens Use Case Analysis –Considers how each Use Case is realized in terms of Analysis Classes

15. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analyze Behavior Workflow Detail Overview Diagram

16. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Model The User Experience Overview: –To define how the behavior of each Use Case is provided by the user-experience elements of the system Input Artifacts: –Use-case Model –Supplementary specification –User-Experience Model –User-Experience Guidelines Resulting Artifacts: –User-Experience Model

17. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Model The User Experience (2) Steps: –For each use Case: Identify the participating Screens Model the screen flows Define the screen Navigation paths –Per iteration: Reconcile the Use Case Storyboards Document Usability Requirements

18. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 User-Experience Model Structure

19. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Traceability between a Use Case Storyboard and a Use Case

20. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 A Screen with Dynamic Content

21. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 A Screen with an Input Form

22. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 A Screen with User Actions

23. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Storyboard Participating Scenes

24. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Storyboard Scene Flow

25. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Storyboard Participating Scenes (Detailed)

26. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Auction Management Navigation Map

27. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Review the User Experience Overview: –To review the user-experience artifacts and obtain acceptance of the system’s user experience from the system’s key stakeholders, especially the end users Input Artifacts: –Supplementary specification –Use-case Model –User-Experience Guidelines –User-Experience Model Resulting Artifacts: –Change Request –Review Record Steps: –Conduct the Review

28. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Use-Case Analysis Overview: –To define how the behavior of each Use Case is provided by the analysis elements of the system Input Artifacts: –Design Guidelines –Design Model –Glossary –Use-case Model –User-Experience Model Resulting Artifacts: –Design Model

29. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Use-Case Analysis(2) Steps: –For each use Case: Identify the participating Analysis Classes Model the use-Case flows Describe the Analysis Classes –Per iteration: Reconcile the Use Case Realizations Ensure consistency with the User-Experience Model

30. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analysis Elements Model Structure

31. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Traceability between a Use Case Realization and a Use Case

32. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Analysis Class Type

33. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Typical Interactions among Analysis Classes

34. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Realization Participating Analysis Classes

35. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Realization Use Case

36. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Place Bid” Use Case Realization Participating Analysis Classes (Detailed)

37. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Relationship between Requirement Elements and Analysis Elements

38. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Traceability between Boundary Classes and Screens

39. Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Review the Analysis Overview: –To review the results of analysis to verify that they accurately represent the system requirements, are consistent with one another, and can serve as a good basis for design. Input Artifacts: –Design Guidelines –Design Model –Supplementary specification –Use-case Model –User-Experience Model Resulting Artifacts: –Change Request –Review Record Steps: –Conduct the Review