QATR.2.0
31 March 1997

Test of Build 2 (Completed March 29, 1997)

Testing Methodology: Each web page link has been subjected to the following tests: connectivity (can it connect to the indicated URL?); readability (can I read the page once connection is established?); and operation /download capability (once linked, can I manipulate the functionality at the "linked" site. If it has document download capability, can I download a readable copy of the document?). Download is marked "N/A" if the site has no download capability (other than saving display as an HTML file). Test findings are shown in notes at the bottom of the page.

Test Results: The existing web page meets minimum SRS Build 2 requirements. Several deficiencies were noted during test (descriptions contained in the notes section of the Test Results Summary Table); however, these do not impact web functionality nor cause a failure to meet minimum SRS requirements. These deficiencies (inconsistencies between document dates shown on the web site versus on the document's cover page) can be corrected and re-evaluated during Build 3 The two errors were found on other web sites during secondary (sublink) testing, and therefore do not require corrective action on the part of the MJY development team.

Test Results Summary Table

ITEMConnect ReadableOps/Dnld SublinkSublink SublinkRisk
ConnectReadable Ops/DnldRelated
*** Intro Risk Mgmt (4.6.4.)
Y
Y
Y
Y
Y
Y
Y
1. Managing Stds V3.5 Risk Mgmt
Y
Y
Y/NA
Y
Y
Y/NA
Y
*** Team Project Documents (4.5.2) (C 1,2)
1. Team Member Roles
Y
Y
Y
N/A
N/A
N/A
N/A
2. Requirements Process Plan
2a. Ver1
Y
Y
Y
2b. Ver 2 (C 3)
Y
Y
Y
Y
Y
Y
N/A
3. SW Reqmnts Spec
3a. Ver 0 (C 3)
Y
Y
Y/Y
N/A
N/A
N/A
N/A
3b. Ver 1 (D 4)
Y
Y
Y/Y
N/A
N/A
N/A
N/A
3c. Ver 2 (D 5)
Y
Y
Y/Y
Y
Y
Y
N/A
4. Risk/Risk Mgmt Plan
4a. Ver 0 (D 6)
Y
Y
Y/NA
N/A
N/A
N/A
NA/
4b. Ver 1
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4c. Ver 2 (D 7)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4d. Ver 3
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4e. Ver 4 (D 7, 8)
Y
Y
Y/NA
Y
Y
Y/NA
N/A
4f. Ver 5 (D 7)
Y
Y
Y/NA
Y
Y
Y/NA
N/A
5. Work Breakdown Structure
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5a. Develop Ver 0
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5b. Developer Ver 1
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5c. Test Ver 0
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5d. Ver 0.1 (C 9)
Y
Y
NA
N/A
N/A
N/A
N/A
5e. Ver 1.0 (C 9)
Y
Y
NA
N/A
N/A
N/A
N/A
6. SW Proj Mgmt Plan
6a. Ver 0.1 (D 10)
Y
Y
Y/NA
Y
Y
Y/NA
NA
6b. Ver 1.0 (D 10, C 11)
Y
Y
Y/NA
Y
Y
Y/NA
NA
7. S/W Design Doc
7a. Ver 1.0 (D 6)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
7b. Ver 1.1 (D 6)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
8. QA / Test Plan
8a. Ver0.1 (D 6)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
8b. Build 1 Test Results (D 6)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
9. Config Mgmt Plan
9a. Ver 0.1
Y
Y
Y/NA
Y
Y
Y/NA
N/A
9b. Ver 0.2
Y
Y
Y/NA
Y
Y
Y/NA
N/A
*** Risk Mgmt Bulletin Board (4.6.2.)
Y
Y
Y/NA
E12
N
*** Bibliography (4.8.2.) - Final Build
Y
Y
*** Levity Section (4.7.2.) - Build 3
Y
Y
*** Lessons Learned Section (4.8.3.) -- Final Build
Y
Y
*** Final (Term) Papers (4.8.1.) -- Final Build
Y
Y
Jordan
May
McNeese
Miller
Mirantes
Mundell
Young
*** Related Site (4.6.3.)Connect ReadableOps/Dnld SublinkSublink SublinkRisk
ConnectReadable Ops/DwdRelated
1. HMS Software
Y
Y
Y/NA
Y
Y
Y/NA
N
1a. S/W White Papers
Y
Y
Y/NA
Y
Y
Y/NA
N
1b. PM Resources
Y
Y
Y/NA
Y
Y
Y/NA
N
1c. SW PM Articles
Y
Y
Y/NA
Y
Y
Y/NA
N
2. Key practices of CMM
Y
Y
Y/NA
Y
Y
Y/NA
N
2a. Lvl 2-Proj Tracking
Y
Y
Y/NA
Y
Y
Y/NA
N
3. ProjectNet
Y
Y
Y/NA
Y
Y
Y/NA
Y
4. Practical SW Measurement
Y
Y
Y/NA
Y
Y
Y/AN
N
5. SW Engr Institute
Y
Y
Y/Y
Y
Y
Y/NA
Y
5a. Featured Publications of SEI
E-13
5b. SEI Risk Program
Y
Y
Y/NA
Y
Y
Y/NA
Y
5c. SEI SW Engr Risk Repository
Y
Y
Y/Y
Y
Y
Y/Y
Y
5d. SEI Conf on Risk Mgmt
Y
Y
Y/NA
Y
Y
Y/NA
Y
5e. SEI Continuous Risk Guidebook
Y
Y
Y/NA
Y
Y
Y/NA
Y
6. SW Risk Mgmt @ ASU
C 14
Y
Y/NA
Y
Y
Y/NA
Y
7. Config Mgmt Yellow Pages
Y
Y
Y/NA
Y
Y
Y/NA
N
8. NASA IV&V Facility Home Page
Y
Y
Y/NA
Y
Y
Y/NA
N
8a. IV&V Related Links
Y
Y
Y/NA
Y
Y
Y/NA
N
9. Risk and Competitive Advantage
Y
Y
Y/NA
Y
Y
Y/NA
Y
9a. Seven Mgmt (New) Tools
Y
Y
Y/NA
Y
Y
Y/NA
N
9b. Risk Bibliography
Y
Y
Y
9c. Proj Risk Bibliography
Y
Y
Y/NA
Y
Y
Y/Y
Y
10. Quantitative SW Mgmt - Risk Mgmt Strategies
Y
Y
Y/NA
Y
Y
Y/NA
Y
11.Quantitative Risk & Policy Analysis Guide
Y
Y
Y/NA
Y
Y
Y/NA
Y
*** Tools (4.7.3.) Build 3
1. Tools and Models Index
2. Automated Cost Estimating Integrated Tools (ACEIT)
3.
4.
5.
*** Other SWSE 625 Team Sites
1. ACDFGHIK
Y
Y
Y/NA
Y
Y
Y/NA
N/A
2. BE (C 15)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
3. LMNOPQR
Y
Y
Y/NA
Y
Y
Y/NA
N/A
4. STUVWXZ
Y
Y
Y/NA
Y
Y
Y/NA
N/A
*** WEB Searches on Risk Mgmt (4.6.5.) (C 16)
Y
Y
Y/NA
Y
Y
Y/NA
N/A

Prefix Legend

(E) -- error;

(D) -- defect;

(C) -- comment;

*** -- Major Requirement Descriptor (Note: the related WBS numeric identifier comes in parentheses immediately following the descriptor)

Notes

1. (C) Although build #1 discusses prototyping the team draft documents section, build #2 in the software project management plan (rev 1.0, 24 Feb 97) doesn't stipulate the build/delivery of the draft documents section. This is not the case with the 10 related site links (items 4.5.1. and 4.6.3.) We need to update the SW management plan accordingly.

2. (C) We need to agree on a standard version numbering convention. From the looks, I would recommend that the initial draft version be Ver 0.1; the first draft (with all team comments incorporated) could be Ver 1.0, with subsequent versions Ver2.0, Ver 3.0, etc.

3. (C) We need to agree on a standard cover sheet for each of our plans. We are at a point where we are cross-referencing between plans. Without a cover sheet, there is no way to tell if we're linked into the most current version of the appropriate management plan. I would suggest that CM Ver 0.2 cover sheet be adopted as the standard.

4. (D) Web page document date shows 2/12/97; actual cover sheet date shows 2/03/97

5. (D) Web page document date shows 2/17/97; actual cover sheet date shows 2/03/97

6. (D) No cover sheet

7. (D)Web page document date shows 2/25/97; actual cover sheet date shows 2/10/97

8. (D)Web page incomplete - shows "transfer interrupted" comment at bottom of page

9. (C)Why carry an HTML selection if we can't (cheaply!) convert MS Project to a browser-readable format?

10. (D) Software Requirements Specification dates throughout both documents show current SRS dated February 3, 1997. However, the SRS links to the 10 Feb 97 SRS version - need to change both document texts accordingly.

11. (C) Internal links to appendix A work correctly; however, they link to nothing (since we can't get MS Project to display correctly using a Web browser). You might want to put in a statement similar to what was used in the latest WBS section (i.e., can't get it to display) so a user doesn't think he/she has a malfunctioning browser.

12. (E) Matt Wright's home page (http//alpha.pr1.k12.co.us/~mattw/home.html) link incorrect - getting "site not found" error.

13. (E) Featured Publications of SEI link - error during connection; appears to be an SEI site problem. If problem persists, remove link.

14. (E) Software Risk Mgmt @ ASU - you've linked into the intro section instead of the "home page", which misses some additional functionality. No big deal, but might want to consider linking to the title page, with an additional Sublink to the intro section (similar to the SEI implementation).

15. (C) No sublinks in this home page to test (other than the GMU home page, which operates normally.)

16. (C) Need PM clarification if "precanned" search routines on popular search engines meet the requirement for "a list of suggested keywords." Otherwise, all links are operating normally.

Software Project Management / Comments? / Back / Last Updated: April 13, 1997