- Chained Stores System Design Report
Chained Stores System Design Report
According to the system requirement description, the aim of this
project is to design a simple distributed system for chained
electronic appliance shops. The system is supposed to be able to
maintain stock information as well as customer information.
Shopkeepers can access the stock information including name, type,
model number as well as the availability of the products. And they
can also add new customer, search a customer by the customer name
and add new sales information to the existing customers' purchase
history. And the most important thing is that shopkeepers can
access data from other branches' computers.
In the remainder of this report, chapter 2 will show a
description of the system architecture including the model I chose
and the components of the system. Chapter 3 will talk about the
design of the proposed system including textual description and UML
diagrams. Chapter 4 is to point out some further issues in
implementing this system. And the final chapter is to summarize and
conclude this report.
- The security issues in this architecture will be resolved by
providing secure transactions. The customers will be provided with
the unique username and password which will make them authenticate
- Because of the online screen help and easy simple FAQs most of
the faults and queries will be easily solved by the users of the
- The new architecture is an extension and enhancement to the
legacy system. So, the implementation of the new system will
definitely will resolved the usage of the legacy system.
This report has briefly discussed the design of the proposed
chained stores system. At the beginning of the report, a textual
description of the system requirement analysis has been shown. And
then the use cases of the system have been introduced by some
textual description and a use case diagram. And then the system
architecture, which is client/server architecture, has been
illustrated with a system architecture diagram. The later chapter
has included description of system components and design of
classes. Finally, some suggestions and recommendations have been
given out in chapter 4.
From this course work, I have understood the concept of
distributed systems as well as some issues of how to build a