Changes between Version 28 and Version 29 of BluePrint/Guidelines/Template
- Timestamp:
- 11/08/12 00:15:30 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Guidelines/Template
v28 v29 25 25 26 26 '''Tip:''' involve the stakeholders you have named already in the development of your !BluePrint. 27 28 == Use-Cases == 29 30 Describe the use-cases of the solution in detail, typically including: 31 32 - actors and use-cases 33 - activities (work flow) from the user's perspective 34 35 '''Tip:''' a simple, fast and multi-platform tool to draw UML diagrams is [http://www.umlet.com UMLet] (Java-based UML drawing tool). 36 27 37 == Requirements == 28 38 … … 36 46 37 47 If you include links to external resources, please remember to describe what (contents+format) they contain. 38 39 == Use-Cases ==40 41 Describe the use-cases of the solution in detail, typically including:42 43 - actors and use-cases44 - activities (work flow) from the user's perspective45 46 '''Tip:''' a simple, fast and multi-platform tool to draw UML diagrams is [http://www.umlet.com UMLet] (Java-based UML drawing tool).47 48 48 49 == Design == … … 86 87 <Name existing solutions, e.g. in other applications> 87 88 88 == Requirements ==89 <Outline the requirements here>90 <Group requirements in subsections, e.g. functional, non-functional, interoperability etc.>91 92 89 == Use-Cases == 93 90 <Describe actors and use-cases> 94 91 <Describe workflows> 95 92 <Include diagrams where useful> 93 < A <type of user> wants the system to <do something for them> so that <can achieve a goal>. > 94 95 == Requirements == 96 <Outline the requirements here> 97 <Group requirements in subsections, e.g. functional, non-functional, interoperability etc.> 96 98 97 99 == Design ==