Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Req-2.1: Prevalent digital representation throughout time #3

Open
capsulecorplab opened this issue Mar 2, 2019 · 0 comments
Open
Labels
ConOps Concept of Operations - focuses on the context in which the system is operated. Non-Functional Requirement (NFR) Specifies system attributes - s.a. security, reliability, performance, maintainability, scalability. user story As a <role> I want <requirement> so that <reason/ROI>.

Comments

@capsulecorplab
Copy link
Contributor

capsulecorplab commented Mar 2, 2019

As a systems engineer, I want prevailing digital representation of a product in each point in time, in order to foster traceability of artifacts and ensure permeability of documentation.1

1 Heber, D. and Groll, M. “Towards a Digital Twin: How the Blockchain Can Foster E/E-Traceability In Consideration of Model-Based Systems Engineering.” 21st International Conference on Engineering Design. 21-25 August, 2017. p. 324

@capsulecorplab capsulecorplab added user story As a <role> I want <requirement> so that <reason/ROI>. ConOps Concept of Operations - focuses on the context in which the system is operated. labels Mar 2, 2019
@capsulecorplab capsulecorplab added the Non-Functional Requirement (NFR) Specifies system attributes - s.a. security, reliability, performance, maintainability, scalability. label Mar 2, 2019
@capsulecorplab capsulecorplab changed the title Prevalent digital representation throughout time Req-2.1: Prevalent digital representation throughout time Mar 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ConOps Concept of Operations - focuses on the context in which the system is operated. Non-Functional Requirement (NFR) Specifies system attributes - s.a. security, reliability, performance, maintainability, scalability. user story As a <role> I want <requirement> so that <reason/ROI>.
Projects
None yet
Development

No branches or pull requests

1 participant