In Software Engineering Jackson's Principle based on A. Designation B. Definitions C. Refutable Assertions D. Formal Review E. Requirement Elicitation Choose the correct answer from the options given below:
A, B & C Only
Michael Jackson, in his work on software requirements and specifications, argued that a requirements description must be precise about how its terms relate to the real world. He proposed three kinds of statements on which such descriptions rest.
A. Designation: a designation is an informal but precise rule that tells how to recognise a basic phenomenon in the world and gives it a formal name (for example, 'x is a mother of y' recognised in a stated way). It anchors the formal terms to reality.
B. Definitions: once basic terms are designated, further terms are introduced by formal definitions built from designated terms, adding no new facts about the world.
C. Refutable assertions: statements about the world expressed in the designated and defined terms that could in principle be shown false by observation; these carry the actual content of the requirements.
D. Formal review and E. requirement elicitation are activities of the requirements engineering process (validation and gathering), not elements of Jackson's descriptive principle, so any combination including D or E is wrong.
A, B & C Only option is correct.
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
Which one of the following is not the part of requirement management?
What is the other name of Data Flow Diagram (DFD)?
The process followed in order to find difficult, unknown and hidden information about a software system is called