CS5391 Survey of Software Engineering
Project Fall 2007
Personal Time/Defect Tracking System

Official Project Information

Goal

Using a basic software development process (Requirements, Design, Implementation and Verification) develop a Personal Time/Defect Tracking System with a high degree of rigor.

Statement of Need

The Personal Software Process (PSP) requires practitioners to record the time they spend working on specific tasks/projects. Because the PSP is a defect avoidance approach to software quality, practitioners' tract the defeats they find during each development phase. To facilitate tracking this information, the PSP provides forms. These forms are not difficult to use, but they are cumbersome and they make reporting to either the instructor or supervisor difficult. Examples of these forms are provided in Attachment A. For some projects it is necessary to use multiple time and defect recording logs.
The probability of the practitioners to continue to use the PSP with these forms, after completing their train, is very low. What is need is a small application that permits a practitioner to enter and retrieve time and defect data for a specific project. Two features that would extend the tools usability is a project planning a reporting facility and the ability to provide a summary to a central data collection facility.

Basic System

• Implement a basic system (time and defect logs) with all of the necessary documentation and no more than three (3) undocumented defects. You may have more defects, if they are documented.

Extra Credit

• Implement the project planning and reporting facility.
• Implement the central data collection facility.

Required Documents

• Requirements Specification uses IEEE std 830-1998 as a guide. Be sure to include use case and other supporting diagrams.
• Design Specification uses IEEE std 1016-1998 as a guide.
• Program Documentation
• Module Header
• Class Header
• Method/Function headers.
• Data descriptions.
• Verification and Validation uses IEEE std 1012-2004 as a guide
• User Guide as either a help facility or a document of the groups design.
• All diagrams will conform to the UML guidelines.

Due Dates

• Requirements Specification due the 6th week of class.
• Design Specification due the 9th week of class.
• Verification and Validation Plan due the 12th week of class
• Project due the 15th week of class.
• Known defect log due with project.
• Weekly a progress report, filed by the team leader, containing the attendance at the team meeting, time spent on the project by team member, and problems encounter and their resolutions.

Leadership

To insure that each team member will get the experience of being in-charge, the leadership will rotate ever 3 weeks.

Link to Relevant Files

http://www.austinbooking.com/mark/cs5391/links.html
A directory currently maintained (manually) by Mark. Contents (as of 9/10) include the three IEEE documents referenced in the project description.

Group Membership

adolfox at gmail
ds1336 at txstate
julia_isong at hotmail
mark.a.landry at gmail
rao.smita at gmail

Open Forum for Group Input/Comments/Status/Questions

• Added Julia's minutes to the Requirements Specification page. (Mark 9/12)
• Extraneous comment to show newest comments should probably be placed on top (Mark 9/10)
• Note: we probably have to turn in a status report on Monday the 10th (perhaps by 8pm like last week's deadline)
• Requirements Specification page created. (Mark 9/9)