Systems Analysis Course

• Home
• 1.What is a System
  • Introduction
  • Parts of a System
• 2.System Lifecycle
  • Project Management
  • Project Lifecycle
  • Check Understanding
  • SDLC Comparison
  • Exercise
• 3.Feasibility Study
  • Sections
  • Exercise
• 4.CostBenefit Analysis
• 5.System Investigation
  • Introduction
  • Methods
  • Identify method
  • Exercise
• 6.Data Flow Diagrams
  • Introduction
  • Video
  • Definitions
  • Steps to create
  • Exercises
• 7.Relational Diagrams
  • Terminology
  • Examples
  • Exercise
  • Using a DFD level1
• 8.Data Dictionary
• 9.Design Specification
• 10.Creating a Test Plan

 

 

Lesson 5 - Investigation techniques

Assuming that the feasibility study indicates that a new system would be advantageous the next stage is to produce a detailed requirement specification.
The Systems Analysts job at this stage is to fully investigate and present the requirement information in as clear and unambiguous form as possible.

The Systems Analyst needs to decide who they need to contact, what they need to find out from them and how they will record the information they are given. Anyone who has an interest in the system under investigation is called a STAKEHOLDER.:

Stakeholders can be:.

o End users - those people that will use the system in order to do their job
o Managers - those people responsible for the department that will use the system
o Customers - those people that the system is being run for, usually their details will be stored in the system
o Experts - usually professionals who are expert in a particular buisness area eg. Accountant or Web designer.

When you have decided who you need to contact to gather your information for the new system, you then need to decide the METHOD of investigation that you will use.

Copyright JK Nichols 2009