Changes between Version 39 and Version 40 of BluePrints


Ignore:
Timestamp:
01/18/09 10:09:24 (14 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrints

    v39 v40  
    33These are areas of work that need interested developers to tackle.
    44
    5 The Blueprints should act as the specification for [DeveloperGuidelinesTesting Testers] to work with.[[BR]]
    6 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]]
    7 We could look at following a [http://behaviour-driven.org/BDDProcess Behaviour-Driven Development] style (e.g. using tools like [http://www.codeplex.com/pyspec pyspec] or [http://pypi.python.org/pypi/PyFIT/0.8a2 PyFIT]).
     5The Blueprints should act as the [http://en.wikipedia.org/wiki/Requirement Requirements] specification for [DeveloperGuidelinesTesting Testers] to work with.[[BR]]
     6This 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])
     7
     8In order to have a user-centric solution, 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]).
    89
    910Sahana2 requirements: http://wiki.sahana.lk/doku.php?id=req:start