Archive

Posts Tagged ‘Requirements Validation’

Business Requirements Vs System Requirements

March 12, 2011 3 comments
S No Business Requirements System Requirements

1

Business requirements are criteria in order for the software to be successful in meeting the user needs. Generally they focus on the “what” not the “how”. System requirements address the “how” associated with the business requirements (the “what”).

2

Business requirements concern the business. Software requirements concern the software solution to the “problem” stated in the business requirements.

3

Business requirements defined as benefits of the business desires. Software requirements define what the solution must do (or be) to assure the business requirements.

4

Business Requirements are goals and targets the business wants to achieve.

Examples:  No: 1 jobs consultancy company

System Requirements are technical goals

 Example: Implement web based job portal.

Benefits of traceability Matrix

March 12, 2011 2 comments
  • Demonstrate the relationship between the requirements to the system.
  • To ensure the design is based on established scope, business requirement or functional requirements.
  • To ensure that the design documents are appropriately verified, and that functional requirements are appropriately validated.
  • To track the requirements changes and their impact to the system
  • To demonstrate the system built met the functionality of the customer, end users needs and expectations.
  • At faster rate can trace back to the functionality/design/test cases, if there is means of any defect/changes to the system.