1. CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University

2. Goals for today Course Objectives Introduction to Modeling with UML and Java Working with UML Gathering requirements for a sample application

3. Enterprise Java with UML CT Arrington Chapter 1 Based on the book: “Enterprise Java with UML” OMG Press, John Wiley and Sons, 2001.

4. Why model? Building enterprise, distributed solutions is hard. To harness the power of complex technologies such as J2EE, need a way to visualize and communicate design goals and implementation decisions UML is a standard for modeling software

5. What is a UML model? A language for specifying, visualizing, constructing and documenting software artifacts A simplified representation of the problem to be solved and of the solution – This facilitates collaboration and review Can incorporate multiple perspectives – from user perspective, developer perspective Multiple levels of details – overview level, detailed level

6. The Basics Abstraction Encapsulation Object Class myHondaAccord -name:String -rank:String -carryingRifle:boolean ToySoldier +attackKenDoll()

7. Relationship between Objects Dependency Association Aggregation Composition

8. Related concepts Navigability Multiplicity Interface Polymorphism

9. Modeling Software Systems with UML The Customer’s Perspective – Use Case – Text Description of each use case – An activity diagram The Developer’s Perspective – Class diagram – State Chart – Package diagram – Sequence Diagram – Collaboration Diagram

10. Modeling Process Requirements Gathering Analysis Technology Selection Architecture Design and Implementation

11. Gathering Requirements with UML Chapter 2 Based on the book: “Enterprise Java with UML” OMG Press, John Wiley and Sons, 2001.

12. What are good requirements Find the right people – Domain Experts – End Users Listen to the stakeholders

13. Develop accessible requirements Find actors Find use cases Describe actors and use cases – Use case description Preconditions, postconditions, performance requirements, security requirements, deployment constraints – Flow of events Normal, or baseline flow; Alternative flows; Exception flows – Activity diagrams Pg 26 Activity diagrams are similar to flowcharts. However, flowcharts depict a solution, activity diagrams describes the problem.

14. Refactor the Use Case Model Split up the use case (eg. Pg 2.3) Use of Include and Extend Relationships (pg 30) Use Case Generalization Actor generalization

15. Guidelines for gathering requirements Problem driven Do it phases Don’t go too far

16. Detecting poor requirements Excessive schedule pressure No clear vision Premature Architecture and Design

17. Gathering Requirements for the Timecard Application Chapter 3 Based on the book: “Enterprise Java with UML” OMG Press, John Wiley and Sons, 2001.

18. Process Interview key stakeholder (pg 43) Build a use case – Find the actors Find Candidates: – Employees, Operations Manager, Managers Refine the actors – Employees, Administrative User – Find the use cases Create Employee Create charge code Record time Comment time entry Export time entries – Evaluate use cases

19. Determine the Actor-to-Use-Case relationships Create Charge Code Create Employee Export Time Entries Record Time Admin. User Employee Billing System

20. Capturing the details Name of use case Description Preconditions Deployment constraints Normal flow of events Alternate flow of events Exception or error flow Activity diagram Nonfunctional requirements Notes Open issues

21. Developing use cases Create Charge Code (pg 50) Create Employee (pg 51) Record Time (pg 53) Export Time Entries (pg 56)