Release Plan

Symptomatic Release Plan

Overview:

The strategy is to implement riskier tasks earlier, such as adding geo locations, and mapping photos to body locations.
- These riskier tasks can be implemented as soon as we implement a problem list that we can add records to. Thus, we should get these simple tasks out of the way quickly.
- More comprehensive/time consuming tasks can be divided into teams of 2 or 3 members
- Internal timelines should be created for each task depending on the number of members assigned to that task and the tasks complexity.
Tasks that rely heavily on the completion of other tasks, such as searching for problems or records near a body-location, can be implemented later on (part 5) once we have successfully completed the relied upon task.
Must have a working prototype with about half of the requirements implemented for part 4. There must be some server connectivity at this point.
In order to release a proper prototype for part 4 we must ensure that we implement the main tasks that connect patients with their care providers (such as "add patients"). This ensures potential use from our prototype.
Project part 5 contains additional objectives, such as preparing a product promotional video.
- We must keep this in mind when planning out our time management.
We must prioritize time for testing prior to releases. Testing should be done early to ensure that we finish on schedule.
** The release plan is subject to change based on user requirements and task complexity.

Deliverables/Goals:

Must have server connectivity for this release.
- Syncing and saving user data.
- User login functions.
Develop the separate user functions needed for patients and care providers.
** Get small tasks out of the way early to start developing and testing more complex tasks.
- Have to be able to add records to problems in order to start testing photo addition/geo-location.
Get photo functionality fully incorporated in this release
- Making photos consistent
- Adding photos to records
- Slideshow mode saved for part 5
Implement adding body location to photos with cutout doll
If all goes well, start implementing geolocation before this release deadline.
*** Must make time for integration and functional testing throughout

Delegation of tasks:

Note: More comprehensive/time consuming tasks are comprised of 2 members.
Nick:
- User login and creating accounts
- User records functionality
- User problem functionality
Ryan:
- Server connectivity (saving and syncing data)
- Adding body location to records
Helen:
- Photo functionality such as making photos consistent and adding photos to records.
Ahzam:
- User problems functionality
- Care provider functionality
Aaron:
- Server connectivity (saving and syncing data)
- Adding body location to records
Amy:
- Photo functionality such as making photos consistent and adding photos to records.

Use Cases and the User Stories that they cover for this release:

Note: The Use cases are listed in terms of priority: High priority use cases at the top, low priority at the bottom. (besides testing)

Deliverables/Goals:

Incomplete tasks have been pushed forward from project part 4.
Finish any possible underlying issues from project part 4.
Finish photo functionality.
Finish geolocation functionality.
Finish Search functions.
Finish small tasks that were not key to project part 4 functionality.
- Such as caregiver commenting on patient record.
Prepare product promotional view.
Prepare product demonstration.
If all is completed, work on "Wow Factor" functions.
*** Must make time for integration and functional testing throughout.

Delegation of tasks:

Note: More comprehensive/time consuming tasks are comprised of 2 members.
Nick:
- Geolocation and map functionality.
Ryan:
- Slideshow mode.
- Viewing user profiles.
Helen:
- Search functionality.
Ahzam:
- Geolocation and map functionality.
Aaron:
- User contact info.
- Care provider adds comment.
- Deleting/editing problems.
Amy:
- Search functionality.

Use Cases and the User Stories that they cover for this release:

Note: The Use cases are listed in terms of priority: High priority use cases at the top, low priority at the bottom. (besides testing)