Specification & Design of Real-time Systemspages.erau.edu/~kornecka/realtimelab/BLUE/07 SE545... ·...

Specification & Design of Real-time Systems

FA_07_SE_545: ERAU TEAM BLUE

Software Test Plan Automatic Production Environment

Christopher Griffis

Steve Harvey

Leonardo Matos

Jason McGuire

Sean Pfeifer

Caylyne Shelton

Software Test Plan: Automatic Production Environment Version: 2.0

FA_07_SE_545: ERAU TEAM BLUE Date: 12/11/07

ii

Document Information Category Information

Document ID Software Test Plan: Automatic Production Environment

Document Owner FA_07_SE_545: ERAU TEAM BLUE

Revision History Date Version Description Author

10/30/07 0.1 Initial document template Leonardo Matos

11/05/07 0.2 Initial test cases Leonardo Matos

11/14/07 0.9 Updated test cases

Added new test cases

Leonardo Matos

11/15/07 1.0 Test Plan version 1 release TEAM BLUE

12/11/07 2.0 Test Plan Completed

Test Plan version 2 release

Sean Pfeifer

TEAM BLUE

Document Approvals Role Name Signature Date

Project Sponsor A. Kornecki 12/11/07

Project Review Group FA_07_SE_545 12/11/07

Project Lead Christopher Griffis 12/11/07

Requirements Lead Sean Pfeifer 12/11/07

Hardware Lead Jason McGuire 12/11/07

Design Lead Caylyne Shelton 12/11/07

Programming Lead Steve Harvey 12/11/07

Quality Manager Leonardo Matos 12/11/07

Preface

This Software Test Plan loosely follows the layout suggested by IEEE Std. 829-1998, “IEEE Recommended

Practice for Software Test Documentation.” However, certain liberties have been taken with the compliance of the

format suggested in IEEE Std. 829-1998; the material provided herein is presented to best fit the needs of Software

Test Plan as a project communication tool and reference document.



iii

Table of Contents

TITLE PAGE .................................................................................................................................................................ii

SIGNATURE PAGE......................................................................................................................................................ii

CHANGE HISTORY.....................................................................................................................................................ii

PREFACE ......................................................................................................................................................................ii

1. INTRODUCTION ................................................................................................................................................1

1.1 DOCUMENT PURPOSE .................................................................................................................................1 1.2 STAKEHOLDERS..........................................................................................................................................1 1.3 SCOPE.........................................................................................................................................................1 1.4 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS .......................................................................................1 1.5 REFERENCES...............................................................................................................................................3 1.6 OVERVIEW..................................................................................................................................................3

2. TEST ITEMS........................................................................................................................................................3

3. SOFTWARE RISK ISSUES.................................................................................................................................3

4. FEATURES TO BE TESTED BY TEST CASE ..................................................................................................3

5. FEATURES TO BE TESTED BY CHECKLIST.................................................................................................4

6. APPROACH .........................................................................................................................................................6

7. ITEM PASS/FAIL CRITERIA.............................................................................................................................6

8. ENTRY & EXIT CRITERIA................................................................................................................................6

9. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS ...............................................................6

10. TEST DELIVERABLES..............................................................................................................................6

11. REMAINING TEST TASKS .......................................................................................................................6

12. ENVIRONMENTAL NEEDS......................................................................................................................6

13. STAFFING AND TRAINING NEEDS .......................................................................................................6

14. RESPONSIBILITIES...................................................................................................................................6

15. PLANNING RISKS AND CONTINGENCIES...........................................................................................6

16. APPENDIX ..................................................................................................................................................7

16.1 TEST CASE SCENARIOS...........................................................................................................................7 16.2 REQUIREMENTS TRACEABILITY MATRIX..............................................................................................15



Page 1

Software Test Plan

Automatic Production Environment

1. Introduction

1.1 Document Purpose

This document is to act as a project communication tool and reference document, outlining the intended test plan to

be conducted after implementation.

1.2 Stakeholders

• Sponsor: Dr. Andrew J. Kornecki, Embry-Riddle Aeronautical University

• Members of TEAM BLUE

o Christopher Griffis (Project Lead)

o Steve Harvey (Programming Lead)

o Leo Matos (Quality Lead)

o Jason McGuire (Hardware Lead)

o Sean Pfeifer (Requirements Lead)

o Caylyne Shelton (Design Lead)

1.3 Scope

The diagrams, definitions, test cases, and related material in this document address how the system should behave as

a whole. This document intends to provide a guideline on how testing of the system should occur and the functions

to be tested. Only the main functions of the system as specified by the user needs and the system’s SRS will tested at

this time.

1.4 Definitions, Acronyms, and Abbreviations

Active – a motor is active if the motor is powered and turning

APE – Automatic Production Environment

Auto Control Mode – This is the default software mode in which control of the system occurs automatically and

without user intervention.

BELT1 – see

Figure 1; the conveyer belt driven by Motor1.

BELT2 – see

Figure 1; the conveyer belt driven by Motor2.

Detect – the sensor "detects" an object if the light path is occluded such that the sensor does not detect light,

therefore detecting an occluding object instead.

END PLACE – see

Figure 1; the last logically detectable position the package can be in.

Extended - the pusher moves to "extended" when it pushes the object away from SCAN PLACE towards the

TRANSITION PLACE.



Page 2

Home – a scanner in the home position is the most retracted position as detectable by the position switch such that

the package can enter the scanning area. The pusher in the home position is in the furthest most position from the

transition area as detectable by the position switch and is such that the package can enter the scanning area.

Inactive – when the motor is not moving because it is not being powered, it is considered inactive

M1 – see

Figure 1; Motor1, drives BELT1

M2 – see

Figure 1; Motor2, drives BELT2

M3 – see

Figure 1; Motor3, drives the scanner

M4 – see

Figure 1; Motor4, drives the pusher

No detect - the sensor does not detect an object if the light path is not occluded such that the sensor does detect

light, therefore not detecting an occluding object.

Package – the object used to model the payload that is acted upon in the APE system.

Pusher – the apparatus used to move a package from the SCAN PLACE to the TRANSITION PLACE

S1 – see

Figure 1; line sensor1

S2 – see


S3 – see


S4 – see


SCAN PLACE – see

Figure 1; the next sequentially and logically detectable position a package can have in the system after being moved

by BELT1 away from START PLACE. A package can be scanned only if it is detected in the SCAN PLACE.

Scanner – the apparatus used to model the systems ability to scan a package.

Scanning - the scanner is in its lowered position such that it triggers the position switch to detect such a position.

START PLACE – see

Figure 1; the first sequentially and logically detectable position a package can have in or when being introduced into

the system

TRANSITION PLACE – see

Figure 1; the next sequentially and logically detectable position the package can be in after it has been scanned and

pushed onto BELT2.

User Control Mode – This is the alternate software mode in which automatic control of the system is suspended to



Page 3

allow the user direct control over the system motors.

Figure 1: Automatic Production Environment - Logical Component Layout

1.5 References

[1] Kornecki, Dr. A.J., “Embry-Riddle Real Time Class Resource: Description of the SE545 Project.” SE545

Project System Description 8/10/2007, Version 01 - draft 1. Fall 2007.

[2] Software Engineering Standards Committee of the IEEE Computer Society, “Recommended Practice for

Software Test Documentation,” IEEE Std 829-1998.

[3] TEAM BLUE, “Software Requirement Specification: Automatic Production Environment.” SE545 10/24/07,

Version 2.0.

1.6 Overview

This document loosely follows the layout suggested by IEEE Std. 829-1998, “IEEE Recommended Practice for

Software Test Documentation.” Areas that do not apply or are not addressed are described as such. The

documentation provides a guideline on how to conduct testing of the system and what functions will be tested. Test

cases (scenarios) are provided in the appendix section.

2. Test Items

All main functions of the system will be tested in accordance with the user needs and SRS. Special attention will be

given to the automatic functioning of the system (e.g. prioritization of package movement based on location of the

package), the reporting capabilities of the system to a user at a remote station, and the capability of allowing a user

to toggle between auto control mode and user control mode.

3. Software Risk Issues

Not addressed at this time.

4. Features to be Tested by Test Case

The following table indicates which main features will be tested through the use of test cases (See 16.1) and their



Page 4

level of risk:

Table 1: Features to be tested

Feature Level of Risk (H, M, L)

Auto Mode Control High

User Mode Control Medium

Reporting Capabilities Medium

Timing Requirements High

User Interface Medium

5. Features to be Tested by Checklist

The following table indicates the requirements that are not covered in the test cases and will be tested by

examination of requirements and marked off in the following checklist:

Table 2: Requirements Coverage Checklist (RCC)

Requirement met? Requirements not covered in Test

Cases YES NO

[SYS_CNST1] OK

[SYS_CNST2] OK

[SYS_CNST3] OK

[SYS_CNST4] OK

[SYS_CNST5] OK

[SYS_CNST6] OK

[SYS_CNST7] OK

[SYS_CNST8] OK

[SYS_CNST9] OK

[SYS_CNST10] OK

[SYS_CNST11] OK

[SYS_CNST12] OK

[SYS_STRD1] OK

[SYS_STRD2] OK

[SYS_STRD3] OK

[ASMP4] OK

[SYS_FUNC8.1] OK

[SYS_FUNC8.2] OK

[SYS_FUNC8.3] OK

[SYS_FUNC9] OK

[INT_SYS1] OK

[INT_SYS2] OK

[SYS_CNST11] OK

[SYS_CNST12] OK

[HW_CNST1] OK

[HW_CNST2] OK

[HW_CNST3] OK

[HW_CNST4] OK

[HW_NONF1] OK

[HW_NONF2] OK

[HW_NONF3] OK

[HW_NONF4] OK



Page 5

[HW_NONF5] OK

[HW_NONF6] OK

[HW_NONF7] OK

[HW_NONF8] OK

[HW_NONF9] OK

[HW_NONF10] OK

[HW_FUNC1] OK

[HW_FUNC2] OK

[HW_FUNC3] OK

[HW_FUNC4] OK

[HW_FUNC5] OK

[HW_FUNC6] OK

[HW_FUNC7] OK

[HW_FUNC8] OK

[HW_FUNC9] OK

[HW_FUNC10] OK

[INT_USER1] OK

[INT_USER1.1] OK

[INT_USER2.2] OK

[INT_USER2.2.1] OK

[INT_USER2.2.2] OK

[INT_USER2.2.3] OK

[INT_USER2.2.4] OK

[INT_USER2.2.5] OK

[INT_USER2.2.6] OK

[INT_USER2.3] OK

[INT_USER2.4] OK

[INT_USER2.5] OK

[INT_USER2.6] OK

[INT_USER2.7] OK

[INT_USER2.8] OK

[INT_USER2.9] OK

[INT_USER2.10] OK

[INT_USER3.3] OK

[INT_USER3.4] OK

[INT_USER3.5] OK

[INT_USER3.6] OK

[INT_USER3.7] OK

[INT_USER3.8] OK

[INT_USER3.9] OK

[INT_USER3.10] OK

[INT_COMM1] OK

[INT_COMM2] OK

[SW_FUNC1] OK

[SW_FUNC2] OK

[SW_FUNC2.1] OK

[SW_FUNC3] OK

[SW_FUNC4] OK

[SW_FUNC5] OK

[SW_FUNC6.1] OK

[SW_FUNC6.1.1] OK



Page 6

[SW_FUNC6.2] OK

[SW_FUNC6.2.1] OK

[SW_FUNC6.4] OK

[SW_PERF1] OK

[SW_PERF2] OK

6. Approach

Happy path testing method will be used when testing the APE. In this approach the test cases will only test the

default main features of the system, using known inputs, executing without exception, and producing expected

outputs.

7. Item Pass/Fail Criteria

If a particular item does not behave as expected both the item and the test case are considered to have failed. In that

case the developer shall return to the implementation of the code and fix the problem.

8. Entry & Exit Criteria

Entry criteria are defined as preconditions in each test case. Exit criteria are defined as the successful completion of

the test case.

9. Suspension Criteria and Resumption Requirements


10. Test Deliverables

The completed test cases and items not to be tested checklist will be delivered to the team members via blackboard

once testing is completed.

11. Remaining Test Tasks

Testing will be conducted in one phase. There will be no need to schedule secondary phases to complete testing

unless failures are encountered, in which case, after the developer has fixed the issues found during testing, the

failed test(s) will be conducted in the same manner as before.

12. Environmental Needs


13. Staffing and Training Needs


14. Responsibilities

Testing will be conducted by the quality manager and observed by the programming lead, and any other member

required by the project lead, so that assistant can be provided when needed.

15. Planning Risks and Contingencies

This is considered to be a low risk test; therefore, this is not addressed at this time.



Page 7

16. Appendix

16.1 Test Case Scenarios

OST Developer Leonardo Matos Tester Name Sean Pfeifer

Date November 11, 2007 Date December 11, 2007

Scenario # TC 1 Scenario Objective Package placed at sensor 1, system moves package to sensor

4

Use Cases Covered: 1, 2, 3, and 4

Preconditions: System is turned on and inactive

No packages detected on conveyer belt (sensors 2, 3, and 4 and scanner and pusher in home

positions)

No packages being moved about the conveyer belt

Step Source Action Actual Behavior

1 User Places package at sensor 1 OK

2 System Detects package at sensor 1 OK

3 System Ensures there are no packages at sensors 2, 3, and 4 OK

4 System Turns Belt 1 on OK


6 System Turns Belt 1 off OK

7 System Ensures sensors 3 and 4 do not detect packages OK

8 System Waits 2 seconds OK

9 System Moves scanner to extended (down) position OK


11 System Moves scanner to home (up) position OK


13 System Moves pusher to extended position OK

14 System Detects pusher at extended position OK

15 System Returns pusher to home position OK


17 System Ensures sensor 4 does not detect package OK




21 System System stopped until package is removed from sensor 4 *System will move packages as

far as it can until there's a package

in the way, including scanning

and waiting to push.



Page 8



Scenario # TC 2 Scenario Objective User wishes to observe system status from remote location

Use Cases Covered: 5

Preconditions: System is turned on


1 User Opens status page OK

2 System Reports status of sensors and motors, and system activity to

web server

OK

3 System Displays status page OK

4 System Refreshes status page every 2 seconds Every 1 second

5 User Clicks on appropriate button to refresh earlier then 2 seconds Every 1 second

6 User Closes status page OK

7 System Continues automatic operation OK



Page 9



Scenario # TC 3 Scenario Objective User wishes to activate manual control mode

Use Cases Covered: 6

Preconditions: System is turned on


1 User Opens control webpage OK

2 System Displays control webpage OK

3 User Chooses to activate manual control mode OK

4 System Disables automatic control mode OK

5 System Activates manual control mode OK

6 User Chooses a control toggle from webpage OK

7 System Activates specified motor in specified manner OK

8 User Chooses to resume automatic mode OK

9 System Deactivates manual control mode OK

10 System Activates automatic control mode OK

11 System Resumes automatic operations OK



Page 10



Scenario # TC 4 Scenario Objective Packages placed at sensor 1 and 2, system moves packages

to sensor 4



No packages detected at sensors 3 and 4 and scanner and pusher in home positions



1 User Places packages at sensor 1 and 2 OK




5 System Moves scanner to extend (down) position OK
















18 User Removes package from sensor 4 OK




















38 System System stopped until package is removed from sensor 4 OK



Page 11



Scenario # TC 5 Scenario Objective Packages placed at sensor 1, 2, and 3. System moves

packages to sensor 4



No packages detected at sensor 4 and scanner and pusher in home positions



1 User Places packages at sensors 1, 2, and 3 OK











































Page 12
















Page 13



Scenario # TC 6 Scenario Objective Packages placed at sensor 1, 2, 3, and 4. System moves

packages to sensor 4



Scanner and pusher in home positions



1 User Places package at sensors 1, 2, 3, and 4 OK


3 System System stopped until package is removed from sensor 4 OK









































Page 14



















Page 15

16.2 Requirements Traceability Matrix

Requirements Traceability Matrix

Name BLUE Date 10/8/2007 Version 3

Project APE Course SE545 Instructor Kornecki

Class/Method/ Process/

Entry# Req # Owner Priority

Use Case #

Use Case Design Section

Test Case

Edit/ Change

1

[SYS_USER1]

Griffis webPage TC 1, 4, 5, 6

2

[SYS_USER1.1]


3

[SYS_USER1.2]


4

[SYS_USER1.3]


5

[SYS_USER1.4]


6

[SYS_USER2]


7 [SYS_USER3]

Griffis webPage TC 2

8 [SYS_USER4]


9 [SYS_USER5]


10 [SYS_CNST1]

Pfeifer Section 1.1 RCC

11 [SYS_CNST2]


12 [SYS_CNST3]


13 [SYS_CNST4]


14 [SYS_CNST5]

Pfeifer Deleted RCC

15

[SYS_CNST6]

Pfeifer PROC1, PROC2, PROC3, PROC4,

PROC5

RCC

16

[SYS_CNST7]

Pfeifer PROC1, PROC2, PROC3, PROC4, PROC5, PROC6

RCC

17 [SYS_CNST8]

Pfeifer Deleted RCC

18 [SYS_CNST9]


19 [SYS_CNST10]


20 [SYS_CNST11]


21 [SYS_CNST12]


22 [SYS_STRD1]


23 [SYS_STRD2]


24 [SYS_STRD3]


25

[ASMP1]

Griffis Section 1.1 TC 1, 4, 5, 6

26

[ASMP5]


27

[ASMP2]




Page 16

28

[ASMP3]


29 [ASMP4]

Griffis Section 1.2

30

[SYS_FUNC1]

Pfeifer sensorPoll, autoControl or userControl,

statusManager, webPage,

motorControl

TC 1, 4, 5, 6

31

[SYS_FUNC2]



motorControl

TC 1, 4, 5, 6

32

[SYS_FUNC3]

Pfeifer motorControl TC 1, 4, 5, 6

33

[SYS_FUNC4]

Pfeifer motorControl TC 1, 4, 5, 6

34

[SYS_FUNC5]



motorControl

TC 1, 4, 5, 6

35

[SYS_FUNC6]



motorControl

TC 1, 4, 5, 6

36

[SYS_FUNC7]



motorControl

TC 1, 4, 5, 6

37 [SYS_FUNC8]

Pfeifer statusManager RCC

38 [SYS_FUNC9]

Pfeifer webPage RCC

39

[SYS_FUNC11]



motorControl

TC 1, 4, 5, 6

40 [INT_SYS1]

Griffis webPage RCC

41 [INT_SYS2]

Griffis Section 1.2 RCC

42

[SYS_CNST11]

Pfeifer sensorPoll, autoControl, userControl, motorControl

RCC

42

[SYS_CNST12]

Pfeifer sensorPoll, autoControl, userControl, motorControl

RCC

43 [HW_CNST1]

McGuire

Section 1.2 RCC

44 [HW_CNST2]

McGuire

Deleted deleted

45 [HW_CNST3]

McGuire

Figure 1 RCC

46 [HW_CNST4]

McGuire

Figure 1 RCC



Page 17

47 [HW_NONF1]

McGuire

Section 1.2 RCC

48 [HW_NONF2]

McGuire

Section 1.2 RCC

49 [HW_NONF3]

McGuire

Section 1.2 RCC

50 [HW_NONF4]

McGuire

Figure 1, Section 1.2 RCC

51 [HW_NONF5]

McGuire


52 [HW_NONF6]

McGuire


53 [HW_NONF7]

McGuire


54 [HW_NONF8]

McGuire


55 [HW_NONF9]

McGuire


56 [HW_NONF10]

McGuire


57 [HW_FUNC1]

McGuire


58 [HW_FUNC2]

McGuire


59 [HW_FUNC3]

McGuire


60 [HW_FUNC4]

McGuire


61 [HW_FUNC5]

McGuire


62 [HW_FUNC6]

McGuire


63 [HW_FUNC7]

McGuire

Figure 1, Section 1.2

RCC

64 [HW_FUNC8]

McGuire


RCC

65 [HW_FUNC9]

McGuire


RCC

66 [HW_FUNC10]

McGuire


RCC

67

[INT_USER1]

McGuire

webPage RCC Griffis 10/08/07

68

[INT_USER1.1]

McGuire


69

[INT_USER2]

McGuire

webPage TC 2 Griffis 10/08/07

70

[INT_USER2.1]

McGuire


71 [INT_USER2.1.

1]

McGuire


72

[INT_USER2.2]

McGuire

Deleted RCC Griffis 10/08/07

73 [INT_USER2.2.

1]

McGuire


74 [INT_USER2.2.

2]

McGuire


75 [INT_USER2.2.

3]

McGuire




Page 18

76 [INT_USER2.2.

4]

McGuire


77 [INT_USER2.2.5]

McGuire


78 [INT_USER2.2.6]

McGuire


79

[INT_USER2.3]

McGuire


80

[INT_USER2.4]

McGuire


81

[INT_USER2.5]

McGuire


82

[INT_USER2.6]

McGuire


83

[INT_USER2.7]

McGuire


84

[INT_USER2.8]

McGuire


85

[INT_USER2.9]

McGuire


86 [INT_USER2.10

]

McGuire


87

[INT_USER3]

McGuire


88

[INT_USER3.1]

McGuire


89

[INT_USER3.2]

McGuire


90

[INT_USER3.3]

McGuire


91

[INT_USER3.4]

McGuire


92

[INT_USER3.5]

McGuire


93

[INT_USER3.6]

McGuire


94

[INT_USER3.7]

McGuire


95

[INT_USER3.8]

McGuire


96

[INT_USER3.9]

McGuire


97 [INT_USER3.10

]

McGuire


98 [INT_COMM1]


99 [INT_COMM2]


100 [SW_FUNC1]

Griffis PROC1 RCC



Page 19

101 [SW_FUNC2]

Griffis PROC2 RCC

102 [SW_FUNC2.1]

Griffis PROC2 RCC

103 [SW_FUNC3]

Griffis PROC3 RCC

104 [SW_FUNC4]

Griffis PROC4 RCC

105 [SW_FUNC5]

Griffis PROC5 RCC

106

[SW_FUNC6]

Griffis autoControl, userControl, webPage

TC 3

107 [SW_FUNC6.1]

Griffis autoControl, motorControl

RCC

108 [SW_FUNC6.1.1]

Griffis motorControl RCC

109 [SW_FUNC6.2]

Griffis userControl, motorControl

RCC

110 [SW_FUNC6.2.

1] Griffis motorControl RCC

111 [SW_FUNC6.3]

Griffis autoControl TC 3

112 [SW_FUNC6.4]


113 [SW_PERF1]

Griffis Deleted RCC

114 [SW_PERF2]

Griffis Deleted RCC

Specification & Design of Real-time Systemspages.erau.edu/~kornecka/realtimelab/BLUE/07 SE545... ·...

Documents

Transcript of Specification & Design of Real-time Systemspages.erau.edu/~kornecka/realtimelab/BLUE/07 SE545... ·...