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

Framework

• Appliance
• Authentication, Authorization & Accounting
• Backups
• Barcode
• CSS
• Framework
• Internationalisation
• Mobile Portal
• OCR
• Reporting/Charting
• RESTful API
• Synchronisation
• Ticketing
• VITA Person Entity Model
• Web Setup
• Zero Configuration Networking
• Time

Modules

• Decision Making based on the Delphi method
• GIS
• Instant Messaging
• Inventory Management
• Knowledge Management
• Medical Records for Emergencies
• Messaging Module
  • J2ME Client
• Logistics Module
• Organisation Registry
• Person Registry
  • Fatality Management/DVI
  • Real Time Victim Tracking/Tracing
• Project Management
• Request Tracking
• Situation Awareness/Ticketing
• Situation Reporting
• User Dashboard
• Volunteer Management
• Who's doing What Where and When (4W)

Support Tools

• Bzr Hooks
• Testing
• Trac
• Windows Installer
• Ubuntu live CD and installer

Ideas from the Fire/Police Emergency Response sector:

• ​http://www.decisionsforheroes.com/
• ​http://www.e-sponder.com/express/tour/index.html
• ​http://www.swanisland.net/products/ties_web.htm

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