Section 7 - The systems life cycle Flashcards

1
Q

What does the analysis look at?

A
Current problems
Problem to be solved by new system
What does the user want 
Identify inputs, processing and outputs
User and information requirements of new system (what tasks it should be able to do)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the methods of researching an existing system?

A

Observation
Interviews
Questionnaires
Examination of existing documents

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

Observation

A

An analyst observes somebody using the current system

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

Advantages + disadvantages of observation

A

ads:
Can see exactly what is going well

disads:
Person might feel uncomfortable → work differently

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

Interviews

A

Face to face, talks to people at various levels of the business, detailed questions

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

Advantages + disadvantages of interviews

A

ads:
Questions can be explained
Questions can be changed to suit different people

disads:
Expensive to carry out
Takes longer

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

Questionnaires

A

Prepared questions given to users, left to compete (paper/digital)

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

Advantages + disadvantages of questionnaires

A

ads:
Questions can be answered quickly
Fairly cheap

disads:
Unclear questions cannot be explained
Incorrect data if people misunderstand

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

Examination of existing documents

A

Looking at paperwork for current system

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

Advantages + disadvantages of examining existing documents

A

ads:
Allows analyst to predict size of system needed
Can see existing inputs, processing and outputs

disads:
Time consuming
Expensive

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

What is ‘requirements specification’?

A

Systems analysts specifies a list of requirements for new system

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

What are ‘designs’ for?

A

the new system have a lot of thoughts put into them to try and reduce faults at a later stage.

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

What are the things that are designed?

A
  1. Data entry screens (how data can be entered in system (e.g text boxes, drop menus)
  2. User-interface layouts (what will things - menus, searching look like
  3. Printed outputs (what will printed outputs look like)
  4. Screen-based outputs (what will outputs on screen look like)
  5. Structures to store data (e.g. for databases, how table will be designed)
  6. Data validation methods (how will system prevent incorrect data from being entered)
  7. Data verification methods (How will system check data entered is correct)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the four stages of development?

A
  1. Creating data/file structures
  2. Creating validation routines
  3. Creating input methods (e.g. user interface)
  4. Creating output formats
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What do validation checks/rules make sure of?

A

Validation checks/rules make sure that only the correct data can be entered into system

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

How are systems created?

A

System developed from lines of code (using code then creating interface)

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

How are data structures tested?

A

Entering data that should be accepted

Purposely entering data that should not be accepted

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

What are input methods?

A

A system that allows users to enter data into the system is known as data entry forms

19
Q

What are two types of system outputs?

A

On screen

Printouts (hard copies)

20
Q

How are system outputs created?

A

Report invoices
Pay slips
etc.

21
Q

Why is it important that testing takes place?

A

It must be tested to make sure that it works correctly

22
Q

Examples of modules that should be tested

A

Data structures - do tables hold data correctly?
Validation rules
Input screens
Output screens

23
Q

How to test for the whole system?

A

Make sure that all the individual modules work with each other correctly

24
Q

What is ‘normal data’?

A

data which should be accepted and pass the test without any problems (in this example any numbers between 1 and 5)
E.g. the numbers 1,2,3,4, or 5 should be accepted

25
What is 'extreme data'?
data on the border of what the system will accept | E.g. In the same scenario, 1 or 5 would be used to test the borderline data
26
What is 'abnormal data'?
Data that should not be accepted by the system | E.g. data anything than 1,2,3,4,5 should be tested
27
What is 'live data'?
data that is actually used by the company’s customer | All modules would be tested with real-life data that the company actually uses
28
What is 'implementation'?
To install the system ready to use
29
Direct changover
Old system stops getting used one day, new system starts being used the next (very fast)
30
Advantages + disadvantages of direct changover
ads: Takes minimal time and effort Can be used immediately disads: New system fails, no backup system, data lost Staff have to be trained to use new system before installed
31
Parallel running
Old system + new system run alongside each other for period of time (data input into both old + new producing two sets of results)
32
Advantages + disadvantages of direct changover
ads: If anything wrong with new system, old system = backup Outputs can be compared to see if new system is running correctly disads: Takes a lot of time and effort
33
Pilot running
New system piloted (trialled) in one part of business, if successful = introduced to all business/organisation
34
Advantages + disadvantages of pilot running
ads: All features can be fully tested Something goes wrong, only small part of organisation is affected Staff who were part of pilot scheme can teach other staff disads: For the department doing the the pilot, there’s no backup
35
Phased implementation
New system introduced in phases (stages, or steps), gradually replacing parts of old system until new system has taken over
36
Advantages + disadvantages of phased implementation
ads: Allows users to gradually get used to the new system Staff training can be done in stages disads: If systems is broken or crashes, no back up
37
What is 'technical documentation'?
Created for future developers of the system (explains how system was made)
38
What is included in technical documentation?
Purpose of system (problem that system solves) Hardware requirements (hardware needed to run system - e.g. processor speeds Software requirements Memory (RAM) requirements (lowest + recommended amount of RAM needed to run system Copies of all system designs (designs for input screens and outputs screens described) Copies of system flow charts (how data will flow through new system) Explanations of file structures (tables) used - table's field names, data types, etc. Programming language used to code the system (make it easier to hire people in future) Listings of the code (how code joins together + annotations that explain what code does) Details of system bugs User interface designs Input formats - kind of data system accepts Output formats - what kind of data system produces
39
Why is 'user documentation' needed?
Created for the benefit of anyone who is expected to use the system
40
What is included in user documentation?
The purpose of the system - what the system can be used for Limitations of the system Hardware requirements - listing of hardware user needs to run the system Operating system required - which operating systems can be used to run the system (Windows, MAC OS etc.) How to open load the system How to login and logout of system How to search for system data How to input new data How to amend data How to sort data How to save files How to print files How to handle system errors/meaning of error messages Frequently asked questions (FAQs) Troubleshooting guides - how to identify what has gone wrong, what can be done Help guides/Tutorials - help user to learn how to use the main features of system Glossary of terms
41
Why is it important to evaluate a system?
see if the system is doing the job it was designed to do. see if the system is working well with minimum errors. see if the staffs can use the system properly.
42
How is an evaluation carried out?
Comparing the system against the initial requirements Evaluating user's experiences Identifying limitations of the new system Identifying system improvements
43
What are some of the final improvements?
Error correction Add functionality Performance improvement