WBS.19.FEB.97
19 February 1997

SWSE 625 MJY Team Project Work Breakdown Structure

  1. ANALYZE SOFTWARE REQUIREMENTS
    1. Understand functional and software requirements
      1. Introduction to Software Risk Management section
      2. Link(s) to original Software Risk Management Articles
      3. Link(s) to Software Risk Management Material in the Public Domain
      4. Bibliography of articles and publications related to Software Risk Management
      5. Link(s) to Tools used for Software Risk Management
      6. Link(s) to articles and publications related to lessons learned in Software Risk Management
      7. Link(s) to information on Software Risk Management metrics (Industry norms)
      8. Levity section containing humorous pictures or articles related to Software Project Management
      9. Chat room for interested users to interact with others
      10. MJY team draft documentation review section
    2. Identify missing, vague, ambiguous, and conflicting requirements
      1. Introduction to Software Risk Management section
      2. Link(s) to Tools used for Software Risk Management
      3. Link(s) to articles and publications related to lessons learned in Software Risk Management
      4. Link(s) to information on Software Risk Management metrics (Industry norms)
      5. Chat room for interested users to interact with others
    3. Clarify stated requirements
      1. Introduction to Software Risk Management section
      2. Link(s) to Software Risk Management Tools, their descriptions and/or reviews
      3. Link(s) to articles and publications related to lessons learned in Software Risk Management
      4. Link(s) to information on Software Risk Management metrics (Industry norms)
      5. Chat room for interested users to interact with others
    4. Verify that stated requirements fulfill requester's goals
    5. Assess technology for supplying required software
      1. Determine space available for web site requirements
      2. Determine if permissions required to support chat room requirement are available
    6. Propose alternate requirements or capability
    7. Document revised requirements
      1. Produce draft Software Requirements Specification (SRS)
      2. Submit draft SRS for team review
      3. Incorporate team comments into draft SRS
      4. Release Initial SRS to customer/team
      5. Update SRS for Preliminary Design Review (PDR)
      6. Update SRS for Critical Design Review (PDR)
      7. Produce final SRS for Functional Acceptance Testing (FAT)

  1. DEVELOP SOFTWARE ARCHITECTURE
    1. Determine architectural approach
      1. Select Markup Language for development - 1/20/97 - HTML
      2. Select script/programming language for implementation of chat room
    2. Develop software architecture
      1. Standard HTML links and references (Allow 0.25 hours for the addition of each set of links reported to the Developer for inclusion in the site, total number of such tasks TBD)
        1. Link(s) to Software Risk Management Material in the Public Domain
        2. Link(s) to Tools used for Software Risk Management
        3. Link(s) to articles and publications related to lessons learned in Software Risk Management
        4. Link(s) to information on Software Risk Management metrics (Industry norms)
      2. HTML markup of outside documents (with links incorporated where possible) (Allow 0.25 hours per *full page* of text/Word documents to be converted to HTML, total number of pages TBD)
        1. Introduction to Software Risk Management section
        2. Bibliography of articles and publications related to Software Risk Management
        3. Levity section containing humorous pictures or articles related to Software Project Management
      3. CGI scripts for interaction, possibly from an outside source
        1. Chat room for interested users to interact with others
      4. HTML markup of internal documents, with revisions available (Allow 0.25 hours per *full page* of text/Word documents to be converted to HTML, total number of pages TBD)
        1. Link(s) to original Software Risk Management Articles - 10 pages x 7 papers x 0.25 hours = 17.5 hours (4/21/97 - 4/28/97) WILL REQUIRE ASSISTANCE!!
        2. MJY team draft documentation review section
    3. Assess solution architecture vs. requirements
      1. Design review by Program Manager
    4. Revise architecture and/or re-negotiate requirements
    5. Document architecture and/or changed requirements

  1. PRODUCE AND DELIVER SOFTWARE ITEMS
    1. Define programming, test and verification, QA, and documentation standards and conventions
      1. Programming
        1. Use standard HTML without browser-specific additions
        2. CGI script standards -- TBD
      2. Test and Verification
        1. *RAY'S PART HERE*
      3. Quality Assurance
        1. Determine location of backup site and/or files
        2. *RAY'S PART HERE*
    2. Formalize internal environment and interface specifications
      1. Set up directory hierarchy for web site files under public_html directory
        1. swse625 - contains main site and subsection HTML files
          1. chat - contains files necessary to implement chat room function
          2. docs - contains the Word 6.0 documents required for class (including individual final papers)
          3. html - contains HTML versions of documents in docs directory
          4. images - contains all picture format files used in the site
          5. other - contains outside documents and HTML files used
    3. Obtain support tools
      1. Research required for:
        1. HTML editor, preferably with Word 6.0 document conversion
        2. CGI script editor/creator, depending on language chosen
    4. Refine and formalize the internal design
      1. Chat room, as research progresses
    5. Define testing specifications to demonstrate required performance
      1. *RAY'S PART HERE*
    6. Define QA specifications
      1. *RAY'S PART HERE*
    7. Code and check the program
      1. Standard HTML links and references
      2. HTML markup of outside documents (with links incorporated where possible)
      3. CGI scripts for interaction, possibly from an outside source
      4. HTML markup of internal documents, with revisions available
    8. Demonstrate acceptability and deliver software

  1. PREPARE FOR SOFTWARE SUSTAINING AND OPERATIONS
    1. Provide documentation describing setup and maintenance requirements and procedures
    2. Deliver all software, source files and data deliverables to operations

  1. PERFORM PROJECT MANAGEMENT FUNCTIONS
    1. Define project goals and objectives
    2. Scope and plan the project
      1. Produce project Work Breakdown Structure (WBS) elements
      2. Determine appropriate project milestones
      3. Establish schedule requirements for tasks
      4. Assign resources to tasks
    3. Administrate the implementation
      1. Collect actual values for task cost and schedule (weekly)
    4. Evaluate performance and product
      1. Conduct weekly project reviews
        1. Evaluate actual versus projected schedule
        2. Evaluate actual versus projected cost
    5. Terminate the project
Software Project Management / Comments? / Back / Last Updated: April 7, 1997