System Acceptance Test Plan

Exercise #2

Using the 1stPage Program

Instructor: Jim Harris

Purpose

The purpose of this exercise is to show that you know how to use the 1stPage program to enter HTML tags.

Preparation

Double click the desktop icon for the 1stPage program (In the HTML Class folder.).
Open the file:Flash-Drive-Letter:\HTML_Class\Lesson2\Exercise2.htm. (Hint: Click File, Open.)
Perform a File - Save As to your WorkDisk folder as Flash-Drive-Letter:\HTML_Class\Lesson2\Exercise2Done.htm.

Confirmation

Confirm that what is on your screen looks like the pages starting at Page #2 of this handout except that the long lines of text may run off the page to the right.
If they do, click the Word Wrapbutton and notice that the long lines are now entirely visible on the screen.

Execution

You are encouraged to periodically examine the result of your tag editing by clicking the Preview button often during the exercise. Click Preview now and observe that without tags, the browser has ignored all spacing in the file.

Follow the markup instructions beginning on Page #4.

Hints and Caveats

Most tags apply until the end-tag is reached. Thus, if you have a font tag specifying the color blue and forget to put an end-font-tag, the whole rest of the document will be blue. Also, if you want to make three adjacent paragraphs bold, put the bold tag at the beginning of the first paragraph and the end-bold tag at the end of the third paragraph.
In the exercise file, there are many blue <H2> tags. After you make the first one, you can copy and paste tag text for the subsequent one.
Sometimes there are long lines of text that extend beyond the right edge of the page. Since HTML ignores extraneous spacing, you can use the Word Wrap button to break the line into shorter segments that can be viewed on the screen.
When you select text for the List function, you sometimes include an extraneous space at the end of the last item. The List function may then add a blank list item at the end of the list. If this happens, just delete that list item.
Selecting an item and pressing Ctrl+Q will tag the item with the last used tag.
If you encounter a problem or get confused, a successfully tagged sample file is shown beginning on Page #6.

Confirmation

When your finished product is displayed via the Preview button, it should look like Page #8 of this document.

Save the file to your WorkDisk folder as Exercise2Done.htm. Close 1stPage.

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN”“

<HTML>

<HEAD>

<Title>(put title here)</TITLE>

<META NAME = “keywords” CONTENT = “(put keywords here”

<META NAME = “Description” CONTENT = “(put description here)”

</HEAD>

<BODY>

System Acceptance Test Plan

for

CARAT

Scope

Identification

This document is the System Acceptance Test (SAT) Plan for the Congestion Avoidance and Reduction for Automobiles and Trucks (CARAT) Traffic Management System (TMS) of the North Carolina Department of Transportation (NCDOT).

Purpose

The purpose of this document is to specify the plan for performing the CARAT System Acceptance Test which will formally verify the CARAT system.

Scope

This test plan applies to the overall system and relates to system-level tests to verify compliance with project functional requirements. The Hardware Compatibility Test (HCT) is part of the subsystem tests. Some levels of unit testing, subassembly testing, and subsystem testing may be completed and documented separately.

This plan provides:

Description of the test environment

Description of text baseline management

Definition of general test requirements

Definition of levels of tests

Definition of test classes

Definition of qualification methods

Sample of items that will be provided in the System Acceptance Test Procedure document:

Test description

Test definition (procedures)

Requirements verification matrix

NCDOT Relationships to the SAT

NCDOT has the contractual right to observe all aspects of informal and formal CARAT testing in the ATSC ITS lab, the ATSC CARAT lab, and the TOC.

NCDOT has the contractual responsibility to be present during the HCT and SAT in order to officially verify that the CARAT system meets all requirements.

System Overview

CARAT will provide the infrastructure required to accomplish not only the CARAT goals but also the NCDOT long-term goals. This infrastructure will include the systems and services to support the planning and execution of the CARAT mission operations in addition to providing a platform for future expansion and improvement. To accomplish this goal, the following requirements must be satisfied:

The design must specify open and expandable modular architectures and utilize COTS products to the maximum extent.

Standards-based COTS components will reduce the risk and cost of development and test, and allow the insertion of new technology for future applications.

A proven operations engineering process must be established with the participation of the CARAT systems engineering organization.

Document Overview

This document is organized in the following manner:

Section 1 describes the document purpose and scope

Section 2 describes any referenced documents

Section 3 describes the test environment

Section 4 describes test baseline management

Section 5 describes the general test provisions

Section 6 describes data recording, reduction and analysis

Section 7 describes the System Acceptance Test Procedure document.

Section 8 describes the System Acceptance Test Report document.

Section 9 provides a description of baseline management forms

Section 10 provides an acronym list

This document presents the SAT plan. SAT procedures are documented in the System Acceptance Tests Procedures. SAT test results are documented in the System Acceptance Test Report.

This plan complies with the configuration management and quality assurance provisions of the Software Project Management Plan for the CARAT System.

<A HREF=“#TOP”>Return to Top of Page</A>

</BODY>

</HTML>

Markup Instructions for Exercise #2

Action / File Text
Make this the 3-line title at the top of the page. Make each line a BOLD centered paragraph, size 5.

Hint: use

Font tag –1 (on Tags menu) change size to 5
Para tag (on Tags menu) with align=“center”attribute with line breaks.
Bold tag (on Tags menu)
put end-Font tag

/ System AcceptanceTest Plan
for
CARAT
Also add as a one line title inside the TITLE tag.
Add a horizontal rule under the title. Hint: Place cursor before next line. Click HR button on Standard tab.
Make red Heading 1
Hint: use H1 tag plus font tag with color attribute (on Tags menu). put end-font tag / Scope
Make blue Heading 2
Hint: see above. / Identification
Make paragraph
(on Tags menu) / This document is the System Acceptance Test (SAT) Plan for the Congestion Avoidance and Reduction for Automobiles and Trucks (CARAT) Traffic Management System (TMS) of the North Carolina Department of Transportation (NCDOT).
Make blue Heading 2. Hint: copy tag from “Identification” if you like. / Purpose
Make paragraph / The purpose of this document is to specify the plan for performing the CARAT System Acceptance Test which will formally verify the CARAT system.
Make blue Heading 2 / Scope
Make paragraph / This test plan applies to the overall system and relates to system-level tests to verify compliance with project functional requirements. The Hardware Compatibility Test (HCT) is part of the subsystem tests. Some levels of unit testing, subassembly testing, and subsystem testing may be completed and documented separately.
Make bold paragraph. / This plan provides:
Make into ordered list.
Hint: select each item in turn, Click LI on toolbar. Select all items, click ordered list.
Hint: Use the 1-2-3 Button / Description of the test environment
Description of text baseline management
Definition of general test requirements
Definition of levels of tests
Definition of test classes
Definition of qualification methods
Make paragraph / Sample of items that will be provided in the System Acceptance Test Procedure document:
Make into unordered list.
Hint: select each item in turn, Click LI on toolbar. Select all items, click unordered list. / Test description
Test definition (procedures)
Requirements verification matrix
Make blue Heading 2 / NCDOT Relationships to the SAT
Make italic para. / NCDOT has the contractual right to observe all aspects of informal and formal CARAT testing in the ATSC ITS lab, the ATSC CARAT lab, and the TOC.
NCDOT has the contractual responsibility to be present during the HCT and SAT in order to officially verify that the CARAT system meets all requirements.
Make blue Heading 2 /

System Overview

Make para / CARAT will provide the infrastructure required to accomplish not only the CARAT goals but also the NCDOT long-term goals. This infrastructure will include the systems and services to support the planning and execution of the CARAT mission operations in addition to providing a platform for future expansion and improvement. To accomplish this goal, the following requirements must be satisfied:
Make into unordered list. / The design must specify open and expandable modular architectures and utilize COTS products to the maximum extent. Standards-based COTS components will reduce the risk and cost of development and test, and allow the insertion of new technology for future applications.
A proven operations engineering process must be established with the participation of the CARAT systems engineering organization.
Make blue Heading 2 / Document Overview
Make para / This document is organized in the following manner:
Make into unordered list. / Section 1 describes the document purpose and scope
Section 2 describes any referenced documents
Section 3 describes the test environment
Section 4 describes test baseline management
Section 5 describes the general test provisions
Section 6 describes data recording, reduction and analysis
Section 7 describes the System Acceptance Test Procedure document.
Section 8 describes the System Acceptance Test Report document.
Section 9 provides a description of baseline management forms
Section 10 provides an acronym list
Make 2 paras / This document presents the SAT plan. SAT procedures are documented in the System Acceptance Tests Procedures. SAT test results are documented in the System Acceptance Test Report.
This plan complies with the configuration management and quality assurance provisions of the Software Project Management Plan for the CARAT System.

A Successfully Tagged HTML File

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN”“

<HTML>

<HEAD>

<Title>(put title here)</TITLE>

<META NAME = “keywords” CONTENT = “(put keywords here”

<META NAME = “Description” CONTENT = “(put description here)”

</HEAD>

<BODY>

<b>System Acceptance Test Plan<br>

for<br>

CARAT</b</p>

</font>

<HR>

<!— The following line of code is out of sequence

<H1<FONT COLOR=”RED”>Scope</H1</FONT>

-->

<H1>

<FONT COLOR=”RED”>Scope</FONT>

</H1

<H2>

<FONT COLOR=”BLUE”>Identification</FONT>

</H2>

<P>This document is the System Acceptance Test (SAT) Plan for the Congestion Avoidance

and Reduction for Automobiles and Trucks (CARAT) Traffic Management System (TMS)

of the North Carolina Department of Transportation (NCDOT).</P>

<H2<FONT COLOR=“BLUE”>Purpose</FONT</H2>

<P>The purpose of this document is to specify the plan for performing the CARAT System

Acceptance Test which will formally verify the CARAT system.</P>

<H2<FONT COLOR=“BLUE”>Scope</FONT</H2>

<P>This test plan applies to the overall system and relates to system-level tests to

verify compliance with project functional requirements.

The Hardware Compatibility Test (HCT) is part of the subsystem tests.

Some levels of unit testing, subassembly testing, and subsystem testing may be

completed and documented separately.</P>

<B>This plan provides:</B>

<OL>

<LI>Description of the test environment

<LI>Description of text baseline management

<LI>Definition of general test requirements

<LI>Definition of levels of tests

<LI>Definition of test classes

<LI>Definition of qualification methods

</OL>

<P>Sample of items that will be provided in the System Acceptance Test Procedure document:</P>

<UL>

<LI>Test description

<LI>Test definition (procedures)

<LI>Requirements verification matrix

</UL>

<H2<FONT COLOR=“BLUE”>NCDOT Relationships to the SAT</FONT</H2>

<I<P>NCDOT has the contractual right to observe all aspects of informal and

formal CARAT testing in the ATSC ITS lab, the ATSC CARAT lab, and the TOC.

NCDOT has the contractual responsibility to be present during the HCT and SAT

in order to officially verify that the CARAT system meets all requirements.</P</I>

<H2<FONT COLOR=“BLUE”>System Overview</FONT</H2>

<P>CARAT will provide the infrastructure required to accomplish not only the CARAT goals but also the NCDOT long-term goals. This infrastructure will include the systems and services to support the planning and execution of the CARAT mission operations in addition to providing a platform for future expansion and improvement. To accomplish this goal, the following requirements must be satisfied:</P>

<UL>

<LI>The design must specify open and expandable modular architectures and utilize COTS products to the maximum extent.

<LI>Standards-based COTS components will reduce the risk and cost of development and test, and allow the insertion of new technology for future applications.

<LI>A proven operations engineering process must be established with the participation of the CARAT systems engineering organization.

</UL>

<H2<FONT COLOR=“BLUE”>Document Overview</FONT</H2>

<P>This document is organized in the following manner:</P>

<UL>

<LI>Section 1 describes the document purpose and scope

<LI>Section 2 describes any referenced documents

<LI>Section 3 describes the test environment

<LI>Section 4 describes test baseline management

<LI>Section 5 describes the general test provisions

<LI>Section 6 describes data recording, reduction and analysis

<LI>Section 7 describes the System Acceptance Test Procedure document.

<LI>Section 8 describes the System Acceptance Test Report document.

<LI>Section 9 provides a description of baseline management forms

<LI>Section 10 provides an acronym list

</UL>

<P>This document presents the SAT plan. SAT procedures are documented in the

System Acceptance Tests Procedures. SAT test results are documented in the System

Acceptance Test Report.</P>

<P>This plan complies with the configuration management and quality assurance

provisions of the Software Project Management Plan for the CARAT System.</P>

<A HREF=“#TOP”>Return to Top of Page</A>

</BODY>

</HTML>

System Acceptance Test Plan

for

CARAT

Scope

Identification

Purpose

The purpose of this document is to specify the plan for performing the CARAT System Acceptance Test which will formally verify the CARAT system.

Scope

This plan provides:

Description of the test environment
Description of text baseline management
Definition of general test requirements
Definition of levels of tests
Definition of test classes
Definition of qualification methods

Sample of items that will be provided in the System Acceptance Test Procedure document:

Test description
Test definition (procedures)
Requirements verification matrix

NCDOT Relationships to the SAT

NCDOT has the contractual right to observe all aspects of informal and formal CARAT testing in the ATSC ITS lab, the ATSC CARAT lab, and the TOC. NCDOT has the contractual responsibility to be present during the HCT and SAT in order to officially verify that the CARAT system meets all requirements.

System Overview

The design must specify open and expandable modular architectures and utilize COTS products to the maximum extent.
Standards-based COTS components will reduce the risk and cost of development and test, and allow the insertion of new technology for future applications.
A proven operations engineering process must be established with the participation of the CARAT systems engineering organization.

Document Overview

This document is organized in the following manner:

Section 1 describes the document purpose and scope
Section 2 describes any referenced documents
Section 3 describes the test environment
Section 4 describes test baseline management
Section 5 describes the general test provisions
Section 6 describes data recording, reduction and analysis
Section 7 describes the System Acceptance Test Procedure document.
Section 8 describes the System Acceptance Test Report document.
Section 9 provides a description of baseline management forms
Section 10 provides an acronym list

This document presents the SAT plan. SAT procedures are documented in the System Acceptance Tests Procedures. SAT test results are documented in the System Acceptance Test Report.

This plan complies with the configuration management and quality assurance provisions of the Software Project Management Plan for the CARAT System.

Return to Top of Page

09/11/2013 8:09 AM1 of 10