Documentation
Documentation
Documentation
INDEX
1
`
(MCA)
2
`
3
`
On
Imperial Library Management System
4
`
Developed By:
Sonal Purohit,
81-A,New Lalbahadurnagar,
Dhebar Road (South),
Rajkot-360002
Enrollment No:012669092
5
`
Region Code:09
Programme Name:MCA
Date:
Student’s Sign:
Guide’s Sign:
Introduction
Computerization is the need of hour is an undisputable fact that without the help of IT,
6
`
phased manner. The phase relate towards the objective of the whole exercise i.e. faster
access of information, for speedier reporting, better planning and decision making
system to support the operation of generation of telephone bill. The system must be
system technology for all types and sizes of libraries. With modules for all public and
This system is designed for a smaller institutions. In future this can enhanced with
7
`
I ’ve designed a system for a library that can maintain its transaction easily with
It shows all the details about of library, branch, department, members, books,
also calculates fine rates in case the books is not returned in time. Whenever book is
returned it’s record will be deleted from the issue/return table. There are some rules for
issue/return of the books that are recorded in rule_details table according to that
particular fine rates is offered to particular members. Different types of members have
I n today’s fast growing world, information has the vital and most essential role to
play. The IT revolution has not only affected business, education, science but also the
way people think. Speedy change in economy and globalization are putting more and
more stress on the cutting edge technology and to process information swiftly, accurately
8
`
and reliably. The manual system is not capable to show accuracy and speed. Thus, it has
(computerize) the existing manual system of an organization for maintaining the records
in digital manner.
Objectives
The main purpose of this software is to gather and interpret facts, analyse the problem,
use the information to recommend improvement of the system and fully automate the
desired requirements with solutions. This software will help the Organization
in arranging relevant information conveniently. With the help of this software, the
9
`
organization not only increases its efficiency of working but also can attain accuracy in
day-to-day working. The purpose of this project is to provide a system which is more
The objective of the project is to design the Imperial Library Management System
(LMS ) as a POS tool for the management of organization activities. The data structure of
the (LMS) will be laid out, including the different types of modules that are needed. The
front-end of the system will be developed using Visual Basic, and the back-end will be
In my project I’m trying to develop some facilities which are listed below:
----------------------------
to 95%
----------------------------
10
`
3) Registry Coding...
4) ActiveX.
10) It also provided facilities for searching a particular books information, issue/return
member details, book details, author details, publisher details ,issue/return details, etc.
also allows some pre defined conventions such that fine rate is fixed for various types
of members so it doesn’t need of adding particulars each time. It’ll take necessary
System should be capable to keep track for all type of accounts and should be capable of
System must have the facility of adding new users who work on the system and each user
11
`
To maintain the data, system must provide the backup and restore facility, which is only
System needs customize generation, which makes the system generalize for all the
for simplification and rapid application development. The “visual” part refers to the
method used to create the graphical user interface (GUI). Rather than writing numerous
lines of code to describe the appearance and location of interface elements (as in Visual
C++), Visual Basic allows the designer to simply place per-built objects to the screen.
This feature of Visual Basic saves a lot of time in designing the screen and allows the
Identification Of Need
Behind every application there is a need which forms the base for that application. The
need for this application was discovered by LMS after it found that the information
related to a particular project was getting difficult to maintain manually. The report
generation was becoming tedious and information was never available quickly. As per
the detailed system study and information provided by M.J.Library , Head office, The
data is being manually collected, compiled, processed & information reports are also
12
`
prepared manually every month. The availability of data is limited and not up-to-date.
This led to delay in interaction between Officers and Clients. Consequently, when the
communication expenses. Apart from these factors the current manual system is not able
to utilize the maximum capabilities of the Setup and employees. Moreover the time
utilized in certain processes is very high. Thus the current system being not so efficient
paved the way for a system that is highly automated, fixes the entire above problem and
more importantly yields desired output. After discovering the need a very extensive study
of the various stages in completion of a project was done and the work flow was studied.
13
`
Requirement Analysis
T
he complete understanding of software requirements is essential to the success of a
software development effort. Requirement analysis is the first technical step in the
software process. It is at this point that a general statement of software or its scope is
refined into a concrete specification that becomes the foundation of all software
engineering activities.
specification. The software scope initially established by the system engineer and refined
in detail during software project planning. Modeler of the required data, information and
control flow, and operational behavior are first created. Alternative solutions are analyzed
engineering task that bridges the gap between system level requirements engineering and
software design.
System
Engineerin Software
g Requireme
nt Analysis Software
Design
14
`
The software requirement analysis may be divided into five areas of effort:
Problem Recognition
Modelling
Specification
Review
The most crucial phase of managing system project is to create a master plan detailing the
steps. The initial investigation has the objective of determining whether the user request
has potential merits and major steps are defining user requirement.
Initially, the analyst studies the system specification and the software project plan.
Problem evaluation and solution synthesis is the next major area of effort for analysis
during evaluation current problems and desired information (input and output) the analyst
Analysis Principles –
Each analysis method has a unique point of view. However all analysis
15
`
4. The models that depict information, function and behaviour must be partitioned in
implementation detail.
software engineer who takes there principles to heart is more likely to develop a software
In addition to these operation principles, Davis suggests a set of guiding principles for
requirements engineering.
Understand the problem before beginning the creation of the analysis model:
Rank requirements.
16
`
Problem Definition –
The existing manual system suffers from all the
disadvantage of a manual system. Given below are the problems faced in the various
application areas:
cumbersome.
reports and reconciliation statements are generally manual in nature and time
consuming.
fields.
17
`
18
`
Preliminary Investigation
T he first step in the system development life cycle is the preliminary investigation
investigation is to evaluate project requests. It is not a design study nor does it include the
information that help committee members to evaluate the merits of the project request
and make an informed judgment about the feasibility of the proposed project.
objectives:
According to the rules of the Library, it gives gives the chance to take
books from the library and return it in the prescribe time period, if the member
doesn’t follow the rule thenfine shold be paid according to the rules of Library.
project right from the day the idea for that project was conceived to the date of its
19
`
completion was studied and a work flow diagram was made. All the sources of necessary
data were analyzed and a session with the people involved in a particular project was
held. Based on the self study and the interactive session with the employees of the
Feasibility Study
B
efore starting the new system it is important to determine the feasibility involved in the
developed system so that the new system could be developed. Feasibility is the
determination of whether a project is worth doing or not. The project followed in making
this determination is called a feasibility study. Once it has been determined that project is
feasible, the analyst can go ahead and prepare the project specification, which finalizes
project requirements.
Generally, feasibility studies are undertaken within tight time constraints and
To find out whether the purposed project is feasible or not I did three types of
20
`
Technical Feasibility
Operational Feasibility
Economic Feasibility
T Technical Feasibility
technical feasibility is concerned with specifying equipment and software that will
The consideration that are normally associated with technical feasibility include
Development risk
Resource availability
Technology
The technical needs of the system may vary considerably, but might include:
21
`
feasible as the technology required for the system, is easily available and Imperial
Library Management sysytem already have all the resources needed for the system. The
current system works manually. We change this system with computerized environment.
Proposed system will increase the processing. The necessary technologies exist to do
what is suggested. The proposed equipments have the technical capacity to hold the data
required to use the new system so the purposed system is technically feasible.
22
`
Operational Feasibility
F
or checking out operational feasibility of the system, first of all I find out answer to the
I attended several meetings with the management and authorities of the Library
Management System and talked with them in reference to the project and tried to find
out their views and concluded that they all are ready to cooperate with me.
When I met with the Clerks and Employees of the M.J.Library and talked with
them I find out that they are satisfied with the current business methods but hopes that if
it is replaced by the computerized system then their work load will be reduced and their
Have the users been involved in the planning and development of the project?
I met the Clerks, and Employees a number of time during the project and tried to
get the exact working scenario of the M.J.Library, How they work, What are the
information that are to be stored and how they store them. What types of reports they
generally require. What are the errors they do in managing the information? I study their
views and ideas and concentrate on those for which I think will be needed for the good
23
`
After completing each module I test it deeply giving a large combination of input
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 so much popular
While developing the system it was kept in mind that it should be user friendly and easy
Economic Feasibility
E
conomic analysis is the most frequently used technique for evaluating he effectiveness of
is to determine the benefits and the savings that are expected from a proposed system and
compare with cost. If benefits out weigh cost a decision is taken to design and implement
the system otherwise further justification or alternative in the proposed system will have
to be made if it has a chance of being approved. This is an ongoing effort that improves
The analysis part also clears the doubt of economic problems that could be
24
`
The Finance company has just to pay the developed software cost and not other
investment is needed at the time of implementation of the new system, as the preliminary
used in this software package. We will also present the Software requirement
specification. Like any other product, a software product completes a cycle from its
The process of software development not only needs writing the program and
maintaining it, but also a detail study of the system to identify current requirements
needs to meet the objective of low cost, and good quality along with minimum
development time.
should be divided into phases so that project’s progress and change in requirement can be
controlled along with the quality of the product. Following are the general phases in the
25
`
Operation and maintenance for the use and to ensure its availability to users.
This application was also developed in phases for effective output. Each phase was given
its due importance with respect to time and cost. The time scheduling is later described in
The system development life cycle of Integrated Loan Management System is shown
below:
Requirement
Analysis and
Specification
Designing
Coding
Testing and
Validation
26
Operation and
Maintenance
`
In general there are three approaches to software development life cycle namely
27
`
might be reapplied to the end products of the approach. This approach is handy in
techniques used to develop software. Software models serve as standards and provide
Build Fix
Produc Proble
t m
28
`
Preliminary
Investigation
Requirement
Definition
Requirement Analysis
and Specification
Design
Implementation
Testing
Maintenance
29
`
System Design: To determine the overall structure of the system. It is up to the analyst
that either he/she can purchase ready-made software or may develop new custom made
software.
Implementation and Maintenance: For the developed system first step is to install it
and implement it. The second step is to evaluate it whether it is sufficient to the
requirement and if not then what changes required. The final step is to keep on the
System Testing: It insures that system works properly and minimizes the re-testing
process.
Spiral Mode
Risk Analysis
Planning
Toward a
Complete system
30
Engineerin
`
Spiral model provides a framework for designing the software production process, guided
by the risk levels in the project at hand. It suggests iterative production of prototypes
Risk Assessment: Key risks identified and risk reduction steps taken.
Prototype Model
In this model we develop a working prototype with the available requirement
details and get feedback of the customer for the actual requirement of the product to
develop the product. Prototype is the timed version of the actual product with limited
31
`
features and functionality and with low level of reliability. Prototype model is used
Design
Implement
Testing
The software is developed in three phases during the first phase the dry prototype
is developed in which after the analysis screens are designed and no validations are
dry prototype suggestions from the clients are noted and the development process is
moved to the second phase i.e. wet prototype in which the actual design is incorporated,
validations are performed and the software is submitted to the user for acceptance and
testing and then after final submission of the software is produced with user manual.
32
`
developed to satisfy the needs of the customer and enabling the developer better
33
`
T
he software requirements specification is produced at the culmination of the analysis task.
The function and performance allocated to software as part of system engineering are
LMS
1. Introduction
a. System reference
b. Overall description
c. Software project Constraints
2. Information Description
2. Control flow
3. Functional Description
a. Functional partitioning
b. Functional description
34
`
1. Processing Narrative
2. Restrictions / Limitations
3. Performance Requirements
4. Design constraints
5. Supporting diagrams
c. Control description
1. Control specification
2. Design constraints
4. Behavioral Description
a. System states
a. Performance bounds
b. Classes of tests
d. Special considerations
Introduction
It states the goals and objectives of the software descriptions actually in the
Project report
35
`
RDBMS
Information Description :-
It provides a detailed description of the problem that the software must solve.
Information contest and relationships, flow and structure are documented. Hardware,
software and human interfaces are described for external system elements and
Functional Description :-
It presents description of each function, which is required to solve the problem. A
processing narrative is provided for each function, design constraints are stated and
justified, performance characteristics are stated, and one or more diagrams are
included to graphically represent the overall structure of the software and interplay
among software functions and other system elements under this topic, the functional
working of the various modules gives the complete picture of the data flow from one
Behavioral Description :-
This section of the specification examines the operation of the software as the
this topic many project shows the event flow diagram, which tells us at what step
36
`
Validation criteria
Probably the most important section of software requirements specifications is the
all other requirements. The tests must be conducted to validate function, performance
and constraints.
In this project I have try the various steps in testing the links and connectivity.
appendices. Last section of the project have comes the bibliography and appendix
which help us to know from where I have taken the references and graphical analysis
concrete specification that becomes the foundation for all software engineering
activities that follows. Analysis must focus on the information functional and
37
`
can be refined to properly conduct prototyping special tools and techniques are
required.
General Description
T
he study has revealed that the computerization of the entire department is a mission
critical activity in order to get the maximum return of investment, not only the quality of
the software but the speed and tempo of mission critical project will have to be
maintained. In such projects it is important that the department take a look on all aspects
of the project and prepare a team of champions who will work towards the goal of total
Specific Requirements
F
unction requirement specify what output should be produced from the given inputs. They
describe the relationship between the input and output of the system. For each functional
requirement, a detailed description of all the data inputs and their source, the unit of
measure, and the range of valid inputs must be specified. All the operations to be
38
`
This include specifying the valid checks on the input and output data parameters
affected by the operation and equations or other logical operations that must be used to
transform the inputs into corresponding outputs. An important part of the specification is
the system behavior in abnormal situations like invalid inputs or error during
computation. The functional requirements must clearly state what the system should do if
such situation occurs. It should specify the behavior of the system for invalid inputs and
invalid outputs.
User interface
Interface with Devices: The software has just one peripheral device to deal with
and that is printer.
Interface with the Operating System: The application will be an executable file
and hence there is no need for an interface with the operating system.
39
`
Interface with the Database used: The application being developed in Oracle8i
so the interface will be the ODBC driver.
Interface with the User : The application assumes its users to be novice and has
an extremely simple and user-friendly interface.
Error Messages
Error messages are displayed in validation checks section.
Performance Constraints
This part of the software requirement specification specifies the performance constraints
the system must be specified. There are two types of performance requirement.
Static Requirements
Static requirements are those that do not impose constraint on the execution
characteristics of the system. These include requirements like the number of terminals to
be supported, the number of simultaneous users to be supported and the numbers of files
that the system has to process and their sizes. It is also called capacity requirements of the
system.
40
`
Dynamic Requirements
Dynamic requirements specify constraints on the execution behavior of the
system. These typically include response time and throughput constraints on the system.
Response time is the expected time for the completion of an operation under specified
a unit time.
Our project has good performance and its static and dynamic requirements are
both fulfilled. The dynamic performance of our project is excellent. Software is capable
to analyze and give output of any user query in a good response time. System processes
Design Constraints
System Requirements:
Software Hardware
Requirement
The following tables list the software requirements necessary to run the
Drive.
41
`
System Design
o Input Design
When designing input, the objective is to ensure that the data will be processed by the
system is collected and entered in to, the system efficiently according to the specified
requirement and with minimum errors in description with the client, the designer will
choose a method of input which is caused effective and acceptable to the end users. The
Firstly, identifying the inputs into the system by listing the data flows on the
required logical data flow diagram, which crosses the system boundary in its
way.
Then determining the contents of these inputs by inspecting the data dictionary.
Next choosing an appropriate input device to change the user’s data into form,
And finally completing the detailed design work involved in specifying forms,
42
`
The data in database is organized according to the data structure ‘imposed’ upon it by
the physical data model. The physical data model is normally produced during the
physical data design stage in the development life cycle and tailored specifically to the
The Database Management systems available today can be grouped in to four types.
These are:-
In this project the database used is RDBMS. Which has following properties:-
43
`
Project
Category
Project Category(RDBMS/OOPS/Networking/Multimedia/Artificial
Intelligence/Expert Systems etc.
redundancy.
44
`
Book Info:
Branch_Code:
Department_Details:
45
`
46
`
Issue/Return Details:
Library_Details:
Memebr_Details:
47
`
Publisher:
Rule_Details:
User_Details:
Analysis (DFD’s, E-R Diagrams, Class Diagrams etc. as per the project
requirements.)
2. Organize the DFD so that the main sequence of actions reads left to right
4. Identify all manual and computer processes (internal to the system) with
48
`
5. Label each process symbol with an active verb and the data involved.
never connect a data store to a data source or destination or another data store
9. Identify all data flows for each process step, except simple record
retrievals.
11. Use data flow arrows to indicate data movement, not non-data physical
transfers.
13. Draw data flows into data stores only if the data store will be changed.
14. Indicate external sources and destination of data, when known, with
squares.
16. Do not indicate persons or places as entity squares when the process is
49
`
Check
Dept_Id
New Member_No
Dept_Id
Members
Dept/Member
Allocate
Member
New department allocating
Receive _No
(If not have dept)
New
Member
Members Information
Department_Details/Members
Members
50
`
Insert
Books
New
Books
Classify
New
Document
s
51
`
Books
Information
New Documents
Books_Details
Publications
Magazines
Magazines Information
Insert
New
Magazines
52
`
Check
Receive Documents
New
Member
Checking
53
`
Information
I/R ticket
Documents
Books_Details
54
`
Documents
Department_Details/Members
Reply
To
Members
Members
55
`
Reply Infromation
Report
about Library
Document
Books_Info s
Report Department_Details
I/R Ticket About I/R
Document
s
Of Dept
Membe
Department_Details Report
Overdue
Members
56
`
/ Members
Lb_Name
Issued_Book_Nam Member_Mname
e Member_Fname
Pub_Website Has Member_Lname
Many
Member_Ad
Pub_E-mail Pub_Phone d
Members
Publishe Issue/
r return
Pub_Ad
d
Member_N
Phone o
Department_Detail
Publisher_Details s
Type_Of_Member Has
Colle
cts Dept_Id Dept_Name
Publish
es E-Mail ISBN
57
Book_Info Contain Author_Detail
ISBN
Edition
No_Of_Page
Publishe No_Of_Days
Member_N
No_Of_Book Book_Price
Type_Of_Boo
Member_N
Year_Pu
Fine_Rate s Collects
Issue/return_Details
Time_Pub Total_Charge
Author_snam
ISBN
Due_DateTotal_Days
Birth_Dat
Death_Date
Date_Of_Issue
Fine_Charg
Date_Of_Ret ur
`
A Complete
Structure
There are about 21 modules which are used in this project. This is an
1. About Me
58
`
2. Backup Database
This form helps for backing up database. It shows details about back up path,
59
`
3. Book Information
This form shows all the details of books just as ISBN, Book Name, Book Price,
Type of Book, No of Pages, Edition, etc. This form shows all the details of
books just as ISBN, Book Name, Book Price, Type of Book, No of Pages, Edition,
etc. Data grid is used to list the all Books name. It provides direct navigation to
Next, Previous and last. Other operational keys like Add for adding records, Delete
for deleting buttons, Save for saving data and Cancel for cancellation of data
60
`
Members details. It shows Sample form for filling up the details of members.
Previous and last. Other operational keys like Add for adding records, Delete for
61
`
5. Login Screen
This form asks details for User Name and Password to use the facilities provided by
this project. If the user enters correct user name and password then only he/she will
be able to use the facilities provided by this project. This form asks details for User
Name and Password to use the facilities provided by this project. If the user enters
correct user name and password then only he/she will be able to use the facilities
provided by this project. If correct user name and password can be entered then only
a user can log in. user name and password are same like user, LMS, and admin. It has
two buttons Login and Cancel. Login for Log into system and Cancel for
cancellation.
62
`
Address.
63
`
7. Members Information
It shows all the details like Member No, Member FName, Member Mname,
Member Lname, Phone, Address, Issued Book Name, Type of member, etc.
8. News bar
This is for displaying messages for the users to get the feed back form the
9. Publication Information
64
`
Publisher Information gives details of publisher like Publisher, Pub Add, Pub
No of Days (for how any days he/ she kept his/her book ), Due Date, Date Of
Charge,etc.
65
`
66
`
67
`
15. Tips
For
This is a dialog box, which shows the tips of living good life.
68
`
Death Dataset.
69
`
This form records all the information regarding return of the book just like No of
Days (for how any days he/ she kept his/her book ), Due Date, Date Of Issue,Date
Of Return, Fine Rate, No Of Books, Total Days, Fine Charge, etc. It provides a link
to the module Book Information. It uses following formulas to calculate the result.
70
`
71
`
Every system has some process of data storing which is a set of rows and columns. Collection of
this set of data is stored in user-defined object called table and each table contains fields and data
according to the structure of the table, which has been defined by the developers.
This system also has store-, which contains the tables and tables contains the collection of
records.
Student Administration is using Microsoft SQL server as a back-end for the front-end Visual
Basic. Connection has been established using the ADO connection, facility available in Visual
Basic.
Validation Check:
Date,Due Date shouls be in specific date format otherwise it will give an error.
It this form after entering issue date and date of return it will automatically count due
date,no of days books has been kept for that a member must have to pay fine and that will
In all the forms Tips for living good llife has been provided.
72
`
User must enter password then only he/she allow to enter in the screen.
User id and password are same. LMS,Admin,etc.If wrong id and passwod is entered
At the time of closing the repoert it will always display ask that are you
73
`
order to check the primary level stability and functionality of the software.
Automated test scripts will be provided to perform the sanity testing. The
each script, how and in which environment to run the scripts etc.
Call the basic functions and APIs with passing correct parameter values.
Check the behavior of the application after calling the functions and APIs for
them.
74
`
e.g.:
Developers compile the code and hand it over to testers, which is termed a build.
This build is assigned a code along with the version number i.e. 1.00_1, 1.00_2, 1.00_3
At certain stage of testing, there is a high frequency of builds, which come in for testing.
Therefore to check for the stability of the build, QA acceptance testing is done
Validation methods:
Black box testing: Black box testing focuses on the functional requirements of the
software. That is, black box testing enables the software engineer to derive sets of input
conditions that will fully exercise all functional requirements for a program.
User Interface testing: Testing the GUI of the front–end for look and feel, static testing
e.g.
75
`
On home page of yahoo mail, username and password field should appear on the
Capture x,y coordinates and then verify their position and alignment.
Functionality testing: Process of testing to verify that the functions of the system are
present as specified.
e.g.
-Display mail
- Send mails
- Store mails
document.
Boundary Value testing: Check the system by entering all the boundary value conditions.
76
`
Equivalence Class testing: Divide the input domain in classes of data from which test
e.g. yahoo mail client requires a username and password to login. You can have a
Numeric – 1,2,3,4,
Wildcard: ab*,………
Error Trapping: Test all the error messages (whether the error message displayed is
proper against the generated error or not, check the grammar of the messages, check the
In this case, the error message displayed is grammatically correct & consistent
77
`
In this case, the error message is displayed is wrong to the type of error.
White-box testing:
White box testing of software is close examination of procedural detail. Logical paths
through the software are tested by providing test cases for specific sets of conditions,
Conditional testing:
- Conditions using relational and logical operators will be checked for all possible
outcomes.
e.g
take all possible values of a and b to check the relation operator for various
conditions
78
`
Loop testing
- With different conditions of the loop test the validity of the loop construct.
e.g.
Statement coverage
e.g.
All the lines of the 100 lines have to be executed at least once, as passing criteria
79
`
e.g. find all the sub paths where x is used. Used means, variable is used in some
If (a == b){
b = x * 10;
if (a < b) {
a = x + 10;
both the sub paths will have to be exercised for this testing for x.
Memory Leakage testing: Check the used memory is releasing after the function is
destroyed.
80
`
Eg.
After invoking the function and when the function is running memory used is
1000KB.
The function does not release the memory used by variable to the free memory
API testing: Check the comprehensive functionality set provided by each API to test
e.g.
Integration testing: Integration testing will be performed to check for data loss/mismatch
across interfaces, check for adverse effect of one module over other module. Check for
global data structures may not cause problem after integration of modules.
e.g
Consider two modules one of sending a mail, and other of displaying the mails that
were sent. These two modules were developed by different developers, which are to
81
`
be used together. Here integration testing will take place, to check that the mail sent
would be stored in the folder of sent mails. Since both the modules are talking
together check whether they are working as a single entity perfectly or not.
Performance testing: Check the performance of the system at different loads and for
different iterations.
Load testing: Check the performance of the application by creating load by hundreds of
virtual users. This testing will be performed by automated tools and no. of users will be in
a incremental way.
e.g.
The yahoo server experiences the load & hence the response time for each request
Stress testing: Check the performance of the application by creating load by hundreds of
e.g.
When 300 users log in & logout of the yahoo mail client 10 times. At such point of time,
the yahoo server is stressed, which will affect the response time.
Compatibility testing: This will include validating the compatibility of the system for:
82
`
- Different Hardware
- Different Browsers
e.g.
An image attachment with the mail should be displayed in Netscape & Internet Explorer.
Interface testing: Test the interfaces given to the other applications are working properly
e.g.
If a file has to be attached with a mail-using yahoo, the mail client has to interface with
System testing: Check the process of testing an integrated system to verify that it meets
Configuration testing: Test system works properly for the minimum configurations
e.g
If a software installation guide says that minimum requirement for software to function
smoothly is
1. Intel Pentium P3
83
`
2. 64 MB Ram
Test the software with configuration specified, lower configuration and with
higher configuration.
Installation/Un-installation testing: Follow the installation procedure and verify that the
installation is done properly or not. This will include installation through CD, installation
from Web & see that, installing according to the instructions given in the installation
manual results in the proper installation & files being created in appropriate directories.
The uninstall procedure will also be tested to see that it works properly.
e.g
during installation.
Recovery testing: Test how well the system recovers from crashes, hardware failures, or
other disastrous problems at runtime and ensure that the system provides enough
information in such a case to take appropriate measures for avoiding this from happening
in the future.
84
`
Security testing: Attempt to penetrate the system through inappropriate manner, to verify
e.g.
Usability testing: Test the user effort to learn, operate, and prepare inputs. Also test the
e.g. While surfing through the yahoo site, if the user is at the 30th page , there
should be a way out to go to the home page, so that the user does not get stuck up.
tests that have already been conducted to ensure that changes have not propagated
unintended effects. This test will run every time a major change is made to the software
e.g.
85
`
While enroll new user for Hotmail, the password length was kept 8 characters.
Test cases created in previous versions were executed on the new page.
e.g. A bug was found in sent mail module of yahoo mail. The bug was, that the
message sent was truncated after 20 words, while storing in the table of sent mail, as
the field length was less. This bug has been fixed.
Now there are several modules which access this field in the table in which the mail
Regression testing is done to verify whether the bug fix has not affected any other
modules.
Beta testing: Conduct tests like end user of the software and random testing in ‘live’ beta
environment.
e.g.
copies of the Beta version of windows to the customers along with the help files &
installation guidelines. The customers are requested to use product and place bugs
86
`
Database Testing:
Conduct test to ensure proper storage of data in database, and proper retrieval from
database.
e.g.
The book number, member number and other details will be inserted in some table.
Check whether the insertion has taken place in right table with right values.
Security Mechanisms
Any computer-based systems that manage sensitive information or causes actions that
can improperly harm individuals are a target for improper or illegal access.
There should be a correct user id and password for accessing the software. Three
user id and password are provided for accessing this software. User id and password are
same. If user failed to enter correct the details then he/she will not be able to use the
87
`
The cost involved in designing, coding and implementing this software is around Rs.
1450.00
88
`
Reports Generation
*Reports Generations.
Here in this project six reports are generated.
Books_Details:
It provides all the details for books. It also provides details date vise.
Issue/Return Details:
89
`
Member Details:
90
`
Branch_Details:
91
`
Department_Details:
It shows all the information about the departments of a library.
92
`
Author_Details:
PERT Chart
progress.
September
August
June
May
July
PPPPP
Analysis 02-05-2006 15-06-2006
AAAC
PP
A
93
`
P – Plan A – Actual C -
Completion
A network chart, as well as showing the scheduled times for each task,
also shows the dependence of one task is a continuation from lines of a previous
task. A task cannot start until all its incoming tasks have been completed.
The earliest time that a task can begin when all preceding tasks are
completed in the shortest possible time. The latest time for task initiation before
Gantt Chart
Gantt Chart
Gantt Chart (Timeline Chart) can be developed for the entire project.
Analysis
Design
Develop
Implementation
94
`
15 September
30 September
1 September
15 August
1 August
15 June
15 May
15 July
1 June
1 May
1 July
Future Scope and Further Enhancement Of
the project
Development is a constant process. There is always scope of
improvement in every work.
The development of LMS can be further be enhanced by providing some more
facilities. If the Organization wanted to establish a presence on the World Wide Web, the
LMS could easily be adapted to handle e-commerce. To facilitate this web interface will
be developed and similar customer services will be offered through Internet or extranet
A data warehouse pilot project may be introduced depending upon the business growth in
next few years. If management finds it feasible to analyze the strategic data, the data
In future, this application can be further enhanced using serious thought. It is a small
effort to give facilities of this system to smaller organizations. This can be a module to
6. Bibliography
95
`
Black Book
StevSen Holzner
NIIT -
SSI-
96