CSC 321

SYSTEM ANALYSIS AND DESIGN

(SAD)
MODULE-1:
Introduction to Systems and Development
Methodologies

Week 2:
Systems and Information Systems

Lecturer:
Awoseyi A. A.
 LEARNING OUTCOME
❑Define and describe constitutes a system, components and
types, such as:
❑Information systems,
❑Management systems,
❑and transaction processing systems.

❑Explain the role and importance of systems analysis and

design in:
❑Development
❑and Improvement of organizational processes.

❑Identify and outline the

❑Qualities, tasks, and responsibilities of a systems analyst,
❑Role in translating business needs into technical solutions.

2
 Learning Outcome
❑Differentiate between types of systems:
❑Centralized, decentralized, multi-user, and networked systems,
❑understand their applications in various real-world contexts.

❑Illustrate how systems are structured, including:

❑key elements like inputs, processes, outputs, and feedback mechanisms,
❑Through simple diagrams or examples.

❑Relate systems analysis and design concepts to practical

scenarios,
❑Discuss their application to solve common problems within an organization or
department.
 OVERVIEW OF SAD
❏ Roles of A System Analyst:

❏ Task of A System Analyst:

❏ Attributes of System Analyst:

❏ Skill Required for System Analyst:

4
 SYSTEM DEVELOPMENT
System Development Life Cycle (SDLC):
❑ SDLC is a structured approach used for developing information systems.
❑ It provides a systematic process for
❑ Planning,
❑ Creating, Testing, and Deploying information systems,
❑ Ensuring that high-quality systems are delivered that meet or exceed customer
expectations.
❑ The SDLC consists of distinct phases, each with specific tasks and deliverables.
❑ Understanding these phases helps in managing the complexity of system
development projects and improving project success rates:

5
 Phases of the SDLC:
❏ Planning Phase:
❏ Purpose: To define the scope, objectives, and feasibility of the project.
❏ Activities: Project initiation, feasibility analysis, project scheduling, resource
allocation.
❏ Deliverables: Project charter, feasibility study report, project plan.
❏ Analysis Phase:
❏ Purpose: To gather detailed requirements and analyze business needs.
❏ Activities: Requirement gathering (interviews, surveys, document analysis),
requirement analysis, requirement documentation.
❏ Deliverables: System requirements specification (SRS), use cases, process
diagrams.

6
 Phases of the SDLC:
❏ Design Phase:
❏ Purpose: To create detailed system designs based on requirements gathered.
❏ Activities: System architecture design, database design, interface design,
specification of system components.
❏ Deliverables: Design documents, data models, UI/UX prototypes.
❏ Implementation (Development) Phase:
❏ Purpose: To build and develop the system based on design specifications.
❏ Activities: Coding, integration of system components, development of databases,
creation of system interfaces.
❏ Deliverables: Source code, database schema, developed system modules.

7
 Phases of the SDLC:
❏ Testing Phase:
❏ Purpose: To ensure the system works as intended and is free of defects.
❏ Activities: Unit testing, integration testing, system testing, user acceptance testing
(UAT).
❏ Deliverables: Test plans, test cases, test scripts, defect reports..
❏ Deployment Phase:
❏ Purpose: To deliver the system to the users and make it operational.
❏ Activities: System installation, data migration, user training, deployment planning.
❏ Deliverables: Deployed system, user manuals, training materials.
❏ Deliverables: Source code, database schema, developed system modules.

8
 Phases of the SDLC:
❏ Maintenance Phase:
❏ Purpose: To monitor, support, and enhance the system post-deployment.
❏ Activities: Bug fixing, system updates, performance tuning, new feature
integration.
❏ Deliverables: Maintenance reports, system updates, enhancement specifications.
❏ Types of SDLC Models:
❏ Different Types of SDLC models have been developed to address various project
requirements and constraints. Each model has its
❏ Strengths
❏ Weaknesses
❏ Use Case

9
 Phases of the SDLC: Waterfall Model
❑ Description:
❑ A linear and sequential approach
❑ Each phase must be completed before the next one begins.
❑ Strengths:
❑ Simple,
❑ Easy to understand,
❑ Suited for projects with clear requirements.
❑ Weaknesses:
❑ Inflexible,
❑ Difficult to accommodate changes,
❑ High risk if initial requirements are not well-understood.

10
 Phases of the SDLC: Waterfall Model
❑ Use Case: Suitable.
❑ Projects with well-defined requirements and low uncertainty
❑ E.g: Personal Budget Application

11
 Phases of the SDLC: V-Model
(Validation and Verification Model):
❑ Description:
❑ An extension of the Waterfall model
❑ Includes corresponding testing phases for each development stage.
❑Strengths:
❑ Emphasizes verification and validation
❑ Ensures early detection of defects.
❑ Works for small to medium projects where requirements are well understood
❑Weaknesses:
❑ Similar to Waterfall,
❑ It can be rigid and
❑ Challenging to handle changes.

12
 Phases of the SDLC: V-Model
❑ Use Case: Suitable.
❑ Projects where quality and reliability are critical
❑ E.g: Banking Application

13
 Phases of the SDLC: Iterative Model
❑ Description:
❑ Develops the system through repeated cycles (iterations)
❑ This allows for refinement through each iteration.
❑Strengths:
❑ Flexible, allows for changes and refinements,
❑ Reduces risk through early iterations.
❑Weaknesses:
❑ Can lead to scope creep,
❑ Requires careful project management.
❑ May face integration challenges when combining features from different iterations
❑ Documentation can become complex due to multiple version updates

14
 Phases of the SDLC: Iterative Model
❑ Use Case: Suitable.
❑ Complex projects where requirements may evolve over time.
❑ E.g: Social Media Platform

15
 Phases of the SDLC: Spiral Model
❑ Description:
❑ Combines iterative development with risk assessment.
❑ Each iteration involves planning, risk analysis, engineering, and evaluation.
❑Strengths:
❑ Focuses on risk management, iterative refinement, and
❑ Client feedback.
❑ Good for large, complex, and high-risk projects
❑Weaknesses:
❑ Can be complex to manage,
❑ Requires significant risk assessment expertise
❑ Not cost-effective for small or low-risk projects and
❑ Time consuming.

16
 Phases of the SDLC: Spiral Model
❑ Use Case: Suitable.
❑ Large, high-risk projects where risk management is a priority.
❑ E.g: Healthcare Information System

17
 Phases of the SDLC: Agile Model
❑ Description:
❑ Emphasizes flexibility, collaboration, and customer feedback.
❑ Uses iterative cycles called sprints to develop system increments.
❑Strengths:
❑ Highly flexible, adaptive to changes,
❑ Focuses on customer satisfaction
❑ Direct customer involvement in the development process
❑Weaknesses:
❑ Requires strong team collaboration,
❑ Can be challenging in fixed-budget projects.
❑ Risk of scope creep due to constant requirement changes

18
 Phases of the SDLC: Agile Model
❑ Use Case: Suitable.
❑ Large, high-risk projects where risk management is a priority.
❑ E.g: Healthcare Information System

19