Test plan including test cases, Software Engineering

This assignment aims to provide the opportunity to integrate and develop your analytical and written communication skills, and speci?cally to:develop your skills at developing test plans,

  • develop your at developing test cases, and
  • develop your ability to present a coherent professional report detailing the a test plan.

Outline:

The analysis phase of a system development project has ended and the design phase is beginning. Working on the Real estate multiple listing service system case study develop a test plan including test cases for the system. Assume that the testing phase will take place over a 4 week period. As well as yourself, you will have two other - similarly skilled - testers on your team.

Deliverable:

Your submission will take the form of a report that will include:

  • A test plan, and
  • A set of test cases for one of the major uses cases detailed in the system requirements speci?cation.

Audience

The audience for this submission is primarily technical. As a result the plan you create will need very little explanation, you can assume the reader is UML literate and also understands the nature of software testing. The test cases should contain space and places for the test results to be recorded. The plan should contain the following sections:

Letter of transmittal This letter should be attached to the outside of the report and should explain who has produced the report, the reason for the report, why it was written, for whom it is intended and even the main ?nding/outcome if it is appropriate or signi?cant. This letter should be a maximum of one page.

Executive summary This is a summary of the report. It is to be a maximum of one page. The client will read this section ?rst to determine what parts of the report they need to read thoroughly. Any signi?cant ?ndings or contentious issues should be mentioned to direct them to the relevant sections.

• Table of contents Page This section must accurately identify all major sections and headings with page numbers.

• Introduction This section details main features of the system test plan.This will include an overview of the schedule and milestones.

• Resource requirements This section will list the required hardware, software and staf?ng requirements.

• Features to be tested This section will list the system features to be tested and also the aspects of the system that will not be tested.

• Test plan This section will contain a description of how the tests will be performed, when they will be performed, and who will conduct them.

• Dependancies and risks This section will outline the major dependencies and risks.

• Test Cases This section will contain the test cases for one use case selected by you from the case study. (Normally - of course - test cases will be developed for the entire set of use cases, however, doing that for this assignment would require more effort than is reasonable for 20% value. The plan should assume that all uses cases will be tested.)

• Recommendations and conclusions The summary will contain any conclusions and recommendations, such as which aspects of your system are most critical and why.

Posted Date: 3/1/2013 1:28:06 AM | Location : United States







Related Discussions:- Test plan including test cases, Assignment Help, Ask Question on Test plan including test cases, Get Answer, Expert's Help, Test plan including test cases Discussions

Write discussion on Test plan including test cases
Your posts are moderated
Related Questions
what is halstead software science measures

List the pre-requisites for white-box testing The pre-requisites for white-box testing are same to that of black-box testing with one main difference: - During white-box tes

Text Retrieval Packages: Text retrieval comprises storage and subsequent retrieval of rat girds, essentially textual rather than numerical, tabular or graphical. Although, eac

Explain in detail about the real time systems. Hard and soft real time systems. Real time and high performance. Real-Time control. Real time software design P

Describe design walk throughs A design walkthrough is a quality practice that allows designers to obtain an early validation of design decisions related to the development and t

testing

What are the principle stages of VORD method? Viewpoint identification: Identify the services given to each viewpoint. Viewpoint structuring: Grouping linked viewpoints in t

What are the misunderstanding arise in software development Some of the common misunderstandings regarding software development are given below. 1.  Correcting errors is eas

What is software metric? A Software metric is a easy quantitative measure derivable from any attribute of the software life cycle (E.g.) LOC (Line Of Code) Function poin

Why decision tables are used in many cases instead of boundary value and equivalence partitioning analysis? - A decision table is an efficient way to deal with combinations of