The Software Product Model

Welcome to the Software Product Model. A humble but quite opinionated newsletter about software architecture and engineering. The newsletter follows my white paper and publishes smaller, bite-sized content about it.

To get started, read the white paper here:

https://storage.googleapis.com/archmind-whitepapers/Software%20Product%20Model.pdf

Here's what to expect:

• An ontology that joins the conceptual model with the technical models (logical and physical) and defines maps between each model
• A metamodel that centers around behavioral composition and derives software structures around it

Here are some ontological questions and answers you might encounter:

• What is a software product and what models does it need?
• What is Architecture or Engineering in the context of a software product?
• Who are the primary stakeholder groups?

Finally, here are some questions that the metamodel might help with:

• When I draw a line between two boxes, how do I know that line is even valid?
• For a given feature, why do I have to look at a diagram of the entire system?
• What is the relationship between composition and structure?
• How can I define once and render many?

I hope you'll subscribe and help build a community around the model.