Use case 1: User Login: Actor: Admin, Faculty, or Student Basic Flow 1. User clicks the login link or enters the login URL into the browser. 2. The system displays login page. 3. User clicks login (Submit) button after entering the credentials and roles. 4. According to the role, the system retrieves a “User List”. 5. The system checks to see if the username exists in the “User List”. 6. If the account exists, the system compares the password. 7. If the input password is valid, based on the role provided, the system starts an authenticated session, retrieve Faculty List and displays View Faculty page (landing page). Alternate Flow Invalid username or password: The system checks to see if the username exists in the “Users”. If the username is not found, the system displays a message “Invalid username. Click on “OK” to try again.” The user clicks on the “OK” button. The system redisplays login page. User clicks on the forgot username link. The system asks user to enter his/her email address. User enters the email address associated with his/her account. The system displays a message ”Username was sent to your email.” Use Case 2: Admin Adds Student Normal Flow: 1. Admin selects the “Students” tab in the “Admin home page”, 2. System retrieves Student_list and displays “Student View” page. 3. Admin clicks “New Student” button. 4. System displays “Add student” page. 5. Admin Provides student details by selecting the institute name from dropdown box, enters student’s details 6. Admin clicks on “Save” button. 7. System validates the entered data; 8. System Save data to the database, if valid. 9. System displays successfully saved message on top of student list, which includes the new added student. Use case 3: Team Member Makes Comments on Assessment Done by other Members: Basic Course: 1. Student clicks “Make a Comment” button on the “ViewPeerAssessment” Page. 2. The system checks the Session to make sure the student is logged in and then displays a Write Comment page with a multi-line Text box. 3. Student writes a comment on the comment box. 4. Student clicks on the “Save” button. 5. The system validates the comment (e.g. not too long, or too short). 6. If the comment validation is ok, the system display a confirmation page, and send the comment to Instructor for approval. States Machine for “comments on assessment” Comments created by evaluate Comments Approved by instructor Comments displayed to students Comments disapproved by instructor Comments revised by evaluate Alternate Course Too long or short comment: The system displays a message “Comment length is out side the allowable range. Click on “OK” to try again.” Robustness Analysis OutlineWhat is robustness analysis?Key roles in robustness analysisObject types found in discoveryDiagramming rulesWhere are the diagram and objects placed in the modelUpdates to th ...

1. Use case 1: User Login:
Actor: Admin, Faculty, or Student
Basic Flow
1. User clicks the login link or enters the login URL into the
browser.
2. The system displays login page.
3. User clicks login (Submit) button after entering the
credentials and roles.
4. According to the role, the system retrieves a “User List”.
5. The system checks to see if the username exists in the “User
List”.
6. If the account exists, the system compares the password.
7. If the input password is valid, based on the role provided, the
system starts an authenticated session, retrieve Faculty List and
displays View Faculty page (landing page).
Alternate Flow
Invalid username or password: The system checks to see if the
username exists in the “Users”. If the username is not found, the
system displays a message “Invalid username. Click on “OK” to
try again.” The user clicks on the “OK” button. The system
redisplays login page. User clicks on the forgot username link.
The system asks user to enter his/her email address. User enters
the email address associated with his/her account. The system
displays a message ”Username was sent to your email.”

2. Use Case 2: Admin Adds Student
Normal Flow:
1. Admin selects the “Students” tab in the “Admin home page”,
2. System retrieves Student_list and displays “Student View”
page.
3. Admin clicks “New Student” button.
4. System displays “Add student” page.
5. Admin Provides student details by selecting the institute
name from dropdown box, enters student’s details
6. Admin clicks on “Save” button.
7. System validates the entered data;
8. System Save data to the database, if valid.
9. System displays successfully saved message on top of student
list, which includes the new added student.

3. Use case 3: Team Member Makes Comments on Assessment
Done by other Members:
Basic Course:
1. Student clicks “Make a Comment” button on the
“ViewPeerAssessment” Page.
2. The system checks the Session to make sure the student is
logged in and then displays a Write Comment page with a multi-
line Text box.
3. Student writes a comment on the comment box.
4. Student clicks on the “Save” button.
5. The system validates the comment (e.g. not too long, or too
short).
6. If the comment validation is ok, the system display a
confirmation page, and send the comment to Instructor for
approval.
States Machine for “comments on assessment”
Comments created by evaluate
Comments Approved by instructor
Comments displayed to students
Comments disapproved by instructor
Comments revised by evaluate
Alternate Course
Too long or short comment: The system displays a message

4. “Comment length is out side the allowable range. Click on
“OK” to try again.”

5. Robustness Analysis

6. OutlineWhat is robustness analysis?Key roles in robustness
analysisObject types found in discoveryDiagramming
rulesWhere are the diagram and objects placed in the
modelUpdates to the static modelRobustness Analysis
StepsExample robustness analysisDesign following robustness
What Is Robustness Analysis?
Bridge between analysis and design, helps define objects
participating in use cases
Key Roles in Robustness AnalysisRobustness AnalysisClass
Discovery - fine missing classes like <<control>>,
<<boundary>> and <<interface>> typesCompleteness Check –
walk through use case scenarios and make sure all alternative
paths are coveredSanity 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
Object Types Found in Discovery
External facing
windows, screens,
dialogs, menus, in
our example web
pages.

7. Map to database
tables for
persistent objects
Application
logic and process
control
Reader
object
Accesses
database
Tables (author)
Diagramming Rules
Updates To The Static Domain Model
Robustness analysis steps:
Decompose narrative use case flow into “steps”.
Use objects from the domain model and link them together to
simulate these steps.
Add missing classes and associations in the domain model
during step (2).
Use terms from the domain model to disambiguate the use case
during step (2).
Complete other information in use case text that might be

8. missing during step (2).
Alternative flows in use case descriptions may be highlighted or
colored in the robustness diagram to distinct from the nominal
flow.
Robustness Example
TheEyesHaveIt.com
“Register a Seller”
Use Case Diagram
Register a Seller
Use Case “Register a Seller”Preconditions SELLER must not
exist in systemUse Case DescriptionPrimary 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 redisplayedPostconditionsAn entry for SELLER
information is created in the database.An new ACCOUNT is
created for the SELLER.
“Register a Seller” UI Prototype

9. Incomplete data or duplicate person
Robustness Analysis New ObjectsPotential design objects
include:Registration Page <<boundary>> web page for seller
registrationRegistration Controller <<controller>> controller
object for managing the registration process Submit Button
<<boundary>> part of the registration web pageCancel Button
<<boundary>> part of the registration web pageValidation
Controller <<controller>> controls the process of data
validation
Example Robustness Analysis
Object Discovery
New objects discovered during robustness analysis
Design
Classes
Object

10. Sequence
Youtube ResourceUML Tutorial 5.1 - Basics of UML Sequence
Diagrams for Robustness Analysis in Eclipse with
Papyrushttps://www.youtube.com/watch?v=aKNh08Vq_78
Assignment – Requirements
for Use Cases Revise Use case: two-paragraph description (main
flow and alternative flow)numbered listCreate activity diagram
for each use case based on:Main flow Domain modelScreen
mock-upsRobustness AnalysisRobustness Diagram
Use case example
Robustness Analysis
Use case description with domain model
*
Robustness Diagram
Revised usecase description, revised domain model and
robustness diagram
*

11. Quality Attributes of Robustness Diagrams
Use case description with domain model
*
Revised usecase description, revised domain model and
robustness diagram
*
Register a seller
Seller
(from Actors)
Register
<<communicate>>
Validation Controller
Registration Controller
process registration
Account
(from Business Domain Model)
create
SellerEntity
(from Business Domain Model)
1
1
1
1
create
Submit Button
registration info
Cancel Button
Registration Page
highlight bad entries
displays
displays
cancel

12. IN: new registration from
authentication page
OUT: processed registration to
authentication page
OUT: cancel to main menu
Seller
(from Actors)
Enter Info
submit
Cancel
`
Perform robustness analysis:
1. Decompose narrative use case flow into “steps”.
2. Use objects from the domain model and simulate these steps
with a swim lane Activity diagram.
3. Add missing classes and associations in the domain model
during step (2).
4. Use terms from the domain model to disambiguate the use
case during step (2).
5. Complete other information in use case text that might be
missing during step (2).
6. Following diagramming rules, develop a robustness diagram
for each use case using MVC architectural pattern. The general
objects layout in the robustness diagram: view objects are on
left side; entity objects are on the right side; the controllers are
in the middle. Alternative flows in use case descriptions may be
highlighted or colored in the robustness diagram to distinct
from the nominal flow.