COMPUTER SYSTEMS RESEARCH
Project Estimate for your Program, 2nd quarter 2006-2007

  1. Your name: __________________________________, Period: _____

  2. Project title: _______________________________

  3. Language and/or software you are using:
    
    
    
  4. 1st quarter version. Describe the characteristics of your program, its current state, that you achieved for 1st quarter.

    2nd Quarter Version

  1. Problem definition and your estimate(s) for 2nd quarter
    - Clear statement of the problem(s) or goal(s) that you estimate your 2nd quarter version will solve (what goal do you intend to achieve for 2nd quarter).
    
    
    
    
    
    
    
    
    
  2. How does this fit into the larger scale, or longer term, problem or goal you are trying to solve or investigate with your project or system. Estimate what your project can achieve, the state of your project could be, for 3rd and 4th quarters. (This may be difficult to estimate, but it's a good exercise to try)
  3. Requirements for 2nd quarter (see the link to Software Construction, item #2) -

    List specific requirements you have for 2nd 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? Are the requirements clear enough to be turned over to an independent group and still be understood - as if another group would be doing the programming of your requirements?
    2. Are the requirements at a fairly consistent level of detail? should any be specified in more detail? in less detail?
    3. Is each requirement testable?
    4. Are possible changes to the requirements specified, the likelihood of each change?
        

  4. Architecture of your program for 2nd 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)

       

  5. Outline your organization for the 2nd 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.

  6. What do you think your focus will be for the first iteration of your program 2nd quarter (your first iteration report for 2nd quarter)?