QATR.3.0
12 April 1997

Test of Build 3 (Completed April 12, 1997)

Testing Methodology: Each new 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).

Regression testing was accomplished on at least 10% of links delivered during build 2. Included in this number were re-evaluation of links that were found to have defects during build 2 testing (for example, those links where index document date did not match with the date on the document's cover page or header. Regression testing would involve connectivity and readability (no download test)of the primary link and one sublink.

Test Results: The existing web page meets minimum SRS Build 3 requirements. All defects noted during Build 2 testing have been correction with the exception of standardizing the document version conventions. Additional deficiencies involving version conventions 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 can be corrected and re-evaluated during final build testing.

Two errors were discovered on other web sites used by the home page during Build 2 testing. Both errors have been corrected; however, another error was discovered during this testing cycle. The error is occurring at the other web site and is not caused by our implementation; therefore it does not require corrective action on the part of the MJY development team. One Build 2 "error" remains open, and requires a decision by the program manager. The error does not impact site functionality nor cause a failure to meet minimum standards.

Test Results Summary Table

ITEM Connect Readable Ops/Dnld Sublink Sublink Sublink Risk
Connect Readable Ops/Dnld Related
Site Cover Page (C1)
Y
Y
Y/NA
Y
Y
Y/NA
Y
*** 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 (D 2)
1. Team Member Roles
Y
Y
Y
N/A
N/A
N/A
N/A
2. Requirements Process Plan
2a. RQMP 1.1
Y
Y
Y
2b. RQMP 1.0
Y
Y
Y
Y
Y
Y
N/A
3. SW Reqmnts Spec
3a. SRS 3.0
Y
Y
Y/Y
N/A
N/A
N/A
N/A
3b. SRS 2.0
Y
Y
Y/Y
N/A
N/A
N/A
N/A
3c. SRS 1.0
Y
Y
Y/Y
Y
Y
Y
N/A
3d. SRS 0.0
Y
Y
Y/Y
Y
Y
Y
4. Risk/Risk Mgmt Plan
4a. RSKP 2.0
Y
Y
Y/NA
N/A
N/A
N/A
NA/
4b. RSKP 1.3
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4c. RSKP 1.2
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4d. RSKP 1.1
Y
Y
Y/NA
N/A
N/A
N/A
N/A
4e. RSKP 1.0
Y
Y
Y/NA
Y
Y
Y/NA
N/A
4f. RSKP 0.0
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. WBS 31.MAR.97
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5b. WBS 25 FEB 97
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5c. WBS 24 FEB 97
Y
Y
Y/NA
N/A
N/A
N/A
N/A
5d. WBS 22 FEB 97 (D3)
Y
Y
NA
N/A
N/A
N/A
N/A
5e. WBS 19 FEB 97
5f. WBS 14 FEB 97
5G. WBS 11 FEB 97
Y
Y
NA
N/A
N/A
N/A
N/A
6. SW Proj Mgmt Plan
6a. SPMP 1.0
Y
Y
Y/NA
Y
Y
Y/NA
NA
6b. SPMP 0.0
Y
Y
Y/NA
Y
Y
Y/NA
NA
7. S/W Design Doc
7a. SWD 2.0 (D4)
Y
Y
Y/NA
E7, 8
7b. SWD 1.0 (D5)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
7c. SWD 0.0 (D6)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
8. QA / Test Plan
8a. QATR 2.0
Y
Y
Y/NA
N/A
N/A
N/A
N/A
8b. QATR 1.0
Y
Y
Y/NA
N/A
N/A
N/A
N/A
8c. QATP 1.0
Y
Y
Y/NA
N/A
N/A
N/A
N/A
9. Config Mgmt Plan
9a. CMP 1.1
Y
Y
Y/NA
Y
Y
Y/NA
N/A
9b. CMP 1.0
Y
Y
Y/NA
Y
Y
Y/NA
N/A
10. Status Report
10a. RSR 31.MAR.97
Y
Y
Y/NA
N/A
N/A
N/A
10b. PSR 24 MAR 97
Y
Y
Y/NA
Y/NA
Y/NA
Y/NA
10c. RSR 3 MAR 97
Y
Y
Y/NA
N/A
N/A
N/A
*** Risk Mgmt Bulletin Board (4.6.2.) (R9)
Y
Y
Y/NA
Y
Y
Y/NA
N
*** Bibliography (4.8.2.) - Final Build
Y
Y
*** Levity Section (4.7.2.)
Y
Y
Y/NA
Y
Y
NA
*** 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 Readable Ops/Dnld Sublink Sublink Sublink Risk
Connect Readable Ops/Dnld Related
1. HMS Software (R)
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 (R)
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 ( R )
Y
Y
Y/NA
Y
Y
Y/AN
N
5. SW Engr Institute(R)
Y
Y
Y/Y
Y
Y
Y/NA
Y
5a. Featured Publications of SEI (R)
Y
Y
Y/NA
Y
Y
Y/E10
5b. SEI Risk Program(R)
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 ( R11 )
Y
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 (R)
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.)
1. Tools and Models Index
Y
Y
Y/NA
Y
Y
Y/NA
2. Automated Cost Estimating Integrated Tools (ACEIT)
Y
Y
Y/NA
Y
Y
Y/Y
3. Project Management Products
Y
Y
Y/NA
Y
Y
Y/NA
3a. Welcom Software Technology
Y
Y
Y/NA
Y
Y
Y/NA
4. Seven Management Tools
Y
Y
Y/NA
Y
Y
Y/NA
4a. Risk from the Perspective of Competitive Advantage
Y
Y
Y/NA
Y
Y
Y/NA
5. Cost Track
Y
Y
Y/NA
Y
Y
Y/NA
5a. OnTrack Engineering, LTD
Y
Y
Y/NA
Y
Y
Y/NA
*** Other SWSE 625 Team Sites
1. ACDFGHIK (R)
Y
Y
Y/NA
Y
Y
Y/NA
N/A
2. BE (R)
Y
Y
Y/NA
N/A
N/A
N/A
N/A
3. LMNOPQR (R)
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.)
Y
Y
Y/NA
Y
Y
Y/NA
N/A

Prefix Legend

(E) -- error;

(D) -- defect;

(C) -- comment;

(R) - regression test item

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

Notes

1. (C) This documents correct functionality of website's initial page - not explicitly specified in SRS.

2. (D) Three differing version numbering conventions are inconsistently reflected on the posted documents. If date stamps are used as version numbers for reports, then QA's two test reports (QATR1.0 and QATR 2.0) should have a date versus a numeric version number. Additionally, the team member roles and WBS documents should not be using date stamp version numbering, as they are not "reports" - they need to be changed to version numbers. When using numeric versions, two schemes are in use: 1.0, 2.0, 3.0, etc or 1.0, 1.1, 1.2, etc. We need to come to closure on this during final build phase. This correction will also clear all cover page related defects (4-7) noted in build 2.

3. (D) Web page index specifies version 0.3, but title page indicates version 0.1 (header specifies version 0.3).

4. (D) Web page index specifies version 2.0, but header specifies version 4.Apr.97

5. (D) Web page index specifies version 1.0, but header specifies version 11.Mar.97

6. (D) Web page index specifies version 0.0, but header specifies version 25.Feb.97

7. (E) Functional specification 5 (tools) links to the "software project management sites" section instead of "tools"section

8. (E) Functional specification (search engines) links to the "software project management sites" section instead of "search engines" section

9. (R) Error E12 from build 2 has been corrected.

10. (E) Error E13 from build 2 has been corrected. However, during test could not download 3 documents that were specified as available for download. Error message from site indicates that it is a connectivity problem on the SEI site, and is can't be fixed by our development team. We will re-evaluate this problem at final build testing.

11. (R) "Error" E14 from build 2 has not been corrected (connects to a subsection of the ASU web site instead of to the web site's index page.)

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