Scribd
Upload
4 views2 pages

Analysis Stage Assignment

The System Analysis Stage Summary outlines the critical phase of evaluating existing systems to identify gaps between current capabilities and user needs. Key objectives include determining information needs, assessing the current system, defining intended outputs, and identifying necessary resources. The document emphasizes the importance of clarity, user involvement, and efficiency in system analysis to guide subsequent development stages.

Uploaded by

ellfaysal22
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views2 pages

Analysis Stage Assignment

The System Analysis Stage Summary outlines the critical phase of evaluating existing systems to identify gaps between current capabilities and user needs. Key objectives include determining information needs, assessing the current system, defining intended outputs, and identifying necessary resources. The document emphasizes the importance of clarity, user involvement, and efficiency in system analysis to guide subsequent development stages.

Uploaded by

ellfaysal22
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Khalil Faisal - CBS6/0101/24

System Analysis Stage Summary


Introduction
-​ The analysis stage in System Analysis and Design (SAD) is a critical phase where the
existing system is evaluated to identify gaps between current capabilities and
organizational/user needs.

Objectives of System
1.​ Determine Information Needs:
●​ Identify what data the organization and its users require.
2.​ Assess Current System:
○​ Evaluate existing processes, inputs, outputs, and resources.
3.​ Define Intended Outputs:
○​ Specify deliverables the new system must produce.
4.​ Resource Identification
○​ Determine hardware, software, and human resources needed.
5.​ Capability Mapping
○​ : Establish system functionalities to meet organizational goals.

Key Activities in System Analysis


1.​ Organizational Environment Analysis
-​ Evaluate information needs of stakeholders (customers, suppliers, regulators).
-​ Study the organization’s structure, management, and external interactions.
2.​ Current System Evaluation
-​ Analyze strengths, weaknesses, cost-effectiveness, and alignment with goals.
-​ Document inputs, processes, outputs, storage, and controls of the existing
system.
3.​ Requirement Analysis
-​ Gather user requirements through interviews, surveys, or workshops.
-​ Define inputs, outputs, procedures, and activity levels for the new system.
4.​ Statement of Requirements
-​ Prepare a document outlining system goals, cost-effectiveness, transferable
components, and gaps in the current system.
Tools and Techniques
1.​ Data Flow Diagrams (DFDs):
●​ Graphically represent processes, data flows, and storage to illustrate the
system’s functionality.
●​ DFDs are developed from a general overview (Level-0) to detailed sub-processes
(Levels 1 and 2).
2.​ Flowcharts:
●​ Visualize step-by-step processes within a system, including decision points and
data flows.
3.​ Decision Trees:
●​ Map out decision-making processes and conditions in a systematic tree format.

4.​ Data Dictionary:


●​ A repository documenting all elements within the system, such as data flows and
storage, to ensure consistent communication and design

Organizational and Present System Analysis

Organizational Analysis
●​ Focus Areas:
-​ Management structure (centralized vs. decentralized).
-​ Business activities (core vs. support functions).
-​ Existing IT infrastructure (cloud vs. on premise systems).
●​ Case Study: A university transitioning to online learning needs to analyze faculty tech
literacy and student accessibility.

Present System Analysis

●​ Components:
-​ Inputs: Data sources (e.g., IoT sensors in a manufacturing plant).
-​ Processes: Conversion mechanisms (e.g., ERP software automating payroll).
-​ Outputs: Reports, alerts, or physical products.
-​ Storage: Databases, cloud repositories.
-​ Controls: Security protocols, audit trails.
-​ Challenges: Legacy systems with outdated codebases or siloed data.

Functional Requirements Analysis


●​ Steps:
1.​ Elicitation: Use cases (e.g., "As a manager, I need real-time budget tracking").
2.​ Specification: Document requirements in tools like JIRA or Confluence.
3.​ Validation: Prototyping or mockups to confirm alignment with user needs.
●​ Example:
-​ Input: Employee timesheets (Excel upload).
-​ Process: Automatically calculate overtime hours.
-​ Output: Payroll summary sent to HR.

Importance and Benefits


1. Clarity: Provides a clear understanding of system requirements.
2. User Involvement: Enhances collaboration between analysts and stakeholders.
3. Efficiency: Reduces development time by avoiding rework.
4. Guidance: The statement of requirements serves as a blueprint for subsequent stages.
5. Cost-Effectiveness: Identifies reusable components, minimizing redundant investments.

You might also like