Chapter 15 (HL only): IT Systems in Organizations

0.0(0)
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/103

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

104 Terms

1
New cards
acceptance testing
Testing performed by the client and users as part of the handover process.
2
New cards
adaptive maintenance
Maintenance that changes software to make it work with a new software environment.
3
New cards
agile development
Development method that focuses on creating small, working parts of a project at regular intervals.
4
New cards
alpha testing
Initial testing of an IT system.
5
New cards
analyst
In project development, person who documents the current system, finding its problems and areas for improvement
6
New cards
attributes
Component of an Entity Relationship Diagram.
7
New cards
beta tester
Person who attempts to find bugs in software before it is released to customers.
8
New cards
beta testing
Testing of an IT system once all features have been added and only bugs need to be worked out.
9
New cards
bug tracking system
Used to track and manage bugs in a piece of software.
10
New cards
bugs
Errors in a computer program or system, hopefully found during testing.
11
New cards
business case
Analysis of the benefits and problems of a proposed IT project.
12
New cards
Capability Maturity Model Integration
Quality assurance method that describes an organisation's level of maturity.
13
New cards
cardinality
Property of a relationship in an Entity Relationship Diagram.
14
New cards
changeover
Moving from an old system to a new IT system.
15
New cards
client
Person or organisation who commissions an IT project.
16
New cards
CMMI
Quality assurance method that describes an organisation's level of maturity.
17
New cards
constraints
Limitations within which an IT system must work.
18
New cards
corrective maintenance
Maintenance that fixes bugs in software.
19
New cards
CP
Longest (slowest) path through a project's development, as determined by using a PERT chart.
20
New cards
Critical Path
Longest (slowest) path through a project's development, as determined by using a PERT chart.
21
New cards
Custom / bespoke software
Software created specific for an individual or organisation.
22
New cards
data collection
Used to find information about an existing system during the development of a new system.
23
New cards
Data Flow Diagram
Shows processes in a system and the flows of data between them.
24
New cards
data structure
The way the data within an IT system is organised and related.
25
New cards
database administrator
The person in an organisation who is responsible for setting up, maintaining, and monitoring the organisation's database(s).
26
New cards
delivery
Installing a new IT system at the client's premises.
27
New cards
deployment
Stage in the SDLC where the system is deployed at the client's site.
28
New cards
development manager
In project development, person who oversees programmers as they create the system specified in the design.
29
New cards
DFD
Shows processes in a system and the flows of data between them.
30
New cards
direct changeover
Immediate removal of an old system and complete replacement with a new IT system.
31
New cards
emulator
A computer program which simulates another type of computer, so that it can run programs designed for it.
32
New cards
end-user
Person who will use an IT project one it is finished.
33
New cards
entities
Component of an Entity Relationship Diagram.
34
New cards
entity relationship diagram
Shows the items of data stored in a system and the relationships between them.
35
New cards
ERD
Shows the items of data stored in a system and the relationships between them.
36
New cards
feasibility study
Examination of a proposed system to see if its creation is possible.
37
New cards
Frequently Asked Questions
A list of common problems that users experience, and their answers.
38
New cards
functional requirements
Specific features and functions that a proposed IT system must have.
39
New cards
Gantt chart
Used to chart the stages of a planned IT project and the people responsible for each stage.
40
New cards
handover
Point at which the developers of a system formally pass it to the client.
41
New cards
IDE
Set of programs used by system developers to create IT systems.
42
New cards
implementation
Stage in the SDLC where the system is created (programmed).
43
New cards
incident escalation
Moving a problem with an IT project to a higher level if it cannot be solved.
44
New cards
Incident management system
Used to keep track of problems and difficulties encountered in an IT system.
45
New cards
incident tracking system
Used to keep track of problems and difficulties encountered in an IT system.
46
New cards
information system (IS) managers
Person responsible for all IT purchases, deployments, and systems within an organisation.
47
New cards
installation
Installing a new IT system at the client's premises.
48
New cards
Integrated Development Environment
Set of programs used by system developers to create IT systems.
49
New cards
internal support
Support for an IT system provided within an organisation.
50
New cards
legacy system
An old, out of date IT system which is still used because it is essential to an organisation.
51
New cards
load testing
Testing of an IT system with the amount of work it can be expected to process in real world conditions.
52
New cards
maintenance
Alterations made to a system after it has been formally handed over.
53
New cards
milestones
Key points during project development, such as the completion of a stage.
54
New cards
network manager
The person responsible for the installation, configuration, and monitoring of an organisation's network.
55
New cards
non-functional requirements
Conditions that a proposed IT system must meet, such as working on certain hardware or giving results within a certain time.
56
New cards
off-the-shelf software
Software which is widely available and can be bought by anybody.
57
New cards
online lessons
A form of training delivered online.
58
New cards
organisational IT policies
Policies governing the appropriate use of IT, data integrity, security procedures, and other aspects of IT use with an organisation.
59
New cards
outputs
During analysis, a list of the results that a system must produce.
60
New cards
parallel running
Running the old system and the new system side by side.
61
New cards
perfective maintenance
Maintenance that changes software to incorporate new user requirements (or changed requirements).
62
New cards
PERT chart
Charting system to show the inter-dependencies in projects.
63
New cards
phase out
Gradually removing an old IT system from use.
64
New cards
phased changeover
One part of an organisation switches to a new IT system to test it, while others remain using the old system.
65
New cards
PMBoK
Project Management Body of Knowledge. A project management methodology.
66
New cards
preventative maintenance
Maintenance that changes software to avoid possible future problems.
67
New cards
PRINCE2
PRojects IN Controlled Environments 2. A project management methodology.
68
New cards
processes
During analysis, a list of the procedures a system must implement.
69
New cards
procurement
The act of acquiring the necessary items (software, hardware, staff) to develop an IT system.
70
New cards
programmer
A person who writes computer programs by following a design document.
71
New cards
project goals
Clear statement of the intentions of a proposed IT project.
72
New cards
project initiation document
Document used in PRINCE2 to describe the key features of an IT project.
73
New cards
project management methodology
Systems and techniques designed to encourage successful projects and avoid project failure.
74
New cards
project management software
Software to help plan, manage, and guide the process of IT project development.
75
New cards
project manager
Person with overall responsibility for an IT project.
76
New cards
project plan
Clear definition of the goals, scope, and schedule of a proposed IT project.
77
New cards
prototype interface
Early version of a user interface to get feedback about its effectiveness.
78
New cards
prototypes
An early version of a project, designed to get feedback from the client and users.
79
New cards
quality assurance methods
In project development, used to ensure the whole development team are following standardised best practises.
80
New cards
quality control processes
Processes to ensure code produced by programmers followed accepted best practices.
81
New cards
regression testing
Testing to ensuring changes to an IT system did not break any previously working functionality.
82
New cards
relationships
The links between separate items of data.
83
New cards
requirements specification
Clear list of the functional and non-functional requirements for a proposed IT project.
84
New cards
scope
Clear definition of the boundaries of an IT project.
85
New cards
SDLC
The stages in the life time of an IT system, from its first proposal, through its design and creation, to its eventual phasing out.
86
New cards
software testers
People who perform alpha, beta, and acceptance testing.
87
New cards
source code
Instructions that make up the software, entered by the programmer using a programming language.
88
New cards
SSADM
Structured Systems Analysis and Design Method. A project management methodology.
89
New cards
support
Staff who help users with problems they encounter while using an IT system.
90
New cards
support staff
Staff who train users and help them with problems as they occur
91
New cards
SWOT
Analysis method sometimes used when creating a business case.
92
New cards
system context diagram
High level DFD of a system.
93
New cards
System development lifecycle
The stages in the life time of an IT system, from its first proposal, through its design and creation, to its eventual phasing out.
94
New cards
technical documentation
Documentation intended for programmers and developers of an IT system.
95
New cards
test plan
List of all tests and test data that should be tried with a system.
96
New cards
training
Ensuring that users will be able to work with a new IT system.
97
New cards
tutorial
A document which explains how to perform key tasks, step by step.
98
New cards
user acceptance testing
Tests performed by a client before formally accepting an IT system from the developers.
99
New cards
user acceptance testing
Testing performed by the client and users as part of the handover process.
100
New cards
user documentation
Documentation intended for users of an IT system, helping them understand and use it.