4.

0 – DESIGN FUNCTIONAL MODEL FOR THE

SYSTEM

4.1 - S.S.A.D.M. – STRUCTURED SYSTEM ANALYSIS DESIGN

METHOLOGY

SSAMD means Structured System Analysis & Design Method. It is

widely used for computer application development. SSADM divides an
application development project into modules, stages, steps and tasks
and provides a framework for describing projects. SSADM covers the
aspects of the life cycle of a system from the feasibility study phase to
the production of a physical design. The main feature of SSADM is the
intensive user involvement in the requirements analysis stage. The
stages SSADM include,

• Determine feasibility

• Investigating the current environment

• Determining business system option

• Defining requirements

• Determining technical system options

• Creating the logical design

• Creating the physical design

Important characteristics of SSADM are,

• Dividing a project into small modules with well-defined objectives.

• Diagrammatic representation.
 • Preforming activities in a sequence.

• Simple and easily understood by clients and developers.

SSADM’s objectives are,

• Improve project management and control

• Develop better quality system

• Make effective use of experienced and inexperienced development staff

• Establish a framework for good communication between participants in a

projects.
4.2 – CONTEX LEVEL DIAGRAM

Figure 14
4.2.1. – CONTEX DIAGRAM FOR ONLINE MOBILE
APPLICATION

F
igure 15

4.3 – DFD LEVEL 0 DIAGRAM

 Figure 16

4.4 –DFD LOWER LEVEL DIAGRAM

1.0 Login
 Figure 17
2.0 Check availability
 Figure 18

3.0 Book a conference room

 Figure 19

4.0 cancellation of booking

 Figure 20

4.5-TOP DOWN DESIGN METHOD

 This method starts by identifying the data sets from
general and moves to the specific.

 In other words, someone starts with a general idea of

what is needed for the system and then work him or her
way down to the more specific details of how the system
will in interacts.

 This process involves the identification of different

entity types and the definition of each entity’s attribute.

 This method appropriates for complex databases which

start with the development of data models that contain a
few high-level entities and relationships (ER model).

 And it applies successive top-down refinements to

identify lower-level entities, relationships and associate
attributes.

 Entities, relations and transaction more easily managed.

Figure 21
4.6-BOTTOM UP DESIGN METHOD

 This method starts with specific details and moves up

to the general.
 Here first identifies the data elements and then group
them together in data sets.
 In other words, it first defines attributes, and then
groups them to form entities.
 This method appropriates for small databases with
few entities, attributes, relations and transactions.

 Suitability for begin with normalization which

identifies the required attributes into normalized relations
based on functional dependencies between the attributes.

 The selection of primary emphasis often depends on

the scope of the problem or on personal preferences.

Figure 22
4.7 – O.O.A.D.M – OBJECT ORIENTED ANALYSIS AND
DESIGN
METHOLOGY

This is a structured method for analyzing, designing, a system

by applying the object oriented concepts and develop a set of graphical
models during the development life cycle of the software which created
and managed by the Object management group in 1989. In the
framework or protest situated investigation period of programming
improvement, framework prerequisites will be resolved, classes will be
perceived and the relationships between the classes will be recognized.
The object oriented model visualized the elements of the software
application in terms of objects. So the basic concepts and terminologies
are,

• Objects and Classes

• Encapsulation and Data Hiding
• Message Passing
• Inheritance
• Polymorphism
• Generalization and Specialization
• Links and Association
• Aggregations and Composition

The benefits of OOAD are,

• Helps in faster development of software.
• Easy to maintain
• Enables reuse of objects, function and designs.
• Reduces development risks
4.8 – USE CASE DIAGRM

Figure 23
4.9 – CLASS DIAGRAM

Figure 24
 4.10 – SEQUENCE DIAGRAM
Login

Search a conference room Figure 25

 Figure 26
Cancel reservation

Figure 27
Reschedule

Figure 28