5 | | == What is a !BluePrint? == |
6 | | |
7 | | We use [http://en.wikipedia.org/wiki/Blueprint BluePrints] to capture ideas, requirements and design options for Eden components. |
8 | | |
9 | | This can start with a simple [http://en.wikipedia.org/wiki/User_story User Story] (or a full [http://en.wikipedia.org/wiki/Use_case Use Case]) |
10 | | |
11 | | - [http://mekongict.org/2010/06/user-oriented-design/ User-Oriented Design] |
12 | | - [http://www.jnd.org/dn.mss/activity-centered_design_why_i_like_my_harmony_remote_control.html Activity-Centered Design] |
13 | | |
14 | | It can then be mocked-up using [http://webstyleguide.com/wsg3/10-forms-and-applications/4-design-process.html Wireframes], using tools like: |
15 | | |
16 | | - '''[http://code.google.com/p/evoluspencil Evolus Pencil]''' (FOSS, also as Add-on for Firefox 3.5+, GPL2) |
17 | | - Install Pencil as Firefox Add-on directly from [http://code.google.com/p/evoluspencil/downloads/detail?name=Pencil-1.2-0-fx.xpi here] |
18 | | - [http://live.gnome.org/Dia Dia] (FOSS, GPL) |
19 | | - [http://balsamiq.com Balsamiq] (non-OSS, US$79) |
20 | | - [http://doc.google.com GoogleDoc]'s new Drawing functionality |
21 | | |
22 | | !BluePrints can be used by yourself or other contributors to: |
23 | | |
24 | | - develop and evaluate solutions |
25 | | - develop [wiki:DeveloperGuidelinesTesting test cases] |
26 | | - write documentation |
27 | | |
28 | | Typically, a !BluePrint would contain the following sections: |
| 4 | 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: |