Note: the concept of “data-centric SE” is discussed in my blog series: I ntegrated Data as the Foundation of Systems Engineering. are going to provide a positive ROI, improved time to market, reduce the number of product defects, reduce the amount of rework, or reduce the number of warranty work and recalls. Organizations (at the enterprise level) need to perform trade-studies to see if the expense of purchasing a specific SE tool or toolset, maintaining the licenses, training people to use the tool(s), maintaining the tool(s), maintaining models and other work products and their underlying data and information developed by the tool(s), etc. Individual SE tools tend to focus on specific needs and types of work products. The original list has been expanded to include suggestions made at the INCOSE IW 2016 and IW 2017 RWG sessions.Ĭurrently, in order to meet the intent of the INCOSE’s MBSE Initiative, many organizations want to increase their capability to practice SE from a data-centric perspective. Many of these features need a “tool” to realize that capability. During the discussion of these features during INCOSE IW 2016 and IW 2017 RWG sessions, it became clear that the list was more a list of features the organization’s Systems Engineering (SE) toolset needs to have in order for the organization to have the capabilities they need to better manage their systems engineering projects. Note: I originally came up with the list of features with a focus on features that a Requirement Management Tool (RMT) should have to better manage an organization’s requirements throughout the product development lifecycle.
0 kommentar(er)
