Document

Document Sample
Document Powered By Docstoc
					          FPT-APTECH COMPUTER EDUCATION




eProject Document
   Library Management System

                Bamboo Group
                Nam Phuong Tran - A03916 - 684
Group Member Hoang Phu Do - A03933 - 1689
                Minh Hoang Duong - A03969 - 5597
     Instructor Tu Ngoc Nguyen
         Batch HDSE
     Semester 2|4




                 - Hanoi, 06/2010 -
FPT – Aptech Computer Education                                                           eProject Document

    Table of Contents
    1.     Introduction ............................................................................................................ 4
    2.     Problem Definition................................................................................................. 4
         2.1.    Problem Abstraction ........................................................................................ 4
         2.2.    The Current System ......................................................................................... 4
         2.3.    The Proposed System ...................................................................................... 4
         2.4.    Boundaries of the System................................................................................ 4
         2.5.    Development Environment ............................................................................. 4
           Hardware ................................................................................................................ 4
           Software ................................................................................................................. 5
    3.     Requirements and Business Flow .......................................................................... 5
         3.1.    Customer Requirement Specification.............................................................. 5
           Manage Employee ................................................................................................. 5
           Manage Book ......................................................................................................... 5
           Search ..................................................................................................................... 6
           Check-in, Check-out book ..................................................................................... 6
         3.2.    Activity Diagram ............................................................................................. 7
           Login: ..................................................................................................................... 7
           Manage Book: ........................................................................................................ 8
           Manage Employee: ................................................................................................ 8
           Manage User: ......................................................................................................... 9
           Check – in Book: ................................................................................................. 10
           Check – out Book: ............................................................................................... 11
           Search:.................................................................................................................. 12
         3.3.    Use Case Diagram ......................................................................................... 13
         3.4.    Use Case Specification .................................................................................. 14
         3.5.    Other Concerns<Optional> ........................................................................... 15
    4.     Design .................................................................................................................. 16
         4.1.    System Architecture ...................................................................................... 16
         4.2.    Class Diagram ............................................................................................... 16
         4.3.    Class Diagram Explanation ........................................................................... 17
         4.4.    Sequence Diagram (Optional) ....................................................................... 17
         4.5.    Collaboration Diagram (Optional) ................................................................ 17
         4.6.    State Diagram (Optional) .............................................................................. 17
         4.7.    Entity Relationship Diagram ......................................................................... 17
         4.8.    Database Design ............................................................................................ 18



    Bamboo                                                         Page 2                       CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                                                          eProject Document
         4.9.      Algorithms (optional) .................................................................................... 18
         4.10.        Others (optional) ........................................................................................ 18
    5.      System Prototype ................................................................................................. 18
    6.      Management and Project Planning ...................................................................... 18
         6.1.      Management Approach ................................................................................. 18
         6.2.      Project Plan ................................................................................................... 18
         6.3.      Task Sheet ..................................................................................................... 19
         6.4.      Meeting Minutes (Optional) .......................................................................... 19
    7.      Checklists ............................................................................................................. 19
         7.1.      Check List of Validation ............................................................................... 19
         7.2.      Submission Checklist .................................................................................... 19
    8.      Screenshots .......................................................................................................... 19
    9.      Coding Convention .............................................................................................. 19
    10.         Other Concerns<Optional> ............................................................................... 19
    Appendix ...................................................................................................................... 20
         Glossary [Optional] .................................................................................................. 20
         References [Optional] .............................................................................................. 20
         Others<Optional> .................................................................................................... 20




    Bamboo                                                         Page 3                      CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                              eProject Document

    1. Introduction
    This document contains the entire library management project. It is organized into
    categories such as Problem Definition, Requirements and Business Flow, Design,
    System Prototype, Management and Project Planning, Checklists, Screenshots,
    Coding Convention…

    2. Problem Definition
    2.1. Problem Abstraction

    Mohan Ltd. has a library which is managed by Ms. Monica manually. All records are
    on paper and Monica finds it very difficult to manage when somebody issues
    or returns the books. She has to maintain list of books along with details such
    as Author name, book title etc. When a book is to be issued, she has to
    manually search for that book and again for issuing book she has to maintain a
    register which will have details of book issued such as Name of the book, Author,
    Employee details (name, department etc) , Date of issue, Date of return, etc. This
    process is tedious and time consuming. She has brought it to the notice of her seniors
    and they have proposed the solution of developing a system which will help Monica
    managing the things more effectively and also save her time. She will be the only
    user of the system.

    2.2. The Current System
          The library is managed manually.
          All records are on paper.
          The librarian has to maintain list of books and employee along.
          The librarian has to search manually.
          It is very difficult to manage when somebody issues or return the books.
          The process is tedious and time consuming.

    2.3. The Proposed System
          A system will operate automatically.
          All data are digitalized.
          The system will have some tools which help the librarian managing books,
           employees, searching books, employees, and check-in, check-out books.
          The process is fast and comfortable.

    2.4. Boundaries of the System
    The system has only one user who is the librarian of the library.


    2.5. Development Environment
    Hardware
          A minimum computer system that will help you access all the tools in the
           courses is a Pentium 166 or better


    Bamboo                                    Page 4             CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                            eProject Document
          128 Megabytes of RAM or better


    Software
          Java Virtual Machine/ J2EE server
          Notepad/Java editor
          j2sdk1.4.1_02 (or later)

    3. Requirements and Business Flow
    3.1. Customer Requirement Specification
    Depending on the decision taken to computerize the entire operation of library
    management, a system is to be developed based on the following requirements.

    Manage Employee
       1. Add employee record. Each employee should have following attributes:
           Employee ID (unique)
           Name
           Address
           Phone Number
           Department
       2. A unique system ID would also be generated internally for each employee.
       3. Update/Delete an employee record
           The record would be selected using employee ID
           The record can be deleted if there are no books issued by user.

    Manage Book
       4. Add a book item. Each book should have following attributes:
           Call Number
           ISBN/Name of book
           Title
           Author name
       5. The call number format to be adopted would be as follows:
           (First 2 alphabets of title)-(first 2 alphabets of author)-sequence number of
              book
           XX-XX-NNN
       6. The ISBN number format to be adopted would be as follows:
           (Numeric code for subject)-(sequence number)
           NNN-NNNN
           It would be unique for each specific title/author combination
       7. Author name shall support 30 character names
       8. Title shall support 100 character names.
       9. Update/Delete a book item.
           The book can be retrieved using the call number
           The data items which can be updated are:
                  a. ISBN
                  b. Title


    Bamboo                                  Page 5             CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                             eProject Document
                 c. Author Name
      10. The book can be deleted only if no user has issued it.

    Search
      11. Query the database
           The system shall let librarian query book’s detail information by their
             ISBN number or Author or Title.
           The search result would also produce a list of books, which match the
             search parameters with following Details:
                 a. Call number
                 b. ISBN number
                 c. Title
                 d. Author
           The display would also provide the number of copies which is available for
             issue.
           The display shall provide a means to select one or more rows to a user-list
           A detailed view of each book should provide information about check-
             in/check-out status, with the borrower’s information.
           The search display will be restricted to 20 results per page and there
             would be means to navigate from sets of search results.
           The user can perform multiple searches before finally selecting a set of
             books for check-in or check-out. These should be stored across searches.

    Check-in, Check-out book
      12. Check – Out a book
           Librarians can check out a book using its call number
           The checkout can be initiated from a previous search operation where user
             has selected a set of books.
           The student ID who is issuing the book would be entered
           The issue date would automatically reflect the current system date.
           The due date would automatically be stamped as 5 days from current date.
      13. Check –in a book
           Librarians can check in a book using its call number
           The check-in can be initiated from a previous search operation where user
             has selected a set of books.
           The return date would automatically reflect the current system date.
           Any late fees would be computed as difference between due date and
             return date at rate of 10 cents a day.
      14. Display book detail.
           This view would display details about a selected book from search
             operation
           The details to be displayed are:
                 a. Call number
                 b. ISBN
                 c. Title
                 d. Author
                 e. Issue status (In library or checked out)
                 f. If book is checked out it would display


    Bamboo                                  Page 6             CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                          eProject Document
                g. User ID & Name
                h. Checkout date
                i. Due date
      15. View Employee details
           Librarian can select a user record for detailed view
           The detail view should show:
                a. User name, ID, Address & Phone number
                b. The books issued by user with issue date, due date, call number,
                    title
                c. Late fees & Fines summary and total

    3.2. Activity Diagram
    Login:




    Bamboo                                Page 7             CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education     eProject Document
    Manage Book:




    Manage Employee:




    Bamboo                 Page 8    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education     eProject Document
    Manage User:




    Bamboo                 Page 9    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education      eProject Document
    Check – in Book:




    Bamboo                 Page 10    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education      eProject Document
    Check – out Book:




    Bamboo                 Page 11    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education      eProject Document
    Search:




    Bamboo                 Page 12    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education       eProject Document

    3.3. Use Case Diagram




    Bamboo                  Page 13    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education                             eProject Document

    3.4. Use Case Specification

    USE CASE SPECIFICATION

    Use-case No.             UC001                   Use-case          1.0
                                                     Version
    Use-case Name            Library Manager System
    Author                   Hoang Phu Do, Nam Phuong Tran
    Date                     15/06/2010              Priority   High
    Actor:
             Librarian, Administrator

    Summary:
          Login, Logout, Search Book, Display Book Result, Search Employee, Display
    Employee Result, Check-in, Check-out, Add Book, Update Book, Delete Book, Add
    Employee, Delete Employee, Update Employee, Add User, Update User, Delete User.
    Goal:
              o Add Book, Update Book, Delete Book: manage Book.
              o Add Employee, Update Employee, Delete Employee: manage
                 Employee.
              o Add User, Update User, Delete User: manage User who using the
                 system.
              o Search Book, Search Employee: help the librarian in searching Book
                 and Employee.
              o Check-in, Check-out: Check-in book, Check-out book.

    Triggers

    Preconditions:

    Post Conditions:

    Main Success Scenario:


    Alternative Scenario:

    Exceptions:

    Relationships:

    Business Rules:




    Bamboo                                 Page 14              CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education         eProject Document

    3.5. Other Concerns<Optional>




    Bamboo                    Page 15    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education          eProject Document

    4. Design
    4.1. System Architecture




    4.2. Class Diagram




    Bamboo                     Page 16    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education             eProject Document

    4.3. Class Diagram Explanation


    4.4. Sequence Diagram (Optional)
    4.5. Collaboration Diagram (Optional)

    4.6. State Diagram (Optional)


    4.7. Entity Relationship Diagram




    Bamboo                      Page 17      CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education            eProject Document

    4.8. Database Design




    4.9. Algorithms (optional)
    4.10. Others (optional)

    5. System Prototype

    6. Management and Project Planning

    6.1. Management Approach


    6.2. Project Plan




    Bamboo                       Page 18    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education               eProject Document

    6.3. Task Sheet


    6.4. Meeting Minutes (Optional)


    7. Checklists

    7.1. Check List of Validation

    7.2. Submission Checklist

    8. Screenshots
    9. Coding Convention
    10. Other Concerns<Optional>




    Bamboo                          Page 19    CONFIDENTIAL11/20/2012
FPT – Aptech Computer Education       eProject Document

    Appendix

    Glossary [Optional]


    References [Optional]


    Others<Optional>




    Bamboo                  Page 20    CONFIDENTIAL11/20/2012

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:11/21/2012
language:Latin
pages:20
 
http://www.docstoc.com/docs/136626316/Document
www.docstoc.com
crawl=CC-MAIN-2014-10
69067
application/http; msgtype=response
sha1:XISFNEFCBBAQCG3BG2AFNJ23GZ6UBVBJ
<urn:uuid:5ed83498-5953-45b5-979f-2f386167eac2>
2014-03-08T00:38:45Z
72.172.88.41
sha1:VYQ5LFUJKF3WXQV7ZQSRGZQLV7664L4R
<urn:uuid:8d6d6d3a-abe4-4879-b763-a27ae4e349d8>
http://www.docstoc.com/docs/136626316/Document
response
<urn:uuid:ef7847c2-a03e-47a2-82b0-a11461be67fc>
robots: classic
hostname: ip-10-183-142-35.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-10
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for March 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf