Scribd
Upload
209 views

Assignment # (3) : Abasyn University Peshawar

The document contains answers to questions about software requirement engineering. 1) Requirements engineering artifacts like use cases and models are used by both requirements engineers and software architects. Architecturally significant requirements can be elicited from stakeholders through techniques like interviews, workshops, and prototyping. 2) One can analyze design tradeoffs and associated risks by using techniques like Architecture Tradeoff Analysis Method, which provides a rigorous process to evaluate alternatives and ensure the best solution meets requirements. 3) The engineering project traceability model is explained using the V-model, where each requirement is traced from elicitation through validation. Requirement traceability brings consistency and helps verify the origin, location, and application

Uploaded by

Reality Techs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
209 views

Assignment # (3) : Abasyn University Peshawar

The document contains answers to questions about software requirement engineering. 1) Requirements engineering artifacts like use cases and models are used by both requirements engineers and software architects. Architecturally significant requirements can be elicited from stakeholders through techniques like interviews, workshops, and prototyping. 2) One can analyze design tradeoffs and associated risks by using techniques like Architecture Tradeoff Analysis Method, which provides a rigorous process to evaluate alternatives and ensure the best solution meets requirements. 3) The engineering project traceability model is explained using the V-model, where each requirement is traced from elicitation through validation. Requirement traceability brings consistency and helps verify the origin, location, and application

Uploaded by

Reality Techs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

ABASYN UNIVERSITY PESHAWAR

DEPARTMENT OF COMPUTER SCIENCE

Assignment # (3)

Subject: - Software Requirement Engineering

Question no 1:

Which requirements engineering artifacts are likely to be used by


both requirements engineers and software system architects? What
kinds of practices can be used to elicit architecturally significant
requirements from stakeholders?
Answer:
Requirements engineering is the process of eliciting stakeholder needs and desires and
developing them into an agreed-upon set of detailed requirements that can serve as a
basis for all subsequent development activities. The purpose of requirements
engineering methodologies is to make the problem that is being stated clear and
complete, and to ensure that the solution is correct, reasonable, and effective. This
chapter summarizes available representative requirements engineering methodologies,
mainly focusing on the principles. Requirements engineering approaches are processes
that develop real-world problems into digital world solutions. Each approach has its
specialized thinking about the real-world problem and follows a unique process to build
the system specification as the solution.

Question no 2:
How does one analyze design tradeoffs and the associated risks with
implementing a system that best meets requirements?
Answer:
An Architecture Tradeoff Analysis Method-based technique is the most rigorous of the
three approaches discussed in this book and as such may yield the best results,
providing that the review is conducted by closely following the Architecture Tradeoff
Analysis Method process and the review team has gone through the formal Architecture
Tradeoff Analysis Method evaluator training.

Question no 3:
Describe the given “engineering project traceability model” briefly
with step by step. As the V-model is used here to elaborate every
requirement to be trace. Discuss the requirement elicitation and
validation briefly in terms of requirement traceability.
Answer:
Traceability in software engineering describes the extent to which documentation or code
can be traced back to its point of origin. The goal of traceability is to provide better
quality and consistency of product development. It brings the ability to verify the history,
location, and application of an item by means of documented identification.
Question no 4:
Considering the requirement traceability in a project SDLC, how we
can answer the given questions briefly.

You might also like