COMPUTER SYSTEMS RESEARCH
Project Estimate for your Program, 3rd quarter 2006-2007 - Feb 2, 2007

Your name: __________________________________, Period: _____
Project title: _______________________________
Language and/or software you are using:
2nd quarter version. Describe the characteristics of your program, its current state, that you have achieved for 2nd quarter.
- Problem definition and your original estimate(s) for 2nd quarter
- Clear statement of the problem(s) or goal(s) that your 2nd quarter version was projected to solve (what goal did you intend to achieve for 2nd quarter).
- Did you meet your project estimate for 2nd quarter? If possible, describe how far off you were with your original estimate(s) for 2nd quarter and any changes you now are making with your programming plans considering your estimates/expectations for 3rd quarter.

3rd quarter projected version

Problem definition and your estimate(s) for 3rd quarter
Clear statement of the problem(s) or goal(s) that you estimate your 3rd quarter version will solve (the goal do you intend to achieve for 3rd quarter).
How does this fit into the larger scale problem or goal you are trying to solve or investigate with your project or system for this year. Estimate what your project can achieve, the state of your project could be, for 4th quarter.
- 4th Quarter estimate
```
    
```
Requirements for 3rd quarter (see the link to Software Construction, item #2) -
List specific requirements you have for 3rd quarter:
You should be able to outline at least 3 or 4 requirement areas for your project 2nd quarter. For example #1 & 2 - input and output, and #10 - how your style of programming and classes you use help in future program maintainability, #11 - how you are justifying success or non-success for your program (or a specific piece of the program) and how you are specifically testing each part of your program.
Think about the quality of your requirements
1. Are the requirements written clearly so that they can be understood by someone outside of your expertise?
2. Are the requirements at a fairly consistent level of detail?
3. Is each requirement testable?
4. Are possible changes to the requirements specified, the likelihood of each change?
```
    
    
    
    

    
    

   
  
```
Architecture of your program for 3rd quarter - software architecture is the high-level part of software design, the frame that holds the more detailed parts of your program's design (see the link to Software Construction from Code Complete, item #3).
Comment on at least 2 or 3 of the above architectural considerations relating to your program and 2nd quarter (for example #1,3,4,10)
```
   
    
    
    

   
```
Outline your organization for the 3rd quarter version of your program's code and project. Determine types of inputs your program will expect, the algorithms and processes your program will work with this quarter, and specific kinds of output(s) you will expect.
- Types of input(s) you'll expect to deal with 3rd quarter (try to test a variety of kinds of inputs):
```
 
```
- Algorithms and processing internal to the program that you expect to learn and program this quarter:
```
 
```
- Types of output you expect to analyze. What do you expect the program to do, how should the program behave based on your input and algorithms?
```
 
```
- Tests - how will you validate the success or failure, how will you analyze your research project during 2nd quarter. What pieces of code, functions, classes, algorithms are you checking and what specific tests are you doing?
```
  
```
What is the focus of the first iteration of your program 3rd quarter?

COMPUTER SYSTEMS RESEARCH Project Estimate for your Program, 3rd quarter 2006-2007 - Feb 2, 2007

COMPUTER SYSTEMS RESEARCH
Project Estimate for your Program, 3rd quarter 2006-2007 - Feb 2, 2007