Sri Lanka Institute of
Information Technology
BSc (IT) – First Year
Systems Analysis & Design
N106
LECTURE 1
Introduction
Course Identification


Lecturer in charge
E-mail
– Nideshika Ellepola
– nideshika.e@sliit.lk

Meeting lecturer on Wednesday 2.30 PM to 3.30 PM
Unit Objective
To provide students an overall knowledge on the
Software Development Life Cycle (SDLC) and to
facilitate a detailed learning of the main phases
which are,





Planning
Analysis
Design
Implementation
Unit Learning Outcomes

On completion of the unit you should know,
 The phases and the sub activities of the SDLC
 Should also have a good knowledge of the different
mechanisms used in the sub activities
 Able to compare and select an appropriate mechanism
according to the given situation
Unit Assessment Criteria




Mid term examination
Group Project
Lab Attendance & Performance
Final Examination
–
–
–
–
30%
15%
05%
50%

To pass this unit, students are required to get at
least 45% of the marks for the midterm, the
assignment and the final examination.
Unit Outline - Lectures
Week
Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Week 7
Week 8
Week 9
Week 10
Week 11
Week 12
Week 13
Week 14
Lecture
Introduction to SAD
Project Initiation
Project Management
Systems Analysis
Gathering Information
Process Modeling
Mid Term Examination
System Design
Architecture Design
User Interface Structure Design
User Interface Design Components
Program Design
Construction & Installation
Revision
Assignments
Group Registration
Assignment 1
Assignment 2
Unit Outline - Labs
Week
Week 2
Week 3
Week 4
Week 5
Week 6
Week 7
Week 8
Week 9
Week 10
Week 11
Week 12
Week 13
Week 14
Lecture
Introduction to Microsoft Visio 2010
Introduction to Microsoft Project 2010
Exercises on Microsoft Project
Compiling a survey for information gathering
DFD Tutorial 1 & 2
Mid Term Examination
DFD Tutorial 3 & 4
DFD Tutorial 5 & 6
DFD Tutorial 7 & 8
DFD – Past Papers
Structure Chart Tutorial 1
Structure Chart Tutorial 2 & 3
Structure Chart - Past Papers
References

Systems Analysis & Design By – Alan Dennis &
Barbra Haley Wixom
Attention



Attendance for the lecture + tutorial sessions is
compulsory. (80% of attendance is compulsory)
Lab Attendance is compulsory and marks will be
given for performance.
Plagiarism is prohibited. You will be penalized.
Key Ideas

Many failed systems were abandoned because
analysts tried to build wonderful systems without
understanding the organization.

The primarily goal is to create value for the
organization.
Key Ideas

The systems analyst is a key person analyzing the
business,
identifying
opportunities
for
improvement, and designing information systems
to implement these ideas.

It is important to understand and develop through
practice the skills needed to successfully design
and implement new information systems.
THE SYSTEMS
DEVELOPMENT LIFE
CYCLE
Major Attributes of the Lifecycle

The project –
 Moves systematically through phases where each
phase has a standard set of outputs
 Produces project deliverables
 Uses deliverables in implementation
 Results in actual information system
 Uses gradual refinement
Project Phases

Planning (Why build the system?)

Analysis (Who, what when, where will the system
be?)

Design (How will the system work?)

Implementation (System delivery)
A “Simple” Process for Making Lunch
Planning





Identifying business value
Analyze feasibility
Develop work plan
Staff the project
Control and direct project
Analysis




Analysis
Information gathering
Process modeling
Data modeling
Design





Physical design
Architectural design
Interface design
Database and file design
Program design
Implementation


Construction
Installation
Processes and Deliverables
Process
Product
Planning
Project Plan
Analysis
System Proposal
Design
Implementation
System
Specification
New System and
Maintenance Plan
1–21
SYSTEM DEVELOPMENT
METHODOLOGIES
What Is a Methodology?


A formalized approach or series of steps
Examples
 Process-Centered
 Data-Centered
 Object-Oriented
Waterfall Development Method
1–24
Pros and Cons of the Waterfall
Method
Pros
Identifies systems
requirements long
before programming
begins
Cons
Design must be
specified on paper
before programming
begins
Long time between
system proposal and
delivery of new
1–25
system
Alternatives to the SDLC






Parallel Development
Rapid Application Development (RAD)
Phased Development
Prototyping
Spiral Development
Packaged Systems
Parallel Development Method
1–27
Pros and Cons of Parallel
Development
Pros
Cons
Reduces Scheduled
Time
Still Uses Paper
Documents
Less Chance of
Rework
Sub-projects May Be
Difficult to Integrate
1–28
Rapid Application Development




CASE tools
JAD sessions
Fourth
generation/visualization
languages
Code generators
programming
Three RAD Categories

Phased development
 A series of versions

Prototyping
 System prototyping

Throw-away prototyping
 Design prototyping
Phased Development
Phased Development

Advantages
 Identification of important requirements.
 Quickly get a useful system to the users.

Disadvantage
 Difficult to include all the important features in the
version 1.
How Prototyping Works
1–33
Prototyping

Advantages
 Have a system in place for the user at an early stage.
 Ability to quickly refine real requirements.
 Reassures the client.

Disadvantage
 Requirements have to be analyzed quickly and
carefully.
Throwaway Prototyping
Throwaway Prototyping

Advantages
 Resolve technical issues.
 Enables the users to understand the system.

Disadvantage
 Do not make use of the prototype.
Criteria for Selecting the
Appropriate Methodology






Clear user requirements
Familiar technology
Complexity
Reliability
Time schedule
Schedule visibility
TEAM ROLES AND SKILLS
Information Systems Roles





Business analyst
System analyst
Infrastructure analyst
Change management analyst
Project manager
Summary



The Systems Development Lifecycle consists of four
stages:
Planning,
Analysis,
Design,
and
Implementation
There are five major development methodologies:
the waterfall method, the parallel development
method, the phased development method, system
prototyping and design prototyping.
There are five major team roles: business analyst,
systems analyst, infrastructure analyst, change
management analyst and project manager.
Thank you!

Q&A