Version 32 (modified by Michael Howden, 11 years ago) ( diff )


Blueprint - Template

Although BluePrints may begin as a rough collection of ideas, ideally they should be developed into formal documentation to support the development of features and requirements. This will contain the following sections:

DescriptionIntroduction into the problem and general description of the suggested solution
Users/Stakeholders Who will be engaged?
User Stories User Story
RequirementsOutline of the requirements
Use-CasesDescriptions of use-cases of the suggested solution
DesignSuggestions for the design of the solution
ImplementationList of existing implementations

BluePrints are developed collaboratively and in several iterations. You can just start with some bullet points, discuss the idea with others and then elaborate.

Tip: keep the BluePrint as clear and simple as possible


Start with a brief description of the solution you have in mind, remember to include:

  • an introduction of the problem
  • overview of the technology architecture of the solution
  • important functionality to be implemented

Tip: involve the stakeholders you have named already in the development of your BluePrint.


A list of the stakeholders/users who will be engaged in the solution.

User Stories

A good User Story should answer the following questions:

  • Who the user is
  • What they want the application to do for them?
  • Why they want it to do that? (Purpose)

A <type of user> wants the system to <do something for them> so that <can achieve a goal>.


Outline requirements for the solution, typically including:

If you include links to external resources, please remember to describe what (contents+format) they contain.


Describe the use-cases of the solution in detail, typically including:

  • actors and use-cases
  • activities (work flow) from the user's perspective

Tip: a simple, fast and multi-platform tool to draw UML diagrams is UMLet (Java-based UML drawing tool).


Describe the possible design of the suggested solution, typically including:

  • data model (e.g. EER or class diagrams)
  • interaction models and sequences
  • screen mockups and wireframes
  • code samples

Tip: it is absolutely reasonable (in fact - desired) to have alternative design options.


Append a list of implementations of this BluePrint, each including:

  • a brief description of the implementation (date/time, name, design options chosen)
  • a link to the code
  • list of deployments of the implementation
  • links to case studies
  • short analysis of achievements/problems


Links to external resources

BluePrint Template

Copy and paste this into the wiki editor, then fill in the sections:

= !BluePrint: <Name of the solution> =

== Introduction ==
<Introduce the problem the solution is meant for>
<Explain why this could be relevant for Eden>

== Description ==
<Briefly describe the solution, e.g. start with a user story>
<Name existing solutions, e.g. in other applications>

== User Stories ==

== Requirements ==
<Outline the requirements here>
<Group requirements in subsections, e.g. functional, non-functional, interoperability etc.>

== Use-Cases ==
<Describe actors and use-cases>
<Describe workflows>
<Include diagrams where useful>
< A <type of user> wants the system to <do something for them> so that <can achieve a goal>. >

== Design ==
<Describe a possible design, repeat any design sections for alternative designs>
<Include diagrams, screen mockups and wireframes where useful>

== Implementation ==
<Leave open for a list of implementation>

== References ==
<Links to external resources>


Eden Development Model

Also see:

Note: See TracWiki for help on using the wiki.