A. C Customer
C. T Transformation
D. A Actor
A. Middle level stakeholder</strong>
B. Entry level Personnel
C. . Users
A. Middle level stakeholder
B. Managers
D. Entry level personnel
B. TRUE
B. Volatile
C. Both Enduring & Volatile
D. All of the mentioned
A. TRUE
A. FALSE
A. Problem of understanding
C. Problem of volatility
D. Problem of scope
A. Primary
B. Secondary
C. Ternary
A. Traceable
B. Verifiable
C. Complete
A. Five
C. Four
D. Two
A. all of the mentioned
B. last for about 2-3 days
C. cover the technology used for the development
B. It involves successive steps
C. The prototype is built with the idea that it will eventually be converted into final system
D. It has a shorter development time
A. Investigation
B. Design
C. Construction and Test
A. Performance, Design
B. None of the mentioned
C. Functional, Non-Functional
A. None of the mentioned
B. Functional Application Specification Technique
C. Fast Application Specification Technique
A. Portability
B. Robustness
C. Maintainability
B. none of the mentioned
C. quality function design
D. quality function development
A. Three
B. Four
D. Six
A. Security, Safety, Testability, Usability
B. Availability, Reliability, Maintainability, Security
C. Usability, Reliability, Security, Flexibility
A. Functional, Non-Functional
C. Known, Unknown, Undreamed
D. User, Developer
A. Staffing
B. Delivery Schedule
C. Cost
B. FALSE
A. Idea -> Question -> Argument
B. Question -> Idea -> Argument
C. Issue -> Position -> Justification
B. Process-oriented Approach Focus on how NFRs can be used in the design process
C. Product-oriented Approach Focus on system (or softwarE. quality
D. Qualitative Approach Study various relationships between quality goals
A. RDD 100
B. RTM
C. DOORS
A. ER model
B. DFDs
C. Context Diagrams
A. Consistent
C. Correct
D. Ambiguous
B. Correct
C. Consistent
B. Quality graphical display
C. Overall operational correctness and reliability
D. Ease of software installation
A. Non-Functional
B. Developer
D. User
A. Usability
C. Availability
D. Flexibility
A. Fusion (by Coleman)
C. Object Modeling Technique (by Rumbaugh)
D. Object Oriented Design (by Booch)
A. Automatic Link Creation and Change
B. Documentation Support
C. Graphical Representation
B. Poor change management
C. All of the mentioned
D. Poor quality control
A. Scribe
B. Sponsor
B. SRS is written by a developer
C. . SRS serves as a contract between customer and developer</strong>
B. SSM is suitable for new systems
C. It incorporates human element into design
D. Standard methodologies like Role Exploration, Issue Resolution and Reorganization support SSM
C. Known Requirement
D. Non-Functional
A. every requirement stated therein is verifiable
C. every requirement stated therein is one that the software shall meet
D. its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure
B. Requirements Gathering
D. Listing out Requirements
Showing 1 to 50 of 80 mcqs