Changes between Version 1 and Version 2 of BluePrint/Guidelines/Template
- Timestamp:
- 11/10/10 09:53:25 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Guidelines/Template
v1 v2 4 4 == What is a !BluePrint? == 5 5 6 We use [http://en.wikipedia.org/wiki/Blueprint !BluePrints] to capture ideas, 7 requirements and design options for Eden components. 6 We use [http://en.wikipedia.org/wiki/Blueprint !BluePrints] to capture ideas, requirements and design options for Eden components. 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]) 8 7 9 The Blueprints should act as the [http://en.wikipedia.org/wiki/Requirement Requirements] specification for [DeveloperGuidelinesTesting Testers] to work with.[[BR]] 10 This could 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])[[BR]] 11 [http://mekongict.org/2010/06/user-oriented-design/ User-Oriented Design] 12 [[BR]] 13 It can then be mocked-up using [http://webstyleguide.com/wsg3/10-forms-and-applications/4-design-process.html Wireframes] using a tool such as [http://live.gnome.org/Dia Dia], [http://balsamiq.com Balsamiq] or just [http://doc.google.com GoogleDoc]'s new Drawing functionality 8 - [http://mekongict.org/2010/06/user-oriented-design/ User-Oriented Design] 14 9 15 We could look at following a [http://behaviour-driven.org/BDDProcess Behaviour-Driven Development] style to formalise requirements whilst still being [http://en.wikipedia.org/wiki/Agile_software_development Agile] (e.g. using tools like [http://www.codeplex.com/pyspec pyspec] or [http://pypi.python.org/pypi/PyFIT/0.8a2 PyFIT]). 10 It can then be mocked-up using [http://webstyleguide.com/wsg3/10-forms-and-applications/4-design-process.html Wireframes], using tools like: 16 11 17 Joel Spolsky has a good write-up on [http://www.joelonsoftware.com/articles/fog0000000036.html Why to write Functional Specs] & [http://www.joelonsoftware.com/articles/fog0000000035.html How] 12 - [http://live.gnome.org/Dia Dia] 13 - [http://balsamiq.com Balsamiq] 14 - [http://doc.google.com GoogleDoc]'s new Drawing functionality 18 15 19 16 !BluePrints can be used by yourself or other contributors to: 20 17 21 18 - develop and evaluate solutions 22 - develop test cases19 - develop [wiki:DeveloperGuidelinesTesting test cases] 23 20 - write documentation 24 21 … … 37 34 Tipp: keep the !BluePrint as clear and simple as possible 38 35 36 We could look at following a [http://behaviour-driven.org/BDDProcess Behaviour-Driven Development] style to formalise requirements whilst still being [http://en.wikipedia.org/wiki/Agile_software_development Agile] (e.g. using tools like [http://www.codeplex.com/pyspec pyspec] or [http://pypi.python.org/pypi/PyFIT/0.8a2 PyFIT]). 37 38 Joel Spolsky has a good write-up on [http://www.joelonsoftware.com/articles/fog0000000036.html Why to write Functional Specs] & [http://www.joelonsoftware.com/articles/fog0000000035.html How] 39 39 == Description == 40 40