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
project management methodology
Systems and techniques designed to encourage successful projects and avoid project failure.
26
project management software
Software to help plan, manage, and guide the process of IT project development.
27
project manager
Person with overall responsibility for an IT project.
28
project plan
Clear definition of the goals, scope, and schedule of a proposed IT project.
29
requirements specification
Clear list of the functional and non-functional requirements for a proposed IT project.
30
scope
Clear definition of the boundaries of an IT project.
31
SWOT
Analysis method sometimes used when creating a business case.
32
technical documentation
Documentation intended for programmers and developers of an IT system.
33
user documentation
Documentation intended for users of an IT system, helping them understand and use it.
34
Design Stage
3
35
attributes
Component of an Entity Relationship Diagram.
36
cardinality
Property of a relationship in an Entity Relationship Diagram.
37
Data Flow Diagram
Shows processes in a system and the flows of data between them.
38
data structure
The way the data within an IT system is organised and related.
39
DFD
Shows processes in a system and the flows of data between them.
40
entities
Component of an Entity Relationship Diagram.
41
entity relationship diagram
Shows the items of data stored in a system and the relationships between them.
42
ERD
Shows the items of data stored in a system and the relationships between them.
43
outputs
During analysis, a list of the results that a system must produce.
44
processes
During analysis, a list of the procedures a system must implement.
45
prototype interface
Early version of a user interface to get feedback about its effectiveness.
46
relationships
The links between separate items of data.
47
system context diagram
High level DFD of a system.
48
user interface
The part of a system that allows a user to interact with it.
49
Implementation Stage
4
50
alpha testing
Initial testing of an IT system.
51
bugs
Errors in a computer program or system, hopefully found during testing.
52
Capability Maturity Model Integration
Quality assurance method that describes an organisation's level of maturity.
53
CMMI
Quality assurance method that describes an organisation's level of maturity.
54
Frequently Asked Questions
A list of common problems that users experience, and their answers.
55
implementation
Stage in the SDLC where the system is created (programmed).
56
load testing
Testing of an IT system with the amount of work it can be expected to process in real world conditions.
57
online lessons
A form of training delivered online.
58
prototypes
An early version of a project, designed to get feedback from the client and users.
59
quality assurance methods
In project development, used to ensure the whole development team are following standardised best practises.
60
quality control processes
Processes to ensure code produced by programmers followed accepted best practices.
61
software testers
People who perform alpha, beta, and acceptance testing.
62
test plan
List of all tests and test data that should be tried with a system.
63
training
Ensuring that users will be able to work with a new IT system.
64
tutorial
A document which explains how to perform key tasks, step by step.
65
user manual
A document which explains to users how to use a computer system.
66
Testing Stage
5
67
beta tester
Person who attempts to find bugs in software before it is released to customers.
68
beta testing
Testing of an IT system once all features have been added and only bugs need to be worked out.
69
bug tracking system
Used to track and manage bugs in a piece of software.
70
handover
Point at which the developers of a system formally pass it to the client.
71
user acceptance testing
Tests performed by a client before formally accepting an IT system from the developers.
72
Installation Stage
6
73
changeover
Moving from an old system to a new IT system.
74
delivery
Installing a new IT system at the client's premises.
75
deployment
Stage in the SDLC where the system is deployed at the client's site.
76
direct changeover
Immediate removal of an old system and complete replacement with a new IT system.
77
installation
Installing a new IT system at the client's premises.
78
parallel running
Running the old system and the new system side by side.
79
phased changeover
One part of an organisation switches to a new IT system to test it, while others remain using the old system.
80
Maintenance Stage
7
81
adaptive maintenance
Maintenance that changes software to make it work with a new software environment.
82
corrective maintenance
Maintenance that fixes bugs in software.
83
incident escalation
Moving a problem with an IT project to a higher level if it cannot be solved.
84
Incident management system
Used to keep track of problems and difficulties encountered in an IT system.
85
incident tracking system
Used to keep track of problems and difficulties encountered in an IT system.
86
internal support
Support for an IT system provided within an organisation.
87
maintenance
Alterations made to a system after it has been formally handed over.
88
perfective maintenance
Maintenance that changes software to incorporate new user requirements (or changed requirements).
89
phase out
Gradually removing an old IT system from use.
90
preventative maintenance
Maintenance that changes software to avoid possible future problems.
91
regression testing
Testing to ensuring changes to an IT system did not break any previously working functionality.
92
support
Staff who help users with problems they encounter while using an IT system.
93
Development Approach and Methodologies
8
94
acceptance testing
Testing performed by the client and users as part of the handover process.
95
agile development
Development method that focuses on creating small, working parts of a project at regular intervals.
96
PMBoK
Project Management Body of Knowledge. A project management methodology.
97
PRINCE2
PRojects IN Controlled Environments 2. A project management methodology.
98
procurement
The act of acquiring the necessary items (software, hardware, staff) to develop an IT system.
99
project initiation document
Document used in PRINCE2 to describe the key features of an IT project.
100
SSADM
Structured Systems Analysis and Design Method. A project management methodology.
101
user acceptance testing
Testing performed by the client and users as part of the handover process.
102
waterfall development
Development method that focuses on completing each stage of the SDLC for the entire project before moving onto the next.
103
Misc Terms
9
104
Custom / bespoke software
Software created specific for an individual or organisation.
105
emulator
A computer program which simulates another type of computer, so that it can run programs designed for it.
106
IDE
Set of programs used by system developers to create IT systems.
107
Integrated Development Environment
Set of programs used by system developers to create IT systems.
108
legacy system
An old, out of date IT system which is still used because it is essential to an organisation.
109
off-the-shelf software
Software which is widely available and can be bought by anybody.
110
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.
111
source code
Instructions that make up the software, entered by the programmer using a programming language.
112
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.
113
virtual machine
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.