Database Design for E-commerce System

This assignment focuses on designing a relational database schema for an e-commerce system. The schema must include tables for Orders, Suppliers, Customers, Order Items, and Shippers with appropriate attributes and relationships between them. The design should consider data integrity, efficiency, and scalability.

System Analysis And
Design

Contents
Contents................................................................................................................................................2
Introduction..........................................................................................................................................3
Extreme Programming.........................................................................................................................3
Core Values of XP................................................................................................................................3
Practices of XP.....................................................................................................................................3
Core Values of XP................................................................................................................................4
Communication................................................................................................................................4
Simplicity of the program.................................................................................................................4
Feedback of the customers...............................................................................................................4
Courage............................................................................................................................................4
Project Activities of XP in Comfort Quilts Limited.............................................................................4
Domain Model Class Diagram.............................................................................................................6
Design Class Diagram..........................................................................................................................7
Use Case Diagram................................................................................................................................8
Conclusion............................................................................................................................................9
References............................................................................................................................................9

Introduction
System development is the process of enhancing the features of the old system to make a new
system for the already undergoing business. Adaptive System development approach has some
methodologies, the company can adapt any methodology that suits their business operations. There
are three system methodologies like SCRUM, UP and XP to develop a new system. Adaptive
System development approaches make use of the types of iterations that permits the phases like
Analysis, Design and implementing the smaller portion of the application which is to be
implemented fully and also make evaluation of it. The company called Comfort Quilts plan which
focuses on selling the silk eiderdowns through online for their private people. They mainly focuses
on the transactions of the consumer. The adaptive system development methodology which is used
to focus on the consumer applications is XP (Extreme Programming). XP is advised for this
company to make their business to expand.
Extreme Programming
Extreme Programming (XP) is the adaptive system development methodology that is used for
the organization to make best practices for developing their system. The core values that are
followed by the extreme programming and the practices that are maintained by the extreme
programming are as follows (Satzinger, Jackson and Burd, n.d.).
Core Values of XP
 Communication
 Simplicity
 Feedback and
 Courage
Practices of XP
 Planning
 Testing
 Designing simply
 Code refractoring
 Collective code owning
 Integrating the operations continuously
 Metaphor of the system
 Standards of coding

Core Values of XP
Communication
Lack of Communication is considered as the important reason for the failure of any project.
Effective means of communication not only focuses on the documentation but also on the verbal
discussion of the key stakeholders and business executive people. This core value mainly
concentrates on the open and often communication occurence (Satzinger, Jackson and Burd, n.d.).
Simplicity of the program
The developers of the program have the opinion to keep solutions simple, but they did not
follow their opinion in the development. This simplicity is the principle followed by the Extreme
programming methodology (Satzinger, Jackson and Burd, n.d.).
Feedback of the customers
As the program is designed in a simple way, the users understand it easily. So that the user
give their feedbacks on the functions and needs of the system. Feedacks regarding the design and
code of the system should be employed with the developers of the program. If the client gets
satisfied, then they give positive feedbacks about the deliverables (Satzinger, Jackson and Burd,
n.d.).
Courage
The developers of the system requires courage to handle their choice of performing right
things or throwing the developed code away if it did not work. This core value of extreme
programming are made to provide courage to the developers of the system to "Do it Right"
(Satzinger, Jackson and Burd, n.d.).
Project Activities of XP in Comfort Quilts Limited
The extreme programming is divided into 3 different levels like System (The external ring),
Release (The middle ring) and the iterations (The inner ring) (Wood, Michaelides and Thomson,
2013). The newly developed system is being delivered to the system using different types of stages
called Releases. The company when releases the new model of Quilt, then it should make use of the
release stage like releasing their new designs and models to their business executive. Release stage
has many number of iterations. Each release has multiple iterations, so that the middle ring iterates
multiple times for each stage of the release. Once the iteration level is planned well, then the real
work of designing and modeling the quilt begins. When the first stage of the iteration gets passed
then next level of testing called integration testing is performed. Unit testing is the first satge of
release which test the features of the quilt one by one. For example first the colour of the quilt is
tested then the design of the quilt. Likewise, after completing the separate features are tested, the

integration testing is testing all the features of the quilt (Svanidzaitė, 2014). And then the
acceptance testing which test whether the user likes the model of the quilt. Then when the quilt has
demand and accepted in the markets, the acceptance testing gets completed. When the final testing
is passed, the quilt is ready to be released to the executive people of the program (Levine and
Walker, 2006). The development approach diagram of the extreme programming (XP) is
represented below (Satzinger, Jackson and Burd, n.d.).
Purchase details can be maintained by using the practice of XP known as planning and testing
phase (Okoli and Carillo, 2010). The purchase report has to be developed by specifying the order
date of the purchase, delivery date of the purchase. If there occurs any delay in the delivery, it
should be intimated to the customers in prior. The designing persons should follow some coding
standards for designing the quilt for their customers. It should be attractive for the customers to buy
the quilt atonce. They must keep track of the details of the purchase from their suppliers. If the
customers ordered some quilt, the company should arrange prior orders to their suppliers (Brighthub
Project Management, 2017).

Event Table
An event table is used to store the information about the modifications that happen in the
application table. The types of events associated with the system analysis are the external event,
temporal event and the state events.
Event Trigger Source Use Case Response Destination
Users see the
catalog of the
Quilt items
Inventory
Request
Customer Quantity of the
order gets
displayed
Web page
inventory
report
Customer
Sales Report
Documentation
End of the
month
Sales of the
month.
Producing the
monthly sales
report
Final monthly
sales report
Manager
Order Delivery Orders of the
month
Shipper Delivering the
customer order.
Final report of
the order
details.
customer
Customer
Feedback
Feedback
about the
delivered
quilts.
Customer Feedback
about the quilt.
Feedback
report of the
customer.
Company
Domain Model Class Diagram
Domain Class diagram is an object oriented model that is being implemented within the layer
that make use of the persistence from the lower layer and by publishing an Application Program
Interface it goes to the higher level layer. Here Company, Suppliers, Shippers and customers are
used as the classes. The separate tables are constructed for the classes and the attributes are defined
in the tables. Separate private key is provided for each table.

Order ID
Order Item Name
Quantity
Price
Supplier no
Supplier name
Order Id
Order item name
Quantity
Price
Comfort Quilts Limited
Customer-no
Customer-name
Customer-address
Customer-Phone
Supplier no & name
Supplier no & name
Customer no & name
Customer address & phone number
Order
Supplier
Customer
Shipper
Shipper No
Shipper Name
Order Id
Customer Id
Customer Name
Customer address
Customer phone number

Design Class Diagram
Design Class diagram is slightly similar to domain class model as the same classes are used
here also. This class diagram is derived from the collaboration diagram. The same classes and
Name:- String
No:- INT
Quantity:- INT
Order Date:- Date
Orders Supplier
Supp No:- INT
Supp Name:- String
Order No:- INT
Order Date:- Date
Quantity:- INT
Order Name:- String
Customer
Customer Name:- String
Customer No:- INT
Quantity :- INT
Order No:- INT
Customer Address:- String
Comfort Quilts Limited
Supplier No:-
Supplier Name:- String
Shipper No:- INT
Shipper Name:- String
Customer Name:- String
Customer No:- INT
Order No:- INT
Shipper
Shipper No:- INT
Shipper Name:- String
Customer No:- INT
Customer Name:- String
Customer Address:- String
Order no:- INT
Order Name:- String
Create ( ) : Order

attributes are used in the design class diagram.
Use Case Diagram
Customer Company
Shipper
Supplier
Use Case Description
Here the use case diagram is represented above. The actors of the use case diagram are
View Events
Transaction (bill
payment) through
Online
Customer Details
Order Details
Deliver
y
Cash
on
deliver
y
Order Details
Customer Details
Order
Details
Order
Delivery

company, supplier, shipper and customer. The use case that is being interacted with the actors are
order details, customer details and order delivery. The order details is sent from the customer to the
company, then company to the supplier, from company to shipper and finally delivering to the
customer.
Conclusion
The Company called Comfort Quilt Plan is taken for analysis. The report of this company
specifies the adaptive system development approach called Extreme Programming. The Extreme
programming (XP) is one of the methodology of the adaptive system development approaches that
is recommended t the Quilt company to make their business operations in an efficient way using
enhanced features. This methodology is found to be suitable as it focuses on the direct consumsers.
The core values, practices and the project activities of XP are specified in this report. The thing
about reporting and planning the purchase of the company is specified in this report. This is called
analysing the system and designing the system by adapting the suitable methodology for developing
the system of the company.
References
Brighthub Project Management. (2017). Understanding the Extreme Programming Life Cycle
Phases. [online] Available at: http://www.brighthubpm.com/methods-strategies/88996-the-
extreme-programming-life-cycle/ [Accessed 17 Oct. 2017].
Levine, D. and Walker, H. (2006). XP practices applied to grading. ACM SIGCSE Bulletin, 38(1),
p.173.
McKay, V. (2017). What is Extreme Programming? (XP) | Process Maturity | FAQ. [online]
Selectbs.com. Available at: http://www.selectbs.com/process-maturity/what-is-extreme-
programming [Accessed 17 Oct. 2017].
Okoli, C. and Carillo, K. (2010). The best of adaptive and predictive methodologies: Open source
software development, a balance between agility and discipline. [online] Available at:
http://chitu.okoli.org/media/pro/research/pubs/OkoliCarillo2010IJAESD.pdf [Accessed 17 Oct.
2017].
Satzinger, J., Jackson, R. and Burd, S. (n.d.). Systems analysis and design in a changing world.
Svanidzaitė, S. (2014). An approach to SOA development methodology: SOUP comparison with
RUP and XP. Computational Science and Techniques, 2(1).

Umsl.edu. (2017). Various approaches of systems analysis and design. [online] Available at:
http://www.umsl.edu/~sauterv/analysis/termpapers/f11/jia.html [Accessed 17 Oct. 2017].
Wood, S., Michaelides, G. and Thomson, C. (2013). Successful extreme programming: Fidelity to
the methodology or good teamworking?. Information and Software Technology, 55(4), pp.660-
672.