Model-based Systems Architecting by Daniel Krob

Author:Daniel Krob [Olivier Cardin]
Language: eng
Format: epub
ISBN: 9781119988489
Published: 2022-06-10T00:00:00+00:00

4

Identifying Stakeholders: Environment Architecture

4.1. Why identify stakeholders?

Stakeholder identification, or equivalently environment architecture, is a key systemic analysis: each mistake in this analysis may indeed result in flaws in the product under design. We must indeed remember that a system is nothing other than a concrete answer to a series of needs1 and that these needs are coming from external stakeholders. As an immediate consequence, forgetting important stakeholders, misevaluating their role and/or considering erroneous ones will result in missing needs and/or working with incorrect needs, and hence in missing requirements and/or working with wrong derived requirements, relatively to a given system. The resulting concrete system that might be developed on such a basis will therefore typically either miss the functions and components that are specifically addressing these missing needs, or have unnecessary functions and components that are associated with these incorrect needs. We can therefore easily understand the crucial importance of correctly identifying stakeholders – that is, the necessary and sufficient ones – since any system development process fundamentally relies on the quality of this identification.

To stress on this last point, we shall also have in mind the potential cost(s) of incorrect stakeholder identification which explain why we must put the necessary energy into this core initial analysis. In this matter, we commonly consider that such costs follow a geometric progression within the system lifecycle (see Figure 4.1): if the correction of an error during stakeholder identification has cost 1 (i.e. typically adding a missing stakeholder or replacing an erroneous stakeholder in this analysis), we usually consider that correcting the consequence of that error will have cost 10 when done during system design, cost 100 when corrected during detailed design, cost 1,000 when discovered during integration and even cost 10,000 if managed when the system is in service. We must thus spend enough time initially in order to achieve an as-sound-as-possible environment architecture.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.