S b Ph ub-Phase Low Level Design (cont)
Contents
1. Janice Regan 2008 _ _ Refined Scenario 1 Use Case Name ChecklnResource 7 Scenario Student Patron Paul returns a book on time Preconditions Librarian Eva has successfully gained access to the LMS LMS is ready to go DB has been populated network is up and LMS has been initialized LMS screen with Check menu is displayed Janice Regan 2008 a Refined Scenario 1 Main flow of events 1 Student Patron Paul comes up to the librarian counter to return the Quantum Physics book he borrowed last week Eva the Librarian chooses CheckI nResource option from the LMS screen by selecting the In command option under the Check menu 3 A window representing a Check In Form is then displayed Janice Regan 2008 Refined Scenario 1 Main flow of events cont 4 Eva takes the book Paul is handing to her and types in its Dewey call number in the appropriate text field then presses the Accept button to commit the entry The Dewey call number for the book was entered successfully and it was a valid call number information about the Quantum Physics book and the borrowing patron is retrieved from the Database and displayed on the Check In screen Janice Regan 2008 _ SSE Refined Scenario 1 Main flow of events cont Since Student Patron Paul is returning the Quantum Physics book before its due date there is no overdue cha2. List of requested resources Outstanding fees Resource borrowing limits get ExpiryDate getName checkIn call create student db Janice Regan 2008 Resource Title Borrowing Patron s ID Resource Type Dewey call number Status Due Date Date of Loan Date of Return Daily overdue fee Maximum overdue fee Rewinding fee getBorrowingPatronld get Title getAuthor getLoanDate get DueDate getStatus checkin date create book db Discovering more methods To be sure we have all the methods for a class we need to consider all use cases that involve that class and all the scenarios associate with each of these use cases Remember that although there is one class diagram for the system there is at least one collaboration diagram or sequence diagram for each use case A collaboration diagram or sequence diagram can contain information for more than one scenario associated with a particular use case Usage of discovered methods must be consistent between all use cases and scenarios Janice Regan 2008 12 Creating interaction diagrams ki Note that either a sequence diagram or a collaboration diagram can be derived directly from your use case and scenarios It is also possible to translate a collaboration diagram into a sequence diagram or a sequence diagram into a collaboration diagram The development of interaction diagrams represent an e
3. 2 1 paul create student db VARAI ok update paul Paul Student 2 1 2 ok r W1 1 1 QPBook create book db update QPBook 2 1 1 flag done checkin call db LibraryDB QPBook Book 1 8 loanDate getLoanDate 1 9 dueDate getDueDate _1 1U status getotatus done ok checkin dat equence Diagram Librarian Press done or cancel Set status reshelve Set loan date Set due date 0 Set return date today date Set borrowing patron id 0 Remove QPBook from list of borrowed resources ok update QPBook th a Display startpage ok update paul f au Collaboration Diagram C J 1 11 display checkInpage 1 checkin Dewey call 422 okz update paul tw ay 2 4 ok update QPBook LibrarySystem Librarian 1 1 QPBook getResource call paul getPatron patronid 1 4 name getName 1 5 expiryDate getExpiryDate db LibraryDB 2 2 flag done ch eckin call H 1 2 1_paul create student db Paul Student 1 1 1 QPBook create book db qi patronid getBorrowingPatronld 1 7 author getAuthor QPBook Book eine eeb anDate getLoanDate b pate act oa etDueDate 4 1 flad donel ok checkin date kin dat 11 JA Patron and Resource class attributes Name Address Phone Patron ID Patron Type List of borrowed resources
4. Sub Phase Low Level Design cont Map of design phase DESIGN HIGH LEVEL DESIGN DESIGN a ee er Data Persistant Subsystem Module Interfaces Classes Interaction Diagrams Modularization Class Interfaces architecture Ser Interface User Manual Implementation Janice Regan 2008 2 LLL Low Level Design Objective of Low Level Design Refine representation models of software system to a level of detail that will allow resulting representation to be used as a blueprint for implementation and unit test planning phases Janice Regan 2008 aoa Interaction Diagrams Model dynamic aspects of the software system by specifying the interaction among objects to produce a particular behaviour For each use case Show object interaction Show how software system realizes a use case Help identify object operations methods Janice Regan 2008 4 _ Interaction Diagrams Two types of interaction diagrams are defined in UML Collaboration diagram emphasizes the structural organization of objects that send and receive messages Sequence diagram emphasizes the time ordering of the messages passed between objects However both diagrams are not computationally complete they are not algorithms gt They do not define the behaviour Janice Regan 2008 dt Modeling at different phases Static Dynamic 1 System Context Diagram 2 In
5. formal Scenarios 3 Class Diagram 4 Use cases 5 Use cases Diagrams 6 Scenarios Requirements analysis 8 Analyze data persistence N 7 Architecture from 1 4 5 6 f High Level 9 Refined use cases from 4 7 8 Design 10 Sequence Diagrams from 9 11 Refined Class Diagram 12 Refined use cases and scenarios Low Level including attributes and _ from 9 Design methods from 3 12 13 43 Refined Sequence Diagrams and Janice Regan 2008 collaboration diagrams from 12 UML Notational Elements of Collaboration Diagram Link Object object Class Sequence of message Message Condition response method parameters OO initiating actor Janice Regan 2008 m Creating Collaboration Diagrams Summary 1 scenario use case per collaboration diagram Identify participating classes objects Determine messages to be sent parameters to carry out the behaviour by reading scenario use case Look at 1 scenario per use case What changes for other scenarios Introduce solution for object persistence if needed Janice Regan 2008 JA Refined Scenario 1 Use Case Name CheckinResource 7 Scenario Student Patron Paul returns a book on time Preconditions Librarian Eva has successfully gained access to the LMS LMS is ready to go DB has been populated network is up and LMS has been initialized LMS screen with Check menu is displayed
6. n date Set status reshelve Set loan date Set due date 0 Set return date today date Set borrowing patron id 0 ok update QPBook checkin call Remove QPBook from x list of borrowed resources update paul checkin ok update ok display checkInPage Display startpage diagram A Collaboration startpa LibrarySystem Librarian et ils Sear Seno 1 4 name getName 1 5 expiryDate getExpiryDate 1 12 flag done checkin call 1 3 1 paul create student db d2 ok update paul Paul Student A 1 1 1 QPBook create book db PA patronid getBorrowingPatronld 1 7 author getAuthor QPBook Book I q Ld loanDate getLoanDate etLoanDate b pate act oe etDueDate q Litlilaa donel ok checkin date db LibraryDB 1 11 1 ok update QPBook Sequence Diagram 2 B Librarian done or cancel flag done ok chgckin date Set status reshelve Set loan date 0 Set due date Set return date today date Set borrowing patron id 0 Remove QPBook from ok update list of borrowed resources and E ok update QPBook ok checkin call Display startpage gration Diagram 2 verify checkinpage LibrarySystem Librarian 1 4 name getName 1 5 expiryDate getExpiryDate H 1
7. rge Also no one is currently requesting the Quantum Physics book LMS completes the check in process by changing the status of the book to reshelve canceling its due date and date of loan updating its date of return to today Clearing the borrowing patron ID removing the Quantum Physics book from the Student Patron Paul s list of borrowed resources Janice Regan 2008 Refined Scenario 1 Main flow of events cont LMS updates the records for the Quantum Physics book and the borrowing Student Patron Paul in the Database LMS updates the screen showing the newly checked in book along with the updated dates Eva verifies by looking at the screen that the book has been checked in properly then presses the Done button Janice Regan 2008 penned SITEU 1 Postconditions Student Patron Paul s record is now showing that he is no longer borrowing the Quantum Physics book The Quantum Physics book has now a Status of reshelve today s date as a date of return date of loan has been cleared and so has the due date Janice Regan 2008 Sequence Diagram 1 LibrarySystem db LibraryDB heckin Dewey call author getAuthor loanDate getLoanDate dueDate getDueDate status getStatus _ Sequence Diagram 2 A Librarian LibrarySystem ap Book Book Book Paul Pau Student db a Library m ok checki
8. volution of your model from abstract class diagram to more concrete Need to summarize the addition information back to the class diagram Add more detail to the methods and attributes on the class diagram Janice Regan 2008 13
Download Pdf Manuals
Related Search