Week 1: Introduction to System Analysis & Design

Lecture Notes:

1. Definition and Importance of Systems Analysis and Design

A. Systems Analysis and Design

• Systems Analysis: The process of studying a system to understand its components,

interactions, and flow of information. It aims to identify and solve problems within the
system to improve its performance or functionality.

• Systems Design: The process of creating a blueprint for how a system will function. It
involves translating the requirements gathered during analysis into a plan for building
the system, specifying hardware, software, and network requirements, and designing
the user interface and system architecture.

B. Importance of Systems Analysis and Design

• Improves Efficiency: By identifying system problems and designing solutions,

systems analysis and design help improve the efficiency and effectiveness of business
processes.

• Reduces Costs: Proper design and analysis help identify the best approach to building
a system, thus reducing unnecessary expenditure during implementation.

1
 • Ensures Quality: Systems analysis and design focus on identifying and implementing
user requirements, ensuring the final product is of high quality and meets stakeholder
needs.

• Risk Management: A proper analysis and design process helps identify potential risks
and issues before they affect the project, leading to smoother project execution.

• Scalability: Well-designed systems are scalable, allowing for easy expansion and
integration with other systems in the future.

2. Overview of the Systems Development Life Cycle (SDLC)

A. Introduction to SDLC

The Systems Development Life Cycle (SDLC) is a structured approach to software

development, encompassing all stages of creating an information system, from the initial idea
to the final implementation and maintenance. It helps ensure that systems are developed in an
organized and efficient manner.

B. Phases of SDLC

1. Planning: This initial phase involves defining the scope, objectives, and constraints of
the system project. Feasibility studies (technical, operational, and financial) are often
conducted during this stage.

2. Analysis: In this phase, the system requirements are gathered from users and
stakeholders. The existing system (if applicable) is evaluated, and the new system's
specifications are defined.

2
 3. Design: The system's architecture, user interface, and database structures are planned.
Both high-level design (overall system architecture) and detailed design (specific
components and modules) are created.

4. Development: The actual coding or programming of the system takes place in this
phase. The design documents are converted into executable programs.

5. Testing: After development, the system is thoroughly tested to ensure it works as

expected. This includes unit testing, system testing, integration testing, and user
acceptance testing.

6. Implementation: The system is deployed into the live environment, where users begin
to interact with it. Training and support are provided to ensure a smooth transition.

7. Maintenance: After implementation, the system enters the maintenance phase, where
bugs are fixed, updates are made, and the system is optimized based on user feedback.

C. SDLC Models

• Waterfall Model: A linear approach where each phase must be completed before
moving to the next.

The Waterfall model is a traditional, linear approach to software development and project
management. It is characterized by a sequential, phase-by-phase progression, where each phase
is completed before moving on to the next one.

3
Key Characteristics of the Waterfall Model:

1. Linear progression: The project is divided into distinct phases, and each phase is
completed before moving on to the next one.
2. Predictive planning: The project plan is created at the beginning, and it outlines the
scope, timeline, and budget.
3. Sequential phases: The phases are completed sequentially, with no overlap between
them.
4. No iteration: Once a phase is completed, it is not revisited.

Phases of the Waterfall Model:

1. Requirements gathering: Collecting and documenting the project requirements.

2. Design: Creating a detailed design of the project.
3. Implementation: Developing the project.
4. Testing: Testing the project to identify defects.
5. Deployment: Deploying the project to production.
6. Maintenance: Maintaining and updating the project.

Advantages of the Waterfall Model:

1. Easy to manage: The linear progression makes it easy to manage and understand.
2. Predictable timeline: Predictive planning helps to create a predictable timeline.
3. Clear requirements: The requirements gathering phase ensures that the requirements
are clear and well-defined.

Disadvantages of the Waterfall Model:

1. Inflexible: The linear progression makes it difficult to make changes once a phase is
completed.
2. High risk: Predictive planning can lead to a high risk of project failure if the
requirements change.
3. Long development time: The sequential phases can lead to a long development time.

When to Use the Waterfall Model:

1. Well-defined requirements: When the requirements are clear and well-defined.

2. Small projects: When the project is small and simple.
3. Regulated industries: When working in regulated industries, such as finance or
healthcare, where predictability and stability are crucial.

4
 • Agile Model: An iterative approach focusing on collaboration and flexibility, with
frequent releases of working software.

The Agile model is an iterative and incremental approach to software development and project
management. It emphasizes flexibility, collaboration, and rapid delivery.

Key Characteristics of the Agile Model:

1. Iterative development: The project is divided into small, manageable chunks, and each
chunk is developed in a series of iterations.
2. Incremental delivery: The project is delivered in small increments, with each
increment building on the previous one.
3. Flexibility: The Agile model is highly flexible, and changes can be made at any stage
of the project.
4. Collaboration: The Agile model emphasizes collaboration between team members and
stakeholders.
5. Customer involvement: The customer is involved throughout the project, providing
feedback and guidance.

Agile Methodologies:

1. Scrum: A framework for managing and completing complex projects using iterative
and incremental practices.
2. Kanban: A visual system for managing work, emphasizing continuous flow and
limiting work in progress.
3. Lean: A methodology that aims to minimize waste and maximize value for the
customer.
4. _Extreme Programming (XP)_: A methodology that emphasizes technical practices
such as pair programming, continuous integration, and refactoring.

5
Advantages of the Agile Model:

1. Flexibility: The Agile model is highly flexible, and changes can be made at any stage
of the project.
2. Rapid delivery: The Agile model emphasizes rapid delivery, with working software
delivered in short cycles.
3. Improved quality: The Agile model emphasizes continuous testing and integration,
leading to improved quality.
4. Increased customer satisfaction: The Agile model involves the customer throughout
the project, leading to increased customer satisfaction.

Disadvantages of the Agile Model:

1. High overhead: The Agile model requires significant overhead in terms of meetings,
planning, and documentation.
2. Difficulty in predicting timelines: The Agile model makes it difficult to predict
timelines and budgets.
3. Requires skilled team members: The Agile model requires skilled team members who
are able to work independently and make decisions quickly.

When to Use the Agile Model:

1. Unclear or changing requirements: When the requirements are unclear or changing

rapidly.
2. High-risk projects: When the project is high-risk or has a high degree of uncertainty.
3. Projects with multiple stakeholders: When there are multiple stakeholders with
competing interests and priorities.

• Spiral Model: Combines iterative development with a focus on risk management,

allowing for repeated refinement of the system.

6
The Spiral model is a risk-driven software development process model that combines elements
of the Waterfall and Agile models. It was first introduced by Barry Boehm in 1988.

Key Characteristics of the Spiral Model:

1. Iterative development: The Spiral model involves iterative development, with each
iteration consisting of four phases.
2. Risk-driven approach: The Spiral model is a risk-driven approach, where the
development process is driven by the need to reduce and manage risks.
3. Combines Waterfall and Agile elements: The Spiral model combines elements of the
Waterfall and Agile models, allowing for a flexible and adaptable approach to software
development.

Phases of the Spiral Model:

1. Planning phase: Identify the objectives, constraints, and risks associated with the
project.
2. Risk analysis phase: Analyze the risks associated with the project and identify
strategies for mitigating them.
3. Engineering phase: Develop and test the software, using a combination of Waterfall
and Agile approaches.
4. Evaluation phase: Evaluate the software and the development process, identifying
lessons learned and areas for improvement.

Advantages of the Spiral Model:

1. Risk-driven approach: The Spiral model allows for a risk-driven approach to

software development, reducing the likelihood of project failure.
2. Flexible and adaptable: The Spiral model combines elements of the Waterfall and
Agile models, allowing for a flexible and adaptable approach to software
development.
3. Emphasizes continuous improvement: The Spiral model emphasizes continuous
improvement, with each iteration providing an opportunity to learn and improve.

Disadvantages of the Spiral Model:

1. Complex and difficult to manage: The Spiral model can be complex and difficult to
manage, particularly for large and complex projects.
2. Requires significant resources: The Spiral model requires significant resources,
including personnel, equipment, and budget.
3. Can be time-consuming: The Spiral model can be time-consuming, particularly if the
project involves multiple iterations.

When to Use the Spiral Model:

1. High-risk projects: The Spiral model is particularly suited to high-risk projects,

where the need to reduce and manage risks is critical.

7
 2. Complex projects: The Spiral model is also suited to complex projects, where the
need for a flexible and adaptable approach is important.
3. Projects with multiple stakeholders: The Spiral model can be used for projects with
multiple stakeholders, where the need to manage and mitigate risks is critical.

• V-Model: Similar to the waterfall model but emphasizes testing and validation at each
stage of development.

The V-Model is a software development process model that emphasizes the importance of
testing and validation in the development process. It is also known as the Verification and
Validation model.

Key Characteristics of the V-Model:

1. Verification and Validation: The V-Model emphasizes the importance of verification

(checking if the software meets the specifications) and validation (checking if the
software meets the user's needs).

8
 2. Sequential Phases: The V-Model consists of sequential phases, with each phase
building on the previous one.
3. Testing Emphasis: The V-Model places a strong emphasis on testing, with testing
activities occurring at each phase of the development process.

Phases of the V-Model:

1. Requirements Gathering: Gather and document the software requirements.

2. System Design: Create a high-level design of the software system.
3. Architecture Design: Create a detailed design of the software architecture.
4. Component Design: Create a detailed design of the individual software components.
5. Coding: Write the software code.
6. Unit Testing: Test individual software components.
7. Integration Testing: Test the integration of software components.
8. System Testing: Test the entire software system.
9. Acceptance Testing: Test the software to ensure it meets the user's needs.

Advantages of the V-Model:

1. Improved Quality: The V-Model's emphasis on testing and validation helps to ensure
that the software meets the required quality standards.
2. Reduced Defects: The V-Model's sequential phases and emphasis on testing help to
identify and fix defects early in the development process.
3. Increased Confidence: The V-Model's verification and validation activities help to
increase confidence in the software's ability to meet the user's needs.

Disadvantages of the V-Model:

1. Inflexible: The V-Model's sequential phases can make it difficult to accommodate

changes in requirements or design.
2. Time-Consuming: The V-Model's emphasis on testing and validation can make the
development process more time-consuming.
3. Resource-Intensive: The V-Model's testing activities can require significant
resources, including personnel, equipment, and budget.

When to Use the V-Model:

1. Safety-Critical Systems: The V-Model is well-suited for safety-critical systems, such

as aerospace, healthcare, or financial systems.
2. High-Risk Projects: The V-Model is also suitable for high-risk projects, where the
consequences of failure are significant.
3. Regulated Industries: The V-Model can be used in regulated industries, such as
finance or healthcare, where compliance with regulatory requirements is critical.

9
3. The Role of a System Analyst

A. Responsibilities of a System Analyst

• Requirement Gathering: System analysts communicate with stakeholders to

understand their needs and document system requirements.

• Problem Identification: They analyze existing systems to identify inefficiencies,

bottlenecks, or areas that need improvement.

• System Design: They assist in designing the system, ensuring it meets user
requirements and is technically feasible.

• Documentation: System analysts create detailed system specifications, functional

requirements, and user documentation.

• Liaison Between Users and Developers: Analysts act as intermediaries between users
and the development team, ensuring that both parties understand each other's needs.

• Testing and Evaluation: They assist in testing the system, identifying bugs, and
ensuring it meets the requirements set out during the analysis phase.

• Project Management Support: They may also assist in managing the project timeline,
resources, and costs.

B. Skills Required

• Strong problem-solving abilities

• Analytical thinking and attention to detail

• Excellent communication skills (both written and verbal)

• Knowledge of both technical and business environments

• Proficiency in tools and methodologies for system design and analysis

10
4. Introduction to Types of Information Systems

A. Transaction Processing Systems (TPS)

• These systems handle the collection, storage, and processing of transaction data.
Examples include banking systems, inventory management systems, and order
processing systems.

• Key Characteristics:

o A high volume of transactions

o Real-time processing

o Reliability and accuracy are crucial

o Examples: ATM systems, online transaction systems, payroll systems.

B. Management Information Systems (MIS)

• MIS provides managers with reports and tools to make decisions based on the data
collected by TPS.

• Key Characteristics:

o Helps in strategic decision-making

o Generates periodic reports on operational performance

o Analyzes trends and patterns in business data

o Examples: Sales reporting systems, human resources management systems.

C. Decision Support Systems (DSS)

• DSS assists in complex decision-making by providing analytical tools and models to

evaluate different options.

• Key Characteristics:

o Analyzes large volumes of data to assist in decisions

o Uses mathematical models, simulations, and statistical analysis

o Used in planning and decision-making in areas like finance, marketing, and

logistics

o Examples: Financial planning systems, and marketing analysis tools.

11
D. Expert Systems

• These systems emulate the decision-making abilities of a human expert in a specific

domain.

• Key Characteristics:

o Encodes expert knowledge into rules and databases

o Provides advice or recommendations based on user input

o Examples: Medical diagnostic systems and legal advisory systems.

E. Enterprise Resource Planning (ERP) Systems

• ERP systems integrate various business functions, such as accounting, inventory

management, human resources, and sales, into one unified system.

• Key Characteristics:

o Helps streamline business operations and improve efficiency

o Facilitates data sharing across departments

o Examples: SAP, and Oracle ERP systems.

F. Knowledge Management Systems (KMS)

• KMS facilitates the capture, distribution, and management of knowledge within an

organization.

• Key Characteristics:

o Encourages collaboration and sharing of expertise

o Assists in decision-making by leveraging organizational knowledge

o Examples: Knowledge sharing platforms, and intranet-based knowledge

repositories.

Summary:

In this introductory week, students are exposed to the fundamental concepts of systems analysis
and design, the importance of the SDLC in guiding software development projects, and the
critical role of a system analyst. Students also explore various types of information systems
and their relevance to business and organizational operations. By the end of the week, they
should clearly understand how these systems support decision-making and operations within
organizations.

12
Multiple Choice Questions (MCQs):

1. Which of the following is NOT a phase of the Systems Development Life Cycle
(SDLC)? a) Planning
b) Development
c) Testing
d) Retirement
Answer: d) Retirement

2. Which type of information system is primarily designed to help managers make

decisions based on data analysis? a) Transaction Processing System
b) Management Information System
c) Decision Support System
d) Expert System
Answer: c) Decision Support System

3. What is the main role of a system analyst? a) To program the system

b) To gather requirements and design the system
c) To manage the project budget
d) To conduct user training
Answer: b) To gather requirements and design the system

4. Which of the following is an example of a Transaction Processing System (TPS)?

a) Payroll system
b) Financial planning tool
c) Inventory management system
d) Human resources management system
Answer: a) Payroll system

Essay Questions:

1. Explain the importance of systems analysis and design in developing an information

system. Provide examples of how a well-designed system can improve efficiency and
reduce costs.

2. Describe the phases of the Systems Development Life Cycle (SDLC). How do these
phases contribute to the successful development of an information system?

3. Compare and contrast Transaction Processing Systems (TPS) and Decision Support
Systems (DSS). Provide examples of when each system would be used in an
organization.

13