Which one of the following is not the part of requirement management?
Page Traceability Table
Requirements management is the set of activities that identify, control and track requirements and their changes throughout the project. Pressman describes how each requirement is given an identifier and then related to other project elements through traceability tables.
The traceability tables Pressman lists are: the features traceability table (how requirements relate to observable system or product features), the source traceability table (the source of each requirement), the dependency traceability table (how requirements are related to one another), the subsystem traceability table (which subsystems govern each requirement) and the interface traceability table (how requirements relate to internal and external system interfaces).
Features, dependency and interface traceability tables are therefore all part of requirements management.
A 'page traceability table' does not exist in this scheme; requirements are traced to features, sources, other requirements, subsystems and interfaces, not to pages of a document.
Page Traceability Table option is correct.
Similar Questions
To compute function points (FP), the following relationship is used
FP = Count – total × (0.65 + 0.01 × Σ(Fi)) where Fi (i = 1 to n) are value adjustment factors (VAF) based on n questions. The value of n is
Which one of the following statements, related to the requirements phase in Software Engineering, is incorrect ?
In CRC based design, a CRC Team consists of :
(a) one or two users representatives
(b) several programmers
(c) project co-ordinators
(d) one or two system analysts
Codes :
Which one of the following non-functional quality attributes is not highly affected by the architecture of the software ?
Requirements prioritisation and negotiation belongs to :
Match the following :
(a) Size-oriented metrics (i) uses number of external interfaces as one of the measurement parameter. (b) Function-oriented metrics (ii) originally designed to be applied to business information systems. (c) Extended Function Point metrics (iii) derived by normalizing quality and/or productivity measures by considering the size of the software. (d) Function point (iv) uses algorithm characteristics as one of the measurement parameter. Codes :
Match the following :
List - I List - II a. Correctness i. The extent to which a software tolerates the unexpected problems b. Accuracy ii. The extent to which a software meets its specifications c. Robustness iii. The extent to which a software has specified functions d. Completeness iv. Meeting specifications with precision Consider a project with the following functional units :
Number of user inputs = 50
Number of user outputs = 40
Number of user enquiries = 35
Number of user files = 06
Number of external interfaces = 04
Assuming all complexity adjustment factors and weighing factors as average, the function points for the project will be
In function point analysis, the number of complexity adjustment factors is
Collaborative document inspection technique used for?
Important Questions from Software Requirement
What is the other name of Data Flow Diagram (DFD)?
- Which of the followings belongs to MaCall's quality factors?
A. Maintainability
B. Usability
C. Integrity
D. Functionality
Choose the correct answer from the options given below: - Which of the following is not a requirement elicitation Technique
The process followed in order to find difficult, unknown and hidden information about a software system is called
- Which of the followings is NOT a software characteristic?
