sysml-roadmap:secm_concept_definitions_snapshot_1_28_2016
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
sysml-roadmap:secm_concept_definitions_snapshot_1_28_2016 [2016-01-28 20:04] roncwilliamson |
sysml-roadmap:secm_concept_definitions_snapshot_1_28_2016 [2016-01-28 20:14] roncwilliamson |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Back to [[http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-roadmap:sysml_assessment_and_roadmap_working_group| SysML Assessment and Roadmap Working Group]] | Back to [[http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-roadmap:sysml_assessment_and_roadmap_working_group| SysML Assessment and Roadmap Working Group]] | ||
| + | |||
| + | Back to [[Systems Engineering Model Construction Focus Area]] | ||
| Line 42: | Line 44: | ||
| |Discrete time model|A model which is based on properities that vary discretely with time.| | |Discrete time model|A model which is based on properities that vary discretely with time.| | ||
| |Domain|A scope that encompasses a set of entities and relationships that may be addressed by the model.| | |Domain|A scope that encompasses a set of entities and relationships that may be addressed by the model.| | ||
| - | |Effectiveness measure|A criterion for system optimization that is critcial to the success of the mission.| Note: The criterion are often used to support trade studies to select among alternatives, as well as to optimize a given design.| | + | |Effectiveness measure|A criterion for system optimization that is critcial to the success of the mission. Note: The criterion are often used to support trade studies to select among alternatives, as well as to optimize a given design.| |
| |EIA 632|A process standard for Engineering a System.| | |EIA 632|A process standard for Engineering a System.| | ||
| |Element|Anything of interest to the modeler, which is uniquely identifiable and can be characterized by a set of properties.| | |Element|Anything of interest to the modeler, which is uniquely identifiable and can be characterized by a set of properties.| | ||
| Line 50: | Line 52: | ||
| |Event|A noteworthy occurrence that occurs at the instant of time when a specified expression evaluates true.| | |Event|A noteworthy occurrence that occurs at the instant of time when a specified expression evaluates true.| | ||
| |Execution|The state of the system or model when it is running. For a model, this implies that model computation is occuring.| | |Execution|The state of the system or model when it is running. For a model, this implies that model computation is occuring.| | ||
| - | |Expression|Refer to UML specification | + | |Expression|Refer to UML specification| |
| |Facility|A physical infrastructure that supports use of equipment and other resources.| | |Facility|A physical infrastructure that supports use of equipment and other resources.| | ||
| |Failure|An inability to satsify a requirement.| | |Failure|An inability to satsify a requirement.| | ||
| Line 64: | Line 66: | ||
| |Input/Output|An element that is subject to a transformation by a function.| | |Input/Output|An element that is subject to a transformation by a function.| | ||
| |Instance|A unique model element in a set that iis defined by the general features of its classifier.| | |Instance|A unique model element in a set that iis defined by the general features of its classifier.| | ||
| - | |Integer|A whole number | + | |Integer|A whole number| |
| |Interaction|Emergent behavior that results from two or more dependent behaviors Note: A system or component interacts with other components its environment, to yield an emergent system behavior from the individual component behaviors .| | |Interaction|Emergent behavior that results from two or more dependent behaviors Note: A system or component interacts with other components its environment, to yield an emergent system behavior from the individual component behaviors .| | ||
| |Interface|The inputs, outputs, ports, connections, connecting components (i.e. harness), and associated information that support one or more interactions between systems. Note: The UML definition of interface also includes the operations that must be performed in response to the inputs or invocations.| | |Interface|The inputs, outputs, ports, connections, connecting components (i.e. harness), and associated information that support one or more interactions between systems. Note: The UML definition of interface also includes the operations that must be performed in response to the inputs or invocations.| | ||
| Line 90: | Line 92: | ||
| |Parametric model|An analysis model which defines a set of dependent or logically grouped parametric relationships.| | |Parametric model|An analysis model which defines a set of dependent or logically grouped parametric relationships.| | ||
| |Parametric relationship|A dependency between properties, such that a change to the value of one property impacts the value of the other property.| | |Parametric relationship|A dependency between properties, such that a change to the value of one property impacts the value of the other property.| | ||
| - | |Performance property|A measure of the transformation or response of a function or behavior (i.e response time, etc|).| | + | |Performance property|A measure of the transformation or response of a function or behavior (i.e response time, etc).| |
| |Performance requirement|A performance property a system must satsify.| | |Performance requirement|A performance property a system must satsify.| | ||
| |Physical property|A physical characteristic of a system or element (i.e. weight, color).| | |Physical property|A physical characteristic of a system or element (i.e. weight, color).| | ||
| Line 97: | Line 99: | ||
| |Probability distribution|A mathematical function which defines the likelihood of a paritcular set of outcomes.| | |Probability distribution|A mathematical function which defines the likelihood of a paritcular set of outcomes.| | ||
| |Probe|A component that monitors the values associated with one or more parameters (i.e. properties).| | |Probe|A component that monitors the values associated with one or more parameters (i.e. properties).| | ||
| - | |Problem|A deficiency, limitation, or failure to satisfy a requirement or need, or other undesired outcome. Note: A problem may be associated with the behavior, structure, and/or properties of a system or element at any level of the hierarchy (i.|e.| system of system level, down to a component/part level).| | + | |Problem|A deficiency, limitation, or failure to satisfy a requirement or need, or other undesired outcome. Note: A problem may be associated with the behavior, structure, and/or properties of a system or element at any level of the hierarchy (i.e. system of system level, down to a component/part level).| |
| - | |Problem cause|The relationship between a problem and its source problems (i.e. cause). Note: This cause affect relationship is often represented in fishbone diagrams, fault trees, etc.|.| | + | |Problem cause|The relationship between a problem and its source problems (i.e. cause). Note: This cause affect relationship is often represented in fishbone diagrams, fault trees, etc.| |
| |Process|A set of inter-related functions and their corresponding inputs and outputs, which are activated and deactivated by their control inputs.| | |Process|A set of inter-related functions and their corresponding inputs and outputs, which are activated and deactivated by their control inputs.| | ||
| |Property|A quantifiable characteristic.| | |Property|A quantifiable characteristic.| | ||
| Line 110: | Line 112: | ||
| |Requirement attribute|An attrirbue fo a requirement, which may include its criticality or weighting, level of uncertainty, verification status, etc.| | |Requirement attribute|An attrirbue fo a requirement, which may include its criticality or weighting, level of uncertainty, verification status, etc.| | ||
| |Requirement traceability|The relationship between a source requirement and the derived requirements needed to satisfy the source requirement.| | |Requirement traceability|The relationship between a source requirement and the derived requirements needed to satisfy the source requirement.| | ||
| - | |Requirement type|A category of requirement.| Note: This includes functional, interface, performance, etc.| | + | |Requirement type|A category of requirement. Note: This includes functional, interface, performance, etc.| |
| |Requirement verification|A comparison between a requirement and the verification results that is intended to satisfy the requirement.| | |Requirement verification|A comparison between a requirement and the verification results that is intended to satisfy the requirement.| | ||
| |Resource|Any element that is needed for the execution of a function.| | |Resource|Any element that is needed for the execution of a function.| | ||
| Line 116: | Line 118: | ||
| |Scalable|A measure of the extent to which the modeling langauge (or methodology, etc), can be adapted to an increase in scope and/or complexity.| | |Scalable|A measure of the extent to which the modeling langauge (or methodology, etc), can be adapted to an increase in scope and/or complexity.| | ||
| |Selection|A control operator which represents a test that enables an output based on the values/conditions of the input.| | |Selection|A control operator which represents a test that enables an output based on the values/conditions of the input.| | ||
| - | |Semantics|The meaning of a model element.| Note: a precise meaning should be able to be expressed mathematically.| | + | |Semantics|The meaning of a model element. Note: a precise meaning should be able to be expressed mathematically.| |
| |Sequential state|A state which can only be active when the other sequential states are not active.| | |Sequential state|A state which can only be active when the other sequential states are not active.| | ||
| |Simple state|A state that does not have nested states.| | |Simple state|A state that does not have nested states.| | ||
| Line 122: | Line 124: | ||
| |Source requirement|The requirement which is the basis for deriving one or more other requirements.| | |Source requirement|The requirement which is the basis for deriving one or more other requirements.| | ||
| |Spatial representation|A geometrical relationship among elements.| | |Spatial representation|A geometrical relationship among elements.| | ||
| - | |Specialization|A classification of an entity (e.|g.|, element, system, function, requirement, ...), which specifies the common features of the more general element, and unique features of the specific element.| | + | |Specialization|A classification of an entity (e.g., element, system, function, requirement, ...), which specifies the common features of the more general element, and unique features of the specific element.| |
| |Specialized requirement|A requirement that is not explicitly addressed by the default requirement types. Note: This may include safety, reliabillity, maittianability, producibility, usability, security, etc.| | |Specialized requirement|A requirement that is not explicitly addressed by the default requirement types. Note: This may include safety, reliabillity, maittianability, producibility, usability, security, etc.| | ||
| |Specialty engineering|A general term for engineering disciplines associated with some specific aspects of a system, suchas reliability or safety engineering.| | |Specialty engineering|A general term for engineering disciplines associated with some specific aspects of a system, suchas reliability or safety engineering.| | ||
| |Specification|One or more requirements for a system, component or element.| | |Specification|One or more requirements for a system, component or element.| | ||
| |Stakeholder|Individuals, groups, and/or institutions which may be impacted by the system throughout its life cycle, including acquisition, development, production, deployment, operations, support, and disposal.| | |Stakeholder|Individuals, groups, and/or institutions which may be impacted by the system throughout its life cycle, including acquisition, development, production, deployment, operations, support, and disposal.| | ||
| - | |State (finite)|A condition of a system or element, as defined by some of its properties, which can enable system behaviors and/or structure to occur. Note: The enabled behavior may include no actions, such as associated with a wait state.| Also, the condition that defines the state may be dependent on one or more previous states.| | + | |State (finite)|A condition of a system or element, as defined by some of its properties, which can enable system behaviors and/or structure to occur. Note: The enabled behavior may include no actions, such as associated with a wait state. Also, the condition that defines the state may be dependent on one or more previous states.| |
| |State based behavior|Behavior which is described by states and transitions between states.| | |State based behavior|Behavior which is described by states and transitions between states.| | ||
| - | |Storage device|A component of a system that is used to store a system store.| Note: this may include memory device, a battery, or a tank.|.| | + | |Storage device|A component of a system that is used to store a system store. Note: this may include memory device, a battery, or a tank.| |
| |Store requirement|An element a system must store.| | |Store requirement|An element a system must store.| | ||
| |String|A value represented by alphanumeric characters.| | |String|A value represented by alphanumeric characters.| | ||
| Line 139: | Line 141: | ||
| |System hierarchy|A decomposition of a system and its components.| | |System hierarchy|A decomposition of a system and its components.| | ||
| |System interconnection|The connection between systems and between components.| | |System interconnection|The connection between systems and between components.| | ||
| - | |System role|A subset of its behaviors, properties, and structure.| Note: The subset may be associated with specific interactions.| | + | |System role|A subset of its behaviors, properties, and structure. Note: The subset may be associated with specific interactions.| |
| - | |System store|An input/output element that persists over time, which may be depletable or non-depletable. Note: Non-depletable stores may include data store in computer memory, and depletable stores may include energy in a battery, or fluid in a tank.|.| Physical stores obey the conservation laws (only take out what is put in). A non-depletable store, such as a data store, is not constrained by the conservation laws.| The system store should be differentiated from the storage device, which stores the element.| | + | |System store|An input/output element that persists over time, which may be depletable or non-depletable. Note: Non-depletable stores may include data store in computer memory, and depletable stores may include energy in a battery, or fluid in a tank. Physical stores obey the conservation laws (only take out what is put in). A non-depletable store, such as a data store, is not constrained by the conservation laws. The system store should be differentiated from the storage device, which stores the element.| |
| |Test case|The input stimulus, expected output, and associated test criteria which verify that the system satisfies its requirements or needs.| | |Test case|The input stimulus, expected output, and associated test criteria which verify that the system satisfies its requirements or needs.| | ||
| |Test scenario|A scenario which replicates the behavior of the environment that interacts with the system under test.| | |Test scenario|A scenario which replicates the behavior of the environment that interacts with the system under test.| | ||
| |Text based requirement|One or more requirements specified in text.| | |Text based requirement|One or more requirements specified in text.| | ||
| |Thread|A process with no concurrent functions, and represents a single path of execution.| | |Thread|A process with no concurrent functions, and represents a single path of execution.| | ||
| - | |Time property|A property of the model that represents a local or global time, which other properties may depend on. Note: The property can support continuous or discrete-time models.| This variable should not be confused with the measured or computed time that an actual system uses, which depends on a number of implementation specific factors related to clocks, synchronization, etc.| | + | |Time property|A property of the model that represents a local or global time, which other properties may depend on. Note: The property can support continuous or discrete-time models. This variable should not be confused with the measured or computed time that an actual system uses, which depends on a number of implementation specific factors related to clocks, synchronization, etc.| |
| |Topology|A graph of nodes and arcs.| | |Topology|A graph of nodes and arcs.| | ||
| |Trade-off study|An evaluation of alternatives based on a set of evaluation criteria.| | |Trade-off study|An evaluation of alternatives based on a set of evaluation criteria.| | ||
| Line 156: | Line 158: | ||
| |Vector|A data type, which specifies a magnitude and direction.| | |Vector|A data type, which specifies a magnitude and direction.| | ||
| |Verification|The process for demonstrating a system satisfies its requirements.| | |Verification|The process for demonstrating a system satisfies its requirements.| | ||
| - | |Verification procedure|The functions needed to support execution of a test case. Note. This may include generating an input stimulus and monitoring an output | + | |Verification procedure|The functions needed to support execution of a test case. Note. This may include generating an input stimulus and monitoring an output| |
| - | + | ||
| - | + | ||
sysml-roadmap/secm_concept_definitions_snapshot_1_28_2016.txt · Last modified: 2016-01-28 20:15 by roncwilliamson
Page Tools
