//// ---- This is a test commit from Galen Goforth - ghgofort ---- ////
//// ---- This is a test commit from Kevin Bryant - kjbryan1 ---- ////
//// ---- This is the test commit from Thomas Johnson (tjjohn1) for testing ability to edit ---- ////
//// ---- This is a test commit from Michael Gibson - mdgibso2 ---- ////
This is the initial dump for the cst316 spring 2016 project. It is a slightly modified version of the Memoranda project from memoranda.sf.net
The purpose of this project is to enhance the Memoranda application to support Time Management for Software Engineers. In essence, to augment Memoranda with features that support the time management concepts in the Personal Software Process, which you learned some of last year in SER215.
Memoranda is a project that has largely been dormant since 2007, so why are we using it? I have used this codebase in the past, it is of sufficient size and scope to challenge your skills in understanding a complete application (it has somewhere in the neighborhood of 25k lines of code). It also has features that just about anyone who has ever used a calendaring application can understand. Further, I have some documents from a former student project (one of the best ever done in my projects' classes) that we can leverage to help you bootstrap your Agile process.
In the docs directory are a few starting documents that may help you get going on your User Stories. The first is a Project Inception document. This short document describes the vision of the project, and can serve as a guide as you write your Sprint Goals. One is a SRS - Software Requirements Specification - which has 21 use cases that you can readily translate to stories. However you are not constrained to just use these nor are you required to use all of them.
Also in the docs directory is an initial set of analysis models - class diagrams and sequence diagrams in UML, that a previous team did as part of their solution process. These were included only in the event that you may want to use these as a head start on your design and implementation work. You are absolutely not required to use or implement anything in the analysis document!
Your first steps should be to get your team set up with this code, ensure you can build it and run it. The ant script should work, and you should also be able to run it directly from within Eclipse or the command line or from the .bat/.sh scripts provided.
Enjoy! Dr. Gary