: Public Note
Created: |
12/6/2021 4:25:44 PM |
Modified: |
12/6/2021 5:04:53 PM |
|
Project: |
|
Author: |
1362763084C |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{499C1E65-AF37-4358-B7F4-138B54FA6A1D} |
Appears In: |
Basic Model Structure |
<b><i><u>Basic Model Structure</u></i></b><br/>Each model in the model library has this basic package structure. Some may have additional packages, but these should at least be present to support basic program model structure. Once a program model is created from this reference model library, the program model may also have other packages including, but not limited to: logistics and support, production release, transition, cyber security, safety, etc. <br/><br/><b><i><u>Requirements Location</u></i></b><br/>Current discussions on the domain of where requirements will be maintained are still ongoing (as of December 2021) with the general consensus leaning towards requirements being "held" in the Product Lifecycle Management (PLM) platform. How and where requirements are stored and managed will require scrutiny as this will impact how the modeling tools access those requirements, whether those tools will have direct manipulation or derivation of requirements capability, etc. <br/>A central repository database should be able to be accessed by modeling tools without having to go through the PLM system to get to them. Thus the PLM platform needs to manage the database(s) in a way that is compatible with the modeling tools. A tool-agnostic database definition with a defined platform-independent API is required in order to do that. All tools - modeling tools, MS Office tools, PLM tools, database tools, etc. - all need to have scripting capabilities that allow complete access to data, and ability to create/read/modify/write/destroy any type of data elements within the database. <br/>A version control system with a robust version control process (change submission, review, approval/disapproval, release, bug tracking, feature request reporting, etc.) is necessary to ensure the integrity of the data, and that change is managed sensibly.<br/>