Most Unstructured : DVM Whiteboard, Domain-format, Basic English Structure Reference
Key Points:
- Requirements and stories in English (no translation into any 'restricted' English format). However, some useful tips are here.
- This is a top-down approach. Interpretation of the text and translation into code is deferred till needed (should be pretty early).
- Someone's job is to domain-format or domain-markup these sentences in a nested fashion. Basic grammar skills important.
- The final formatted English document is an important deliverable (second only to the code/tests ?).
- A Domain Virtual Machine can take this document and convert it into its specific computer language. My thoughts on this.
- An example with potential translations...
- Some simple Ruby code if it were to be generated for the above example using a DVM, to get a sense of things.
- Important Point: Not attempting Natural Language Processing; rather, to determine basic markup to enable the machine make useful decisions while templating code.
Notes
- Discussion on English as a DL - Andy
- Chris' Notes
- The main goal here is to not tie down the developer/analyst having to define every domain term at the beginning. The interactions should allow him to get a rough and ready code version going. Need to think how to deal with undefined terms.
- Developers will be able to change the code from the DVM. This is a good thing. This may feed back into the domain propositions as well.
Pending Questions
- How does this fit into TDD ?
- How many levels of markup ? To what detail ?
- Markup Editor ?
Chats
Some terms