Phase 1 Report Format
Phase 1 Report Format
Objectives [1 page]
This section should detail the objectives of this proposal which must be focused on
the general theme of the Caribbean Innovators Challenge: Mobile Applications for
Development, developing a needs-based, pro-poor mobile application for an
identified community.
Rationale [1 page]
This section is expected to explain, using fundamental reasons, the selection of a
mobile solution that meets the competitions theme. This section should identify the
needs of a low-income community and document the contemplation of ideas that
must satisfy these needs to realise expected benefits.
In this section, the contestants are expected to:
Select a low-income community based on the analysis of existing and new
data
Identify the information and communication needs of this community
Propose a mobile application intervention that meets the above needs
Suggest the expected benefits of the mobile application to the identified
community
Identify how the activities or outputs of the proposed application
development could be incorporated into the teaching and / or research at the
candidates TLI as a means of stimulating further development-focussed
mobile innovation in the Caribbean.
Design
This section should report on the use of requirements specifications, in the previous
section, to transform the user requirements into a high-level view, functional design
of the mobile application. It should include a description of the process used to
develop a structured design as well as the input data, output data and processes
that transform input data to output data.
This design is required to show the key functionalities of the mobile application
using at least one static and at least one dynamic design model. Static models show
the structural aspect, which defines the modules or sub-systems that constitute the
system. Examples of these include Block Diagrams, Data Flow Diagrams, Use Case
Diagrams and Class Diagrams. Dynamic models show the responses of a system to
certain events or actions. Examples of these include Flow Charts, Activity
Diagrams, State Machine Diagrams and Collaboration Diagrams.
This section leads the contestant to visually represent the system so that it can be
easily explained to an audience of non-software engineers or developers to facilitate
a thorough understanding of the operation of the mobile application.
Schedule [1 page]
This section should document an initial project plan for the development and
deployment of the mobile solution. It should define required resources and activities
for development and deployment of the mobile application.
Budget [1 page]
This section should detail costs associated with all elements of development and
deployment of the mobile application.