Sunteți pe pagina 1din 17

EXPERIMENT: 1

SOFTWARE INTRODUCTION
RATIONAL ROSE: ROSE = Rational Object Oriented Software Engineering. Rational Rose is a powerful visual modeling tool to aid in the analysis and design of objectoriented software systems. It is used to model the system before writing any code, so one can be sure that the system is architecturally sound from the beginning.

CAPABILITIES:

It helps with system analysis by enabling us to design use cases and Use Case diagrams to show the system functionalities. It will let us design Interaction diagram to show how the objects work together to provide the needed functions. A Class diagrams can be created to show the classes in a system and how they relate to each other. Component diagrams can be developed to illustrate how the classes map to implementation components. Finally, Deployment diagrams can be produced to show the network design for the system.

There are four views in Rational Rose:

1) Use Case view 2) Logical view


OBJECT ORIENTED SOFTWARE ENGINEERING

3) Component view 4) Deployment view USE CASE VIEW: The Use Case view is an implementation-independent look at the system. It focuses on a high-level picture of what the system will do, without worrying about the details of how the system will do. Use Case view includes: Actors, Use cases, Associations, Use case documentation, Use Case diagrams, Sequence diagrams, Collaboration diagrams, Packages.

LOGICAL VIEW: The Logical view focuses on how the system will implement the behavior in the use cases. It provides a detailed picture of the pieces of the system, and describes how the pieces interrelate. With these detailed elements, developers can construct a detailed design for the system. Logical view includes: Classes, Class diagrams, Associations, Interfaces, Sequence diagrams, Collaboration diagrams, State chart diagrams, Packages.

COMPONENT VIEW: The Component view contains information about the code libraries, executable files, run-time libraries, and other components in your model. The Component view of the system allows you to see the relationships between the modules of code. Component view includes: Components, Interfaces, Component diagrams, Packages

DEPLOYMENT VIEW: The Deployment view is concerned with the physical deployment of the system, which may differ from the logical architecture of the system. The Deployment view contains processors, devices, processes, and connections between processors and devices. All of this information is diagrammed on a Deployment diagram. The interface may be separated from the business logic and the database logic. Deployment view includes:

Processes, Processors, Connectors, Devices, Deployment diagram.

The tool Objectory was created by the team at Objectory AB to implement the OOSE methodology. After success in the marketplace, other tool vendors also supported OOSE.
OBJECT ORIENTED SOFTWARE ENGINEERING

After Rational Software bought Objectory AB, the OOSE notation, methodology, and tools became superseded. As one of the primary sources of the Unified Modeling Language (UML), concepts and notation from OOSE have been incorporated into UML. The methodology part of OOSE has since evolved into the Rational Unified Process (RUP). The OOSE tools have been replaced by tools supporting UML and RUP. OOSE has been largely replaced by the UML notation and by the RUP methodology.

Difference between Object Oriented Software Engineering & Software Engineering

1. 2. 3. 4. 5. 6. 7.

Object Oriented Software Engineering (OOSE) It uses OOPs concept. Provide encapsulation. Provide inheritance Models are not obsolete. Contains SE as its part. Not intangible. Independent flow of objects.

Software Engineering (SE) Does not use OOPs concept. No encapsulation. No inheritance. Models are obsolete. Does not have OOSE as its part. It is intangible. No objects are used.

OBJECT ORIENTED SOFTWARE ENGINEERING

EXPERIMENT: 3

AIM: To design use case diagram & class diagram for Library Management system. Requirements: Rational Rose Software, Processor: Min 450 MHz, RAM: Min 256 MB, Available Disk Space: 400 MB (Product Image), + 50 MB (Work Space)

Administrator

Log in Data Base

Search

User

User Profile

Modify Update Add User Check Status

Log in

User Id

Fine Check

Reciept

Exit

Profile Check

New account

Use Case Diagram for Library Management System Database Package:

OBJECT ORIENTED SOFTWARE ENGINEERING

Book Category

Departments Cd/DVD's

e papers Book Details Projects Accesories Issue/unissue

New Arrivals Magazines Reference Book

Book Category Package:

Novels Computers Religious Book

Medical

Book Selection

Accountancy

Management

Humanities

Electronics

NewUseCase

mathematics

USE CASE REPORTS:

Administrator Use Case Report: U USE CASE Login Update D DESCRIPTION ESCRIPTION The Administrator has to Login In in order to begin his work Update all the records .

OBJECT ORIENTED SOFTWARE ENGINEERING

Add User Check Status Modify Fine Check Search

Add new user to the system. Check Status of the System and users. Modify the contents of the system & user details. Check the fine generated. Search for the availability required book.

User Use Case Report: USE CASE Login Search Profile Check New Account User Id DESCRI DESCRIPTION ESCRIPTION PTION The User has to Login In in order to get the services. Search for the availability required book. Check the User profile using user id and password. Creating a new account. Entering the user Id.

Admin Update Id Us er Update() Book Update() Database Update() ID DOB Address Search() Feedback() Queries() Manage database() User management()

Spec ial Us er ID Search() Update() Feedback () Queries() Special rate() Log in Us ernam e Password Us ernam e/Password Check()

User ID Login() profile c heck() search() feedeback() database() update()

Class Diagram for Library Management system

OBJECT ORIENTED SOFTWARE ENGINEERING

EXPERIMENT: 2
AIM: To design the use case diagram & class diagram for ATM System. Requirements: Rational Rose Software, Processor: Min 450 MHz, RAM: Min 256 MB, Available Disk Space: 400 MB (Product Image), + 50 MB (Work Space)

User

Atmost 3 times p...

If Valid Card Check Pin Check

Correct Display screen

If Unvalid

Incorrect

Withdrawl type

Exit

Use Case Diagram for ATM System Package : Withdrawal Type


OBJECT ORIENTED SOFTWARE ENGINEERING

C u rre nt A c c o un t

S a vin g A c c ou nt

W it hdra w l A

W it hd ra w l B

Package : Withdrawal A

OBJECT ORIENTED SOFTWARE ENGINEERING

Blance Enquiry

Mini Statement

Display screen A

Transaction

Status Check A Reciept A If Available

If Not Display Screen A 1 Transaction Mode A

Yes

If Available

Self Operation A

Update A

If Yes End Process A Display Screen A 2

Package : Withdrawal B

OBJECT ORIENTED SOFTWARE ENGINEERING

Balance Enquiry

Mini Statement

Transaction B

Display Screen B

Reciept B

Status Check B

If Available

If Not Display Screen B 1 Yes Transaction Mode B If Available

Self operation B

Update B

If Yes End Process B Display Screen B 2

USE CASE REPORTS: User Use case report: USE CASE Card Check Pin Check Exit DESCRIPTION Check the validity of ATM card Check the validity of PIN Exit in case of invalid card or pin or after successful usage of system

OBJECT ORIENTED SOFTWARE ENGINEERING

Log in Username Password Username/Password Check()

W ithdrawal Pin Update() Transaction()

User Operation ID Name Address DOB Tel E-Mail id Balance Enquiry Pin Balance Check() Mini Statement() Enter pin() W ithdrawal() Change pin() Balance Enquiryt() Transfer Money() Language selection()

Update Id User Update() Balance Update() Pin Update() Transfer Update()

Class Diagram for ATM system

EXPERIMENT: 4
OBJECT ORIENTED SOFTWARE ENGINEERING

AIM: To design use case diagram & class diagram for Parking System. Requirements: Rational Rose Software, Processor: Min 450 MHz, RAM: Min 256 MB, Available Disk Space: 400 MB (Product Image), + 50 MB (Work Space)

manage workers Assign Jobs

Access Grant

Manage Payment

Area Assignment user

manage accounts admin Payment check operator Entry/Exit Vehical Parking Payment

customer verification Decide Rates

Manage Parking Parking Status

Slip provider

Security Customer Authoriztion

Guard Parking Assistance

Use Case Diagram for Parking System USE CASE REPORTS: Admin Use Case Report: USE CASE DESCRIPTION Assign Jobs Assign job to the right person for a particular work. Manage accounts Manage the accounts for the parking lot. Customer Customer Verification is also done by the admin Verification Decide Rates Deciding rates according to the vehicle & time. Security Security arrangements for the vehicles + Security check . Payment Check Checking the payment made. Access Grant Granting permission to various seekers of system. Manage workers Manage the workers under the system. Operator Use Case Report:
OBJECT ORIENTED SOFTWARE ENGINEERING

USE CASE Slip Provider Entry/Exit Area Allotment Manage Payment Access Grant Parking status Manage parking

DESCRIPTION Provide slip to the system users or customers. Entry and Exit permission is granted by the operator. Allotting the appropriate area for vehicle parking. Managing the payment. Granting permission to various seekers of system Frequently checking the status of parking area Parking management is also done by the operator.

User Use Case Report: USE CASE Vehicle Parking Entry/Exit Payment DESCRIPTION Using the services of the system Entry/Exit for/after using the services of system. Making the required payment as per system.

Guard Use Case Report: USE CASE Parking Assistance Entry/Exit Customer Authorization Vehicle Parking DESCRIPTION Assisting the user in parking. Managing Entry/Exit of the vehicles. Customer Verification is also a part of guards job. Parking the vehicle for the user.

OBJECT ORIENTED SOFTWARE ENGINEERING

A dm in ID DOB A ddres s M anage W ork er() A s s ign Jog() M anage A c c ount() Cus tom er V eri() Rate M anagem... ent() P ay m ent Chec k () G rant A c c es s () S ec urity Chec k ()

Guard ID S ec urity () E ntry /E xit() P arking A s s is tance() V ehic al P arking() Cus tom er A uthoriz ation() ...

Operator ID DO B P arking S tatus () S lip P rovider() E ntry /E xit() P ay m ent M anagem ent() ... A rea m anagem ent() Us er ID E ntry /E x it() V ehic al P arking() P ay m ent()

Class Diagram for Parking System

OBJECT ORIENTED SOFTWARE ENGINEERING

EXPERIMENT: 5

AIM: To design use case diagram & class diagram for travelling agency System. Requirements: Rational Rose Software, Processor: Min 450 MHz, RAM: Min 256 MB, Available Disk Space: 400 MB (Product Image), + 50 MB (Work Space)

M anage D B

M anage A c c ounts

A c c ount

R ating F eedbac k

Q uery Res olution E x t ra Loc ations E x tra F ac ilities

M anager S earc h Loc ation

A gen t

Cus tom er

R eques t P as s enger Info S earc h Cus tom er M ediator

P lans Ty pe O f V ehic le P ay m ent Chec k S ign In/Up A c c es s G rant Cus tom er V erific ation

P ay m ent B ook P lan

F air & A c c om odation

Use Case Diagram for Travelling agency System

OBJECT ORIENTED SOFTWARE ENGINEERING

Package : Types Of Vehicles


P c a eT p OV h le a k g y e f e ic

XV U

A C Cr a

SV U

N nA o C

Tx ai

S ee le p r

D lu ex

Bs u

V lv oo

D u leD c e ob ek r

Spr s u efa t

R jd a i a hn

Ta r in

Sa b d h ta a i

E pe s xrs

Eoo y c nm

F h lig t

Bs es u in s

OBJECT ORIENTED SOFTWARE ENGINEERING

L o g in U s e rn a m e P a s s w o rd U s e rn a m e / P a s s w o rd C h e c k ( )

S y s te m M a n a g e ID Nam e A d d re s s DOB Tel E - M a il A d d C u s t o m e r() M o d i fy C u s t o m e r() In fo rm a t io n () vie w re p o rt s () B a c k u p () S e a rc h D a ta b a s e ()

U p d a te Id C u s t o m e r U p d a t e () D a t a b a s e U p d a t e () A g e n t U p d a te () P ro fil e u p d a t e () In fo rm a t io n U p d a t e () F a re U p d a t e ()

A gent ID DOB R e q u e s t( ) S e a rc h ( ) Q u e r ie s () A c c o u n t m a n a g e ()

C u s to m e r ID A d d re s s DOB P a y m e n t () In fo rm a t io n () F e e d b a c k / ra t in g () B o o k p la n () F a c ilit ie s () F a ir() L o c a t io n ( )

M anager ID DOB A d d re s s A c c e s s G ra n t( ) V e rifi c a t io n ( ) P a y m e n t C h e c k () M a n a g e D a t a b a s e ()

Class Diagram for Travelling Agency System

OBJECT ORIENTED SOFTWARE ENGINEERING

S-ar putea să vă placă și