Booktopian Project: Applying OO Methodology for System Design

This project provides a comprehensive analysis of the Booktopian system using the object-oriented (OO) methodology. The assignment begins with requirements gathering, outlining the owner's and user's perspectives, detailing system users, and defining various use cases, including membership, book sales, and exchange. The project then delves into domain analysis, defining the scope of different domains like new books, exchange books, and membership, along with domain concepts and a domain dictionary. Behavioral modeling is addressed through stakeholder identification, a use case summary, and a detailed use case template for book exchange. The project also includes use case diagrams, activity diagrams, and structural and dynamic modeling, with a class diagram and sequence diagrams. The solution covers various aspects of the Booktopian system, from conceptualization to design, providing valuable insights into the application of OO principles.

Title: Booktopian using the OO methodology

Table of contents:
1. Requirements Gathering
2. Domain Analysis
3. Behavioral Modeling
4. Structural and Dynamic modeling
5. References

1. Requirements Gathering
1.1 Owner’s view
This phase of the complete assignment is provides the owner’s view for complete
Booktopian system. The owner’s view is created to show it to the stakeholders for
their feedback about the complete organization named as Booktopian. The
Booktopian is an organization which is dealing with the books the user’s view
description about the Booktopain for stakeholders are described as follows:
There are defined different use cases of Booktopian organization to present the
complete business towards the stakeholder.
 Booktopian organization sales and exchange books.
 This organization also arranged the book fair events.
 The organization also has a online website that perform multiple operations.
 The users can take the membership by which they can add their books,
make online orders or book and also can exchange the books with other
users.
 The Booktopian take commission of 20% from book sales and membership
fee of 100$ this is the complete fund that is used by the Booktopian to pay
manager’s salary, website service, book fair event organization, accounting
service.
 The Booktopian is continuously trying to update their system in different
fields.
Thus this is the complete owner’s view to represent the Booktopian to the
stakeholders for their feedback.
1.2 List of system users
There can be different users of Booktopian online website one is member user who
own the membership, guest user, manager. Each user can perform a number of
operations which are given as follows:
Users Name Task
1. Membership 1. Access the system
2. Make book exchanges.
3. Book fair even cast and credit
card sales
4. Update online inventory
5. Maintain delivery service
6. Endorsing other members
2. Guest user 1. Order book
2. Access system

3. Get delivery
3. Manager 1. Manage membership
2. Update book fair event
information.
3. Deals directly with website
service provider.
4. Accounting and financial
services
5. Approve membership
2. Domain Analysis
2.1 Domain definition
The Booktopian has a huge range of domain including in many fields such as new
books selling, exchange book domain, membership domain. There are described
each domain with their scope.
Domain Scope Outline
1. New books The Booktopian organization can start
dealing with different types of new
books such as comics, political books,
novel, and technical books.
2. Exchange Books The Booktopian can further expand
their business with the used books also.
They can provide this facility to the
people who are not financially able to
deal with purchasing of new books.
3. Membership The organization can start some
different types of members in various
rate to provide proper funding to the
organization
2.2 Domain concepts
There are defining some domain concepts as per the domain definition given for the
Booktopian organization. There are defined domain concepts including the process,
functions, rules, objects and the business rules in the domain dictionary.
Booktopian

Domain dictionary
Name Type Description
Selling Sales The Booktopian will sell
their books to the users or
other clients.
Purchase Sales The member users or
guest users will purchase
the books.
Exchange Sales The members or guest
users can exchange books
as per the price with each
other.
Membership membership The users can register
their membership
3. Behavioral Modeling
3.1 Stakeholder List
Booktopian
Stakeholders & Actors
Name Description
1. Members The member can be the stakeholder of
the system it can endorse another
member also.
2. Investors The organization may have some
investors which can provide fund to the
business and then take business profit.
3. Owner The organization owner will be the
stakeholders or actors of the system
who will provide the complete initial and
further support to the system.
4. Government The government can be a stakeholder
which can support the business to
support the business idea.
3.2 Use case summary
Booktopian
Use case summary
Id Name Description Actor

1. Apply for
membership
The guest user or non member
user will apply for membership
User
2. Approve
membership
The manager of the system will
approve the user’s membership
request
Manager
3. Update book fair
event information
The manager will update the
upcoming book fair event
information on the online
website
Manager
4. Make new book
order
The user and the member will
make the order to purchase
new book via system.
Member,
guest user
5. Update online
inventory
The members will update the
inventory via system
members
6. Endorse other
member
The members who has
membership can endorse
another member
member
7. Make payment The users and member both
will make the payment for
membership or book
purchasing.
Member,
guest user
8. Exchange book Multiple members will
exchange the book with each
other by exchanging the credit.
Member
9. Renew membership The member will renew their
membership after expiration
Member
Thus these are some major use cases of Booktopian organization which are listed as
above.
3.3 Use case template
There are described a complete use case template for a use case that is related to
the member acquiring a book via exchange the credits. There are described the use
case template in tabular form.
Use Case: Exchange the books
ID: 8
Scope: The scope of exchange of books is not
limited to the new book and it can be
done for the used books also.
Priority: As per the financial requirement of user.
Summary: The multiple members in the system of
Booktopian will exchange the books

with each other via exchanging the
credits.
Primary Actors: Members user
Supporting Actors: Manager
Stakeholders: Members
Generalization: The process will be from selection of
exchanging to the customers feedback.
Include: The books must have a type
Extend: The user must be from an members list
Precondition: The credits must have the equal value
Trigger: Choose the option of exchange instead
of new order.
Normal Flow: The members or other user will access
the system and then match the credits
of books for exchanging.
Sub flows: The matching of credits of both
exchanging books.
Alternate flow: There may be an unsuccessful exchange
due to the credits.
Post Condition The member’s feedback is noticed after
the exchange.
Non behavioral Requirement The type of exchanging books.
Open Issues The individual party may be unsatisfied
form the exchange.
Source: Members Book’s account
Author: Member
Revision & Date Revised & 17 May 2018
3.4 Use case diagram

3.5 Activity Diagram

4. Structural and Dynamic modeling
4.1 Classes of Booktopian
There are described a list of classes in the Booktopian system.
Booktopian
Preliminary Class candidates
Class Responsibilities Use cases
Guest User To purchase any new
order.
The guest user will
purchase the new book or
exchange the book.
Order Contain the details about
all orders.
This class maintains the
complete new order or
each type or in details
Manager Manage different types of
operations such as
membership, website
service etc.
The manager will approve
membership
Member The member will make
new order, add book, edit
book and remove book
The member will make
new order, exchange
book.

4.2 Class diagram
There are not exist any relationship between the case study which can be defined
by the aggregation or composition and generalization or specialization besides this
classes are connected with each other via association relationship.
4.3 Sequence diagram

5. References
Kindleer, E. Krivy, I. (2011). Object oriented simulation of systems with the sophisticate
control. International Journal of General systems.
Lewis, John, Joftus, Wiliam. (2008). Software solutions. Pearson Education Inc.
John C, Mitchell. (2003). Concepts in programming languages. Cambridge University
Press.