Fandom

The IT Law Wiki

Baseline

32,181pages on
this wiki
Add New Page
Talk0 Share

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.

Definitions Edit

Business Edit

A baseline is

[a] 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.[1]

General Edit

A baseline is

[t]he current or "as is" state of the business, information or technology environment, captured in a set of graphic and textual models.[2]
(1) A specification or product that has been formally reviewed and agreed upon that thereafter serves as the basis for further development and that can be changed only through formal change control procedures. (2) A document or set of such documents formally designated and fixed at a specific time during the life cycle of a configuration item. Note: Baselines, plus approved changes from those baselines, constitute the current configuration identification. (3) Any agreement or result designated and fixed at a given time from which changes require justification and approval.[3]

Product development Edit

A baseline is

[a] specification or product that has been formally reviewed and agreed upon, that serves as the basis for further development, and that can be changed only through formal change control procedures.[4]
[a] [f]ormally approved version of a configuration item, regardless of media, formally designated and fixed at a specific time during the configuration item's life cycle.[5]

Outsourcing Edit

Baseline refers to the current status of the functions to be outsourced in terms of assets used, actual costs, and service levels achieved. It is the starting point for customer to define its needs in an outsourcing relationship.

References Edit

  1. FFIEC IT Examination Handbook, Development and Acquisition, Appendix B: Glossary (full-text).
  2. California Technology Agency, Enterprise Architecture Glossary 1 (Apr. 2011) (full-text).
  3. Information Technology: An Audit Guide For Assessing Acquisition Risks, Glossary, at 88.
  4. U.S. Food and Drug Administration, Glossary of Computerized System and Software Development Technology (Aug. 1995) (full-text).
  5. NIST Special Publication 800-160, App. B, at 167.

See also Edit

Also on Fandom

Random Wiki