LIBRARY MANAGEMEN T SYSTEM
1.) Megha Jain roll no: B.Sc. (Hons.) Comp. Sc. (2nd year)
ACKNOWLWDGEMENT
Exchange of ideas generates the new object to work in a better way whenever a person is helped and cooperated by others his heart is bound to pay gratitude and obligation to them. To develop a project is not a one-man show. It is essentially a collective work, where every step taken with all precautions and care. Therefore our first duty is to thanks all persons who took pain in completing this project.
irstly, we thank Mrs. RACHNA S!H"# who gave us inspiration to do work in this field and gave us her precious time whenever needed. Thanks may be matter of merely formality but with us it is expression of heartfelt gratitude to our project supervision. !e are highly indebted for her gestures, invaluable suggestions and boosting confidence to make this successful. The success of this work is mostly due to her suitable guidance.
!e also thank our class fellows and friends, who helped us a lot during our project work.
ACKNOWLWDGEMENT
Exchange of ideas generates the new object to work in a better way whenever a person is helped and cooperated by others his heart is bound to pay gratitude and obligation to them. To develop a project is not a one-man show. It is essentially a collective work, where every step taken with all precautions and care. Therefore our first duty is to thanks all persons who took pain in completing this project.
irstly, we thank Mrs. RACHNA S!H"# who gave us inspiration to do work in this field and gave us her precious time whenever needed. Thanks may be matter of merely formality but with us it is expression of heartfelt gratitude to our project supervision. !e are highly indebted for her gestures, invaluable suggestions and boosting confidence to make this successful. The success of this work is mostly due to her suitable guidance.
!e also thank our class fellows and friends, who helped us a lot during our project work.
CERTIFICATE
This is to certify that the project entitled $%"BRAR& MANA'MN! S&S!M" S&S!M" prepared by us, Shohna # Megha Jainfor Jainfor the partial fulfilment of the re$uirements of the B.Sc. (Hons.) Comp. Sc. degree, Sc. degree, embodies the work, we all are doing during % th semester of our course under due supervision of the supervisor from this college.
&I'()T*+E
INDEX
Conens
S.N
Chaper 1 *ro+ec "nrod,cion
1.
• • • • •
•
2.
• • • • • • •
-. • • • •
7 8 9 10 11
12-33 13 15 18 20 21 22 23 27 32
Introduction about roject anagement. &/! rocess odel. Team &tructure. Introduction about &/! roject &cheduling. Introduction to Time-0ine 1hart. Time-0ine 1hart. +isk )nalysis # anagement. 1omplexity Tables. ) 1alculation.
Chaper Re/,iremen Analysis 0 Managemen •
6-11
Introduction about the project. &tatement of bjectives. &tatement of &cope. roblems with the current system. )dvantages )dvantages of the new system system being designed. designed.
Chaper 2 *ro+ec Managemen •
*age N o .
Introduction about +e$uirement )nalysis # anagement. !hat is +e$uirement )nalysis2 )nalysis rinciples. rinciples. unctional # (on-unctional +e$uirements. 3ata 3ictionary.
34-52 35 36 38 39 41
• •
Entity +elationship 3iagram 4E+35. 3ata low 3iagrams 4336s5.
46 48
Chaper esign •
.
• • • • •
Introduction about 3esign 1oncepts # rinciples. 3esign odel 3atabase 3esign. seudo 1ode. )rchitectural 3esign. Interface 3esign.
53-86 54 55 56 61 64 65
Chapter – 1 Projet I!tro"#t$o! •
• • • •
Introduction about the project. &tatement of bjectives. &tatement of &cope. roblems with the current system. )dvantages of the new system being designed.
INTROD%CTION 0ibrary anagement &ystem is a comprehensive library management solution that is suitable for both large and small libraries. Its flexible design enables 0ibrary anagement &ystem to be installed in a range of 0ibrary organi7ations, ranging from public libraries, through to academic, joint use and special libraries. This 0ibrary anagement &ystem &oftware is capable of handling 8ooks # eriodicals with e$ual ease and efficiency. This is a !indows-based 0ibrary anagement &ystem, utili7ing the latest advancements in the Information Technology to provide and improve 0ibrary &ervices.
OB&ECTI'E The objective of this project is to develop an application that will automate the whole procedure of a library. The software that would be developed should have facilities like )dd / 3elete embers, )dd / 3elete 8ooks, Issue # +eturn. The application should be secured, as well as with limited access. . The main re$uirement of the project will be the ease of use, besides being the most efficient and effective tool for the purpose. The application should be user friendly .It should be robust and scalable. )n automated solution would be very beneficial to the organi7ation, as it would bring structure to the whole process so that it can be traced for any kind of $uery. )lso an automated solution will lead to optimal utili7ation of the available resources, reducing duplication of effort, increasing efficiency and minimi7ing time-delays.
ollowing are the main objectives of computeri7ation9 •
To provide services to all the employees for issue, return # search etc. at one place.
•
To improve co-ordination in staff.
•
To reduce paper filling work
•
To reduce risk of fraud.
•
To reduce chances of information leaking.
SCOPE 3or Memers •
acility for &E)+1: of 8ooks based on )ccession (umber, Title, )uthor, &ubject, ;eyword.
•
acility for I&&*E / +ET*+( 8ooks.
•
acility for +E(E!)0 of 8ooks.
3or %irary Sa44 •
)utomatic installation
•
&imple and intuitive '*I for performing all functions
•
&hort-cut keys and point-and-click operation.
•
&ecurity features like access control using passwords and login-i.d.
•
•
)utomatic calculation of late-fee. acility to )33 / 3E0ETE embers, 0ibrary &taff # 8ooks and aintain an easy record of all these.
PROBLEMS WIT( T(E C%RRENT SYSTEM
•
•
•
Issue / +eturn a book from / to the library is a cumbersome process.
aintenance of the record of each member / book is a very tedious job. 0arge amount of human efforts are re$uired to keep a track of members who have issued a book, who have returned a book and which book is issued / returned.
odifying the details of members or books is a very tedious job if done manually.
AD'ANTAGES The benefits of the proposed software are as follow9
Reliailiy The application would efficiently store all the information related to the various processes in the system and output the relevant information.
A5ailailiy The application would be available to all the employees of the organi7ations with an authori7ed access to the workstations and those who are subject to the authori7ation permissions.
Sec,riy The system would have ade$uate security checking through the authentication of the users. The reports would only be available to the employees of the library as per their specific re$uirements.
Cos Red,cion It can be achieved by minimi7ing the use of the stationary for reports. &oft copy of all the reports. &oft copy of all the reports can be viewed and hence reducing the need of the hard copy.
Chapter – ) Projet Ma!a*e+e!t •
•
•
•
• • • • •
Introduction about roject anagement. &/! rocess odel. Team &tructure. Introduction about &/! roject &cheduling. Introduction to Time-0ine 1hart. Time-0ine 1hart. +isk )nalysis # anagement. 1omplexity Tables. ) 1alculation.
PRO&ECT MANAGEMENT SYSTEM roject management involves the planning, monitoring, and control of the people, process, and events that occur as software evolves from a preliminary concept to an operational implementation. Effective software project management focuses on the four principles9 people, product, process, and project.
!H *6*% &oftware engineering institute has developed a people management capability maturity model 4-15. The people management maturity model defines the key practice areas for software people like9 recruiting, selection, performance management, training, compensation, carrier development, organi7ation and work design, and team/culture development.
!H *R67C! 8efore a project can be planned, product objectives and scope should be established, alternative solutions should be considered and technical and management constraints should be identified. &cope identifies the primary data, functions and behaviours that characteri7e the product.
!H *R6CSS ) software process provides the framework from which a comprehensive plan for &oftware development can be established. 3rame8or9 aci5iies are populated with tasks, milestones, work products and =uality assurance points. These activities characteri7e the software product and the project team. 7mrella aci5iies i.e. software $uality assurance, software configuration management and measurement overlay the process model.
!H *R6JC! lanned and controlled software projects are conducted to manage complexity. To avoid project failure, the project manager must avoid a set of common warning signs, understand critical success factors and develop a common sense approach for planning, monitoring and controlling the project.
SOFTWARE PROCESS MODEL ,L$!ear Se-#e!t$a. Mo"e./ ) process model for software engineering is chosen based upon9-
•
(ature of the roject.
•
ethods and Tools to be used.
•
1ontrol and desired deliverables.
The process model, we have chosen to develop this software is a 0inear &e$uential odel
0inear &e$uential odel suggests a systematic, se$uential approach to software development that begins at the system level and progresses through analysis, design, coding, testing and support.
%inear Se/,enial Model approach has he 4ollo8ing phases:
So48are re/,iremens analysis In this, software engineer understand the nature of a program to be built, he must understand the information domain for the software as well as re$uired function, behaviour, performance and interface. +e$uirements for both the system and the software are documented and reviewed with the customer.
esign It has four distinct attributes of a program9 data structure, software architecture, interface representations and procedural detail. It is documented and becomes part of the software.
Code generaion 3esign must be translated into a machine readable form which is done by code generation.
!esing It focuses on the logical internals of the software, ensuring that all the statements have been tested, and on the functional externals> that is conducting test to uncover errors and ensure that defined input will produce actual results.
The &oftware model used is %"NAR S;7N!"A% M6% because of the following reasons9-
roject being small demands a systematic and se$uential approach to software
development i.e. system engineering, software re$uirement analysis, design, code generation, testing and support occur in se$uence.
)ll re$uirements for the project have been explicitly stated at the beginning.
There is very little scope of customers6 deviation from current re$uirements, coding and testing after detailed analysis is much easy.
&tructure is less complex and less innovative with less need of iteration.
S,ppor This is a phase when software will undoubtedly undergo change after it is delivered to the customer. 1hange will occur because errors have been encountered, because the software must be adapted to accommodate changes in its external environment, or because the customer re$uires functional or performance enhancements. &oftware support/maintenance reapplies each of the preceding phases to an existing program rather than a new one.
TEAM STR%CT%RE The “best” team structure depends on91. anagement style of the organi7ation. 2. The number of people who will populate the team and their skill levels, and -. The overall problem difficulty.
The three generic team organizations are9
emocraic decenrali
Conrolled decenrali
Conrolled cenrali
The team structure used in our project is DEMOCRA!C DECE"RA#!$ED. The team comprises of two members9•
Shohna(=>?)
•
Megha Jain(=>-=)
3ecentrali7ed teams generate better solutions and have greater probability of success when working on different problems. 33 team structure is best applies to programs with low modularity.
8ased on the difficulty of the problem to be solved relatively low modularity of the project and high volume of the communication re$uired a democratic decentrali7ed team structure is proposed. This software engineering team has no permanent leader. +ather, ?task coordinators are appointed for short duration and then replaced by others who may coordinate different tasks." roblem solving is a group activity. 1ommunication among team members is hori7ontal. 3ecentrali7ed team generates more and better solutions than individuals. Therefore such teams have a greater probability of success when working on difficult problems.
) decentrali7ed structure can be applied to both simple and difficult problems, but it is best applied in case of difficult problems. These team structures result in high morale, therefore good for teams that will be together for a long time. The decentrali7ed team structure is best applied to the problem with relatively low modularity because of the higher volume of communication needed. These teams re$uire more time to complete a project and at a same time be best when high sociability is re$uired. In these teams, team members have trust on each other, distribution of skills must be appropriate to the problem and they share a common goal.
SOFTWARE PRO&ECT SC(ED%LING @HA! "S "! &oftware roject &cheduling is an activity that distributes estimated effort across the planned project by allocating the effort to a specific software engineering tasks.
!hen you develop a schedule, compartmentali7e the work, represent the task interdependencies, allocate effort and time to each task, define responsibilities for the work to be done, and define outcomes and milestones.
@H& "S "! "M*6R!AN! In order to build a complex system, many software engineering tasks occur in parallel, and result of work performed during one task may have a profound effect on work to be conducted in another task. These interdependencies are very difficult to understand without a schedule. It6s also a virtually impossible to progress on a moderate or large software project without a detailed schedule.
INTROD%CTION TO TIMELINE C(ART !hen creating a software project schedule, the planner begins with a set of tasks. If automated tools are used, the work breakdown is input as a task network or task outline. Effort, duration and start date are then input for each task outline. In addition, tasks may be assigned to specific individuals.
)s a conse$uence of this input a Timeline 1hart is generated. It enables you to determine what tasks will be conducted at a given point of time.
TIMELINE C(ART S. No.
1
!AS
ae o4 Sar
ae 64 Compleion
Re/,iremen gahering 0 Analysis
1.1
%irary Sa44
?2.?1.2??>
?.?1.2??>
1.2
?.?1.2??>
?D.?1.2??>
1.-
Memers (S,dens 0 !eachers) Search
11.?1.2??>
1.?1.2??>
1.
"ss,e 0 Re,rn
1.?1.2??>
2-.?1.2??>
1.E
3*A Calc,laion
2E.?1.2??>
-1.?1.2??>
1.
aa icionary
?2.?2.2??>
?E.?2.2??>
1.=
R
?=.?2.2??>
11.?2.2??>
1.>
3
1E.?2.2??>
21.?2.2??>
2
esign
2.1
aa esign
2.?2.2??>
2D.?2.2??>
2.2
Archiec,ral esign "ner4ace esign
1?.?-.2??>
1E.?-.2??>
1=.?-.2??>
2-.?-.2??>
2.-
RISK ANALYSIS 0 MANAGEMENT +isk analysis and management are a series of steps that help a software team to understand and manage uncertainty. any problems can plague a software project, a risk is a potential problem that might happen or might not.
R"S "N!"3"CA!"6N This is the first step for recogni7ing what can go wrong. (ext, each risk is analy7ed to determine the likelihood that it will occur and the damage that it will do if it does occur. nce this information is established, risks are ranked by their probability and impact. inally, a plan is developed to manage those risks with high probability and impact.
"!FS @6R *R67C! +isk mitigation, monitoring and management 4+5 plan or a set of risk information sheets is produced.
CATEGORIES OF RISK
*ro+ec Ris9s They threaten the project plan. They identify potential budgetary, schedule, personnel, resource, custom potential and re$uirements problem and there impact on software project. They might result in delay in project schedule and cost.
!echnical Ris9s They identify potential design, implementation, interface verification, and maintenance problem. They threaten the $uality and timeliness of software
B,siness Ris9s They often jeopardi7e the project or the product # include market risk, strategic risk, management risk and budget risk.
R$2 M$t$*at$o! P.a! )ll risk analysis activities presented to this point have a single goal-to assist the project team in developing a strategy for dealing with risk.
Issues9 •
+isk avoidance
•
+isk monitoring
•
+isk management and contingency planning
&teps taken are9 •
eet with current staff and check cause for problems
•
itigate causes which are under control before project starts
•
resume turnover will occur develop plans
•
1onduct peer reviews
RISK STRATEGIES Reaci5e ) +eactive &trategy monitors the risk project for likely risk and set aside resources to deal with them, should they become actual problems. &oftware team does nothing about risks until something goes wrong.
*roaci5e ) roactive strategy begins long before technical work is initiated. otential risks are identified, their probability impact is assessed, and they are ranked by importance.
Co+p.e3$t4 Ta5.e
INP%T SCREEN COMPLEXITY TABLE S. No
Screen Name
No. o4 4ields
No. o4 4iles CompleGiy
1.
)dd ember
@A
@
)verage
2.
)dd 8ook
B
@
)verage
-.
Issue !ith ember I3
C
C
)verage
.
Issue !ith )cc. (o.
C
C
)verage
E.
Issue
%
C
)verage
+eturn
D
D
0ow
=.
+eturn after ine
@
C
0ow
S. No
Screen Name
No. o4 4ields
No. o4 4iles CompleGiy
1.
ember &earch
@@
D
)verage
2.
@@
D
)verage
-.
ember6s 3etail 8ook &earch
@
)verage
.
8ook6s 3etail
B
@
)verage
O%TP%T SCREEN COMPLEXITY TABLE
6%ERY SCREEN COMPLEXITY TABLE
S. No
Screen Name
No. o4 4ields
1.
0og-in
D
@
0ow
2.
3elete ember
@
@
0ow
-.
3elete 8ook
@
@
0ow
.
1heck ember6s +ecord 1heck 8ook6s 3etail
@
@
0ow
@
@
0ow
E.
No. o4 4iles CompleGiy
S. No
3ile Name
No. o4 4ields
No. o4 records
CompleGiy
@.
ember6s +ecord
@%
@
0ow
D.
8ook6s +ecord
B
@
0ow
C.
&taff +ecord
@A
@
0ow
ILF COMPLEXITY TABLE
FPA Ca.#.at$o!
%NAD&%STED F%NCTIONAL POINT CALC%LATION No. o4 inp,s No. o4 o,p,s No. o4 4iles No. o4 /,eries 73*
Simple
A5erage
CompleG
!oal
DFC AF% CF GFC
GF% %FG AF@A AF%
AFH AF AF@G AFH
DH DA D@ @G BD
3,ncion *oin Calc,laion 3* 73* I ( ?.E ?.?1 I
J BD F 4 A.HG K A.A@ F %D5 J BD F @.A J B.%
3i )
Chapter – 7 Re-#$re+e!t A!a.4$ 0 Ma!a*e+e!t •
• • •
• • •
Introduction about +e$uirement )nalysis # anagement. !hat is +e$uirement )nalysis2 )nalysis rinciples. unctional # (on-unctional +e$uirements. 3ata 3ictionary. Entity +elationship 3iagram 4E+35. 3ata low 3iagrams 4336s5.
INTROD%CTION This is the process of deriving system re$uirements through observation of existing system, discussions with potential users, task analysis and so on. This may involve the devel develop opme ment nt of one one or more more diffe differen rentt system system model. model. These These help help the analy analyst st to understand the system to be more specific.
RE6%IREMENT ANALYSIS Re%uirement analysis is analysis is a software engineering task that bridges the gap between system level re$uirements engineering and software design.
System Level Engineerin g Requirement Analysis
S!t"are #esign
The software re$uirements analysis may be divided into five areas of efforts9efforts 9-
*rolem recogniion +ecognition of basic problem elements as perceived by the users.
5al,aion and synhesis
3efine all data objects, evaluate the flow and content of information, define and elaborate all functions, understand software behaviour and establish interface characteristics.
Modelling unctional models represent the information that software transforms, functions enabling the transformation, and behaviour of the system during transformation.
Speci4icaion &tates the goals and objectives of the software, describing it in context of the 1omputer based system.
Re5ie8 1hanges to the specification may be recommended.
A!a.4$ Pr$!$p.e 1. The 1. The information domain of a problem must be represented and understood. 2. The 2. The functions to be performed by software must be defined. -. The -. The behaviour of the software must be represented. . The . The models that depict information function and behaviour must be partitioned in a manner that uncovers detail in a layered fashion. E. The E. The analysis process should move from essential information towards implementation detail.
NON8F%NCTIONAL RE6%IREMENTS 4@5
&erver must have enough disk space so as to store large amount of data.
4D5
&ystem should provide data security. *nauthori7ed users should not be allowed to access the system so that the integrity and secrecy of each client must be maintained.
4C5
) network operating system that can support the software.
F%NCTIONAL RE6%IREMENTS 4@5
The system must be easy to learn and easy to use so that it is readily accepted by its prospective users. It must provide easy and convenient means of communication between different clients.
4D5
It should synchroni7e the access of channels to clients. (o two clients should be allowed to transmit data simultaneously.
4C5
It must detect collisions and recover lost messages.
4%5
1lient should not be allowed to run while the server is not running.
4G5
It must handle exceptional conditions appropriately and efficiently.
4H5
)ppropriate error messages should be generated in case some exception has occurred.
45
It must support client-to-client communication as well as broadcasting.
4B5
&ystem must be fault tolerant i.e. it can continue in operation even after some system failure has occurred.
DATA DICTIONARY
S. No.
aa "em
1
!ACHRS
!ype
%engh
1.1
Name
Sring
-?
1.2
3. Name
Sring
-?
1.-
M. Name
Sring
-?
1.
.6.B.
"neger
1?
1.E
SeG
Sring
1.
Add.
Sring
E?
1.=
*h. No.
"neger
1?
1.>
S,+ec
Sring
1?
1.D
Coll. "..
"neger
1?
1.1?
&r. 64 Join
"neger
2
escripion
Conains Name o4 he eacher Conains 3aherFs Name o4 he eacher Conains MoherFs Name o4 he eacher ae o4 Birh SeG 64 he eacher Residenial Address Conac N,mer S,+ec a,gh y he eacher College ".. No. &ear o4 +oining
S!7N!S
2.1
Name
Sring
-?
2.2
3. Name
Sring
-?
Conains Name o4 he s,den Conains 3aherFs Name o4 he s,den
2.-
M. Name
Sring
-?
2. 2.E
.6.B. SeG
"neger Sring
1?
2.
Add.
Sring
E?
2.=
*h. No.
"neger
1?
2.>
Co,rse
Sring
1?
2.D
Coll. Code
"neger
1?
2.1?
&r. 64 Admission
"neger
-
"SS7 K R!7RN
-.1 -.2
. 64 "ss,e . 64 Re,rn
"neger "neger
1? 1?
-.-
Ac,al . 64 Re,rn
"neger
1?
Conains MoherFs Name o4 he s,den ae o4 Birh SeG 64 he s,den Residenial Address Conac N,mer Co,rse chosen y he s,den College Code o4 he s,den &ear o4 admission
ae o4 iss,e ae o4 re,rn Ac,al ae o4 re,rn
MMBRFS RC6R
.1
Memer "..
"neger
1?
.2
No. 64 Boo9s "ss,ed
"neger
1
.-
Lalidiy
"neger
MemerFs ".. No. N,mer o4 oo9s iss,ed on memerFs acco,n ae o4 eGpiry o4 memership
.
E
3ine !ill ae
"neger
B66S
E.1
Name
Sring
-?
E.2
A,hor
Sring
-?
E.-
*,lisher
Sring
-?
E.
diion
"neger
2
E.E
No. 64 Copies
"neger
-
E.
*riceKCopy
"neger
E.=
Acc. No.
"neger
1?
E.>
S,+ec
Sring
2?
.1
.2
3ine o e paid ill presen dae
Conains Name o4 he oo9 Conains A,horFs Name o4 he oo9 Conains *,lisherFs Name o4 he oo9 diion o4 he oo9 No. o4 copies a5ailale o4 he oo9 *rice per copy o4 he oo9 Acc. N,mer o4 he oo9 S,+ec relaed o he oo9
%"BRAR& S!A33 Name
3. Name
Sring
Sring
-?
-?
Conains he Name o4 he sa44 memer Conains 3aherFs Name o4 he sa44 memer
.-
M. Name
Sring
-?
. .E
.6.B. SeG
"neger Sring
1?
.
Add.
Sring
E?
.=
*h. No.
"neger
1?
.>
&r. 64 Join
"neger
.D
%ogin "..
Sring
2?
.1?
*ass8ord
Sring
2?
Conains MoherFs Name o4 he sa44 memer ae o4 Birh SeG 64 he sa44 memer Residenial Address Conac N,mer &ear o4 +oining %ogin ".. o4 sa44 memer *ass8ord o4 he sa44 memer
E!t$t4 Re.at$o!h$p D$a*ra+ ,ERD/
Data F.o9 D$a*ra+ ,DFD:/
Le;e. <=: DFD
Le;e. <1: DFD
Chapter – >
De$*! •
• • • • •
Introduction about 3esign 1oncepts # rinciples. 3esign odel 3atabase 3esign. seudo 1ode. )rchitectural 3esign. Interface 3esign.
DESIGN CONCEPTS 0 PRINCIPLES
3esign is a meaningful engineering representation of something that is to be built. It can be traced to customer6s re$uirements and at the same time assessed for good $uality against a set of predefined criteria for a ?'ood 3esign".
&oftware 3esign is applied regardless of the software process model that is used. nce software re$uirements have been analy7ed and specified, software design is the first of three technical activities L design, code generation and test L that are re$uired to build and verify the software.
3esign focuses on four major areas of concern9 data, architecture, interfaces and components.
C6M*6NN! %L% S"'N It transforms structural elements of software architecture into a procedural description of software components.
"N!R3AC S"'N It describes how the software communicates within itself, with systems that interoperate with it, and with the users who use it.
ARCH"!C!7RA% S"'N It defines the relationship between major structural elements of the software.
A!A S"'N
It transforms the information domain model created during analysis into the data structures that will be re$uired to implement the software.
DESIGN MODEL
# $ C6M*6NN! %L% S"'N
"N!R3AC S"'N
ARCH"!C!7RA% S"'N
A!A S"'N
DATABASE DESIGN !ACHRS
S.No.
aa "em
!ype
%engh escripion MandaoryK *rimary 6pional ey
1.1
Name
Sring
-?
1.2
3.Na me
Sring
-?
1.-
M.Na me
Sring
-?
1.
"neger
1?
1.E
.6.B . SeG
Sring
1.
Add.
Sring
E?
1.=
*h. No.
"neger
1?
1.>
S,+e c Coll.". . &r. 64 Join
Sring
1?
"neger
1?
"neger
1.D 1.1?
Conains Name o4 he eacher Conains 3aherFs Name o4 he eacher Conains MoherFs Name o4 he eacher ae o4 Birh SeG 64 he eacher Residenial Address Conac N,mer S,+ec a,gh y he eacher College ".. No. &ear o4 +oining
M
6
6
6
M
6
6
M
M
&S
6
S!7N!S
S.No.
aa "em
!ype
%engh escripion MandaoryK *rimary 6pional ey
2.1
Name
Sring
-?
2.2
3.Name
Sring
-?
2.-
M. Name
Sring
-?
2. 2.E
.6.B. SeG
"neger Sring
1?
2.
Add.
Sring
E?
2.=
*h. No.
"neger
1?
2.>
Co,rse
Sring
1?
2.D
Coll. Code &r. 64 Admiss ion
"neger
1?
"neger
2.1?
Conains Name o4 he s,den Conains 3aherFs Name o4 he s,den Conains MoherFs Name o4 he s,den ae o4 Birh SeG 64 he s,den Residenial Address Conac N,mer Co,rse chosen y he s,den College Code o4 he s,den &ear o4 admission
M
6
6
6 M
6
6
M
M
&S
6
"SS7 K R!7RN
S.No.
aa "em
!ype
-.1
. 64 "ss,e . 64 Re,rn Ac,al . 64 Re,rn
"neger
1?
ae o4 iss,e
M
"neger
1?
ae o4 re,rn
M
"neger
1?
Ac,al ae o4 re,rn
M
-.2 -.-
%engh escripion MandaoryK *rimary 6pional ey
MemerFs Record
S.No. .1
aa "em
!ype
Memer "neger "..
%engh escripion MandaoryK *rimary 6pional ey 1?
.2
No. 64 Boo9s "ss,ed
"neger
1
.-
Lalidiy
"neger
.
3ine !ill ae
"neger
MemerFs ".. No. N,mer o4 oo9s iss,ed on memerFs acco,n ae o4 eGpiry o4 memership
M
&S
M
M
3ine o e paid ill presen dae
M
B66S
S.No.
E.1
aa "em Name
!ype Sring
%engh escripion MandaoryK *rimary 6pional ey -?
E.2
A,hor
Sring
-?
E.-
*,lisher
Sring
-?
E.
"neger
2
E.E
diion No. 64 Copies
"neger
-
E.
*riceKCopy "neger
E.=
Acc. No.
"neger
1?
E.>
S,+ec
Sring
2?
Conains Name o4 he oo9 Conains A,horFs Name o4 he oo9 Conains *,lisherFs Name o4 he oo9 diion No. o4 copies a5ailale *rice per copy o4 he oo9 Acc. N,mer o4 he oo9 S,+ec relaed o he oo9
M
M
M
M
6
6
M
&S
M
%"BRAR& S!A33 S.No.
aa "em
!ype
%engh escripion MandaoryK *rimary 6pional ey
.1
Name
Sring
-?
.2
3.Name
Sring
-?
.-
M.Name
Sring
-?
.
.6.B.
"neger
1?
.E .
SeG Add.
Sring Sring
E?
.=
*h. No.
"neger
1?
.>
&r. 64 Join
"neger
.D
%ogin "..
Sring
2?
.1?
*ass8ord Sring
2?
Conains Name o4 he sa44 memer Conains 3aherFs Name o4 sa44 he memer Conains MoherFs Name o4 he sa44 memer ae o4 Birh SeG 64 he sa44 memer Residenial Address Conac N,mer &ear o4 +oining %ogin ".. o4 sa44 memer *ass8ord o4 he sa44 memer
M
6
6
6
M 6
6
M
M
&S
M
Pe#"o Co"e
%ogin Screen This screen takes the uni$ue login-id # password of the library staff member allowing him/her to use the system at his/her level of interference.
Men, Screen This screen asks the library staff member to input the choice of task he/she wants to perform. 1hoices include- )dd/3elete a member, )dd/3elete a book, &earch for a member/book, 1heck the details of a particular member/book, Issue/+eturn a book etc.
Add a ne8 memer This screen takes the details of the new member to be added from the library staff # then accepts the new member as a part of the library unless # until some fields are not left empty or are given invalid inputs. 3etails include- (ame, ather6s name, other6s name, &ex, )ddress, hone (o., 1ollege code, Mear of joining/)dmission, &tatus in the college 4whether &tudent or Teacher5, 1ourse etc.
elee a memer This screen takes the member6s id of the member to be deleted as the input from the library staff # then deletes the member from the library records unless an invalid member id is not entered by the staff member.
Add a ne8 oo9 This screen takes the details of the new book to be added from the library staff # then makes the new book available for Issue/+eturn unless # until some fields are not left empty or are given invalid inputs. 3etails include- (ame, )uthor6s name, ublisher6s name, Edition, (o. of copies, rice per copy, )cc. (o., &ubject etc.
elee a oo9 This screen takes the )cc. (o. of the book to be deleted as the input from the library staff # then deletes the book from the library records unless an invalid )cc. (o. is not entered by the staff member. The book deleted no longer remains available for Issue/return purposes.
Search 4or a memer This screen takes some description about the member to be searched according to the method of searching chosen by the library staff member. The methods of searching include- &earch by name, by course, by member id etc. The records found are displayed on the same screen 4if they really exist5. This screen also allows the staff member to select a name from the records found # then check the details of the member directly from here.
Chec9 memer deails This screen takes the member id as the input from the library staff member # then searches for the member among a list of members and then displays the full details of the member searched if a valid member id is provided as the input. This screen also allows the library staff to issue this member a book directly from this screen as the staff member doesn6t needs to enter the member id while issuing the book. The book is issued unless the member6s account is not full 4max. of G books is taken as an assumption5 or an invalid )cc. (o. is not added.
Search 4or a oo9 This screen takes some description about the book to be searched according to the method of searching chosen by the library staff member. The methods of searching include- &earch by name, by subject, by author etc. The records found are displayed on the same screen 4if they really exist5. This screen also allows the staff member to select a book from the records found # then check the details of the book directly from here.
Chec9 oo9 deails This screen takes the )cc. (o. as the input from the library staff member # then searches for the book among a list of books and then displays the full details of the book searched if a valid )cc. (o. is provided as the input. This screen also allows the library staff to issue this book directly to a member from this screen as the staff member doesn6t needs to enter the )cc. (o. while issuing the book. The book is issued unless the member6s account is not full 4max. of G books is taken as an assumption5 or an invalid member id is not added.
"ss,e This screen takes member id, )cc. (o., 3ate of issue, 3ate of return from the library staff # then issues the selected book the member unless an invalid member id or )cc. (o. is not entered by the staff member or the member6s account is not full 4max. of Gbooks is taken as an assumption5 or else the book is not already issued to some other member.
Re,rn This screen takes the member id, )cc. (o. as the input from the library staff # then displays the details of the book. The details include- 3ate of issue, 3ate of return. 3ate of actual return is entered by the staff member # the fine is calculated if the )ctual date of return is later than the 3ate of return specified to the member. The book is then deleted from the member6s account when all dues are cleared and it is again available for issue/return purposes.
Arh$tet#ra. De$*!
I!ter?ae De$*!
