ACKNOWLEDGEMENT
I take this occasion to thank God, almighty for blessing us with his grace and
taking our endeavour to a successful culmination. I extend my sincere and
heartfelt thanks to our esteemed guide, Mr. ADITYA TRIVEDI, for providing
us with the right guidance and advice at the crucial junctures and for showing
me the right way. I also take this opportunity to express a deep sense of
gratitude to our class coordinator Mr. ADITYA TRIVEDI for his cordial
support, valuable suggestions and guidance. I extend my sincere thanks to our
respected Head Of Division Mr. ANAND RAJAWAT for allowing us to use the
facilities available. I would like to thank the other faculty members also, at this
occasion. Last but not the least, I would like to thank our friends and family for
the support and encouragement they have given us during the course of my
work.
TABLE OF CONTENTS
1. System Analysis
1.1. Identification of Need
1.2. Preliminary Investigation
2. Feasibility Study
2.1. Technical Feasibility
2.2. Economical Feasibility
2.3. Operational Feasibility
3. Literature Survey
3.1. Work done by other
3.2. Benefits
3.3. Proposed Solution
3.4. Technology used
4. Software Engineering Approach
4.1. Software Engineering paradigm Applied
4.1.1. Description
4.1.2. Advantage & Disadvantages
4.1.3. Reasons for use
4.2 Requirement Analysis
4.2.1 Software Requirement Specification
4.2.1.1 Glossary
4.2.1.2 Supplementary Specifications
4.2.1.3 Use Case Model
4.2.1.4 Comparative analysis documents
4.2.2 Conceptual Level Activity Diagram
4.3 Design
4.3.1. Design Concept
4.3.2. Design Technique
4.3.3. Modeling
4.3.3.1. ER Model
4.3.3.2. DFD Model
4.3.3.2.1. DFD Model Level-0 and 1
4.3.3.2.2. DFD Model Level 2 and 3
4.3.3.3. Data Dictionary
4.3.3.4. Activity Diagram
4.3.3.5. Software Architecture
4.4 Implementation Phase
4.4.1. Language Used Characteristics
4.4.2. Coding
4.5 Testing
4.5.1. Testing Objectives
4.5.2. Testing Methods & Strategies used along with test data and
the error listed for each test case for each function provided by the
system.
Chapter-1
System Analysis
System Analysis is the process of gathering and interpreting facts, diagnosing
problem and using the information to recommend improvement to the system.
In brief, we can say that analysis specifies what the system should do. System
analysis is thus a management technique, which helps in designing a new
system or improving an existing system. System Analysis takes in to
consideration the fallowings:
Types of Output Concerned: The objectives or goals are to be determined
at first. This is achieved by determining the outputs that the system is
supposed to generate. This helps to find out the purpose of the proposed
system. This makes a clear understanding of the aim for which a system
is to be approached for development. The objectives are however
identified in terms of needs. Needs are the actual determinants of the
output of the system.
Types of inputs Concerned: Based on the output needed to be generated
by the project inputs needed for the projects are determined. Inputs also
depend on constraint like accuracy, correctness and timeliness etc. all
these considerations help to determine the necessary inputs to be feed into
the system for processing.
Types of Storage Concerned: Types of storages are also needed to be
determined as they are the most important point taken into consideration.
Different systems have different types of storages. Database systems or
file systems are generally used for storing data concerned with the
system.
Types of Processing Concerned: This deals with the procedures needed to
develop the system and also how these procedures are to be implemented.
It involves the logical steps involved for the development of the system.
1.1 Identification of need
Identification of needs is generally concerned with the user's requirements and
expectations from the system. Systems can be classified under two categories:
Manual and Computerized. It is obvious that in most cases computerized
systems are more capable and beneficial than manual system due to their faster
responses and quick and fast processing capabilities. Thus in most cases manual
systems are concerned with their transformations into computerized ones. In
other cases computerized systems are concerned with more betterment of their
existing system. Whatever may be the reason there must be some expectation of
the users from the new system to be developed. These expectations are from the
identification of needs of project.
The following are the needs for the development of the proposed system.
Faster performance of calculations and safe storage of records for later
needs.
Faster Updates and Modifications of the existing records.
Presentations in ordered and well-structured format.
Secured storage and retrieval of data.
1.2 Preliminary Investigation
Analysis working on the preliminary should accomplish the following
objectives:
Benefits to be provided by the system: Here the system replaces a
manual system of maintenance of member details, book details
and monetary transactions.
Gathering Information: This deals with the gathering of
information of the way the organizers are maintaining the above
said records, their manuals if present or if they likely to public
them for the development of the new system.
Getting Knowledge of the project request: This is concerned with
user's expectation from the system to be developed. This is
however already covered in the "Identification of Need " section.
Rough estimation of the costing for the system: This is concerned
with an outline costing needed to develop the system as a system
must not only be work effective but also must be cost effective to
be developed and to be brought for usage.
Feasibility of development: Based on all the information gathered
the next step is to find out whether the project is suitable for
development, whether the project could be developed or not under
the circumstances planed for its development.
Chapter-2
Feasibility Study
Feasibility is the determination of whether or not a project is worth doing. The
process followed in making this determination is called a Feasibility study. This
type of study determines if a project can or should be taken. Once it has been
determined that a project is feasible, the analyst can go ahead and prepare the
project specification which finalizes project requirements.
2.1 Technical Feasibility
We can strongly say that it is technically feasible, since there will not be much
difficulty in getting required resources in developing and maintaining the
system as well. All the resources required for developing and maintaining the
software is available in the organisation. Here we are using the resources which
are available already.
Hardware Specifications: -
Processor: - Intel(R) Core(TM) i5 9300H CPU
RAM: - 8.00 GB
Hard Disk: - 1Tb
Keyboard: - 89 Keys
Software Specifications: -
Operating System:- 64-bit Operating system(Windows 10)
Language: - JAVA
Database: - SQL-YOG
2.2 Operational Feasibility
Book’s and Librarian’s record can be change anytime as per the need.
Librarian’s time will be reduced as he/she can access books record faster
and can also keep the record of books in a systematic manner.
Library Management System can make user so faster because system is
easy to use.
Reduce redundancy in the information required from the students so thet
they can easily issue the books they want.
2.3 Economical Feasibility
Development of this application is highly economically feasible . The
organization needed not spend much one for the development of the system
already available. The only thing is to be done is making an environment for the
development with an effective supervision. If we are doing so, we can attain the
maximum usability of the corresponding resources. Even after the development,
the organization will not be in a condition to invest more in the organization.
