Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

A-ICT- IB- Tom > IT organization > Flashcards

IT organization Flashcards

IT organization

1
Q

Development Personnel

A

1

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

information system (IS) managers

A

Person responsible for all IT purchases, deployments, and systems within an organisation.

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

analyst

A

In project development, person who documents the current system, finding its problems and areas for improvement

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

database administrator

A

The person in an organisation who is responsible for setting up, maintaining, and monitoring the organisation’s database(s).

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

development manager

A

In project development, person who oversees programmers as they create the system specified in the design.

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

network manager

A

The person responsible for the installation, configuration, and monitoring of an organisation’s network.

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

programmer

A

A person who writes computer programs by following a design document.

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

support staff

A

Staff who train users and help them with problems as they occur

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

Analysis Stage

A

2

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

business case

A

Analysis of the benefits and problems of a proposed IT project.

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

client

A

Person or organisation who commissions an IT project.

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

constraints

A

Limitations within which an IT system must work.

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

CP

A

Longest (slowest) path through a project’s development, as determined by using a PERT chart.

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

Critical Path

A

Longest (slowest) path through a project’s development, as determined by using a PERT chart.

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

data collection

A

Used to find information about an existing system during the development of a new system.

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

end-user

A

Person who will use an IT project one it is finished.

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

feasibility study

A

Examination of a proposed system to see if its creation is possible.

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

functional requirements

A

Specific features and functions that a proposed IT system must have.

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

Gantt chart

A

Used to chart the stages of a planned IT project and the people responsible for each stage.

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

milestones

A

Key points during project development, such as the completion of a stage.

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

non-functional requirements

A

Conditions that a proposed IT system must meet, such as working on certain hardware or giving results within a certain time.

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

organisational IT policies

A

Policies governing the appropriate use of IT, data integrity, security procedures, and other aspects of IT use with an organisation.

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

PERT chart

A

Charting system to show the inter-dependencies in projects.

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

project goals

A

Clear statement of the intentions of a proposed IT project.

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

project management methodology

A

Systems and techniques designed to encourage successful projects and avoid project failure.

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

project management software

A

Software to help plan, manage, and guide the process of IT project development.

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

project manager

A

Person with overall responsibility for an IT project.

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

project plan

A

Clear definition of the goals, scope, and schedule of a proposed IT project.

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

requirements specification

A

Clear list of the functional and non-functional requirements for a proposed IT project.

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

scope

A

Clear definition of the boundaries of an IT project.

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

SWOT

A

Analysis method sometimes used when creating a business case.

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

technical documentation

A

Documentation intended for programmers and developers of an IT system.

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

user documentation

A

Documentation intended for users of an IT system, helping them understand and use it.

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

Design Stage

A

3

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

attributes

A

Component of an Entity Relationship Diagram.

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

cardinality

A

Property of a relationship in an Entity Relationship Diagram.

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

Data Flow Diagram

A

Shows processes in a system and the flows of data between them.

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

data structure

A

The way the data within an IT system is organised and related.

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

DFD

A

Shows processes in a system and the flows of data between them.

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

entities

A

Component of an Entity Relationship Diagram.

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

entity relationship diagram

A

Shows the items of data stored in a system and the relationships between them.

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

ERD

A

Shows the items of data stored in a system and the relationships between them.

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

outputs

A

During analysis, a list of the results that a system must produce.

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

processes

A

During analysis, a list of the procedures a system must implement.

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

prototype interface

A

Early version of a user interface to get feedback about its effectiveness.

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

relationships

A

The links between separate items of data.

47
Q

system context diagram

A

High level DFD of a system.

48
Q

user interface

A

The part of a system that allows a user to interact with it.

49
Q

Implementation Stage

A

4

50
Q

alpha testing

A

Initial testing of an IT system.

51
Q

bugs

A

Errors in a computer program or system, hopefully found during testing.

52
Q

Capability Maturity Model Integration

A

Quality assurance method that describes an organisation’s level of maturity.

53
Q

CMMI

A

Quality assurance method that describes an organisation’s level of maturity.

54
Q

Frequently Asked Questions

A

A list of common problems that users experience, and their answers.

55
Q

implementation

A

Stage in the SDLC where the system is created (programmed).

56
Q

load testing

A

Testing of an IT system with the amount of work it can be expected to process in real world conditions.

57
Q

online lessons

A

A form of training delivered online.

58
Q

prototypes

A

An early version of a project, designed to get feedback from the client and users.

59
Q

quality assurance methods

A

In project development, used to ensure the whole development team are following standardised best practises.

60
Q

quality control processes

A

Processes to ensure code produced by programmers followed accepted best practices.

61
Q

software testers

A

People who perform alpha, beta, and acceptance testing.

62
Q

test plan

A

List of all tests and test data that should be tried with a system.

63
Q

training

A

Ensuring that users will be able to work with a new IT system.

64
Q

tutorial

A

A document which explains how to perform key tasks, step by step.

65
Q

user manual

A

A document which explains to users how to use a computer system.

66
Q

Testing Stage

A

5

67
Q

beta tester

A

Person who attempts to find bugs in software before it is released to customers.

68
Q

beta testing

A

Testing of an IT system once all features have been added and only bugs need to be worked out.

69
Q

bug tracking system

A

Used to track and manage bugs in a piece of software.

70
Q

handover

A

Point at which the developers of a system formally pass it to the client.

71
Q

user acceptance testing

A

Tests performed by a client before formally accepting an IT system from the developers.

72
Q

Installation Stage

A

6

73
Q

changeover

A

Moving from an old system to a new IT system.

74
Q

delivery

A

Installing a new IT system at the client’s premises.

75
Q

deployment

A

Stage in the SDLC where the system is deployed at the client’s site.

76
Q

direct changeover

A

Immediate removal of an old system and complete replacement with a new IT system.

77
Q

installation

A

Installing a new IT system at the client’s premises.

78
Q

parallel running

A

Running the old system and the new system side by side.

79
Q

phased changeover

A

One part of an organisation switches to a new IT system to test it, while others remain using the old system.

80
Q

Maintenance Stage

A

7

81
Q

adaptive maintenance

A

Maintenance that changes software to make it work with a new software environment.

82
Q

corrective maintenance

A

Maintenance that fixes bugs in software.

83
Q

incident escalation

A

Moving a problem with an IT project to a higher level if it cannot be solved.

84
Q

Incident management system

A

Used to keep track of problems and difficulties encountered in an IT system.

85
Q

incident tracking system

A

Used to keep track of problems and difficulties encountered in an IT system.

86
Q

internal support

A

Support for an IT system provided within an organisation.

87
Q

maintenance

A

Alterations made to a system after it has been formally handed over.

88
Q

perfective maintenance

A

Maintenance that changes software to incorporate new user requirements (or changed requirements).

89
Q

phase out

A

Gradually removing an old IT system from use.

90
Q

preventative maintenance

A

Maintenance that changes software to avoid possible future problems.

91
Q

regression testing

A

Testing to ensuring changes to an IT system did not break any previously working functionality.

92
Q

support

A

Staff who help users with problems they encounter while using an IT system.

93
Q

Development Approach and Methodologies

A

8

94
Q

acceptance testing

A

Testing performed by the client and users as part of the handover process.

95
Q

agile development

A

Development method that focuses on creating small, working parts of a project at regular intervals.

96
Q

PMBoK

A

Project Management Body of Knowledge. A project management methodology.

97
Q

PRINCE2

A

PRojects IN Controlled Environments 2. A project management methodology.

98
Q

procurement

A

The act of acquiring the necessary items (software, hardware, staff) to develop an IT system.

99
Q

project initiation document

A

Document used in PRINCE2 to describe the key features of an IT project.

100
Q

SSADM

A

Structured Systems Analysis and Design Method. A project management methodology.

101
Q

user acceptance testing

A

Testing performed by the client and users as part of the handover process.

102
Q

waterfall development

A

Development method that focuses on completing each stage of the SDLC for the entire project before moving onto the next.

103
Q

Misc Terms

A

9

104
Q

Custom / bespoke software

A

Software created specific for an individual or organisation.

105
Q

emulator

A

A computer program which simulates another type of computer, so that it can run programs designed for it.

106
Q

IDE

A

Set of programs used by system developers to create IT systems.

107
Q

Integrated Development Environment

A

Set of programs used by system developers to create IT systems.

108
Q

legacy system

A

An old, out of date IT system which is still used because it is essential to an organisation.

109
Q

off-the-shelf software

A

Software which is widely available and can be bought by anybody.

110
Q

SDLC

A

The stages in the life time of an IT system, from its first proposal, through its design and creation, to its eventual phasing out.

111
Q

source code

A

Instructions that make up the software, entered by the programmer using a programming language.

112
Q

System development lifecycle

A

The stages in the life time of an IT system, from its first proposal, through its design and creation, to its eventual phasing out.

113
Q

virtual machine

A

A software implementation of a computer system, allowing one physical computer to run several ‘virtual computers’, each with their own independent operating system and application software.

A-ICT- IB- Tom (33 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions