Project Design

lvlupnow

test_plan.docx

Home >Computer Science homework help >Project Design

Reliability Test Plan (Pre-Design) for Lean Bean Fitness Application

UMUC

CMIS 495

Dr. Paul Comitz

Group 1

Team Hwang, Sun Mok

Guillermo, John Reivy

Perez, Luis

Tyler, Kelly

Stephens, Henry

Lui, Shan

Table of Contents 1.0 Introduction 2 1.1 Scope 2 1.2 References 2 1.3 Definitions 3 2.0 Environment Description 4 2.1 Hardware & Infrastructure 4 2.2 Software 5 2.3 Resources 6 2.4 Data & Driver Elements 6 3.0 Strategy 7 3.1 Test Plan 7 3.2 Test Design Specification 9 4.0 Cases & Procedures 12 TEST CASE REFERENCE GUIDE 12 4.1 White Box Test Cases & Procedures 12 4.1.1 Profile, settings data entry and motivational queue 12 4.1.2 Diet: Food item entry, options, and suggestions. 14 4.1.3 Weight plan data entry and progress. 15 4.2.2 Exercise plan data entry and progress. 16 4.2 Black Box Test Cases & Procedures 17 4.2.1 Profile, settings data entry and motivational queue. 17 4.2.2 Diet: Food item entry, options, and suggestions. 18 4.2.3 Weight plan data entry and progress. 19 4.2.4 Exercise plan data entry and progress. 20 4.3 Example Test Cases 21 5.0 Traceability Matrix 29 6.0 Testing Schedule and Milestones 30 7.0 Control Procedures 31 Annex A: Details for Procedures and Measurements 31

1.0 Introduction

1.1 Scope

The product to be tested is the Lean Bean Fitness Application, version 1.0. The application is designed to help users reach their fitness goals by tracking nutrition and fitness levels, recommending appropriate dietary and exercise plans, and displaying this information to the user.

The scope of this Pre-Design Reliability Test Plan document is to anticipate validation requirements for the operability of the application. Post-design elements are annotated as “reserved for final STS.” Black box (BB) and white box (WB) test requirements are outlined based upon Project Plan / Software Requirement Specifications. These listings and outlines serve as an addendum to requirements analysis by presenting perspective test criteria for use cases and the expected outputs associated with use case inputs. Planning for test tools and drivers is also addressed.

1.1.1. Test Plan Objectives

· To act as a guide for developers to test the program

· To define the tasks required in testing, and therefore the responsibilities to be distributed to the developers

· To outline and estimate the total amount of work needed for this project, leading to final decisions on the ultimate scope and functions of the project

1.1.2. Features to Be Tested

· Interface Functionality

· First time opening app – takes you to Main Menu

· User Profile Creation

· Name, Age, Height, Weight

· Weight Plan Creation

· Fitness Goals (Lose, gain, or maintain weight)

· Daily Caloric Limit Recommendation

· Healthy Food Item Recommendations

· Food, Exercise, and Manual Caloric Input by User

· Calorie Tracking

· Progress Report Display

· Daily goals / update page

· Motivational Message Display

1.2 References

Ainsworth BE, et al. (2011) compendium of physical activities: A second update of codes and MET values. Medicine & Science in Sports & Exercise. 2011; 43:1575.

Group 1. (2015) UMUC CMIS 495 Section 6381 Project Plan / Software Requirement Specification (SRS).

The Institute of Electrical and Electronics Engineers (IEEE), Inc. (1998) IEEE Std. 1016-1998: IEEE Recommended Practice for Software Design Descriptions.

The Institute of Electrical and Electronics Engineers (IEEE), Inc. (12/22/1998) IEEE Std. 1233-1998: IEEE Guide for Developing System Requirements Specifications.

The Institute of Electrical and Electronics Engineers (IEEE), Inc. (1998) IEEE Std. 830-1998: IEEE Recommended Practice for Software Requirements Specifications.

The Institute of Electrical and Electronics Engineers (IEEE), Inc. (1998) IEEE Std. 829 - 1998: IEEE Standard for Software Test Documentation.

University of Maryland University College (UMUC). (2015) Test Plan. Available from: https://learn.umuc.edu/d2l/lms/news/main.d2l?ou=133204

How to Write a Test Plan Document from Scratch. (2015, June 26). Retrieved September 2, 2015, from http://www.softwaretestinghelp.com/how-to-write-test-plan-document-software-testing-training-day3/

How many calories should you eat? (n.d.). Retrieved September 2, 2015, from http://www.calorieking.com/interactive-tools/how-many-calories-should-you-eat/

Fitness Programs | Top 25 Fitness Motivational Quotes. (n.d.). Retrieved September 2, 2015, from http://www.acefitness.org/acefit/fitness-programs-article/2927/top-25-fitness-motivational-quotes

Pierson, V. (n.d.). How Many Calories Do You Need. Retrieved September 2, 2015, from http://primusweb.com/fitnesspartner/weight/caloriesneeded.htm

Calorie Calculator. (n.d.). Retrieved September 2, 2015, from http://www.active.com/fitness/calculators/calories

BMI & Daily Needs Calculator. (n.d.). Retrieved September 2, 2015, from http://nutritiondata.self.com/tools/calories-burned

1.3 Definitions

Black Box Testing (BB)	A method of software testing that examines the functionality of an application without peering into its internal structures or workings
GUI	Graphical User Interface
IAW	In Accordance With
JDK	JAVA Developer Kit
SDD	Software Design Description
SDK	Software Development Kit
SDLC	Software Development Life Cycle
SRS	Software Requirement Specification
STS	Software Test Specification
Software Pass	Output is as expected
Software Fail	Output is different from what is expected or program crashes
TBD	To be determined
Unit Testing	Process in which parts of an application (units) are individually tested for proper operation
System and Integration Testing	Process in which testers verify that all systems maintain data integrity and cooperate as one unit
White Box Testing (WB)	Modular assessment of the application’s computations

*Note: “Test case” is synonymous with “use case” or otherwise traceable to SRS use-case details.

2.0 Environment Description

FIGURE 1: Ideal Main Menu

The test environment will require developer application (SDK) testing and mobile device interface testing. The above layout is not intended to serve as the final GUI design and is for reliability test reference purposes. Additional GUI elements will be introduced for submenu items.

2.1 Hardware & Infrastructure

2.1.1 Hardware

· Standard Human Interface Devices: Keyboard and Mouse

· Monitor (1024x768 Minimum Resolution) and DVI Cable

· Computer, Desktop, Windows 7 Compatible

· Printer

· Android Mobile Device and Computer Interface Accessory

2.1.2 Infrastructure

Testing will be facilitated via online collaboration from multiple locations worldwide, with adherence to software and hardware requirements of this document, at the location of each developer’s workstation.

2.2 Software

Main Application

1. Name: Lean Bean Fitness Application

Version number: 1.0

Description: Android Mobile Device Application

Support Software

1. Name: Microsoft Windows

Version: Windows 7 or newer

Description: Platform operating system

2. Name: Android Kitkat

Version: 4.4 or newer

Description: Platform operating system

3. Name: Android Studio

SDK Version: 24.3.4

Description: Software development environment

4. Name: Netbeans

JDK Version: 1.8.0_60

Description: Software development environment

5. Name: Eclipse

JDK Version: 1.8.0_60

Description: Software development environment

6. Name: Netbeans, Eclipse

Version number: 1.8.0_60

Description: Software development environments

2.3 Resources

· Support Software User Manuals (Used to verify normal operating conditions)

· Development Software Online References

· Developer team contact information

2.4 Data & Driver Elements

2.4.1. Data Table

	Name	Type	Size	Application Feature Detail	Input	Output
1	Age	Int.	2	Profile	x
2	Body Mass Index	double	4	Weight Plan		x
3	Calories (Days)	double	4	Exercise Plan		x
4	Calories (Month)	double	4	Exercise Plan		x
5	Calories (Week)	double	4	Exercise Plan		x
6	Calories Burned	double	4	Exercise Plan		x
7	Calories To Burn	double	4	Exercise Plan		x
8	Exercise Choice	string	1	Exercise Plan	x
9	Exercise Repetitions	int	4	Exercise Plan	x	x
10	Exercise Options	array	[100,40]	Exercise Plan		x
11	Food Item Choice	string	30	Diet	x
12	Food Item Options	array	[100,40]	Diet {Food Menu TBD}		X
13	Food Suggestion	string	30	Diet		X
14	Gender	Boolean	1	Profile	x
15	Heart Rate	Int.	3	Settings	x
16	Height (inches)	double	4	Profile	x
17	Journal Entry	string	240	Weight, Diet, & Exercise Plans	x
18	Motivator Queue	string	60	Settings		x
19	Queue Option	Boolean	1	Settings	x
20	Password	string	30	Profile	x
21	Plan Start	date	10	Settings	x
22	Plan Stop	date	10	Settings	x
23	Username	string	30	Profile	x
24	Waist Size	double	3	Weight Plan	x
25	Weight (lbs)	double	4	Weight Plan	x
26	Weight Goal (lbs)	double	6	Weight Plan	x
27	Weight Progress	double	2	Weight Plan		x

*Note: This data list serves as a preliminary guide for invalid/valid test input. Final list TBD.

2.4.2 Drivers (To be listed by the Test Manager and Quality Assurance Manager)

#	Driver Module	Source
1		Android Studio Interface
2		Android Studio Interface
3		JDK Interface
4		JDK Interface

3.0 Strategy

3.1 Test Plan

A. Test plan identifier:

LBFA-1.0 (Lean Bean Fitness Application, version 1.0)

B. Introduction:

This test plan introduces use cases associated with I/O listings in Section 2.4.1 of this document.

C. Features to be tested:

1. Menu/Interface Selection (Menus selected from the Main Menu)

2. Data Entry

2.1. User Information (Name, Gender, Age, Weight, and Height)

2.2. Activity level (Sedentary, moderately active, or very active)

2.3. Weight Plan (Weight loss, gain, or maintenance)

2.4. Meal type (breakfast, lunch, dinner, or snack)

2.5. Food and exercises selected from drop-down lists

2.6. Manual entry of calories consumed or burned

3. Display Output

See Section 3.2.d for more details and examples

D. Features not to be tested:

1. Features supporting analysis requirements which are not related to items listed in Section 3.1.C

E. Approach:

1. Black Box Testing

For this stage of the application development, we will use a Black Box testing strategy to lay out the expected results of the input and output of the features before programming. Black Box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings.

2. Overall Approach

Adherence to an approved test matrix using resources listed in Sections 2.2 and 2.3 will ensure adequate testing of the features listed in section 3.1.C. Primary tasking for completion of the planning matrix are detailed in the test cases associated with the test case ID reference listed in the planning matrix.

F. Item pass/fail criteria:

Pass / fail is as defined in Section 1.3 with regard to the expected output condition listed in each test case.

G. Suspension criteria and resumption requirements:

See test case procedures in Section 4 regarding shutdown, restart, and contingencies.

H. Test deliverables:

Annotated test plan matrices and test logs.

I. Testing tasks:

Provided within the test cases and procedural annex A, and also described in Section 3.2.

J. Environmental needs:

Environment is set for an incremental testing model. JDK and Android Studio driver elements simulating the mobile hardware device interface will be needed to support the testing environment.

K. Responsibilities:

See test plan matrix below.

L. Staffing and training needs:

See test plan matrix below.

M. Schedule:

See test plan matrix below.

N. Risks and contingencies:

Safety is of most importance. Ensure all safety precautions are adhered to IAW hardware/software user manual guidelines, ergonomics, and adequate periods of rest. Maintain adequate air temperature in vicinity of machinery. Contingencies are addressed within each test case.

O. Approvals:

The test plan matrix must be approved, assignments made, and drivers listed by the Test Manager and the Quality Assurance Manager prior to test start.

Test Plan Matrix for test plan Lean Bean Fitness Application (LBFA-1.0)

*Note: When testing within the JDK/Android Studio, procedures require test log completion of WB testing before BB testing. Additionally, the application must be loaded and BB testing completed on the mobile device prior to initialing BB testing as complete.

Project Name: Lean Bean Fitness Application Test

Project Manager: Sun Mok Hwang ____________________________________(Signature)

Quality Assurance Manager: Henry Stephens_________________________(Signature)

Profile, Settings, and Queue (PSQ-1T)

Test ID PSQ-1T

Test Case

Procedure ID (Initial upon completion of test case procedure)

Planned Date:

Case ID

Tester

C10

Date Completed:

Successful

PSQ-1T WB

Hwang

4.1.1

PSQ-1T BB

Liu

4.2.1

Test ID D-1T

Test Case

Procedure ID (Initial upon completion of test case procedure)

Planned Date:

Case ID

Tester

C11

C12

C13

C14

C15

C16

C17

C18

C19

C20

Date Completed:

Successful

D-1T WB

Perez

4.1.2

D-1T BB

Lui

4.2.2

Diet, Weight, and Exercise (DWE-1T)

Test ID W-1T

Test Case

Procedure ID (Initial upon completion of test case procedure)

Planned Date:

Case ID

Tester

P10

Date Completed:

Successful

W-1T WB

Stephens

4.1.3

W-1T BB

Tyler

4.2.3

Test ID E-1T

Test Case

Procedure ID (Initial upon completion of test case procedure)

Planned Date:

Case ID

Tester

P11

P12

P13

P14

P15

P16

P17

P18

P19

P20

Date Completed:

Successful

E-1T WB

Guiller-mo

4.1.4

E-1T BB

Tyler

4.2.4

3.2 Test Design Specification

A. Test Design Specification Identifier:

LBFA-1.0-PSQ/DWE

B. Features to Be Tested:

As listed in section 3.1 (e). See also SRS references per test case in sections 4.0 – 5.0 of this document.

C. Approach Refinements:

1. Test techniques:

1.1. In-House/Alpha Testing (Unit Testing)

· Each developer will be given a function/task that they are primarily responsible for. Other developers can provide aid outside of their primary task, as needed.

· Each developer will test the coded function, according to the strategies listed below.

· Any issues in fulfilling the task (such as time constraints, technical problems, etc.) will be reported to other group members for discussion and resolution.

· Communication will primarily be through the “Group 1” Discussion Board on the course site.

Methodology:

· For their primary function, each developer should list all possible user inputs (For example: Pre-defined inputs, manual entry, and data types).

· Check that all input types can be accepted, and that appropriate messages are displayed for incorrect inputs.

· Check that no errors (runtime and logical) exist.

· Developers will record the inputs tested, and the results of each test. These developer notes will be reviewed to make sure that all inputs have been tested, and to take note of issues/errors to be reviewed and corrected.

1.2. Incremental Testing / System and Integration Testing

· Unit testing checks that each unit/function runs correctly, on an individual level. System and Integration Testing is used to make sure that the units function correctly together. For example, is the user’s data consistent from unit to unit? Are the units synchronized so that all units affect each other correctly?

· Once each unit is deemed to be running as expected, System and Integration Testing (testing the system as a whole) can be conducted. The focus would be to check that data is maintained or updated as expected, and that there are no inconsistencies when a user moves from unit to unit.

Methodology:

· All developers will participate in this exercise.

· Create your own profile with your own inputs.

· Explore each function (link), and review and record the outputs for reasonableness.

· Update the profile, and review and record each function’s outputs again, noting any unusual outputs or inconsistencies

· Repeat this process with each function that requires an input. Check that the other functions/interfaces output expected data.

· Again, developer notes will be reviewed to discuss any issues/errors that need corrections.

1.3. Logical Condition Testing

2. Results Analysis Method: Visual Inspection

3. Test Case Selection Criteria: Determined by inter case dependencies.

4. Universal Test Case Attributes:

4.1 Constraints

· Ensure login feature is bypassed or valid username and password entered.

4.2 Environmental Needs:

· Hardware and infrastructure conditions normal.

4.3 Special Procedural Requirements:

· Support software initialized to normal conditions.

4.4 Dependencies:

· WB Testing must be completed before BB testing

D. Test identification:

Case ID	Description
PSQ-1T A/WB	Profile, settings and motivational queue.
D-1T B/WB	Diet: Food item entry, options, and suggestions.
W-1T A/WB	Weight plan data entry and progress.
E-1T B/WB	Exercise plan data entry and progress.
PSQ-1T A/BB	Profile/settings data entry and motivational queue.
D-1T B/BB	Diet: Food item entry, options, and suggestions.
W-1T A/BB	Weight plan data entry and progress.
E-1T B/BB	Exercise plan data entry and progress.

E. Feature pass/fail criteria:

Case ID	Pass	Fail
PSQ -1T A/WB	Reserved for final STS.	Reserved for final STS.
D-1T B /WB	Reserved for final STS.	Reserved for final STS.
W-1T A /WB	Reserved for final STS.	Reserved for final STS.
E-1T B /WB	Reserved for final STS.	Reserved for final STS.
PSQ -1T A / BB	Profile and settings data entry creates a record that remains in the database when the GUI is refreshed. Error cues on invalid entry.	Entry fields inaccessible, entry records corrupted, GUI layout degraded, or system crashes without error cue.
D-1T B / BB	Food item entry creates a record that remains in the database when the GUI is refreshed. Menu array is displayed as selected. Error cues on invalid entry.	Entry fields inaccessible, entry records corrupted, GUI layout degraded, or system crashes without error cue. Array of options, suggestions, and entry records are not displayed as selected.
W-1T A / BB	Weight plan data entry creates a record that remains in the database when the GUI is refreshed. Difference in weight gain/loss is displayed as selected. Error cues on invalid entry.	Entry fields inaccessible, entry records corrupted, GUI layout degraded, or system crashes without error cue. Difference in weight gain/loss not displayed or inaccurate.
E-1T B / BB	Exercise plan data entry creates a record that remains in the database when the GUI is refreshed. Exercise list is displayed as selected. Error cues on invalid entry.	Entry fields inaccessible, entry records corrupted, GUI layout degraded, or system crashes without error cue. Exercise list is not displayed or inaccurate.

4.0 Cases & Procedures

TEST CASE REFERENCE GUIDE
Unique Test Case Identifier	IEEE Std 829-1998 Section 6.2.1
Test Item & Objective(s)	IEEE Std 829-1998 Section 6.2.2
Input Specification	IEEE Std 829-1998 Section 6.2.3
Output Specification	IEEE Std 829-1998 Section 6.2.4
Special Environmental Conditions	IEEE Std 829-1998 Section 6.2.5
Special Procedural Requirements	IEEE Std 829-1998 Section 6.2.6
Dependencies	IEEE Std 829-1998 Section 6.2.7
Procedures	IEEE Std 829-1998 Section 7.2.4.1 – 7.2.4.10

4.1 White Box Test Cases & Procedures

4.1.1 Profile, settings data entry and motivational queue.
Unique Test Case Identifier	PSQ-1T A / WB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Reserved for final STS.
Input Required	Reserved for final STS.
Output Expected	Reserved for final STS.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must pass before starting case 4.2.1.
C1: Procedure Log (Until completion of C10)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
C2: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application/Driver.
C3: Procedure Start (5min)	Set application interface to DSR.
C4: Procedure Execution (15min)	See annex A.
C5: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
C6: Procedure Shutdown (5min)	Close all panes and exit application.
C7: Procedure Restart (5min)	Initialize test case procedure C2 setup.
C8: Procedure Stop (As Required)	Review completed log of results.
C9: Procedure Wrap Up (As required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial C10 on plan matrix if no errors are submitted.
C10: Procedure Contingencies	Call tech support for hardware and support-software errors.

4.1.2 Diet: Food item entry, options, and suggestions.
Unique Test Case Identifier	D-1T B/WB
Requirement Specification Ref.	SRS Section 2.2
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Reserved for final STS.
Input Required	Reserved for final STS.
Output Expected	Reserved for final STS.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must pass before starting case 4.2.2.
C11: Procedure Log (Until completion of C20)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
C12: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application/Driver.
C13: Procedure Start (5min)	Set application interface to DSR.
C14: Procedure Execution (15min)	See annex A.
C15: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
C16: Procedure Shutdown (5min)	Close all panes and exit application.
C17: Procedure Restart(5min)	Initialize test case procedure C12 setup.
C18: Procedure Stop (as required)	Review completed log of results.
C19: Procedure Wrap Up (as required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial C20 on plan matrix if no errors are submitted.
C20: Procedure Contingencies	Call tech support for hardware and support-software errors

4.1.3 Weight plan data entry and progress.
Unique Test Case Identifier	W-1T A/WB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Reserved for final STS.
Input Required	Reserved for final STS.
Output Expected	Reserved for final STS.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must pass before starting case 4.2.3.
P1: Procedure Log (Until completion of P10)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
P2: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application/Driver.
P3: Procedure Start (5min)	Set application interface to DSR.
P4: Procedure Execution (15min)	See annex A.
P5: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
P6: Procedure Shutdown (5min)	Close all panes and exit application.
P7: Procedure Restart (5min)	Initialize test case procedure P2 setup.
P8: Procedure Stop(As Required)	Review completed log of results.
P9: Procedure Wrap Up (As required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial P10 on plan matrix if no errors are submitted.
P10: Procedure Contingencies	Call tech support for hardware and support-software errors

4.2.2 Exercise plan data entry and progress.
Unique Test Case Identifier	E-1T B/WB
Requirement Specification Ref.	SRS Section 2.2
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Reserved for final STS.
Input Required	Reserved for final STS.
Output Expected	Reserved for final STS.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must pass before starting case 4.2.4.
P11: Procedure Log (Until completion of P20)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
P12: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application/Driver.
P13: Procedure Start (5min)	Set application interface to DSR.
P14: Procedure Execution (15min)	See annex A.
P15: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
P16: Procedure Shutdown (5min)	Close all panes and exit application.
P17: Procedure Restart (5min)	Initialize test case procedure P12 setup.
P18: Procedure Stop (as required)	Log results.
P19: Procedure Wrap Up (as required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial P20 on plan matrix if no errors are submitted.
P20: Procedure Contingencies	Call tech support for hardware and support-software errors

4.2 Black Box Test Cases & Procedures

4.2.1 Profile, settings data entry and motivational queue.
Unique Test Case Identifier	PSQ-1T A / BB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Confirm valid operation of items and features as listed in section 3.1.
Input Required	See annex A when completing step C4.
Output Expected	Profile and settings data entry creates a record that remains in the database when the GUI is refreshed. Error cues on invalid entry.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must follow case 4.1.1.
C1: Procedure Log (Until completion of C10)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
C2: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application.
C3: Procedure Start (5min)	Set application interface to DSR.
C4: Procedure Execution (15min)	See annex A.
C5: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
C6: Procedure Shutdown (5min)	Close all panes and exit application.
C7: Procedure Restart (5min)	Initialize test case procedure C2 setup.
C8: Procedure Stop (As Required)	Review completed log of results.
C9: Procedure Wrap Up (As required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial C10 on plan matrix if no errors are submitted.
C10: Procedure Contingencies	Call tech support for hardware and support-software errors.

4.2.2 Diet: Food item entry, options, and suggestions.
Unique Test Case Identifier	D-1T B/BB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Confirm valid operation of items and features as listed in section 3.1.
Input Required	See annex A when completing step P14.
Output Expected	Weight plan data entry creates a record that remains in the database when the GUI is refreshed. Difference in weight gain/loss is displayed as selected. Error cues on invalid entry.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must follow case 4.1.2.
P1: Procedure Log (Until completion of P10)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
P2: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application.
P3: Procedure Start (5min)	Set application interface to DSR.
P4: Procedure Execution (15min)	See annex A.
P5: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
P6: Procedure Shutdown (5min)	Close all panes and exit application.
P7: Procedure Restart (5min)	Initialize test case procedure P2 setup.
P8: Procedure Stop(As Required)	Review completed log of results.
P9: Procedure Wrap Up (As required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial P10 on plan matrix if no errors are submitted.
P10: Procedure Contingencies	Call tech support for hardware and support-software errors

4.2.3 Weight plan data entry and progress.
Unique Test Case Identifier	W-1T B/BB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Confirm valid operation of items and features as listed in section 3.1.
Input Required	See annex A when completing step C14.
Output Expected	Weight plan data entry creates a record that remains in the database when the GUI is refreshed. Difference in weight gain/loss is displayed as selected. Error cues on invalid entry.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must follow case 4.1.3.
C11: Procedure Log (Until completion of C20)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
C12: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application.
C13: Procedure Start (5min)	Set application interface to DSR.
C14: Procedure Execution (15min)	See annex A.
C15: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
C16: Procedure Shutdown (5min)	Close all panes and exit application.
C17: Procedure Restart(5min)	Initialize test case procedure C12 setup.
C18: Procedure Stop (as required)	Review completed log of results.
C19: Procedure Wrap Up (as required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial C20 on plan matrix if no errors are submitted.
C20: Procedure Contingencies	Call tech support for hardware and support-software errors

4.2.4 Exercise plan data entry and progress.
Unique Test Case Identifier	E-1T B/WB
Requirement Specification Ref.	SRS Sections 2.2 and 4.
Design Specification Ref. (DSR)	Reserved for final SDD. See also section 2 figure 1 herein.
Objective(s)	Confirm valid operation of items and features as listed in section 3.1.
Input Required	See annex A when completing step P14.
Output Expected	Exercise plan data entry creates a record that remains in the database when the GUI is refreshed. Exercise list is displayed as selected. Error cues on invalid entry.
Special Environmental Conditions	Hardware and infrastructure conditions normal.
Special Procedural Requirements	Support software initialized to normal conditions.
Inter case Dependencies	Must follow case 4.1.4.
P11: Procedure Log (Until completion of P20)	Note error details in annex A. Initial procedure ID in test plan upon procedure completion.
P12: Procedure Set up (15min)	See section 2.0. Display / Login OS. Launch Application.
P13: Procedure Start (5min)	Set application interface to DSR.
P14: Procedure Execution (15min)	See annex A.
P15: Procedure Measurements*	See annex A. *(Reference only, no timed tasking)
P16: Procedure Shutdown (5min)	Close all panes and exit application.
P17: Procedure Restart (5min)	Initialize test case procedure P12 setup.
P18: Procedure Stop (as required)	Log results.
P19: Procedure Wrap Up (as required)	Submit annex A log to program code developer. Submit plan log to quality assurance manager. Initial P20 on plan matrix if no errors are submitted.
P20: Procedure Contingencies	Call tech support for hardware and support-software errors

4.3 Example Test Cases

4.3.1 General Template

Function to Test	Interface	Input	Expected Output
Interface functionality	Profile	User clicks "Profile" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Main Menu" from "Profile"	User is redirected to the "Main Menu" interface
	Weight Plan	User clicks "Weight Plan" interface from "Main Menu"	User is redirected to the "Weight Plan" interface
		User clicks "Main Menu" from "Weight Plan"	User is redirected to the "Main Menu" interface
	Food	User clicks "Foods" interface from "Main Menu"	User is redirected to the "Foods" interface
		User clicks "Main Menu" from "Food"	User is redirected to the "Main Menu" interface
	Exercises	User clicks "Exercises" interface from "Main Menu"	User is redirected to the "Exercises" interface
		User clicks "Main Menu" from "Exercise"	User is redirected to the "Main Menu" interface
	Progress Report	User clicks "Progress Report" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Main Menu" from "Progress Report"	User is redirected to the "Main Menu" interface
User Profile Creation	Profile	User inputs Name	Display name
		User inputs Gender	Display gender
		User inputs Age	Display age
		User inputs Height	Display height
		User inputs Weight	Display weight
			User's recommended weight/BMI, based on above data
		User selects "Done"	Verifies all Profile information is filled out and saves.
Weight Plan Creation & Daily Caloric Limit Recommendation	Weight Plan	Activity level (sedentary, moderately active, or very active)	Display activity level
		Weight plan (lose, gain, or maintain weight)	Display weight plan
		Rate of loss or gain (e.g. "Lose one pound per week")	Display calorie limit per day, to reach current goal (e.g. "To lose weight you should eat 1400 to 1600 calories per day")
Healthy Food Item Recommendation	Food Menu	Meal selected (e.g. breakfast, lunch, snack, or dinner)	List of healthy items for selected meal (e.g. "Healthy foods for breakfast are: Oatmeal, …")
Food Caloric Input & Calorie Tracking	Food Menu	Food selected from drop-down list	Calories consumed, added toward daily total
		Manual entry of food name, calories	Calories consumed, added toward daily total
Exercise Caloric Input & Calorie Tracking	Exercise Menu	Exercise selected from drop-down list	Calories burned, subtracted from daily total
		Manual entry of exercise name, calories	Calories burned, subtracted from daily total
Progress Report	Progress Report	Carried over from above inputs	Daily net total of calories consumed and burned (e.g. "Today you have consumed 1468 calories total.")
Motivational Message Display	Progress Report	Carried over from above inputs	A motivational message (e.g. "Good job Bob! Keep it up!")

4.3.2 Example Test Case 1

Function to Test	Interface	Input	Expected Output
Interface functionality	Profile	User clicks "Profile" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Profile"	User is redirected to the "Main Menu" interface
	Weight Plan	User clicks "Weight Plan" interface from "Main Menu"	User is redirected to the "Weight Plan" interface
		User clicks "Done" from "Weight Plan"	User is redirected to the "Main Menu" interface
	Food	User clicks "Foods" interface from "Main Menu"	User is redirected to the "Foods" interface
		User clicks "Done" from "Food"	User is redirected to the "Main Menu" interface
	Exercises	User clicks "Exercises" interface from "Main Menu"	User is redirected to the "Exercises" interface
		User clicks "Done" from "Exercise"	User is redirected to the "Main Menu" interface
	Progress Report	User clicks "Progress Report" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Progress Report"	User is redirected to the "Main Menu" interface
User Profile Creation	Profile	Thomas Jefferson	Display and Save "Thomas Jefferson"
		Male	Display and Save "Male"
		27	Display and Save "27"
		5' 7''	Display and Save "5' 7''"
		170 lbs	Display and Save "170 lbs"
			Display "Daily Caloric Needs (Weight * 13) = 170*13 = 2210 needed per day"
		User selects "Done"	Verifies all Profile information is filled out and saves.
Weight Plan Creation & Daily Caloric Limit Recommendation	Weight Plan	Moderately active	Display and Save "Moderately active"
		Lose weight	Display and Save "Lose weight"
		Lose one pound per week	Display "To lose one pound per week you should eat 1500 calories per day."). Calculation TBD.
Healthy Food Item Recommendation	Food Menu	Breakfast	Display and Save "Healthy foods for breakfast are: Oatmeal, Granola, Fruit."
Food Caloric Input & Calorie Tracking	Food Menu	Fried eggs (2)	Display and Save "+150 calories"
		Milk (1 glass, 100 calores)	Display and Save "+100 calories"
Exercise Caloric Input & Calorie Tracking	Exercise Menu	Walking (2 mph, 30 minutes)	Display and Save "-100 calories"
		Running (5 mph, 60 minutes)	Display and Save "-600 calories"
Progress Report	Progress Report	N/A	Display "Today you have netted -450 calories total."
Motivational Message Display	Progress Report	N/A	Display “Strive for progress, not perfection”

4.3.3 Example Test Case 2

Function to Test	Interface	Input	Expected Output
Interface functionality	Profile	User clicks "Profile" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Profile"	User is redirected to the "Main Menu" interface
	Weight Plan	User clicks "Weight Plan" interface from "Main Menu"	User is redirected to the "Weight Plan" interface
		User clicks "Done" from "Weight Plan"	User is redirected to the "Main Menu" interface
	Food	User clicks "Foods" interface from "Main Menu"	User is redirected to the "Foods" interface
		User clicks "Done" from "Food"	User is redirected to the "Main Menu" interface
	Exercises	User clicks "Exercises" interface from "Main Menu"	User is redirected to the "Exercises" interface
		User clicks "Done" from "Exercise"	User is redirected to the "Main Menu" interface
	Progress Report	User clicks "Progress Report" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Progress Report"	User is redirected to the "Main Menu" interface
User Profile Creation	Profile	John Doe	Display and Save "John Doe"
		Male	Display and Save "Male"
		42	Display and Save "42"
		6' 2''	Display and Save "6' 2''"
		185 lbs	Display and Save "185 lbs"
			Display "Daily Caloric Needs (Weight * 13) = 185*13 = 2405 needed per day"
		User selects "Done"	Verifies all Profile information is filled out and saves.
Weight Plan Creation & Daily Caloric Limit Recommendation	Weight Plan	Very active	Display and Save "Very active"
		Lose weight	Display and Save "Lose weight"
		Lose one pound per week	Display "To lose one pound per week you should eat 1700 calories per day.") Calculation TBD.
Healthy Food Item Recommendation	Food Menu	Lunch	Display and Save "Healthy foods for breakfast are: Salad, Vegetable Wrap."
Food Caloric Input & Calorie Tracking	Food Menu	Bagel with cream cheese	Display and Save "+500 calories"
		Pizza (2 slices, pepperoni)	Display and Save "+600 calories"
Exercise Caloric Input & Calorie Tracking	Exercise Menu	Swimming (5 mph, 30 minutes)	Display and Save "-600 calories". Calculations TBD.
		Biking (10 mph, 60 minutes)	Display and Save "-500 calories". Calculations TBD.
Progress Report	Progress Report	N/A	Display "Today you have netted 0 calories total."
Motivational Message Display	Progress Report	N/A	Display “The finish line is just the beginning of a whole new race.”

4.3.4 Example Test Case 3

Function to Test	Interface	Input	Expected Output
Interface functionality	Profile	User clicks "Profile" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Profile"	User is redirected to the "Main Menu" interface
	Weight Plan	User clicks "Weight Plan" interface from "Main Menu"	User is redirected to the "Weight Plan" interface
		User clicks "Done" from "Weight Plan"	User is redirected to the "Main Menu" interface
	Food	User clicks "Foods" interface from "Main Menu"	User is redirected to the "Foods" interface
		User clicks "Done" from "Food"	User is redirected to the "Main Menu" interface
	Exercises	User clicks "Exercises" interface from "Main Menu"	User is redirected to the "Exercises" interface
		User clicks "Done" from "Exercise"	User is redirected to the "Main Menu" interface
	Progress Report	User clicks "Progress Report" interface from "Main Menu"	User is redirected to the "Profile" interface
		User clicks "Done" from "Progress Report"	User is redirected to the "Main Menu" interface
User Profile Creation	Profile	Jane Doe	Display and Save "Jane Doe"
		Female	Display and Save "Female"
		22	Display and Save "22"
		5' 1''	Display and Save "5' 1''"
		115 lbs	Display and Save "115 lbs"
			Display "Daily Caloric Needs (Weight * 13) = 115*13 = 1495 needed per day"
		User selects "Done"	Verifies all Profile information is filled out and saves.
Weight Plan Creation & Daily Caloric Limit Recommendation	Weight Plan	Sedentary	Display and Save "Sedentary"
		Gain weight	Display and Save "Gain weight"
		Gain one pound per week	Display "To gain one pound per week you should eat 2100 calories per day.") Calculation TBD.
Healthy Food Item Recommendation	Food Menu	Dinner	Display and Save "Healthy foods for breakfast are: Grilled Chicken with Vegetables, Steamed fish with rice."
Food Caloric Input & Calorie Tracking	Food Menu	Grilled chicken breast (1)	Display and Save "+300 calories"
		Orange Juice (1 glass, 150 calories)	Display and Save "+150 calories"
Exercise Caloric Input & Calorie Tracking	Exercise Menu	Yard work (60 minutes)	Display and Save "-200 calories". Calculations TBD
		Weight lifting (60 minutes)	Display and Save "-300 calories". Calculations TBD
Progress Report	Progress Report	N/A	Display "Today you have netted -50 calories total."
Motivational Message Display	Progress Report	N/A	Display “The difference between a goal and a dream is a deadline.”

5.0 Traceability Matrix

Cate-gory	Description	SRS Require-ment Ref.	SRS Use Case (functional SR ref.)	SDD Ref. Fig.	Test Case Ref.	Pass/Fail
WB Test	Profile, settings data entry and motivational queue.	SRS Sections 2.2 and 4.	SRS 4.1	Reserved for final SDD.	4.1.1
WB Test	Diet: Food item entry, options, and suggestions.	SRS Sections 2.2 and 4.	SRS 4.4	Reserved for final SDD.	4.1.2
WB Test	Weight plan data entry and progress.	SRS Sections 2.2 and 4.	SRS 4.2, 4.3, & 4.7	Reserved for final SDD.	4.1.3
WB Test	Exercise plan data entry and progress.	SRS Sections 2.2 and 4.	SRS 4.5, 4.6 & 4.7	Reserved for final SDD.	4.1.4
BB Test	Profile, settings data entry and motivational queue.	SRS Sections 2.2 and 4.	SRS 4.1	Reserved for final SDD.	4.2.1
BB Test	Diet: Food item entry, options, and suggestions.	SRS Sections 2.2 and 4.	SRS 4.4	Reserved for final SDD.	4.2.2
BB Test	Weight plan data entry and progress.	SRS Sections 2.2 and 4.	SRS 4.2, 4.3, & 4.7	Reserved for final SDD.	4.2.3
BB Test	Exercise plan data entry and progress.	SRS Sections 2.2 and 4.	SRS 4.5, 4.6 & 4.7	Reserved for final SDD.	4.2.4

6.0 Testing Schedule and Milestones

Time required for testing each function can vary widely, depending on the correctness of the initial programming. Initial tests and documentation should take about one to two hours. Follow-up tests to check fixes or updates should be about the same, adding to the total time required.

Project coding begins on Week 5, giving the team a total of 4 weeks of development time. Initial coding and unit testing can be done in tandem. We can estimate that initial coding and unit testing can take place in the first two weeks, leaving the last two weeks for additional tests, error corrections, and finalization.

Schedule:

· Week 5 – Begin initial coding and unit testing of each individual function

· Week 6 – Finalize coding and unit testing

· Week 7 – Begin System and Integration Testing of the whole system

· Week 8 – Finalize the project with last discussions, packaging, and documentation

Major Deliverables per Developer/Tester:

· Unit Testing Report (Individual Functions)

· Name of the function tested

· List of all possible inputs

· Inputs tested

· Test results

· Issues to be discussed and resolved

· System and Integration Testing Report (Entire Program)

· Unit to be tested

· Inputs tested

· Results of all other units

· Issues to be discussed and resolved

· Repeat for all units

7.0 Control Procedures

7.1 Problem Reporting Procedures

· Report any problems or situations to the entire group - Create a post in that week’s discussion, under the “Group 1” Discussion Board.

· Other members will provide necessary feedback and aid to resolve the issue.

7.2 Change Requests

· Report to the entire group any requests to deviate from the initial project plan - Create a post in that week’s discussion, under the “Group 1” Discussion Board.

· All members will discuss and come to a final decision regarding the change.

Annex A: Details for Procedures and Measurements

4.1.1 Profile, settings data entry and motivational queue. (WB)
C4: Procedure Execution	Reserved for final STS / output computations.
C5: Procedure Measurements	Reserved for final STS / output computations.
Test Data	Table 2.4.1 # {1, 13, 14, 17, 18, 19, 20, 21}
4.1.2 Diet: Food item entry, options, and suggestions. (WB)
P4: Procedure Execution	Reserved for final STS / output computations.
P5: Procedure Measurements	Reserved for final STS / output computations.
Test Data	Table 2.4.1 # {10,11,12}
4.1.3 Weight plan data entry and progress. (WB)
C14: Procedure Execution	Reserved for final STS / output computations.
C15: Procedure Measurements	Reserved for final STS / output computations.
Test Data	Table 2.4.1 # {2, 16, 22,23,24,25}
4.1.4 Exercise plan data entry and progress. (WB)
P14: Procedure Execution	Reserved for final STS / output computations.
P15: Procedure Measurements	Reserved for final STS / output computations.
Test Data	Table 2.4.1 # {3,4,5,6,7,8,9}

4.2.1 Profile, settings data entry and motivational queue. (BB)
C4: Procedure Execution	1. Under Profile: Enter invalid & valid Username 2. Under Profile: Enter invalid & valid Password 3. Under Profile: Enter invalid & valid Age 4. Under Profile: Enter invalid & valid Gender 5. Under Profile: Enter invalid & valid Height 6. Under Settings: Enter invalid & valid Heart Rate 7. Under Settings: Enter invalid & valid Queue Option 8. Under Settings: Enter invalid & valid Plan Start 9. Under Settings: Enter invalid & valid Plan Stop 10. Under Profile: Enter invalid & valid journal entry.
C5: Procedure Measurements	1. “Shady User” & “Authorized User” 2. “bad” & “good” 3. “Dirty” & “30” 4. “Trans” & {“M”,”F”} 5. “Dirty” & “30” 6. “Sexy” & “60” 7. “Yes” & {Y,N} (Cue output expected for Y) 8. { “Today”, “3/14/2015”} & “3/8/2015” 9. { “Today”, “3/8/2015”} & “3/14/2015” 10. Enter 241charactors & 240 characters. *Note: Ensure error cues for reversed dates.
Test Data	Table 2.4.1 # {1, 13, 14, 17, 18, 19, 20, 21}
4.2.2 Diet: Food item entry, options, and suggestions. (BB)
P4: Procedure Execution	1. Enter invalid & valid Food Choice(s) 2. Enter invalid & valid journal entry.
P5: Procedure Measurements	1. Menu TBD & Menu TBD. 2. Food (Option) Menu (Output Expected) 3. Food (Meal) Menu (Output Expected) 4. Enter 241charactors & 240 characters.
Test Data	Table 2.4.1 # {10,11,12}
4.2.3 Weight plan data entry and progress. (BB)
C14: Procedure Execution	1. Enter invalid & valid Waist Size. 2. Enter invalid & valid Weight. 3. Enter invalid & valid Weight Goa.l 4. Enter invalid & valid journal entry.
C15: Procedure Measurements	1. “Fat” & valid “32.5” 2. “Fat” & valid “130” 3. “Skinny” & “120” 4. Weight difference between #2 & 3 (Output Expected) 5. BMI (Output Expected) 4. Enter 241charactors & 240 characters.
Test Data	Table 2.4.1 # {2, 16, 22,23,24,25}
4.2.4 Exercise plan data entry and progress. (BB)
P14: Procedure Execution	1. Enter invalid & valid Exercise Choice 2. Enter invalid & valid Exercise Repetitions
P15: Procedure Measurements	1. “Sex” & All menu choices listed on page 22 2. Calories (Days) (Output Expected) 3. Calories (Month) (Output Expected) 4. Calories (Week) (Output Expected) 5. Calories Burned (Output Expected)
Test Data	Table 2.4.1 # {3,4,5,6,7,8,9}

Note: Additional inter-case dependencies must be listed in further consideration of relationships such as calories-to-burn in the exercise feature based on calories generated as a result of food menu choices, and calories as listed on page 22.

*Valid Exercise Menu

Activity (1-hour duration)	Weight of person and calories burned
	160 pounds (73 kilograms)	200 pounds (91 kilograms)	240 pounds (109 kilograms)
Aerobics, high impact	533	664	796
Aerobics, low impact	365	455	545
Aerobics, water	402	501	600
Backpacking	511	637	763
Basketball game	584	728	872
Bicycling, < 10 mph, leisure	292	364	436
Bowling	219	273	327
Canoeing	256	319	382
Dancing, ballroom	219	273	327
Elliptical trainer, moderate effort	365	455	545
Football, touch or flag	584	728	872
Golfing, carrying clubs	314	391	469
Hiking	438	546	654
Ice skating	511	637	763
Racquetball	511	637	763
Resistance (weight) training	365	455	545
Rollerblading	548	683	818
Rope jumping	861	1,074	1,286
Rowing, stationary	438	546	654
Running, 5 mph	606	755	905
Running, 8 mph	861	1,074	1,286
Skiing, cross-country	496	619	741
Skiing, downhill	314	391	469
Skiing, water	438	546	654
Softball or baseball	365	455	545
Stair treadmill	657	819	981
Swimming laps, light or moderate	423	528	632
Swimming laps, vigorous	715	892	1,068
Tae kwon do	752	937	1,123
Tai chi	219	273	327
Tennis, singles	584	728	872
Volleyball	292	364	436
Walking, 2 mph	204	255	305
Walking, 3.5 mph	314	391	469
Yoga, hatha	183	228	273
Yoga, power	292	364	436

(Ainsworth BE, et al. 2011)