Chapter 15 (HL only): IT Systems in Organizations

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

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

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

Initial testing of an IT system.

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

Component of an Entity Relationship Diagram.

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

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

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

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

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

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

Property of a relationship in an Entity Relationship Diagram.

Moving from an old system to a new IT system.

Person or organisation who commissions an IT project.

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

Limitations within which an IT system must work.

Maintenance that fixes bugs in software.

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

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

Software created specific for an individual or organisation.

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

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

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

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

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

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

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

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

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

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

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

Component of an Entity Relationship Diagram.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Support for an IT system provided within an organisation.

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

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

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

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

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

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

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

A form of training delivered online.

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

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

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

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

Charting system to show the inter-dependencies in projects.

Gradually removing an old IT system from use.

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

Project Management Body of Knowledge. A project management methodology.

Maintenance that changes software to avoid possible future problems.

PRojects IN Controlled Environments 2. A project management methodology.

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

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

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

Clear statement of the intentions of a proposed IT project.

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

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

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

Person with overall responsibility for an IT project.

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

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

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

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

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

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

The links between separate items of data.

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

Clear definition of the boundaries of an IT project.

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

People who perform alpha, beta, and acceptance testing.

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

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

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

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

Analysis method sometimes used when creating a business case.

High level DFD of a system.

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

Documentation intended for programmers and developers of an IT system.

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

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

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

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

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

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