wiki:BluePrints

Version 92 (modified by Fran Boon, 12 years ago) ( diff )

--

BluePrints

These are areas of work that need interested developers to tackle.

The Blueprints should act as the Requirements specification for Testers to work with.
This could start with a simple User Story (or a full Use Case)
It can then be mocked-up using Wireframes

We could look at following a Behaviour-Driven Development style to formalise requirements whilst still being Agile (e.g. using tools like pyspec or PyFIT).

Joel Spolsky has a good write-up on Why to write Functional Specs & How

Sahana2 requirements: http://wiki.sahana.lk/doku.php?id=req:start

Easy Tasks for Beginners

  • Replace the open_module() used by the menu system with something that doesn't use implicit redirects as these take unnecessary resources
  • Replace jquery.autocomplete.js with jquery.ui.autocomplete.js (1.8.1)
  • Replace jquery.cluetip.js with jquery.ui.tooltip.js (1.9 once released)
  • Provide localisation of jquery.ui.datepicker
    • Means that user profile will need extending to support locales

Framework

Modules

Support Tools

Ideas from the Fire/Police Emergency Response sector:

In time we may use this area to provide just the detailed specifications for the Blueprints functionality within Launchpad

Note: See TracWiki for help on using the wiki.