A. Functional, Non-Functional
B. User, Developer
C. Known, Unknown
D. All of the mentioned
Explanation: The CORE sessions includes the discussion of functional and non-functional requirements
A. Functional, Non-Functional
B. User, Developer
C. Known, Unknown
D. All of the mentioned
Explanation: The CORE sessions includes the discussion of functional and non-functional requirements
A. Idea -> Question -> Argument
B. Question -> Idea -> Argument
C. Issue -> Position -> Justification
D. Both Question -> Idea -> Argument and Issue -> Position -> Justification
Explanation: IBIS is a simple and non-intrusive method that provides a framework for resolving issues and gathering requirements.
A. User
B. Tester
C. Scribe
D. Sponsor
Explanation: A Tester’s role is seen in after coding phase rather than in elicitation phase
A. FODA
B. CORE
C. IBIS
D. Prototyg
Explanation: Feature Oriented Domain Analysis (FODA. is defined as the process of identifying, collecting, organizing and representing relevant information in a domain
A. True
B. False
Explanation: IBIS is a more structured approach as it captures information which is consistent and important.On the other hand CORE gives importance to every view point even if it is obsolete.
A. Context Diagrams
B. DFDs
C. ER model
D. UML diagrams
Explanation: Unified Modeling Language (UML) diagrams are constructed during the design phase of the SDLC.
A. Enduring
B. Volatile
C. Both Enduring & Volatile
D. All of the mentioned
Explanation: For library management system issue/return of a book, cataloging etc. are core activities and are stable for any system.
A. True
B. False
Explanation: Quality makes no sense without reference to requirements, which means quality-oriented development is requirements-driven development, thus requirements management is a prerequisite for quality-oriented development.
A. User and Developer
B. Functional and Non-functional
C. Enduring and Volatile
D. All of the mentioned
Explanation: Enduring requirements are core requirements & are related to main activity of the organization while volatile requirements are likely to change during software development life cycle or after delivery of the product.
A. to the environment
B. in technology
C. in customer’s expectations
D. in all of the mentioned.
Explanation: Systems continue to be built as the advancement of new products being launched in the market and so does the market changes, the technology and in turn customer’s expectation.