Preliminary Report: IS2 - Full Online Shopping System Design Analysis

This report provides a preliminary analysis of a full online shopping system, focusing on its design and development. It begins by comparing structured and object-oriented approaches, highlighting the advantages of the object-oriented approach for this system. The report outlines functional and non-functional requirements, including customer and product data storage, security, and system availability. It then explores conceptual models, use cases, and diagrams like context diagrams, DFDs, and ERDs. The report also discusses the system's objectives, maintainability, and technology choices such as Java, Tomcat, and MySQL. Furthermore, it covers APIs, requirement gathering techniques (interviews, JAD, questionnaires, prototyping), vendor selection, and the unified software development process. The report concludes by comparing structured and object-oriented approaches and emphasizes the benefits of object-oriented principles and UML in system development.

PRELIMINARY REPORT: LIMITED ANALYSIS AND COMMENTS ON DESIGN
1. IS2: Full Online Shopping System
1.1
Structure approach to system analysis and design mainly work on processes and on logical
structure. After that data is required for the processes. It is basically follow the top to down
approach. It has fixed specifications. It uses a list of instructions to get work completed. In this
process programs are divided in to various small processes. It has more function dependencies as
well as less reusability properties. Structure approach have also less flexibility in nature. Data
hiding facilities is also not available in this approach.
Whereas in object oriented approach all the works are mainly depend
upon data. It divides the whole requirements in to object which carries the methods and data
togather. It follows the bottom to top approach. It has properties of data encapsulation as well as
polymorphism. It has more reusability and have less function dependencies properties. Here in
online shopping system design we are going to use the object oriented approach. Object oriented
approach can solve any complex program as well as having data hiding feature. Oops is more
famous than structure approach it provide facilities of dynamic binding and multi-threading as well
as objects,class etc.
1.2
The most general approach in SDLC is structure approach which is based upon waterfall model. It
follow step by step process to complete the phase. In this we see that work of one phase must
completed before moving to another one. Planning, analysis, design and implementation are the
main phase of structure approach. It uses set of diagram which repersent functionality of system is
mainly termed as DFD. Whereas in object oriented approach have several phases like inception,
elaboration, construction and transition. It has no logical process for SDLC . During iterartion it
repeated every phases. In this approach we uses different models to repersent the different
functionality of the system is also known as UML (unified modeling language). This process follow
mainly increamental and iterative approach for the development of the system.
(Waterfall Method)

(Iterative and Incremental Model of SDLC )
1.3
Functional Requirements for online shopping system
a) Stores the record of customers on daily basis
b) Stores the records of products available
c) Stores the record of daily sell and feedback provides by the customer
d) Update or stores the details of deliverable products.
e) Keep the product in temporary storage which is selected by the customer
Non Functional Requirements for online shopping system
a) Secure access of customer confidential details.
b) 24 * 7 online system availability
c) Design of better component and architecture for flexible service
Various other non-functional requirements are reusability, extensibility as well as application
compatibility and utilization of resources.
1.4
(Conceptual Model )

1.5
use case for the scenario Customer checking out and paying for their basket.
1.6
( Context Diagram )

1.7
Admin Side ( 1st level DFD)

1.8
(ERD)
1.9

1.10
1.11

1.12

1.13

1.14
2.1
As
we
know

that the main aim of developing this online system is to provide or fullfill the requirements of
customers according to their needs and stores the valuable information in such a manner so that they
can access it easily. The main idea behind the online shopping system is to manage all the details of
customer and their shopping details as well as product details. Its help in tracking all the details
which are used mainly during online shopping like payment, delivery and about product etc. It also
going to help in monitoring the required information and information about the payment. Due to
proper resource management of shopping system help in improving editing, updating and adding
new records . It helps in collecting perfect management in details. The old manual system is very
complex . During the primary phase the system is going to design at block level. The block are
created according to the need of of problem. Here we can see that user interface design is mainly
develop between user and the computer.
2.2
The online shopping system should be developed in such a manner so that changes can be made
easily in the system either for fixing problem or for adding new features to the system. Its
maintainability is very user friendly. It should be portable to various operating environments
available. It should be able to protect and store the transactions records very safely. It should be
developed in such a manner so that it can be easily reused. Java and other web technologies should
be used for development of the website. Apache’s Tomcat Web-Server should be used to install the
application. Whereas MySQL should be used as the database. whole documents delivered should
compatible to the IEEE standards for software engineering.
2.3
API is an acronym for application programming interface. It helps in allowing two application to
converse with each other. It is also described as connectivity interface to an application. As we see
that modern API are more developer friendly as well as easily maintain and understood. It is
designed for the use of specific peoples . They are very high statndards of uses so that they more
secure and have high maintainance as well as life cycle. The modern API has its own software
development life cycle which consists of designing , testing, building, managinging as well as
versioning. We can also see that, the modern APIs are documented in a good manner for the
consumption and versioning.
MEMORANDUM TO BOARD OF DIRECTORS
3.1
As we know that it is very hard to make a solution of anything in which you dont know about the
requirements. In todays world there are so many techniques available for the requirement gathering.
There are so many cases in which we have to use multiple techniques to get a common picture from
different type of stakeholders and clients. Following are the main requirements gathering process
used nowadays worldwide :

a) By going one to one interviews with the clients and ask them what they actually need in their
project. To uncover the requirements we have to talk with the clients in a very detailed and
informative manner.
b) By doing group interviews which is similar to one to one interviews but here more than one
person is going to be interviewed. It uncover greater part of requirements in limited period of time if
we are well prepared for asking the requirements from different type of people at the same time.
c) By doing JAD(Joint Application Development) in which all the clients or participants stay in a
specific period of time until they got a complete set of requirements which are agreed and mutually
documented.
d) By going for questionnaires round we gather the requirements of remote locations from the
clients or stakeholders.
e) By going for prototyping which is very modern technique we give the clients or stakeholders
already prepared gather requirements. Where it can be added by the additional requirements again
by the clients or stakeholders. This process repeated until the satisfaction of both sides.
3.2
The selection of vendors is very tough process when you are about to start. When we start to gather
the required information by performing interviews and making a team we have to first select
specific vendor for specific product. Here not every vendor able to provide all the requirements but
which vendors provide more requirements information then he will be selected. The main work of
vendor team is to choose the right software application through which they gather more
requirements information. The first work of this team is to get the information about high features
of software system and gather additional information from the clients and stakeholders. The very
common mistakes which people do during vendor selection methods is design the system instead of
explaining the needs of the business. The final process of vendor selection process is making a
contact negotiation stratgey.
3.3
The unified software development process is not just a simple process but it has large framework
which is specially developed for specific clients or stakeholders. It is an incremental in nature.
Transition, construction and elaboration are different phases in this iterations. The most important
things about this process is architecture baseline which is executable and created during the phase
of elaboration. Testing techniques mainly used to make different approches and startegies to test the
specific product about their fitness for purpose and to check compatibility. System testing mainly
done for testing the complete system to check the errors and their bugs. In acceptance testing last
phase of functional software testing is done which confirms that all the requirements of the product