📝§ Software Modeling

Modeling does not necessarily involves building programs and running simulations. Sometimes, it’s just drawing a diagram or a table.

Master models:

• Business model (TODO)

• Domain model—describe the problem domain regardless of your solution

  • For domain modeling, beware of adding technical details

• Design model—describe designed solution

• Code model—the code of actual implementation

Tips

• Question first and model second

• When modeling, pick important details and ignore the rest

• Use simple notations

• Put legend on diagrams

• Avoid arrowheads on connectors

• Use hand-drawn diagrams to convey a feeling of casual and temporary

See also

• Levels of using models

  • Models can be used to amplify reasoning

• Multi-level functionality scenarios

• § Mental models—software models are mental models

Backlinks

• 📝 Avoid arrowheads on connectors
• 📝 Put legend on diagrams
• 📝 § Software Architecture