Appendix B: Glossary

A  B  C  D  E  F  I  L  M  N  O  P  S  


Acceptance CriteriaPre-established standards or requirements a product or project must meet.
ApplicationSoftware that performs automated functions for a user. Examples include home banking, word processing and payroll. Distinguished from operating system or utility software.
Automated ControlsSoftware routines designed into programs to ensure the validity, accuracy, completeness, and availability of input, processed, and stored data.


BaselineA documented version of a hardware component, software program, configuration, standard, procedure, or project management plan. Baseline versions are placed under formal change controls and should not be modified unless the changes are approved and documented.


CodeSoftware program instructions.


DatabaseA repository of information or data, which may or may not be a traditional relational database system.NIST Glossary
A repository of information or data organized to be accessed, managed, and updated.FFIEC Adapted for Supervisory Purposes
DeliverableA project goal or expectation. Deliverables include broadly-defined, project or phase requirements and specifically-defined tasks within project phases.
Distributed environmentA computer system with data and program components physically distributed across more than one computer.


End userAn individual who will utilize a product or program.
Enterprise architectureThe overall design and high-level plan that describes an institution's operational framework and includes the institution's mission, stakeholders, business and customers, work flow and processes, data processing, access, security, and availability.


FlowchartsTraditional flowcharts involve the use of geometric symbols, such as diamonds, ovals, and rectangles to represent the sequencing of program logic. Software packages are available that automatically chart programs or enable a programmer to chart a program without the need to draw it manually.
Functional requirementsThe business, operational, and security features an organization wants included in a program.


IterativeRepetitive or cyclical. Iterative software development involves the completion of project tasks or phases in repetitive cycles. Tasks and phase activities are repeated until a desired result is achieved.


LAN (Acronym)Local Area Network.


MetricA quantitative measurement.
MilestoneA major project event.


NetworkTwo or more computer systems grouped together to share information, software, and hardware.


Object codeSoftware program instructions compiled (translated) from source code into machine-readable formats.
Operating systemA system that supports and manages software applications. Operating systems allocate system resources, provide access and security controls, maintain file systems, and manage communications between end users and hardware devices.
OutsourcingThe practice of contracting through a formal agreement with a third-party(ies) to perform services, functions, or support that might otherwise be conducted in-house.FFIEC Developed for Supervisory Purposes


PhaseA project segment.
ProjectA task involving the acquisition, development, or maintenance of a technology product.
Project managementPlanning, monitoring, and controlling an activity.


ScriptA file containing active content; for example, commands or instructions to be executed by the computer.
Source codeSoftware program instructions written in a format (language) readable by humans.
Spiral developmentAn iterative project management model that focuses on the identification of project and product risks and the selection of project management techniques that best control the identified risks.
Systems Development Life Cycle (SDLC)An approach used to plan, design, develop, test, and implement an application system or a major modification to an application system.


Previous Section
Appendix A: Examination Procedures