CMPSC 487W Software Engineering and Design Group Assignment #4 Fall 2018

Transcription

1 CMPSC 487W Software Engineering and Design Group Assignment #4 Fall 2018 Due Date: Wednesday, December 5, 2017 Total Points: 100 Description: The first three steps of developing a software product in ICONIX process are creating the domain model, use cases, and robustness diagrams. The next step is building sequence diagrams from use cases and robustness diagrams. Assignment: Draw sequence and class diagrams from robustness diagrams in last 5 pages. This assignment is the extension of the assignment 3. You should submit sequence diagrams and class diagrams in this assignment. You can find a sample sequence and class diagrams in pages 4-10 that show some of the requirements for this assignment, which are captured from the Rosenberg s book. Aware that the sample diagrams are not perfect. (The book intentionally provides diagrams having error(s), to fix them later.) In this assignment, reference the flow of sequence highlighted in light blue color (to help to draw sequence diagram), but you do not need to fully follow that sequence. You should copy the entity/domain and boundary objects in the robustness diagrams and paste them into your class and sequence diagrams. You do not need to show all domain and boundary objects. If you need, add extra classes into the class and sequence diagrams. The following shows the basic rubrics for sequence and class diagrams. Additional rubrics can be added when grading. It does not include the points that sum up 100 since it is hard to build complete rubrics to catch your mistakes before looking at your assignments. Reference the text book for more detailed patterns for drawing the sequence diagram in ICONIX style. Add the use case text at the left side of the sequence diagram; Use all actors, entity/domain objects, and boundary objects in robustness diagrams if possible; Map use case text to the message on the sequence diagram (see power-point slide 16); Do not use Focus of control (see power-point slide 17); Draw messages on sequence diagram (use a form of calling functions, not use plane text), add operations to classes in class diagram, cross check sequence diagrams and class diagram, and make sure that all messages in sequence diagrams appear in class diagrams; Assign operations to the right classes; o For example, in power-point slide 20, operation checkpriceisinrange() should be in the ExternalBook class, not in the AddExternalBookPage class, since the domain object has the responsibility to check it and you should focus on operations on domain objects, rather than boundary objects. 1

2 o Additionally, in power-point slide 10, operation () below isuserloggedin should be assigned to the WriteReviewPage boundary class not to the CustomerReview domain/entity class. Convert controllers into messages/operations; however, if you have to convert controllers into classes, add the controller class into class diagram and use controller symbols in sequence diagram (see the right image); Use comment to invoke a use case (see the right image); Use red (or similar distinguishable) color for handling exception or alternate cases; Add multiplicity to the class diagram (see power-point slide 14); Add member variables and member functions to the classes in class diagram (see page 213 in book, or power-point slide 12); Cover all use case texts in the sequence diagram, including both base and alternate cases. Update use case text to make it consistent with your sequence diagram. te that your sequence diagram should have enough details to write a code without ambiguity. In this assignment, I will check how the sequence/logic of calling functions achieves the goal of each use case. When calling functions, use parameter passing and return values as if you write a code. Draw the OO version and abstract version of sequence diagram; do not include details that requires technical architectures such as ASP, JSP, Http Session classes, Servlet classes, Dao classes, etc. You can update use case texts. Follow the below rules when updating use case texts: Write your use cases in active voice; Write your use case using an event/response flow; Write your use case in the context of the object model; Write your use case using a noun-verb-noun sentence structure; Make sure you have all the alternate courses; Check that the use case text isn t too abstract. What to hand in: Submit hardcopies of cover sheet, discussion, class diagrams, and sequence diagrams in a folder at the beginning of class of the due date. Cover sheet: The cover sheet should show group member names. Discussion page: The group leader should write a discussion page that especially includes who did what. Class diagram: In this assignment, group leader has a task to draw class diagram. te that the class diagram should be composed of all classes that appear in sequence diagrams, and each class should have member variable and all operations used in sequence diagrams. Additionally, in the class diagram, the relationships between classes should show multiplicity. Sequence diagram: Each group member except group leader selects one of the robustness diagrams shown in the last 5 pages of this assignment, and draws its sequence diagram. Each sequence diagram should be drawn in individual page that contains its author on top of the page. In the sequence diagram, its corresponding use case text should be presented as a comment as sown in power-point slides 4. Following 6 pages shows the sample class and sequence diagrams captured from Figures in Rosenberg s book 2

3 Last 5 pages in this assignment show the robustness diagrams that you should use to draw the sequence diagrams. te 1: Follow the red parts in this assignment. Those red parts and rules (for sequence diagram and use case modeling) will be the part of rubric. Additional rules can be added. te 2: You may find partially incorrect/inaccurate descriptions in use case texts or robustness diagram, or you may need more detailed descriptions in the use case text to disambiguates sequence diagram. Aware that this situation is considered in ICONIX process, and correcting them in sequence diagram is a part of ICONIX process. Update use case texts if you need. 3

4 CHAPTER 8 SEQUENCE DIAGRAMS 213 «boundary» View + () : void «boundary» LoginScreen «boundary» HomePage «boundary» BookDetailScreen «boundary» WriteReviewScreen + () : void + showvalidationerrors(list) : void «boundary» ConfirmationScreen «entity» CustomerSession Overriding () method to show validation errors. «entity» CustomerReview - rating: int - reviewtext: String + setrating(int) : void + setreviewtext(string) : void + validate(list) : void + isuserloggedin() : boolean «entity» BookCollection «entity» PendingReviewsQueue + add(customerreview) : void «entity» Book - synopsis: String - title: String Figure Prefactored Internet Bookstore static model, still pure OO

5 CHAPTER 9 CRITICAL DESIGN REVIEW 249 CustomerReview + book: Book + customer: Customer + id: int + rating: int + review: String 0..* 0..* Book 1 + id: int + synopsis: String + title: String 1 Customer + String + firstname: String + id: int + lastname: String WriteCustomerReviewController + dosubmitaction(customerreview) : void + formbackingobject(httpservletrequest) : CustomerReview Figure 9-6. Command class for WriteCustomerReviewController, after prefactoring and with multiplicity added in for good measure

6 CHAPTER 8 SEQUENCE DIAGRAMS 207 Figure Building a sequence diagram, beginning of step 4 (pure OO version of the completed sequence diagram)

7 CHAPTER 8 SEQUENCE DIAGRAMS 223 Add External Books to Catalog: BASIC COURSE: The system s the Add External Book page. The Seller types in the External Book details (title, ISBN, price etc) and clicks the Add Book button. The system checks that each field has a value, and that the price is numeric, isn't a negative value or > $1,000. The system also checks that there's a matching ISBN in the Bookstore database. The system then creates the External Book in the database. Seller Add External Book page click Add Book button checkfieldshavevalues checkpriceisnumeric book= create Bookstore Database External Book validate checkpriceisinrange save doesisbnexist save(this)... Figure The corrected sequence diagram excerpt for Exercise 8-1

8 Figure The corrected sequence diagram excerpt for Exercise 8-2 CHAPTER 8 SEQUENCE DIAGRAMS 225

9 228 CHAPTER 8 SEQUENCE DIAGRAMS User Edit Shopping Cart page Customer Session Customer Account Shopping Cart From the Checkout page, the user clicks on Edit Shopping Cart. The system s the Edit Shopping Cart page. click link Page customer= getcustomeraccount cart= getshoppingcart lineitems= fetchlist populate LineItems Component *new {for each LineItem in the ShoppingCart } Line Item page The user clicks on a Line Item in the list of items in his Shopping Cart, then modifies the quantity of the Line Item, and clicks Update. submit modified LineItem qty updatelist checkquantities The system checks that the quantities entered are valid, and res the Edit Shopping Cart page with the totals updated and a confirmation message.... page createconfirmationmessage Figure The corrected sequence diagram excerpt for Exercise 8-3

10 Create User Account BASIC COURSE: The system s Create User Account Page. The user enters Account Information (such as ID, password, credit-card, etc.), and Ride Information (such as VIN, Bank-Account, Carpool Cost, Pick-up Time, etc.). The user clicks Create Account Button. The system ensures that password is valid and ID is unique by accessing Master Account List. The system then adds User Account into Master Account List. The system s the Account Create Confirmation Page, and invokes Login use case. ALTERNATIVE COURSE: ID already exists: The system s ID already exists message on Error Page, and s Create User Account Page again. Invalid password: The system s Password is invalid message on Error Page, and s Create User Account Page again. Incomplete Riding Information entered: The system s Incomplete riding information is entered message on Error Page, and s Create User Account Page again. User Display Create User Account Page Login Enter Ride Information Click Create Account Button Enter Account Information Is Ride Information complete? User Account Is Password valid? Display Incomplete riding information is entered message Is ID already exist? Display Password is invalid message Error page Display ID already exists message Master Account List Add Account into Master Account List invoke Account Create Confirm Page

11 Search Carpool BASIC COURSE: The system s Search Carpool Page. The user enters Carpool Query (such as cost range, Pick-up Time, Pick-up Location, etc.), and click Query Button. The system retrieves Ride Information from Master Account List (by accessing other User Accounts and Organization Accounts), and determines Ride Information List whose elements match with Carpool Query by checking cost ranges, times, and locations. The system s the matching Ride Information List and the user s Carpool History on Rank Ride Information Page to send to Carpool Suggestion Service. Carpool Suggestion Service then reorders Ride Information and submits the result to the system. The system s Send Carpool Request Page to show the ordered Ride Information to the user. ALTERNATIVE COURSE: There is blank(s) in Carpool Query: The system s Carpool Query is incomplete message on Error Page, and s Search Carpool Page again. There is no matching Ride Information: The system s matching Ride Informations are found message on Error Page, and s Search Carpool Page again. response from Carpool Suggestion Service: The system s Suggestion Service Unavailable Page and s Send Carpool Request Page without reordering Ride Information. User Enter Query Search Carpool Page Display Error page Click Query Button Carpool Query Has Blank in Query? Display Carpool Query is incomplete message Display matching Ride Informations are found message Retrieve list of Ride Info consistent with Query Is Ride Info List empty? Master Account List Ride Information List Is Carpool Suggestion Service available? Reorder Ride Info Send Carpool Request Page submit Rank Ride Info Page matching Ride Info List Carpool History Display Carpool Suggestion Service Suggestion Service Unavailable Page

12 Pre-match carpool BASIC COURSE: The system s Send Carpool Request Page that lists Ride Information. The user selects a preferred Ride Information, and clicks Request Ride Button. For the selected Ride Information, the system determines its corresponding Account, gets the Account and Ride Request Queue from Ride Information, creates Ride Request with setting it as undetermined, and adds Ride Request to the Ride Request Queue and Central Database. The system invokes Send Message To Account use case to send the request conformation message to its user, and s Send Carpool Request Page to allow request ride to other Accounts. User Send Carpool Request Page Click Request Ride Button select Ride Information selected Ride Information Determine Ride Request Queue from Account Ride Request Queue Create Ride Request and set undetermined Central Database Add Ride Request to Ride Request Queue and Central Database ALTERNATIVE COURSE: Selected Account does not have an instant contact information: The system skips invoking Send Message To Account use case, and s Send Carpool Request Page. Ride Information(s) is selected: The system s ride information is selected message on Error Page, and s Send Carpool Request Page again. Display Error page Display ride information is selected message Account Ride Request Does Account has instant contact info? Send Message To Account invoke

13 Confirm Availability BASIC COURSE: When the user logs in, the system gets Ride Request Queue from User Account, and s Ride Request Confirm Page. The user clicks Button. The system updates Ride Request as accepted in Central Database, and removes Ride Request from Ride Request Queue. The system s Main Page. ALTERNATIVE COURSE: User Ride Request Confirm Page Click button Click button Get one Request from Queue Is Queue empty? User Account Ride Request Queue is empty: The system s Main Page. The user clicks Button: The system updates Ride Request as declined in Central Database, and removes Ride Request from Ride Request Queue. The system s Main Page. Click Defer button Set Declined Set Accepted Ride Request Retrieve Queue The user clicks Defer Button: The system s Main Page. Update in Central Database Ride Request Queue Login Central Database Main Page Remove from Queue

14 Match Carpool BASIC COURSE: Login The system s Main Page. The user clicks View Ride Request Status Button. The system retrieves Ride Request List from Central Database, and s View Ride Request Status Page with each status in Ride Request List. The user selects an accepted Ride Request and clicks Match Carpool Button. The system retrieves Ride Information from selected Ride Request, removes all Ride Request(s) from all Ride Request Queue(s) and Central Database. The system stores the retrieved Ride Information into Central Database, and invokes Send Message To Account use case to send a confirmation message and Detailed Ride Information to the selected Account. ALTERNATIVE COURSE: The user clicks Match Carpool Button without selecting an accepted Ride Request Confirmation: The system s a Ride Request Conformation must be selected message, and s View Ride Request Status Page again. User clicks View Ride Request Status Button without requesting ride: The system s a message explaining that he/she must request ride before viewing ride request status. The system s Main Page again. User invoke Store Ride Info Into Database Main Page Ride Information Remove All Ride Requests from Queues Central Database Click View Ride Request Status Button Ride Request Queue Determine Requests from Central Detabase Remove All Ride Requests from Database Ride Request List Requests found select Retrieve Ride Info Ride Request Click Match Carpool button View Ride Request Status Page Is a Ride Request is selected Display Ride Request Conformation must be selected message Ride Requested Error Page Error page