Dynamic Meeting Scheduler

Size: px

Start display at page:

Download "Dynamic Meeting Scheduler"

Jasper Barrett
8 years ago
Views:

1 Dynamic Meeting Scheduler Preliminary Project Plan Aaron Turrie at.nelret@gmail.com Eric Meyer eric.meyer@utdallas.edu Mario Medina mariomedina.se@gmail.com Jordan Savant jjs074000@utdallas.edu Tyler Smith tyler@tyler-smith.net Tim Caswell creationix@gmail.com David Granado - davidjgranado@gmail.com Preliminary Project Details for: Professor Lawrence Chung CS Phase 2 1

com Jordan Savant - 10493282 - jjs074000@utdallas.edu Tyler Smith - 10460113 - tyler@tyler-smith.

2 Table of Content 1. Introduction... Error! Bookmark not defined. 1.1 Project Description... Error! Bookmark not defined. 1.2 Project deliverables... Error! Bookmark not defined. 1.3 References... Error! Bookmark not defined. 1.4 Definitions, Acronyms, and Abbreviations... Error! Bookmark not defined. 2.Project organization... Error! Bookmark not defined. 2.1 Process model... Error! Bookmark not defined. 2.2 Organizational structure... Error! Bookmark not defined. 2.3 Organizational boundaries and interfaces... Error! Bookmark not defined. 2.4 Project responsibilities... Error! Bookmark not defined. 3. Managerial process... Error! Bookmark not defined. 3.1 Management objectives and priorities... Error! Bookmark not defined. 3.2 Assumptions, dependencies, and constraints... Error! Bookmark not defined. 3.3 Risk management... Error! Bookmark not defined. 3.4 Monitoring and controlling mechanisms... Error! Bookmark not defined. 4. Technical process... Error! Bookmark not defined. 4.1 Methods, tools, and techniques... Error! Bookmark not defined. 4.2 Software documentation... Error! Bookmark not defined. 4.3 Project support functions... Error! Bookmark not defined. 5. Work elements, schedule, and budget... Error! Bookmark not defined. 5.1 Work Elements... Error! Bookmark not defined. 2

.. Error! Bookmark not defined. 2.4 Project responsibilities... Error! Bookmark not defined. 3. Managerial process... Error! Bookmark not defined. 3.1 Management objectives and priorities... Error! Bookmark not defined. 3.2 Assumptions, dependencies, and constraints.

3 1. Introduction 1.1 Project Description This document contains the preliminary information regarding the development of the meeting scheduler system. It provides information in regard to deliverables, project responsibilities, organizational structure, managerial process and schedule of development. 1.2 Project Deliverables The following is a breakdown of deliverables regarding the development of the meeting scheduler system. Phase Deliverable 1 Preliminary Project Plan 2 Requirements Elicitation 3 Requirements Analysis 4 Architectural Design 5 Object/Component Design 6 Coding 7 Testing 3

development. 1.2 Project Deliverables The following is a breakdown of deliverables regarding the development of the meeting scheduler system.

4 1.3 References Reuse openwysiwyg PHPCalendar CalendarControl Timeframe URL dex.htm Calendar Web Reference Prof. Lawrence Chung URL Definitions, Acronyms, and Abbreviations Acronyms: DMS - Distributed Meeting Scheduler ESS - Exclusive Scoring System ISS - Inclusive Scoring System 4

edu/ecn/support/kb/docs/javascript Calendar http://stephencelis.com/projects/timeframe Web Reference Prof.

5 2. Project Organization 2.1 Process Model The development of the Meeting Scheduler System will be completed by team members represented under the project responsibilities section. During initial development, each team member will contribute to the entire structure of the project plan. During development of the project, work will be delegated to each team member based upon the deliverable phases and the role of team leader will change upon each new phase of the project. 2.2 Organization Structure For the project, the team will be organized with one member operating as the team leader and the rest of the team reporting to that individual. Through the various phases of the project, the role of team leader transfers to each member of the team. As team leader, each team member organizes and coordinates the efforts of the team to keep the project on schedule. Team members: Aaron Turrie Eric Meyer Mario Medina Jordan Savant Tyler Smith Tim Caswell David Granado Team leader for each phase: 1. Aaron Turrie 2. Jordan Savant 3. Eric Meyer 5

During development of the project, work will be delegated to each team member based upon the deliverable phases and the role of team leader will change upon each new phase of the project. 2.

6 2.3 Organizational Boundaries and Interfaces Submission Communication Technique Member Responsible Meeting Scheduling Google Group Website Team Leader Project documentation Google Group Website All Communicate group meeting changes, cancellation and etc , Google Group Website, and Phone Team Lead Submit Assigned Work to Group Google Group Website All 2.4 Project Responsibilities The group will consist of seven members, including one team leader. The team leader will be charged with writing meeting minutes, keeping an up to date calendar of planned meetings, and ensuring that all work is posted on the team website on a regular basis. The role of team leader will be rotated, giving all members an opportunity to experience working in a leadership position. Work on the project will be delegated as the project progresses, and will be divided evenly between the members. Each member will be responsible for his own contribution to the group presentation, though the group will work together to ensure the presentation flows nicely. 3. Managerial Process 3.1 Management objectives and priorities Provide an excellent work environment Provide excellent leadership Ensure that the team maintains communication in all aspects of the project Ensure that the project timeline is met Ensure that project members know and fulfill their responsibilities Ensure that the project maintains its quality through its progression Manage risk for all areas of the project 6

4 Project Responsibilities The group will consist of seven members, including one team leader.

7 Ensure that every member of the project is contributing Document all progression 3.2 Assumptions, dependencies, and constraints Assumptions Project members will be reliable and productive The customer will not change the project in anyway and has approved of it as is Customer will be available for contact in case questions arise Dependencies Project must be completed in phases Project must have a project description before continuing with requirements specification Requirement specification needs to be developed before the prototype can be worked on Constraints Resources: o Team members are limited to Risk Management 3.4 Monitoring and Controlling Mechanisms 4. Technical Process 4.1 Methods, tools, and techniques 7

is Customer will be available for contact in case questions arise Dependencies Project must be completed in phases Project must have a project description before continuing with

8 Process model: Agile Unified Process Requirements model: TBD Software Tools: Microsoft Visio/Omnigraffle/DIA: Diagrams Google Groups: Group collaboration Google Office: Project documentation Dreamweaver / Textmate (php) Trac: bug tracking Selenium: Software Testing Version Control: SVN Third Party Tools: openwysiwyg: Rich Text Editor PHPcalendar: Javascript main calendar interface CalendarControl: Javascript Popup calendar Timeframe: Date range selector Computer Systems Prototype Server: LAMP (Linux, Apache, MySQL5, PHP5) SSH, FTP access Client Computer: Standard Web browser (Firefox, IE, Safari, Chrome) 4.2 Software Documentation Software Project Management Plan (SPMP) System Requirements Specification (SRS) Software Design Description (SDD) User Manual 4.3 Project Support Functions Configuration Management Change requests can be tracked using a ticket tracking system such as trac. Version control software such as Subversion will be used to aid in development. Quality Assurance shall be tested using Selenium unit testing. User training shall be provided. 8

9 5. Work Elements, Schedule and Budget 5.1 Schedule Phase Deliverable Due Date 1 Preliminary Project Plan Sep. 3, Requirements Elicitation Sep. 19, Requirements Analysis Sep. 24, Architectural Design TBD 5 Object/Component Design TBD 6 Coding TBD 7 Testing TBD 9

A.Team Software (.DMS) Dynamic Meeting Scheduler Vision Document

A.Team Software (.DMS) Dynamic Meeting Scheduler Vision Document Aaron Turrie - 10451675 - at.nelret@gmail.com Eric Meyer - 10829232 - eric.meyer@utdallas.edu Mario Medina - 2010809959 - mariomedina.se@gmail.com