1.What is the primary limitation of the CORE methodology?
2.Is a narrative essay considered an effective type of specification document?
3.In requirement elicitation, how many distinct scenarios are typically involved?
4.What makes the process of Requirements Elicitation challenging?
5.Is the process of requirements elicitation iterative in nature?
6.Which characteristic of a Software Requirements Specification (SRS) is described by the phrase: "Adherence to a standard is ensured"?
7.Which of the following statements regarding the Software Requirements Specification (SRS) is correct?
8.Analyze the statement: "The data set will include an end of file character." Which attribute of a Software Requirements Specification (SRS) does this statement illustrate?
9.Which element is typically part of a Software Requirements Specification (SRS)?
10.How should the following components be ordered to create an IEEE-compliant SRS prototype outline?
11.Analyze the following statement: "The product must provide an intuitive human interface." Which SRS quality attribute does this statement illustrate?
12.Analyze the following statement: "The program's output must be delivered within 10 seconds of event X in at least 10% of cases." Which attribute of a Software Requirements Specification (SRS) does this illustrate?
13.What type of specification is the SRS document commonly referred to as?
14.When is an SRS considered consistent?
15.Which characteristic is not desirable for a well-written Software Requirements Specification (SRS)?
16.Which requirement gathering technique, created by IBM in the 1970s, is commonly used for facilitating requirement elicitation?
17.Which types of actors are identified in Object-Oriented Software Engineering (OOSE)?
18.Which categories of requirements are identified in Quality Function Deployment (QFD)?
19.What is the initial phase in the process of requirement elicitation?
20.Which methodology was introduced for requirements gathering and modeling to provide a functional perspective of the system?