A See Auditor
AC See Application Development Methodology Council
Acceptance Testing See Testing.
Accountable Subject to giving an accounting for their actions (answerable).
Activity Generic term referring to any action or procedure performed by UCD.
ADM See Application Development Methodology.
Analysis Stage The stage of the ADM in which is performed a high level and broad analysis of the processes occurring within a business activity and the data required to support that activity. The analysis is at higher level and covers a broader scope than the detailed analysis performed in the design stage. The analysis stage follows the project initiation stage and precedes the design stage.
Application The set of business processes which capture and maintain business data and provide business information. These processes may be either manual or automated.
Application Development Methodology A methodology of tasks, deliverables and techniques established for use by staff of University of California, Davis.
Application Development Methodology Council An organization which manages the application development methodology for information technology within the University.
Approval Responsibility The role of the party who must formally approve the contents of the deliverable before the deliverable can become baselined and the development process can proceed. Accountability for obtaining the approval of the designated party rests with the party having primary responsibility for that deliverable.
Once approved, any further changes require the use of the change management process. Issues not resolved are to be escalated through the designated approval party's management chain. Unresolved issues arising from a deliverable will stop the development process.
Attribute An occurrence of an attribute type.
Attribute Type A fact, having a value, about an entity type.
Auditor An organization unit or individual which performs a control function for the University.
BAA See Business Area Analysis.
Baseline The content of a deliverable has been reviewed and accepted by approving parties. It cannot be changed without appropriate management approval and acceptance by the approving parties.
BCA See Business Contract Administrator
BE See Business Expert
BPM See Business Project Manager
BPR See Business Process Re-Engineering.
BSD See Business System Design.
Bug A software error which is characterized by a deviation or omission from specified functionality.
Business Activity A generic term referring to an action performed or executed by the business and which produces output meaningful to the business. .
Business Area A set of related business activities and the data entities which those activities create or update.
A business area is usually segmented into multiple design areas when transitioning from the analysis stage to the design stage.
Business Area Analysis The stage of the Application Development Methodology which defines the business' requirements.
Business Area Analysis Project A project analyzing the business processes and events within a proscribed set of business activities and the data created or updated within that set of business activities.
Business Area Model The set of models reflecting business activities, data, business locations and organization units which represent a business area.
Business Contract Administrator A party or organization unit which provides legal consultation, manages and/or enforces a University contractual obligation.
Business Data A set of facts which are meaningful to the business.
Business Event An instance (or happening) in the life of the business when an external party interacts with the business and as a result of that interaction causes a change in the current state of the business. Anticipated business events result in business response(s). One or more business activities are executed to generate that business response.
Business Event Model A series of models pertinent to a business area which depicts its business events and the set of business processes producing the responses to those events.
Business Expert An individual with in-depth knowledge of an organization unitís overall business processes and data and who is able to identify the business needs of a particular organizational unit.
Business Function A high level summary of ongoing processes which are taking place to perpetuate the business. Each business function is decomposed into multiple lower level business functions or business activities.
Business Location A geographic area, county, city, town or site where UCD does business.
Business Model A technology independent business area model.
Business Process Re-Engineering A project wherein the current methods of conducting a set of business activities is evaluated and revised with the intent of increasing the efficiency of the business activities.
Business Project Manager A person representing the business who has decision making authority for the user community. They are responsible for assignment of users to the project team and to develop user guides, office procedures and user training. Further, they identify users to be interviewed, users to participate in review walkthroughs and inspections. They also will identify users who will participate in testing, development of test scripts, test cases and test data. Additionally, they will resolve user conflicts, be a focal point for change control, prioritize user requests and keep the user community informed of project status.
Business Organization See Organization Unit.
Business Response The business deliverable or output of a set of business activities which satisfies the business event which triggered the set of business activities.
Business System Design The phase of the design stage of the Application Development Methodology addressing the external interfaces of system being designed.
CCM See Code Configuration Manager
Code Configuration Manager A person or organization unit responsible for maintaining the library of code "objects" for a system and migrating/installing/configuring new and/or revised versions to appropriate environments.
Code Library A repository of executable modules and/or objects pertaining to the University's systems and databases.
Computer File UCD business data stored in/on a computer readable media.
Computer System An automated set of tasks that performs one and only one business activity or some implementable portion of a business activity.
Concur Responsibility The role wherein a party must formally endorse or concur with the approval of the deliverable in order for the deliverable to be baselined and the development process to proceed. Responsibility for gaining the concurrence of the designated concurrence rests with the party having primary responsibility for that deliverable.
Verification of the fulfillment of a deliverable may be either verbal or in writing. It is the party having primary responsibility for the deliverable to determine which mode is appropriate.
Contingency Plan A set of directives and procedures to be followed if implementation is not successful. It specifically refers to the contingency during the test to production turnover, not the contingencies that might occur during an operational situation.
Control Code See Job Control Software.
Control Function Any organization unit performing a University control function such as auditing, production control or quality assurance.
Construction Project A set of processes and tasks which transforms an information system design into an implementable module.
Construction Stage The stage of the ADM wherein is created the information system, the files and databases which it requires, the implementation plans and the operational documentation and in which the operational training is performed. The construction stage follows the design stage and precedes the implementation stage.
Consultation Responsibility The role of the party which may be required to provide assistance to complete the deliverable.
Conversion Plan A set of directives and procedures which addresses the change of a process or set of data from one mode or format to another.
Critical Success Factor Critical success factors are those few key areas in which satisfactory results will ensure competitive performance for the University. CSFs support the attainment of University Goals.
CSF See Critical Success Factor.
DAD See Data Administrator
Data Representation of concepts, facts or instructions in a formalized manner. Data are the raw material of information.
Data Acquisition System An information system which collects and validates data and stores that data in a sharable data structure.
Data Administrator An organization unit or individual which develops and maintains an unambiguous and consistent set of definitions of data, activities and their relationships to facilitate common understanding and to provide a consistent framework for information systems within the enterprise.
Data Application System An information system which extracts data from a sharable data structure, manipulates it in a prescribed manner and produces information in any form.
Data Capture The activity of collecting data from an information source and storing that data in a sharable data structure to enable its access at a later time.
Data Conversion The activity of changing the structure, format, location or media of data. The activity is frequently associated with the transfer of data from one or more existing operational systems to a new information system during its implementation.
Data Entity A class of persons, places, things, events or concepts about which UCD wishes to keep data.
Data Life Cycle The continuum of the planning, acquisition, employment, maintenance and disposition of data.
Data Management Tools Software and hardware resources and techniques for capturing, storing and controlling data as well as for delivering information.
Data Model A representation of the business data captured by and required to support the UCD business processes.
Data Steward An organization unit or individual which is responsible for the accuracy, timeliness, access and security of a segment of UCD's business data.
Data Stewardship The role of establishing the definition of a data object, establishing data validation rules and establishing data access authority.
Data Validation The activity of validating data as to it reasonableness.
Database A set of logically structured data which enables direct access to individual members using multiple criteria.
Database Administrator The organization unit or individual responsible for designing and maintaining the physical database(s) required by an information technology project and develops database roll-back and recovery strategies.
DBA See Database Administrator
DC See Documentation Specialist
Deliverable The products of the Application Development Methodology tasks performed. . Deliverables represent tangible products of the system development process.
Design Area The scope of a project whose objective is to create the design of an information system.
The design area is usually formed as a subset of a business area. That is, a business area is usually segmented into multiple design areas when transitioning from the analysis stage to the design stage.
Design Stage The stage of the ADM in which the design of the information system, the files and databases which it requires, implementation and training plans and information system documentation is formulated. This stage typically occurs after the analysis stage and prior to the construction stage.
Design Project A work effort whose objective is to produce the design of an information system.
Detailed Business Area Analysis The second (and more detailed) phase of the Business Area Analysis stage of the ADM.
Detailed Business Model An outline business model which also incorporates one or more of the following models: entity state transition diagrams, process logic diagrams, process involves attribute associations, process action diagrams, attribute type domains, attribute type properties, attribute type ranges and physical data flow diagrams.
Disaster Recovery Plan A set of directives and procedures which identifies the actions to be taken in the event of an unplanned disruption to the automated and manual operations (processes) of the business.
Documentation Specialist A person who writes, reviews, maintains and releases all product documentation; including user guides, reference manuals, detailed system specifications; and designs and defines documentation standards.
DS See Data Steward
EM See Enterprise Model
EMS See Enterprise Modeling Stage.
Emergency A situation under which the end user is unable to carry on their mission critical business.
Emergency Fix A software modification which returns a system to its original working condition.
End User They provide the primary input to and receive the output from an information system.
Enhancement A modification to an existing system which is intended to provide an additional functionality or improve quality.
Enterprise Model A model of the enterprise's business activities, data, business locations, organization units, existing systems and long term directions.
Enterprise Modeling Stage The stage of the ADM in which the enterprise defines its strategic plan for those information system(s) which it might develop.
Entity An occurrence of an entity type.
Entity Type A class of persons, places, things, events or concepts of importance to the business.
Entry Point The point of entry in a set of program code statements.
Environmental Software Computer software other than that which directly captures and maintains business data and provides the business information. It is that software which establishes and maintains the software envelope in which the application software can operate. Common components of environmental software include operating systems, language compilers and utilities.
Environmental Software Support An organization unit or individual which provides and maintains that software which establishes and maintains the software envelope in which the application software operates.
EU See End User
External Specifications Content and format definitions of information vehicles associated with an information system which are visible and directly usable by human beings. Examples include video screens, forms and reports. Specifically excluded are the contents of computer memory or storage devices.
Field The smallest addressable portion of a computer file defined to contain data.
File A set of logically structured data.
IM See Implementable Module.
Implementable Module A set of manual and/or automated procedures which operate as a unit to produce business information and/or perform a meaningful business task. An automated implementable module consists of code statements. An implementable module represents a business activity or subset thereof and interfaces or integrates with other implementable modules.
Implementation To move all components of a system from a test environment to a production environment.
Implementation Stage The stage of the ADM in which the products created in the construction stage are implemented for operational use.
Information Data in a meaningful association or context.
Information Library A repository of information about the data, activities and technology components of the University's systems and databases.
Information Model A representation of the business information produced by and required to support the UCD business processes.
Information Resource Management A set of management approaches that enable organizations to manage information as a shared resource.
Information Resources Planner An organization unit or individual which plans the information systems technology environment and recommends the business areas and information systems needed by the University.
Information Resources Strategy A long-term direction, specifically related to information resources, which supports the University strategies.
Information System A grouping of one or more implementable modules which comprises an information system.
Information System. Architecture A structure composed of business data and business processes which identifies individual business systems that can be developed with the knowledge that they can be readily integrated and can share data.
Information System Plan A plan showing the allocation of information systems resources over the forthcoming three to five year time horizon. It describes the development and supporting projects and integrates the priorities of University management and the strategies of Information Resources.
Information System Project A work effort whose objective is to produce an information system.
Information Technology This refers to the application or utilization of technology in a system; not a University organization unit.
Information Technology Steering Committee A decision making body of individuals accountable for the selection and prioritization of the University's information technology projects.
Information User The individual or group which utilizes information to perform their assigned business tasks.
Infrastructure Project Projects directed at implementing technology, methodology, training, procedures or access systems over a broad section of the University and are, therefore, beyond the scope of a single business area.
Input Responsibility The role of the party which must provide necessary information (either written or verbal) to complete the deliverable.
Integration Testing See Testing.
IR See Information Resources
IRP See Information Resources Planner
IS See Information System.
IT See Information Technology.
Iteration The process of repeating a set of activities till the products of the activities are satisfactory. The set of repeated activities can be limited or substantial in scope.
ITS See Information Technology Steering Committee
Job Control Software The set of instructions which control the operation of automated procedures. Examples include job control software and "C" Lists.
JAD See Joint Application Development.
Joint Application Development The use of facilitated sessions involving subject matter experts to gather information and make business decisions concerning an information system project.
Joint Requirements Planning The use of facilitated sessions involving subject matter experts to plan future sessions concerning an information system project.
JRP See Joint Requirements Planning.
Legal and Contracts An organization unit which either provides legal consultation or manages the establishment of University contractual obligations.
Level of Effort A quantity of human time associated with the performance of a specified activity.
Library A repository of information or program code relating to information systems and databases.
Linkage A connection between two related records by which records may be accessed, but of which modules need have no knowledge.
Location See Business Location.
Logical Business Activity See Business Activity.
Logical Business Data Conceptual representation of business data.
Logical Data Structure A representation of business data logically structured in the data definition language and constraints of a particular database management system.
Mandated Maintenance A predictable system change required by the federal government, state government, UCOP or academic senate.
Mechanism The implementation in technology of a business process.
Migration Plan A set of directives and procedures providing for the movement or duplication of automated processes and/or data from one location or place to another without changing its form or function. Sometimes referred to as a Turnover Plan.
MM See Model Manager
Model Manager A person or organization responsible for managing the University's library of models.
Needs Analysis Preliminary definition of the business situation needing correcting or resolving.
Needs Analysis Report A collection of information about the nature and extent of a perceived business need. The information includes the description and objectives of the perceived business need as well as identification of the business activities, data entities, locations and organization units involved in the need.
O See Operations
OBAA See Outline Business Area Analysis.
Office of Record The University department which is custodian for the University's official version of a set of information.
Operational Control Procedures Procedures which are intended to ensure that a system is being operated in an expected and approved manner.
Operational System An information system which processes business data and creates information on which UCD business decisions are made.
Operations An organization unit responsible for operating an information system, communications network and for hardware and communications facilities maintenance.
Organization Unit A person or group of people within the University structure assigned to perform or manage specific business processes.
Outline Business Area Analysis The initial (and more generalized) phase of the Business Area Analysis stage of the ADM.
Outline Business Model The set of models representing a business area which typically includes a process decomposition diagram, entity-relationship diagram, business event model, either logical data flow diagrams or process dependency diagrams, process involves entity type association and design areas.
PD See Project Director
Physical Data Structure The framework or skeleton of a data storage facility which is not populated with data.
Physical Database A data storage facility populated with business data. It is usually associate with a computer.
Pilot A pilot is a system that is not yet fully operational. Whereas a prototype is used when the functions and detailed design of a system are not fully understood, in a pilot system the functions and design are thought to be understood, but the system is cut over in limited form so that experience can be gained with it before the full system is implemented. As a result of pilot operation, modifications are usually made before the system is fully deployed.
Policy A stated course or method of University action to guide and determine present and future decisions.
Post Implementation Assessment Stage The stage of the ADM which follows the Implementation Stage, supports the implementable module during its immediate post implementation period and responds to emergencies affecting the operational system during this period.
Post Implementation Assessment A project normally conducted 90 to 180 days after the completion of a system development project. The purpose of which is to review the effectiveness of the system development process employed, to determine whether the operational system achieved the system development project's intended benefits and whether the operational system is efficient.
Primary Responsibility The role of the party that has primary responsibility for consolidating all information and producing and publishing the deliverable. It includes coordination of all activities associated with the development and approval of the deliverable.
Principle A comprehensive and fundamental doctrine.
Problem Description Section of the project initiation request form used to describe the business situation needing correcting or resolving.
Procedure A technology dependent activity normally expressed as a series of action steps followed in a definite order.
Process A technology independent business activity.
Process Dependency Diagram A model relating the dependencies, conditions, plurality and optionality among the processes within a theme.
Process Specifications The definitions of an information system's information vehicles and business activities.
Processing Operations An organization unit responsible for operating an information system as well as for maintaining its operability.
Program Specifications Structured guide identifying the actions to be performed or accomplished by a program.
Project Defined work effort to accomplish a specific task.
Project Boundary The outer limits of a project's scope.
Project Director A person who resolves issues between the Business Project Manager and Technical Project Manager. They have decision authority for budget issues and resource issues beyond the scope of the project managers. Further, they act as a liaison between the project and the rest of the University community and resolve political issues beyond the scope of the project managers. The role of mediation is assumed in each task where it is not specified.
Project Initiation Request Request to create new business information or functionality, increase the cost effectiveness and efficiency of existing business activities or to correct a deficiency in an existing system, file or database.
Project Initiator An individual or group responsible for initiating a project request who may or may not become the project sponsor.
Project Initiation Stage The stage of the ADM in which individual implementable module construction projects, design projects and business area analysis projects are formulated and their pursuit approved.
Project Leader An individual having primary responsibility for the welfare of an project.
Project Plan A plan identifying the deliverables and activities to be performed in a project. It includes the project's resource requirements, estimated costs, timeline and project schedule.
Project Scope The business activities, business data, organization units and business locations which represent the subjects or territory to be addressed by a project.
Project Scope Document A document which defines the objectives, scope, time-line and resources of the project.
Project Sponsor An individual or group of individuals representing University faculty or administrative management that endorses the scope and objectives of a project as well as representing that project in University councils.
Project Steering Committee A group of individuals having collective accountability for overseeing the welfare of an project.
Prototype:
¤ Application Concept Prototype An application concept prototype is a system developed to test and refine the underlying premise of an application.
¤ Application Package Prototype This is a "canned" application tried out with a small group of users before its full-scale implementation.
¤ Calculations and Logic Prototype These are examples of the computations for complex logic or calculations in an application.
¤ Data Entry Prototype This is a shell routine or system to check the speed and accuracy of data entry, and to test validity and integrity checks.
¤ Data System Prototype This is a small-scale database to test database contents and organization.
¤ Dialog Prototype This is a simulation of the interplay of user actions and the intended system response.
¤ Partial-System Prototype A partial-system prototype emulates a facet of an application.
¤ Reporting System Prototype This is a mock-up of reports provided to users.
¤ Screen Prototype A screen prototype is a working model of the screens and their interaction that simulates the operation of the system once it is ultimately developed. The prototype lacks logic to process or display data. It can, however, demonstrate movements from one screen to another, simulating navigation through a real version of the system.
¤ System Prototype A system prototype is an executable version of the system procedures. The prototype is based on the source code developed to implement the system, which is itself derived from the design specifications describing the procedure.
A prototype of the system will be produced to whatever level of detail is required. At a minimum, this will consist of an agreed-upon sequence of dialogs for the system, in whole or in part.
Public Relations An organization unit or individual responsible for creating and maintaining a positive image regarding an aspect of the University's business.
QA See Quality Assurance/Quality Control
Quality Assurance/Quality Control A function responsible for defining standards, guidelines and maintaining a glossary of terms to facilitate common understanding among anyone who has to interact with the project. Additionally, Quality Assurance ensures all deliverables meet or exceed standards set for the deliverable. Standards are usually based on the intended use, target audience and impact on the community of the deliverable.
RAD See Rapid Application Development.
Rapid Application Development A method of developing information systems which places a heavy reliance on group facilitation and operational prototyping. This method is most frequently associated with the development of small, stand-alone systems.
Record The collection of fields representing a single occurrence of a record type. A record is a single occurrence of a record type.
Record Type The physical incarnation of an entity type.
Relationship An occurrence of a relationship type.
Relationship Type A business based association between entity types.
Requirements Definition of the business processes, events and data included within the scope of the information system.
Resource Something available for use in achieving a goal or objective.
Responsible Liable to be called to account as the primary party.
Review Responsibility The role of the party who is to review and comment on the deliverable. After the review is complete, issues not resolved to a reviewer's satisfaction, are to be escalated through the reviewer's management chain. Such action will not necessarily stop the development process.
Risk Anything that might adversely affect the success of a project. Examples of risks include length of project, costs associated with projects, technological and functional uncertainties, lack of technical experience, potential reorganization issues and input of changing business activities.
Risk Analysis The process of identifying and planning for risks associated with a project.
S See Sponsor
SA See System Architect
SAC See Security Administrator
SAD See Systems Administrator
SC See Steering Committee
Scope Defines and limits the area of interest and level of detail of a work activity. Scope is usually stated in measurable terms such as data entities, business activities, business locations and organization units.
SD See System Developer
Security Administrator The organization unit(s) accountable for implementing the security and protection of the information and technology resources of UCD.
SEM See Strategic Enterprise Modeling.
Specification The precise definition of something which exists or which is to be created.
Sponsor An individual or group representing the University's faculty and/or administrative management that endorses the scope and goals of a project and represents that project in management councils. The sponsor has primary responsibility for marshaling the resources needed to fund the project.
Stakeholder A party who has a vested interest in the outcome of a study or project.
Standard A model or measure of quantity or quality established by authority, custom or general consent to guide present and future behavior.
Steering Committee Members of the academic and/or administrative staff having collective accountability for overseeing the welfare of an information technology project.
Strategy Model Representation of UCD's University goals and critical success factors.
Strategic Enterprise Modeling A method of determining the enterprise's business functions, information needs, business locations, organization units and business goals with the intent of establishing an information system architecture, data architecture and a development plan for enterprise's strategic information systems.
Stress Testing See Testing.
Subject Area A bounded set of data entities logically grouped by a common subject.
Support Responsibility The role of the party which must be involved in the creation of the deliverable to ensure that its requirements and responsibilities are met. It may involve supplying significant input or providing a control function.
SWAT Skilled Workers with Advanced Tools.
SWOT Strengths, Weaknesses, Opportunities and Threats.
System One or more processes or set of actions which may be either manual or automated.
System Activity A technology dependent procedure.
System Architect An individual responsible for the overall design of the system and for the successful integration of sub-systems. The System Architect provides technical leadership, plans and estimates, technical interfaces external to project; and manages overall test strategies. This individual also resolves technical issue/conflicts, and ensure adherence to standards.
System Developer The individual(s) responsible for the modeling, analysis, programming, testing and/or implementation of an information system. (AKA: Modeler, Developer, Application Developer, or Programmer/Analyst)
System Life Cycle The continuum of the planning for and creation, employment, maintenance and disposition of a system.
System Testing See Testing.
Systems Administrator An organization unit or individual which provides and maintains that hardware and software which establishes and maintains the environment in which the application software operates.
TD See Technical Design.
Technical Design The phases of the design stage of the ADM which addresses technology issues and internal design issues.
Technical Project Manager An individual having primary technical responsibility for the welfare of an information system project.
Technology Refers to hardware, operating and other control software, methods and communications.
Technology Architecture A representation of technology components (computing, data communications and environmental software) configured logically to support an enterprise.
Technology Support Contact A user department's representative who has been given responsibility as the first point of contact for computing related problems or questions. This person has the responsibility to communicate all unsolved problems and unanswered questions to appropriate personnel for resolution. An individual who installs and maintains all software, hardware and the networks for end-clients.
Test Scenario Specification of test data and the expected results of the test.
Testing:
¤ Acceptance Testing The evaluation of all facets of the implementable module by the end user's staff. The objective is to place the implementable module under situations and conditions unforeseen by the development team as well as to test the completeness and clarity of the operational training and documentation.
¤ Benchmark Testing Tests performed to determine whether the time-related and volume-related business requirements of an entire system have been met.
¤ Integration Testing Testing the integration of all components of an implementable module to ensure that all modules and all interfaces of new and existing modules are functioning properly.
¤ Regression Testing Testing of a business system as a whole to ensure that recently made revisions have not adversely affected the functioning of the system as it operated prior to the introduction of the revisions.
¤ Stress Testing Evaluation of the measured performance of all the software, hardware and communications facilities within an implementable module under maximum data volumes and extreme transaction frequencies as well as other demanding conditions.
¤ System Testing Testing of a business system as a whole to ensure that the entire system including all interfaces to existing systems operates satisfactorily.
¤ Unit Testing The testing of individual segments of code to ensure that errors can be detected.
Theme A business event coupled with those business processes which it triggers along with the business response(s) produced by those processes which satisfies the event.
Timeline A series of identified tasks, their dependencies and their durations. This information is not associated with the calendar.
TPM See Technical Project Manager
Training Plan A set of directives and procedures which identifies the organizational positions requiring training, the skills for which training is required and the training vehicle which will be employed to effect the training.
Training Specialist An organization unit or individual which prepares and/or teaches a full curriculum of technical courses to the user community. They manage all aspects of courseware development process and work with management to insure proper course rollout and translation/localization of course material.
TS See Training Specialist.
TSC See Technology Support Contact
UCD Control Function Group One or more persons which have restrictive influence or authority over a project's execution but which are not involved in providing information to the project or in performing the project.
UIM See University Information Model.
University Functional Model A representation of the business processes performed by the University.
University Goal Specific targets which are intended to be reached in a specific time.
University Information Model Collection of the UCD Business and data models.
University Strategy A business direction, long-term in nature, toward which the University intends to move.
User A person or organization which is supplying input to and/or receiving output from an information system.
Walkthrough A guided assessment of the product of a development activity by a group of people with the intent of discovering errors or omissions in the product. Evidence of the walkthrough's findings is generally demonstrated with a participant "sign-off" process.
Overview : Table of Contents