Changes between Version 3 and Version 4 of BluePrint/Guidelines/Template

Timestamp:

11/10/10 09:55:54 (14 years ago)

Author:

Dominic König

Comment:

--

BluePrint/Guidelines/Template

@@ -4 +4 @@
 == What is a !BluePrint? ==
 
-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])
+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])
 
   - [http://mekongict.org/2010/06/user-oriented-design/ User-Oriented Design]
@@ -32 +34 @@
 some bullet points, discuss the idea with others and then elaborate.
 
-Tipp: keep the !BluePrint as clear and simple as possible
-
-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]).
-
-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] 
+'''Tipp:''' keep the !BluePrint as clear and simple as possible
 == Description ==