| Version 115 (modified by , 14 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)
User-Oriented Design
It can then be mocked-up using Wireframes using a tool such as Dia, Balsamiq or just GoogleDoc's new Drawing functionality
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
Easy Tasks for Beginners
Framework
- Appliance
- Authentication, Authorization & Accounting
- Backups
- Barcode
- CSS
- Framework
- Importer
- Internationalisation
- Menu
- Messaging
- Mobile Portal
- OCR
- Reporting/Charting
- RESTful API
- S3XRC
- Synchronisation
- Time
- VITA Person Entity Model
- Web Setup
- Zero Configuration Networking
Modules
- Decision Making based on the Delphi method
- GIS - Mapping
- Hospital Management System
- Inventory Management
- Knowledge Management
- Medical Records for Emergencies
- Logistics Module
- Organisation Registry / Who's doing What Where and When (4W)
- Person Registry
- Project Management
- Request Management
- Situation Awareness/Ticketing
- Situation Reporting
- Survey Tool
- Ticketing Module
- User Dashboard
- Volunteer Management: Human Resources Management
Support Tools
Sahana2 requirements:
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
