Software Quality Engineering Software Requirements vs Requirements

Software Requirement Engineering vs Software Quality Engineering Software Requirements vs Requirements Software requirements are not similar to requirements in other domains Software is not tangible till first demoable version. Pg. 111 The Unschooled Mind

Software Requirement Engineering vs Software Quality Engineering Software Requirements vs Requirements Software Requirement changes after Demoable version Requirements in other domains usually does not change once started i-e Construction Industry Pg. 111 The Unschooled Mind

Software Quality Engineering Attributes of Software Requirements

Software Quality Engineering Correct

Software Requirement Engineering vs Software Quality Engineering Correct Requirement should capture client expectation There should be no room for ambiguity. Requirement should be in single line. Should not exceed 30-50 words in length. Pg. 111 The Unschooled Mind

Software Requirement Engineering vs Software Quality Engineering Correct Avoid using open ended and subjective terms. Use of etc or assumed are key avoidable Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Correctness

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Correctness Avoid falling in the trap of using subjective terms. Pg. 111 The Unschooled Mind

Software Quality Engineering Coherent

Software Requirement Engineering vs Software Quality Engineering Coherent Requirements should not conflict with any other requirement in the system. Vocabulary should be consistent for all the stakeholders. Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Coherent

Software Requirement Engineering vs Software Quality Engineering Example of Coherent Customer support should be IT ISO-ITIL 3.0 compliant The network support should be ISO-90 – ITIL 3.0 compliant Question: Which one is correct or different? Pg. 111 The Unschooled Mind

Software Requirement Engineering vs Software Quality Engineering Example of Coherent Answer: Only one standard should be used. Pg. 111 The Unschooled Mind

Software Quality Engineering Complete

Software Requirement Engineering vs Software Quality Engineering Complete Requirements should not leave anyone keep guessing or assuming To all stakeholders understanding should be same. Assumption is mother of all failures Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Completeness

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Completeness Requirements should be closed ended as much as possible Pg. 111 The Unschooled Mind

Software Quality Engineering Feasible

Software Requirement Engineering vs Software Quality Engineering Feasible Requirements should be possible to implement within limitations and capability of system. Core practice is to engage developer to provide technical reality check Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Feasible

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Feasible It is very difficult to identify feasible or non-feasible requirement without technical input. Pg. 111 The Unschooled Mind

Software Quality Engineering Necessary

Software Requirement Engineering vs Software Quality Engineering Necessary Work on the tasks as expected by the client not what developer want. Effort of working should be mapped with Business value Lead to scope creep Gold Platting is typical example of Necessary Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Necessary

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Necessary Focus should be on what is expected by client from market view-point. Pg. 111 The Unschooled Mind

Software Quality Engineering Verifiable

Software Requirement Engineering vs Software Quality Engineering Verifiable Requirements should be demoable or QA should be able to close the requirement after verification. Not testable requirements are usually not verifiable. Avoid writing shall or etc or must keywords Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Verifiable

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Verifiable Always look for keywords to be avoided. Get requirements vet from QA dept also. Pg. 111 The Unschooled Mind

Software Quality Engineering Traceable

Software RE vs Software QE Traceable Requirements should be linked to source in Requirement Specifications. Requirements should be linked with Use cases, design and test cases. Requirements should have forward and backward matching Pg. 111 The Unschooled Mind

Software Quality Engineering Example of Traceable

Software Requirement Engineering vs Software Quality Engineering

Software Requirement Engineering vs Software Quality Engineering Example of Verifiable Always look for keywords to be avoided. Get requirements vet from QA dept also. Pg. 111 The Unschooled Mind

Software Quality Engineering Traceable

Software RE vs Software QE Traceable Requirements should be linked to source in Requirement Specifications. Requirements should be linked with Use cases, design and test cases. Requirements should have forward and backward matching Pg. 111 The Unschooled Mind