View source for Incremental model-based activities

'''Incremental Model-based activities'''

For incremental adoption of model-based approach across SE activities, it is important to consider the flow of information between stakeholders and activities, and between two sequential activities, since the complexity introduced due to any change in approach may be prohibitive. In all these discussions it is assumed that all stakeholders who need to create or consume a particular artefacts have an adequate understanding of the languages used. To consider otherwise would be equivalent to proposing to do one activity in French and another in English when neither of the activity teams speak the other language. A taxonomy has been explored considering the generic transfers of information between the three key elements within MBSE / DCSE, namely:
* The human stakeholder (engineer or engineering manager);
* Document
* Model 

Regardless of the specific SE activity, a view of Effort (cost) versus Effectiveness can provide simple insight into the type of transfer. An elaboration of this Effort/Effectiveness is available on the wiki MBSE Where effort effectiveness page. A complementary perspective of where MBSE can be employed with respect to a subset of ISO 15288 Processes will be produced in a subsequent document; likely processes to be covered will include: architecture definition process; Business or Mission analysis process; integration process; stakeholder needs and requirements definition process; system analysis process; system requirements definition process; validation process; verification process.