Which of the following is not a 'concern' during management of a software project?
Pick an option to check yourself, or open the answer below.
Show answer & explanation
Correct answer: A. Project/Product information
Explanation
Software project management is classically organised around the measurable constraints of a project — the time taken (schedule), the money spent (cost/budget) and the quality delivered — which together with scope form the standard project-management trade-off triangle. 'Project/Product information' is not itself a management constraint or concern; it is simply descriptive data about the project, not something that project management actively tracks and trades off the way it does time, cost and quality. Therefore, of the given choices, Project/Product information is the one that is not a genuine management concern.More Software Engineering questions
- Which document outlines the functional and non-functional requirements of a software system?
- Match the LIST-I with LIST-II. LIST-I (Process model) LIST-II (Characteristics) A. Classical Waterfall Model I. Risk Analysis B. Prototype…
- Match the LIST-I with LIST-IILIST-I (Life Cycle Model) LIST-II (Description) A. Waterfall Model I. Interactive collaboration, customer feed…
- The entire program is written in FORTRAN. The percentage decrease in the execution time, resulting from rewriting the 1% of code (that acco…
- If 99% of the program is written in FORTRAN and the remaining 1% directly in assembly language, the percentage increase in the execution ti…
- If a project team needs 13 days to completely write the program in FORTRAN and rewriting (converting) the 1% code to assembly language, the…