This document contains a presentation on software requirements engineering. It lists 10 multiple choice questions covering topics such as the difference between the system-as-is and system-to-be, examples of descriptive and prescriptive statements, how to relate software requirements to system requirements, the benefits of requirements taxonomies, and the aim of domain understanding. Interview techniques are also discussed such as identifying the right interview sample and appearing trustworthy. Other questions define fault trees, frame diagrams, and the difference between causal and biddable components.

1. SOFTWARE REQUIREMENTS
ENGINEERING
Presented by,
S.Divya M.E CSE

2. 2 MARK QUSTION
1.What is system-as-is and system-to-be?
• System-as-is: system as it exists before the machine is built into it
• System-to-be: system as it should be when the machine will operate into it
2.Draw the dimensions of requirement engineering.

3. 3.Give an example for the descriptive and prescriptive statements.
• If train doors are closed, they are not open”
• Descriptive :“If the train’s acceleration is positive, its speed is non-null”
• Prescriptive Statements :“Doors shall always remain closed when the
train is moving”
4.How you will relate the software requirements to system requirements?

4. 5.What are the benefits of requirements taxonomies?
• Quality of service
• Usability
• Scalability
• Architectural constraint
• Development constraint
6.Bring out the aim of domain understanding.
• To make sure that a software solution correctly solves a particular
problem, we must first correctly understand and define what problem
needs to be solved.

5. 7.Give your ideas to increase the effectiveness of interviews.
 Identify the right interviewee sample for full coverage of Issues
 Come prepared, to focus on right issue at right time
 – backgound study first
 – predesign a sequence of questions
 Keep control over the interview
 Make the interviewee feel comfortable
 – Start: break ice, provide motivation, ask easy questions
 – Consider the person too, not only the role
 – Do always appear as a trustworthy partner

6. 8.Define fault trees.
• Fault tree analysis (FTA) is a top down, deductive failure analysis in
which an undesired state of a system is analyzed using Boolean logic to
combine a series of lower-level events.
9.Define frame diagram and its phenomenon.
• A frame diagram is a generic problem diagram capturing a problem pattern
Called a frame.
• The interface labels are now typed parameters, they are fixed by ‘C’ , ‘E’
or ‘Y’ depending on whether they are to be instantiated to causal ,event or
symbolic phenomena respectively.

7. 10.What is casual and biddable component?
• A causal component ,marked by a ‘C’ has some internal causality that
can be enforced .
• A biddable component, marked by a ‘B’,has no such enforceable
causality.