USECASE DOCUMENTATION

Outline:

Introduction to UML Usecase diagrams: identifying actors and usecases Sequence diagrams Dataflow diagrams Activity diagrams

Introduction:

The Unified Modeling Language (UML) is a standard language for :- 

specifying, visualizing, constructing, documenting ,

the artifacts of software systems, as well as for business modeling and other non-software systems.

o The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems.

o The UML is a very important part of developing objects oriented software and the software development process. 

o The UML uses mostly graphical notations to express the design of software projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software.

Usecase diagrams:

o A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. The two main components of a use case diagram are use cases and actors.

o An actor is represents a user or another system that will interact with the

system you are modeling. A use case is an external view of the system that represents some action the user might perform in order to complete a task.

Use Case Relationships o Between actor and use case.

o Association / Communication.

o Arrow can be in either or both directions;arrow indicates who initiates communication.

o Between use cases (generalization): – Uses

Where multiple use cases share pieces of same functionality.

– Extends

Optional behavior. Behavior only runs under certain conditions (such as alarm). Several different flows run based on the user’s selection.

The primary goals in the design of the UML were: 

o Provide users with a ready-to-use, expressive visual modeling language so they candevelop and exchange meaningful models.

o Provide extensibility and specialization mechanisms to extend the core concepts.

o Be independent of particular programming languages and development processes.

o Provide a formal basis for understanding the modeling language.

o Encourage the growth of the OO tools market.

o Support higher-level development concepts such as collaborations, frameworks, patterns and components.

o Integrate best practices.

Advantages of uml diagrams:

Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML diagrams commonly created in visual modeling tools include:

o Use Case Diagram displays the relationship among actors and use cases.

o Class Diagram models class structure and contents using design elements such as classes, packages and objects. It also displays relationships such as containment, inheritance, associations and others. 

Interaction Diagrams 

Sequence Diagram displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects).Collaboration Diagram displays an interaction organized around the objects and their links to one another. Numbers are used to show the sequence of messages.State Diagram displays the sequences of states that an object of an interaction goes through during its life in response to received stimuli, together with its responses and actions.1Activity Diagram displays a special state diagram where most of the states are action states and most of the transitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven by internal processing.

Physical Diagrams 

Component Diagram displays the high-level packaged structure of the code itself. Dependencies among components are shown, including source code components, binary code components, and executable components. Some components exist at compile time, at link time, at run times well as at more than one time.

Deployment Diagram displays the configuration of run-time processing elements and the software components, processes, and objects that live on

them. Software component instances represent run-time manifestations of code units.

USCASE DIAGRAMS FOR PHARMACY MANAGEMENT SYSTEM:

The modules present in the pharmacy management system are

o ADMINSTRATORo SALES MANo ACCOUNTANT

1. ADMINSTRATOR:

The administrator manages all things in the management of any system. In pharmacy management system, the administrator take a look over product management, customers management, vendors management, category , and discount , reports management as shown in the below usecase diagram.

The following diagram can represent the administrator functionalities of usecase

USECASE NAME: Login

Goal of function:

o Different type of users can do different types of operations, so they must authenticate when they are going to do the application.

Precondition:

o The application is started up.

Description:

user must login into their accounts through this. The system validates the login and password.

Primary actor:

o administrator

Flow of events: username and password are correct. Enter into the main form. Activating the operations that the user able to do.

Alternative flow of events:

username and password are wrong. Show error return to the same window.

USECASE NAME : Employee records

Goal of function:

o The administrator deals with this employee records. Adding , deleting and editing employee list will be managed by this function. Salary details also managed by this.

Precondition:

o The administrator must login into his account.

Description:

o Administrator manages the employee records through this function. The system updates the edited details.

Primary actor:

o administrator

Flow of events:

Login into system by using username and password. Edit the employee details and salary details if need. Update the changes.

Alternative flow of events:

Login account is failed. Produce the error messages.

USECASE NAME : medicine records

Goal of the function:

o This function is used to manage all the medicine records like add medicine, delete medicine, change medicine, purchase, and sale the medicine. Search for the medicine also will be managed by this function.

Brief description:

o Medicine records will be managed by the administrator of the site. This function is helpful to know about the details of the medicine in the pharmacy store.

Primary user:

o Administrator, sales man.

Flow of events:

Enter in to the account Do the changes and update the medicine if need, by using the

operations that allowed for the user. Update the changes.

Alternative flow of events:

o login failedo Generate the report.

USECASE NAME : change password

Goal of the function:

o User can change password of his account through this , to provide more security .

Brief description :

o Change password function can be used by any user, who has account in the site. With help of this, user can change his password to avoid the hacking disturbances.

Primary user:

o Administrator, end-user, accountant. All are primary users.

Precondition: o User must have login account.

Flow of events:

Enter the login details Choose change password option. Change the password, and update the user details.

Alternative flow of events:

Login details are wrong. Discard the process, by generating the report.

USECASE NAME: log out.

Goal of the function:

o Any users can logout from their accounts through this, after performing the operations.

Brief description:

o User who can login into their accounts can becomes logout through this function. Any user who has registered in the site can use this function.

Primary user:

o Administrator, end-user, accountant. All are the primary users.

Flow of events:

Enter the details. Perform the operations that are allowed to the user. Update the changes. Logout from the account.

Alternative flow of events:

Entered details are wrong. Generate the report.

1.1 End user:

The end-user is nothing but a customer who registered in the site. He may order the product by login into his account.The below diagram shows the use case diagram for the end user.

USECASE NAME: registration

Goal of function:

o The main thing is, through this function customers can create their accounts in the site, and can order for the required products.

Precondition:

o The user should have only single account with his original details. Should not have more than two accounts.

Primary actor:

o End user.

Flow of events:

The user fills up the registration form present in the site. After the completion of the process he login into his account. Moreover, orders for the required product.

Alternative flow of events:

User entered details are wrong.

Generate the error reports. Discard the registration process.

2. Sales man:

The sales man is another actor, who plays the important role in selling of the medicine. The following use case diagram describes briefly, the functions that can be performed by the sales man.

USECASE NAME: salary.

Goal of the function:

o This function is helpful to know the salary details of the employee , who is working the system currently.

Brief description:

o The employees who are working in the pharmacy system can know their salary details through this function. It gives the full information about the salary details of a particular employee.

Primary actor:

o Sales man.

Precondition:

o Sales man should have an account.

Flow of events:

Login into the account. Know about the salary details. Logout from the account.

Alternative flow of events:

Login failed. Generate the error report.

USECASE NAME: print bill.

Goal of the function:

o After selling the medicine, the sales man must print the bill. This helps to know about the medicines that are sold by the sales man, depending upon this report salary details are updated.

Brief description:

o This function is can be used by the sales man, and accountant. Helps to know about the billing details.

Precondition:

o Medicine should be sold before printing the bill.

Primary actors:

o Sales man.

Flow of events:

Sale the medicine.

Update the changes. Print the bill.

Alternative flow of events:

Medicine not present in the store. Stop the sale.

3. ACCOUNTANT:

o The payment details will be managed by the accountant. He can login into his account and collects all bills that are printed by sales man. And updates the payments.

o The brief usecase diagram about the accountant is shown bellow.

USECASE NAME: medicine sales .

Goal of the function: o To know details about the medicine sales.

Brief description:

The accountant can deals with this function. It helps to know about the information which medicine was sold, which is required and other details.

Primary actor:

o Accountant.

Precondition:

o The medicine should present in the store.

Flow of events:

Enter login details. Collect the bills and perform the updating. Logout from the account.

Alternative flow of events:

Login failed. Generate the error report.

USECASE NAME: medicine purchase.

Goal of the function:

o Help to know the information about which medicine is required to purchase.

Brief description:

o This function is used by the accountant. He generates the reports about which medicine is need to purchase, its demand, its quality, and quantity and amount need to purchase that medicine.

Primary actor:

o Accountant.

Precondition:

o required medicine should be specified with it’s importance.

Flow of events :

Enter login details.

Generate the report about medicine required. Update the changes. Logout from the account.

Alternative flow of events:

Login details are failed. Generate the report.

USECASE NAME: collect bill.

Goal of the function:

o This will generate the details about bills.

Brief description:

o Bills contain the information about medicines sold by the sales man. This will be managed by the accountant.

Primary actor:

o Accountant.

Precondition:

o User must register into the account.

Flow of events :

Login into account. Collect all bills. Generate the report. Update the payment details. Logout from the account.

Alternative flow of events:

Login failed. Generate the error report.

Sequence diagrams:

For performing operations:

: AdministratorLogin Product Admin Customer

AdminVendors Admin Category

AdminDiscount

Admin : End User : End User : End User : End User

(id,pwd)

(validate())

(select option)

(select option)

(select option)

(select option)

(select option)

For enduser registration:

: E n d U s e r

R e g is t ra t io n L o g in O r d e r P ro d u c t

( E n t e r d a t a )

( id , p w d )

( va l i d a t e ( ) )

( e n t e r p ro d u c t i n fo )

Data flow diagrams:

At context level:For administration module:

For customer module:

ADMINISTRATIONPharmacy system

Request

Response

CUSTOMERPharmacy System

Request

Response

For entire pharmacy system:

OrderDetails

ProductsInformation

VendorInformation

Pharmacy System

DirectOrdering

User IdPassword

User IdPassword

User IdPassword User Id

Password

Signup

For validation of the password:

Signup ValidationProcess

Display Total

Information

RegistrationProcess

USER

Customer Table

ErrorCustomer ID

YES

User

InformationMessage

User

Information

Message

For product information:

Amount table

Discount table Product tables Discount table

OrderingProducts

ProductInformation

OrderProcessing

PaymentProcess

User Id Password

Category Name

Qty, tax,discount

AmountPayment Mode

DiscountProductInformation

Order Information

USER

ACTIVITY DIAGRAMS

For validation of password: