Library Management System



Library Management System

Detail Level Design Document

 

Version 1.0

 

 

Dated: 15th August, 2008

Authors

K. Sridharan

Revision History

|Date |Version |Description |Author |

|15th August, 2008 |1.0 |First version |Coding Team |

Table of Contents

|1. Introduction ……………………………………………………………………….. 3 |

| 1.1 Reference ………………………………………………………………………………………….. 3 |

|2. Programming platform ……………………………………………………………………… 3 |

|3. Database …………………………………………………………………………………………… 3 |

|4. Database tables ………………………………………………………………………………… 3 |

|5. Classes ………………………………………………………………………………………………4 |

| 5.1 Class diagram …………………………………………………………………………………. 4 |

| 5.2 Class design detail …………………………………………………………………………….5 |

|6. Activity diagrams/State diagram …………………………………………………………..7 |

| 6.1 Activity diagram of whole system …………………………………………………………7 |

| 6.2 Activity diagram of each operation ……………………………………………………….8 |

| 6.2.1 Student class ……………………………………………………………………………8 |

| 6.2.2 Book class ……………………………………………………………………………. 10 |

| 6.2.3 Transaction class …………………………………………………………………… 14 |

| 6.2.4 MyList class ……………………………………………………………………………16 |

1.                  Introduction

This document provides a detailed design of the system. Please refer to the requirement analysis document and high level design document for the overall view and high level design of the system. This document concentrates on the detailed design of the system, including database connection, programming platform, activities diagrams of whole system and each operation of each class.

 

1.1 References

Requirements Document Version 1.0

High level design Document Version 1.0

2. Programming platform

The system will be written in Java language. Thus our software is system-independent and can be run in both MS Windows and Unix system. During development process we will use the MS Windows system.

3. Database

The database being used is the DB2 database system, and the connection to the database is made by Java’s JDBC interface. The tables will be created using SQL statements; the runtime SQL will be sent to database and the query result will be sent back to application by JDBC connection.

4. Database tables

[pic]

5. Classes

5.1 Class Diagram

[pic]

5.2 Class Design Details

Student Class :

This class encapsulates all student related operations and details.

[pic]

Book Class :

This class encapsulates all Book related operations and details.

[pic]

Transaction Class :

This class encapsulates a single transaction, and maps a student to a book which has been checked out. All associated details of a transaction are also stored in this class (late fees, checkin, checkout dates).

[pic]

MyListClass :

This class encapsulates the usecases related to maintaing a temporary subset of user selected books during a search operation.

[pic]

6. Activity diagrams/State diagrams

6.1 State diagram of whole system

[pic]

6.2 Activity diagram of each operation

6.2.1 Student class

• AddStudent : add a new student

[pic]

• DeleteStudent : delete an existing student

[pic]

• UpdateStudent : update information of existing student

[pic]

• SearchStudent : search students

[pic]

• ValidateStudent : validate student

[pic]

2. Book class

addBook: Add a new book in database

[pic]

exist: Check if the book record already exist in database.

[pic]

searchBook: Search books in database

[pic]

updateBook: modify book info

[pic]

deleteBook: Delete a book in database

[pic]

3. Transaction class

checkIn() : check in one book

[pic]

checkOut() : check out one book

[pic]

4. MyList class

addTolist() : add one book to mylist

[pic]

deleteFromList() : delete one book from mylist

[pic]

Mylist.viewList() : retrieve books in mylist

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download