Skip to content

Add stakeholder, and possible needs to the context #46

@Baasie

Description

@Baasie

Hello friends!

I want to suggest to add at least a stakeholder field to the canvas. I find it important, also for software architecture, to know who the stakeholders are. These can of course be the users (Specified) that interact with the model, but also departments in the organisation that have certain needs they need to see fulfilled.

For instance, for a cinema, you can model the bounded context called movie screening seat allocation. Who has the stakeholder which is a movie visitor that want to select seats. Then we might also have finance who's needs is it to fully fill the cinema as much as possible. But at some points during corona you also have legal that had certain needs to the context.

Now the more stakeholders on a context can signal that the context might be to big as wel!

Now all can be described right now in the purpose, but I would like to make it explicit in the canvas, including the needs.
Here an example of how it might look like, but first let;s discuss if it is needed!

afbeelding

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions