System Analysis Flashcards

1
Q

Order of creating a new Computer System

A
  1. Analysis
  2. Design
  3. Development and Testing
  4. Implementation
  5. Documentation
  6. Evaluation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Analysis

A
  1. Researching the existing system
  2. Recording information about the current system
  3. System Specification
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Methods of researching the existing system

A
  1. Questionnaires
  2. Interviews
  3. Observations
  4. Examination of existing documents
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Questionnaires

A

Prepared questions are given to users of the system and they are left with the user to complete. They focus on simple questions like yes or no answers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Advantages of Questionnaires

A
  1. Questions are answered quickly
  2. Fairly cheap to carry out
  3. Answers are honest because they are annonymous.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Disadvatages of Questionnaires

A
  1. People often dont complete or return them.
  2. You can get incorrect data if they dont understand the question.
  3. It is hard to ask very technical or specific questions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Interviews

A

They take place face to face and usually involve more detailed questions than questionnaires. The interviewer talks with different people at different levels of the business and they might be asked different questions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Advantages of Interviews

A
  1. Questions can be explained if misunderstood.
  2. Complex questions can be asked.
  3. You get a full set of data because the person has no choice but to answer all the questions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Disadvantages of Interviews

A
  1. They take more time to complete
  2. They are more expensive because employees are taken out of their work hours.
  3. Answers might not be honest because they dont remain annonymous.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Observations

A

A system analyst sits and watches someone using the current system, this way they can log and make notes about different facts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Advantages of Observations

A
  1. Analyst can see exactly what the system fails in and what it does well.
  2. Not as expensive because employees arent taken from their work space.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Disadvantages of Observation

A
  1. Person being watched might feel uncomfortable and work different than normally.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Looking at the current system’s documentation

A

The system analyst looks through the paperwork for the current system which contains the information needed to implement the new system.
Paperwork includes technical documentation, payroll systems and list of stock items to be stored in the new system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Advantages of looking at the current system’s documentation

A
  1. It can save time because there are copies of previous analysis.
  2. You see existing inputs, outputs and processing.
  3. The analyst can predict the size of the system needed by looking at the amount of data it will need to handle.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Disadvantagges of looking at the current system’s documentation

A
  1. Time consuming to look through all the paperwork
  2. The analyst needs to be paid for the time they spend looking at the documentation.
  3. Time is wasted if the documentation isnt relevant to the new system.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Recording and analysing information about the current system

A
  1. Inputs and outputs need to be identified and process the current system.
  2. Problems are identified.
  3. User inforamtion and requirements for the new system are needed.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

System Specification

A
  1. Need to identify suitable hardware and software for the new system.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Design

A

Documents, files, forms/inputs, reports/outputs and validation are to be designed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What to design in design phase

A
  1. Designs to solve any problems
  2. Data capture forms and screen layouts
  3. Report layouts and screen displays
  4. Validation routines
  5. Required data/file structures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Validation checks

A
  1. Range check
  2. Length check
  3. Character check
  4. Format check
  5. Limit check
  6. Presence check
  7. Consistency check
  8. Check digit
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Range check

A

Checks if data is between acceptable values

22
Q

Length check

A

Checks if data contains the required number of characters

23
Q

Character check

A

Checks that the input data doesnt contain invalid character.

24
Q

Format check

A

Checks that data is in a specific format

25
Q

Limit check

A

Similar to range check but only one of the limits is checked

26
Q

Presence check

A

Checks if data is actually present and hasnt been missed out

27
Q

Consistency check

A

Checks if fields correspond with each other

28
Q

Check digit

A

Looks at an extra digit calculated from the digits of a number and then put on the end of the number

29
Q

Verification Checks

A
  1. Double entry

2. Visual check

30
Q

Double Entry

A

Data is entered twice by two different people. The computer compares the two entries and lets the user know if it finds any differencess.

31
Q

Visual Check

A

The person enters data nto the computer carfully comparing what they have entered with the data in the original document.

32
Q

Developent and Testing

A
  1. Testing Designs
  2. Testing Strategies
  3. Improvements needed as a result of testing
33
Q

Testing designs

A
  1. Data file structures are created and tested.
  2. Validation routines are created and tested.
  3. Input and output methods are created and tested.
34
Q

Testing Strategies

A
  1. Testing each module is made to ensure each one functions correctly on its own.
  2. Now the system needs to be completely tested (all modules together).
35
Q

Normal Data

A

Data is acceptable or valid, having an expected value

36
Q

Extreme data

A

Data at the limits of acceptability or validity.

37
Q

Abnormal Data

A

Data outside the limits of acceptability or validity.

38
Q

Live Data

A

Used to test the system after it has been installed into the customer’s workplace.
It is data that is actually used in the company.

39
Q

Implementation Methods

A
  1. Direct Implementation
  2. Parallel Running
  3. Pilot Implementation
  4. Phased Implementation
40
Q

Direct Implementation

A

The old system is stopped overnight and the new system introduced immediately.

41
Q

Advantages/Disadvantages of Direct Implementation

A

The benefits are immediate

The method can be disastrous if the new system fails.

42
Q

Parallel running

A

The old and new systems are run side by side for a time until everyone gets used to it.

43
Q

Adv/Dis of parallel running

A

The staff learns to use it gradually but they are required to run both at the same time.

44
Q

Pilot Implementation

A

The system is introduced into part of the company and its performance assesed.

45
Q

Adv/Dis Pilot Implementation

A

If the new system fails only one part of the company is affected.
It is more expensive than direct changeover.

46
Q

Phased Implementation

A

Initially only part of the new system is introduced. When this proves to work properly the next part is introduced until the old system is fully replaced.

47
Q

Adv/Dis Phased implementation

A

You ensure that the system works perfectly but you need to evaluate each phase one by one which is expensive.

48
Q

Documentation

A
  1. User Documentation

2. Technical Documentation

49
Q

User Documentation

A

It is designed to help users know how to use the software or system.

  1. How to log in / out
  2. How to save files
  3. How to search
50
Q

Technical Documentation

A

It helps programmers and analysts who make improvements to the system or repair and maintain it.

  1. Input formats
  2. Program listing and coding
  3. File structures
  4. Hardware and software requirements.
  5. Purpose of the system
51
Q

Evaluation

A

It is necssary to do some evaluation and carry out maintainance if necessary.

52
Q

Evaluation Strategies

A
  1. Compare the solution with the original task requirements
  2. Identify limitations and necessary improvements to the system
  3. Evaluate the users’ resposes to the results of testing the system