Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
7 views4 pages

CSC186 ProjectExample

The document outlines the KONAKUNI Bookstore Management System project, detailing its organizational structure, objectives, and scope. Key functionalities include storing customer and book information, calculating total purchases, and determining the highest demand type of book. The system features a UML class diagram and use case diagram, highlighting relationships between classes and the role of the administrator in managing the system.

Uploaded by

anisafiqah5c
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views4 pages

CSC186 ProjectExample

The document outlines the KONAKUNI Bookstore Management System project, detailing its organizational structure, objectives, and scope. Key functionalities include storing customer and book information, calculating total purchases, and determining the highest demand type of book. The system features a UML class diagram and use case diagram, highlighting relationships between classes and the role of the administrator in managing the system.

Uploaded by

anisafiqah5c
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

CSC186 – Project Example

KONAKUNI – BOOKSTORE MANAGEMENT SYSTEM

FRONT COVER AND TABLE OF CONTENT


1.0 ORGANIZATIONAL STRUCTURE

2.0 INTRODUCTION

3.0 OBJECTIVES

1. System can store all information for both customer and book.
2. System can calculate and display the total price of all purchases on 22nd July.
3. System can determine the highest demand type of book by displaying either “Digital
Book!”, “Physical Book!” or “Equal demand!”.

4.0 SCOPE

Class diagram
1. There are 4 classes; Customer, Book, Digital Book, Physical Book and Date. Class
Date is optional.
2. Customer and Book has a many-to-many relationship with aggregation link. It is a part
of relationship where Book is the whole and Customer is the part-of objects. Books
with same serial number and title can be purchased by many customers, no customer
at all and one customer only. This implies a relationship which part of object Customer
can still exist independently of the whole object Book.
3. Digital book and physical book are type of books. This implies inheritance relationship
where Book has general attributes; ISBN, title and quantity sold. Digital book has
unique attribute which is size of memory and date to determine discount for digital
awareness day while physical book has number of pages and hardcover or softcover.
4. Date and Digital Book has a one-to-one relationship with composition link. They are
dependent to each other.

Use Case diagram


1. Only one actor which is Administrator. Administrator either contract or permanent can
do the same process.
2. Processes;
a. Administrator can add information about customer.
b. Administrator can add information about book.
c. Administrator can update/edit customer’s phone number.
d. Administrator can calculate the total purchase price.
e. Administrator can calculate and display the total of price of all purchases on
22nd July.
f. Administrator can determine the highest demand type of book by displaying
either “Digital Book!”, “Physical Book!” or “Equal demand!”.

1
5.0 UML DIAGRAM

UML Class Diagram

2
UML Use Case Diagram

3
6.0 INPUT FILE

7.0 CLASS DEFINITION OF INHERITANCE, POLYMORPHISM AND RELATED CLASSES

8.0 CLASS APPLICATION

9.0 OUTPUT FILE OR/AND SAMPLE INTERFACES

10.0 REFERENCES

You might also like