LECTURE 1:

INTRODUCTION TO
SYSTEM ANALYSIS
AND DESIGN
Lecture by: Dr Salome Maro
8th Nov 2021
RECAP: LECTURE PLAN
 Lecture Time : Every Monday 16:00 – 18:00
 Plan:

Activity Time
Lecture 16:00 – 16:45
Break 16:45 – 17:00
Lecture 17:00 – 17:45
Q&A 17:45 – 18:00
LOGISTICS OF THE COURSE
 Interruptions with questions and comments are welcome during the
lecture
 Questions regarding the course or anything outside the topic of the day
should be reserved until the end of the lecture
 The lecture applies a flipped classroom mode
 I encourage everyone to participate fully in the lectures
TODAY’S CLASS
 Information Systems and Examples
 Major failures of famous systems
 What is System Analysis?
 Who is a System Analyst?
 Software development lifecycle
WHAT IS A SYSTEM?
 Derived from Greek word Systema, which means an
organized relationship between any set of components to
achieve some common cause or objective.

 A system is “an orderly grouping of interdependent

components linked together according to a plan to achieve
a specific goal.”
EXAMPLES OF SYSTEMS
 A system is “an orderly grouping of interdependent components linked
together according to a plan to achieve a specific goal.”
 Examples:
 Telephone systems
 Radio system
 Conveyer belt systems
 Etc.
INFORMATION SYSTEMS
 An information system is a collection of interrelated components that
collect, process and store, and provide as output the information
needed to complete a business task.
 Examples of information systems are:
 Course registration system
 Online shopping system
 Online banking system

 Most of the software out there is information systems software

 Large organizations own and operate hundreds or even thousands of
information systems.

Information systems make organizations run!

CLASS
ACTIVITY:
EXAMPLES
OF
INFORMATIO
N SYSTEMS
THE BAD NEWS
 30% of large IT projects are cancelled before completion

 50% of IT projects are over-budget by more than 200%

 The majority of completed projects deliver 60% or less of prescribed functionality

 Many delivered information systems are under-used because they don’t meet user
needs and/or expectations

 Legacy systems are a serious and growing bottleneck to organizational evolution

INFORMATIO
N SYSTEMS
HORROR
STORIES
HTTPS://YOUTU.BE/N6PWATVLQCY
INFORMATION SYSTEMS
HORROR STORIES
 FoxMeyer Health Care Service Company:
 Launched a project to create an ERP system for the company
 Budget was $65 million (TZS 149 B)
 Expected to save $40 million per year (TZS 92 B)

 Results:
 Project’s actual cost was $100 million (TZS 230 B)
 Only saved half the expected amount
 The company had to file for bankruptcy

 This failure was the result of poor planning and implementation.

CLASS ACTIVITY: SYSTEM
FAILURES IN TZ
 Air port control system
 Tanesco LUKU system
 Aris3
 DART – Ticket system
 You can think of more
WHY IS THIS COURSE
IMPORTANT?
 Most errors (54%) are detected after coding and testing.

 Almost half of all errors in software (45%) are in requirements and design.

 Most errors made during requirements analysis are non-clerical (77%)

 Requirements errors can cost up to 100 times more to fix than

implementation errors
WHAT IS SYSTEM ANALYSIS?
 The collection of notations, methodologies and tools used to gather details and
analyze a problem situation prior to information system design and implementation.

 Systems analysis must ensure that the proposed information system meets user
needs, can be delivered on time, and can be updated inexpensively.

 Solves problems in "getting the systems analysis right", such as ill-defined

situations, ambiguities, inconsistencies, mixing requirements with design.

Remember, finding and fixing a fault after software delivery is 100x more
expensive than finding and fixing it during systems analysis or early design
phases
NOTATION, METHODOLOGIES AND TOOLS

Systematic information system development is based on notations, methodologies and

associated tools.

• Notation: used to describe the information captured during different phases; notations
range from natural language, to diagrammatic notations (such as entity-relationship or
data flow diagrams), or formal languages, such as programming languages.

• Methodology: this determines the process whereby the software developer creates,
refines, analyzes and validates a software system; methodologies are often project- or
situation-specific.

• Tools: are software applications that support the creation, refinement, analysis and
validation of software (such as CASE tools).
 As a user I want to be able to …

NOTATION
Notation: used to describe the
information captured during different
phases; notations range from natural
language, to diagrammatic notations
(such as entity-relationship or data
flow diagrams), or formal languages,
such as programming languages.

IF total_amount is
greater than 100,000
THEN apply 10%
discount
METHODOLOGY
 Methodology: this determines the
process whereby the software
developer creates, refines, analyzes
and validates a software system;
methodologies are often project- or
situation-specific.
TOOLS
 Tools: are software applications that support the
creation, refinement, analysis and validation of
software (such as CASE tools).

 A computer-aided software engineering (CASE)

tool is a software package that
provides support for the design and
implementation of information systems.
WHAT IS SYSTEMS
DESIGN?
The specification of the information system to be built. This specification includes:
 The software architecture of the proposed system, including interfaces between the
system modules.
 The function of each module, i.e., what does each module do, I.e., transformations it
performs on its inputs.
 The database(s) that will be part of the information system, stored in database
management systems (DBMSs) or in files.
 User interfaces that need to be in place to facilitate use of the system by different user
groups
 The software platform on which the system will run, i.e., operating system, DBMS,
programming language, etc...
 The hardware configuration on which the system will run, including network interfaces.
WHO IS A SYSTEM ANALYST?
 “To provide technical support in analyzing, designing and
implementing information systems within the foundation and
will also assess their suitability and liaise with end users,
software vendors and programmers in order to achieve
intended outcomes of the foundation. He/she will serve as a
change agent who will identify the foundations improvements
needed, design systems to implement these changes, and
train and motivate others to use the systems”
-- ICT Systems Analyst (BMF)
ROLE OF SYSTEM ANALYST
 Consultant: often hired from outside, specifically for a project; this means that
she brings a new perspective but will not be familiar with company
culture/politics.
 Supporting Expert: knows well relevant hardware and software technologies,
advises on alternative hardware/software configurations.
 Change Agent: will be expected to suggest alternative business processes
which improve on current practices (business reengineer).

Systems analysis is, above all, a problem-solving

activity
SKILLS OF A SYTEM
ANALYST

Technical Business Analytical

Ethical (fair,
honest,
Interpersonal Management maintain
confidentiality…
)
TYPES OF SYSTEM
ANALYSTS
 Large organizations build project teams that incorporate
several analysts with different, but complementary, roles.
 In smaller organizations, one person may play several of these
roles.
TYPES OF SYSTEM
ANALYSTS
 System analyst
 Business analyst
 Requirements analyst
 Infrastructure analyst
 Change management analyst
 Project manager
 TYPES OF SYSTEM ANALYSTS –
LMS FORUM (DEADLINE 10TH NOV)
FORUM
AWARDS
First responders : Awarded to
first 3 respondents with
meaningful answers!

1. Edgar Nyandoro
2. Joseph Maziku
3. Michael Mushi
MORE BADGE AWARDS
 Most replies to others posts (meaningful replies)
 Examples of replies that are NOT meaningful: Yes, No, maybe, of course, great,
thanks…

Related to assignments:
 Early submissions (Early bird badge) – 24 hours before deadline
 Ontime submissions (Within 24 hours of the deadline)

 More to come!
KEY IDEAS
Systems analyst is a key person

 analyzing the business

 identifying opportunities for improvement

 designing information systems to implement

these ideas.
KEY IDEAS
 Many failed systems were abandoned because analysts tried
to build wonderful systems without understanding the
organization.

 The primary goal is to create value for the organization.

SHORT BREAK
 THE SYSTEMS
DEVELOPMENT LIFE
CYCLE
WHAT IS SYSTEM
DEVELOPMENT LIFECYCLE?
 Defines the general steps that are taken to build software
 Defines responsibilities of each team member during each step
of phase.
 Process of gradual refinement
 Some steps may overlap but generally define phases of the
project
 If some steps are not successful, the project may fall back to
an earlier step.
SYSTEMS DEVELOPMENT
LIFE CYCLE
Planning

Implementatio
Analysis
n

Design
SDLC: PLANNING
1. Project Initiation
 Develop a system request
 Conduct a feasibility analysis

2. Project Management
 Develop work plan
 Staff the project
 Control and direct the project

Why should we build this system?

SDLC: ANALYSIS
1. Develop analysis strategy
2. Gather requirements
3. Develop a system proposal

What should the system do for us?

Who will use the system?
Where and when will it be used?
SDLC: DESIGN
1. Develop a design strategy
2. Design architecture and interfaces
3. Develop databases and file specifications
4. Develop the program design

How will we build the system?

SDLC: IMPLEMENTATION
1. Construct system – Coding and testing
2. Install system
3. Implement a training plan for the users
4. Establish a support plan

Build the system!

PUTTING THE SDLC
TOGETHER
 Each phase consists of steps that lead to specific
deliverables
 The system evolves through gradual refinement
 Once the system is implemented, it may go back into
a planning phase for its next revision, a follow-on
system, or maintenance releases
PROCESSES AND
DELIVERABLES
Process Product
Project Plan
Planning

System Proposal
Analysis

System
Design
Specification

New System and

Implementation
Maintenance
Plan
 DIFFERENCES WITH THE
VIDEO ON LMS?
Planning

Implementati
Analysis
on

Design
QUESTIONS?
NEXT: SOFTWARE
DEVELOPMENT
METHODOLOGIES
To do, before the lecture:

 Read Chapter 2 of the course book (Page 51 to 61)
 Watch a video about a software development methodology
called Scrum

 Remember the 2nd Lecture will also be a flipped classroom.