Index > Software Engineering > 2021-08-31: Effective Team Communications and Domain Analysis
Groups are assigned! That’s cool.
Let’s talk about Key Stakeholders:
The non-key stakeholders get no attention :(
A stakeholder has some interest in the outcome of the project.
It’s a short dev team meeting. Each person should answer three questions:
Things that can go wrong:
Prof, aka the manager, wants to see some things:
Show off!
The Domain is the context in which software operates. What problem are we working in?
This could also be called “The Application Domain”
The Domain Model describes the world in which the system’s users and experts exist. A Domain might have:
A domain model establishes a common understanding of the problem. It uses vocabulary from the problem statement.
Look for the nouns - what do the experts call them? Then, take a gander at the relationships between these “things”.
A domain model looks like an entity-relationship-diagram from database, but it’s a little less formal. It could just be two boxes with an arrow and a label: “An address describes where a customer is”.
It is begun. Take a look at:
Do some things:
Also on the list:
Index > Software Engineering > 2021-08-31: Effective Team Communications and Domain Analysis