StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODomain Language: What is the best way to express?
text
Body
copied!<p>One of my client sent me a requirement document and while reading that document there was a flash came in my mind. I started rewriting that big document similar like below. Do you think, an automated tool can generate a data model and rules by running through this. Say, if any client communicate their requirement in this approach, it will make every one to understand the domain better.</p> <p>I understand that since I know what is blog and comment and post I am able to relate it easily here. However, if one chop down all the technical terms of their business in this manner, will it not be easy to make every one on the same page?</p> <ul> <li>Model: <ul> <li>blog <strong>has a</strong> date </li> <li>blog <strong>has a</strong> content</li> <li>blog <strong>has a</strong> author </li> <li>blog <strong>has many</strong> comments </li> <li>content <strong>may have</strong> images</li> <li>content <strong>may have</strong> links </li> <li>comment <strong>has a</strong> blog </li> <li>comment <strong>has a</strong> name </li> <li>comment <strong>has an</strong> email </li> <li>comment <strong>may have</strong> an url </li> <li>comment <strong>has a</strong> date</li> </ul></li> <li>Rules: <ul> <li>blog <strong>cannot be</strong> empty</li> <li>blog <strong>may be</strong> published <strong>or</strong> drafted</li> <li>blog <strong>should have a</strong> author</li> <li>blog <strong>cannot be</strong> deleted <strong>when</strong> comment is present</li> <li>blog <strong>cannot have</strong> comments <strong>after</strong> 20 days</li> </ul></li> </ul> <p><strong>Edit:</strong></p> <p>What I am really trying to come up here is -- once you get a requirement document and if you create a document that is mentioned here you will be able to figure out what the client is exactly looking for. </p> <p>And, the other advantage is that you can use this document for further enhancements and development of the project. Or even a client can directly edit this document by hand since he now learnt how we are looking his requirements (I mean our language). </p> <p>Now to some degree this statements can be interpreted in different way. </p> <p>For example, I could have some tool that will analyze the statements and come up with information like if any model changes, rule changes are made it into this document. </p> <p><strong>Edit:</strong></p> <p>I am currently trying to follow this approach in a complex model like Order Management, I will update here what ever I learnt. Meanwhile, if you anyone is interested in here they can also involve with me.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload