Docstoc

gcss_af_acronyms

Document Sample
gcss_af_acronyms Powered By Docstoc
					GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




                                                 GCSS-AF
      Global Combat Support System - Air Force
                Developer’s Guide

        Architecture Dictionary and Acronyms


                                                                                           Prepared for:
                                                                            Department of the Air Force
                                                            Headquarters Standard Systems Group (SSG)
                                                                Maxwell Air Force Base - Gunter Annex
                                                                                Montgomery, Alabama


                                                                     Contract Number: F01620-96-D-0004

                                                            Document Number: GCSS-REPORT-1999-0100
                                                                                          Version: 1.2
                                                                                     Date: 05/28/1999




                                                                               Lockheed Martin Federal Systems
                                                                                               1801 Route 17C
                                                                                        Owego, NY 13827-3998
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




                                         DOCUMENT CHANGE HISTORY

                 VERSION                  CHANGE DESCRIPTION (REQUIRED FOR CHANGES AFFECTING
                                          TPM, REQUIREMENTS, CONFIGURATION, COST & SCHEDULE)

      NO.    APPROVAL         DATE       CHANGE      SECTION     NARRATIVE (OF ITEMS AFFECTED)
                                         DOC.

      0.1        IPT       07/14/97                            INITIAL DRAFT

      1.0       CCB        02/08/99                            RELEASE WITH GCSS-AF
                                                               DEVELOPER’S GUIDE TABS A AND B

      1.1       CCB        03/25/99                            RELEASE WITH GCSS-AF
                                                               DEVELOPER’S GUIDE TAB B

      1.2       CCB        06/09/99                            SCR 067 – UPDATES FOR TAB A AND B
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




                                  This Page Intentionally Left Blank
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




                                                            TABLE OF CONTENTS

1.   INTRODUCTION .............................................................................................................................................. 1

2.   REFERENCE DOCUMENTS .......................................................................................................................... 2

3.   COMMON VOCABULARY............................................................................................................................. 3
     3.1.1       0-9 .......................................................................................................................................................... 3
     3.1.2       A ............................................................................................................................................................. 3
     3.1.3       B ............................................................................................................................................................. 5
     3.1.4       C............................................................................................................................................................. 5
     3.1.5       D ............................................................................................................................................................ 6
     3.1.6       E ............................................................................................................................................................. 8
     3.1.7       F ............................................................................................................................................................. 8
     3.1.8       G ............................................................................................................................................................ 9
     3.1.9       H ............................................................................................................................................................ 9
     3.1.10      I .............................................................................................................................................................. 9
     3.1.11      J ........................................................................................................................................................... 11
     3.1.12      K........................................................................................................................................................... 11
     3.1.13      L ........................................................................................................................................................... 11
     3.1.14      M .......................................................................................................................................................... 11
     3.1.15      N........................................................................................................................................................... 12
     3.1.16      O .......................................................................................................................................................... 12
     3.1.17      P ........................................................................................................................................................... 12
     3.1.18      Q .......................................................................................................................................................... 13
     3.1.19      R ........................................................................................................................................................... 13
     3.1.20      S ........................................................................................................................................................... 13
     3.1.21      T ........................................................................................................................................................... 14
     3.1.22      U .......................................................................................................................................................... 14
     3.1.23      V ........................................................................................................................................................... 15
     3.1.24      W .......................................................................................................................................................... 15
     3.1.25      X ........................................................................................................................................................... 16
     3.1.26      Y ........................................................................................................................................................... 16
     3.1.27      Z ........................................................................................................................................................... 16
4.   ACRONYMS .................................................................................................................................................... 17




                                                                                     i
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




                                  This Page Intentionally Left Blank




                                                    ii
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



1. Introduction
This document contains the list of terms and definitions as used in the context of Global Combat
Support System – Air Force (GCSS-AF) Project. These terms or phrases are listed in
alphabetical order with meanings and/or descriptions. This dictionary provides the common
vocabulary for the project.

Note: The parenthesis [e.g. (XXX)] following some of the definitions indicates the definition’s
origin.




                                                    1
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100




2. Reference Documents

   Global Combat Support System - Air Force (GCSS-AF) Developer’s Guide Tab A -
    Architecture Overview and Description; GCSS-REPORT-1997-0010.

   Global Combat Support System - Air Force (GCSS-AF) Developer’s Guide Tab B -
    Design and Development; GCSS-REPORT-1997-0011.

   Global Combat Support System - Air Force (GCSS-AF) Developer’s Guide Tab C -
    Operations and Support Plan; GCSS-PLAN-1997-0016.

   Global Combat Support System - Air Force (GCSS-AF) Developer’s Guide Tab D -
    Program Objectives Memorandum Considerations; GCSS-PLAN-1997-0017.

   Global Combat Support System - Air Force (GCSS-AF) Integrated Technical Management
    Plan (ITMP); GCSS-PLAN-1997-0010.




                                                    2
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



3. Common Vocabulary
Term                   GCSS-AF Definition
3.1.1 0-9

24x7                   24 hours a day, 7 days a week


3.1.2 A

Abstraction            The principle of ignoring those aspects of a subject that are not
                       relevant to the current purpose in order to concentrate more fully on
                       those that are. (Dictionary of Computing, Oxford University).


Actor                  1. Objects that reside outside the modeled system. An actor
                          represents everything that has a need to exchange information with
                          the system, including what is usually referred to as the Users.
                          (Ivar Jacobson)
                       2. Any object that models a role that a users plays. This can be a
                          person, an organization or another system. (G. Booch, Robi)
                       3. An Actor represents all things that interface with the system,
                          including humans as well as machines. (ITMP)


Active X               Microsoft's general term for standardized controls or visual objects.
Automated              1. Identifies an existing legacy Automated Information Systems.
Information            2. An aggregation of software, control language, data structures, user
System (AIS)              interface that support a functional activity and generally used in
                          reference to legacy system. Legacy systems are candidates for
                          phase-out, upgrade, or replacement. Generally legacy systems are
                          in this category because they do not comply with data standards or
                          other standards. Legacy system workloads must be converted,
                          transitioned, or phased-out (eliminated). Such systems may or
                          may not operate in a legacy environment. (DoD, GCSS-AF
                          Proposal)

Applet                 A visual object written in Java for embedding on Web pages.




                                                    3
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Ad Hoc Query           A built on the fly request for information.


Application            The defined interface, by which one application gains access to
Program Interface      services or data of another application, defined at the source-code
(API)                  level.

Application            A computer program that operates on a target platform(s) and
Program                performs a specific user function. Office automation programs such as
                       word processors, graphic presentation packages, and spreadsheets are
                       common examples of application programs (DoD).


Architecture           Architecture defines the organizational structure of a system or
                       component (components), their relationships (connectors), and the
                       principles and guidelines governing their design and evolution over
                       time (constraints). (IEEE 610.12; TAFIM, Version 3.0).

                       1. An Architecture Framework provides the rules, guidance, and
Architecture
                          product descriptions for developing and presenting architectures
Framework
                          that ensure a common denominator for understanding, comparing,
                          and integrating architectures. (C4ISR Architecture Framework
                          Version 2)

                       2. A family of related architectures, allowing an instance or
                          individual architecture to be created by selection from and
                          modification of the defined existing framework components. The
                          framework description is in the form of models, made up from a
                          set of conceptual building blocks, and shows how the building
                          blocks fit together. The visual representation of the structure
                          should also provide a common vocabulary. The framework should
                          be extensible so that it can deal both with future technology and
                          with legacy systems. It should also include a list of recommended
                          specifications or products satisfying the conceptual building
                          blocks. (The Open Group) see DSSA Reference Architecture.

Authentication         To ensure that a user or system entity is who or what is claims to be.




                                                    4
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.3 B

Bandwidth              The amount of information (messages, bytes, packets, etc) that can be
                       pushed through the network (LAN and/or WAN), defined as a data
                       rate, considering the network as a shared resource, with other systems.

Business Area          1. A group of related tasks focusing on one business function.

                       2. A business department or focus area, exclusively containing the all
                          the necessary business expertise to provide a complete specific
                          product in support of the enterprise. (EG. Personnel, New Hire
                          Processing, Accounts Payable etc.) (DB Robi) See Functional
                          Area

Business Object        1. A model of business procedures, policy & control around data
Classes                   about a single concept. A method to organize the right data and
                          right procedures about a single concept. (Robert Shelton)

                       2. The business object classes are responsible for implementing
                          functionality or business logic within the application. These object
                          classes capture the business rules of the application. They provide
                          the dynamic behaviors and run-time data to describe and define
                          business activities. Some examples of business object classes are:
                          Transaction, Sub-Transaction, Policy, Assembly, and Order-
                          Equipment. (ITMP)

Business Process       The Fundamental rethinking and radical redesign of business
Reengineering          processes to achieve dramatic improvements in critical, contemporary
(BPR)                  measures of performance, such as cost, quality, service and speed.
                       (Hammer & Champy)


3.1.4 C

Centralized            Management of a group of computer systems that may be co-located
Systems                (local) and/or dispersed (remote) over a wide geographic area, from a
Management             single (centralized) location. System administrators can access and/or
                       login to any managed computer system from a single display console.




                                                    5
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Class                  A uniquely identified abstraction. Classes are defined as encapsulated
                       data entities whose behavior is controlled by supporting (surrounding)
                       operations or methods (ITMP).


Co-located             To be in the same physical (same room) or electrical (point-to-point
                       cable connection, or on the same LAN) proximity.


Common Object          The COM is an Object-Oriented Analysis and Design Model. It is the
Model (COM)            GCSS-AF System and Application design and documentation vehicle.
                       The COM provides opportunities for reuse, enables technology
                       infusion, promotes a high-level systems view of the project, and
                       enhances business modernization by promoting best business
                       practices.


Component              A software component is a unit of composition with contractually
                       specified interfaces and explicit context dependencies only. A
                       software component can be deployed independently, is self-contained,
                       and is sufficiently specified to be useable by third parties.

Component Based        Development that primarily consists of integrating instances of
Development            previously defined logical classes of objects and their physical
(CBD)                  implementations as components. These include 3GL, 4GL and NDI,
                       COTS/GOTS components (Firesmith, Robi).

CORBA Object           An object which is invoked in a distributed environment via CORBA
                       mechanisms.


3.1.5 D

Data Object Class      The data object classes represent the persistent data typically found in
                       a DBMS. These object classes also provide a standard interface to, and
                       hide the details of, how the data is stored. The data object classes will
                       be used as input to our data modeling activity for a relational data
                       model. Typical data object classes could be: Account, Order,
                       Personnel or Item.




                                                    6
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Defense                An architecture that is fully compliant with the DoD Joint Technical
Information            Architecture for Information Management (TAFIM), Volume 3. An
Infrastructure         approach for building interoperable systems, a collection of reusable
Common                 software components, a software architecture for supporting a mission
Operating              area application, and a set of guidelines and standards (DISA).
Environment (DII
COE)


Data Integrity         To ensure that data is not altered inadvertently.
Domain                 1. Any subject area of expertise used to decompose a system.
                          (Firesmith, Lorenz, Robi)
                       2. The overall area of business with which the applications under
                          development is concerned. (Firesmith, Lorenz)
                        3. A set of current and future systems that share a set of common
                           requirements, capabilities, and data. A logical grouping of related
                           functions and objects. Often referred to as problem domain,
                           problem space or problem area.
Enterprise Domain      The Object-Oriented Analysis model defining the business areas and
Analysis Model         business classes (objects) specific to the enterprise under consideration
                       including features, functions and relationships between these business
                       areas and classes (a.k.a. Business Model.) (DB Robi).
Domain                 A process that identifies, collects organizes and represents domain
Engineering (DE)       information based on the study of existing systems, requirement
                       specifications, domain expertise, engineering knowledge and emerging
                       technology. In the development of software systems this information is
                       used to enable and maximize reusability (DISA, Robi).
Domain Specific        A specification for assemblage of software components that are
Software               specialized for a particular class of tasks (domain); generalized for
Architecture           effective use across that domain; composed in a standard structure; an
(DSSA)                 effective for building successful application. (E. Mettala)




                                                    7
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.6 E

Engineering Data       Is the GCSS-AF data repository consisting of a logical data store
Repository (EDR)       cataloging project lifecycle data. This data is made up of files and
                       metadata. The files are the actual development artifacts. The metadata
                       is information about these native files including relationships between
                       the files.

Endian                 A term used for byte ordering. (e.g. Most significant bit first / Least
                       significant bit first)
End-user               The person who uses a computer application, as opposed to those who
                       developed or supports it.

Enterprise              A coordinated group of business organizations functioning together to
                       achieve a common goal. Enterprise-wide within the Air Force means
                       Air Force wide. Enterprise-wide within a MAJCOM within the Air
                       Force means MAJCOM wide.

Externalization        The mapping of an object’s identity and state, including references to
                       other objects, to a serial stream. (a.k.a. Serialization)

3.1.7 F

Federated              The union of two or more naming contexts.
Firewall               A dedicated gateway machine with special security precautions on it,
                       used to service outside network, especially Internet, connections and
                       dial-in lines. The idea is to protect a cluster of more loosely
                       administered machines hidden behind it from crackers. Typical
                       firewall is an inexpensive microprocessor-based Unix machine with
                       no critical data, with modems and public network ports on it, but just
                       one carefully watched connection back to the rest of the cluster. The
                       special precautions may include threat monitoring, callback, and even
                       a complete iron box keyable to particular incoming Ids or activity
                       patterns. Firewalls often run proxy gateways.
Framework              See Architecture Framework.




                                                    8
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Functional Area        A functional area (e.g., personnel) is comprised of one or more
                       functional activities (e.g., recruiting), each of which consists of one or
                       more functional processes (e.g., interviews). (See Business Area)
                       (DoD 8320.1-M-1)

3.1.8 G

Global Combat          Global Combat System Support –Air Force (GCSS-AF) is the
Support System –       contracting vehicle for the procurement and implementation of the
Air Force (GCSS-       Combat Support Information System (CSIS). GCSS-AF will enable
AF)                    agile combat support and information superiority. Providing the future
                       battlefield air force, joint and/or coalition commanders and
                       participants with the right assets, in the right place, at the right time,
                       because they have the right information when and where they need it.

Graphical User         The use of pictures rather than just words to represent the input and
Interface (GUI)        output of a program. A program with a GUI runs under some
                       windowing system (e.g. Microsoft Windows). The program displays
                       icons, buttons, dialogue boxes etc. in its windows on the screen and
                       the user controls it mainly by moving a pointer on the screen (typically
                       controlled by a mouse) and selecting certain objects by pressing
                       buttons on the mouse while the pointer is pointing at them.

3.1.9 H

Happy Path             The typical scenario or nominal path through a Use Case. This is the
Scenario               situation where everything that can go wrong goes right. There are no
                       alternative situations encountered and no exceptional conditions
                       raised. Sometimes referred to as the “Sunny Day Scenario” (DB Robi)


3.1.10 I

IDEF0                  A modeling technique used to produce a “function model”. A
                       function model is a structured representation of the functions,
                       activities or processes within the modeled system or subject area.
                       (FIPS PUB 183)




                                                    9
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
IDEF1X                 A modeling technique used to produce an “information model” which
                       represents the structure and semantics of information within the
                       environment or system. (FIPS PUB 184)
Immutability           The property that an item does not change over time.
Infrastructure         The underlying foundation, or basic framework, as of a system.

Integrated Master      The IMP is the manifestation of the GCSS-AF Process and as such
Plan (IMP)             addresses ALL task orders from new development to modifications.
                       The IMP is tailored for each task order’s needs and specific
                       requirements. A tailored IMP, containing a subset of all of the
                       development activities in the generic IMP, is combined with timeline
                       information and dependencies to form an Integrated Master Schedule.
                       (see IMS) (ITMP)

Integrated Master The IMS for a specific Task Order is a tailored version of the IMP for
Schedule (IMS)    that Task Order including the specific set of tasks and events, schedule
                  timeline, resource allocation information and dependencies for that
                  task order. (ITMP)

Interface              Used to define an interface according to a certain model (usually an
Definition             object model) in a programming language-neutral form.
Language
Iterative and          Software is partitioned into increments whose development is phased
Incremental            over the total development cycle. It allows the user to employ part of
Development            the product before it is entirely completed. Incremental delivery
                       strategies are characterized by a build-a-little, test-a-little approach to
                       deliver an initial functional subset of the final capability.

Internet               The Internet is the largest network in the world. It is a three level
                       hierarchy composed of backbone networks (e.g. ARPAnet, NSFNet,
                       MILNET), mid-level networks, and stub networks. These include
                       commercial (.com or .co), university (.ac or .edu) and other research
                       networks (.org, .net) and military (.mil) networks and span many
                       different physical networks around the world with various protocols
                       including the Internet Protocol. There are several bodies associated
                       with the running of the Internet, including the Internet Architecture
                       Board, the Internet Assigned Numbers Authority, the Internet
                       Engineering and Planning Group, Internet Engineering Steering Group
                       and the Internet Society. (FOLDOC)




                                                    10
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.11 J


3.1.12 K


3.1.13 L

Local Area             A communications network which is geographically limited (typically
Network (LAN)          to a 1 km radius) allowing easy interconnection of terminals,
                       microprocessors and computers within adjacent buildings. Ethernet
                       and FDDI are examples of standard LANs. Because the network is
                       known to cover only a small area, optimizations can be made in the
                       network signal protocols that permit data rates up to 100Mb/s or more.
                       See also token ring; wide area network; metropolitan area network.
                       (FOLDOC)
Legacy System          Existing information systems that pre-date the GCSS-AF and DII COE
                       initiatives. These comprise the respective AIS to be modernized.
                       These systems must be maintained and supported until a modernized
                       system is fielded Air Force Wide.


3.1.14 M

Middleware             Software that mediates between an application program and a
                       network. It manages the interaction between disparate applications
                       across the heterogeneous computing platforms. The Object Request
                       Broker (ORB), software that manages communication between
                       objects, is an example of a middleware program. (FOLDOC)


Mission                Within the GCSS-AF domain, an application that performs a specific
Application            Air Force support function. A GCSS-modernized AIS, where the AIS
                       is/was considered a legacy application. Within the context of this
                       document, a Mission Application and Modernized Application are the
                       same.




                                                    11
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.15 N

Network                Hardware and software data communication systems. The OSI seven-
                       layer model attempts to provide a way of partitioning any computer
                       network into independent modules from the lowest (physical) layer to
                       the highest (application) layer. Many different specifications exist at
                       each of these layers. Networks are often also classified according to
                       their geographical extent: local area network (LAN), metropolitan area
                       network (MAN), wide area network (WAN) and also according to the
                       protocols used (Tanenbaum, A.).


Non-Repudiation        A guarantee that a particular piece of data originated from a particular
                       user.


3.1.16 O

Object                 Any abstraction that models a single thing. In object-oriented
                       programming, a unique instance of a CLASS including the data,
                       indicating the object’s State, and defined services / operations used for
                       accessing and manipulating this data.

Operational            The operational architecture view is a description of the tasks and
Architecture View      activities, operational elements, and information flows required to
                       accomplish or support a military operation. (C4ISR) The operational
                       elements are the Actors, Relationships, Use Cases / Scenarios, and
                       System Boundary.



3.1.17 P

Persistence            The preservation of an object’s identity or state, as in persistent data..
Postcondition          A formal condition that is expected to hold just after completion of an
                       operation.
Precondition           A formal condition that is expected to hold just before execution of an
                       operation.




                                                    12
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Presentation           The presentation object classes provide the user interface, separating
Object Classes         the graphic user interface (GUI) details from the business logic and the
                       data. Typical presentation object classes are: windows, frames, menus,
                       list-boxes and widgets (or controls). (ITMP)


3.1.18 Q


3.1.19 R

Rapid Application      The rapid development of the user interface layer (GUI) of a system
Development            under development, typically using a GUI builder, for purposes of
(RAD)                  clarifying and refining use functional needs and requirements. (DB
                       ROBI)



3.1.20 S

Scenario               One particular path through a Use Case describing the sequence of
                       actions or an instance of the Use Case. Each scenario path through the
                       use case describes another alternative of the Use Case. (DB Robi)
Segmentation           The engineering process of composing or decomposing system
                       elements into segments (GCSS-AF components) and creating the
                       appropriate segment descriptor files. (DII COE I&RTS, Robi)
Serialization          (see Externalization)
System                 A regularly interacting or interdependent group of components
                       forming a unified whole, under the influence of a set of rules,
                       conditions, and constraints that perform one or more vital functions
                       (i.e., a system of systems).
Systems                The systems architecture view is a description, including graphics, of
Architecture View      systems and interconnections providing for, or supporting, warfighting
                       functions. (C4ISR)




                                                    13
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.21 T

Technical               The technical architecture view is the minimal set of rules governing
Architecture View      the arrangement, interaction, and interdependence of system parts or
                       elements, whose purpose is to ensure that a conformant system
                       satisfies a specified set of requirements. (C4ISR)

Touch Labor            A situation where a human is required to perform a physical contact
                       activity in support of a task. For example, packing or unpacking a
                       container, connecting or disconnecting a cable, turning a switch on or
                       off, removing or installing a component or module in a piece of
                       equipment, inserting or removing tape cartridges from a tape drive or
                       autoloader.
Transaction            A unit of work that has the following (ACID) characteristics:
                        A transaction is atomic; if interrupted by failure, all effects are
                          undone (rolled back).
                        A transaction produces consistent results; the effects of a
                          transaction preserve invariant properties.
                        A transaction is isolated; its intermediate states are not visible to
                          other transactions.
                        Transactions appear to execute serially, even if they are performed
                          concurrently.
                        A transaction is durable; the effects of a completed transaction are
                          persistent; they are never lost (except in a catastrophic failure).

3.1.22 U

Unified Modeling       The Object Management Group’s (OMG) standardized language for
Language (UML)         Object-Oriented Analysis and Design visual modeling.




                                                    14
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
Use Case               1. A Use Case is a way to use the system. It is a sequence of
                          transactions (events), offered by the system, which yield a
                          measurable value for a particular user (Actor). (Ivar Jacobson)

                       2. Use Cases describe a system from the user’s perspective. Once
                          defined, the Use Cases identify the User needs being satisfied by
                          the system in a stable fashion. The complete set of Use Cases
                          delineates the scope of the system. The Use Cases describe the
                          Business Areas being supported by the system. Scenarios further
                          refine these business areas identifying the lower level.



3.1.23 V


3.1.24 W

Wide Area              A network usually constructed with serial lines, extending over
Network (WAN)          distances greater than one kilometer. Compare to local area network,
                       metropolitan area network. (FOLDOC)

World-Wide Web          (WWW, W3, The Web) An Internet client-server distributed
                       information retrieval system originated from the CERN High-Energy
                       Physics laboratories in Geneva, Switzerland. The WWW represents
                       objects in HTML format with hyperlinks referring to other documents
                       by their URLs. The World Wide Web Consortium is the main
                       standards body for the web.
Wrapper                A software technique used to encapsulate functionality and provide
                       well-defined interfaces with which to access that functionality.




                                                    15
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



Term                   GCSS-AF Definition
3.1.25 X


3.1.26 Y


3.1.27 Z




                                                    16
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100



4. Acronyms
3GL                     Third Generation Language
4GL                     Fourth Generation Language
          A
A&D                     Analysis and Design
AATS                    Automated Architecture Tool Suite
ABP                     Abstract Business Process
ACID                    Atomic, Consistent, Isolated, Durable
ACS                     Agile Combat Support
AF                      Air Force
AF/ILX                  Air Force / Integrated Logistics
AFIN                    Air Force Information Network
AFNCC                   Air Force Network Control Center
AFORMS                  Air Force Operations Resource Management System
AIS                     Automated Information System
AMWG                    Architecture Methodology Working Group
ANSI                    American National Standards Institute
API                     Application Program Interface
ASCII                   American Standard Code for Information Interchange
ASR                     Alternative System Review
B
BAPI                    Business Application Programming Interfaces
BBP                     Best Business Practice
BDA                     Business Data Area
BLSM I                  Base Level Systems Modernization, Phase I
BOA                     (CORBA) Basic Object Adapter
BOD                     Business Object Document
BPR                     Business Processing Reengineering
BSR                     Business Service Request
C
C2                      Command and Control
CAE                     Common Application Environment
CAR                     COM Architecture Repository
CASE                    Computer Aided Software Engineering
CAP                     Controlled Access Protection
CBD                     Component Based Development
CDE                     Common Data Environment
CDE                     Common Desktop Environment
CDR                     Critical Design Review
CGI                     Common Gateway Interface
CIE                     Common Infrastructure Environment
CM                      Configuration Management
COE                     Common Operating Environment
COM                     Common Object Model


                                                    17
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100


COM+                    Component Object Model +
CONOPS                  Concept Of Operations
COOP                    Continuity of Operations
CORBA                   Common Object Request Broker Architecture
COTS                    Commercial Off The Shelf
CRD                     Capstone Requirements Document
CRUD                    Create, Read, Update, Delete
CSC                     Computer Software Component
CSCI                    Computer Software Configuration Item
CSIS                    Combat Support Information System
CSU                     Computer Software Unit
        D
D/C                     Don’t Care
DAA                     Designated Approval Authority
DBMS                    Data Base Management System
DCE                     Distributed Computing Environment
DCI                     Data Conversion Interface
DCOM                    Distributed Component Object Model
DDA                     Data Definition Area
DDL                     Data Definition Language
DII                     Defense Information Infrastructure
DII COE                 Defense Information Infrastructure Common Operating Environment
DIREP                   Discrepancy Report
DISA                    Defense Information Systems Agency
DISN                    Defense Information System Network
DLL                     Dynamic Link Library
DMC                     Defense MegaCenter
DMS                     Defense Messaging System
DNCC                    Deployed Network Control Center
DoD                     Department of Defense
DOORS                   Dynamic Object Oriented Requirements System
DPP                     Defect Prevention Process
DSD                     Data Store Driver
DSS                     Decision Support Systems
DSSA                    Domain Specific Software Architecture
        E
EBCDIC                  Expanded Binary Coded Decimal Interchange Code
EDIFACT                 Electronic Data Interchange for Administration, Commerce and
                        Transport
EDM                     Enterprise Data Model
EJB                     Enterprise Java Beans
ERP                     Enterprise Resource Planning
ESD                     Electronic Software Distribution
          F



                                                    18
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100


FAB                     Field Assistance Branch
FIPS                    Federal Information Processing Standard
FQR                     Functional Qualification Review
FQT                     Functional Qualification Test
          G
GOLD                    Government On Line Data
GOTS                    Government Off The Shelf
GUI                     Graphical User Interface
GUID                    Globally Unique Identifier
          H
HLD                     High Level Design
HP                      Hewlett Packard
HQ                      Head Quarters
HQ SSG                  Head Quarters Standard Systems Group
HTML                    HyperText Markup Language
HTTP                    HyperText Transport Protocol
H/W                     Hardware
          I
IAC                     Inter-Applet Communication
I&RTS                   Integration and Runtime Specification
IBM                     International Business Machines
ID                      Identifier
IDB                     Integrated Database
IDEF                    Integrated Computer Aided Manufacturing Definition
IDIQ                    Indefinite Delivery / Indefinite Quantity
IDL                     Interface Definition Language
IDS                     Interface Definition Specification
IIOP                    Internet Inter-ORB Protocol
IL                      Integrated Logistics
ILS-S                   Integrated Logistics System - Supply
IMDS                    Integrated Maintenance Data System
IMP                     Integrated Management Plan
IMS                     Integrated Management Schedule
IOC                     Initial Operational Capability
IP                      Internet Protocol
IPT                     Integrated Product Team
ISO                     International Standards Organization
ITMP                    Integrated Technical Management Plan
          J
JAD                     Joint Application Development
JDK                     Java Development Kit
JMCIS                   Joint Maritime Command Information System
JOPES                   Joint Operations Planning and Execution System
JTA                     Joint Technical Architecture



                                                    19
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100


JTA-AF                  Joint Technical Architecture - Air Force
          K

          L
LAN                     Local Area Network
LDAP                    Lightweight Directory Access Protocol
LDM                     Logical Data Model
LLD                     Low Level Design
LMFS                    Lockheed Martin Federal Systems
      M
MA                      Mission Application
MAJCOM                  Major Command
MB                      Megabyte
MCG&I                   Mapping, Charting, Geodesy and Imagery
MHz                     Mega-Hertz
MLS                     Multi-Level Secure
MOM                     Message Oriented Middleware
MOU                     Memorandums of Understanding
MQI                     Message Queue Interface
MS                      Microsoft
      N
NDI                     Non-Developmental Item
NDS                     NetWare Directory Service
NIPRNET                 Non-Secret Internet Protocol Routed Network
NSM                     Network & Systems Management
NT                      New Technology
NT                      Microsoft Windows NT
      O
O-O                     Object Oriented
O&S                     Operations & Support
OA                      Office Automation
OAG                     Open Applications Group
OAGIS                   Open Applications Group Integration Specification
OAMAS                   Open Applications Group Middleware API Specification
ODBMS                   Object Database Management System
ODMG                    Object Database Management Group
OLAP                    On-line Analytical Processing
OLE                     Object Linking and Embedding
OLTP                    On-line Transaction Processing
OMG                     Object Management Group
OOD                     O-O Design
OOA&D                   Object-Oriented Analysis and Design
OQL                     Object Query Language
ORD                     Operational Requirements Document



                                                    20
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100


ORB                     Object Request Broker
OSF DCE                 Open Software Foundation Distributed Computing Environment
OTS                     Object Transaction Service
       P
PC                      Personal Computer
PDR                     Preliminary Design Review
PDS                     Persistent Data Service
PKI                     Public Key Infrastructure
PL/SQL                  (Oracle) Procedural Language/Structured Query Language
PMO                     Program Management Office
POA                     Portable Object Adapter
POC                     Point Of Contact
POS                     Persistent Object Service
POSIX                   Portable Operating System Interface for UNIX
POM                     Program Objective Memorandum
PSS                     Persistent State Service
       Q
QOS                     Quality of Service
       R
RAM                     Random Access Memory
RAS                     Reliability, Availability, Serviceability
RDBMS                   Relational Data Base Management System
RFP                     Request For Proposal
ROI                     Return On Investment
RPC                     Remote Procedure Call
       S
S/W                     Software
SBSS                    Standard Base Supply System
SDM                     Shared Data Model
SDS                     Shared Data Store
SFR                     System Functional Review
SHADE                   SHAred Data Environment
SIPRNET                 Secret Internet Protocol Routed Network
SIS                     Shared Information Segment
SLA                     Service Level Agreement
SMC                     Systems Management Center
SON                     Statement Of Need
SOO                     Statement Of Objectives
SOW                     Statements Of Work
SQL                     Structured Query Language
SRR                     System Requirements Review
SRS                     System Requirements Specification
SSG                     Standard Systems Group
SSG/SSQ                 Standard System Group / Quality Assurance Organization



                                                    21
GCSS-AF Architecture Dictionary and Acronyms, Version 1.2
Document No. GCSS-REPORT-1999-0100


STP                     System Training Plan
SUN                     Sun Micro Systems
          T
TAFIM                   Technical Architecture for Information Management
TBA                     To Be Addressed
TBD                     To Be Determined
TCP                     Transmission Control Protocol
TCP/IP                  Transmission Control Protocol/Internet Protocol
TOA                     Task Order Approval
TP                      Transaction Processing
TPM                     Technical Performance Measure
TRD                     Technical Requirements Document
TRR                     Test Readiness Review
          U
UDP                     User Datagram Protocol
UML                     Unified Modeling Language
URL                     Universal Resource Locator
USAF                    United States Air Force
          V
VTS                     Voyager Transaction Service
         W
WAN                     Wide Area Network
WWW                     World Wide Web
          X
XA                      Extended Architecture
XML                     Extensible Markup Language
          Y

          Z




                                                    22

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:7
posted:9/14/2011
language:English
pages:27