STATISTICAL ANALYSIS WITH SOFTWARE APPLICATION
CHAPTER 01: Introduction to System Analysis and Design
Overview of System Analysis
System Development Life Cycle (SDLC)
Role of System Analysts
1. Overview of System Analysis
What is System Analysis?
System analysis is the process of studying and understanding a system’s components and
operations to identify problems and design improvements. It involves gathering information,
analyzing data flows, and recommending solutions to optimize performance.
Importance of System Analysis:
Improves business processes and system efficiency.
Helps organizations meet user needs accurately.
Reduces system failures and enhances quality.
Facilitates better decision-making through data analysis.
Key Concepts in System Analysis:
1. System – A set of interacting components working together toward a common goal
(e.g., an inventory management system).
2. Subsystem – A smaller, self-contained component of a larger system (e.g., order
tracking within an inventory system).
3. Process – A sequence of actions or operations transforming inputs into outputs (e.g.,
user data being processed to generate reports).
4. Information System – A system that collects, processes, stores, and disseminates
information for decision-making (e.g., a payroll system).
Types of Systems:
1. Open System – Interacts with its environment (e.g., online shopping platforms).
2. Closed System – Operates in isolation (e.g., a standalone accounting application).
3. Manual System – Performed by humans (e.g., paper-based inventory records).
4. Automated System – Uses technology (e.g., barcode scanning systems).
2. System Development Life Cycle (SDLC)
The System Development Life Cycle (SDLC) is a structured process for planning, creating,
testing, and deploying an information system. It ensures systematic development and
reduces project risks.
Phases of SDLC:
1. Planning Phase:
Objective: Define project goals and assess its feasibility.
Tasks:
o Identify business problems and opportunities.
o Conduct feasibility studies (technical, economic, legal, operational, and
schedule).
o Develop a project plan (timeline, resources, deliverables).
Example: A retail company needs a system to manage customer orders. The planning
phase involves defining system requirements and assessing costs.
2. Analysis Phase:
Objective: Understand business needs and gather requirements.
Tasks:
o Conduct interviews, surveys, and observations.
o Document functional (what the system should do) and non-functional
(performance, security) requirements.
o Analyze current systems (strengths, weaknesses, and areas for improvement).
Tools Used:
o Data Flow Diagrams (DFD) – Visualize how data moves through the system.
o Entity-Relationship Diagram (ERD) – Illustrates database relationships.
Example: Analysts interview employees to gather requirements for a new payroll
system.
3. Design Phase:
Objective: Create technical specifications based on analysis findings.
Tasks:
o Design system architecture (hardware, software, databases).
o Develop user interfaces (UI/UX).
o Create process models (data flow diagrams, system flowcharts).
Types of Design:
o Logical Design – Focuses on system functionality.
o Physical Design – Details hardware and software implementation.
Example: Design screens for employee data entry and define how the payroll system
calculates wages.
4. Development (Implementation) Phase:
Objective: Build and code the system based on the design specifications.
Tasks:
o Write and compile code.
o Create databases and integrate components.
o Conduct unit testing (testing individual modules).
Example: Developers code an online registration system using Python and SQL.
5. Testing Phase:
Objective: Ensure the system meets specified requirements and functions correctly.
Types of Testing:
o Unit Testing – Tests individual modules.
o Integration Testing – Checks combined modules.
o System Testing – Evaluates the entire system.
o User Acceptance Testing (UAT) – Ensures the system meets user expectations.
Example: Test whether the payroll system accurately calculates tax deductions.
6. Deployment (Implementation) Phase:
Objective: Install and roll out the system for end-users.
Tasks:
o Migrate data from the old system.
o Train end-users and provide user manuals.
o Monitor the system’s initial performance.
Deployment Strategies:
o Direct Cutover – Immediate switch to the new system.
o Parallel – Run both old and new systems simultaneously.
o Phased – Implement the system in stages.
Example: A bank implements a new loan processing system while offering user
training.
7. Maintenance Phase:
Objective: Ensure the system continues to function correctly after deployment.
Tasks:
o Fix bugs and errors.
o Apply software updates and security patches.
o Enhance features as needed.
Example: Updating the payroll system to comply with new tax laws.
Common SDLC Models:
1. Waterfall Model – Sequential and linear; each phase is completed before the next
begins.
o Best for: Small, well-defined projects.
2. Agile Model – Iterative and flexible; involves regular user feedback and continuous
improvement.
o Best for: Complex, rapidly changing projects.
3. Spiral Model – Combines iterative development with risk analysis.
o Best for: High-risk projects requiring frequent evaluation.
3. Role of System Analysts
System analysts bridge the gap between business needs and technical solutions. They play a
crucial role in the SDLC process.
Key Responsibilities of System Analysts:
1. Requirement Gathering: Collect information from stakeholders.
2. System Design: Create models and specifications for the new system.
3. Documentation: Maintain records such as user manuals and technical reports.
4. Communication: Act as a liaison between users, management, and technical teams.
5. Problem-Solving: Identify and resolve system issues.
6. Quality Assurance: Ensure the system meets business and technical standards.
Skills Required for System Analysts:
Analytical thinking and problem-solving.
Communication and interpersonal skills.
Technical knowledge (programming, databases).
Project management capabilities.
Attention to detail and documentation skills.
System Analyst’s Role in SDLC:
Planning: Assist in defining the project scope.
Analysis: Identify business needs and prepare requirement documents.
Design: Help create system models and workflows.
Development: Work with developers to ensure correct implementation.
Testing: Validate system accuracy and user satisfaction.
Deployment: Support system roll-out and user training.
Maintenance: Address ongoing issues and improvements
