OPF Glossary - O

a software component that models something in an application. An instance of a class that conforms to a type.

a desired result, more detailed than a goal.
Note that a high-level goal is achieved if its associated more detailed objectives are achieved.
Note that objectives should be attainable, cohesive, measurable, and realistic.

object model

a model in terms of objects and their associated relationships.
Contrast with business model and use case model.

object modeling guidelines

conventions that provide guidelines for performing object modeling.

observable

describing a characteristic or behavior that is visible to its stakeholder.
For example information hiding makes software less observable, and therefore less testable because the tester needs to be able to observe the actual characteristic or behavior in order to compare it with the expected characteristic or behavior.

OPEN Modeling Language (OML)

a standard object-oriented modeling language from the OPEN Consortium.

OPEN Process Framework (OPF)

a standard process for creating a project-specific delivery process. The components of the OPF are process components (endeavors, stages, producers, work units, work products, and languages) and associated usage guidelines.

operation

the functional abstraction that can be performed by some object.

operational availability

(1) a user-oriented quality requirement specifying the proportion of the time that an application or component shall function (i.e., be available for performing work).

(2) a quantitative quality factor measuring the proportion of the time that an application or component actually functions.
Note that operational availability is typically:

Defined in terms of the minimum average percent of time that an application must operate without scheduled or unscheduled downtime.
Specified as either a number of nines (e.g., 3 nines = 99.9% and 5 nines = 99.999%) or continuous availability (i.e., absolutely no downtime is allowed).

operational goal

any goal that captures a function to be performed by the application.
Contrast with business goal and quality goal.

operational requirement (a.k.a., functional requirement)

any requirement that specifies a behavior (e.g., function to be performed).
Contrast with design constraint, external API requirement, informational requirement, and quality requirement.

operations

the activity consisting of the cohesive collection of all tasks that are primarily performed to keep an application operating after it has been deployed for use by the user organizations.

operations manual

the operations work product that documents operational procedures for performing operations tasks.

operations organization

the organization that keeps an application functioning once it has been deployed to the user organizations.

operations team

the team that keeps a data center and all of its applications and components operating properly.

oracle

the source (e.g., the requirements, design, or an authoritative domain expert) of testing information that specifies the expected (i.e., correct) behavior of an executable work product.

organization

the largest producer consisting of a cohesive collection of one or more teams.
See also customer organization, development organization, user organization,

organization chart

the management work product consisting of a diagram that documents the composition of the either the development organization or the project team in terms of its component teams and the aggregation relationships between them.

output device

a device for outputing information and commands from a computer system.