A. black-box
B. white-box
C. grey-box
D. none of the mentioned
Explanation: The system is considered as a black box whose internal details are not known that is, only its visible external (input/output) behavior is documented.
A. its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure
B. every requirement stated therein is one that the software shall meet
C. every requirement stated therein is verifiable
D. no subset of individual requirements described in it conflict with each other
Explanation: Real world object may conflict with each other for example one requirement says that all lights should be red while the other states that all lights should green
A. Verifiable
B. Ambiguous
C. Complete
D. Traceable
Explanation: The SRS should be unambiguous in nature which means each sentence in SRS should have a unique interpretation.
A. JAD
B. Traceability
C. FAST
D. Both JAD and Traceability
Explanation: Joint application design (JAD. is a process used to collect business requirements while develog new information systems for a company. Requirements traceability is concerned with documenting the life of a requirement and providing bi-directional traceability between various associated requirements.
A. Primary
B. Secondary
C. Ternary
D. Both Primary and Secondary
Explanation: A primary actor is one having a goal requiring the assistance of the system whereas, a secondary actor is one from which system needs assistance.There is no such thing as ternary actor in Software Engineering.
A. Known, Unknown, Undreamed
B. User, Developer
C. Functional, Non-Functional
D. Normal, Expected, Exciting
Explanation: According to QFD, Normal, Expected and Exciting requirements maximizes customer satisfaction from the Software Engineering Process.
A. Identifying Stakeholder
B. Listing out Requirements
C. Requirements Gathering
D. All of the mentioned
Explanation: Stakeholders are the one who will invest in and use the product, so its essential to chalk out stakeholders first.
A. Object Oriented Design (by Booch)
B. Use Cases (by Jacobson)
C. Fusion (by Coleman)
D. Object Modeling Technique (by Rumbaugh)
Explanation: Use Case captures who does what with the system, for what purpose, without dealing with system internals?
i. Consolidation
ii. Prioritization
iii. Requirements Gathering
iv. Evaluation
A. iii, i, ii, iv
B. iii, iv, ii, i
C. iii, ii, iv, i
D. ii, iii, iv, i
Explanation: Requirements gathering captures viewpoint from different users followed by evaluation of those view points.Now comes the task of checking the relative importance of the requirements and finally to consolidate or bind together the information collected.
A. Availability
B. Testability
C. Usability
D. Flexibility
Explanation: A developer needs to test his product before launching it into the market.