Unit 7 new Flashcards
1
Q
Stages of systems life cycle:
A
1) Analysis of current system.
2) Design.
3) Testing.
4) System implementation.
5) Documentation.
6) Evaluation.
2
Q
Methods of researching an existing system:
A
1) Interviews.
2) Observation.
3) Questionnaires.
4) Examination of existing documents.
3
Q
Advantages of research method: Interviews.
A
i. Allows analyst to talk to people using the system.
ii. Can find out practical issues.
iii. Follow up questions can be asked.
4
Q
What is research method: Interviews?
A
Talking to people who use the system already.
5
Q
What is research method: Obeservation?
A
Watching what is going on.
6
Q
What is research method: Observation?
A
Watching what is going on.
7
Q
What is research method: Questionaries?
A
Questions with a choice of answers.
8
Q
What is research method: Examination of existing documents?
A
Viewing already collected information from documents to make a proper analysis.
9
Q
Advantages of research method: Observation:
A
i. Gathers real life details in depth.
10
Q
Advantages of research method: Questionaries:
A
i. Can be completed online.
ii. Answers are recorded automatically.
iii. Recorded and analyzed by software.
iv. Analyst and worker do not need to be available at the same time.
v. More truthful.
11
Q
Advantages of research method: Examination of existing documents:
A
Collection of new document is not needed.
12
Q
Disadvantages of research method: Interviews:
A
i. Workers may feel stressed as they are being interrogated.
13
Q
Disadvantages of research method: Observation.
A
i. People don’t work normally if they are being watched.
14
Q
Disadvantages of research method: Questionnaires.
A
i. People may not take it seriously.
15
Q
Disadvantages of research method: Examination of existing documents
A
i. May be difficult for someone from outside to understand.
16
Q
Technical documentation contents:
A
1) Purpose of system.
2) Limitations of system.
3) How to install and run system.
4) Program flowchart.
5) Program language and listing.
6) System flowchart.
7) List of variables used.
8) File structure.
9) Hardware and software requirements.
10) Input and output format.
11) Sample and test runs.
12) Validation routines.
17
Q
Importance of efficiency of system:
A
The system was made to ensure the tasks of the business are being solved more efficiently and quickly. If the system makes the company or employees take longer to complete the task, that means the system was a failure.
18
Q
Characteristics of the existing system that will be analyzed:
A
1) Data input and output.
2) How data is processed.
3) Problems with the system.
19
Q
Things shown in system specification:
A
1) The purpose of the system.
2) Data that needs to be input and output.
3) How the data needs to be processed.
4) Performance indicators such as the time it should take for a user to carry out a particular task.
20
Q
What are the things design should show?
A
1) File/data structure.
2) Input formats.
3) Output formats.
4) Validation rules.
21
Q
Importance of validation routines:
A
Invalid data can cause a system to behave unexpectedly or stop. If the data entered into a system is incorrect, the output will also be wrong.
22
Q
Factors to change from one system to another:
A
1) Hardware.
2) Data files.
3) Training.
23
Q
Explain system change factor: Hardware.
A
It is possible old hardware might work, but it is unlikely. The business may have to be shut down to install hardware.
24
Q
Explain system change factor: Data files:
A
May be necessary to employ data entry staff to make sure data is entered properly.
25
Explain system change factor: training
If they are familiar with a computerized system already, they may not need training
26
Training methods for system change:
a. Using a tutor.
b. Put all the lessons in company intranet for employees to see in their own time.
27
Advantages of phased implementation:
1) No implementation problems.
2) Lesson learnt from early implementation makes it easier to implement later stages.
3) Allows users to adjust to new system gradually
4) Staff training can be done in different stages.
28
Disadvantages of phased implementation:
1) May be confusing.
2) Data produced by old system may not be compatible.
3) Expensive as two systems run together.
29
Contents of user document.
1) Purpose of system.
2) Limitations of system.
3) Hardware and software requirements.
4) How to install and run system.
5) Error handling.
6) How to save a file.
7) How to print data.
8) How to access, edit and delete data.
9) Input and output formats.
10) Sample/test runs.
11) Frequently asked questions.
12) Glossary of terms.
30
Systems life cycle:
Series of stages that are worked through during the development of a new IT system or to improve a new one.
31
Analysis:
Detailed examination of something for a specific purpose.
32
Questionnaire:
Questions with a choice of answers to carry out a survey.
33
Documentation:
Written or printed information like a presentation, spreadsheet, report, database.
34
Requirement specification:
A document listing to all the functions the system is expected to do.
35
System specification:
List of all the software and hardware required by the new system.
36
Design:
Process of defining the elements of a system.
37
File/data structure:
The way in which the different data items will be stored.
38
Input format:
How data will be entered into the system.
39
Output format:
How the results of processing a data will be presented.
40
Validation rules:
Routines to check if data entered by user meets specific requirements.
41
Top-down design:
Decomposition of a system into smaller parts in order to comprehend its compositional sub-systems.
42
Bottom-up design:
Smallest sub-systems are designed first then combined into progressively larger units.
43
Data structure:
A way of sorting and managing data.
44
Record:
Consists of all the field about an individual instance of an entity in a database.
45
Entity:
A thing recognized as being capable of an independent existence which can be identified uniquely.
46
Field:
The item of information about an entity.
47
Table:
A collection of rows and columns forming cells that are used to store data in a structured manner.
48
Data capture form:
A document used for capturing data.
49
Transcription:
The transfer of data from one medium to another.
50
Database queries:
Searches made on the data held in a database to find one with a particular specification.
51
Valid:
Data that has passed validation test.
52
Validation routines:
Routines to check that the data entered meets the specified requirements.
53
Range check:
A validation rule to ensure the data is between a minimum and maximum value.
54
Character check:
Validation rule to ensure that only certain characteristics are entered.
55
Length check:
Check which ensures that the data entered is no longer than a specified maximum number of characters.
56
Type check:
A validation rule to ensure that the correct data type has been entered.
57
Format check:
A validation rule to ensure the characters entered are in a particular order or pattern.
58
Input mask:
A string of characteristics that indicates the format of valid input values.
59
Presence check:
A validation rule to ensure that data is entered.
60
Check digit:
An extra value that is calculated from the entry and is sometimes added to it.
61
Testing:
Checking and using samples and ensuring things are as they should be.
62
Test strategy:
A set of guidelines explaining how the testing will be carried out.
63
Modules:
Part of a computer program that carries out a particular function.
64
Functions:
A self-contained section of code with a module.
65
Final testing (terminal testing):
Tests carried out on the whole system has been completely developed.
66
Test plan:
A detailed document on how testing will be carried out.
67
Test design:
Detailed description of a particular task listing test data.
68
Normal data:
Data that would normally be expected to be entered.
69
Remedial action:
Steps taken to correct an error.
70
Test data:
Data that will be used to test a system.
71
Extreme data (boundary data):
Minimum and maximum values that should be accepted by the system.
72
Abnormal data:
Data that should normally not be accepted by the system.
73
Live data:
Real life data that has been used when the old system was running.
74
Live system:
A system tha is being used in real life.
75
Implementation:
The act of starting to use a new system.
76
Direct changeover:
Implementation where old system is shut down and new system is started up.
77
Phased implementation:
Where one part of the system is changed but some parts continue to function with the old system.
78
Pilot running:
New system is trialed in just one part of the organization.
79
Parallel running:
Both new and old systems running at the same time.
80
Documentation:
Official information about a system.
81
Technical documentation:
Documentation about details about structure of the system and required software and hardware.
82
System manager:
The person who oversees the system and is responsible for ensuring it works correctly.
83
Programming language:
The language used to make commands for the system.
84
Program code:
Sets of commands and instructions and the rules of how to use them.
85
System flowchart:
Diagrams using symbols to display how data flows in a computer system.
86
Variable:
A section of computer memory used to store data.
87
Technical documentation:
Information about the system that a technician or future developer needs.
88
User documentation:
Information about the system that is needed by people that will use the system.
89
Evaluation against original task requirements:
If the system does not live up to the tasks that it was made for, that means the problem has not been solved.
90
Limitations:
Restrictions that prevent something from working correctly.
91
Efficiency:
The amount of work that has to be done to carry out a particular task.
92
Ease of use:
How easy it is to perform a task.
93
Appropriateness:
How suitable or fitting something is.
94
Explain technical documentation content: Purpose of system.
the problem that the system will solve.
95
Explain technical documentation content: Limitations of system
what the system is not able to do.
96
Explain technical documentation content: How to install and run system
how to install, run and restart system.
97
Explain technical documentation content: Program language and listing
language used and functions explained.
98
Explain technical documentation content: File structure.
define the data types, and show the files used by system.
99
Explain technical documentation content: List of variables used
include the names of all variables.
100
Explain technical documentation content: Program flowchart
logical structure of the system.
101
Explain technical documentation content: System flowchart
how data flows through system.
102
Explain technical documentation content: Hardware and software requirements.
hardware required to run the system properly.
103
Explain technical documentation content: Input and output format.
types of data acceptable by the system.
104
Explain technical documentation content: Validation routines.
information about different validation rules used to test the system.
105
Explain technical documentation content: Sample and test runs
details and information about tests and sample runs.
106
Explain the importance of validation routines.
Invalid data may lead to a system to behave unexpectedly or may even cause the system to stop working.
107
Explain the functionality of validation routines.
It ensures that the data is reasonable and matches the criteria.
108
What is the importance of validation routines?
Invalid data may lead to a system to behave unexpectedly or may even cause the system to stop working.
109
What is the functionality of validation routines?
It ensures that the data is reasonable and matches the criteria.
110
What are the types of validation rules?
(1) Range check.
(2) Character check.
(3) Length check.
(4) Type check.
(5) Format check.
(6) Presence check.
(7) Check digit.
111
What is the functionality of test strategy?
The approach to be taken for testing can be selected during the development or after completion, the test strategy needs to be able to check each function, module and the whole system with different types of information. The test strategy ensure that all data flows properly and smoothly without errors and makes it easier to solve errors.
112
What are the factors tested by validation routines?
(1) Data and file structures such as tables and fields.
(2) Input formats.
(3) Output formats.
113
What are the details to show for each test?
(1) What is being tested.
(2) The test data being used.
(3) Expected outcomes.
(4) Actual outcomes.
(5) Space to describe remedial actions.
114
What are the types of data that can be used for tests?
(1) Normal data.
(2) Extreme data.
(3) Abnormal data.
(4) Live data.
115
What are the methods of system instillation?
(1) Direct changeover.
(2) Phased implementation.
(3) Pilot running.
(4) Parallel running.
116
How to properly install system with direct changeover?
All workers must be trained, system must be fully tested and all files must be uploaded.
117
How to properly install system with phased implementation?
Implementation different parts and units of the system gradually until it has all been replaced or implementing the new system in different parts of the organization until the entire organization is using the new system.
118
What are the advantages of direct changeover?
(1) Quick to do.
(2) Little time and effort.
119
What are the disadvantages of direct changeover?
Upon failure, normal work will not happen until issues have been resolved.
120
What is the functionality of evaluation?
If the system does not satisfy requirements, the problem has not been solved.
121
What are the limitation and improvement from evaluation?
Evaluations will lead to a list of required changes and fixes in the system that will need to be implemented in the next version of the system.
122
What is the importance of proper system?
Proper system justifies the use of proper and more expensive components along with memory requirements.
123
What is the importance of design stage?
Overall structure of the system with details of the software are specified and planned.
124
What are the things to be planned in designed stage?
(1) File and data structure.
(2) Input format.
(3) Output format.
(4) Validation routine.
125
Explain the importance of file and data structure in a system
Files are stored in memory and storage devices and the data needs to be structured properly so that it can be accessed by the system and relationships can be found between the data.
126
What are the things that need to be prepared before implementing a new system?
(1) Hardware.
(2) Data files.
(3) Training.
127
What is the importance of ensuring proper hardware before changeover?
Check if the old hardware is good enough.
128
What is the importance of ensuring data files hardware before changeover?
It may be necessary to employ data entry staff temporarily to ensure data is being entered properly.
129
What is the importance of ensuring proper training before changeover?
Staff may need to be trained to ensure they can use the new system properly.
130
What are the methods of training staff for new system?
(1) Tutor.
(2) Online.
131
What is the advantage of using tutor to train staff for new system?
(1) Staff can ask questions.
(2) Organization can ensure staff has done training.
132
What is the disadvantage of using tutor to train staff for new system?
Staff are not working while training sessions are held.
133
What is the advantage of using internet to train staff?
(1) Firm can run normally.
(2) Staff learn at their own time.
(3) Staff learn at their own speed.
(4) Staff can skip lessons they know.
(5) Staff can redo lessons they are confused in.
134
What is the disadvantage of using internet to train staff?
(1) Takes up the time on staff.
(2) No proper way to ensure all staff members have done training.
135
How to properly install new system with pilot running?
System is trialed in a single part of the organization and if successful, it is then used in the entire organization.
136
What is the advantage of pilot running?
(1) Problems can be more easily identified.
(2) Staff from trail can train other staff.
137
What is the disadvantage of pilot running?
(1) Expensive to run two systems at once.
(2) Difficult to keep both systems synchronized.
138
How to properly implement with parallel running?
Old system runs alongside the new one until there is confidence in the new one.
139
What are the advantages of parallel running?
(1) If the new system shows errors, the old one can be used.
(2) Outputs from both systems can be compared.
140
What are the disadvantages of parallel running?
(1) May be expensive to run both systems at the same time.
(2) Difficult to keep systems synchronized.
