Chapter 3

Modules of the proposed system

Module 2: Login
Here customers and admin can verify their account details.

Module 3: Admin
Admin can add, update or delete the products. The admin can also confirm the payment
and make sure that the orders are delivered on time.

Module 4: Products
It contains the details of all the products available. It also shows whether a product is in
stock or not.

Module 5: Shopping Cart

Module 6: Order
Here customers can add details on their address for ordering the product.

Module 7: Payment
Customers can choose their mode of payment here.
 Gantt chart
No. of Tasks:-
(1) Planning
(2) Estimating Schedule
(3) Gathering Information and Requirements
(4) Designing the Project
(5) Documentation
[Link]
 ERD
ER Diagrams are composed of entities and attributes. They also depict cardinality, which
defines relationships in terms of numbers.
(1) Entity:- A definable thing—such as a person, object, concept or event—that can have
data stored about it. Think of entities as nouns.
(2) Attribute:- A property or characteristic of an entity.
(3) Cardinality:- Defines the numerical attributes of the relationship between two
entities or entity sets. The three main cardinal relationships are one-to-one, one-to-
many, and many-many.
 Use case
The Diagram Symbols and Notations used in this Use Case Diagram are:-
(1) Use cases: Horizontally shaped ovals that represent the different uses that a user
might have.
(2) Actors: Stick figures that represent the people employing the use cases.
(3) Associations: A line between actors and use cases. It is important to know which
actors are associated with which use cases in complex diagrams.
(4) System boundary boxes: A box that sets a system scope to use cases. All use cases
outside the box would be considered outside the scope of that system.
 Sequence diagram
In the following Sequence diagram the following icons and elements are used:-

(1) Object Symbol:- Represents a class or object in UML. The object symbol
demonstrates how an object will behave in the context of the system. Class attributes
should not be listed in this shape.
(2) Activation Box:- Represents the time needed for an object to complete a task. The
longer the task will take, the longer the activation box becomes.
(3) Lifeline Symbol:- Represents the passage of time as it extends downward. This
dashed vertical line shows the sequential events that occur to an object during the
charted process. Lifelines may begin with a labeled rectangle shape or an actor
symbol.
(4) Synchronous message symbol:- Represented by a solid line with a solid arrowhead.
This symbol is used when a sender must wait for a response to a message before it
continues. The diagram should show both the call and the reply.
(5) Reply message symbol:- Represented by a dashed line with a lined arrowhead, these
messages are replies to calls.
(6) Delete message symbol:- Represented by a solid line with a solid arrowhead,
followed by an X. This message destroys an object.
 Class Diagram
The basic components used in Class Diagram are:-
(1) Upper section: Contains the name of the class. This section is always required,
whether we are talking about the classifier or an object.
(2) Middle section: Contains the attributes of the class. We use this section to describe
the qualities of the class.
(3) Bottom section: Includes class operations (methods). They are displayed in list
format, each operation takes up its own line.
 Deployment diagram
Components used in this deployment diagram:-
(1) Node: A hardware or software object, shown by a three-dimensional box.
(2) Node as container: A node that contains another node inside of it—such as in the
example below, where the nodes contain components.
(3) Component: A rectangle with two tabs that indicates a software element.
(4) Association: A line that indicates a message or other type of communication between
nodes.
 Component diagram
Components of a Component Diagram are as following:-
(1) Component Symbol:- An entity required to execute a stereotype function. A
component provides and consumes behavior through interfaces, as well as through
other components.
(2) Node Symbol:- Represents hardware or software objects, which are of a higher level
than components.
(3) Dependency Symbol:- Shows that one part of your system depends on another.
Dependencies are represented by dashed lines linking one component (or element)
to another.
(4) Required interfaces: A straight line from the component box with an attached half
circle (also represented as a dashed arrow with an open arrow). These symbols
represent the interfaces where a component requires information in order to
perform its proper function.
 Data Flow Diagram
The symbols that depict the components of Data Flow Diagrams are as follows:-
(1) External entity: An outside system that sends or receives data, communicating with
the system being diagrammed. They are the sources and destinations of information
entering or leaving the system. They might be an outside organization or person, a
computer system or a business system. They are also known as terminators, sources
and sinks or actors. They are typically drawn on the edges of the diagram.
(2) Process: Any process that changes the data, producing an output. It might perform
computations, or sort data based on logic, or direct the data flow based on business
rules. A short label is used to describe the process.
(3) Data flow: The route that data takes between the external entities, processes, and
data stores. It portrays the interface between the other components and is shown
with arrows.