Use Case Analysis - UML-Diagrams - Activity Diagram: 8/18/2012 Latest in IT Industry

UML- Session 3
Use Case analysis UML-Diagrams Activity Diagram
8/18/2012
Latest in IT Industry
UML- Use Case details
Tracking the Steps in the Scenarios Each use case is a collection of scenarios, and each scenario is a sequence of steps.
Use case diagrams is usually part of a design document that the client and the development team refer to. Design document will have details for each diagram use case diagram. Each scenario of each use case will get documented in same format covering following details :
The actor who initiates the use case Assumptions for the use case Preconditions for the use case Steps in the scenario with brief description. Post conditions when the scenario is complete The actor who benefits from the use case
8/18/2012
UML- Activity diagrams
Requirement for Feedback system:

A module is to be designed for collecting semester wise feedback for the teaching staff of the college from the students. A module will use data from students management system , course catalog system. Module should authenticate user when user logs into the system and after validation should display the dashboard having all the subjects details listed as per the current semester of the user. The details should have
Name of logged in user course name and current semester List down all the subject name of the current semester along with the faculty name, total number of lectures conducted, total number of lectures attended by student and link to rate the faculty
When user will click on the link should be taken on rating screen where set of questions along with rating should be displayed. User should answer all the question and rate the faculty on scale of 1-5. If user has already provided feedback then cannot change it again but can view it. Admin should be able to view the all feedback based on individuals users , subject, faculty. Admin should be able to pull and print a reports on the historical data for getting average feedback for each of faculty based on subject-semester.
8/18/2012
UML-Diagram tree
8/18/2012
Activity diagrams are the object-oriented equivalent of flow charts and data-flow diagrams from structured development Activity diagrams describe the workflow behavior of a system The process flows in the system are captured in the activity diagram Activity diagram illustrates the dynamic nature of a system by modeling the flow of control from activity to activity
8/18/2012
UML-Activity Diagram
Activity diagrams can be used to describe the business and operational step-by-step workflows of the components in a system. Basically this diagram intends to shows the overall flow of control. Activity Diagrams are also useful for analyzing a use case by describing what actions need to take place and when they should occur. It is meant for describing a complicated sequential algorithm and modeling applications with parallel processes. Activity diagrams are typically used Business process modeling To model the logic captured by an use case Capture the logic to apply the business rule Depict the activities partitioned by actors
8/18/2012
Activity diagrams are constructed from a limited number of shapes, connected with arrows. The most important shape types:
rounded rectangles represent activities; diamonds represent decisions; bars represent the start (split) or end (join) of concurrent activities; a black circle represents the start (initial state) of the workflow; an encircled black circle represents the end (final state). Arrows run from the start towards the end and represent the order in which activities happen.
8/18/2012
Diagrams are read from top to bottom and have branches and forks to describe conditions and parallel activities. A fork is used when multiple activities are occurring at the same time. The branch describes what activities will take place based on a set of conditions. All branches at some point are followed by a merge to indicate the end of the conditional behavior started by that branch. After the merge all of the parallel activities must be combined by a join before transitioning into the final activity state.
8/18/2012 Latest in IT Industry
Example : creating document Open the word processing package Create a file Save the file under a unique name within its directory Type the document If graphics are necessary, open the graphics package, create the graphics, and paste the graphics into the document If a spreadsheet is necessary, open the spreadsheet package, create the spreadsheet, and paste the spreadsheet into the document Save the file Print a hard copy of the document Exit the word processing package
8/18/2012
8/18/2012
Activity diagrams can be divided into object swimlanes that determine which object is responsible for which activity. Guard expressions (inside [ ]) label the transitions coming out of a branch.
8/18/2012
Requirement for Feedback system:

A module is to be designed for collecting semester wise feedback for the teaching staff of the college from the students. A module will use data from students management system , course catalog system. Module should authenticate user when user logs into the system and after validation should display the dashboard having all the subjects details listed as per the current semester of the user. The details should have
Name of logged in user course name and current semester List down all the subject name of the current semester along with the faculty name, total number of lectures conducted, total number of lectures attended by student and link to rate the faculty
When user will click on the link should be taken on rating screen where set of questions along with rating should be displayed. User should answer all the question and rate the faculty on scale of 1-5. If user has already provided feedback then cannot change it again but can view it. Admin should be able to view the all feedback based on individuals users , subject, faculty. Admin should be able to pull and print a reports on the historical data for getting average feedback for each of faculty based on subject-semester.
8/18/2012
Login Display the dashboard
8/18/2012

Use Case Analysis - UML-Diagrams - Activity Diagram: 8/18/2012 Latest in IT Industry

Uploaded by

Copyright:

Available Formats

Use Case Analysis - UML-Diagrams - Activity Diagram: 8/18/2012 Latest in IT Industry

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Case Analysis - UML-Diagrams - Activity Diagram: 8/18/2012 Latest in IT Industry

Uploaded by

Copyright:

Available Formats

UML- Session 3

Use Case analysis UML-Diagrams Activity Diagram

UML- Use Case details

UML- Activity diagrams

Requirement for Feedback system:

UML- Activity diagrams

UML- Activity diagrams

UML- Activity diagrams

UML- Activity diagrams

UML- Activity diagrams

UML- Activity diagrams

UML- Activity diagrams

Requirement for Feedback system:

UML- Activity diagrams

Login Display the dashboard

You might also like