Kingdom of Saudi Arabia

Ministry of Higher Education

Al-Imam Muhammad Ibn Saud Islamic University
College of Computer and Information Sciences

Chapter 1:
Introduction to Systems
Analysis and Design
IS 309

Systems Analysis and Design

Information Systems Department

Learning Objectives
• Systems development life cycle
• Identify the four phases
• How it came about
• Methodology alternatives
• Team roles & skill sets
• Object-oriented systems characteristics
• Object-oriented systems analysis & design
• The Unified Process & its extensions
• The Unified Modeling Language (UML)

IS Department 2
Introduction (cont.)
• System Analysis: the of understanding and specifying in
detail what the information system should do.

• System Design: the process of specifying in detail how the

many components of the information system should be
physically implemented.

• System Analyst: a business professional who uses

analysis and design techniques to solve business
problems using information technology.

IS Department 3
Introduction
• Why do we need a formal process?
• Failures occur (too) often
• Creating systems is not intuitive
• Projects are late, over budget or delivered with fewer features than
planned

• The System Analyst is the key person

• Designs a system to add value
• Must understand the business processes
• Job is rewarding, yet challenging
• Requires specific skill sets

IS Department 4
Systems Development
Life Cycle (SDLC)

IS Department 5
The SDLC Process

• The process consists of four phases

• Each phase consists of a series of steps
• Each phase is documented (deliverables)
• Phases are executed sequentially,
incrementally, iteratively or in some other
pattern

IS Department 6
Questions to be Answered
• Planning phase
• Why should we build this system?
• What value does it provide?
• How long will it take to build?
• Analysis phase
• Who will use it?
• What should the system do for us?
• Where & when will it be used?
• Design phase
• How should we build it?

IS Department 7
SDLC: The Planning Phase
1. Project Initiation
• Develop/receive a system request
• Conduct a feasibility analysis
• Technical feasibility
• Economic feasibility
• Organizational feasibility

2. Project Management
• Develop the work plan
• Staff the project
• Monitor & control the project

IS Department 8
SDLC: The Planning Phase
System Request

IS Department 9
SDLC: The Analysis Phase
1. Develop an analysis strategy
• Model the current system
• Formulate the new system
2. Gather the requirements
• Develop a system concept
• Create a business model to represent:
• Business data
• Business processes

3. Develop a system proposal

IS Department 10
SDLC: The Design Phase
1. Develop a design strategy
2. Design architecture and interfaces
3. Develop databases and file specifications
4. Develop the program design to specify:
• What programs to write
• What each program will do

IS Department 11
SDLC: The Implementation Phase

1. Construct the system

• Build it (write the programming code)
• Test it
2. Install system
• Train the users
3. Support the system (maintenance)

IS Department 12
SDLC: Methodologies + 31 ‫اليد‬$ ‫س‬
• Methodology: a formalized approach to
implementing the SDLC
• Categories
• Process centered
Elements of the system(type)
• Data centered
• Object-oriented
• Structured
• Rapid action development Amount of time and
effort
• Agile development

IS Department 13
Classes of Methodologies

• Structured Development
• Waterfall Development
• Parallel Development

• Rapid Application Development

• Phased
• Prototyping

• Agile Development
• eXtreme Programming
• SCRUM

IS Department 14
 Structured Development
Waterfall Model

+ sys requirements are identified 

+ minimize change
-Design must be completely specified before
programming
-Long time between analysis and delivery
IS Department 15
 Structured Development
Parallel Model

+ less time, less chance of required rework

- Long documentation like waterfall
- Interdependent subproject
- Requires integration

IS Department 16
 identifies the overall system concept, and
RAD Development the project team, users, and system
sponsor then categorize the
Phased Model requirements into a series of versions

+Use CASE, JAD, Visual programming,

automatic code generation to speedup
+ quick delivery of a functional system
- Managing expectation
- User might get frustrated

IS Department 17
RAD Development
Prototyping_Based Methodology

a quick-and-dirty program
that provides a minimal
amount of features

+ very quick
+ less paper work
- problem for complex design
- short analysis phase

IS Department 18
 RAD Development
Throwaway Prototyping_Based Methodology

+ long analysis, so more stable and reliable

- may take more time than prototype

IS Department 19
Agile Development
eXtreme Programming

IS Department 20
Agile Development

IS Department 21
Which Methodology to Use?

IS Department 22
The Systems Analyst: Skills
• Agents of change
• Identify ways to improve the organization
• Motivate & train others

• Skills needed:
1.Technical: must understand the technology
2.Business: must know the business processes
3.Analytical: must be able to solve problems
4.Communications: technical & non-technical audiences
5.Interpersonal: leadership & management
6.Ethics: deal fairly and protect confidential information

IS Department 23
The Systems Analyst: Roles ‫أدوار‬

IS Department 24
Characteristics of Object-Oriented
Systems
• Classes & Objects
1. Object (instance): instantiation of a class
2. Attributes: information that describes the class
3. State: describes its values and relationships at a point
in time
• Methods & Messages
• Methods: the behavior of a class
• Messages: information sent to an object to trigger a
method (procedure call)

IS Department 25
Characteristics of Object-Oriented
Systems (cont.)

• Encapsulation & information hiding

• Encapsulation: combination of process & data
• Information hiding: functionality is hidden
• Inheritance
• General classes are created (superclasses)
• Subclasses can inherit data and methods from a
superclass

IS Department 27
Characteristics of Object-Oriented Systems
(cont.)

• Polymorphism & dynamic binding

• Polymorphism: the same message can have different meanings
• Dynamic binding: type of object is not determined until run-time
• Contrast with static binding

IS Department 29
 Object-Oriented
Systems Analysis & Design
• Attempts to balance data and process
• Utilizes the Unified Modeling Language (UML) and
the Unified Process
• Characteristics of OOAD:
1. Use-case Driven
2. Architecture Centric
3. Iterative and Incremental

IS Department 31
Object-Oriented Systems Analysis & Design

• Use-case driven
• Use-cases define the behavior of a system
• Each use-case focuses on one business process
• ‫مايصلح اجمع‬

• Architecture centric
1.Functional (external) view: focuses on the user’s perspective
2.Static (structural) view: focuses on attributes, methods, classes &
relationships
3.Dynamic (behavioral) view: focuses on messages between classes
and resulting behaviors

IS Department 32
Object-Oriented Systems Analysis & Design
(cont.)
• Iterative & incremental
• Undergoes continuous testing & refinement
• The analyst understands the system better over time

• Benefits of OOSAD
• Break a complex system into smaller, more manageable
modules
• Work on modules individually
• See the system more realistically—as the users do

IS Department 33
The Unified Process
• A specific methodology that maps out when and how to
use the various UML techniques for object-oriented
analysis and design
• A two-dimensional process consisting of phases and
workflows
• Phases are time periods in development
• Workflows are the tasks that occur in each phase
• Activities in both phases & workflows will overlap

IS Department 34
The Unified Process

IS Department 35
Unified Process Phases
• Inception = planning
• Feasibility analyses performed
• Workflows vary but focus is on business modeling
& requirements gathering
• Elaboration
• Heavy focus on analysis & design
• Other workflows may be included
• Construction: Focus on programming
(implementation)
• Transition--Focus on testing & deployment

IS Department 36
Engineering Workflows
• Business modeling
• Requirements
• Analysis
• Design
• Implementation
• Testing
• Deployment

IS Department 37
Supporting Workflows
• Project management
• Configuration and change management
• Environment

IS Department 38
Extensions to the Unified Process

• The Unified Process does not include:‫مشاكل‬

1. Staffing
2. Budgeting
3. Contract management
4. Maintenance
5. Operations
6. Support
7. Cross- or inter-project issues

IS Department 39
Extensions to the Unified Process
(cont.)
• Add a Production Phase to address issues after the
product has been deployed
• New Workflows:
1. Operations & Support
2. Infrastructure management
• Modifications to existing workflows:
1. Test workflow
2. Deployment workflow
3. Environment workflow
4. Project Management workflow
5. Configuration & change management workflow
• ‫اضافو االبرودكشن‬
• + ‫ت___و ن__يو ورك ف___لو‬
• ‫تعديل ع ورك فلو‬

IS Department 40
IS Department 41
Enhanced Unified Process

IS Department 42
Unified Modeling Language
• Provides a common vocabulary of object-
oriented terms and diagramming techniques rich
enough to model any systems development
project from analysis through implementation
• Version 2.0 has 14 diagrams in 2 major groups:
• Structure diagrams
• Behavior diagrams

IS Department 43
UML Structure Diagrams
• Represent the data and static relationships in an
information system
1. Class
2. Object
3. Package
4. Deployment
5. Component
6. Composite structure

IS Department 44
UML Behavior Diagrams
• Depict the dynamic relationships among the instances or
objects that represent the business information system
1. Activity
2. Sequence
3. Communication
4. Interaction overview
5. Timing
6. Behavior state machine
7. Protocol state machine,

IS Department 45
Summary

• All systems development projects follow

essentially the same process, called the system
development life cycle (SDLC)
• System development methodologies are
formalized approaches to implementing SDLCs
• The systems analyst needs a variety of skills and
plays a number of different roles
• Object-oriented systems differ from traditional
systems

IS Department 46
Summary

• Object-Oriented Systems Analysis and Design

(OOSAD) uses a use-case-driven, architecture-
centric, iterative, and incremental information
systems development approach
• The Unified Process is a two-dimensional
systems development process described with a
set of phases and workflows
• The Unified Modeling Language, or UML, is a
standard set of diagramming techniques

IS Department 47