Question

a) Why is it essential to distinguish between and specify both user requirements and system requirements in the software specification process? Using one of the systems presented in Section 1.3, present one user requirement and the system requirements derived from it. b) How do you validate the user requirements and system requirements? Explain your validation procedure (~ step by step)for the above requirements.c) How do you do the software validation for the same requirements you selected above?Hint: ReviewSections 1.3 Case Studies,2.2.1Software Specification, and 2.2.3 Software Validation.

Answer 1

a.

The user requirements are drawn from system Definition Document, This document (sometimes known as the user requirements document or concept of operations document) records the system requirements. It defines the high-level system requirements from the domain perspective. Its readership includes representatives of the system users/customers (marketing may play these roles for market-driven software), so its content must be couched in terms of the domain.

The system requirements are drawn from System Requirements Specification, Developers of systems with substantial software and nonsoftware components—a modern airliner, for example—often separate the description of system requirements from the description of software requirements. In this view, system requirements are specified, the software requirements are derived from the system requirements, and then the requirements for the software components are specified. Strictly speaking, system requirements specification is a systems engineering activity and falls outside the scope of this Guide.

User requirement: Easy accessibility, flexible to use

System requirement: Automatic addition, fast

b. The validation of user and system requirements, Requirements validation is the fourth component—with elicitation, analysis, and specification—of requirements development. Validation assesses whether a product actually satisfies the customer needs (doing the right thing). Requirements validation attempt to ensure that:

• The SRS correctly describes the intended system capabilities and characteristics that will satisfy the various stakeholders’ needs.
• The software requirements were correctly derived from the system requirements, business rules, or other sources.
• The requirements are complete and of high quality.

The validation is performed by defining an acceptance criteria for accessing the software project.

c. The software validation for reuiremets selected above is performed as: The software validation process is defined and controlled through the use of a plan. The software validation plan defines “what” is to be accomplished through the software validation effort. Software validation plans are a significant quality system tool. Software validation plans specify areas such as scope, approach, resources, schedules and the types and extent of activities, tasks, and work items. For software that was previously validated, the existing software validation plan should be revised to support the validation of the revised software. If no previous software validation plan exists, such a plan should be established to support the validation of the revised software.

So, to validate a software a plan is required and if there is any change in the software then the plan is also changed.

----------------------------------------------------------------Please Upvote-----------------------------------------------------------