Agile methodology

A form of XP, aims for customer satisfaction trhoug

continuous delivery of useful software components

Analysis phase

Analyzing end-user business requirements and ref

goals into defined functions and operations of the i

Business requirement

The detailed set of business requests that the syst

order to be successful.

Change control board (CCB)

Responsible for approving or rejecting all change r

Change management system

Includes a collection of procedures to document a

and define the steps necessary to consider the cha
expected impact of the change.

Commercial off-the shelf (COTS)

A software package or solution that is purchased to

more business functions and information systems.

Computer-aided software enginnering (CASE)

Software suites that automate systems anlysis, de

development.

Critical success factor (CSF)

A factor that is critical to an organization's success

Data flow diagram (DFD)

Illustrates the movement of inormation between ex

the processes and data stores within the system.

Data model

A formal way to express data relationships to a dat

management system (DBMS).

Design phase

Involves describing the desired features and opera

system including screen layouts, business rules, p
pseudo code, and other documentation.

Development phase

Involves taking all of the detailed design document

phase and transforming them into the actual system

Entity relationship diagram (ERD)

A technique for documenting the relationships betw

database environment.

Extreme programming (XP) methodology

Breaks a project into tiny phases, and developers c

on to the next phase until the first phase is comple

Feasability study

Determines if the proposed solution is feasible and

a financial, technical, and organizational standpoin

Feature creep

Occurs when developers add extra features that w

initial requirements.

Graphical user interface (GUI)

The interface to an information system.

Help desk

A group of people who respond to internal system

Implementation phase

Involves placing the system into production so use

perform actual business operations with the system

Joint application development (JAD)

A session where employees meet, sometimes for s

define or review the business requirements for the

Maintenance

The fixing or enhancing of an information system.

Maintenance phase

Involves performing changes, corrections, addition

to ensure the sytem continues to meet the busines

Modeling

The activity of drawing a graphical representation o

Online training

Runs over the Internet or off a CD-ROM.

Planning phase

Involves establishing a high-level plan of the intend

determining project goals.

Process modeling

Involves graphically representing the processes th

manipulate, store, and distribute information betwe
its environment.

Prototype

A smaller-scale representation or working model o

requirements or a proposed design for an informat

Rapid application development (RAD) (rapid prototyping)

methodology

Emphasizes extensive user involvement in the rap

evolutionary construction of working prototypes of
accelerate the systems development process.

Requirements definition document

Contains the final set of business requirements, pr

of business importance.

Scope creep

Occurs when the scope of the project increases.

Sign-off

The system users' actual signatures indication they

the business requirements.

Systems development life cycle (SDLC)

The overall process for developing information sys

planning and analysis through implementation and

Test condition

The detailed steps the system must perform along

results of each step.

Testing phase

Involves bringing all the project pieces together int

environment to test for errors, bugs, and interopera
that the system meets all of the business requirem
the analysis phase.

User documentation

Highlights how to use the system.

Waterfall methodology

A sequential, activity-based process in which each

SDLC is performed sequentially from planning thro
implementation and maintenance.