TABLE OF CONTENTS

EX. DATE NAME OF THE EXPERIMENT PAGE SIGNATURE

NO. NO.
EXP NO: 1A PROBLEM STATEMENT FOR LIBRARY MANAGEMENT SYSTEM

Date:

AIM:

To perform analysis of the given problem statement for listing the functional requirements

PROBLEM STATEMENT:

LIBRARY INFORMATION SYSTEM:

As the size and capacity of the institute is increasing with the time, it has been proposed to develop a
Library Information System (LIS) for the benefit of students and employees of the institute. LIS will
enable the members to borrow a book (or return it) with ease while sitting at his desk/chamber. The system
also enables a member to extend the date of his borrowing if no other booking for that particular book has
been made. For the library staff, this system aids them to easily handle day-to-day book transactions. The
librarian, who has administrative privileges and complete control over the system, can enter a new record
into the system when a new book has been purchased, or remove a record in case any book is taken off the
shelf. Any non-member is free to use this system to browse/search books online. However, issuing or
returning books is restricted to valid users (members) of LIS only. The final deliverable would a web
application (using the recent HTML 5), which should run only within the institute LAN. Although this
reduces security risk of the software to a large extent, care should be taken no confidential information
(eg., passwords) is stored in plain text.

FUNCTIONAL REQUIREMENTS:

Administrator Menu:

 Admin should be able to insert, modify and delete books.

 Can accept or reject a new user according to the library policy.
 Can get the information of any member who has borrowed a book.
 Add and edit book categories and arrange books by categories.
 Can record books returned by users.

User Requirements:

 Allow user to view quick reports like book issues/ returned etc. in particular time.
 Stock verification in different criteria or according to different categories.
Usability:

 The system shall allow the users to access the system from the Internet using HTML or its
derivative technologies. The system uses a web browser as an interface.
 Since all users are familiar with the general usage of browsers, no specific training is required.
 The system is user friendly and self-explanatory.

5
New user Registration:

Any member of the institute who wishes to avail the facilities of the library has to register himself with the
library information system.

Search book:

The system must be able to search the database based on select search type, must be able to filter book
based on keyword entered and must be able to show the filtered book in table view.

Reliability:

The system has to be very reliable due to the importance of data and the damages incorrect or incomplete
data can do

Availability:

The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The system shall
be operational 24 hours a day and 7 days a week.

Issue books and return books:

The system must be able to enter issue information in database, must be able to update number of books,
must be able to search if book is available or not before issuing books and should be able to enter issue and
return date information

Accuracy:

The accuracy of the system is limited by the accuracy of the speed at which the employees of the library
and users of the library use the system.

Event addition:

System should be able to add detailed information about events and display information on notice board
available in the homepage of site.

RESULT: The given problem statement is analysed and various functional requirements are listed.

6
EXP NO: 1B PROBLEM STATEMENT FOR ONLINE VOTING SYSTEM

Date :

AIM:

To perform analysis of the given problem statement for listing the functional requirements

PROBLEM STATEMENT:

ONLINE VOTING SYSTEM:

Internet has led to discussion of e-democracy and online voting. Many peoples think that the internet could
replace representative democracy, enabling everyone to vote on everything and anything by online voting
.Online voting could reduce cost and make voting more convenient. This type of voting can be done for e-
democracy, or it may be used for finalizing a solution, if many alternatives are present. Online voting
make’s use of authentication, hence it needs security, and the system must be able to address obtaining,
marking, delivering and counting ballots via computer. Advantage of online voting is it could increase
voter turnout because of convenience, and it helps to reduce fraud voting.

FUNCTIONAL REQUIREMENTS:

 Mobility: The voter should not be restricted to cast his ballot at a single poll-site at his home
precinct.
 He shall be able to vote from any poll-site within the nation.

 Convenience: The system shall allow the voters to cast their votes quickly, in one session, and
should not require many special skills or intimidate the voter (to ensure Equality of Access to Voters).

 User-Interface: The system shall provide an easy-to-use user-interface. Also, it shall not
disadvantage any candidate while displaying the choices (e.g., by requiring the user to scroll down to see
the last few choices).

 Transparency: Voters should be able to possess a general knowledge and understanding of the
voting process.

 Flexibility: The system shall be flexible in that it allows a variety of ballot question formats
including open-ended questions (e.g. Write-in candidates and survey questions).

 Support for Disabled Voters: The system shall cater to the needs of physically challenged voters
(e.g. blind voters).

7
 Accuracy: The system shall record and count all the votes and shall do so correctly.
 Eligibility: Only authorized voters, who are registered, should be able to vote.

 Uniqueness: No voter should be able to vote more than once.Audit ability: It should be possible to
verify that all votes have been correctly accounted for in the final election tally, and there should be
reliable and demonstrably authentic election records, in terms of physical, permanent audit trail (which
should not reveal the user’s identity in any manner).

 Voter Confirmation: The voter shall be able to confirm clearly how his vote is being cast, and shall
be given a chance to modify his vote before he commits it.

 Provisional Ballots: The voter shall be able to vote with a provisional (electronic) ballot if he has
some registration problems, which could be counted if verified by the authorities later.

 Documentation and Assurance: The design, implementation, and testing procedures must be well
documented so that the voter-confidence in the election process is ensured.

RESULT: The given problem statement is analyzed and various functional requirements are listed.

8
EXP NO: 1C PROBLEM STATEMENT FOR ONLINE SHOPPING SYSTEM

Date:

AIM:

To perform analysis of the given problem statement for listing the functional requirements

PROBLEM STATEMENT:

ONLINE SHOPPING SYSTEM:

In day to day life, we will need to buy lots of goods or products from a shop. It may be food items,
electronic items, house hold items etc. Now a day, it is really hard to get some time to go out and get them
by ourselves due to busy life style or lots of works. In order to solve this, B2C E-Commerce websites have
been started. Using these websites, we can buy goods or products online just by visiting the website and
ordering the item online by making payments online. This existing system of buying goods has several
disadvantages. It requires lots of time to travel to the particular shop to buy the goods. Since everyone is
leading busy life now a days, time means a lot to everyone. Also there are expenses for travelling from
house to shop. More over the shop from where we would like to buy something may not be open
24*7*365. Hence we have to adjust our time with the shopkeeper’s time or vendor’s time. In order to
overcome these, we have e-commerce solution, i.e. one place where we can get all required
goods/products online. The proposed system helps in building a website to buy, sell products or goods
online using internet connection. Purchasing of goods online, user can choose different products based on
categories, online payments, delivery services and hence covering the disadvantages of the existing system
and making the buying easier and helping the vendors to reach wider market

FUNCTIONAL REQUIREMENTS:

 Registration:
Every parson can view the store but only the members can checkout it become control by administrator.
For being member of website, the customer needs to register for membership.

 User Profile:
The User Profile page is area that given user maintains his /her own information. The user can only change
his/her password required. The user can browse and search the item and add to shopping cart and can
checkout and also the user can edit profile that include change shipping address and details. For other
information to be changed, the super admin and admin privilege is required.

 Item Selection:
Customer must be able to view his/her orders history. Each customer must be able to view placed order
status. Customer should be able to validate and confirm their invoice

 Browsing Through item:

9
The customer will be given a web interface which allows easy browsing through the different rooms.
Basically the items in the shop are well Organized and well-presented so that a user can find his enquired
item easily.

 Login :
Only customer can login to the system with user id and password. The guest can registered or sign up to
the system.

 User Administration:
This includes registration processing, user deactivation, user suspicious and required password change.

 Payment:
The customers choose the payment option when he was placed a order. The payment is handled by the
bank and the payment which could be done either by using credit card and debit card or cash on delivery.

 Online help:

When the customers are needs a help the system will provide the online help system.

 Administrative
Administrative must be able to add/modify customer. System must be able to accept orders from the
customer via email or online form. System must generate pro forma and customer invoice against an order,
system must be able to view order history of a customer. System must be able to validate and manage
customers order against payments.

RESULT: The given problem statement is analyzed and various functional requirements are listed

10
EXP NO:2 SOFTWARE REQUIREMENT SPECIFICATION (SRS)

Date:
AIM: - Development of SRS document, Design document for the selected project.

Library Management System (LMS)

Introduction:-

The purpose of Software Requirements Specification (SRS) document is to describe the external behavior
of the Online Library System. Requirements Specification defines and describes the operations,
interfaces, performance, and quality assurance requirements of the Online Library System. The document
also describes the nonfunctional requirements such as the user interfaces. It also describes the design
constraints that are to be considered when the system is to be designed, and other factors necessary to
provide complete and comprehensive description of the requirements for the software. The Software
Requirements Specification (SRS) captures the complete software requirements for the system, or a
portion of the system. Requirements described in this document are derived from the Vision Document
prepared for the Online Library System.

Purpose:-
The purpose of this application is as follows:
• The software is for automation of library.
• It provides following facilities to

Operator:
• Can enter details related to a particular book.
• Can provide membership to members.

Admin:
• Can read and write information about any member.
• Can update, create, and delete the record of membership as per requirement and
implementation plants.

Scope:
The different areas where we can use this application are :
• Any education institute can make use of it for providing information about author, content of
the available books.
• It can be used in offices and modifications can be easily done according to requirements.

Assumptions
• This application is used to convert the manual application to the online application.
• Customized data will be used in this application. • User does not have right to enter information
about books.

11
Overview:
Project is related to library management which provides reading services to its members. Any
person can become a member of the library by filling a prescribed form. They can get the book
issued, so that they cab take home and return them.

Functionality:

• Online membership.

• Keeps the track of issues and submission of books.

Functional Requirements:

In this system there is lots of functioning.

 The user can Search book and see his/her account information.
 This will able to get records in any format.

Module description

 Type of user:
 Administrator(librarian)
 HOD of all Department
 Student
 Faculty
 Staff
Administrator module:
 Budget(for all department)
 Stock verification
 Create user
 Accept/ Reject user
 Change password
 Book inventory
 User information
 Report generation
 Search Book

Complaint

 All user can send their complaint

User module

 Change password

12
 Book Search
 See account information
Fine information

 All user check their fine

 Fine by date& Month

Book inventory

 Purchasing book information

 Maintain book inventory

Book search

 Normal search by alphabet

 Quick search by type(Book id, Author, ISBN, Publication)

Other charges

 Book Binding, chair, Rack

 Journals
 Newspaper

External Interface Requirements

User Interfaces

 The design or layout of every form will be very clear and very interactive to the user.
 When the user open the software the welcome window will appear.
 In the login window the user can easily entered the desired password and login name.
 Then it will give the successfully login message.
 From each and every window the user can easily go to any desired window that is there is will be a
absolute and relative linking.
 In every window & Mac there is help and support option is present for the ease of user.
 There will be a proper collection of GUI interface, which will provide better look and feel.

Hardware Interfaces

 The existing Local Area Network (LAN) will be used for collecting data from the users

and also for updating the Library Catalogue.

Software Interfaces

 A firewall will be used with the server to prevent unauthorized access to the system.
13
 Performance Requirements

 This software is not breakdown suddenly in any disaster like power failure.
 The development of the software will be based on the object oriented model.
Security Requirements

 There will be proper security regarding to the accessing of data.

 The external security can be provided by given the login authentication.
 The data that are stored in the database must be private.
 There is also required a user authentication.

Software Quality Attributes

 Our software has many quality attribute that are given below-
Adaptability
Availability
Correctness
Feasibility
Maintainability
Portability
Reliability
Testability
Timelines
Cost effective

RESULT : Thus the SRS was studied for the given project..

14
EXP NO:3 UML DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM

Date:

AIM: To draw USE-CASE diagram for Library management system.

INTRODUCTION:

In the Unified Modelling Language, a use case diagram can summarize the details of your system's users
(also known as actors) and their interactions with the system. To build one, you'll use a set of specialized
symbols and connectors. An effective use case diagram can help your team discuss and represent:

 Scenarios in which your system or application interacts with people, organizations, or external
systems
 Goals that it helps those entities (known as actors) achieve
 The scope of your system

Common components include:

 Actors - the users that interact with a system. An actor can be a person, an organization, or an
outside system that interacts with your application or system. They must be external objects that produce
or consume data.
 System - a specific sequence of actions and interactions between actors and the system. A system
may also be referred to as a scenario.
 Goals - the end result of most use cases. A successful diagram should describe the activities and
variants used to reach the goal.

USE CASE DIAGRAM OBJECTS

 Actor
 Use case
 System
 Package

The objects are further explained below.

Actor:

15
 Use Case:

Actor in a use case diagram is any entity that performs a role in one given system. This could be a person,
organization or an external system and usually drawn like skeleton shown below.

A use case represents function or an action within the system. Its drawn as an ovaland named with
the function.
System:

System is used to define the scope of the use case and drawn as a rectangle. This an optional
element but useful when your visualizing large systems. For example you can create all the use
cases and then use the system object to define the scope covered by your project. Or you can
even use it to show the different areas covered in different releases.

Package:

Package is another optional element that is extremely useful in complex diagrams.

Similar to class diagrams, packages are used to group together use cases. They
are drawn like the image shown below.

USE CASE SCENARIOS:

LOGIN:

To interact with the system, LMS will validate its registration with this system.

The actors involved are

 Administrator
 Librarian
 member

View user details:

1. To see the details of the registered user & the books currently borrowed from the library.

2. Member can involve.

3.User must be logged into the system.

16
View books:

1. To display the details, when a member, guest or administrator want to see the details on the available
books.

2. The Actors involved in step are Administrator, guest and member.

Reserve Books:
1. User can reserve a book by inputting the relevant details and the librarian can also reserve a book for a
member

Search books:

1. Member or guest can search for a particular book in the book library by book name or category or author
name.

Issue books:

1. This use case can describe the process of issuing a certain book for a member by librarian.

2. Get the member ID and book ID before issue a book.

3. Check the availability.

Return books:

1. This use case describes the process of return a book.

2. If return book is late member should be paid fine.

View Members:

To display the details, when a member, guest or administrator wants to see the details of the registered
user.

Add /remove members:

Only administrator is allowed to add or remove a member from library data base .to remove a member,
member should request to leave the library.

Procedure(for rational rose):

17
 Click on the File menu and select New.

Now from the Dialogue Box that appears ,select the language which you want to use for
creatingour model.

18
In the left hand side window of Rational Rose right click on ―UseCase view ‖and select
New>UseCase Diagram.

19
Enter the name of new UseCase file in the space provided, and then click on that filename.

20
You can now use the window that appears on right hand side to draw your UseCase diagram
using the buttons provided on the vertical toolbar.

21
USE CASE DIAGRAM:

22
Some Sample UseCase Diagrams are given below for illustration purpose:

DataTransfer

MobilityManagement

Signalling Management

UseCase Diagram For Bluetooth Software

RESULT:

Thus the use-case diagram for online voting system is drawn and verified successfully

23
EXP NO:4 TO DRAW A SAMPLE ACTIVITY DIAGRAM FOR REAL PROJECT.

Date:

AIM:- To draw a sample activity diagram for real project o system.

THEORY

UML 2 activity diagrams are typically used for business process modeling, for modeling the logic
captured by a single use case or usage scenario, or for modeling the detailed logic of a business
rule. Although UML activity diagrams could potentially model the internal logic of a complex
operation it would be far better to simply rewrite the operation so that it is simple enough that you
onanactivitydiagram.InmanywaysUMLactivitydiagramsaretheobject-oriented equivalent of flow
charts and data flow diagrams (DFDs) from structured development.

Let‘s start by describing the basic notation :

 Initial node. The filled in circle is the starting point of the diagram. An initial node
is though it does make it significantly easier to read the diagram.
 Activity final node. The filled circle with a border is the ending point An activity
diagram can have zero or more activity final nodes.
 Activity. The rounded rectangles represent activities that occur. An activity may be
physical, such as Inspect Forms, or electronic ,such as Display Create Student Screen.
 Flow/edge. The arrow son the diagram .Although there is a subtle difference between
flows and edges, never a practical purpose forth Difference although.
 Fork. A black bar with one flow going into it and several leaving it. This denotes the
beginning of parallel activity.
 Join. A black bar with several flows entering it and one leaving it. All flows going
into the join must reach it before processing may continue. his denotes the end of parallel processing.
 Condition. Text such as [Incorrect Form] on a flow, defining a guard which must
valuate to true in order to traverse the node.
 Decision. A diamond with one flow entering and several leaving. The flows leaving
include conditions although some model will not indicate the conditions if it is obvious.
 Merge. A diamond with several flows entering and one leaving. The implication is
that one or more incoming flows must reach this point until processing continues, based on any guards
on the outgoing flow.
 Partition. If figure is organized into three partitions, it is also called swim lanes,
indicating who/whatisperformingtheactivities(eithertheApplicant,Registrar,orSystem).
 Sub-activity indicator. The rake in the bottom corner of an activity, such as in the
Apply to University activity, indicates that the activity is described by a more finely detailed activity
Diagram.
 Flow final. The circle with the X through it. his indicates that the process stops at
this point.

GUIDELINES ASSOCIATED FOR DRAWING AN ACTIVITY DIAGRAM

24
1. GeneralGuidelines
2. Activities

3.Decision points

4.Guards

5.ParallelActivities

6.Swimlane Guidelines

7.Action-objectGuidelines

MODELING A BUSINESS PROCESS WITH A UML ACTIVITY DIAGRAM.

Place The Start Point In The Top-Left Corner .A start point is modelled with a filled in circle, using the
same notation that UML State Chart diagrams use. Every UML Activity Diagram should have a starting
point, and placing it in the top-left corner reflects the way that people in Western cultures begin reading.
Figure1, which models the business process of enrolling in a university, takes this approach.

25
A UML ACTIVITY DIAGRAM FOR THE ENTERPRISE ARCHITECTURAL MODELING

SUBMITTING EXPENSES.

26
SAMPLE ACTIVITY DIAGRAMS:

SAMPLE1:

Let us consider the example of attending a course lecture, at 8am.

An example Activity diagram

As you can see in Figure , the first activity is to get dressed to leave for the lecture. A decision then
has to be made, depending on the time available for the lecture to start, and the timings of the public
trains (metra). If there is sufficient time to catch the train, then take the train; else, flag down a cab to
the University. The final activity is to actually attend the lecture, after which the Activity diagram
terminates.

27
SAMPLE2:

Identifying the activities and transitions for managing course information

The course administrator is responsible for managing course information in the Course ware
Management System. As part of managing the course information, the course administrator
carries out the following activities:

Check if course exists

If course is new, proceed to the" Create Course" step
If course exists, check what operation is desired—whether to modify the course or remove the
course
If the modify course operation is selected by the course administrator, the "Modify Course"
activity is performed
If there move course operation is selected by the course administrator, the "Remove
Course" activity is performed

In the first step in this Activity diagram, the system determines whether the course that is to be
managed is a new course or an existing course. For managing a new course, a separate activity,"
Create Course," is performed. On the other hand, if a course exists, the course administrator can
perform two different activities—modify an existing course or remove an existing course. Hence, the
system checks the type of operation desired based on which two separate activities can be
performed—"Modify Course" or "Remove Course".
Activity diagram

RESULT: The activity diagram was made successfully by following the steps described above.

28
EXP NO:5 DATA DESIGNS USING DFD DECISION TABLE & ER DIAGRAM

Date:

AIM : To draw the ER diagram, DFD and DATA TABLE design for an project

Data flow diagrams can be used to provide a clear representation of any business function. The technique
starts with an overall picture of the business and continues by analyzing each of the functional areas of
interest. This analysis can be carried out in precisely the level of detail required. The technique exploits a
method called top-down expansion to conduct the analysis in a targeted way.

Data flow diagram symbols

Symbol Description

Data Flow – Data flow are pipelines through the packets of information
flow.

Process : A Process or task performed by the system.

Entity : Entity are object of the system. A source or destination data of a

system.

Data Store : A place where data to be stored.

How to Make a Data Flow Diagram

Step 1 – Open Edraw Max Online.( https://www.edrawmax.com/online/)

Step 2 – Open Flowchart. On the navigation pane on the left side of the screen, scroll down to Flowchart.
Step 3 – Create a DFD. ...
Step 4 – Customize your DFD. ...
Step 5 – Save your File.

29
 DFD for Railway Reservation Project
Context level DFD – 0 level

30
1st Level DFD

2-level DFD:

31
ER DIAGRAM FOR RAILWAY RESERVATION

TABLE 1 CUSTOMER MESSAGE

32
TABLE II ORDER TICKECT MESSAGE

TABLE III TRAIN MESSAGE

RESULT:

The ER diagram, DFD and DATA TABLE design for an project was made successfully by following the
steps described above.

33
EXP NO: 6 A CLASS DIAGRAM FOR ANY PROJECT

Date:

AIM: To draw class diagram for any project.

REQUIREMENTS:

Software Interfaces

Any window-based operating system(Windows98/2000/XP/NT)

IBM Rational Rose Software

THEORY:
Class diagrams show the classes of the System, their inter-relationships, and the operations and
attribute of the classes. Class diagrams are typically used, although not all at once, to:

 Explore domain concepts In the form of a domain Model

 Analyze requirements in the form of a conceptual/analysis model
 Depict the detailed design of object-oriented or object-based software

A class model is comprised of one or more class diagrams and the supporting specifications that
describe model elements including classes, relationships between classes, and interfaces. There are
guidelines

 General issues
 Classes
 Interfaces
 Relationships
 Inheritance
 Aggregation and Composition

HOWTODRAWCLASS DIAGRAM

When designing classes the attributes and operations it will have are observed. Then determining
how instances of the classes will interact with each other. These are every first Steps of many in
developing a class diagram. However, using just these basic techniques one can develop a
complete view of the software system. There are various steps in the analysis and design of an
object oriented system.

STEPSFORDRAWINGCLASSDIAGRAM

 After completing the sequence diagrams and collaboration

diagramwhichareapartoftheinteractiondiagrams.InRationalRose,right click on the ―Use Case
View‖ and select new class diagram.

34
Enter the class name (here ―Hostel Class‖).

35
Double click on the class form enter the class name in the general field.

36
37
38
RESULT: The Class diagram was made successfully by following the steps described above.

39
EXP NO:7 A SEQUENCE DIAGRAM FOR ANY PROJECT

Date:

AIM: Steps to draw the Sequence Diagram using Rational Rose.

Software Requirements:
Rational Rose, Windows XP

Theory:

UML sequence diagrams model the flow of logic within the system in a visual manner, enabling the
user both to document and validate the logic, and are commonly used for both analysis and design
purposes. Sequence diagrams are the most popular UML artifact for dynamic modelling, which
focuses on identifying the behaviour within your system. Sequence diagrams, along with class
diagrams and physical data models are the most important design-level models for modern
application development.

Sequence diagrams are typically used to model:

 Usage scenarios. A usage scenario is a description of a potential way the system is

used. The logic of a usage scenario may be part of a use case, perhaps an alternate course.
 The logic of methods. Sequence diagrams can be used to explore the logic of a
complex operation, function, or procedure. One way to think of sequence diagrams, particularly
highly detailed diagrams, is as visual object code.
 The logic of services. A service is effectively a high-level method, often one that
can be invoked by a wide variety of clients. This includes web-services as well as business
transactions implemented by a variety of technologies such as CICS/COBOL or CORBA-compliant
Object request brokers (ORBs).

FIG .shows the logic for how to enroll in a seminar. One should often develop a system-
levelsequencediagramtohelpbothvisualizeandvalidatethelogicof a usage scenario. It also helps to
identify significant methods/services, such as checking to see if the applicant already exists as a
student, which the system must support.

Enrolling in a seminar(method).

40
The dashed lines hanging from the boxes are called object lifelines, representing the life span of the
object during the scenario being modeled. The long, thin boxes on the lifelines are activation boxes,
also called method-invocation boxes, which indicate processing is being performed by the target
object/class to fulfill a message.

Procedure

Click on the File menu and select New.

41
Now from the Dialogue Box that appears, select the language which you want to use for creating

your model.
In the left hand side window of Rational Rose right click on ―UseCase view ‖and select New>Sequence
Diagram

42
Enter the name of new Sequence file in the space provided, and then click on that filename.

43
You can now use the window that appears on right hand side to draw your Sequence Diagram
using the buttons provided on the vertical toolbar.

44
Another example of a sequence diagram

AUTHENTIC SEARCHING MOBILITYM SIGNALLING DATATR

ATIOn ANAGEMENT MANAGEMENT ANSFER

:User/BT

1:Access_Request()

3:Access_Granted()

4:Device_Search()
5: Range_Check()
6:Frequency_Selection()

7: Signalling_Complete()

8:Results()

10:Transmitting()

11:Acknowldegement()

RESULT: The sequence diagram was made successfully by following the steps described above.

45
EXP NO:8 A COLLABORATION DIAGRAM FOR ANY PROJECT

Date:

AIM: Steps to draw the collaboration Diagram using Rational Rose.

Software Requirements:

Rational Rose, WindowsXP

THEORY

Collaboration diagrams are also relatively easy to draw. They show the relationship between objects
and the order of messages passed between them. The objects are listed as icons and arrows indicate
the messages being passed between them. The numbers next to the messages are called sequence
numbers. As the name suggests, they show the sequence of the messages as they are passed between
the objects. There are many acceptable sequence numbering schemes in UML.A simple 1, 2, 3...
format can be used, as the example below shows, or for more detailed and complex diagrams a 1,
1.1,1.2, 1.2.1... scheme can be used.

Theexamplebelowshowsasimplecollaborationdiagramfortheplacinganorderusecase.Thistimethenames
ofthe objects appear after the colon, such as :Order Entry Window following the object Name: class
Name naming convention. This time the class name is shown to demonstrate that all of objects of that
class will behave the same way.

46
(Ticket reservation)

RESULT :The collaboration diagram was made successfully by Following the steps described
above.

47
EXP NO:9 A STATE TRANSITION DIAGRAM FPR ANY PROJECT

Date:

AIM: To prepare STATE CHART DIAGRAM for any project.

REQUIREMENTS:

Software Interfaces

Any window-based operating System (Windows98/2000/XP/NT)

IBM Rational Rose Software

THEORY:
 State Chart Diagrams provide away to model the various
states in which an object can exist.
 There are two special states :the start state and the stop state. The
Start state is represented by a block dot. The Stop state is represented by a bull’s eye.
 A condition enclosed in square brackets is called a guard
condition, and controls when a transition can or cannot occur.
 Process that occur while an object is in certain state are called actions.

STEPSTODRAWSTATECHARTDIAGRAMINRATIONALROSESOFTWARE

 To insert new state diagram secondary click on Logical View.

Select---New --- State chart Diagram.
 A new diagram will be created, type in a name for the new
diagram.
 Now double click on the new diagram to open it on the stage.
 To be in the diagram click on the “STARTSTATE” button.
 Place a start state icon on the diagram by clicking the mouse once.
 Now add states to the diagram, these makeup the content of the diagram.
Click on the state button. Place the instances for each state in to the diagram and type in
names for them.
 Now arrange the states to fill the diagram better. Drag the states to new
positions to make the easiest layout to work with.
 Add an end state to the diagram by clicking the “END STATE” button.
Place an instance into the diagram. Now add relationships to the diagram.

 Click on the “STATE TRANSITION” button and drag arrows between

the appropriate states.

 To edit the specification secondary click on the relation lines and select
“OPENSPECIFICATION”button.Addanamefortheeventinthespecification.Thenclick
on―apply‖ and then on ―OK‖ button.
 Add details to the specifications of the other relationships in the same way.

48
There may be instances on the diagram where a state can join more than one state. In this
case add a relationship in the same way. Then enter the specification for the new state.
A STATE CHART DIAGRAM FOR RESERVATION OF TICKETS & DISPLAY
OFCONFIRMATION FORM.

RESULT :

The state chart diagram was made successfully by following the steps described Above.

49
EXP NO :10 TEST CASES TO VALIDATE REQUIREMENTS OF ASSIGNED PROJECT

FROM SRS DOCUMENT

Date:

AIM: To validate the test cases for the given SRS or documents.

 https://register.qatouch.com/

 create the account,

 Select education

 Slelect stack >google search> finish

50
 Select add project

Select the required test cases. Based on the test case it will display the output. Activity graph

51
RESULT : Thus the test cases are designed for the for the given project..

52
EXP NO: 11 ESTIMATION OF EFFORT AND PROJECT DURATION USING COCOMO MODEL

Date:

AIM

To estimate Effort and Project Duration using Basic Cost Constructive Model.

PROBLEM STATEMENT

Estimation of Software Maintenance Cost is carried out by COCOMO. For different modes of
operation of COCOMO (Organic, Semi-detached and Embedded),

Calculate the following: a) Effort in Staff months b) Project Duration using the data given
below:

KLOC (thousands of lines of code) = 200

Mode a b

Organic 2.4 1.05

Semi-Detached 3.0 1.12

Embedded 3.6 1.20

Constants to be used for Effort in Staff Months:

Constants to be used for Project Duration:

Mode c d

Organic 2.5 0.38

Semi-Detached 2.5 0.35

Embedded 2.5 0.32

PROBLEM ANALYSIS:

a. Effort in Staff-Month

E= a(KLOC)b

Where KLOC – Kilo Lines of code and a,b are constants.

b. Project Duration in Months

T= c (E) d

Where E is the effort in months and c,d are constants

53
PROGRAM:

#include<stdio.h>
#include<conio.h>
#include<math.h>
inti,ss[3];
float kloc,E[3],D[3],P[3];
float a[3] = { 2.4, 3.0, 3.6 };
float b[3] = { 1.05, 1.12, 1.20 };
float c[3] = { 2.5, 2.5, 2.5 };
float d[3] = { 0.38, 0.35, 0.32 };
void calc(int i);
void main()
{
clrscr();
printf("\nEnter the value of kloc:");
scanf("%f",&kloc);
printf("\n\nESTIMATIONS FOR BASIC COCOMO ARE :");
printf("\n\nFor Organic Mode :");
calc(0);
printf("\n\nForSemidetatched Mode :");
calc(1);
printf("\n\nFor Embedded Mode :");
calc(2);
getch();
}
voidcalc(int i)
{
E[i] = a[i]*(pow(kloc,b[i]));
D[i] = c[i]*(pow(E[i],d[i]));
printf("\n\tEffort, E = %f PM",E[i]);
printf("\n\tDevelopmentTime,D= %fM",D[i]);
}

OUTPUT:

RESULT: Thus the cocomo model is executed and output is verified successfully.

54
EXP NO:12 USE CPM/PERT FOR SCHEDULING THE ASSIGNED PROJECT

Date:

AIM

To create a PERT chart, USING EDRAW OR SMARTDRAW .

A PERT chart is a visual project management tool used to map out and track the tasks and
timelines. The name PERT is an acronym for Project (or Program) Evaluation and Review
Technique.

STEPS

Step 1: Identify all of the project’s activities.

First, define all of the major phases, milestones, and tasks needed to complete the project.

Step 2: Identify dependencies

If you determine some tasks or activities have dependencies, you will want to depict those tasks
with directional arrows. This will ensure your team knows the sequence they need to tackle each
task.

Step 3: Draw your chart.

The next step is to take the events and milestones (numbered nodes) you’ve identified and draw
them out. Then write out the tasks and activities that the team must complete between each node,
using directional arrows or divergent arrows accordingly.

Step 4: Establish timelines for all activities.

55
You should now set a timeframe when the team will need to complete those tasks along with all
arrows. For example, in our mockup above, you can see the “Train sales” activity has a timeframe
of 1 day. This can represent the estimated timeframe and/or deadline you set for the activity.
How to Make a PERT Chart
Step 1: Open Edraw or smart draw tools and click + sign
EdrawMax is an online PERT chart maker that helps you visualize your project better and
evaluate time and resources for your team. It allows you to create transparency in project progress
and control, helps assign tasks to the right team member, identifies potential hurdles within the
project, and understands the project’s completion time and budget.

Step 2: Select PERT Template

56
Using EdrawMax:
 List the milestones of your project. Add notes and arrows, as required.
 Connect the designated landmarks and specify the estimated project time.
 Choose an EdrawMax template or a blank canvas for your PERT chart and share it with
your colleagues.

Step 3: Design.

Steps 4: Create a PERT Chart.

Samples for PERT chart

57
58
Step 5: Add Details and Save.

RESULT : Thus the PERT chart is drawn for the given project..

59
EXP NO:13 USE TIMELINE CHARTS OF THE ASSIGNED PROJECT
Date:

AIM : To draw the timeline chart in excel or any tools for the project management.

PROCEDURE:

An Excel timeline chart is called a milestone chart in project management terms. It is used to
track all the stages of a project visually. As a project manager, deliver the project to the end-
user as committed before the start of the project.

STEPS TO DRAW TIMELINE CHART IN EXCEL

Project Timeline Using Stack Bar Graphs
Suppose you have a list of tasks in tabular form in excel, as it shows in the screenshot below:

In this table, we have the Task Name, Start Date of the task, End Date of the task, and duration (in
the number of days) it takes to complete the task. The duration can be inputted manually, or you
can use a formula as [End Date – Start Date + 1]. Here +1 allows excel to count the Start Date as
well while calculating the Duration.

Go to Excel Ribbon > Click Insert > Select Insert Column or Bar Chart option.

60
Select Stacked Bar under 2D-Bar option

As soon as you click on that chart button, you can see an empty excel chart is generated as

follows. Right-click on it and choose select Data.

A Select Data Source popping window will appear. Under Legend Entries (Series), click

on Add tab.

61
A new pop up window Edit Series will appear on the front. Under Series name, select Start

Date (cell B1). Under Series values, select a range of data from the Start Date column (Column

B, B2:B11). Click OK.

Now add Duration as a Series name and Duration values as Series values by clicking Add button

one more time, same as the above step.

62
Now, click Edit under Horizontal (Category) Axis Labels. It will open up a new pop-up

window, Axis Labels. Select Task Name Range of cells from cell A2 to A11 under Axis label

range and click OK. It will add Project 1 to Project 10 as a label (name) to every stack.

Under Format Data Series, select No Fill under Fill section and No Line under Border section

to make the blue bars invisible.

63
you can see a stacked bar chart as shown below with start date as labels on X-Axis, Duration as

Value for stacks, and Task Name as labels for Y-Axis.

Now, there are these blue bars which are nothing but the start date bars. We don’t want those in

our timeline graph. Therefore, we need to remove those.

Select blue bars and right-click on those to select Format Data Series.

64
Under Format Data Series, select No Fill under Fill section and No

Line under Border section to make the blue bars invisible

65
Now, the graph looks like below:

RESULT : Thus the TIMELINE chart is drawn for the given project..

66