Project 2
Software Requirements Specification
Review and Testcases

Your company ABC has been commissioned by a customer to create a software product for online classroom environment. The business analyst has created software requirements documented that your manager has asked you to review (HYOULearn-SRS.docx). You are also to write up all the test cases for the requirements as indicated by the template (those in bold in table section 3.1). You have been given the validation template that your team has used successfully in the past. You must use this template (project2-validation-template.doc) to document your review and validation test cases.

Validation Document
Fill in the background information for the validation in section 1 of the template

SRS Review
Review the document looking for ambiguous, redundant, duplicate, untestable, inaccurate, incomplete, etc. requirements. Document your findings in the validation document using the provided template (section 2).

Validation Testcases
For EACH requirement use case, define all the tests needed to fully test the requirement (section 3.1). Then document the actual test cases (steps and other information) in the validation document using the provided format in the template for ONLY requirements in bold from table in section 3.1. The validation test for login has been done as example in section 3.2. You are to follow that example for the rest of the validation tests for the bold requirements.

Review IEEE-Standard-1028-2008 Software Reviews and Audits document and make sure to related book chapters and power points charts for week 2, 5, and 6.

Your deliverable must be the validation document submitted as Microsoft Word file named YourName-Project2-Validation.doc or YourName-Project2-validation.docx.

Grading Rubric:

Name    Description    Weight
Grammar/spelling
The document meets graduate level criteria with no issues with grammar, punctuation, spelling, etc.

APA style guide is used for providing any citations and references.
Project was submitted to TurnItIn    10%

Clarity    The document identifies the correct category for the requirements that have an issue and explains why it is an issue
The validation tests for requirements are well defined, correctly testing the requirement    20%

Quality    For each issue identified during review, it is explained clearly and completely

Each validation test has all the required information, such as the requirement it is testing, pre-conditions, steps/flow for the test, and post-conditions, etc.    30%
Completeness    The document identifies all or close to all issues with the requirements
Validation tests cover all the requirements and all aspects of the requirement
40%
Total        100