LIBRARY MANAGEMENT

SYSTEM
SUBMITTED BY-

UPENDRA YADAV(0700318082)
OM PRAKASH YADAV(0700318046)
NITIN GUPTA(0700318045)

Under the guidance of-

Mr. Pushpendra Pratap Singh

in partial fulfillment of the requirements for the award in Bachelor’s

in Computer Application (BCA)

INTEGRAL UNIVEVERSITY
KURSI ROAD
LUCKNOW - 226026 (U.P.)
www.integraluniversity.ac.in
 ACKNOWLEDGEMENT

While presenting this project I express my sincere gratitude

to GOD for his grace and blessings that helped me in this
work.

As with any project, this one wouldn’t have been possible

without contribution of many people.
Project management is a people-intensive activity. Without
motivation, a person is literally unable to make his best
effort. It is needed a matter of great pleasure to record sense
of gratitude and indebtedness towards my project guide Mr.
Pushpendra Pratap Singh for his guidance, constant
supervision and the motivation during my project work.
My parents made me endure sure times with unfailing humor
and warm wishes.

I devote my special thanks to all my friends and family

members who provided me support and inspiration from time
to time to work on this project.

CERTIFICATE OF
ORIGINALITY

This is to certify that the project report entitled “LIBRARY

MANAGEMENT SYSTEM” submitted to UPTEC Computer
Consultancy in partial fulfillment of the requirement for the
award of the degree of Bachelor of Computer Application
(BCA) is original work carried out by
The Upendra Yadav,Om Prakash Yadav & Nitin Gupta with
Roll No. 0700318082,0700318046 And 0700318045 under
my guidance.
This report or a similar report on the topic has not been
submitted for any other examination and does not form part
of any other course
undergone by the candidate.

Signature of Student: Signature of Guide:

Date: Date:
Upendra yadav
Om prakash yadav
Nitin gupta Mr.
PUSHPENDRA PRATAP
SINGH
B-47 Gaytri Nagar Indira
Nagar Lucknow

Signature of Centre Manager

• INTRODUCTION
• OVERVIEW
• WHAT IS A PROBLEM
• PROJECT STATEMENT
• HARDWARE & SOFTWARE REQURIMENT
• DATA FLOW DIGRAM
• DATA BASE DESIGN
• REPORT
• CODING
 • FEATURE SCOPE
• BIBLOGRAPHY

INTRODUCTION

designed in order to keep tracks and record of

books and maintain library level . It maintain
complete Library management system is a well
record of books , its maintain ,it issued a book
and it maintain issued a book date , student
detail ,it maintain student fine etc. The system
will also provide help in identification of
books , its issued date and its record of books
level.This syatem provide a work easily to
under stand by the user.
 OVERVIEW
The project has been developed to fulfill the
requirement of the books. This system provide
access to student by whitch can apply for the issued
of books and for returing of the books and also this
system help to generate the report of the month
according to the data or the available books.This
monthly report will update auitomatacally .

As we know that our records information is

traditionally appear based ;They are maintained on
paper and because of that paper based record
authority face lots of problem and if record will
misplaced then humble of problem has been
occurred. So this library management system will
make the work of authorities bit easy.
The library management system includes the primary
data such as student -ID and student name to which
the book provided . The system requirts only a few
information about the user , which also can we easily
submit by the student and rest of the work is self
generated by the system.

PROJECT STATEMENT
Library management system is desined to
issued a books of student , add a new books ,
add a new student . It is easy to delete a
student name and batch . In this system can
also change user name and password
requirement of our needs .This system easy to
handle solve the problem issued for the
books. some statement of Library management
system are given below :-
We can enter the data of a student easily.
We can search easily student_id , batch
detail ,whose books are issued of a student
and whose books are return of the student.
In this system known as available of
books, writer of a book ,and book_id etc.
We can easily change a password and user
name.

This system flaxciable and portable of

a user. So system can easily handle by the
user.
 HARDWARE & SOFTWARE
REQURIMENT

HARDWARE:

Processer : 1.70 GHz and above

Main Memory : 512 MB
Hard disk : 20 GB
Disk space : 100 MB

Floppy disk drive : 1.44 MB

Key board : Any
Mouse : Any
Monitor : Any
CD ROM DRIVE :52*Samsung CD ROM

SOFTWARE:-

Operating system : Windows

Software : Microsoft visual basic 6.0
Language : visual basic 6.0
Data base :MS Accses
 Web server :IIS

FEATURE SCOPE
PORTABLITY:-

System that existed prveviously manual .As a

result, the system was less portable . one has to
carry the load of many registers to take the data
from one place to another . A big problem was that
the system was less flexible and if be wanted to
calculate yearly or quarterly books and fine report
then it was a big headache .

Sequrity:-

Sequrity concern were also one of the motives

of the University for the need of software . In the
register the data is not sequire as any body can
pamper with the data written in the register . while in
this software , just of password make it absolutely
from the reach of unauthorized person.

Data Redundancy:-

In case of manual system , the registers

are maintained in which , a lot of data is written .
Each time a new queqry rises , It needs to be written
while the old queries may be written repeatebly
because of this which may cause confution . While
tallying the solution for the same query of different
books.

Processing speed:-

In manual system maintain a register as performing

the necessary calculation has prove to be trouble
some job . which take a lot of time and may affect
the performance of the library . But with this software
we can have on all the task perform in a fraction of
second by a single click . Thus making the
troublesome job mutch easier .

Complexcity in work:-

In system when a record is to be updated or to be

daleted a lot of cutting and over writing needs to be
done on the register that are concerned that are
deleted are updated record which make the work
very complex.
LIFE CYCLE OF THE
PROJECT

The software Development Life Cycle (SDLC) was developed

because many computer systems were delivered which did
not satisfy user requirements, and because those projects
that did satisfy user requirements were being developed
over-budget or over time. The SDLC is a methodology that
has been constructed to ensure that systems are designed
and implemented in a methodical, logical and step-by-step
approach. There are nine steps, known as phases, are used
in the project entitled “Library management system”.

The Preliminary Investigation Phase

The Analysis Phase

• The Design Phase

• The Development Phase
• The Implementation Phase
• The Test phase
• The Installation and checkout phase
• The Operation and Maintenance Phase
• The Retirement phase

Each phase of the SDLC creates a tangible product or

deliverable. An important component of the SDLC is that at
each phase, a conscious decision is made to continue
development of the project, or to drop it. In the past, projects
developed without the guidance of the SDLC were continued
well after 'common sense' dictated that it made no sense to
proceed further. The deliverables act as milestones against
which we can judge the progress and continuing viability of
the project.

You might be inclined to skip portions of what the SDLC calls

for, but remember that the value of the process is that it
forces you to follow a standardized methodology for
developing programs and systems. Skipping parts of the
SDLC can be a big mistake, whereas adhering to it ensures
that you give the project the greatest chance for success.

Phase1:The Preliminary Investigation

The Preliminary Investigation Phase may begin with a
phone call from a customer, a memorandum from a Vice
President to the director of Systems Development, a
letter from a customer to discuss a perceived problem or
deficiency, or a request for something new in an existing
system.

The purpose of the Preliminary Investigation is not to

develop a system, but to verify that a problem or
deficiency really exists, or to pass judgment on the new
requirement. This phase is typically very short, usually
not more than a day or two for a big project, and in
some instances it can be as little as two hours!

The end result, or deliverable, from the Preliminary

Investigation phase is either a willingness to proceed
further, or the decision to 'call it quits'. There are three
factors, typically called constraints, which result in a 'go'
or 'no-go' decision:

Technical: - The project can't be completed with the technology

currently in existence. This constraint is typified by Leonardo
da Vinci's inability to build a helicopter even though he is
credited with designing one in the 16th century.
Technological constraints made the construction of the
helicopter impossible.

Time: - The project can be completed, but not in time to satisfy

the user's requirements. This is a frequent reason for the
abandonment of the project after the Preliminary
Investigation phase.

Budgetary: - The project can be completed, and completed on

time to satisfy the user's requirements, but the cost is
prohibitive.

It could be an individual constraint, or any combination of the

three that prevents a project from being developed any
further.

When an agreement has been made to continue with

the project, the second phase of the SDLC is
implemented – The Analysis Phase.

Phase 2: Analysis
In the Analysis Phase, (sometimes called the Data Gathering
Phase) we study the problem, deficiency or new requirement
in detail. Depending upon the size of the project being
undertaken, this phase could be as short as the Preliminary
Investigation, or it could take months.

While some developers would make the case that we have

gathered enough information in Phase 1 of the SDLC to begin
programming, the SDLC dictates that Phase 2 should be
completed before any actual writing of the program begins. It
is surprising to find out how much additional information can
be gleaned from spending just a little more time with the
user.
Phase 3: Design
The exceptional (or foolish) programmer might begin
coding without a good design. Programmers who do so
may find themselves going back to modify pieces of
code they've already written as they move through the
project. With a good design, the likelihood of this
happening will be reduced dramatically. The end result
is a program that will behave in the way it was intended,
and will generally have with a shorter overall program
development time.

Design in the SDLC encompasses many different

elements. Here is a list of the different components that
are 'designed' in this phase:

• Input
• Output
• Processing
• Files

By the end of the design phase, we would hope to have

a formal Requirements Statement for the program, and
a rough sketch of what the user interface will look like.

Most programs are designed by first determining the

output of the program. The reasoning here is that if you
know what the output of the program should be, you can
determine the input needed to produce that output
pretty easily. Once you know both the output from, and
the input to the program, you can then determine what
processing needs to be performed to convert the input
to output. You will also be in a position to consider what
information needs to be saved, and in what sort of file.

While doing the Output and Input designs, more

information will be available to add to the Requirements
 Statement. It is also possible that a first screen design
will take shape and at the end of these designs, and a
sketch made of what the screen will look like.

At this stage of the SDLC it isn't necessary to discuss the

'how' of what the program will do, just to get the
requirements down on paper.

Phase 4: Development
The Development Phase is in many ways the most exciting
time of the SDLC. During this phase, computer hardware is
purchased and the software is developed. That means that
we actually start coding the program.

In the Development phase, examination and re-examination

of the Requirements Statement is needed to ensure that it is
being followed to the letter. Any deviations would usually
have to be approved either by the project leader or by the
customer.

The Development phase can be split into two sections, that of

Prototyping and Production Ready Application Creation.
Prototyping is the stage of the Development phase that
produces a pseudo-complete application, which for all intents
and purposes appears to be fully functional.

Developers use this stage to demo the application to the

customer as another check that the final software solution
answers the problem posed. When they are given the OK
from the customer, the final version code is written into this
shell to complete the phase.

Phase 5: Implementation
In the Implementation Phase, the project reaches
fruition. After the Development phase of the SDLC is
complete, the system is implemented. Any hardware
that has been purchased will be delivered and installed.
 Software, which was designed in phase 3, and
programmed in phase 4 of the SDLC, will be installed on
any PCs that require it. Any people that will be using the
program will also be trained during this phase of the
SDLC.

During the Implementation phase, both hardware and

software is tested. Although the programmer will find
and fix many problems, almost invariably, the user will
uncover problems that the developer has been unable to
simulate. This leads on to the sixth and final stage

Phase6: Test.
During testing the major activities are centered around
the examination and modification of the code. Initially,
small modules are tested in isolation from the rest of the
software product. There are problems associated with
testing a module in isolation. How do we run a module
 without anything to call it, to be called by it or possibly,
to output intermediate values obtained during
execution? Such problems are solved in this phase and
modules are tested after writing some overhead code

Phase 7: Installation and checkout

phase
In this phase the real software is installed on the system
and then the final checking of the software project is
done. Here the software is checked for any errors and if
any error is found it is removed on the spot and
 secondly in this phase the developer checks out whether
the software is producing appropriate result or not in
front of the client. Here the client too gives the input
and checks whether the software is giving appropriate
and quick result or not.

Phase 8: Operation and Maintenance

Phase 6 of the SDLC is the operation and Maintenance Phase.
In this phase someone (usually the client, but sometimes a
third party such as an auditor) studies the implemented
system to ensure that it actually fulfills the Requirements
Statement. Most important, the system should have solved
the problem or deficiency, or satisfied the desire that was
identified in phase 1 of the SDLC - the Preliminary
Investigation.

More than a few programs and systems have been fully

developed that, for one reason or another, simply never met
the original requirements. The Maintenance portion of this
phase deals with any changes that need to be made to the
system.

Changes are sometimes the result of the system not

completely fulfilling its original requirements, but they could
also be the result of customer satisfaction. Sometimes the
customer is so happy with what they have got that they want
more. Changes can also be forced upon the system because
of governmental regulations, such as changing tax laws,
while at other times changes come about due to alterations
in the business rules of the customer.

Phase 9: Retirement phase

This phase the software project becomes obsolete and
remains no longer in use. In this phase the legacy systems
are turned down and new systems replace them. The
software becomes obsolete when

They are no longer needed for the current business model.

The system is being replaced.

Thus the objectives of the retirement phase are:

Complete the removal of the system.

Ensure minimal interruption to users.

All these phases are important for the project entitled

“MATRIMONIAL WITH BRIDAL SHOP” .All these phase reused
in the developing phase.

PROBLEM STATEMENT
Today everyone wants to get globally connected so as to get
into contact with everyone at distance.

As being rightly said marriages are made in heaven n heaven

doesn’t look for distances but yes as human we have to.

It’s not easy for people to be in regular contact to others

through post n telephone.
Even if people have profiles of some very good boys and girls
but they would never be having such vast and detailed
information as provided to them through net, which globally
connects us.

Our “bridal stop” is a place where you can search for you and
yours relatives would be that too just on single click to GO
button. It allows you to search for your would be based on
any mentioned criteria or based on your profiles.
It not only provides you the matrimonial facility but also
provide you with a complete shopping center for a bridal
shopping.

So get engaged and get married.

 SYSTEM ANALYSIS

INDENTIFICATION OF NEED
Since the need is the mother of all inventions. This project is
worthless if it is not supported by some strong needs. In
today’s era we have to consider all the aspects of internet in
every field which makes things easy and valuable. Some of
the drawbacks of working on stand alone system are as
follow

Accessibility:
By using matrimonial in internet ,now we can easily know the
information of the match making , our horoscope , shopping
and our others facilities . It is very easy to access .

Security:
Security concerns were also one of the motives of the
organization to replace the manual match making with
computerized match making .
This security is very secured and quick responsed .

Convenience:
Unlike other sites this site is also for 24 hrs . we can use this
site day and night . This site is always work as a friend of the
user.

Ubiquity:
If you are out of state or out of country .You can use this site
easily . It can easily access anywhere .

Efficiency:
You can access and manage all of your profiles ,updation ,
deletion and all the requirements you can easily do on this
site.

Effectiveness:
Mostly matrimonial site are only give match making facility
but we provide match making with horoscope and shopping
of marriage.

Complexity in Work:
In a manual system, whenever a record is too updated or to
be deleted, a lot of cutting and overwriting needs to be done
on all the registers that are connected with the deleted or
updated record, which makes the work very complex.
However in the software, once a record is updated or deleted,
all the concerned changes are made in the database
automatically.

The above are the limitations of the existing manual system

that forced the organization to request to go for
computerized system that would help the organization get rid
of all the above problems. Beside this there are lots of
advantages of proposed system. We can summarize them as
follows:

• The data storage is simpler, efficient and large amount

of data can be stored easily.
• It becomes a lot easier to respond different queries.
• The exact information about each customer is available
with in few click of mouse.
• The new system is more cost and time efficient.
OBJECTIVES
 Provide easy navigation and selection of profiles
depending upon user choice.Easily update and delete
their profile.

 Providing the facility to match their profiles depending

upon their personal choice.All the criteria professional
with manglik match entered profiles.

 Providing information and registration capability to

consumer’s 24x7.Easily access their profiles from out
of the state or out of the country.

 Providing detailed information about the matched

profiles.It provides information about all the search
criteria(education,best,manglik,education)

 Providing with regular updates .All the updates of

matching profiles , shopping items regularly .

 Providing a centre for various wedding related items.

Items are diamond rings , diamond necklaces , gold
ring , gold necklace , wedding sarees , lehengas , suits
, sherwanis , wedding combo etc .

 Giving easy access to the items available . Name of the

item and item code with item price has already shown
in this site .
 Providing a range from the cheapest to the most
expensive items in bridal shop section . Every range of
items are shown in this site .

FEASIBILITY STUDY
Feasibility is the determination of whether a project is worth
doing or not.

A feasibility study is test of system proposal according to its

workability, impact on the organization, ability to meet user
needs, and effective use of resources. It focuses on there
major questions:-

1. What are user’s demonstrable needs, and how does a

new proposed system meet them?

2. What resources are available for given proposed

system? Is they are used to solve problem?

3. What are the likely impacts of the proposed system on

the organization? How does it fit within the
organization’s MIS plan?

Technical Feasibility:
This is concerned with specifying equipment and software
that will successfully satisfy the user requirement. The
consideration that is normally associated with technical
feasibility include-
• The facility to produce outputs in a given time.
• Response time under certain conditions.
• Ability to process a certain volume of transactions at
a particular speed.
By studying out technical feasibility we find that our project
technically feasible as the technology required for the
system, are easily available and organization have already all
the resources needed for the system.

Operational Feasibility:

For checking out operational feasibility of the system first of

all I find out answer to the following questions these are
given below.
• Is there sufficient support for the project from the
management?
I attended several meetings with the management and
authorities of the institute and talked with them to reference
to the project and tried to find out their view and concluded
that they are ready to co-operate with me.
• Are new business methods acceptable to the users?
When I served the matrimonial site to take the guidance to
improve our project and make more effective and easy to
access.

• Will the proposed system cause harm?

After completing each module I test it deeply giving a large
combination of inputs and find that the results are correct. I
also don’t think that it
will reduce the performance of the staff members because in
previous few years computer becomes too much popular that
every one wants to learn it. There are a number of users in
the banks who can easily operate it.

Economical Feasibility:

The proposed system is economically feasible for the client

because it takes lesser work hours, and is much more
efficient wile working with high accuracy. The proposed
system saves manpower and it doesn’t have expensive
equipments. Thus we can conclude that this system is
economically feasible for the client.

PROJECT PLANNING
Planning may be the most important management activity.
Without a proper plan, no real monitoring or controlling of the
project is possible. Planning may also perhaps the weakest
activity in many software projects, and many failures caused
by mismanagement can be attributed to lack of proper
planning.

The basic goal of planning is to look into the future, identify

the activity that needs to be done to complete the project
successfully, and plan the scheduling and resource allocation
for these activities. Ideally, all future activities should be
planned. A good plan is flexible enough to handle the
unforeseen events that inevitably occur in a large project.

The major issues that the project plan addresses are:-

• Schedules and milestones

• Software quality assurance plans
• Configuration management plans
• Project monitoring plans
• Cost estimation
• Risk management

PERT Chart

A PERT (Program Evaluation and Review Technique) chart is

a network of boxes (or circles) and arrows. There are different
variations of PERT Charts, some use the boxes to represent
the activities and some use arrows to do so. We will use the
first approach here. Each box thus represents an activity. The
arrows are used to show the dependencies of activities on
one another. The activity at the head of an arrow can not
start until activity at the tail of the arrow is finished.

Testing

Impleme
Coding Maintenance
Analysis Design ntation
Week 12

Write Finish
Manual
Week 1 Week 4 Week 8 Week 16
Week 18

Week 15 Week 19

PERT CHART OF MATRIMONIAL WITH BRIDAL SHOPPING

PROJECT SCHEDULING

Scheduling is an inexact process in that it tries to predict the

future. While it is not possible to know with certainty how
long a project will take, there are techniques that can
increase your likelihood of being close. If you are close in
your planning and estimating, you can manage the project to
achieve the schedule by accelerating some efforts or
modifying approaches to meet required deadlines.

One key ingredient in the scheduling process is experience in

the project area; another is experience with scheduling in
general. In every industry area there will be a body of
knowledge that associates the accomplishment of known
work efforts with time duration. In some industries, there are
books recording industry standards for use by cost and
schedule estimators. Interviewing those who have had
experience with similar projects is the best way to determine
how long things will really take.

When preparing a schedule estimate, consider that transition

between activities often takes time. Organizations or
resources outside your direct control may not share your
sense of schedule urgency, and their work may take longer to
complete. Beware of all external dependency

Relationships. Uncertain resources of talent, equipment, or

data will likely result in extending the project schedule.

Experience teaches that things usually take longer than we

think they will, and that giving away schedule margin in the
planning phase is a sure way to ensure a highly stressed
project effort. People tend to be optimistic in estimating
schedules and, on average, estimate only 80% of the time
actually required.

Failure to meet schedule goals is most often due to

unrealistic deadlines, passive project execution, unforeseen
problems, or things overlooked in the plan.
 Software Requirement
Specification
SRS is a document that completely describes what the
proposed software should do without describing how the
software will do it. The basic limitation for this is that the user
need keeps changing as environment in which the system
was to changes function with time. This leads to a request for
requirement changes even after the requirement phase is
done and the SRS is produced.
The basic purpose of the SRS is to bridge this communication
gap. The SRS is the medium through which the client and the
user needs are accurately specified; indeed SRS forms the
basis of the software development. A good SRS should satisfy
all the parties -- something very hard to achieve – and
involves trade-offs and persuasions. The important purpose
of developing SRS is helping the client understand their own
needs.

Advantages of SRS:
• An SRS establishes the basis for agreement between the
client and the supplier on what the software product will
do.
• An SRS provides a reference for validation of the final
product.
• A high quality SRS is a prerequisite to a high quality
software.
• A high quality SRS reduces the development cost.

Characteristics of an SRS:
A good SRS is:
 Correct
 Complete
 Unambiguous
 Verifiable
 Consistent
 Ranked for importance and/or stability
 Modifiable
 Traceable
 Requirement specification
document
The requirement for the proposed system is that, it would be
less vulnerable to the mistakes being made due to entry at
two or three searching levels. Moreover, the control of the
administrator would be centralized. This will provide the
support for matching process.

Introduction:
Purpose of the software-
This project is in matrimonial .The
development of this project is basically give very easy way to
all the user to match their profiles and easy way to shopping
of marriage .It contains some functions:-

• login
• Registration
• Profile View
• Horoscope
• Searching basis on criteria
• Shopping
- Men Apparel
- Women Apparel
- Jewellry
 You can access the information anywhere that you have
access to the Internet. It makes your marital life much easier
to manage.

The main objective to develop the project is to make the

information part simple and to provide user friendly access of
this program to all the users of this site.

Scope:

 Selection of privileged customer to give them their

needs.

 Customer satisfaction surveys for understanding the

needs of customer.

 Better GUI features for faster and better control over

web site with higher satisfaction for the customer.

 Higher level of security.

 Provide a greater area for shopping.

 Providing greater discounts based on different criteria.

 Providing the chat facility.

Many matrimonial sites are taking this plan .Matrimonial site

are going to play the important role in married life.

To search partner according to your Criteria.Many facilities

like shopping,
Horoscope etc.
In addition , some other matrimonial sites continues their
work by adding all the features of the same site as we
develop.Its a service of 24 x 7 day to night and very
successful in all type of marriage.

General description:

Product function and overview:

Data Entry Section

User sectionà This section is developed using ASP.NET as

front-end and SQL in back end .This will provide customer a
unique profile ID and password.It can be accessed by
providing administrator password. In this section the
administrator can authorize persons to data entry. The
administrator can add or edit the master table information.

Data Updating Section

User sectionà This section is developed using ASP.NET as

front-end and SQL back-end. End customers have no privilege
to update any type of data except their account login
password.

Administrator sectionà This section can be accessed by

providing administrator password. In this section the
administrator can update user requests by data updating.
The administrator can edit the shopping items and all the
details of shopping section.
Data Deletion Section

User sectionà Users have privilege to delete their account

from this site.When any customer want to delete their
profile . It can easily done .

Administrator sectionà This section can be accessed by

providing administrator password. In this section the
administrator can delete records of the shopping details with
item code and supplier code.

Data Processing Section:

This section can be accessed by providing administrator

password. In this section the only administrator can process
the insertion,updation,deletion,searching etc.

User Characteristics

The user at the entry section can be either the customer or

administrator. The employee can feed the entries, while
administrator can navigate through the entire system.
General Constraints:

The back-end has to be SQL so the system should run

properly.

Specific Requirements

(a) Input and Output

User’s detail entry and provide them a unique user id and
password. By providing the given id and password user can
access different services which are being provided by this
site like shopping knowing horoscope by zodiac sign.

(b) Functional Requirement

There should be no manual entry in the database table by
directly accessing the tables i.e. there should be security at
database server.
Only administrator can perform any operation on delete ,
insert and update profiles.

(c) External Interface Requirement

The software must be a user friendly platform to reduce
the complexity of operation. The Internet Banking System
should be capable enough to support multi-user environment.
The software is based on client-server architecture so that
one or more user can do entries in the software system as
well as view reports at a time.

(d) Performance Constraints

The software is supposed to have lacks of records so it
should be capable to generate reports and to perform
cumbersome calculations in seconds.

(e) Acceptance Criteria

Before accepting the system, the developer must
demonstrate that the system works on Internet Bank
Planning. The developer will have to show through the test
cases that all conditions are satisfied.