Académique Documents
Professionnel Documents
Culture Documents
SOFTWARE REQUIREMENT
SPECIFICATION
• In software engineering a functional
requirement defines a function of a system or its
component.
• A function is described as a set of inputs, the behavior,
and outputs. Functional requirements may be
calculations, technical details, data manipulation and
processing and other specific functionality that
define what a system is supposed to accomplish.
• Behavioral requirements describing all the cases where
the system uses the functional requirements are
captured in use cases.
SOFTWARE REQUIREMENTS:-
1: Login
2: Validate
3: Display options
6: Response
7: Generate cart
13: Update
14: Logout
Collaboration Diagram
• A Usecase diagram is a diagram that shows a
set of use cases and actors and their
relationships. These diagrams are used to
model the static usecase view of a system.
4: Select the item
6: Response
7: Generate cart
3: Display options
5: Request for more
VISITOR
9: Entered account no. and other information
14: Logout
2: Validate
1: Login ACCOUNT
SESSION
11: Verify
DATA
BASE
Activity Diagram
• An activity diagram shows the flow from
activity to activity .An activity is an ongoing
non atomic execution within a state machine
.Activities ultimately result in some action
,which is made up of executable atomic
computations. we can use these diagrams to
model the dynamic aspects of a system.
State Chart Diagram
• Statechart diagram is used to model dynamic
nature of a system. They define different
states of an object during its lifetime. And
these states are changed by events. So
Statechart diagrams are useful to model
reactive systems. Reactive systems can be
defined as a system that responds to external
or internal events.
COMPONENT DIAGRAM
• Component diagrams are used to model
physical aspects of a system. Now the
question is what are these physical aspects.
• Physical aspects are the elements like
executables, libraries, files, documents etc
which resides in a node
Deployment Diagram
• Deployment diagrams are used to visualize the
topology of the physical components of a
system where the software components are
deployed. So deployment diagrams are
used to describe the static deployment view
of a system. Deployment diagrams consist of
nodes and their relationships.