Preliminary Test Plan Report

Software Engineering

The Preliminary Test Plan Report assignment directs student teams to develop a test plan for items on the Prioritized Bug/Enhancement Report. The Preliminary Test Plan Report is fifth of five assignments that prepare students to develop the software they evaluated in the Program Review Report assignment over four two-week scrum cycles.

Students perform the following technical tasks:
1. Identify and accurately describe the key behavior characteristics of an implemented enhancement.
2. Create a set of tests that demonstrates the key behavior characteristics of an implemented enhancement.
3. Identify and accurately describe key behavior characteristics of a fixed bug.
4. Create a set of tests that demonstrates the key behavior characteristics of a fixed bug.
5. Identify the key technical information about enhancements and bugs that the project manger wants when deciding how to test the product.

Mark Hoffman

CSC 225 – Introduction to Software Development PRELIMINARY TEST PLAN REPORT The project manager has decided to continue development of the product begun but not completed by an acquired company. (This is the product your team evaluated in the Product Review Report, developed customer requirements for in the Customer Requirements Report, developed a prioritized bug/enhancement list for in the Prioritized Bug/Enhancement Report, and evaluated project management tools for in the Project Management Tool Report.) The product manager has assigned your development team to develop a test plan for the top six items on the Prioritized Bug/Enhancement List. Specifically, the project manager wants your team’s recommendation on the following:  Enhancement test plan - a detailed description of each enhancement’s intended behavior and a detailed description of tests that demonstrate the behavior.  Bug test plan – a detailed description of the bug behavior (i.e., bug report) and a detailed description of test that demonstrate the bug has been fixed. Your team’s report needs to recommend tests that will verify that enhancements have been correctly implemented and that bugs have been completely fixed. The project manager has asked your team to make a ten-minute presentation summarizing the report. Your team’s report and presentation provides the project manager with critical information to plan how to develop the product. YOUR DELIVERABLES 1. The project manager has asked your team to prepare a three-to-five-page preliminary test plan report. 2. The project manager has asked your team to present significant findings from the preliminary test plan report in a ten-to-fifteen-minute meeting. WHAT YOUR READER WILL DO WITH THE COMMUNICATIONS YOU PROVIDE The manager must develop a plan for completing the project. Therefore, the manager wants your team to answer the following technical questions: 1. What types of tests will be used during the development process? 2. What tests will be used to verify that each enhancement has been correctly implemented? 3. What tests will be used to verify that each bug has been correctly fixed? You must provide answers to these questions in a manner that helps the manager develop a plan. The manager must evaluate your team to determine whether it is capable of completing the project. The manager will use your team’s report to answer the following questions: 1. Can you team accurately describe the behavior of an implemented enhancement and a fixed bug? 2. Can your team accurate describe a test plan that verifies that enhancements have been correctly implemented and bug correctly fixed? 3. Are you and the other team members able to work together effectively? You need to present your information in a way that persuades the manager that your team is technically proficient and effective at collaborating on a complex project. 1

CSC 225 – Introduction to Software Development LEARNING OBJECTIVES FOR THIS ASSIGNMENT While working on this assignment, focus on developing your ability to perform these technical tasks: 1. Identify and accurately describe the key behavior characteristics of an implemented enhancement. 2. Create a set of tests that demonstrates the key behavior characteristics of an implemented enhancement. 3. Identify and accurately describe key behavior characteristics of a fixed bug. 4. Create a set of tests that demonstrates the key behavior characteristics of a fixed bug. 5. Identify the key technical information about enhancements and bugs that the project manger wants when deciding how to test the product. Focus also on developing your ability to perform these communication tasks: 1. Write a report that helps managers make practical decisions efficiently. [Writing] 2. Write a report that builds a manager’s confidence in your team’s technical and communication abilities. [Writing] 3. Write a report that persuades mangers to accept your recommendation. [Writing] 4. Select key information from written report useful to the project manager. [Speaking] 5. Create an informative and useful presentation for the project manager. [Speaking] 6. Demonstrate trustworthy technical expertise and communication skills. [Speaking & Teaming] 7. Deliver your presentation in a professional manner that supports achievement of your goals. [Speaking & Teaming] 8. Collaborate effectively on a software development team. [Teaming] 9. Organize and execute a meeting with the project manager and the software development team. [Teaming] 10. Develop knowledge of individual team member skills and trust among team members. [Teaming] ASSIGNMENT SCHEDULE Monday (9/24): Introduction to software testing. Friday (9/28): Submit your report and make your presentation. Peer review of presentations. GRADING CRITERIA The grading criteria for your team’s written report and presentation are presented in the attached rubrics

2

CSC 225 – Introduction to Software Development Preliminary Test Plan Report

Technical Rubric
TECHNICAL ABILITIES Ability
Identify and accurately describe the key behavior characteristics of an implemented enhancement. Create tests for enhancements .

Details
Identify the key behavior of each implemented enhancement Accurately describe the behavior of each implemented enhancement Tests presented for each key characteristic Each test accurately and completely verifies correctly enhancement implementation

Report Section
Test Plan Section

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Lists key behavior for each implemented enhancement Key behavior not listed or non-key behavior listed

Points

Describes each implemented enhancement accurately Test Plan Section Lists tests for each key behavior Describes test for each that verifies key behavior for each implemented enhancement

Inaccurate or incomplete descriptions Key behavior not listed

Identify and accurately describe key behavior characteristics of a fixed bug. Create tests for fixed bugs.

Identify the key behavior of each fixed bug Accurately describe the behavior of each fixed bug Tests presented for each key characteristic Each test accurately

Test Plan Section

Lists key behavior for each fixed bug

Description is inaccurate or incompletes, or is missing for some implemented enhancement features Key behavior not listed or non-key behavior listed Inaccurate or incomplete descriptions Key behavior not listed

Describes each fixed bug accurately Test Plan Section Lists tests for each key behavior Describes test for each

Description is

3

CSC 225 – Introduction to Software Development
and completely verifies correctly fixed bug that verifies key behavior for each fixed bug inaccurate or incompletes, or is missing for some fixed bug features Omits frequently used test or list infrequently used tests Unpersuasive or inaccurate description or fails to describe relationship between product characteristics and testing methods.

Create a test plan summary

Identify commonlyused tests

Summary Section

Lists the more frequently used test

Analyze product characteristics that require commonlyused tests

Persuasively and accurately describes the relationship between product characteristics and testing methods

4

CSC 225 – Introduction to Software Development Preliminary Test Plan Report

COMMUNICATION RUBRIC
COMMUNICATION ABILITIES Ability
Report helps project manager make practical decisions efficiently

Details
Provides critical information useful to the reader Critical information is easily accessible to the reader

Comm Skill
Writing

EVIDENCE EXAMINED TO EVALUATE YOUR COMMUNICATIONS ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Contains all information useful to the reader and none that is not useful Uses text formatting, organization (e.g., headers), and graphic devices (e.g., lists and tables) that makes information easily accessible to the reader Uses style and tone appropriate for the workplace Useful information is missing or not useful information is included Fails to use formatting, organization, or graphics that makes information accessible to the reader

Points

Report builds project manager’s confidence in team’s technical and communicatio n abilities

Concise and appropriate writing style for project manager Uses precise terms appropriate for the reader

Writing

Uses terms and concepts familiar to the reader, or explains unfamiliar terms or concepts

Uses informal style and tone that is inappropriate for the workplace Misuses terms or concepts or uses terms or concepts unfamiliar to the reader without explanation Key findings are explained inaccurately or imprecisely Fails to used evidence from user training to support key findings

Provides accurate and precise explanations

Key findings are accurately and precisely explained Uses evidence from user training to support key findings

Uses credible evidence to support explanations

5

CSC 225 – Introduction to Software Development

Report persuades project manager to accept your recommendati on

Uses correct and appropriate spelling, grammar, etc. Integrates and interprets findings

Uses correct spelling, grammar, etc. throughout report Writing Provides a summary that prioritizes and integrates individual findings and synthesizes an interpretation Provides a development plan that recommends actions that are supported by key findings Concisely and accurately demonstrates key features of user training Concisely and accurately demonstrates significant features of the user training sample

Several spelling, grammar, etc. errors in report Summary lists without prioritizations or fails to synthesize individual findings

Persuasively describes development plan

Select key information from written report useful to the project manager

Select information the demonstrates key features user training Select information that demonstrates significant features of the user training sample Select information that demonstrates significant factors affecting user experience Select information that recommends plans for program development Key information is presented

Speaking

Development plan that is does not recommend actions or is not supported by key findings Selected features are incomplete or redundant Significant features are missing, insignificant features are included, or irrelevant features

Concisely and accurately demonstrates significant factors affecting user experience

Significant factors are missing, insignificant factors are included, or irrelevant facctors

Create and informative and useful

Speaking

Concise and accurate recommendations for program development Succinctly presents key information

Significant recommendations missing Omits or inaccurately presents key information

6

CSC 225 – Introduction to Software Development
presentation for the project manager

Handouts, visuals, demonstrations, etc. support and complement the presentation

Uses concise, accurate, and useful support materials to support and complement the presentation

Uses verbose, inaccurate, or extraneous support materials that detract from or confuse the presentation Order does not relate to the order of the written report or does not support report understanding Lacks focus or is disorganized; not useful for the project manager

Report order is clear from the presentation

Orders presentation to support the order and understanding of the written report Speaking and Teaming Demonstrates a clear understanding how to organize a presentation useful to the project manager Demonstrates careful planning, avoids firsttime problems, and anticipates potential problems Demonstrates a clearly defined role for each team member Attire for each team member is appropriate for the meeting Demonstrates a clear and accurate understanding of questions, and accurately and respectfully answers

Demonstrate trustworthy technical expertise and communicatio n skills

Focused and organized presentation

Carefully planned and well-executed presentation

Demonstrations lack of preparation and inadequate planning

Each team member’s role is clearly defined

Team member roles are unclear

Each team member is properly attired for the meeting Questions are accurately, authoritatively, and respectfully answered

Team members under dress or over dress for the meeting Demonstrates lack of understanding or the lack of ability to explain answers to questions. Lack of respect for the

7

CSC 225 – Introduction to Software Development
each Each task is independent, clearly defined, and contributes to the overall software development task questioner Tasks are not independent, are vague or unclear, or do not contribute to the software development task Some team assigned tasks that take too little or too much time, and teams are assigned tasks that fall short of or exceed the allotted time Individuals and small groups are unaware of the state of other individual or small group task Results of each task are not clear or are not easy to access No meeting announcement, missing information, or inadequate advanced notice One or more required attendees absent or late Omitted major topics, time not on task, not enough time to answer

Collaborate effectively on a software development team

Breakdown the software development project into small, independent task

Teaming

Effectively and equitable assign tasks to individuals or small groups of developers that can be completed in the allotted time

Each team is assigned tasks that can be accomplished in the allotted time and tasks are evenly assigned

Effectively coordinate task among individuals or small groups

Each individual or small group is aware of the state of tasks assigned to other individuals or small groups Results of each tasks are collected in a uniform, easy to use document Meeting announcement is sent with date, time, and place in advance

Organize and execute a meeting with the project manager and the software development team

Effectively and efficiently coordinate results from each task Required attendees are notified of the meeting arrangement

Teaming

Required attendees are present on time

All required attendees present on time

Meeting is wellorganized and executed

All major topics are presented, no time is wasted, all questions are

8

CSC 225 – Introduction to Software Development
answered in the allotted time Team members are able to clearly state at least two strengths and weaknesses for each team member Team members complete assigned tasks and wait for others to complete assigned tasks all questions Team members cannot identify team member strengths or weaknesses

Develop knowledge of individual team member skills and trust among team members

Identify skills of each team member

Teaming

Develop trust among team members

Team members do not complete assigned tasks or do tasks assigned to others

9



Test Plan

One Week

Writing, Speaking, Teaming

Continuous Quality Assurance

The project manager has decided to continue development of the product begun but not completed by an acquired company. The product manager has assigned your development team to develop a test plan for the top six items on the Prioritized Bug/Enhancement List. The project manager will use your test plan to advise upper management on the status of the project.

4-6

The course (CSC 225 – Introduction to Software Development) is a sophomore-level, experiential introduction to software development that focuses on learning basic software development principles and communications skills by developing an ongoing project. The course project, Tank Wars, continues from the previous semester and is packaged for the next semester.

Over the course there are five set-up assignments
• Program Review Report
• Customer Requirements Report
• Prioritized Bug/Enhancement Report
• Project Management Tools Report
• Preliminary Test Plan Report
that provide background for four two-week Scrum Cycles included in the Scrum Process Management assignment.

Each assignment is a specific Technical Rubric.

The Communication Skills Rubric is the same for all six assignments. Communication skills are assessed cumulatively from the rubric. Communication skills that are to be assessed in this assignment are in red. Communication skills assessed on in earlier assignments and that will continue to be assess in this assignment are in green. Communication skills not assess are in black. All communication skills are assessed for the Scrum Process Management assignment.