MJY TEAM SOFTWARE DESIGN DOCUMENT

PROJECT REQUIREMENTS/FUNCTIONAL SPECIFICATION

The following lists the project requirements, which double as the external functional specification:

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. Link(s) to WWW search engines with Software Project/Risk Management keywords
10. Chat room for interested users to interact with others
11. MJY team draft documentation review section

DETAILED SOFTWARE DESIGN

Tools:

• HTML was chosen as the development Markup Language for its wide use and ease in learning. No special editor is being used, just basic text editors and Word 6.0 for conversion of Word format documents. No special browser-specific elements will be used in development since more of an audience can be accommodated with standard HTML.
• The use of CGI scripts is currently under research. The goal is to use a freeware user interaction package of scripts to avoid the overhead of developing this application in the time available.

Tasks:

This task involves creating the actual source directories and files on the WWW server. Original on-site files will be linked to each other as necessary so the basic structure is in place, even while the data is in flux.

Directory Hierarchy:

• Set up directory hierarchy for web site files under public_html directory
• swse625 - contains main site and subsection HTML files and the following subdirectories:
• chat - contains files necessary to implement chat room function
• docs - contains the Word 6.0 documents required for class (including individual final papers)
• html - contains HTML versions of documents in docs directory
• images - contains all picture format files used in the site
• other - contains outside documents and HTML files used
• Files in swse625 directory:
• swse625.html - main site file contains "Table of Contents", link sets
• intro.html - introduction to Software Risk Management section
• bib.html - bibliography list, linked from swse625.html
• levity.html - levity section, linked from swse625.html
• chat.html - lead page into chat room, linked from swse625.html
• teamdocs.html - MJY Team internal documents Table of Contents, linked from swse625.html
• *All other sets of links will be part of the main swse625.html file, unless the list grows large enough to warrant separation.

This task requires WWW search time for ALL MJY Team members in order to read enough on searched sites to determine the site's usefulness to the project and its worthiness for inclusion.

The following requirements are included in this task, with the minimum number required listed first.

1. (5?)Introduction to Software Risk Management section
2. (10) Link(s) to Software Risk Management Material in the Public Domain
3. (5) Link(s) to Tools used for Software Risk Management
4. (10) Link(s) to articles and publications related to lessons learned in Software Risk Management
5. (5?) Link(s) to information on Software Risk Management metrics (Industry norms)
6. (5) Link(s) to WWW search engines with Software Project/Risk Management keywords

This task refers to the actual addition of HTML lines to the source files in order to add a link visibly to the site once it has been deemed worthy of inclusion.

The following requirements are included in this task, with the minimum number required listed first.

1. (5?)Introduction to Software Risk Management section
2. (10) Link(s) to Software Risk Management Material in the Public Domain
3. (5) Link(s) to Tools used for Software Risk Management
4. (10) Link(s) to articles and publications related to lessons learned in Software Risk Management
5. (5?) Link(s) to information on Software Risk Management metrics (Industry norms)
6. (5) Link(s) to WWW search engines with Software Project/Risk Management keywords

This task refers to the acquisition of outside documents, pictures, and a compilation of the MJY Team final paper's bibliographies which will be converted to HTML. These sections may all end up using original MJY Team materials, but it is anticipated that some material will be from outside sources and will require conversion for inclusion in the site.

The following requirements are included in this task, with the expected number of text pages listed first.

1. (2) Introduction to Software Risk Management section
2. (3) Bibliography of articles and publications related to Software Risk Management (from final papers)
3. (2) Levity section containing humorous pictures or articles related to Software Project Management

This task refers to the implementation of the chat room function. It will require research and either use of freeware implementing such a feature or original development time. Initial research indicates that freeware software is available and development will probably be unnecessary. Internal chat room design will be developed after the research phase is completed.

The following requirement is included in this task.

1. Chat room for interested users to interact with others

This task involves storing Word 6.0 and HTML versions of all revisions of internal project documents for download and view, with download accessibility to at least the MJY Team members, and view accessibility to all as a useful exercise in project progression.

The following requirement is included in this task, with the expected number of text pages listed first.

1. (150) MJY team draft documentation review section

• Task: HTML markup of final papers

Each MJY Team member is required to write a 10 page (or so) paper on a software project management topic that will undoubtedly be in Word 6.0 format and will need to be converted to HTML in order to be viewed here. This task is the conversion of these large documents.

The following requirement is included in this task, with the expected number of text pages listed first.

1. (70) Link(s) to original Software Risk Management Articles