Time Works

Project Management Plan

Software Engineering Fundamentals, Fall, 2014

Modication history:

Team Name: Epoch Inc.
Team Members:
# Bryce Mueller - bcmueller1395@eagle.fgcu.edu
# Matt Sinex - mtsinex2695@eagle.fgcu.edu
# Isaac Gainey - iagainey7197@eagle.fgcu.edu
# Tomas Hoelzel - tchoelzel3565@eagle.fgcu.edu
Contents of this Document
Project Overview
Applicable Standards
Project Team Organization
Timeline
Software Life Cycle Process
Tools and Computing Environment
Conguration Management
Quality Assurance
Project Overview
Our application is named Time Works. It will be delivered as a desktop program for Mac OS X and
Windows. It will be written in the Java programming language. Time Works is a scheduling application
that will have two di$erent sets of users. The Student will have the ability to search a database for
professors, room numbers, available/booked rooms, if the room has computers, and how many seats
it can hold. From there they can ll out a request to book a room for a special event. The other user is
an Admin who controls the requests. They have the ability to deny or approve the request. Both users
will have access to a calendar of events.
Version Date Who Comment
v1.0 Sept 22, 2014 Bryce Mueller Filled in team and application name
V1.1 Sept 23, 2014 Bryce Mueller Edited Team Member section, Project
Overview
V1.2 Sept 27, 2014 Bryce Mueller Wrote the Applicable Standards, Team
Organization, Tools and Computing
Environment, Conguration Management
V1.3 Sept 29, 2014 Bryce Mueller Finished Timeline, Software Life Cycle
Process, Quality Assurance
Applicable Standards
We will be abiding by the Java Coding Conventions set by Oracle at this website for our naming,
formatting and commenting etiquette. If the naming convention is not obvious, there should be a
comment next to it explaining what it is. In addition, whomever uploads a new section of code will
leave a comment on the upload of what changed and what the result was. We will also keep
documentation of class diagrams and their uses as well as a owchart of work that has been done and
what needs to completed.
Project Team Organization
We are a team of four Software Engineering Students as listed above. Each member is in charge of
certain aspects of the project.
# Bryce Mueller is the Group Lead and will be in charge of communication with the professor and
the team as well as keeping the website updated.
# Matt Sinex is our Business Manager and will be in control of the majority of the paperwork and
documentation.
# Isaac Gainey is the Programming Manager and will primarily be working on the code for the
program.
# Tomas Hoelzel is the Database Manager. His main focus will be on maintaining our mySQL
database and the connection to our server.
The team will be communicating by means of the Slack application and website. Slack allows us to
send private and group messages as well as upload any kind of le. It also receives updates from our
BitBucket account so we can be notied if anyone has uploaded or changed the source code. In
addition we will meet face-to-face every two weeks for an hour and half meeting.
Timeline
Artifact Due Dates Team member(s)
responsible
Meeting Minutes
Project Plan (document) 9/29/2014 Bryce Mueller
SRS (document) 9/29/2014 Matt Sinex
Design 10/10/2014 Tomas Hoelzel
Prototype 10/20/2014 Tomas Hoelzel
Presentation 1 10/27/2014 Bryce Mueller
Test Results 12/1/2014 Isaac Gainey
User's Manual (document) 12/1/2014 Matt Sinex
Source, Executable, Build
Instructions
12/1/2014 Tomas Hoelzel
Isaac Gainey
Presentation 2 12/8/2014 Bryce Mueller
Software Life Cycle Process
Our team is going to use the Waterfall model for our application. In choosing the type of model, we
rst removed all the models that were not going to work for this project. Then we narrowed it down to
a few that might work. We settled on the Waterfall model because it made the most sense for this
project and the natural way in which we approached it.
Tools and Computing Environment
We will be using a combination of Macintosh OS X and Windows operating systems. The primary
programming language will be Java and mySQL for database management. We are using the IDE
Eclipse to write and compile the source code. For our UI elements we are using the swing Java library.
Other libraries include: SQL, IOStream, calendar.
Conguration Management
We have setup a Bitbucket account to manage the git repository, which will give us the tools for
version and change control. Whenever a change is made to the repository we are all notied. In
addition, if someone chooses to make a fork in the program they will inform the group of their
decision. We are also using an application called SourceTree to interface between Bitbucket and our
Eclipse source folders to keep the les syncing across our computers. Bryce Mueller (Project Lead)
has set up and will be responsible for the maintenance of this conguration.
Quality Assurance
Whoever is making changes to the source code will run the debugger to check for errors. Once we are
able to execute the program we will check all valid inputs for. After that we will enter invalid data to
check for exceptions. All of the errors will be documented in an order of importance and posted for the
group to see. Tomas Hoelzel and Isaac Gainey will be in charge of QA.
Template created by G. Walton (GWalton@mail.ucf.edu) on Aug 30, 1999 and last updated Aug 15,
2000, modied by A. Koufakou Aug. 2014
This page last modied by Bryce Mueller (bcmueller1395@eagle.fgcu.edu ) on Sept 29, 2014