SDS
SDS
1
4.70 SYSTEM DESIGN SPECIFICATIONS
4.71 INTRODUCTION
The purpose for this document is to show how the system will be developed and implemented. This
phase helps the developers to follow the specification of the system without so many complications thus
facilitate easy maintenance of the system and minimizes errors during implementation.
4.72 SCOPE
Macmillan Library management system is a System of Macmillan Library that strives to provide the best
services to the clients and to achieve this they need a system that is Complete, Available and running
without problems.
The user can gather information sent according to his user level and can manipulate the site accordingly.
Different users have different user privileges that allows everyone do as assigned by the admin.
Develop and implement to cover all the functionality and features of the proposed system,
clearly stating and explaining all attributes to be enforced on the system.
Come up with an easy way of storing data and ensuring security for the data.
Come up with an attractive design to address the mission and objectives of the proposed
system.
Enabling easy way of generating reports whenever required.
2
4.73 CONTEXT DIAGRAM
The diagram illustrates all the information that is received and sent to the system. The Admin (User) is
the only one who can edit information in the database. The rest of the Users (Clients) will be at a
position to just add records and view information about the Clients and books requested. The Client will
only be able to view his/her records.
USER/CLIENTS ADMINISTRATOR
Data Data
MACMILLAN
LIBRARY
MANAGEMENT
SYSTEM
3
4.74 DATA FLOW DIAGRAMS
This is a process of diagrammatic representation the systems input, outputs and processes. It involves;
Process modeling which represents the functional units and the movement of documents, data
or information.
Data flow diagrams (DFD) which is a powerful method of modeling processes, that shows what is
happening in a process.
Data flow charts which show the logic flow of information within a process.
Required output.
The process.
4
4.75 DATA FLOW DIAGRAM
Indicates the direction and characteristics of data flowing in the considered information system. It is
denoted by an arrow.
1
User D1 user
User
Authenticatio Details
n
2
Client D2 Client
Recording the
Client Details Details
3 D3 User/
Adding Client
User/Client
Details
details
Admin D3 Client
4 User
5
4.76 PROCESS MODELLING
1. Start
2. Declare variables username, password
3. Get values of user name, password
4. If username and password match, system logs in
5. Else
Print “Invalid Username or Password, Try Again!!”
6. End If
7. Stop
1. Start
2. Declare variables client details
3. Get values of client details
4. Print client details
5. Stop
1. Start
2. Declare variables client details
3. Get values of client details
4. If client details is correct
Delete
5. Else
Move NeXT
6. End If
7. Stop
6
D. PSEUDO CODE FOR RECORDING THE CLIENT RECORDS.
1. Start
2. Declare variables client Records
3. Get values of client records
4. Print client records
5. Stop
In the Macmillan Library, a Client visits Macmillan Library management system site then first registers
and waits for the Admin to approve the registration. Once the registration is successful the client can
add books to his borrow request and place the request then wait for a response. The admin (librarian)
will see the order and respond to it accordingly. It’s the fastest and most convenient way to request a
book online.
Macmillan Library management system will allow Admins to create user login details for clients, and the
librarian and assign them rights. Librarian will to key in client details and the book they borrow and the
borrowed books can be viewed by the client portal. The client book borrowed will be verified by the
librarian and the admin can view the books borrowed and performance of the clients in terms of books
borrowed and returned and also the reports can be shown on a graphical means and they will be
updated directly to the database.
7
4.81 THE CONTEPTUAL DATA MODEL
Admin Client
id (fk) id (pk)
Client
Book id F- Client L-
(pk) Book name name
name
Book Client
Pl phone
type
BOOK ac CLIENT no:
es
Librarian id
(fk) Client
age
Client ID
(fk)
Records
Records
Admin
User id id (pk)
(pk)
Admin
Libraria
F-
n F-
name
name
LIBRARIAN ADMIN
Librari AdminL
an L- -name
name
Admin
Librarian Admin Admin
Librarian phone
phone specialization address
address no:
no:
8
The following Attributes were identified from the following conceptual diagram.
CLIENT Client id, Client name, client phone number, client age
ADMIN Admin id, admin name, admin phone number, admin address, admin
specialization
LIBRARIAN Librarian id, Librarian name, Librarian phone number, Librarian address
BOOK Book id, Book name, Book type
9
4.82 PHYSICAL DESIGN
TABLES
ADMIN TABLE
LIBRARIAN TABLE
CLIENT TABLE
10
Field name Data type Description
Client id Number Client identification
number
Client first name Text Gives the first name of
the Client
Client last name Text Gives the last name of the
Client
Client phone Number For communication
number purpose
Client age Number Identifies his/her age
BOOK TABLE
11
A. LOGIN
USER NAME
PASSWORD
LOGIN
EXIT
B. HOMEPAGE
12
MACMILLAN LIBRARY MANAGEMENT SYSTEM
NAVIGATION
PANEL
BORROWED
AVAILABLE
BOOKS
BOOKS
SETTINGS
13
D. CLIENT FORUM
Profile
Client F-
name
Auto
Username Generated
Client L-
name
Password
Client
phone
Status
no:
Client age
Client
D.O.B
SAVE
14
15