NATIONAL INSTITUTE OF BUSINESS MANAGEMENT

DIPLOMA IN SOFTWARE ENGINEERING 23.1

SOFTWARE ENGINEERING
COURSE WORK

Book Depot Pvt. Ltd system

Group Members:

KUDSE23.1F-018 Medagedara M G D
KUDSE23.1F-019 Rajapaksha R P K S
KUDSE23.1F-034 Jayasinghe J A D D
KUDSE23.1F-036 Senevirathne B R D M
KUDSE23.1F-060 Pathirana P O D

Supervised by:
R D H Dulshini Jayaratne
 Content

1) Introduction………………………………………………………………………………………3

2) Functional requirements…………………………………………………………………..4

3) Nonfunctional requirements…………………………………………………………….5

4) Domain requirements……………………………………………………………………….5

5) UML diagrams…………………………………………………………………………………..6

i. Use Case Diagrams

ii. Class Diagrams
iii. Sequence Diagrams

2
 1. Introduction
Book Depot Pvt. Ltd., a renowned bookshop, is expanding its operations by developing a web-
based application to efficiently manage its bookstore and library functions. This application
aims to seamlessly integrate operations between the bookstore, library, and a special
coordination office facilitating item transfers and purchases.

Overview

➢ Book Depot Pvt. Ltd:

▪ Well-known bookshop offering a diverse range of technical books, CDs, DVDs, and Blu-ray
discs.
▪ Manages a popular library with special discounts for members on purchases.

➢ Objective:
▪ Develop a web-based application for streamlined operations, integrating bookstore and
library functions.

System Highlights:

a. Functional Requirements:
• Comprehensive features for book acquisition, loan, return, reservation, inquiry, book
registration, and user registration.

b. Non-Functional Requirements:
• Emphasis on performance, security, and usability.

c. Domain Requirements:
• Integration with the coordination office and management of member discounts.

3
 2. Functional requirements

Book Acquisition Process:

• Quarterly compilation of recommended books by the academic consultant.

• Members can suggest books with valid reasons.
• Order placement through the coordination office.

Loan Process:

• Borrower checks out copies after clearance from the librarian.

• Overdue book clearance required before new loans.
• Payment handling by the payment clerk for overdue books.

Return Process:

• Copies returned at the counter, status checked by the librarian.

• Member informed if the copy is already received.

Reservation Process:

• Members can reserve up to 5 copies.

• Librarian accepts reservations based on copy status.

Inquiry Process:

• Librarian handles member inquiries about book availability.

• Member self-service for checking book availability.

Book Registration Process:

• Registration of new books and addition of new copies.

• Recording classification, titles, publisher, and copy details.

User Registration Process:

• Capture user details for registration, including user number, name, date of birth, ID card
number, and address.
• Membership levels: A (general public) and C (University students)
• Verification of student identity for university students
• Issuance of a printed letter for library usage

4
 3. Nonfunctional requirements

Performance:
• Emphasis on efficient operations, quick response times.

Security:
• Secure handling of user and transaction data.

Usability:
• User-friendly interface for both library and bookstore operations.

4. Domain requirements

Integration with Coordination Office:

• Facilitates item transfers and purchases between the library and bookstore.
• Manages member discounts through coordination office integration

5
 5. UML Diagrams

i. Use Case Diagrams

ii. Class Diagrams
iii. Sequence Diagrams

i. Use Case Diagrams

6
Assumptions:

• The coordination office ensures effective communication between the librarian and
academic consultant.
• The librarian has the authority to accept or cancel borrowing requests.
• The payment clerk is involved only if there are fine fees.
• The librarian updates the system promptly and notifies the borrower about the status
of the returned copy.
• The librarian's decision to accept or reject reservations is based on the availability of
copies.
• The librarian provides accurate and up-to-date information about book availability.
• The librarian accurately records book details during the registration process.
• The librarian captures and maintains accurate information about borrowers.
• Assumes the librarian follows different registration procedures for general public and
university students.
• The customer receives a detailed invoice for purchased items.
• Assumes the payment clerk manages transactions.

7
 ii. Class Diagrams

Assumptions:

• Library management is working under special co-ordination office, cannot exist alone.
• Library can exist alone without book company.
• There can be many payment clerks are working.
• Book depot can be operated without consultant.
• Library can be operated without consultant.
• Has Only one consultant for the company.
• No existence for the company without customers/members.
• Library cannot operate without members.
• Payment clerk cannot exist without company.
• Has only one special co-ordination office and it cannot operate without company.

8
 iii. Sequence Diagrams

Loan Process

Purchase Process