Friday, July 26, 2013

Software Engineering 02

11. Which one of the following statements is incorrect?                    [Paper III June 2012]
(A) The number of regions corresponds to the cyclomatic complexity.
(B) Cyclometric complexity for a flow graph G is V(G) = N – E + 2, where E is the number of edges and N is the number of nodes in the flow graph.
(C) Cyclometric complexity for a flow graph G is V(G) = E – N + 2, where E is the number of edges & N is the number of nodes in the flow graph.
(D) Cyclometric complexity for a flow graph G is V(G) = P + 1, where P is the number of predicate nodes contained in the flow graph G.

12. Are we building the right product? This statement refers to        [Paper III June 2012]
(A) Verification
(B) Validation
(C) Testing
(D) Software quality assurance

13. Consider the following pseudo-code:                                        [Paper III June 2012]
If (A > B) and (C > D) then
        A = A + 1
        B = B + 1
Endif
The cyclomatic complexity of the pseudo-code is
(A) 2                (B) 3
(C) 4                (D) 5

14. Which diagram provides a formal graphic notation for modelling objects, classes and their relationships to one another?                                                                                 [Paper III June 2012]
(A) Object diagram
(B) Class diagram
(C) Instance diagram
(D) Analysis diagram





SOLUTIONS


11. B
Refer  Solution to question number 7

12. B
In software project management, software testing, and software engineering, verification and validation (V&V) is the process of checking that a software system meets specifications and that it fulfils its intended purpose.
Definition:

Validation: Are we building the right product?
Verification: Are we building the product right?

13. A
Cyclomatic complexity = No of decision points + 1
Here we have only one decision point, so cyclomatic complexity = 1 + 1 = 2

14. A
All the diagrams given in the options are part of  Unified Modelling Language (UML).
An Object Diagram focuses on some particular set of objects and attributes, and the links between these instances.
The Class Diagram is the main building block of object oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modelling. The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed.


The basic idea of an Instance Diagram is to make a static snap shot of instances (not classes) in your system or subsystem. Make it show exactly who points to whom.

No comments:

Post a Comment