Announcements. How to build a UML model. Rational Unified Process. How RUP builds a model. UI design. Architect

Transcription

1 How to build a UML model RUP Steriotypes, packages, and object diagrams Case study Announcements HW3 Phase 1 due on Feb 6 th, 5:00pm (need to create new pairs, accounts) Feedback on M2: turn procedural code into OO code, Planning game (show tables with features, subtasks, estimates, actuals, pair-programming partners) Register for the Feb 18 Industry Reception 1 CS Rational Unified Process How RUP builds a model Designed to work with UML No longer being promoted by IBM Roles - (out of 20 or so) Architect UI designer Use case specifier Use case engineer Component engineer Gather use cases from customer Make initial object model For each use case: step through use case, note the objects it requires note the operations it uses Clean up the model CS CS Architect Determine which use cases need to be developed first. High priority use cases describe important and critical functionality security database hard to retrofit later UI design Logical design Which user-interface elements are needed for each use case? What information does the actor need to receive from or give to the system? Prototyping Often is on paper. Test on real users CS CS

2 Requirements Specification Not all requirements go in a use case. Example: security Example: global performance Requirements document describes all other requirements that are not suitable for use cases. Analysis model Class diagrams vague interfaces ( responsibilities ) vague associations (ignore navigability) stereotype classes: boundary - UI, associated with actor control - control associated with a use case entity - persistent, the real objects Use-case realization (Analysis) CS CS Stereotypes Packages <<control>> Automatic claim processor <<entity>> Claim -field1 : any -field2 : any +accept/reject() 0..n n Adjudicator +ID : string Mainframe system Postal system +send letter() Logical grouping Used to divide large system into smaller subsystems show dependencies between subsystems Can contain class diagrams or packages use cases, sequence diagrams, etc. CS CS Packages Packages and dependencies «Facade» Claims processing system Image processing Claims Mainframe interface CS Reduce coupling (so that teams can work independently) Increase cohesion In packages cohesion is between classes in a package coupling is between classes in different packages In classes cohesion is between methods in a class coupling is between methods in different classes CS

3 Architect Responsible for the integrity of analysis model Makes sure packages fit together Makes sure each package is good Identifies obvious entity classes Lets other classes be defined during use-case realizations and component analysis Architect Identify common special requirements Persistence Distribution and concurrency Security Fault tolerance Transaction management CS CS Use case engineer Identify analysis classes needed by usecase Boundary classes, control classes, entity classes Distribute behavior of use-case to classes Make use-case realization: a precise description of use-case sequence diagram collaboration diagram Component Engineer Analyze classes Gather information from use cases Make sure class is coherent Make model as simple as possible, but no simpler. Analyze a package Relationships between classes Relationships between packages CS CS Outline of RUP process for analysis Find use cases Architect determines order Repeatedly, take next use case change class diagram to accommodate use case simplify class diagram Object diagram Snapshot of objects in a system at a point in time If there is just one object of each class, the class diagram and the object diagram are the same As classes become more reusable, object diagram becomes more interesting CS CS

4 Class diagram Class and object diagrams <<control>> Automatic claim processor Mainframe system 101:Claim <<entity>> Claim -field1 : any -field2 : any +accept/reject() 0..n n Adjudicator +ID : string Postal system +send letter() :Claim Processor Jim:Adjudicator Id: Jane:Adjudicator Id: :Claim 103:Claim 104:Claim 105:Claim CS CS Summary Analysis is converting vague user needs into a precise model of what the system should do. Analysis is incremental; look at one piece of the problem at a time. Requires continually changing the model until you are done. Analysis/Design in XP Similar to RUP except that everyone does it little written, more oral less is done before writing code CS CS Modeling example in XP Why we model incrementally? Code is the model!! Build up model bit by bit Look at one requirement at a time A new requirement might require adding to model changing model Model should support all the requirements you ve seen so far CS We can only think about one thing at a time Criticism is easier than creation As long as we get the right answer, it doesn t matter how we got it CS

5 The Use Case Diagram for The A direct marketing system Sends customized mail and /_00.pdf Description consists of a set of use cases User generating letters sending letters mail system adding customer info template creation delivery monitoring customer selection CS list information support CS Generating letters A user selects a set of to whom they wish to send letters and a template that defines the letter format. The then generates a letter per customer that is based on filling in the pluggable information for the template with customer-related information. The user then previews the result of expanding the template list for each of the. CS selection Customer CS Dear <<Proper Salutation>> <<Customer Name>> Thank you very much from ordering from us on <<Date of most recent order>>. We recently received several thousand cans of the special ingredient, preview Customer Component If you are interested, please click on thehappy.com/specialorder/<<special order number>>/order.html stringfor(acustomer) { return acustomer.of()} Field Constant CS CS

6 Use template to create a letter for a customer Customer Property Of() stringfor(acustomer) { return acustomer.of()} Component Field Constant letter := empty letter; for each component c of template, add c.stringfor(customer) to letter If c is a constant, c. is c.. If c is a field, c.stringfor(customer) is customer.of(c.) CS CS Sending letters A user chooses from among the generated letters and decides which ones to send out and by which MailingSystem to send them. The should already have information associated with each customer so it can properly distribute the letter by a particular MailingSystem; the user should not need to enter this information as part of the sending process. CS Customer Property Of() selection MailingSystem PostalSystem SMTP CS Adding Customer Information Customer Property selection MailingSystem PostalSystem SMTP A Customer has a property address and postal address which are used by the MailingSystems to obtain an address. A user knows of a new customer that she wants to add to The. The user can create a new customer entry and record relevant information (Name, Salutation, Address, Recent Purchase, and anything needed by other parts of The ) for that customer. CS CS

7 Interface for creating customer Customer Property Name: Salutation: Address: Recent purchase: Create New Customer Anna Kurn Ms. 712 Maple Ave, Toronto NY Recent purchase: #e45 CS CS Creation A user creates a new template either from scratch or by copying an existing template. A template needs to support both constant and pluggable information, and a user should be able to create a template and preview its appearance. Component Field Constant CS CS User interfaces Parser Component Field Constant Generate letters (select a set of and a template) and preview them Select letters to send and the mailing system to use Create new customer and enter info Create new template and preview it CS CS

8 Delivery Monitoring A user reviews the letters to see which have been sent and whether any of them have failed delivery. If so, the user can choose to resend them either by the same Mailing System or by a different one. Also, to support this story, the Mailing System must be able to tell The which sent letters failed delivery. MailingSystem PostalSystem SMTP CS CS Mail delivery failure status MailingSystem PostalSystem SMTP CS Some failures are permanent ( no such user ) and some are temporary ( mailbox full ). Need different status for each. Can have secondary addresses. Select permanent failures and send to secondary address is special case of select messages and send them Need UI for changing status CS Customer selection by criteria Upgrade the template from Story#1 to support selecting the set of by various search criteria. For example, select all who spent more than US$100 on their most recent order, or all who have ever bought a particular product. What query language? SQL? Dialog box? What criteria? Any history? Orders, products Change the UI for select CS CS

9 Conclusion Only half done Process to finish is the same Each step makes progress Keep track of open issues and make sure they get resolved Amount you write down depends on how much you remember Next time Design Fest in class: CRC, UML CS CS