Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
133Activity
0 of .
Results for:
No results containing your search query
P. 1
Design Document for library management system

Design Document for library management system

Ratings:

5.0

(1)
|Views: 11,938|Likes:
Published by kapilisme

More info:

Published by: kapilisme on Feb 22, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

12/09/2014

pdf

text

original

 
Software Design DescriptionVersion <1.0>Date: 06/02/2010ONLINE LIBRARY MANAGEMENTSYSTEMAuthor: Ankit AgarwalKapil Sharma
i
 
Table of Contents
Contents
Contents ............................................................................................................................................................11.0. Introduction ................................................................................................................................................21.1. Purpose and Scope .................................................................................................................................21.2. Glossary .................................................................................................................................................21.3. References ..............................................................................................................................................21.4. Overview of Document ..........................................................................................................................32.0. System Architecture ...................................................................................................................................43.0. Data Dictionary ..........................................................................................................................................53.1. Objects ...................................................................................................................................................53.2. Class Diagram: .......................................................................................................................................64.0. Architectural Design ..................................................................................................................................6..........................................................................................................................................................................85.0.Data Design ..............................................................................................................................................106.0. Use Case Realizations ..............................................................................................................................14We talk about return scenario; Member returns the book to librarian, the system will validate themember and the item that is issued, get return the book calculate the fine and update the database. Return isconnected to member, means member will return the item(book) to librarian. There is a relationship between issue and return, return and calculate fine. It is an extends relationship. It means member will haveto return the book after issuing, but there is a possibility that he/she does not return the book. That is whythere is an extend relationship. After returning the book librarian calculates the fine if there is a latesubmission fine will be added into the account of the member. Here return is specific use case that isgeneralized by issue use case. It means return is using some properties of issue operation..........................147.0 User Interface Design: NA .......................................................................................................................158.0 Help System Design: NA ..........................................................................................................................151
 
1.0. Introduction
1.1. Purpose and Scope
The purpose of this Design Document is to present the system design at alevel that can be directly traced to the specific system objective along withproviding more detailed data, functional, and behavioral requirements. ThisDesign Document will verify that the current design meets all of the explicitrequirements contained in the system model as well as the implicit requirementsdesired by the customer.
1.2. Glossary 
LMS – Library management system
SRS – Software requirements specification
PC – Personal Computer 
HDD - Hard Disc Drive
RAM – Random Access Memory
ISME – International school of management excellence
IE – Microsoft Internet Explorer 
SQL – Structured Query Language
RD – Requirements Documentation
DD – Design Documentation
1.3. References
2

Activity (133)

You've already reviewed this. Edit your review.
Mohamed Mafas liked this
Sirmajnr added this note
i love this, it has helped me clear my work as faster as i could not have imagined. thanks lol
Sirmajnr liked this
1 thousand reads
1 hundred reads
Habtamu Amare added this note
good document
Aya Yakout liked this
Aya Yakout liked this
Wendimu Baye added this note
It is nice documentation.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->