Name of the book:Required: Wiegers, Karl, Software Requirements (3rd Edition), Microsoft Press 2013
Assignment: write about 2 pages (1.5 line spacing and 11 or 12 font size) of summary of chapter in YOUR words, so that it contains:
(part 1) important concepts of the chapter
(part 2) experience/application/opinions of the chapter.
The summary for ch 17,ch 18,ch 19,ch 27,ch 28 in your 'OWN WORDS', the summary will be 2 pages per chapter.

Solution PreviewSolution Preview

These solutions may offer step-by-step problem-solving explanations or good writing examples that include modern styles of formatting and construction of bibliographies out of text citations and references. Students may use these solutions for personal skill-building and practice. Unethical use is strictly forbidden.

C H A P T E R 1 7 - Validating the requirements
“When you can’t let it go, validate it!”. Requirement form the basis for any software and is responsible for either successful or failed product development. As per one of the study its been revealed that it took an average of 30 minutes to fix a defect discovered during the requirements phase. In contrast, 5 to 17 hours were needed to correct a defect identified during system testing. Misinterpreted requirement have potentially to damage deliverables quality, cost money and time to fix in later stages. I we start validating this requirement early we would potentially save development and its associated maintenance cost.
Validation and verification
Verification determines whether the product of some development activity meets its
requirements (doing the thing right). Validation measures whether a product satisfies customer requirements (doing the right thing). Validating requirements allows teams to build a correct solution that meets the Customer requirements.
Reviewing requirements
“Two minds are better than one minds”. When anyone reviewing the work product of someone else, Peer review is taking place. Different technique are:
1. Informal reviews are useful for refining others about the product and collecting informal feedback. These are: First, A peer desk check, in which you ask one team member to look over your work product. Second, A pass around, in which few team members are invited to examine a deliverable. Third, A walkthrough, during which the author describes a deliverable and solicits comments.
2. The inspection processes Inspection is a well-defined multistage process. It involves a small team of participants who carefully examine a work product for defects and improvement opportunities. Inspections serve as a gate keepers through which project deliverables must pass before they are baselined.
Inspection roles
All participants in an inspection, including the author, look for defects and improvement opportunities.
Author The author created or maintains the work product being inspected. The author of a requirements document is usually the business analyst who was involved with requirement gathering phase and interacted with customer and then created the requirements.
Moderator Moderator is responsible to plans the inspection with the author, coordinates the activities, and facilitates the inspection meeting
Recorder The recorder uses standard templates to document the concerns raised and the defects found during the meeting.
Entry criteria
To start with validation there are some specific set of pre- requisites:
1. The document conforms to the standard template.
2. Line numbers or other unique identifiers Page numbers book marks are printed on the
document to facilitate referring to specific locations. All open issues are marked as TBD.
3. The moderator didn’t find more than three major defects in a ten-minute examination of a representative sample of the document.
Inspection stages
An inspection is a multistep process which includes Initial work product, planning, Preparation, Inspection meeting, rework, follow-up and baselined work product.
Exit criteria: Your inspection process should define the exit criteria that must be satisfied
before the moderator declares the full inspection process (not just the meeting) complete.
Here are some possible exit criteria for requirements inspections: First, Any changes suggested in requirements and related work products were made correctly to avoid issue cycle i.e correcting one and introducing newer. Second, All open issues have been resolved, or each open issue resolution process, target date, and owner have been documented.
Defect checklist: Documenting the error, suspect and take it as a checklist before reviewing would serve the purpose. Studies shows that Instead of giving entire checklist to all reviewers, giving checklist to subject matter expert would result in more fruitful error detection rate.
Requirements review tips: Following tips forms the basis: Plan the examination, Start early, Allocate sufficient time, Provide context, Set review scope...

By purchasing this solution you'll be able to access the following files:
Solution.pdf, Solution1.pdf, Solution2.pdf, Solution3.pdf and Solution4.pdf.

50% discount

$55.00 $27.50
for this solution

or FREE if you
register a new account!

PayPal, G Pay, ApplePay, Amazon Pay, and all major credit cards accepted.

Find A Tutor

View available Java Programming Tutors

Get College Homework Help.

Are you sure you don't want to upload any files?

Fast tutor response requires as much info as possible.

Upload a file
Continue without uploading

We couldn't find that subject.
Please select the best match from the list below.

We'll send you an email right away. If it's not in your inbox, check your spam folder.

  • 1
  • 2
  • 3
Live Chats