1. Robustness Analysis Dr. Neal CIS 480

2. Outline What is robustness analysis? Key roles in robustness analysis Object types found in discovery Diagramming rules Where are the diagram and objects placed in the model Updates to the static model Robustness check list Example robustness analysis Design following robustness

3. What Is Robustness Analysis? Bridge between analysis and design, helps define objects participating in use cases

4. Key Roles in Robustness Analysis Robustness Analysis –Class Discovery - fine missing classes like >, > and > types –Completeness Check – walk through use case scenarios and make sure all alternative paths are covered –Sanity Check – does the use case specify behavior that is reasonable and able to be implemented –Establishes Basis for Sequence Diagrams – quickly drawn and can identify issues prior to building sequence diagrams

5. Object Types Found in Discovery External facing windows, screens, dialogs, menus, in our example web pages. Map to database tables for persistent objects Application logic and process control Reader object Accesses database Tables (author)

6. Diagramming Rules

7. Where are the diagram and objects placed in the model Under the design model since we are moving to design Each robustness class diagram and discovered objects are placed in a folder under a named use case, since these objects are the elaboration (realization) of the use case

8. Per Use Case: Robustness Class Diagram Realize Dependency Object Sequence Diagram Discovered classes: > and > types go here within their respective layer, new > types need to be added to the domain diagram in the Analysis Model Design Class Diagrams: Exist by > and overall within the Solution Domain Model

9. Updates To The Static Domain Model If new entity objects are discovered then the static domain model must be updated Any attributes that were discovered as a part of the process must also be added to the static domain classes

10. Updates To The Static Domain Model

11. Completion Check List

12. Robustness Example TheEyesHaveIt.com “Register a Seller”

13. Use Case Diagram Register a Seller

14. Use Case “Register a Seller” Preconditions –SELLER must not exist in system Use Case Description –Primary Flow: The SELLER is directed to a secure Web page. The SELLER must enter a user name, password, address, telephone, and e-mail address. All data is is validated when the SELLER submits request. The password should be entered twice to verify typing errors. the submit button. –Alternate Flow: The SELLER can cancel the registration process and return to the main page. –Alternate Flow: Data entered is not complete causing registration form to be redisplayed with errors highlighted. –Alternate Flow: The SELLER has previously registered or a duplicate name exists causing the registration form to be redisplayed Postconditions –An entry for SELLER information is created in the database. –An new ACCOUNT is created for the SELLER.

15. “Register a Seller” UI Prototype Incomplete data or duplicate person

16. Robustness Analysis New Objects Potential design objects include: –Registration Page > web page for seller registration –Registration Controller > controller object for managing the registration process –Submit Button > part of the registration web page –Cancel Button > part of the registration web page –Validation Controller > controls the process of data validation

17. Example Robustness Analysis

18. Object Discovery New objects discovered during robustness analysis

19. Design Classes

20. Object Sequence

21. What does the code look like? https://bdnet.bus.cba.nau.edu/gln/robustne ss/App/Menu.aspx