This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
mbse:digital_viewpoint [2018/11/14 15:13] jcoleman [Explanation] |
mbse:digital_viewpoint [2018/12/12 11:47] jcoleman [Bibliography] |
||
---|---|---|---|
Line 2: | Line 2: | ||
([[mbse:topical_encyclopedia_for_digital_engineering_information_exchange_deixpedia|Return to DEIXPedia page]]) | ([[mbse:topical_encyclopedia_for_digital_engineering_information_exchange_deixpedia|Return to DEIXPedia page]]) | ||
- | Written By **//John H. Coleman, Ph.D.//** | + | **Written By** John H. Coleman, Ph.D. (Email: <[email protected]>)\\ |
- | For comments, contact: <[email protected]> | + | **Submitted** September 7, 2018\\ |
+ | **Last Modified** on December 12, 2018\\ | ||
===== Concise Definition ===== | ===== Concise Definition ===== | ||
- | A digital viewpoint is the collection of requirements, captured in a modeling language, levied by one or more stakeholders against the digital view of digital artifacts in a digital ecosystem such that it meets stakeholders’ unique needs. | + | A descriptive model of a digital view that uses conventions, formalisms and standards to assembles digital artifacts into the contents of a digital view that meets stakeholders’ unique needs. |
===== The Concept ===== | ===== The Concept ===== | ||
- | The digital viewpoint defines the **[[mbse:digital_view|digital view]]** according to the needs of stakeholders performing specific activities at any phase or step in the system life cycle. The conventions, formalisms, and standards used to define the systematic procedures drive the requirements that comprise the digital viewpoint. Thus, the digital viewpoint defines how to select, compile, layout, and present digital artifacts in a digital ecosystem. The digital viewpoint also identifies sources of content that support the object-of-interests and facilitates information exchange between different stakeholders involved in the lifecycle and the supply chain. The viewpoint is digital because it is applied to a set of digital artifacts using software and digital technology to produce the digital view. The author of a digital viewpoint specifies its requirements according to stakeholders’ needs to perform decision-making activities, conduct their responsibilities, or both. The digital viewpoint specifies the required digital artifacts, the standards and conventions to compile the digital artifacts, or the operations to present digital artifacts in a variety of digital multimedia formats. The digital viewpoint may include models, designs, or computer algorithms that specify the type, structure and organization of content. Thus, the digital viewpoint is a specification for digital multimedia presentations of digital artifacts based on stakeholder requirements, content sources, and standards. | + | The digital viewpoint converts **[[mbse:digital_artifact|digital artifacts]]** into the contents of a **[[mbse:digital_view|digital view]]** [1]. It uses descriptive models to define, assemble, layout, and present digital artifacts in a digital environment; such that, they serve specific activities performed by stakeholders. The digital viewpoint identifies digital artifacts it needs from an **[[mbse:authoritative_source_of_truth|authoritative source of truth]]** to produce the digital view. In addition, the digital viewpoint defines what a stakeholder-network wants to view from its **[[mbse:digital_engineering_ecosystem|digital engineering ecosystem]]**. The digital viewpoint may be unique for stakeholders at any stage of the system lifecycle or any component of the supply chain. The viewpoint is digital because it is applied to a set of digital artifacts using software and digital technology to produce the digital view. A creator of a digital viewpoint would design it to fulfill the **point of view** of the stakeholders [1]; thus, they can perform decision-making activities, conduct their responsibilities, or both. The digital viewpoint defines one or more digital artifacts, the **standards** and **conventions** to compile the digital artifacts, or the operations to present digital artifacts in a variety of digital multimedia formats [1]. The digital viewpoint may include models, designs, or computer algorithms that specify the type, structure and organization of a digital view’s content. Thus, the digital viewpoint is a model for digital multimedia presentations of digital artifacts based on stakeholders’ point of view, authoritative source of truth, and model formalisms [1] |
===== Explanation ===== | ===== Explanation ===== | ||
- | The **[[mbse:digital_engineering|digital engineering]]** community formed the concept of a digital viewpoint out of a need to describe how engineering practitioners use sources and types of digital artifacts, like models, and assemble and present them in forms that diverse stakeholders need and understand. The DE community borrowed the original concept from the system architecture community and re-conceptualized it to fit the digital engineering community’s need to leverage digital technologies to create, exchange, and present their digital work products. However, it is more than a static document that specifies the digital view. It may be a digital model of the digital view using standards such as Information Flow Modeling Language (IFML). Alternatively, it may be an application-programming interface (API) or other executable software code that assembles digital artifacts and renders the digital view according to the design. | + | The **[[mbse:digital_engineering|digital engineering]]** community formed the concept of a digital viewpoint out of a need to describe how engineering practitioners use sources and types of digital artifacts, like models, and assemble and present them in forms that diverse stakeholders need and understand. The DE community borrowed the original concept from the system architecture community and re-conceptualized it to fit the digital engineering community’s need to leverage digital technologies to create, exchange, and present their digital work products. However, it is more than a static document that specifies the digital view. It may be a digital model of the digital view using standards such as [[https://www.ifml.org/ | Information Flow Modeling Language (IFML).]] Alternatively, it may be an application-programming interface (API) or other executable software code that assembles digital artifacts and renders the digital view according to the digital viewpoint. |
===== Characteristics ===== | ===== Characteristics ===== | ||
Line 23: | Line 24: | ||
* List of digital artifact elements | * List of digital artifact elements | ||
* Authoritative sources for digital artifact elements | * Authoritative sources for digital artifact elements | ||
- | * **Digital View Design** | + | * **Digital Viewpoint Model** |
- | * Data Model | + | * Data Model |
- | * Digital Multimedia Design | + | * Relationship Models |
- | * Any executable software code that implements the design of the digital view | + | * Layout Design |
+ | * Interactive Hypermedia Design | ||
+ | * Any executable software code that implements the digital view model | ||
===== Common usage ===== | ===== Common usage ===== | ||
Line 55: | Line 58: | ||
===== Bibliography ===== | ===== Bibliography ===== | ||
- | [4] National Institute of Building Sciences, "Chapter 3: Terms and Definitions," in National BIM Standard – United States® Version 3, Washington, DC, National Institute of Building Sciences buildingSMART alliance®, 2015, p. 16. | + | [1] C. Delp, D. Lam, E. Fosse and C.-Y. Lee, "Model Based Document and Report Generation for Systems Engineering," in IEEE Aerospace Conference Proceeddings, Big Sky, Montana, 2012. |
+ | |||
+ | [2] National Institute of Building Sciences, "Chapter 3: Terms and Definitions," in National BIM Standard – United States® Version 3, Washington, DC, National Institute of Building Sciences buildingSMART alliance®, 2015, p. 16. | ||
+ | |||
+ | [3] ISO/IEC/IEEE, "42010 - 2011: Systems and software engineering -- Architecture description," International Organization for Standardization, Geneva, Switzerland, 2011. | ||
- | [5] ISO/IEC/IEEE, "42010 - 2011: Systems and software engineering -- Architecture description," International Organization for Standardization, Geneva, Switzerland, 2011. | ||