I think that will deserve another article lol. The answer is.... it depends. 😋
Non-functional requirements, system qualities/attributes, cost considerations, staff expertise, etc. all play part in how the actual implementation might work out.
From reading your article, I got the feeling that its inspired from Pivotal Software. After interacting with Pivotal people, I got the impression that when modeling Domains the Architecture will reveal itself and we can start coding and building on that architecture. Is my interpretation correct? if so, can you provide me with an example of this process?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that will deserve another article lol. The answer is.... it depends. 😋
Non-functional requirements, system qualities/attributes, cost considerations, staff expertise, etc. all play part in how the actual implementation might work out.
From reading your article, I got the feeling that its inspired from Pivotal Software. After interacting with Pivotal people, I got the impression that when modeling Domains the Architecture will reveal itself and we can start coding and building on that architecture. Is my interpretation correct? if so, can you provide me with an example of this process?