Web Application Development Advice & How To
Active Server Pages Development Advice & How To

Shining Star Services LLC
Shining Star Services
ASP.net Articles
HTML Tutorial
Auto-select an Element from a Menu or Scrolling List & Save Keystrokes!
ASP Driven DHTML Slider Menus REVISITED One Year Later! Part II
ASP Driven DHTML Slider Menus
ASP Driven HTML Outlines
Reusing Code with ASP Include Files and Subroutines
Hacker Query Check
.htr IIS Security Issue
Databases, Cookies
Functions to Open a Database Connection and Record Set
Setting Up and Using OraSession to Manage Your Oracle Database Objects
Storing Non-Durable Data for Cookie-less Sessions
Smart Popups
Javascript: Validate Numeric Fields
Javascript Confirm Form Submission
Javascript Dynamic Text Area Counter
Javascript: Check All and Uncheck All Check Boxes
Javascript Field Validations -- Client Side Scripting
Tree Select Demo
Adobe Extension Manager
Scandisk & Defrag Pointers
Standards & Style
Setting Up Your Own ASP Development Templates
Creating a Project Template for Estimations of Time, Tasks, and Resources
To Host or Not To Host
ASP Naming Conventions
HTML Naming Conventions & Visual Interdev HTML Generation
Working with and in spite of the Visual Interdev Design Mode
Commenting Your ASP Source Code
Reader Letters

Articles Home

Shining Star Services

Creating a Project Template for Estimations of Time, Tasks, and Resources
By Nannette Thacker - 09/02/1999

  1. Plan Phase
    1. Estimations of Work for Development
      1. Include time for all applicable tasks shown below
      2. Multiply result by 1.5 to allow for interruptions and unexpected issues
    1. Meetings
      1. Project/Timeline planning meeting
      2. Review of Functional Requirements Specifications
      3. Development Team Meeting to Assign Tasks
      4. Weekly status review meetings with analyst or business unit
      5. Weekly status review meetings with development team
        1. Review printed project schedule
        2. Update percents completed
        3. Add new tasks not accounted for
        4. Modify dates on existing tasks as necessary
  1. Analyze Phase
    1. Research and read all existing documentation on project
    2. Ask any needed questions in advance as possible
    3. Review existing source code as needed
  1. Design Phase
    1. Documentation
      1. Project work plan for development
        1. Alter the template to create a project work plan for development
        2. Update the project work plan bi-weekly
        3. Weekly print updated project work plan
        4. Weekly distribute printed work plans to team members and lead
      1. Detailed Design Specification (DDS)
        1. DDS extends throughout duration of entire project
        2. Update DDS throughout project as logic and code changes are made
        3. DDS Outline for Project Lead
          1. Create detailed design specification from template
          2. Create an overview paragraph
          3. Include developers and analysts assigned to project
          4. Include work flow as applicable
          5. Include files, directories altered or created
          6. Include session/application objects created
          7. Include database tables altered or created
          8. Include risks and assumptions applicable to development
          9. Refer reader to Functional Requirements Specification for overall project risks and assumptions as needed
  1. Build Phase
    1. System Admin Duties
      1. Set up development/test environment
      2. Create project branch in code control
      3. Assign code control rights to project developers
    1. Coding
      1. Coding alterations or additions
      2. Break each item in Functional Requirements Specification into tasks
      3. Comment all source code with date, initials, project name, description of change
      4. Don't delete old code, comment out. Can be deleted at a later date - months later.
      5. Primary developer tests changes as they are made
  1. Test Phase
    1. Unit Testing
      1. Primary developer writes test plans (step-by-step instructions) for each change or enhancement
      2. Beta tester is assigned Overall Unit Testing utilizing test plans
      3. Beta tester documents any needed changes after testing
      4. Test results are sent back to primary developer
      5. Primary developer makes any needed code changes
      6. Unit testing steps are looped through until all pass
    1. Code Review
      1. For new development or major changes to pages
      2. Typically takes 2 hours of preparation by Moderator
      3. Developer prints out source code pages to be reviewed
      4. Developer gives master printout to Moderator
      5. Moderator prepares list of evaluators (2-3)
      6. Moderator makes copies of pages and distributes to evaluators
      7. Moderator provides evaluation templates to evaluators
      8. Evaluators spend approximately 1-2 hours in advance reviewing code
      9. Moderator arranges meeting
      10. Meeting takes 3-4 hours
      11. Developer explains project and overview
      12. Evaluators walk through code, looking for code or logic errors
      13. Errors are identified and documented
      14. Solutions are NOT discussed at the meeting
      15. Moderator keeps people on track
      16. Developer does not moderate or evaluate
      17. This is NOT to critique the developers style or lack thereof
      18. If there is another way to do it, but the way done works, move on!
      19. At end of 3rd hour, meeting dismissed
      20. 4th hour is used for those who want to stay and discuss solutions
      21. Moderator compiles list of needed changes, distributes to developer
      22. Developer is responsible for incorporating changes as needed
    1. Dog and Pony Show
      1. For enhancements and features to existing code
      2. Call together group of 2 or more individuals
      3. Walk through the work flow from a user perspective
      4. Demonstrate how product works and changes made
      5. Bugs always pop up when you're showing off to someone
    1. System Testing
      1. QA Support throughout system testing
      2. Alterations of code throughout system testing
      3. Unit testing as needed for new changes
      4. Update to documents as needed
      5. Check out and check in of code as needed


ShiningStar.net | ShiningStarSingles.com | Christian911.com