Object Oriented Software Engineering

Published on June 2017 | Categories: Documents | Downloads: 24 | Comments: 0 | Views: 161
of 11
Download PDF   Embed   Report

Comments

Content

30-01-14

Practical 3

AIM : To create a Use Case diagram showing extend, include and uses relationship . Relationship in Use Case: Use cases share different kinds of relationships. A relationship between two use cases is basically a dependency between the two use cases. Defining the relationship between two use cases is the decision of the modeler of the use case diagram. This use of an existing use case using different types of relationships reduces the overall effort required in defining use cases in a system. Use case relationships can be one of the following: Extend relationship : An extends shows the relationships between use cases. Relationship between use case A and use case B indicates that an instance of use case B may include (subject to specified in the extension) the behavior specified by A. An 'extends' relationship between use cases is depicted with a directed arrow having a dotted shaft. The tip of arrowhead points to the parent use case and the child use case is connected at the base of the arrow. The stereotype “<extends>” identifies as an extend relationship as shown in figure 3.1. For example, validating the user for a system. A invalid password is extension of validating password use case as shown in figure 3.1.

Figure 3.1 An example of an extend relationship

Include/Uses relationship :
8|Page OOSE Practical Lab

When a use case is depicted as using functionality of another functionality of another use case, this relationship between the use cases is named as an include or uses relationship. In other words, in an include relationship, a use case includes the functionality described in the another use case as a part of its business process flow. A uses relationship from use case A to use case B indicates that an instance of the use case will also include the behavior as specified by B. An include relationship is depicted with a directed arrow having a dotted shaft. The tip of arrowhead points to the child use case and the parent use case connected at base of the arrow. The stereotype “<include>” identifies the relationship as an include relationship.

Figure 3.2 An example of an include/uses relationship.

Use CaseDiagram for Library Management System
9|Page OOSE Practical Lab

Issue or Returns Book .Also enquire about his account Pay fine

LIBRARY MANAGEMENT SYSTEM

Works under supervision of Admin Enter Book info . Student info check and validate Read only access to database

Pay FIne <<extend>>

Return book

Controls and maintain database system & software properties

Student

Enquire

Librarian

<<extend>>

Issue book

Database Update Student Details <<include>>

Admin

Account Modification

<<include>>

Generate Report

30-01-14

Practical 4
10 | P a g e OOSE Practical Lab

AIM : To create Sequence diagram for Library Management System . Sequence Diagram : A sequence diagram, in the context of UML, represents object collaboration and is used to define event sequences between objects for a certain outcome. A sequence diagram is an essential component used in processes related to analysis, design and documentation. A sequence diagram is also known as a timing diagram, event diagram and event scenario. The main purpose of a sequence diagram is to define event sequences that result in some desired outcome. The focus is less on messages themselves and more on the order in which messages occur; nevertheless, most sequence diagrams will communicate what messages are sent between a system's objects as well as the order in which they occur. The diagram conveys this information along the horizontal and vertical dimensions: the vertical dimension shows, top down, the time sequence of messages/calls as they occur, and the horizontal dimension shows, left to right, the object instances that the messages are sent to.

11 | P a g e

OOSE Practical Lab

Sequence diagram for Issue Book

12 | P a g e

OOSE Practical Lab

Sequence diagram for Return book

13 | P a g e

OOSE Practical Lab

Sequence diagram for Pay Fine

14 | P a g e

OOSE Practical Lab

Sequence diagram for Account Modification

15 | P a g e

OOSE Practical Lab

Sequence diagram for Enquire

Sequence diagram for Student Details
16 | P a g e OOSE Practical Lab

17 | P a g e

OOSE Practical Lab

Sequence diagram for Generate Report

18 | P a g e

OOSE Practical Lab

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close