certified software

IT355-Final(1).docx

IT355 Software Testing, Documentation and Quality Assurance

Final

Part 1 – QUIZ

Password: Summer

Terms are attached.

Part 2 – Test Plan Sections

Students must prepare sections of a Test Plan for the “GPA Calculator” application. You have been provided with the executable and the source code to assist in developing your test plan sections.

The document should include:

1. Title Page with title, date, author’s name and honor pledge

2. Table of Contents (with page numbers, automatically generated)

3. Description of the application to be tested (two to three paragraphs indicating what is does, who is the intended audience and how it might be used an an image of the application

4. Test scope (related to a small application)

5. Testing strategy including at least 3 test types

6. An estimate of the level of effort that you think it will take to complete the testing, including any assumptions you have made in making this estimate

7. Qualification requirements for the tester

8. Entrance and exit criteria

Software Requirements

Develop an application to collect data for a student’s midterm grades in a specific semester. The page should include the university’s logo.

The student should be able to enter between one and five courses and their midterm grades. The grades are entered as a number between 0 and 100.

Calculate the overall GPA for the student.

Display the student’s name and the grade expressed as a letter where A = 91-100, B = 81-90, C = 71-80, and otherwise the value is F

Make sure there are comments in the code and the developer’s name and the date at the bottom of each screen.

THIS IS THE WRITING SECTION SO YOU WILL BE GRADED ON YOUR GRAMMAR AND SPELLING. MINIMUM WORD COUNT IS 2,000.

Part 3 Test Case Documentation

Develop test cases for the application listed in Part 2

List the test cases in a table (formatted correctly with an embedded Excel spreadsheet or a Microsoft table) including the following columns:

1. A unique code that includes the type of test (BB or WB followed by a four-digit number).

2. The test scenario (what are you testing)

3. The line of test that you are testing

4. The data that you will enter to test this scenario (should include both a passing and a failing test case)

5. The expected result (if the system was working correctly)

The document should include at least at least 7 test cases, based only on white box testing.

Attachments. Code and screenshots.

2