DNA

	Spring Quarter 1997	Project Team:
	Project Sponsor:	Alp Sendil	(Manager)
	Gregory Abowd	Enda Sullivan	(Architect) & (QA)
		Bob Sumner	(Programmer)
		Lynn Bacher	(Technical Writer)

• Task Descriptions

  1.0 Fractals

  1.01 Color Scheme

  2.0 The Learning Algorithm

  3.0 Web Development

  4.0 Processing Votes

  5.0 Administrative Tasks

  6.0 Required Documentation

• Tabular Schedule

Task	Description	Total Hours
1.0	Color Fractals	30
1.1	Learning to generate fractals/research Looking at similar research, finding fractal generators, deciding which kind of fractal to use Exit Condition: Bob and Alp are able to meet to discuss strategy Assigned: Bob	6
1.11	Meeting Meeting to determine strategy in generating fractals Exit Condition: Consensus reached by Alp and Bob Assigned: Alp & Bob	1
1.12	Meeting Meeting to discuss interface of fractal generation and selection Exit Condition: Consensus between Enda and Bob Assigned: Enda & Bob	1
1.2	Writing code Code will generate images based on explicit parameters Exit Condition: A fractal image will be generated Assigned: Bob or Alp	10
1.21	Converting fractals Fractals need to be converted to .gif format Exit Condition: An image is converted Assigned: Bob or Alp	1
1.22	Testing Testing parameters of program Exit Condition: Program passes test criteria Assigned: Lynn & Alp	2
1.3	Documentation Documenting material learned and generated Exit Condition: Material added to notebook Assigned: Bob & Lynn	2
1.4	Configuration Management Tracking updates and storing previous versions of code Exit Condition: Previous version is stored in history file Assigned: Bob	1
1.01	Color Scheme	22
1.011	Exploring Color Use Finding a way to use color in the generation of fractals Exit Condition: Understand how color maps are used in the generation of fractals Assigned: Alp	2
1.012	Coding Color Learning Design and coding of an algorithm to incorporate color into fractals Exit Condition: The algorithm produces color maps Assigned: Alp	5
1.013	Testing Testing the program Exit Condition: The program passes the testing criteria Assigned: Alp	2
1.014	Integration Integrate the color algorithm so that it is used by the fractal generator Exit Condition: Color fractals are generated Assigned: Alp & Bob	2
1.015	Testing Testing the integration of the color module Exit Condition: The program passes the testing criteria Assigned: Alp & Bob	2
1.016	Documentation Documenting material learned and generated Exit Condition: Material added to notebook Assigned: Alp & Lynn	2
1.017	Configuration Management Tracking updates and storing previous versions of code Exit Condition: Previous version is stored in history file Assigned: Alp	1
2.0	The Learning Algorithm	25
2.1	Understanding Algorithm Understanding how we will generate future generations of fractals Exit Condition: An algorithm is decided upon in agreement with Enda Assigned: Bob	3
2.2	Designing & coding The algorithm is design and coded based the earlier plan Exit Condition: A set of fractals in generated from previous fractals Assigned: Bob	10
2.21	Testing The algorithm is tested for a variety of different combinations Exit Condition: Testing criteria is passed Assigned: Bob or Alp	5
2.3	Documentation Documenting material learned and generated Exit Condition: Material added to notebook Assigned: Bob & Lynn	3
2.4	Configuration Management Tracking updates and storing previous versions of code Exit Condition: Previous version is stored in history file Assigned: Bob	1
3.0	Web Development	27
3.1	Create web page Create the web page for the user to select images Exit Condition: A web page is completed and linked from the project page Assigned: Enda & Lynn	2
3.2	Create web page Create the web page for the "pick of the hour" Exit Condition: A web page is created and displays a .gif Assigned: Enda	1
3.21	Learning CGI Review of CGI code pertaining to this project Exit Condition: Start to write the code Assigned: Enda	2
3.3	Writing CGI script Writing the code that will record the votes to agreed upon format Exit Condition: A file is generated that accurately reflects the users choices Assigned: Enda	1
3.31	Testing The web pages are tested Exit Condition: The pages pass the testing criteria Assigned: Enda & Lynn	2
3.311	Check different platforms Test our program on different platforms Exit Condition: The program passes the testing criteria Assigned: All	2
3.312	Check different browsers Test our program using different browsers Exit Condition: The program passes the testing criteria Assigned: All	1
3.4	Configuration Management Tracking updates and storing previous versions of code Exit Condition: Previous version is stored in history file Assigned: Enda	1
3.5	Documentation Documenting material learned and generated Exit Condition: Material added to notebook Assigned: Enda & Lynn	1
4.0	Processing Votes	51
4.1	Learning Perl Review of Perl needed to complete the vote processing Exit Condition: Able to write the code Assigned: Enda	1
4.2	Writing script Writing the code to process votes and determine the top images Exit Condition: The code returns values that accurately reflect the users choices Assigned: Enda	15
4.3	Accessing fractal program Integrating the user interface with the fractal algorithm Exit Condition: When a user selects the pictures a new set of fractals is generated Assigned: Bob & Enda	4
4.4	Testing The algorithm is tested for a variety of different combinations Exit Condition: Testing criteria is passed Assigned: All	5
4.5	Documentation Documenting material learned and generated Exit Condition: Material added to notebook Assigned: Bob & Lynn	3
4.6	Configuration Management Tracking updates and storing previous versions of code Exit Condition: Previous version is stored in history file Assigned: Bob	1
5.0	Administrative Tasks	184
5.1	General meetings General meetings twice a week Exit Condition: Everyone attends the meetings Assigned: All	24
5.11	Meeting documentation Writing of agendas, keep minutes, mailings Exit Condition: Agendas prepared for each meeting and minutes posted Assigned: Alp & Lynn	10
5.12	Progress and schedule updates Re-evaluating schedules as needed Exit Condition: Schedules remain up to date and documented Assigned: All	6
5.2	Status meetings Preparation and attending status meetings with client Exit Condition: Client is updated on current status of the project Assigned: All	9
5.3	Obtaining equipment Obtaining flat screen LCD and any other equipment required Exit Condition: The equipment is obtained Assigned: Alp & Lynn	2
5.4	Obtaining resources Obtaining storage space and computer resources Exit Condition: Are able to store code and use additional resources Assigned: Alp & Enda	2
6.0	Required Documentation	24
6.1	Project Plan Project Plan due 4/18/97 Exit Condition: A document introducing the project topic, team members and providing a schedule for activities to be performed during the quarter is written and posted to the team web page Assigned: All	1
6.2	Requirements Document Requirements Document due 4/28/97 Exit Condition: An extended document that details all functional requirements of the delivered prototype is written and posted to the team web page Assigned: All	1
6.3	Test Plan Test Plan due 5/5/97 Exit Condition: A document that describes how the software product will be tested and includes a section to be filled in later on test results is written and posted to the team web page Assigned: All	1
6.4	Design Document Design Document due 5/16/97 Exit Condition: A detailed description of how the system will be built, including, for example, a high-level software architecture and any component interfaces or interfaces object-oriented analysis and design to show the system structure is written and posted to the team web page Assigned: All	1
6.5	Configuration Management Plan Design Document due 5/19/97 Exit Condition: A description of the procedures to be followed by the team to provide for version control and other configuration management concerns for the whole project is written and posted to the team web page Assigned: All	1
6.6	Early Demo and Final Prototype Plan Design Document due 5/28/97 - 6/6/97 Exit Condition: A presentation is made Assigned: All	1

Table Legend
	Scheduled Task		Additional Time Scheduled
S	Task Started	S	Start Deviated from Schedule
C	Task Completed	C	Completion Deviated from Schedule
X	Task Dropped	X	Task Dropped
--	Task in Progress	--	Task in Progress

TASK	Week
	1	2	3	4	5	6	7	8	9	10
1.1			S	C
1.11				S  C
1.12				S  C
1.2				S  C
1.21
1.22
1.3
1.4				S
TASK	Week
	1	2	3	4	5	6	7	8	9	10
1.011				S  C
1.012				S
1.013
1.014
1.015
1.016
1.017
TASK	Week
	1	2	3	4	5	6	7	8	9	10
2.1				S
2.2				S
2.21
2.3				S
2.4				S
TASK	Week
	1	2	3	4	5	6	7	8	9	10
3.1			S	C
3.2
3.21				S  C
3.3				S
3.31				S
3.311
3.312
3.4				S
3.5
TASK	Week
	1	2	3	4	5	6	7	8	9	10
4.1				S  C
4.2				S
4.3
4.4				S
4.5
4.6
TASK	Week
	1	2	3	4	5	6	7	8	9	10
5.1			S	--
5.11			S	--
5.12				S
5.2			S	--
5.3
5.4			S	C
TASK	Week
	1	2	3	4	5	6	7	8	9	10
6.1			S  C
6.2			S	--
6.3				S
6.4
6.5
6.6				S

Major Activities	Total Hours
Analysis	14
Coding	59
Testing	51
Documentation	22
Configuration Management	5
Administrative	184
Required Documentation	24
Total Hours	359

DNA Home Page
Last Modified 4/27/97 -- C. Lynn Bacher (lynn@cc.gatech.edu)