The team is comprised of Salim Andraos, Joseph Burfield, Sacchin Nayee, Paul Perdue, and Carlos Pereda. As Carlos is the most mature team member and is only taking two classes, he was elected to project manager by the group. Not to mention Carlos has previous software development experience.

As far as other duties go, jobs will be divided evenly between all team members. Exposure to all aspects of the software development life cycle to all team members is very important to this group. The group website and the collaboration website was initially https://andraos.visualstudio.com but later switched to GitHub. Both are maintained by the group as a collaborative effort. Communication is done via email until the team is further into project which then will switch to collaboration website.

This team is adapting the agile software development model for its solution. Frequent delivery of small increments of working software is the goal. All requirements and solutions evolve through collaboration between all team members.This team is following the Waterfall model. Since we are on a preset schedule arranged by the intructor and the requirements and specifications were clear from the onset, waterfall model is aplicable. Furthermore, there was no need to go back and revise any of the stages.

We are using Visual Studio as our IDE, C# as our language, and most likely SVN GitHub as our software versioning and revision control system. The reasons for choosing Visual Studio and C# as our language and IDE are ease of integration and synchronization between Microsoft Project, Visual Studio, and Visio. Furthermore, collaboration between Visual Studio and our collaborative website is further enhanced. Also, Visual Studio's outstanding GUI builder should ease the UI design phase.(see above)

Each team member is responsible for all changes made to each document. Changes to a document and source code shall be clearly noted in the document itself.

Since the work is divided evenly between all team members and this team intends to expose all its members to all aspects of the development life cycle, each member reviews each document. This has two purposes: 1) Quality Assurance is guaranteed throughout the life cycle since each document gets reviewed by six people, and 2) all team members get to see the workings of each document.

Please see detailed GANTT chart below

Please see detailed GANTT chart below

Project Management Plan GANTT Chart

Each phase is appropriately divided into deliverables. We shall use the due dates (i.e. days) for our deliverables metrics and as per the industry standard use bytes, instead of lines of code, as our metrics for coding.

The project manager will post the following information weekly: group time and activity log, status information, issues and problems, and group defect log.

Each week, the project manager will read and analyze the logs, examine the technical content of the work done to date, examine the technical progress metrics, reassess the potential project risks, and take corrective action if necessary.

The project manager will issue a Project Management Report on the schedule as indicated in the deliverables section above. At a minimum, the Project Management Report will be generated every two weeks and will include the following information: 1 sentence description of overall status, 1 or 2 sentence of any planned changes to the project plan, graph of planned vs actual time, graph of planned vs actual for each technical progress metric, and update the GANTT chart."