Artifact whose configuration is being managed.
Copy of an Artifact that is under version control.
Information Item packaging a set of Configuration Items' Versions at a specific time in the product's life (for a product delivery or to establish a relevant point in the Project).
Activity for establishing a Baseline embracing a planned set of Configuration Items' Versions.
Change Request being solved after authorization.
Activity for performing the authorized changes in a set of Configuration Items under version control.
Activity for formally controlling the modification of Configuration Items, in a process of requesting, evaluating, changing and reviewing.
Activity for implementing the changes requested and approved for a Configuration Item.
Stakeholder responsible for implementing a change in Configuration Items.
Activity for closing a reviewed and approved Change Request.
Stakeholder responsible for evaluating if a Change Request should be implemented or not.
Stakeholder responsible for requesting a change in Configuration Items.
Activity for requesting the modification of a set of Configuration Items.
Activity for reviewing an accomplished change assuring that the modifications were made as planned.
Stakeholder responsible for reviewing the changes in Configuration Items regarding a Change Request.
Activity for including new Versions of Configuration Items into a version control repository.
Activity for accessing defined versions of Configuration Items from a version control repository, usually for changing purposes.
Change Request closed after solved, reviewed and approved.
Change Request in the first phase, communicated.
Document reporting the results of a Quality Audit Performing, including Noncompliance and Corrective Action Registers.
Activity for verifying that a Baseline or a Deliverable Product is complete, consistent and in conformity with the specified requirements.
Stakeholder responsible for auditing the Configuration Management related results.
Activity for identifying the Configuration Items of a Project.
Document describing the configuration management parameters for conducting the process, including the identified Configuration Items types, the configuration systems and the planned Baselines, Configuration Audits, and Products Deliveries.
Activity for planning the Configuration Management Process, including, among others, the Configuration Management System Establishment and the Configuration Items Identification.
Process for conducting the activities related to software configuration management, ensuring the completeness and correctness of software Configuration Items.
Activity for establishing the configuration management system, usually composed of version control system, a change control system and a product building system.
Stakeholder responsible for planning and managing the Configuration Management Process.
Software Product ready to be delivered to the client.
Change Request evaluated and set as authorized or rejected.
Object whose configuration may be managed.
Activity for managing the building, releasing and delivering of the products to be delivered to clients.
Activity for evaluating the Change Request for a set of Configuration Items, authorizing or rejecting it.
Change Request reviewed to check if the modifications done are correct.
Change Request solved through the Change Implementation.
Each identified release of a Configuration Item submitted to a version control repository.
Information Item describing a request for modification on a set of Configuration Items.
Object whose configuration is being managed.
Result produced by a Measurement Analysis. An Analysis Result characterizes a Measurable Entity and provides information related to a Measurement Goal.
Measure used to quantify a Directly Measurable Element.
Measurement Procedure applicable to a Base Measure.
Measurement Procedure applicable to a Derived Measure.
Measure used to quantify an Indirectly Measurable Element.
Measurable Element that does not depend on others to be measured.
Measure directly used to indicate the achievement of Measurement Goals.
Measurable Element that depends on others (its sub-elements) to be measured.
Information Needs are identified from Measurement Goals and determine which information have to be met by Measures in order to monitor the achievement of the related Measurement Goal.
Scale in which it is possible to quantify the distance between its Scale Values and there is not a value to represent nonentity (absolute zero). In an Interval Scale, although it is possible to quantify the distance between Scale Values, it is not possible to establish other relations between them.
Measurable property that characterizes a Measurable Entity Type.
Function used to associate a value (Measured Value) to a Measurable Element of a Measurable Entity. Measures quantify Measurable Elements and characterize Measurable Entity Types.
Unit in which measures can be expressed.
Action that measures a Measurable Element of a Measurable Entity by applying a Measure and adopting a Measurement Procedure to obtain a Measured Value. A Measurement is performed based on a Measurement Planning Item.
Action that analyzes Measure Values collected for Measures aiming to characterize a Measurable Entity and provide information related to a Measurement Goal.
Formula that quantifies relations between Measures from which a Derived Measure is obtained.
Goal that can be used to drive the identification of the Measures needed to provide information in a certain context. Measurement Goals are established based on more general Goals.
Action that plans the measurement, i.e., determines the Measurement Goals to be monitored, the Information Needs to be considered, the Measures to be collected to meet the Information Needs and the Measurement Procedures to be applied.
Social Object produced during Measurement Planning. A Measurement Planning Item specifies a Measurement Goal to be monitored, an Information Need to be considered, a Measure to be used to meet the Information Need and a Measurement Procedure to be applied to collect data for the Measure. Several Measurement Planning Items can be produced during Measurement Planning.
Procedure applicable to a Measure and that describe the steps to be carried out to collect data for it.
Scale whose Scale Values can be mapped to a certain order or ranking.
Scale in which it is possible to quantify the distance between its Scale Values, there is a value to represent nonentity (absolute zero) and it is possible to establish relations between Scale Values.
Delimitates the space of values possible to be associated by a Measure to a Measurable Element.
Simple Performed Activity executed for developing the software Code according to previews definitions.
Simple Performed Activity executed for documenting the software Code with useful information.
Simple Performed Activity executed for reviewing the software Code to identify errors and non-conformances.
Document pointing out problems identified in the Code during review activities.
Stakeholder responsible for reviewing the Code according to the Requirements Document and Design Document.
Composite Performed Activity executed for coordinating the Code development and documentation, according to definitions from the Requirements Document and Design Document.
Specific Performed Process for conducting the activities related to software Code production.
Stakeholder with programming skills responsible for producing and documenting the software Code.
Architectural Element describing a software module as part of an Architecture.
Architectural Element connecting two or more Components in an Architecture.
Activity for making the high-level design choices, defining the Software Architecture and involved elements.
Model Element referring to an Architectural Component or Connector, and its Interfaces.
Activity aiming to produce the Software Architecture and specifying its Architectural Components and Connectors.
Activity for refining each Architectural Component of a software.
Activity for refining each Interface Specification of a software.
Information Item describing the high-level choices of how the software will manage data.
Activity for producing a detailed Data Model for data storage and management.
Activity for establish the high-level choices regarding the software data.
Model containing the physical and logical decisions on how to manage and storage the software data.
Document specifying the design of a software, by depicting the software architecture, components, interfaces and data models, as well as other information regarding the design choices and decisions.
Activity for registering the architectural and detailed design choices and decisions, producing a Design Document.
Activity for evaluating a Design Document, registering the identified issues.
Document registering the issues identified in a Design Document evaluation.
Process for defining and specifying a solution to be implemented for a software product, considering the requirements for it. It is a refinement process starting with the software architecture, and going down to the design of its elements, interfaces, and other characteristics of a software, until achieving the design of implementation units.
Stakeholder responsible for making the Detailed Design choices for a software.
Activity for refining a preliminary software design to the extent that it is sufficiently complete to be implemented. [ISO/IEC/IEEE 24765]
Activity for specifying the Interfaces between Architectural Components and with external elements (users or other systems).
Information Item describing an internal or external interface of a software architecture.
Stakeholder responsible for designing the Software Architecture.
Model describing the fundamental structures of a software, including its components, how they are connected, and its internal and external interfaces.
Activity for specifying the User Interfaces in detail.
Interface Specification focusing on the human-computer interaction.
Same as UFO::Organization. A Social Agent involving people and other agents and facilities with an arrangement of responsibilities, authorities and relationships.
A Social Role, recognized by the Organization, assigned to Agents when they are hired, included in a team, allocated or participating in activities.
A Social Object as a temporary endeavor undertaken to create a unique product, service, or result.
Social Agent representing a group of people with a defined purpose.
An Atomic Task is a Task that is not decomposed in other tasks.
A Complex Task is a Task that is composed in other tasks.
Hardgoal is a proposition that is objectively satisfied by a given set of situations.
A Goal in the scope of a specific problem, that describes environmental conditions to be achieved through a desired solution resulting in satisfaction of the underlying strategic goals. In GORE, these goals can be refined by decomposing them into sub-goals, as well as by defining them by means of alternative goals.
Softgoal is an initial and temporary vague expression of a goal not suficiently defined yet. It refers to a vague quality region whose exact boundaries are unknown. Thus it is not possible to determine a priori the set of situations that satisfies the softgoal. Its satisfiability is usually related to an agent's judgement.
Activity for objectively evaluating the adherence of processes and products to the applicable requirements, registering the identified issues.
Activity for objectively evaluating the adherence of products and deliverables to the applicable requirements.
Document describing the evaluation results and identified issues.
Activity for finishing a noncompliance once it is satisfactorily solved.
Activity for managing the registered noncompliances until their effective resolution.
Activity for registering the noncompliances identified in processes and artifacts.
Information Item describing a noncompliance (a failure or refusal to conform to an applicable requirement) in a process or artifact, and related information to solve it.
Activity for analyzing a noncompliance, planning and executing the applicable corrective actions to its resolution.
Stakeholder responsible for solving a noncompliance.
Activity for objectively evaluating the adherence of processes and activities to the applicable requirements.
Document registering the planed quality assurance activities, processes and artifacts to be evaluated and involved personnel.
Activity for planning the quality assurance activities, resulting in a Quality Assurance Plan.
Process for conducting the activities related to software quality assurance, assessing and assuring adherence of the performed processes and produced artifacts to the applicable requirements.
Stakeholder responsible for conducting objective evaluations.
Model describing the Product Requirements under different and relevant views.
Composite Performed Activity executed for modeling requirements, producing Conceptual Models that provide a more comprehensive view of the problem.
Information Item representing the agreement achieved by the Stakeholders, regarding the Requirements for the product.
Specific Performed Process for establishing and developing the requirements for a system or software.
Composite Performed Activity executed for recording Documented Requirements and related Conceptual Models in Requirements Documents, assuring proper recording and management of them during and after the project.
Composite Performed Activity executed for identifying requirements from the Stakeholders and other sources, and documenting them.
Document pointing out problems identified in Documented Requirements and Conceptual Models registered in a Requirements Document.
Composite Performed Activity executed to solve problems in the requirements and to reach an agreement on the set of requirements to be considered in the Project and their priorities.
Stakeholder responsible for conducting reviews in requirements artifacts.
Composite Performed Activity executed for evaluating Documented Requirements and Conceptual Models registered in Requirements Documents, and for recording the identified problems.
Testing technique that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions (adapted from ISO/IEC/IEEE 24765:2017 Systems and software engineering-Vocabulary)
Portion of Code (software module) to be tested by a Test Case.
Software product that manages and maintains lists of issues as needed by an organization (adapted from Wikipedia).
Report describing the occurrence, nature, and status of an incident (adapted from ISO/IEC/IEEE 29119-1:2013 Software and systems engineering--Software testing--Part 1: Concepts and definitions, 4.18).
Level-based Testing focusing on larger components, ensuring that a collection of units functions as desired.
Composite Performed Activity consisting of testing activities and classified by the different levels they can be performed.
Testing technique in which the test cases are derived from a model that describes the system under test.
Testing technique in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations (ISO/IEC/IEEE 24765:2017 Systems and software engineering-Vocabulary)
Skeletal or special-purpose test code substituting a software module, used to test a module that calls or is otherwise dependent on it (adapted from ISO/IEC/IEEE 24765:2017 Systems and software engineering - Vocabulary)
Level-based Testing focusing on the behavior of the entire system, ensuring that it is in conformance with its requirements.
Document containing the analysis of Test Results and how they succeed.
Document containing the input data, expected results, steps and general conditions for testing some situation regarding a Code To Be Tested.
The actual result obtained from the execution of a test case.
Simple Performed Activity for designing the Test Cases to be executed, supported by input artifacts.
Some Artifact defined as an input for the Test Case Design.
Stakeholder responsible for designing test cases and analysing test results.
The result expected from the execution of a test case.
Code produced for implementing a Test Case.
Simple Performed Activity for implementing the Test Cases as Code artifacts (Test Code) to be used during Test Execution.
Software item used to invoke a module under test and, often, provide test inputs, control and monitor execution, and report test results (adapted from ISO/IEC/IEEE 24765:2017 Systems and software engineering-Vocabulary).
Simple Performed Activity for effectively executing the Test Cases, by running the Test Code and producing the Test Results.
Hardware Resource that comprises the Testing Environment of a Project.
Report describing any event that occurs during the testing process which requires investigation (adapted from ISO/IEC/IEEE 24765:2017 Systems and software engineering-Vocabulary)
Descriptions of the parameters and values to be used in a test case, in order to produce an expected result.
Software Product used to store information on how testing is to be done, plan testing activities and report the status of testing activities (adpated from Wikipedia).
Stakeholder responsible for planning and managing the testing activities.
Document describing how the tests should be performed, providing a roadmap for the testing activities.
Composite Performed Activity for planning how the testing activities should be performed, and documenting it in a Test Plan.
Document containing the actual results and identified issues relative to a Test Case execution.
Simple Performed Activity for analyzing Test Results to determine whether or not tests have been successful in identifying defects.
Short program written in a programming language used to test part of the functionality of a software system. Test scripts written as a short program can either be written using a special automated functional GUI test tool or in a well-known programming language (Wikipedia).
Software Resource that comprises the Testing Environment of a Project.
A collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviours (Wikipedia).
Stakeholder responsible for coding and executing test cases.
The set of resources (Hardware and Software Resources) that are used to perform testing activities of a Project.
Levels in which testing activities are performed, such as Unit, Integration and System testing.
Specific Performed Process for planning and executing the dynamic testing activities for the software in development.
Technique for designing test cases. It can be Black-box, White-box, Model-based or Mutation testing techniques, among others.
Major types of testing techniques such as black-box, white-box, model-based and mutation testing techniques.
Level-based Testing focusing on the unit or the individual components that have been developed, ensuring that the unit functions correctly in isolation.
Testing Technique in which the tests are derived from an examination of the structure of the code to be tested (adapted from ISO/IEC/IEEE 29119-1:2013 Software and systems engineering--Software testing--Part 1: Concepts and definitions)
An Adaptation Program is a RRT Program that intends to satisfy at least one Change Runtime Requirement Artifact.
An Adaptation Program Copy Execution is the execution of a Loaded Adaptation Program Copy. It uses Change Runtime Requirement Artifacts as resources to triggers changes in its Loaded Target Program Copy.
Change Runtime Requirement Artifact specifies changes on the system's behavior, in order for the software system to keep fulfilling the goals it has been designed for.
Compliance Program is a RRT Program that intends to satisfy at least one Monitoring Runtime Requirement Artifact.
A Compliance Program Copy Execution is the execution of a Loaded Compliance Program Copy. It uses Monitoring Runtime Requirement Artifacts as resources to monitor Execution States.
A Machine where a Loaded Program Copy is running (Program Copy Execution) plays the role of Controller.
Design Time Requirement Artifact is a Requirement Artifact written in natural language or other format that could not be processed by a program at runtime. It is a Requirement Artifact to be used during design time.
Loaded Adaptation Program Copy is the materialization of an Adaptation Program.
Loaded Compliance Program Copy is the materialization of a Compliance Program.
Loaded Program Copy is the materialization of a Program, inhering in a Machine.
Loaded RRT Program Copy is the materialization of a RRT Program.
Loaded Target Program Copy is the materialization of a Target Program.
Machine is a hardware equipament able to run programs.
Monitoring Runtime Requirement Artifact defines the criteria for verifying if a requirement is being satisfied or not at runtime.
Observable State is a situation resulting from the execution of a program copy. It involves qualities and quality values (qualia) of the Machine in which the Loaded Program Copy inheres, as well as of entities residing in that Machine (including the Loaded Program Copy itself).
Program Copy Execution is an Event representing the execution of the Loaded Program Copy running in a Machine. In other words, the Program Copy Execution is the event of the physical manifestation of the dispositions (represented as the complex disposition Loaded Program Copy) that inhere in the Machine.
An RRT Program is a Program that is built intending to satisfy at least one Runtime Requirement Artifact.
An RRT Program Copy Execution is the execution of a Loaded RRT Program Copy. It uses Runtime Requirement Artifacts as resources.
Runtime Requirement Artifact is a Requirement Artifact written in a computational file that could be processed by a program at runtime (RRT Program Copy Execution).
Software Functions are functional dispositions that constitute the complex disposition Loaded Program Copy. Each Software Function is an instance of a Software Function Universal. When the software development process is accomplished correctly, the Software Functions that constitute the Loaded Program Copy are instances of the exact Software Function Universals described by the Program Specification and successfully implemented by the Program.
Execution State is the Observable State resulting from the Target Program Copy Execution, which is monitored by some Compliance Program Copy Executions.
Target Program is the role a Program plays when it is the targer of a RRT Program, i.e., the RRT Program are built to act over (monitor/change) the Target Program.
A Target Program Copy Execution is the execution of a Loaded Target Program Copy. It brings about to an Execution State.
Information Item that records the Analysis Result produced in a Software Measurement Analysis.
Goal that expresses the intention for which strategic actions are planned and performed.
Activity for analyzing the selected Measured Values and producing the Analysis Result Description that records the Analysis Result.
Activity for collecting and storing data for the Software-Related Measure indicated in the selected Software Measurement Plan Item.
Information Item that documents the description of an Information Need.
Activity for identifying and recording the Information Needs to be included in the Software Measurement Plan. Information Needs are identified from the established Software Measurement Goals.
Type of Measurable Entities related to software.
Information Item that documents the description of a Software-Related Measure.
Information Item that records a Measured Value.
Procedure applied to analyze Measured Values obtained for a Software-Related Measure.
Role played by the Stakeholder in charge of Software Measurement Analysis.
Situation in which a Software Measurement Execution was performed.
Role played by the Stakeholder in charge of Software Measurement Execution. It does not include automated measurement (by tools).
Activity for establishing and recording the Software Measurement Goals to be included in the Software Measurement Plan.
Role played by the Stakeholder in charge of Software Measurement Planning.
Activity for selecting the Software Measurement Plan Item to be used to guide the Software Measurement Execution. The selected Software Measurement Plan Item indicates the Software-Related Measured to be applied in the Software Measurement Execution and the Operational Definition of Measure to be considered.
Activity for defining the Software Measurement Plan structure, its initial information (e.g., organization to which it was defined and elaboration date) and starting its elaboration.
Activity for communicating the Analysis Result Description to the relevant Stakeholders.
Activity for identifying and recording the Software-Related Measures to be included in the Software Measurement Plan. Software-Related Measures are identified from Information Needs in the sense that Measures must meet the identified Information Needs.
Information Item that specifies information regarding data collection and analysis of a Software-Related Measure. An Operational Definition of Measure indicates: Measurement Procedure, Measurement Periodicity, Measurement Moment, Measurement Responsible, Measurement Analysis Procedure, Measurement Analysis Periodicity, Measurement Analysis Moment, and Measurement Analysis Responsible.
Activity for establishing the Operational Definitions of Measures for the identified Software-Related Measures.
Activity for documenting Measurement Planning Items. Each Measurement Planning Item includes a Software Measurement Goal Description, an Information Need Description, a Software-Related Measure and an Operational Definition of Measure. Measurement Planning Items produced during the Software Measurement Analysis are part of the Software Measurement Plan produced in that activity.
Activity for selecting the Measured Values of the selected Software-Related Measures to be analyzed in the Software Measurement Analysis.
Activity for selecting the Software-Related Measurable Entity to be measured in the Software Measurement Execution. The selected entity type must be the Software-Related Measurable Entity Type indicated in the Operational Definition of Measure defined in the selected Software Measurement Plan Item.
Activity for selecting the Software Measurement Goal to be monitored by using information provided by the Software Measurement Analysis.
Activity for selecting, among the Software-Related Measures related to the selected Software Measurement Goal the ones to be analyzed in the Software Measurement Analysis.
Measure used to quantify Measurable Elements of Measurable Software-Related Entities.
Goal that expresses the intention for which software-related actions are planned and performed. Software Goals are based on Business Goals.
Activity for analyzing Measured Values collected for Software-Related Measures aiming to characterize a Software-Related Measurable Entity and provide information related to a Software Measurement Goal.
Activity for measuring a Software-Related Measurable Entity by applying a Software-Related Measure and obtaining a Measured Value.
Measurement Goal related to software. Software Measurement Goals are based on Business Goals or Software Goals.
Information Item that documents the description of a Software Measurement Goal.
Document produced during Software Measurement Planning. It is composed of Software Measurement Planning Items.
Activity for planning the software measurement, i.e., for determining the Software Measurement Goals to be monitored, the Information Needs to be considered, the Software-Related Measures to be collected to meet the Information Needs and the Operational Definition of Measure to be considered.
Measurement Planning Item related to software. It is an Information Item produced during Software Measurement Planning and it is composed of a Software Measurement Goal Description, an Information Need Description, a Measure Description and an Operational Definition of Measure.
The Software Measurement Process is a Process with the purpose of collecting, analyzing, and reporting data relating to the products developed and the processes used to develop them, aiming to support effective processes management and objectively demonstrate products quality.
A Software Measurement Plan defined for a Project.
Assumptions describe states-of-affairs in the environment of interest that the Stakeholders believe to be true, i.e., they are the propositional content of Stakeholders' Beliefs. They express the belief that a specific situation exists in the environment.
Requirement defining a function to be available in the product being built.
Requirement defining criteria or capabilities for the product.
Non-Functional Requirement referring to a Quality Characteristic of the software product.
Quality Universal denoting the types of quality characteristics expected in a software.
Goal to be achieved, representing a condition or capacity needed for the system users for solving a problem.
Information Item describing a Requirement.
Document composed of Documented Requirements and related information, as a basis for other technical software processes, including maintenance.
Stakeholder responsible for conducting the requirements development activities.
Stakeholder that provides needs and expectations for the product.
Function Universal denoting the types of functions expected in a software.
The belief of Requirements Stakeholders regarding the environment of interest that are described in terms of Assumptions.
The intention of Requirements Stakeholders that defines requirements to be achieved.
Information Item describing an action to eliminate the cause or reduce the likelihood of recurrence of a detected nonconformity or other undesirable situation. [ISO/IEC/IEEE 24765]
A Project Process with duration estimated.
A Project Activity with scope, cost, duration and time estimated.
A Project Process with cost, duration and time estimated.
Stakeholder responsible for managing a Project.
Document describing the planning of a Project, to be used as the basis for project management.
A Project Activity with its scope in the project defined in terms of the work packages that it shall produce.
Action Universal representing any generic activity in an Organization (formalized or not), which is the powertype of every Performed Activity.
Object intentionally made to serve a given purpose in the context of a software Project or Organization.
Artifact Participation in which an existing Artifact is modified.
Artifact Participation in which a new Artifact is created.
The participation of an Artifact in a Performed Activity.
Object Kind which is the powertype of Artifact, classifying its specializations.
Artifact Participation in which an existing Artifact is used, but not modified.
Intended Activity composed of other Intended Activities.
Method Activity composed of other Method Activities.
Standard Activity composed of other Standard Activities.
Any written or pictorial, uniquely identified, information related to the software development, usually presented in a predefined format.
Procedure aiming to establish a uniform way for preparing a Document, providing a predefined format and a defined structure for filling with the expected information.
Artifact Type which is the powertype of Document, classifying its specializations.
Intended Process that is composed of Specific Intended Processes, allowing an Organization or Project to define sub-processes that are part of a complete Intended Process.
Standard Process that is composed of Specific Standard Processes, allowing an Organization to establish sub-processes that are part of a complete Standard Process.
Physical Object used for running software programs or to support some related action.
Hardware Equipment when used as Resource of some process activity.
The participation of a Hardware Equipment as a Resource in a Performed Activity.
Object Kind which is the powertype of Hardware Equipment, classifying its specializations.
Standard Process established to be performed in the context of a Project or Organization.
Relevant information for human use, produced or used by Performed Activity.
Intention (Internal Commitment) representing the activity defined to be performed as part of an Intended Process, by a defined role, potentially consuming and producing artifacts, using resources and adopting procedures.
Intention (Internal Commitment) representing the process defined to be performed in a specific project or organizational area, considering its particularities.
Systematic Procedure defining a workflow of activities (a set of steps) and heuristics to perform one or more activities.
Action type representing one of the steps of a Method Workflow.
Complex Action type denoting a set of steps (Method Activities) to be used when a Method is adopted.
A representation (abstraction) of a process or system from a particular perspective.
Organization interested or affected by the process activities or results.
Intended Process defined to be performed in the context of an Organization, regardless of specific Projects.
Standard Process established to be performed in the context of an Organization, regardless of specific Projects.
Action performed, in a specific Time Interval, by a Stakeholder, potentially producing and consuming Artifacts, as part of a Specific Performed Process.
Performed Activity composed of other Performed Activities.
The overall Performed Process executed in a specific Project or Organization, which is necessarily composed of Specific Performed Processes.
Performed Process executed in the context of an Organization, regardless of specific Projects.
Complex Action, composed of other processes or activities, performed in a specific Time Interval, for reaching a goal in a Project or Organization.
Performed Process executed within a Project.
Performed Activity that is not further decomposed into other Performed Activities.
Performed Process that is part of the General Performed Process of a Project or Organization, necessarily composed of at least two Performed Activities.
Person interested or affected by the process activities or their results.
Normative Description prescribing a defined way for performing process activities.
The participation of a Procedure in a Performed Activity.
Complex Action Universal representing any generic process in an Organization (formalized or not), which is the powertype of every Performed Process.
Intended Activity defined to be performed within a Project, and thus that is part of a Project Process.
Intended Process defined to be performed within a Project.
Stakeholder interested in a particular Project.
A Standard Process established to be performed within a Project.
Software Product or Hardware Equipment when used by a process activity.
An Intended Activity defining the time interval it is planned to be performed.
An Intended Process defining the Time Interval it is planned to be performed.
Artifact that is not decomposed into other Artifacts.
Intended Activity that is not further decomposed into other Intended Activities.
Method Activity that is not further decomposed into other Method Activities.
Standard Activity that is not further decomposed into other Standard Activities.
Piece of software, produced during the software process, not considered a complete Software Product, but an intermediary result.
One or more computer programs together with any accompanying auxiliary items, such as documentation, delivered under a single name, ready for use.
Artifact Type which is the powertype of Software Product, classifying its specializations.
A Project related to software development or maintenance.
Software Product when used as Resource of some process activity.
The participation of a Software Product as Resource in a Performed Activity.
Intended Process that is part of the General Intended Process of a Project or Organization, necessarily composed of at least two Intended Activities.
Standard Process that can be part of a General Standard Process of a Project or Organization, necessarily composed of at least two Standard Activities.
Agent (Person, Team or Organization) interested or affected by the process activities or results.
Social Relator representing a Stakeholder allocated to perform a Scheduled Activity acting an Organizational Role.
The participation of a Stakeholder as the main responsible for a Performed Activity, playing an Organizational Role.
The participation of a Stakeholder in a Performed Activity, playing an Organizational Role.
Action Universal representing a generic activity institutionalized as part of a Standard Process in an Organization, establishing general information such as dependence on other activities, types of artifacts created, changed and used, required software and hardware resources, adopted procedures, and roles to perform it.
Complex Action Universal representing a generic process institutionalized in an Organization, establishing basic requirements for Intended Processes to be performed in that Organization or in its Projects.
Plan Description, recognized by an Organization, which describes a set of Standard Processes.
Team interested or affected by the process activities or results.
Procedure that provides heuristics to perform an activity (but in a less rigid and detailed way than a method, since it does not prescribe a set of activities).
Software Item representing a set of computer instructions and data definitions expressed in a programming language or in a form output by an assembler, compiler, or other translator (SEVOCAB).
Computer instructions and data definitions expressed in a form output by an assembler, compiler, or other translator, which can be recognized by the processing unit of a computer machine.
Software Item which aims at producing a certain result through execution on a computer, in a particular way, given by the Program Specification. A Program is constituted by code, but it is not identical to code. Code can be changed without altering the identity of its program, which is anchored to the program's essential property: its intended specification (Program Specification).
A document that describes the purpose (structure and functions) of a program in sufficient detail to permit coding and to facilitate maintenance.
A language used to express computer programs.
Software Item that aims at satisfying a specification (System Specification), concerning a desired change in a data structure inside a computer, abstracting away from the behavior.
A well-formed sequence of computer instructions and data definitions expressed in a programming language, in a form suitable for input to an assembler, compiler, or other translator.