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. Bulletin Board 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.
• CGI scripts written in Perl are being used to implement the bulletin board feature. A freeware user interaction package of scripts is being used to avoid the overhead of developing this application in the limited 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 in html directory ( /home/html/kjordan/ )

• swse625/ - contains main site and subsection HTML files and subdirectories:
• chat/ - contains files necessary to implement bulletin board functionality
• wwwboard/ - contains files necessary to implement bulletin board functionality
• messages/ - directory containing all bulletin board messages
• wwwboard.html - the main bulletin board file
• faq.html - frequently asked questions file for the bulletin board
• data.txt - text file holding latest message number for use in naming next message file
• passwd.txt - file containing password for administration tool for the bulletin board
• index.html - security file used to prevent direct access to directory files
• index.html - security file used to prevent direct access to directory files
• docs/ - contains the Word 6.0 documents required for class (including individual final papers)
• htm/ - 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
• index.html - main site file contains "Table of Contents", link sets
• intro.html - introduction to Software Risk Management section
• bib.html - bibliography list, linked from index.html
• levity.html - levity section, linked from index.html
• teamdocs.html - MJY Team internal documents Table of Contents, linked from index.html
• *All other sets of links will be part of the main index.html file, unless the list grows large enough to warrant separation.

Set up directory hierarchy for web site files in cgi-bin directory ( /home/html/cgi-bin/kjordan/ )

• wwwboard.pl - Perl file to implement bulletin board functionality
• wwwadmin.pl - Perl file to implement bulletin board administration tool functionality

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 bulletin board function. A freeware set of scripts and files from Matt's Script Archive (WWWBoard) will be tailored for use in the web site, minimizing development time.

The following requirement is included in this task.

1. Bulletin board 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

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