| | 1 | [[TOC]] |
| | 2 | = !BluePrint: Simulation Generator = |
| | 3 | |
| | 4 | == Introduction == |
| | 5 | Generate Simulation Data based on set dummy data and a programmable set of “Stories” the data must tell. Functionality to send messages to user (email or in system pop-up) & create data in response within the simulation |
| | 6 | |
| | 7 | == Description == |
| | 8 | <Briefly describe the solution, e.g. start with a user story> |
| | 9 | <Name existing solutions, e.g. in other applications> |
| | 10 | |
| | 11 | == Requirements == |
| | 12 | <Outline the requirements here> |
| | 13 | <Group requirements in subsections, e.g. functional, non-functional, interoperability etc.> |
| | 14 | |
| | 15 | == Use-Cases == |
| | 16 | <Describe actors and use-cases> |
| | 17 | <Describe workflows> |
| | 18 | <Include diagrams where useful> |
| | 19 | |
| | 20 | == Design == |
| | 21 | <Describe a possible design, repeat any design sections for alternative designs> |
| | 22 | <Include diagrams, screen mockups and wireframes where useful> |
| | 23 | |
| | 24 | The Simulation Generator should be an Eden application so that it is easier to maintain and enhance that a collection of scripts and has it clear focus. |
| | 25 | |
| | 26 | == Implementation == |
| | 27 | <Leave open for a list of implementation> |
| | 28 | |
| | 29 | == References == |
| | 30 | <Links to external resources> |
| | 31 | |
| | 32 | ---- |
| | 33 | BluePrints |
