Notes to Help You Do Well on Assignments

The intent of the information on this page is to help you better understand the ideas you saw in the text or in lectures so yo can structure your assignments in a clear fashion. These notes will hopefully help you get started in how to tackle the problems and how to present the material in your reports.

Topics covered on this page:

What is a system analyst?

General Problem-Solving Approach

Seven Fact-Finding Methods

Classes of Information Systems

The PIECES Problem-Solving Framework

Four Tests for Feasibility

Requirements


What is a system analyst?

A systems analyst studies the problems and needs of an organization to determine how people, data, processes, communications, and information technology can best accomplish improvements for the business. When information technology is used, the analyst is responsible for:


General Problem-Solving Approach


Seven Fact-Finding Methods

  1. sampling of existing documentation, forms, databases
  2. research and site visits
  3. observation of the work environment
  4. questionnaires
  5. interviews
  6. prototyping
  7. joint requirements planning


Classes of Information Systems


The PIECES Problem-Solving Framework

Pthe need to improve performance
Ithe need to improve information (and data)
Ethe need to improve economics, control costs, or increase profits
Cthe need to improve control or security
Ethe need to improve efficiency of people and processes
Sthe need to improve service to customers, suppliers, partners, employees, etc.


Four Tests for Feasibility

1. operational feasibility - measures how well the solution will work in the organization, how people feel about the system/project

2. technical feasibility - measures the practicality of a specific technical solution and the availability of technical resources and expertise

3. schedule feasibility - measures how reasonable the project timetable is

4. economic feasibility - measures cost-effectiveness of a project/solution


Requirements

Criteria: consistent, complete, feasible, required, accurate, traceable, verifiable

Functional requirement: = a function or feature that must be included in an IS in order to satisfy the business need and be acceptable to the users

Non-functional requirement: = a description of the features, characteristics, and attributes of the system as well as any constraints that may limit the boundaries of the proposed solution

Types of non-functional requirements:

An ambiguous requirements statement: "Create a means to transport a single individual from home to place of work"

Validation: activity that checks the rquirements definition document for accuracy, completeness, consistency, and conformance to standards.


more to be added...