Changes between Version 16 and Version 17 of Projects/DSO


Ignore:
Timestamp:
05/11/15 02:30:42 (10 years ago)
Author:
Tanu Chellam
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Projects/DSO

    v16 v17  
    2727
    2828
     29=Product and Technical Requirements=
     30==Stakeholders==
     31Within Sahana:
     32
     33==Market Assessment==
     34
     35
     36
     37==Product Overview and Use Cases==
     38
     39==Functional Requirements==
     40Defines what the web setup toolkit should do
     41
     42== Usability Requirements==
     43
     44
     45==Technical Requirements==
     46Defines security, network, platform, integration, clients
     47
     48
     49==Environmental Requirements==
     50
     51==Support/Maintenance Requirements==
     52
     53==Interaction Requirements==
     54Defines how the web toolkit should work with other systems
     55
     56==Assumptions==
     57
     58==Constraints==
     59
     60==High level workflow plans==
     61
     62==Timelines and Milestones==
     63
     64More info in our project plan/scope: https://docs.google.com/document/d/1BCGrEnTtgKCWCrvI9XQl1_ePkJdz8QYCd88hKIBOC78/edit#
     65
     66
     67==Evaluation Plan and Performance Metrics==
     68
    2969= Data Sources =
    3070Currently there is data (predominantly Location Hierarchy/Boundaries
    … …  
    3676environment.
    3777= Configurations / Deployment Process =
    38 Currently, Sahana architecture does not allow the default Sahana template to be deployed as-is. Often, deployments override the default template based on case specifics; Sahana does not have generic templates for standard scenarios which can be easily configured via web setup and rolled out by any community or organization without additional code development. Hence, DSO hopes for our work to contribute to the future development of the web setup facility of Sahana and the development of multiple standard scenarios and turnkey-templates for them.
     78At this time, Sahana architecture does not allow the default Sahana template to be deployed as-is. Often, deployments override the default template based on case specifics; Sahana does not have generic templates for standard scenarios which can be easily configured via web setup and rolled out by any community or organization without additional code development. Hence, DSO hopes for our work to contribute to the future development of the web setup facility of Sahana and the development of multiple standard scenarios and turnkey-templates for them.
    3979
    4080(Our understanding is based on [https://groups.google.com/forum/#!msg/sahana-eden/YRNJf0eOXvY/-cljOWG7-XoJ this conversation] with seasoned Sahana developers)