It reinforces to the business stakeholders that you care about, and eventually confirms you understand, the business needs that the system being designed is intended to fulfill.It is very understandable to business stakeholders.Some reasons it is a great early-stage view: Basically, it defines the capabilities of the system in the middle of the diagram by capturing the expectations that the users have of it. The diagram helps us quickly understand an existing system or define a “to be” system, by defining the ways users will rely on it. It provides a high level functional view of a system and, while it is very powerful for the early stages of functional design, it also ensures you have identified any functional needs that impact the non-functional, or architectural, aspects of the design. We use a system context diagram in the early stages of our Investigative Architecture™ process.
0 Comments
Leave a Reply. |