INDEX

Sr. No. Topics Remarks

Development of SRS document,

1 Design document for the selected
project.

Development of DFD, data

2 dictionary, E-R diagram,
structured chart for the project.

To study and draw various UML

3
diagrams.

To illustrate the use of class

4
diagrams.

To draw an activity diagram and

5 use case diagram for ATM and
Library Management System.

Draw Object Diagram for ATM

6
System.

Development of State Transition

7
Diagram.

Draw ER Diagram for Hospital

8
Management System.
 Practical No.1

Aim: - Development of SRS document, Design document for the selected

project.

Software Requirements Specification (SRS)

Library Management System (LMS)

1. 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

1.1 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.

2.) 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.

3.) Technology Used:

Front End: Java, Netbeans.

Back End: MS Access, SQL.

4.) 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.

5.) 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.

6.) 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.

 He will be able to get the records in any format.

 There will also be a reminder and digital diary through this he can go to know aboutits
important date like his book submission date.

 Admin can add new record and saw all record of any student as well as library.

ModuleDescription

Type of user:
 Administrator(librarian)
 HODofallDepartment
 Student
 Faculty
 Staff
Administrator module:
 Budget(foralldepartment)
 Stockverification
 Createuser
 Accept/Rejectuser
 Changepassword
 Bookinventory
 Userinformation
 Reportgeneration
 SearchBook
Complaint
 •
  Allusercansendtheircomplaint
User module
 Changepassword
 BookSearch
 Seeaccountinformation
Fine information
 Alluserchecktheirfine
 Finebydate&Month
Book inventory
 Purchasingbookinformation
 Maintainbookinventory
Book search
 Normalsearchbyalphabet
 Quicksearchbytype(Bookid,Author,ISBN,Publication)
Other charges
 BookBinding,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.
  In the screen layout the background color is very light and the graphics and
font style will be in proper manner and well organized.
 If the user will print any error statement then it will give the proper error message
display.
 In ea c h an d eve r y win do w the r e wil l be al e r t , co nf i r m etc me s sa g e
box fo r dis pla y i n g message.
 The user will be able to search any data from the record by using proper guideline shown
in the window & Mac.
 In the opening of the software there will be a menu window where the overall table
contents of the software will be present through which the user can move to any desired
window &Mac.
 Th i s wil l pr ov i d e the be t t e r se c ur i t y da t a bec a u se the me nu win do w
wil l be disp l a yi ng according to the login (admin or normal user).
 User can easily save its data in to the database and keep track of the records of
purchase, vendor and inventory etc.
 This software will be easily understandable and operable by the user.
HardwareInterfaces
 The existing Local Area Network (LAN) will be used for collecting data from the users
and also for updating the Library Catalogue.
SoftwareInterfaces
 A firewall will be used with the server to prevent unauthorized access to the system.
CommunicationsInterfaces
 The Online Library System will be connected to the World Wide Web.

Other Nonfunctional Requirements

PerformanceRequirements
 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.
 The timeline of this software must be in our mind.
  The performance of the functions and every module must be well.
 At every step the output of the one phase is the input of the other phase and it will be
reliable and accurate.
 The risk factor must be taken at initial step for better performance of the software.
 For individual function the performance will be well.
 For login to the software password and user name will be matched to the password and
name
 Saved in the database and thus only authenticated users are allowed to the login.
 There will be various ways of retrieving data and it takes less time.
 There will be ambiguity in the data and the record.
 This software will be well supported to the other embedded software such as digitaldairy,
notepad etc.
 The overall performance of the software will reliable and enable the users to
work efficiently.
SecurityRequirements
 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.
 There is also the facility that the admin can lock his private data that will not be accessed
by anyone.
 The whole software is secure from the outside accessing.
SoftwareQualityAttributes
 Our software has many quality attribute that are given below-

Adaptability
 This software is adaptable by any organization.
Availability-
 The availability of the software is easy and for everyone.
Correctness-
  The results of the function are pure and accurate.
Flexibility-
 The operation may be flexible and reports can be presented in many ways.
Maintainability-
 After the deployment of the project if any error occurs then it can be easily
maintain by the software developer.
Portability-
 The software can be deployed at any machine.
Reliability-
 The performance of the software is better which will increase the reliability of the
software.
Reusability-
 The data and record that are saved in the database can be reused if needed.
Robustness-
 If there is any error in any window or module then it does not effect the
remaining part of the software.
Testability-
 The software will be tested at every. Alpha Testing Beta Testing Acceptance Testing
Usability-
 To perform any operations and to understand the functioning of software is
very easy.
Productivity-
 This software will produce every desired result with accurately.
Timelines-
 The time limit is very important. It will save much time and provide fast
accessing.
Costeffective-
 This software is less in cost and bearable by any
 Organization.
 Practical No-2

Aim: -Development of DFD, data dictionary, E-R diagram, structured

chart for the project.
 Practical No.-3

Aim: To study and draw various UML diagrams.

 UML:-
UML stands for Unified Modeling Language which is used in object oriented software
engineering. Although typically used in software engineering it is a rich language that can be
used to model an application structures, behavior and even business processes. There are 14
UML diagram types to help you model this behavior.
They can be divided into two main categories; structure diagrams and behavioral diagrams. All
14 UML diagram types are listed below with examples and a brief introduction to them
explaining how they are used when modeling applications.

 Types of UML diagram:-

 Use Case Diagram

As the most known diagram type of the behavioral UML diagrams, Use case diagrams give a
graphic overview of the actors involved in a system, different functions needed by those actors
and how these different functions are interacted.
It’s a great starting point for any project discussion, because you can easily identify the main
actors involved and the main processes of the system.
 For ATM

 For Library
 Practical No. - 4

Aim: To illustrate the use of class diagrams.

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among objects.

The class diagram is the main building block of object-oriented modelling. It is used both for
generalconceptual modelling of the systematics of the application, and for detailed modelling
translating the models into programming code. Class diagrams can also be used for data
modeling. The classes in a class diagram represent both the main elements, interactions in the
application, and the classes to be programmed.

Class Diagram for atm:

Class Diagram for Library management System:
 Practical No.-5

Aim: To draw an activity diagram and use case diagram for ATM and Library
Management System.
ACTIVITY DIAGRAM:

Activity diagram is another important diagram in UML to describe dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system. So the control flow is drawn
from one operation to another.

Activity Diagram for ATM:

Activity Diagram for Library Management System:
 Practical No. - 6

AIM: - Draw Object Diagram for ATM System.

Object Diagram:
Object diagrams are derived from class diagrams so object diagrams are dependent upon class
diagrams.

Object diagrams represent an instance of a class diagram. The basic concepts are similar for
class diagrams and object diagrams. Object diagrams also represent the static view of a system
but this static view is a snapshot of the system at a particular moment.

Object diagrams are used to render a set of objects and their relationships as an instance

Purpose:
The purpose of a diagram should be understood clearly to implement it practically. The
purposes of object diagrams are similar to class diagrams.

The difference is that a class diagram represents an abstract model consisting of classes and
their relationships. But an object diagram represents an instance at a particular moment which is
concrete in nature.

ATM System:

1
 Practical No.- 7

Aim: -Development of State Transition Diagram.

Hotel Reservation

Library Management System

1
 1

Practical No. - 8
Aim:-Draw ER Diagram for Hospital Management System.
ER-Diagram
Any object, for example, entities, attributes of an entity, relationship sets, and attributes of
relationship sets, can be represented with the help of an ER diagram.
Entity
Entities are represented by means of rectangles. Rectangles are named with the entity set they
represent.
Attributes
Attributes are the properties of entities. Attributes are represented by means of ellipses. Every
ellipse represents one attribute and is directly connected to its entity (rectangle).
Composite Attribute
If the attributes are composite, they are further divided in a tree like structure. Every node is
then connected to its attribute. That is, composite attributes are represented by ellipses that
are connected with an ellipse.
Multivalued Attributes
Multivalued attributes are depicted by double ellipse.
Derived Attributes
Derived attributes are depicted by dashed ellipse.

www.ahirlabs.com 1
www.ahirlabs.com 1
www.ahirlabs.com 1