System Analysis and Design : Initial Investigation and planning| Need Identification| fact finding|

Summary

The video explains the early stages of systems analysis and design: planning a system investigation, identifying user needs, and gathering facts about the current system. The goal is to define the problem accurately before proposing or building a replacement or improved system.

1. System Planning and Initial Investigation

• A system project needs a clear plan describing the steps to be taken and what the proposed system is expected to achieve.
• The initial investigation examines a request to develop, change, or improve a system.
• Its purpose is to determine whether the request is valid, whether the problem is understood, and whether further investigation or a feasibility study is warranted.
• Careful problem definition matters: an inaccurate description can lead to a solution that does not address users’ actual needs.

2. Recording and Reviewing a System Request

A request for a system change or improvement should capture relevant information, such as:

• The problem and the requested work.
• The date the request was submitted and, where relevant, the planned or completed work dates.
• Expected benefits and descriptions of required inputs and outputs.
• The requester’s name, job title, department, and contact details.
• The approving person’s name, title, and department, along with approval details.

Once submitted, the request is reviewed to decide whether it should proceed to further investigation.

3. Defining User Information Requirements

• Analysts must establish what information users need and what the system should do.
• Requirements can be difficult to determine because users may not know how to express their needs, may be unfamiliar with system capabilities, or may initially ask for unnecessary features.
• Requirements can also change during development, so they need to be revisited and refined.
• Users may describe a solution vaguely—for example, asking for “the same thing, but better”—rather than explaining the underlying problem.
• Analysts should distinguish essential needs from optional or unrealistic requests and help users focus on practical, valuable improvements.
• Human limits, such as the difficulty of handling too much information or articulating problems, should be considered during requirements work.

4. Strategies for Determining Requirements

The lecture presents several approaches:

• Ask users directly: Use questions to learn about their needs and problems.
  • Open-ended questions allow a range of answers and explanations.
  • Closed-ended questions seek a limited or specific answer.
• Use group discussion or a Delphi-style process: Gather responses from users, repeat or summarize the discussion, and look for areas of agreement.
• Study the existing system: Examine its information, outputs, decisions, and processes to understand what users currently rely on and where problems occur.
• Analyze decisions: Break complex problems into smaller issues, separating critical decisions from less important ones.
• Build a prototype: Create an initial working model for users to try. Gather feedback, revise it repeatedly, and use the results to clarify requirements for the final system.

5. Fact-Finding Methods

To understand the current system and verify requirements, analysts can use:

• Written documents: Review reports, forms, proposals, and other system records.
• On-site observation: Visit the organization and watch how work is actually performed.
• Interviews: Ask users and managers about system functions, workflow, difficulties, and desired changes.
• Questionnaires: Collect answers from multiple users using structured questions.

Fact-finding should be organized and evaluated. Analysts should draw conclusions and prepare findings for review and approval.

6. Documenting Processes and System Logic

The video mentions several tools for recording how a system works:

• Input/output descriptions show what information enters the system and what it produces.
• Flow diagrams or flowcharts represent the steps and movement of information.
• Decision tables organize conditions and the actions or outcomes associated with them, especially for complex decisions.

Speakers and Sources Featured

• Kumar, identified in the subtitles as an Assistant Professor at ICBM Deemed University, presenting a lecture on System Analysis and Design.
• Let’s learn Programming, the channel identified in the video metadata.