Term
|
Definition
An iterative
system development process that
develops the system in“sprint”increments lasting from two weeks to two
months. |
|
|
Term
|
Definition
Activities that, if
delayed, would delay the entire project |
|
|
Term
|
Definition
A model
of objects, associations, and activities
that describes how data can flow
between and around various objects |
|
|
Term
|
Definition
A line with arrows
that show the direction of data element
movement. |
|
|
Term
|
Definition
Representation of a storage
location for data |
|
|
Term
| end-user systems development |
|
Definition
Any systems development project in
which the primary effort is undertaken
by a combination of business managers
and users |
|
|
Term
|
Definition
Representation of
either a source or destination of a data
element. |
|
|
Term
|
Definition
(XP): An
approach to writing code that promotes
incremental development of a system
using short development cycles to
improve productivity and to accommodate new customer requirements. |
|
|
Term
|
Definition
A technique used during the investigation, analysis, and design phases to
define the business processes included
within the scope of the system. |
|
|
Term
|
Definition
A graphical tool used for
planning, monitoring, and coordinating
projects. |
|
|
Term
| information systems planning |
|
Definition
Translating strategic and organizational
goals into systems development
initiatives. |
|
|
Term
|
Definition
involves linking all of the individual components together and testing them as
a group to uncover any defects in the interface between one component and
other components |
|
|
Term
|
Definition
The
decision regarding whether to obtain
the necessary software from internal or
external sources. |
|
|
Term
|
Definition
Representation of
a function that is performed |
|
|
Term
|
Definition
A person who
represents the project stakeholders and
is responsible for communicating and
aligning project priorities between the
stakeholders and development team. |
|
|
Term
|
Definition
A specialist responsible
for modifying or developing
programs to satisfy user requirements |
|
|
Term
| Program Evaluation and Review Technique (PERT) |
|
Definition
A formalized
approach that creates three time estimates
for an activity to determine a
single time estimate. |
|
|
Term
|
Definition
The date the
entire project is to be completed and
operational |
|
|
Term
|
Definition
The person
assigned by the organization doing
the work of the project to achieve
the project objectives. |
|
|
Term
|
Definition
A critical date for
the completion of a major part of the
project. |
|
|
Term
|
Definition
A detailed
description of what is to be done |
|
|
Term
|
Definition
A key member and
leader of the steering committee who
plays such a critical role that lack of this
essential individual raises the distinct
probability of project failure. |
|
|
Term
|
Definition
A working model of a
system developed to enable users to
interact with the system and provide
feedback so developers can better
understand what is needed. |
|
|
Term
|
Definition
An iterative approach to
the systems development process in
which at each iteration requirements
and alternative solutions to a problem
are identified and analyzed, new solutions
are designed, and a portion of the
system is implemented. |
|
|
Term
| Rational Unified Process (RUP) |
|
Definition
An iterative systems development
approach that was developed by IBM
and includes a number of tools and
techniques that are typically tailored to
fit the needs of a specific company or
organization. |
|
|
Term
|
Definition
The temptation to add
more features and functionality to the
original scope of the system. |
|
|
Term
|
Definition
A method employed to keep
the agile system development effort
focused and moving quickly. |
|
|
Term
|
Definition
The person who
coordinates all scrum activities. |
|
|
Term
|
Definition
People who, either
themselves or through the organization
they represent, ultimately benefit
from the systems development project |
|
|
Term
|
Definition
A small group of
senior managers representing the
business and IS organizations that
provide guidance and support to the
project. |
|
|
Term
|
Definition
A professional
who specializes in analyzing and
designing business systems |
|
|
Term
|
Definition
A professional
who specializes in analyzing and
designing business systems |
|
|
Term
|
Definition
The phase
of systems development that converts
the system design into an operational
system by acquiring and installing
hardware and software, coding and
testing software programs, creating and
loading data into databases, and performing initial program testing. |
|
|
Term
|
Definition
Those activities
that ensure the orderly dissolution of
the system including those activities
required to closeout any contracts in
place, dispose of all equipment in an
environmentally friendly manner, and to
safely migrate information from the
system to another system or archive it
in accordance to applicable records
management policies. |
|
|
Term
|
Definition
The systems
development phase that defines how
the information system will do what it
must do to obtain the solution. |
|
|
Term
|
Definition
The systems
development phase during which
problems and opportunities are identified
and considered in light of the goals
of the business |
|
|
Term
|
Definition
The systems development
phase that ensures the system operates
and modifies the system so that it
continues to meet changing business
needs. |
|
|
Term
|
Definition
Use of a new
or modified system under all kinds of
operating conditions. |
|
|
Term
|
Definition
A prototype that is used to help define the
software solution but does not become
part of the final solution. |
|
|
Term
|
Definition
People who will regularly interact
with the system |
|
|
Term
|
Definition
A prototype
that starts with an initial prototype that
undergoes a series of iterations of
demo, feedback, and refinement and
eventually evolves into the final software solution.
S |
|
|
