| | 5 | |
| | 6 | == Introduction == |
| | 7 | <Briefly describe the solution?> |
| | 8 | <What problem is this solution solving?> |
| | 9 | <How will this solution add value to Sahana?> |
| | 10 | <Name any similar existing solutions> |
| | 11 | |
| | 12 | == Stakeholders == |
| | 13 | <Who will be the users of the solution?> |
| | 14 | <Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?> |
| | 15 | <How will stakeholders be affected?> |
| | 16 | Tip: Engage these stakeholders in the development of your !BluePrint. |
| | 17 | |
| | 18 | == User Stories == |
| | 19 | <http://en.wikipedia.org/wiki/User_story> |
| | 20 | <A good User Story should answer the following questions:> |
| | 21 | <* Who the user is> |
| | 22 | <* What they want the solution to do for them?> |
| | 23 | <* Why they want it to do that? (goal)> |
| | 24 | <eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.> |
| | 25 | |
| | 26 | == Requirements == |
| | 27 | <Group requirements in subsections, e.g.,, etc.> |
| | 28 | <http://en.wikipedia.org/wiki/Requirements_analysis requirements> |
| | 29 | <Identify different types of requirements:> |
| | 30 | === Functional === |
| | 31 | === Non-functional === |
| | 32 | http://en.wikipedia.org/wiki/Non-functional_requirements |
| | 33 | === Interoperability === |
| | 34 | === Standards === |
| | 35 | === System Constraints === |
| | 36 | |
| | 37 | == Design == |
| | 38 | <Where relevant include alternative design options> |
| | 39 | === Data Model === |
| | 40 | (e.g. EER or class diagrams) |
| | 41 | === Workflows === |
| | 42 | <Diagrams or Pseudocode> |
| | 43 | === Site Map === |
| | 44 | <for User Interface solutions> |
| | 45 | === Wireframes === |
| | 46 | <for User Interface solutions> |
| | 47 | === Technologies === |
| | 48 | |
| | 49 | == Current Implementation == |
| | 50 | <Leave open for a list of existing implementation of this solution in Sahana Eden:> |
| | 51 | <*a brief description of the implementation (date/time, name, design options chosen)> |
| | 52 | <*a link to the code> |
| | 53 | <*list of deployments of the implementation> |
| | 54 | <*links to case studies> |
| | 55 | <*short analysis of achievements/problems> |
| | 56 | |
| | 57 | == Planned Implementation == |
| | 58 | <List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on> |
| | 59 | |
| | 60 | == Future Extensions == |
| | 61 | <List of features which could be included, but are outside of the scope of this extension> |
| | 62 | |
| | 63 | == Outstanding Questions == |
| | 64 | <Questions about the features or design that haven't been (and need to be) answered> |
| | 65 | |
