5. The system Life Cycle Flashcards

1
Q

what is a system life cycle?

A

a structured process that guides the planning, creation, testing, and deployment of an information system

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

what does a system life cycle do?

A

Ensures systems are systematically developed, meeting needs of stakeholders, minimising risks and maximising efficiency

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

what’s the first stage and what’s its purpose?

A

analysis, Gather detailed requirements from stakeholders and analyse them to understand what the system should accomplish

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

what are research methods?

A

helps to analyse the current IT system in order to help understand the state of the current system

identify areas for improvement

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

what are the 4 research methods?

A

observations, interviews, questionnaires, existing documents

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

what is an observation?

A

Watching users interact with the current system to see how it acts/works

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

adv of observation

A

Reliable data
Inexpensive
Good for getting an overall picture of existing system

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

dis of observation?

A

People don’t always behave in the same way under observation

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

adv of questionnaire?

A

Quick
Inexpensive
Can be anonymous

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

dis of questionnaire

A

Can’t ask follow up questions
Low response rate
Answers might be vague

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

adv of interviews

A

Can monitor body language and facial queues
Gives employees an opportunity to

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

dis of interviews

A

Time consuming
Cannot remain anonymous
Employees may be uncomfortable and not give honest responses in fear of repercussions

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

adv of esixting docs?

A

Obtain information that can’t be obtained from other methods

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

dis of existing docs

A

Time consuming which can be costly

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

how to analyze the current system?

A

Inputs
Outputs
Processing
Problems
User requirements
Information requirements

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

what is drawn up from the results of the analysis

A

requirements specification

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

what’s the second stage and what is its purpose?

A

design
Develop architectural blueprints for the system, including database design, user interfaces, and system interfaces.

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

What are file/data structures?

A

Field names
Filed lengths
Data types
Primary keys

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

what’s a file?

A

A file consists of records and records are made up of fields
Each record is identified by its unique primary key field

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

what are different data types?

A

alphanumerical: combination of characters (letters or text) and numeric data
character:A single letter/symbol
text: Stores a combination of characters (letters, text, symbols, special characters etc.) and numeric data
boolean: Stores data in a Yes/No or True/False
numeric: Integers, Decimals,Currency
Date/Time

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

What are validation routines?

A

checks placed on data being entered to ensure it matches the design of the system

prevent errors and maintain data integrity

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

what is range check?

A

Ensures the data entered as a number falls within a particular range

For children aged between 5 and 10, checks to make sure numbers <5 and >10 are not accepted

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

what’s length check

A

Checks the length of a string

Password must be a minimum of 8 characters, checks to make sure the length is >=8

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

what’s type check

A

Check the data type of a field

Enter distance in whole miles, checks to make sure decimals are not accepted

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

whats format check

A

Ensures that the data has been entered in the correct format

Enter date of birth (DD/MM/YY), check to make sure the format is correct

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

what’s presence check

A

Looks to see if any data has been entered in a field

Enter your username ,check to make sure the filed has not been left blank

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

whats check digit

A

Check digits are numerical values that are the final digit of a larger code

Barcodes

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

What are input and output formats?

A

What are input and output formats?

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

examples of input formats

A

Having a user-friendly layout
Providing clear instructions
Using appropriate question types -
Using validation routines

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

examples of output formats

A

Screen layouts:
Report layouts:
Readability, visual appeal, and efficient use of space

31
Q

what’s the third stage and whats the purpose?

A

verify that the system meets all requirements, functions correctly, and is free of bugs through various testing methods.

32
Q

what are test designs

A

1.a method of testing a completed system to ensure all parts work as intended

2.Each module needs to be tested independently

3.Testing is done again once all modules are joined together

  1. The results of testing may indicate changes need to be made, testing is repeated once all changes have been made
33
Q

test design- data structures

A

Test all data is stored correctly

34
Q

test design- file structures

A

Test all data is stored in the correct format

35
Q

test designs- input formats

A

test that data can be entered correctly

36
Q

test designs- output formats

A

Tests that screen output and reports are in the correct format

37
Q

test designs- Validation routines

A

Tests that the system rejects unreasonable data being inputted

38
Q

what are test plans and what does it consist of?

A

Test data: specific data used for testing purposes
Expected outcomes: predicted results based on test data
Actual outcomes: results obtained from testing
Remedial action: steps taken to fix identified issues

39
Q

What is test data?

A

specific data used for testing purposes

40
Q

what are the 4 categories of test datas?

A

Normal
Extreme
Abnormal
Live

41
Q

what is normal data

A

data that should be accepted in the system
has a known outcome

42
Q

what is extreme data

A

data that is on the limits of what is acceptable

43
Q

what is abnormal data

A

outside of the limits of what is acceptable
should be rejected by the system

44
Q

what is live data

A

data from the old system used on the new system
has known outcomes, so it can be compared to the new system to ensure the new system works

45
Q

what’s the fourth stage and its purpose?

A

implementation
Deploy the system to the production environment and ensure all components work together in the live setting.

46
Q

system implementation?

A

a process that happens after a system has been fully tested and is working correctly

47
Q

how does implementation occur?

A

Data is transferred from old to new system
then system changeover

48
Q

what’s a changeover

A

changeover is moving from the old system to the new system

49
Q

what are the 4 ways a changeover can happen

A

Direct
Parallel
Pilot running
Phased

50
Q

what is direct changeover

A

The old system is replaced by the new system immediately

Used when quick implementation is necessary

51
Q

what is parallel running

A

Both old and new systems run simultaneously for a period before the old system is phased out

Used when a smooth transition with minimal risk is required

52
Q

what is pilot running

A

The new system is implemented in a small, controlled environment before full-scale implementation

Used when testing the new system in a real-world setting

53
Q

what is phased implementation

A

The new system is implemented in stages, with each stage replacing a part of the old system

Used when a gradual transition is preferred to minimise disruption

54
Q

adv of direct changeover

A

Fast implementation
Cost-effective as only one system is in operation

55
Q

dis of direct changeover

A

High risk of failure
No fallback
Users can’t be trained on the new system
No backup of the system

56
Q

adv of parallel running

A

Lower risk
Easy comparison of systems

57
Q

dis of parallel running

A

Time-consuming
Resource-intensive

58
Q

adv of pilot running

A

Low risk as only trialled in one department/centre/branch
Allows for fine-tuning
Staff have time to train with the new system
Few errors as it’s fully tested

59
Q

dis of pilot running

A

Slower implementation
Potential inconsistencies
Confusion as there are 2 systems in use
No backup for the department/centre/branch using the new system

60
Q

adv of phased implementation

A

Reduced risk
Easier to manage

61
Q

dis of phased implementation

A

Takes longer
Potential compatibility issues

62
Q

what is technical documentation?

A

detailed information on the system’s inner workings and programming for developers and IT staff

63
Q

what does technical documentation enables the system to be?

A

Maintained
Repaired
Updated

64
Q

Technical documentation includes:

A

Purpose of the system/program
Limitations
Program listing
Program language
Program flowcharts/algorithms
System flowcharts
Hardware & software requirements
File structures
List of variables
Input format
Output format
Sample runs/test runs
Validation routines

65
Q

what is user documentation?

A

instructions and guidance for end-users on how to operate the system

enables end-users to effectively use the system and overcome problems

66
Q

User documentation includes:

A

Purpose of the system
Limitations
Hardware & software requirements
Loading/running/installing software
Saving files
Printing data
Adding records
Deleting/editing records
Input format
Output format
Sample runs
Error messages
Error handling
Troubleshooting guide/helpline
Frequently asked questions
Glossary of terms

67
Q

what must you assess in order to evaluate a system?

A

The efficiency of the solution
The ease of use of the solution
The appropriateness of the solution

68
Q

what benefits do you get from evaluating a system?

A

identify limitations and propose improvements

69
Q

how to evaluate a system’s performance?

A

Resource usage
Time
Cost

70
Q

how to evaluate the ease of use?

A

1.user-friendly
2. accessible the solution is for its intended audience
3. system is easy to learn and use, 4. users can accomplish their tasks without difficulty

71
Q

how to evaluate the efficiency of the solution?

A
  1. is the system is operating optimally or if improvements could be made to its efficiency
  2. areas that may be consuming excessive resources or time,
72
Q

how to evaluate the appropriateness of the solution?

A
  1. Compare the implemented solution with the original task requirements.
  2. evaluate how well it meets the intended purpose
    3.Outline the initial objectives of the system and discuss how the solution addresses each one
  3. Highlight requirements that haven’t been fully met and discuss possible reasons for this
  4. Collect users’ responses to the results of testing the system
  5. identify limitations and propose improvements