University of Wollongong in Dubai

CSIT114 – System Analysis

Subject Overview and Introduction

Dr. Haitham Yaish

Dr. Zeenath Reza Khan
 Document Change Control

Version Author Date Change Description

1.0 Dr. Zeenath Reza Khan Autumn 2019 Defined the first version
2.0 Dr. Haitham Yaish Autumn 2023 Updated and Improved
Dr. Zeenath Reza Khan the Lecture Content.

3
 Agenda

• Introduction
• System Development Life Cycle (SDLC)
• SDLC Methodologies
• SDLC Core Processes
• Example
• Class Activity

4
 Introduction

What is Information System (IS) ?

• Information System is a set of interrelated
components that collect, process, store, and
provide as output the information needed to
complete business tasks.

• IS combines people, information technology and

data to facilitate organization planning, controlling,
coordinating, and decision making.

• Each IS (or app) is conceived and built to satisfy

some need to solve a problem(s).
5
 Introduction

• Computer application (app) – a computer software

program that executes on a computing device to
carry out a specific set of functions

• Project – a planned undertaking that has a

beginning and end and that produces some
definite result used to develop an information
system requires knowledge of systems analysis and
systems design tools and techniques.

6
 Introduction

• Systems analysis – those activities that enable a

person to understand and specify what an
information system should accomplish

• Systems design – those activities that enable a

person to define and describe in detail the system
that solves the needs.

7
 System Development Life Cycle (SDLC)

What is SDLC ?

SDLC is a framework that identifies all

the activities required to research,
build, deploy, and often maintain an
information system.

8
 SDLC Methodologies

Structured Iterative Agile

Development Development Development

Traditional Modern

9
 Structured Development

10
 Structured Development

• Through all development stages, the process

moves in a cascade mode.

• Each stage has concrete deliverables and is strictly

documented.

• The next stage cannot start before the previous

one is fully completed.

11
 Structured Development

• Thus, for example, software requirements cannot

be re-evaluated further in development.

• There is also no ability to see and try software until

the last development stage is finished, which
results in high project risks and unpredictable
project results.

• Long elapse between proposal and delivery.

12
 Structured Development

Use cases (Examples):

• Simple small or mid-sized projects with clearly
defined and unchanging requirements.

• Projects where a well-known technology stack and

tools are used.

• Projects that must adhere to multiple rules and

regulations.

13
 Iterative development

• An approach to system development in which the

system is “grown” piece by piece through multiple
iterations.

• Complete small part of system (mini-project), then

repeat processes to refine and add more, then
repeat to refine and add more, until done.

• It is called iterative because the six core development

processes are repeated for each component.

• One big project that has many smaller projects.

14
 Agile development

• An information system development process that

emphasizes flexibility to anticipate new
requirements during development

• It is fast development methodology, and

responsive to change

• Typically used when user and developer do not

understand the problem.

15
 SDLC Core Processes

SDLC includes six core processes:

Identify the problem or need and obtain approval

Plan and monitor the project

Discover and understand the details of the problem or need

Design the system components that solve the problem or satisfy the need

Build, test, and integrate system components

Complete system tests and then deploy the solution

16
 SDLC Core Processes

The six core processes Iterations of the SDLC

showing iterations

17
 Example – Agile & Iterative Method
Pre-Project Activities

• Identify the problem and document the objective of

the system (core process 1)
• Preliminary investigation
Identify the problem
• System Vision Document

• Obtain approval to commence the project (core Plan

process 1)
• Meet with key stakeholders, including executive Discover problem or need
management
• Decision reached, approve plan and budget
Design the system

Produce a “System Vision Document” Build, test, and integrate system

components
• Problem Description
• System Capabilities
Complete system tests
• Business Benefits

18
 Example – Agile & Iterative Method
Day 1 Activities

• Core Process 2: Plan the Project

• Determine the major components (functional
areas) that are needed
• Supplier information subsystem Identify the problem
• Product information subsystem
• Define the iterations and assign each function
Plan
to an iteration
• Decide to do Supplier subsystem first
• Plan one iteration as it is small and Discover problem or need
straight forward
• Determine team members and responsibilities
Design the system

Build, test, and integrate system

components
Develop a Work breakdown Structure
Work Sequence draft
Complete system tests

19
 Example – Agile & Iterative Method
Day 2 Activities

• Core Process 3: Discover and Understand

Details
• Do preliminary fact-finding to
Identify the problem
understand requirements
• Develop a preliminary list of use cases
and a use case diagram Plan
• Develop a preliminary list of classes
and a class diagram Discover problem or need

Design the system

List Use Cases
List Object Classes Build, test, and integrate system
components

Preliminary class diagram

Complete system tests

20
 Example – Agile & Iterative Method
Day 3 Activities

• Core Process 3: Discover and Understand

Details
• Do in-depth fact-finding to
Identify the problem
understand requirements
• Understand and document the
detailed workflow of each use case Plan
• Core Process 4: Design System
Components Discover problem or need
• Define the user experience with
screens and reports
Design the system

Use case diagram Build, test, and integrate system

components
Define Screen Layout
Draft a Screen Layout
Complete system tests

21
 Example – Agile & Iterative Method
Day 4 Activities

• Core Process 4: Design System Components

• Design the database (schema)
• Table design
Identify the problem
• Key and index identification
• Attribute types
• Referential integrity Plan
• Design the system’s high level structure
• Browser, Windows, or Smart phone; OO or Discover problem or need
procedural
• Architectural configuration (components)
Design the system
• Design class diagram
• Subsystem architectural design
Build, test, and integrate system
components
Database Schema
System Architectural diagrams Complete system tests
Design Preliminary Class Diagrams
Sub system architectural design diagrams

22
 Example – Agile & Iterative Method
Day 5 Activities

• Core Process 4: Design System Components

• Continue with design details
• Proceed use case by use case
Identify the problem
• Core Process 5: Build, Test, and Integrate
System Components
• Continue programming (build) Plan
• Build use case by use case
• Perform unit and integration tests Discover problem or need

Design the system

Build, test, and integrate system

components

Coding and Testing Complete system tests

23
 Example – Agile & Iterative Method
Day 6 Activities

• Core Process 6: Complete System Testing

and Deploy System
• Perform system functional testing
Identify the problem
• Perform user acceptance testing
• Possibly deploy part of system
Plan

Discover problem or need

Design the system

Build, test, and integrate system

components

Complete system tests

Testing

24
 Class Activity

• In the class form groups and practice the following exercise:

• It is so hot in Dubai during summer months, standing and

waiting for a bus at a bus station which does not have A/C can
be very difficult. In your groups come up with an innovative
idea that could help solve this problem. Make sure to talk
about how you would go about implementing such a
technological innovation.

• Be prepared to share your answers with the rest of the class.

• You have 20 minutes.

• Note: This is an introductory chapter. Tools mentioned in this

25
lesson will be taught in depth in later chapters.
 References
• Satzinger, J., Jackson, R. & Burd, S. (2016) Systems Analysis And Design In A
Changing World. 7th Edition, Boston, Mass. Cengage Learning.
• 8 Software Development Models: Sliced, Diced and Organized in Charts
https://www.scnsoft.com/blog/software-development-models Accessed 10
September 2023.

26
 THANK YOU
Any Question ?

27