Test plan including test cases, Software Engineering

Assignment Help:

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.


Related Discussions:- Test plan including test cases

Software project planning necessitate what activities, Q. Software project ...

Q. Software project planning necessitate what activities? What are the difficulties encountered in measuring the Software Costs? Ans. Software project planning necessitate th

Define software testing, Q. Define software testing. Explain various level ...

Q. Define software testing. Explain various level of testing? Ans: Software testing- It is a process used to help identify the completeness, correctness and quality of develo

State the technique pilot used in software engineering, State the technique...

State the technique Pilot used in software engineering With this approach, new system is introduced into one part of the company (for example into one warehouse of a supermark

Define evolutionary prototyping, Evolutionary prototyping: Evolutionary Pr...

Evolutionary prototyping: Evolutionary Prototyping (also called as breadboard prototyping) is quite dissimilar from Throwaway Prototyping. The main goal when using Evolutionary Pr

ALTIUM DESIGN 09 + PROGRAMMING, I NEED HELP WITH DESIGN A CIRCUIT ON ALTIUM...

I NEED HELP WITH DESIGN A CIRCUIT ON ALTIUM 09 AND PROGRAMMING WITH DESCRIPTION FOR ALL THE STEPS

Nonfunctional requirements of clue-less system, Nonfunctional Requirements ...

Nonfunctional Requirements Performance Requirements PE-1: The Clue-Less system shall accommodate 6 users during peak usage, with an estimated average session duration of 15 m

What are the main approaches in debugging, What are the common approaches i...

What are the common approaches in debugging? Brute force method: The memory dumps and run-time tracks are checked and program with write statements is loaded to get clues to er

Why waterfall model is advantageous than adhoc methods, Q. Why Waterfall mo...

Q. Why Waterfall model is advantageous than Adhoc Methods? Why Waterfall model is advantageous than Adhoc Methods AC16 Software Engineering Ad-hoc Process Models -Process

Concepts of the object-oriented paradigm, To develop software of lasting qu...

To develop software of lasting quality you have to lay down a solid architectural foundation that is resilient to change. Modelling is at the heart of the development of good quali

Write Your Message!

Captcha
Free Assignment Quote

Assured A++ Grade

Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!

All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd