GW ToDo A Task Manager CSCI 6442 Project Spring, 2016

Requirements Build a WordPress plugin, to be accessible (and free) for public use Can be used by an individual for tracking personal tasks Can be used by an organization to track the organization’s tasks Create, Update, Delete, Display capabilities included Each person or organization sees only their own tasks Flexible reporting tools

Technical Environment Web server from a commercial ISP WordPress to give us a pre-built UI MySQL DBMS

Introduction to GW ToDo GW ToDo : An online application for Generalized Task Management. Support for : Complete Task Management, Groups/Organization hierarchy for multiple level Reports generation : Users can see overview of the task Active, Overdue, Tasks at Risk, On Time Task, etc. Tasks can be reported in task format, calendar format

Why GW ToDo? Flexible : Can be used by Individuals, Groups and Organizations Up-To-Date : Keeps the track of all the Tasks Quick and Robust : User Friendly Interface Reporting : Provides in-depth details of all the tasks. For example - Active Tasks, Overdue Tasks, Complete Tasks etc.

Teams and Membership System Engineering Team : Leads the Project, Coordinates with all teams, controls requirements, establishes software development and configuration control environments Data Administration : Develops and maintains data model and stored procedures Tasks Processing Team : Developed functionality for tasks, users and group management, CRUD operations on tasks Reporting Team : Generation of reports that will help users have an overview of created tasks

Team Requirement Each team must be a mixture of nationalities Each team must be a mixture of experience levels SET should have software development experience DBA team should have significant db experience

Project Requirements A requirements document will be given to the project after the midterm Use case forms will be distributed at that time also Data model design, code design, software engineering process and environment should all begin at that time Weekly progress reports due from each person o Accomplishments during the week: specific accomplishments, not just “worked on” o Planned accomplishments for next week o Homework grade for each progress report, based on difficulty of assignment and accomplishments

Development Environment Nothing is considered accomplished until it works in a shared environment Shared environments: o Development—for software that’s undergoing test o Test—for integrated test of the entire product o Staging—release ready for production o Production SET will establish rules for software release to each environment Only SET will publish into production environment

Development Methodology Usually software development is design, build, test That won’t work—we don’t have time We will conduct design, build, test all at the same time, starting after the midterm SET configures test environments, establishes submission, release procedures DBA team designs data model, first doing parts needed by development teams Development teams develop a first plugin with some functions