Click here for downloadable Word document
Work Breakdown Structure for an Information Technology Development Project
TASK 1: DEVELOP SOFTWARE ARCHITECTURE
1. Determine architectural approach
- Select Markup Language for development
- Select script/programming language for implementation of chat room
2. Develop software architecture
- Standard HTML links and references
a) Link(s) to Software Risk Management Material in the Public Domain
b) Link(s) to Tools used for Software Risk Management
c) Link(s) to articles and publications related to lessons learned in Software Risk Management
d) Link(s) to information on Software Risk Management metrics (Industry norms)
- HTML markup of outside documents (with links incorporated where possible)
a) Introduction to Software Risk Management section
b) Bibliography of articles and publications related to Software Risk Management
- CGI scripts for interaction, possibly from an outside source
a) Chat room for interested users to interact with others
- HTML markup of internal documents, with revisions available
a) Link(s) to original Software Risk Management Articles
3. Assess solution architecture vs. requirements
- Design review by Program Manager
4. Revise architecture and/or renegotiate requirements
5. Document architecture and/or changed requirements
TASK 2: PRODUCE AND DELIVER SOFTWARE ITEMS
1. Define programming, test and verification, QA, and documentation standards and conventions
a) Use standard HTML without browser-specific additions
b) CGI script standards
c) Test and Verification
d) Quality Assurance
2. Formalize internal environment and interface specifications
- Set up directory hierarchy for web site files under public html directory
3. Obtain support tools
a) HTML editor, preferably with Word document conversion
b) CGI script editor/creator, depending on language chosen
4. Refine and formalize the internal design
- Chat room, as research progresses
5. Define testing specifications to demonstrate required performance
6. Define QA specifications
7. Code and check the program
- Standard HTML links and references
- HTML markup of outside documents (with links incorporated where possible)
- CGI scripts for interaction, possibly from an outside source
- HTML markup of internal documents, with revisions available
8. Demonstrate acceptability and deliver software
TASK 3: PREPARE FOR SOFTWARE IINSTALLATION/OPERATIONS
1. Provide documentation describing setup and maintenance requirements and procedures
2. Deliver all software, source files, and data deliverables to operations
