Software Development Methodologies Library Management System (Part-1)

1. PRESENTATION
ON
Software Development
Methodologies
Library Management System
(Part-1)
1

2.  Domain
 Actors
 Functional Requirements
 Non functional Requirements
 Use Cases Diagram
 Class
 Class Diagram
 Object
 Class/Object Relation
 Conclusion
2

3. 3

4. 1. Librarian
2. Member (Student/Other)
3. Guest
4. Asst. Librarian
4

5.  Add Article: New entries must be entered in
database
 Update Article: Any changes in articles should be
updated in case of update
 Delete Article: Wrong/Expiry/Un-usable entry must
be removed from system
 Inquiry Members: Inquiry all current enrolled
members to view their details
 Inquiry Issuance: Inquiry of all database articl
5

6.  Authentication: User must authenticated
before accessing system
 Search Article: User can search any article
 Request Article: After successful searching
member mark this book as requested article
 Check Account:This use case is used to
check account details
6

7. Asst. Librarian
Prepare Library database
All data base must be prepared
Guest
Register user
User must full fill all application form for registration
7

8. Safety Requirements
The database may get crashed at any certain time due
to virus or operating system failure.Therefore, it is
required to take the database backup
Security Requirements
We are going to develop a secured database for
the university .There are differentcategories of users
namely teaching staff, administrator, library staff
,students etc.,Depending upon the category of user the
access rights are decided. It means if the user isan
administrator then he can be able to modify the data,
delete, append etc.
8

9. Software Quality Attributes
The Quality of the database is maintained in such a way
so that it can be very user friendly to all the users of
the database
Hardware Constraints
The system requires a database in order to store
persistent data. The database should have backup
capabilities.
Software Constraints
The development of the system will be constrained by
the availability of requiredsoftware such as database
and development tools.The availability of these tools
will be governed by
9

10. Hardware Interfaces
Server
Operating System: Windows
Processor: Pentium 4.0 GHz or higher
RAM: 1GB Mb or more
Hard Drive: 80 GB or more
Client
Operating System: Windows.
Processor: Pentium III or 2.0 GHz or higher.
RAM: 512 Mb or more
Software interfaces
Oracle database 8i or 10g
Developer 2000
10

11. 11

12.  Library: It is the place where books, newspapers,
magazine etc are placed for users. It
 provides the card to its regular user with or without
cost.
 Library Card: It is a normal identity card containing
the basic information of the user.
 Books: The library most contains books or it is the
main resources of the library.
 Students: They are the primary user of the library
 Bar code reader: It is an electronic device which is
used to read the coded information
 for the validation.
 Librarian: The persons who handle the overall
operation of the library.
12

13. 13

14.  In object oriented analysis design, objects are the
entities through which we perceive the world
around us. We normally see our system as being
composed of things which have recognizable
identities & behavior. Those entities are then
represented as object in the program. They may
represent a person, a place, a bank account, or
any item that the program must handle. For a
simple examples, vehicles are objects as they
have size, weight, color, etc as attributes and
starting, pressing the brake, turning the wheel,
pressing the accelerator etc as the operation(that
is function).
14

15. 15

16.  This project is intend for minimizing the
communication gap of the member and
librarian.
 Librarian can maintain of this online system.
16

17. 17