OSUN STATE UNIVERSITY

Department of Computer Science

SYSTEMS ANALYSIS AND DESIGN

LAB MANUAL

Page | 1
Practical On SADM

Objectives:

 The student is expected to get familiar with the SADM package that will allow him to
run the various practicals
 Other methodologies will also be briefly discussed
 The meaning of SADM, its techniques, logical modeling, data flow modeling, Entity
/Event modeling
 Structure of SADM

Introduction

In the early days of large scale information systems development many organizations used the
Cobol programming language together with indexed sequential files to build systems for
customer billing, payroll, stock control and a variety of other business areas. Developments at
this time were characterized by:-

 limited user involvement;

 inadequate requirements elicitation;
 use of ad hoc analysis and design techniques;
 absence of CASE support for analysis and design;
 time consuming use of 3GL tools;
 inflexible file and 3rd generation database management systems.

Frequently the results of this approach were systems which, on delivery, did not satisfy business
requirements. This caused extensive maintenance requirements and thus an increase in the
applications backlog. A variety of problems may have caused the mis-match between system
functionality and business requirements:-

 a lack of ownership of and commitment to the system from users as a result of the low
level of involvement;
 business requirements may have changed between inception and delivery;
 requirements may have been mis-understood;
 inadequate analysis and design tools and techniques may have been used;
 or more likely a combination of these problems.

The response from the information systems community to these problems was the development
of structured methodologies for ISE. The purpose of these methodologies seems to have been to
(a) formalise the requirements elicitation process to reduce the chances of mis-understanding the
requirements

(b) To introduce best practice techniques to the analysis and design process

Page | 2
 SSADM (in common with other structured methodologies) adopts a prescriptive approach to
information systems development in that it specifies in advance the modules, stages and tasks
which have to be carried out, the deliverables to be produced and furthermore the techniques
used to produce the deliverables.

What is SADM?

SADM (Structured Systems Analysis and Design Methodology) is a methodology ( i.e a system
of ways of doing things especially regular and orderly procedures), used in the analysis and
design stages of systems development. SSADM does not cover SITP issues or the construction,
testing and implementation of software.

"SADM has been used by in computing since its launch in 1981. In a bid to standardise the
many and varied IT projects being developed. Since 1981 SSADM has been further refined and
version 4 was launched in 1990. SSADM is an open standard, i.e. it is freely available for use in
industry and many companies offer support, training and Case tools for it.

Why is SADM Used?

Within government departments SADM has to be used. External contractors producing software
for the government also have to use SADM. SADM is used by other companies because they
expect the use of a disciplined ‘engineering approach will eventually improve the quality of the
systems they produce. many companies have been willing to incur the considerable expense of
implementing SSADM (e.g. staff training) with this expectation in mind.

Page | 3
Major Tools of SADM?

SADM revolves around the use of three key techniques, namely

 Logical Data Modeling,

 Data Flow Modeling
 Entity/Event Modeling.

► Logical Data Modeling; This is the process of identifying, modeling and

documenting the data requirements of a business information system. A Logical
Data Model consists of a Logical Data Structure (LDS - The SSADM terminology
for an Entity-Relationship Model) and the associated documentation. LDS s
represent Entities (things about which a business needs to record information) and
Relationships (necessary associations between entities)
► Data Flow Modeling; This is the process of identifying, modeling and
documenting how data flows around a business information system. A Data Flow
Model consists of a set of integrated Data Flow Diagrams supported by
appropriate documentation. DFDs represent processes (activities which transform
data from one form to another), data stores (holding areas for data), external
entities (things which send data into a system or receive data from a system and
finally data flows (routes by which data can flow)
► Entity Event Modeling; This is the process of identifying, modeling and
documenting the business events which affect each entity and the sequence in
which these events occur. An Entity/Event Model consists of a set of Entity Life
Histories (one for each entity) and appropriate supporting documentation. slide 9

Structure of SSADM

SSADM consists of 5 main modules, which are in turn broken down into a complex hierarchy of
stages, steps and tasks. slide 11

1. Feasibility Study; Module 1 the feasibility study consists of a single stage (Stage 0
Feasibility),which involves conducting a high level analysis of a business area to
determine whether a system can cost effectively support the business requirements. In
stage 0 an overview DFD is produced together with a high level LDS. At this stage the
DFD will represent the existing system warts and all and the LDS may be incomplete and
contain unresolved M:M relationships.

2. Requirements Analysis; Module 2 requirements analysis consists of 2 stages;

Page | 4
 ► Stage 1 Investigation of Current Environment and Stage
► Business System Options (BSO).

During stage 1 the systems requirements are identified and the current business
environment is modeled in terms of the processes carried out and the data
structures involved. During stage 1 DFDs and an LDS are used to produce
detailed logical models of the current system . During stage 2 up to 6 business
system options are produced and presented. As a result one of these options (or
indeed a hybrid solution) is adopted and refined. During stage 2 DFDs and LDS
are produced to support each business system option and the final chosen option.
The transition from stage 1 to stage 2 is a key part of SSADM, this is where we
move from a logical model of the current system to a logical model of the
required system, i.e. this is where the DFDs and LDS have to be refined to cater
new/changed requirements.

3. Requirements Specification; Module 3 Requirements Specification consists of a single

stage (Stage 3 Definition of Requirements) which involves further developing the work
carried out in module 2, detailed functional and non-functional requirements are
identified and new techniques are introduced to define the required processing and data
structures. In stage 3 the DFDs and LDS are refined and cross validated in the light of the
chosen business system option. The LDS is enhanced using relational data analysis
(normalisation). The DFDs and LDS are validated against the ELHs also produced during
this stage. DFDs LDS and ELHs are used as input to the subsequent stages of SSADM.

4. Logical System Specification; Module 4 Logical System Specification consists of 2

stages; Stage 4 Technical System Options and Stage 5 Logical Design. In stage 4 up to
6 technical options (specifying the development and implementation environments) are
produced, one being selected. In stage 5 the logical design of update and enquiry
processing and system dialogues (menus etc.) is carried out.

5. Physical Design; Module 5 Physical Design consists of a single stage (Stage 6 Physical
Design) in which the logical system specification and technical system specification are
used to create a physical database design and a set of program specifications.

Page | 5
WEEK 2 Practicals

This Practical introduces the student to the tutorial sheet of

SSADM Questions are asked and the student is advised to attempt

them.

Tutorial Sheet: Introduction to SSADM

Objectives

The objective is to encourage you to view SSADM not as a magic pill which can be
swallowed whole or not at all, but as an analysis & design framework or set of tools which can
be adopted in whole or in part depending on requirements and which can be modified, tweaked
or manipulated by people with sufficient experience and expertise.

Question 1

Of the three main tools of SSADM (LDS, DFD, ELH) which is the most important and why
from the point of view of the analyst/designer? Which would be the easiest to understand from
the end-users point of view?

Question 2

"When developing information systems the technical environment should be established as

soon as possible to avoid any nasty surprises in the later stages of development." Is this a valid
statement? If so why within SSADM do technical system options not get considered until the
penultimate module.

Question 3

With so many possible implementation environments is there any point having a general physical
design module?

Question 4

Why do you suppose ELHs are not used alongside the DFDs and LDS in the requirements
analysis phase?

Question 5
Page | 6
Would SSADM be feasible without the support of CASE tools?

WEEK 3 Practical

Students are introduced here to a basic software that will allow them to create, design and
implement various kind of system analysis diagrams using Eldraw Max software

Introduction

Edraw Max enables students, teachers and business professionals to reliably create and publish
kinds of diagrams to represent any ideas. It's an all-in-one graphics software that makes it
simple to create professional-looking flowcharts, organizational charts, network diagrams,
business presentations, building plans, mind maps, fashion designs, UML diagrams,
workflows, program structures, web design diagrams, electrical engineering diagrams,
directional maps, database diagrams and more. Screenshot

Create flowcharts, organizational charts, network diagrams with minimum

time loss!

With large pre-drawn libraries and more than 4600 vector symbols, drawing couldn't be easier!
Edraw Max lets you create a wide range of diagrams using templates, shapes, and drawing
tools while working in an intuitive and familiar Office-style environment.

Edraw provides you a versatile, easy, quick and professional solution to let you enjoy your
working.

Why have we Chosen Edraw Max ?

1. Uses the diagramming software that best maps to what you know and where you're
headed.

Page | 7
 2. Is Fully vector-based graphic software, which facilitates the rapid creation of flowcharts,
organizational charts, network diagrams and more.
3. Supports to import the exist Visio XML file perfectly.
4. Just drag the build-in shapes from the library pane and drop them on your page. Drawing
couldn't be easier!
5. Creates professional-looking diagrams quickly with themes, effects and quick styles.
6. Gains greater productivity in diagramming with features like automatically aligns and
arranges all shapes.
7. Includes lots of high-quality shapes, examples and templates.
8. Distinct colors, fonts, shapes, styles, pictures, text, and symbols are available for
each diagram object.
9. Easily visualizes complex information with a wide range of diagrams. Make those
diagrams even smarter and more useful by linking them to underlying data, which
provides a more complete picture of the system or process.
10. Works with MS Office well. It can be integrated with Microsoft Office application
easily. The UI is MS Office-style like, it's easy to learn and use. If you are familiar with
MS Office, you are familiar with Edraw quickly.
11. Generics graphic formats support and WYSIWYG printing.

Additional Features

 The UI is MS Office 2007 style like. Full ribbon features.

 Added Themes, Color Themes, Effects and Fonts. Easy to change the whole diagram by
changing the active theme. With the new Theme feature, you can format the colors and
effects in an entire diagram with a single click.
 Real-time previews. When you scroll over the various galleries in Edraw, you'll see your
drawings and various objects change to display what they'll look like if you decide to
apply those settings. Just click on the thumbnail in the gallery to actually accept the
changes. This makes it a lot faster to see, for example, how changing a color scheme
will affect your drawings.
 Quick layouts and quick styles. These provide quick formatting options for the object in
question, and make it easy to create good-looking slides with just a few clicks.

Page | 8
  Put Edraw graphics into Word, Excel, PowerPoint with one-click buttons.
 Text objects supported line space, bullet, Indent, back color, super script, sub script and
more.
 Shadows in general are so very nice compared to those in previous versions. We
can actually control the transparency, amount of blur, and color now.
 Shape and text presets make it really easy to apply a preset look to an object or text.
 It's quicker to zoom in and out now using the zoom slider in the southeast corner of the
screen.
 Table support.
 Recolor picture, Light and Contrast, transparent PNG support.
 Opened the Shape Sheet for senior users to create more complicated shapes.
 More 2000 clip arts.
 Improved the Insert Hyperlink function.
 Improved the Print function. Support more page sizes such as A0, A1. You can also print
the large size graphics in separate pages.
 Persistent undo and redo.
 High quality graphic export.

Vector-based

Edraw Max is a vector-based diagramming software, which means whatever size you change the
diagram, it will always keep high quality.

Easy and friendly UI

Edraw UI is MS Office-style like, it's easy to learn and use. If you are familiar with MS Office,
you are familiar with Edraw quickly.

Work with MS Office well

Edraw provides several ways to cooperate with MS Office system.

You can copy the selected shapes then paste it into MS Office document.

Page | 9
You can insert the Edraw OLE object in MS Office application.

You also can export the drawings to generics graphic formats such as jpg, tif, bmp. Then switch
to MS Office and insert the picture.

Support almost all kinds of graphics formats

Supports almost all the generics graphics formats, it can export or import those common graphics
formats, like bmp, gif, dib, png, tif, wmf, emf, html and so on.

Save as exe file and share it with anyone without Edraw

You can save your drawing file to exe format and share it with anyone you want, even it has no
Edraw installed.

Provide drawing tools like Illustrator

Provides a set of drawing tools like Adobe Illustrator, with those tools you can draw your own
shapes or change the shapes in library.

Distribute shapes automatically

Edraw can help you align and arrange all shapes automatically, this will speed your working.

Strong style system and plenty of beautiful build-in styles

Edraw has an easy and quick style system, and provides a lot of pre-defined styles, which can
help you make your diagram beautiful and personal in short time.

Abundant libraries and templates involving kinds of fields

Provide abundant libraries and templates include flowcharts, organizational charts, build plans,
network diagrams and more.

Define and manage your own libraries and templates

Page | 10
You can draw your own shapes and documents save as libraries and templates, and use them
as pre-defined libraries and templates.

Edraw System requirements

 Windows® 2000, Windows® XP Tablet PC, Windows® XP, Windows 2003, Windows
Vista
 256 MB of RAM, 20 MB of hard disk space
 Pentium® III, 750MHz processor
 1,024 x 768 or better monitor resolution
 Mouse and keyboard

Page | 11
WEEK 15 Practicals

The student is expected here to familiarize himself with designing and drawing diagrams of
Database models, Marketing models,

Database Model Diagrams

Draw database model diagrams

You can easily use an intuitive database design tool and database model Diagram tool which can
save you hundreds hours of work.

This tool will allows you to reverse engineer already existing database structures, create detailed
HTML or PDF reports.

The Entity-Relationship Model

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way
to unify the network and relational database views. Simply stated the ER model is a conceptual
data model that views the real world as entities and relationships. A basic component of the
model is the Entity-Relationship diagram which is used to visually represents data objects. Since
Chen wrote his paper the model has been extended and today it is commonly used for database
design For the database designer, the utility of the ER model is:

 it maps well to the relational model. The constructs used in the ER model can easily
be transformed into relational tables.
 it is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in a specific database management software.

Symbols for Database Model Diagrams

Thanks to an extensive set of library objects such as entities, links, items, attributes, users, types,
captions, inheritance, references, boundaries, events, clouds etc Edraw is a perfect tool for
database model design and ER diagramming.

Page | 12
You can draw Chen ERD, Database model diagram, Express-G, Martin ERD, ORM Diagram
and a lot more.

Basic Constructs of E-R Modeling

The ER model views the real world as a construct of entities and association between entities.

Entities

Entities are the principal data object about which information is to be collected. Entities are
usually recognizable concepts, either concrete or abstract, such as person, places, things, or
events which have relevance to the database. Some specific examples of entities are
EMPLOYEES, PROJECTS, INVOICES. An entity is analogous to a table in the relational
model.

Entities are classified as independent or dependent (in some methodologies, the terms used are
strong and weak, respectively). An independent entity is one that does not rely on another for
identification. A dependent entity is one that relies on another for identification.

An entity occurrence (also called an instance) is an individual occurrence of an entity. An

occurrence is analogous to a row in the relational table.

Page | 13
Special Entity Types

Associative entities (also known as intersection entities) are entities used to associate two or
more entities in order to reconcile a many-to-many relationship.

Subtypes entities are used in generalization hierarchies to represent a subset of instances of their
parent entity, called the supertype, but which have attributes or relationships that apply only to
the subset.

Associative entities and generalization hierarchies are discussed in more detail below.

Relationships

A Relationship represents an association between two or more entities. An example of a

relationship would be:

1. employees are assigned to projects

2. projects have subtasks
3. departments manage one or more projects

Relationships are classified in terms of degree, connectivity, cardinality, and existence. These
concepts will be discussed below.

Attributes

Attributes describe the entity of which they are associated. A particular instance of an attribute is
a value. For example, "Jane R. Hathaway" is one value of the attribute Name. The domainof an
attribute is the collection of all possible values an attribute can have. The domain of Name is a
character string.

Attributes can be classified as identifiers or descriptors. Identifiers, more commonly called keys,
uniquely identify an instance of an entity. A descriptor describes a non-unique characteristic of
an entity instance.

Classifying Relationships

Relationships are classified by their degree, connectivity, cardinality, direction, type, and
existence. Not all modeling methodologies use all these classifications.

Degree of a Relationship

The degree of a relationship is the number of entities associated with the relationship. The n-ary
relationship is the general form for degree n. Special cases are the binary, and ternary ,where the
degree is 2, and 3, respectively.

Page | 14
Binary relationships, the association between two entities is the most common type in the real
world. A recursive binary relationship occurs when an entity is related to itself. An example
might be "some employees are married to other employees".

A ternary relationship involves three entities and is used when a binary relationship is
inadequate. Many modeling approaches recognize only binary relationships. Ternary or n-ary
relationships are decomposed into two or more binary relationships.

Direction

The direction of a relationship indicates the originating entity of a binary relationship. The entity
from which a relationship originates is the parent entity; the entity where the relationship
terminates is the child entity.

The direction of a relationship is determined by its connectivity. In a one-to-one relationship the

direction is from the independent entity to a dependent entity. If both entities are independent,
the direction is arbitrary. With one-to-many relationships, the entity occurring once is the parent.
The direction of many-to-many relationships is arbitrary.

Type

An identifying relationship is one in which one of the child entities is also a dependent entity.
A non-identifying relationship is one in which both entities are independent.

Existence

Existence denotes whether the existence of an entity instance is dependent upon the existence of
another, related, entity instance. The existence of an entity in a relationship is defined as either
mandatory or optional. If an instance of an entity must always occur for an entity to be included
in a relationship, then it is mandatory. An example of mandatory existence is the statement
"every project must be managed by a single department". If the instance of the entity is not
required, it is optional. An example of optional existence is the statement, "employees may be
assigned to work on projects".

Generalization Hierarchies

A generalization hierarchy is a form of abstraction that specifies that two or more entities that
share common attributes can be generalized into a higher level entity type called a supertype or
generic entity. The lower-level of entities become the subtype, or categories, to the super type.
Subtypes are dependent entities.

ER Notation

Page | 15
There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts and
journals but rarely seen in either CASE tools or publications by non-academics. Today, there are
a number of notations used, among the more common are Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The
notation used in this document is from Martin. The symbols used for the basic ER constructs are:

 entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
 relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs.
 attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
 existence is represented by placing a circle or a perpendicular bar on the line. Mandatory
existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional.

Draw Marketing Charts and Diagrams

Edraw Max is a vector-based diagramming software with

rich examples and templates. Easy to create flow charts,
organizational charts, business process, UML diagrams, work
flows, program structures, network diagrams, chart and
graphics, mind map, directional maps and database diagrams.
With pre-drawn libraries and more than 4600 vector symbols,
drawing couldn't be easier!

Symbols for Marketing Charts and Diagrams

Marketing Shapes

Page | 16
 Marketing Diagrams

Some symbols has the control points and you can move them to change the shape's appearance.

Page | 17
Page | 18