Your Answer : (Not Answered)

Correct Answer : D

The architectural model draws on (i), (ii) and (iii).

Pressman names three sources for the architectural model: information about the application domain for the software to be built, specific requirements model elements such as data flow diagrams or analysis classes with their relationships and collaborations, and the availability of architectural styles and patterns.

Options that exclude any one of these leave out a source the method relies on.

Your Answer : (Not Answered)

Correct Answer : A

All four statements belong to the change control process, so the answer is (i), (ii), (iii) and (iv).

In software configuration management, a configuration item can change freely while it is being developed, since it is not yet under SCM (i). While it undergoes formal technical review it is treated as frozen (ii). Once reviewed and approved it becomes a baseline and is entered into the project library, after which it is formally under SCM (iii). From then on, changes go through check-out and check-in: an approved change checks the item out of the library and checks the modified version back in, which provides access and synchronisation control (iv).

Each option that leaves a statement out omits a genuine stage of the process.

Your Answer : (Not Answered)

Correct Answer : B

CVS performs all four, so the answer is (i), (ii), (iii) and (iv).

Pressman's description of the Concurrent Versions System lists exactly these: it establishes a simple repository; it keeps all versions of a file in a single named file by storing only the differences between successive versions; it protects against simultaneous changes by giving each developer a separate working directory; and it merges the changes when each developer finishes.

Each three-item option leaves out one of these functions.

Your Answer : (Not Answered)

Correct Answer : A

The model is Basic COCOMO.

Boehm's Basic COCOMO estimates effort and development time from product size alone:

\[ E = a\,(KLOC)^{b}, \quad D = c\,E^{d} \]

with constants depending only on whether the project is organic, semi-detached or embedded.

Intermediate COCOMO multiplies the estimate by an effort adjustment factor from 15 cost drivers (product, hardware, personnel and project attributes), and Detailed COCOMO applies those drivers phase by phase, so neither depends on size alone. 'COCOMO' on its own names the whole family.

Your Answer : (Not Answered)

Correct Answer : D

The structure not among the loop classes is the Structured loop.

Loop testing, a white-box technique described by Beizer and in Pressman, considers four classes of loops: simple loops, nested loops, concatenated loops and unstructured loops. Each has its own test strategy; for simple loops, for example, the tests skip the loop, pass through once, twice, m times, and n - 1, n and n + 1 times.

The fourth class is the unstructured loop, which should be redesigned to use structured programming constructs. 'Structured loop' is not one of the classes.

Your Answer : (Not Answered)

Correct Answer : B

The test is Regression testing.

When modules are added or code is changed, regression testing re-runs a selected set of earlier tests to make sure the change has not broken behaviour that previously worked or introduced side effects.

Smoke testing is a quick check that a new build works well enough for further testing. Performance testing measures response time and throughput, and stress testing pushes the system beyond normal load to see how it fails. None of them is aimed at unintended effects of a change.

Your Answer : (Not Answered)

Correct Answer : D

Statements (ii) and (iii) are not true, so the answer is (ii) and (iii).

Quality assurance is process-oriented and proactive: it aims to prevent defects (i) by defining and improving the processes used across the whole development life cycle (iv). Both of those statements are true.

Statement (ii) is false because QA is preventive, not reactive; finding defects after the product is built is the reactive work of quality control. Statement (iii) is also false: validating the quality of the product, through testing and inspection, is quality control's job, while QA manages the process. Options containing (i) or (iv) are therefore wrong.

Your Answer : (Not Answered)

Correct Answer : C

McCall's product transition factors include (ii) and (iv): portability and reusability.

McCall's quality model groups factors under three headings. Product operation: correctness, reliability, efficiency, integrity, usability. Product revision: maintainability, flexibility, testability. Product transition: portability, reusability, interoperability.

Reliability is a product operation factor and testability a product revision factor, so every option containing (i) or (iii) is wrong.

Your Answer : (Not Answered)

Correct Answer : B

The statement that is not a design principle is (ii) only.

The Interface Segregation Principle, one of the class-based component design principles Pressman lists, says the opposite of (ii): many client-specific interfaces are better than one general-purpose interface, so that clients do not depend on operations they do not use.

Statement (i) is the Open-Closed Principle, that a module should be open for extension but closed for modification. Statement (iii) is the Common Closure Principle, that classes that change together belong together in a package. Both are genuine principles, so options including them are wrong.

Your Answer : (Not Answered)

Correct Answer : D

The answer is Formal methods.

Formal methods specify system requirements in a mathematical notation (such as Z or VDM), which gives a concise, unambiguous and consistent description that can be checked for contradictions and even used to prove properties of the design.

CMM is a model of process maturity, ISO standards define quality management processes, and CASE tools support development activities. None of these is itself a precise notation for documenting requirements.

Your Answer : (Not Answered)

Correct Answer : D

The tool least preferred at this stage is the class diagram, the fourth option.

Requirements gathering records what users need the system to do, in terms they can check. A use case diagram does this directly by showing the actors and the goals they achieve with the system. A sequence diagram shows one scenario of those goals as a series of messages between the actors and the system, and a finite-state machine specifies how the system responds to events as it moves between states, so all three describe required behaviour.

A class diagram describes the static structure of the software, its classes with attributes, operations and associations. Those are design decisions about how the software will be built, which stakeholders cannot validate at the gathering stage, so it is the one the question says 'may not be preferred'.

The item is one of degree: a high-level class (domain) diagram is sometimes drawn during analysis, but it is the most design-oriented of the four, and that is the reading the official key follows.

Your Answer : (Not Answered)

Correct Answer : D

The four XP framework activities are planning, design, coding, testing.

In Extreme Programming, planning begins with user stories and the customer's priorities; design follows the keep-it-simple principle with CRC cards and spike solutions; coding starts by writing unit tests and is done in pairs; and testing runs the automated unit tests continuously, with customer acceptance tests.

XP has no separate 'analysis' activity: understanding requirements happens inside planning through user stories. Every option that includes analysis is therefore wrong.

Your Answer : (Not Answered)

Correct Answer : A

The model is the Agile development model.

Agile methods, such as Scrum and Extreme Programming, deliver working software in short iterations, each adding an increment, and treat changing and emerging requirements as normal: the plan is revised after every iteration in response to feedback.

The evolutionary model also grows a system in versions, but it is defined by refining an initial prototype rather than by short, change-driven delivery cycles. Rapid application development stresses speed through reusable components and prototyping, and open source development describes a community-based way of building software, not a response to changing requirements.

Your Answer : (Not Answered)

Correct Answer : B

The agile practice is to Implement the system incrementally, building it up bit by bit.

Agile and iterative methods deliver working software in short iterations, each adding a small increment of functionality that users can see and give feedback on, so requirements and design evolve as the system grows.

Gathering all requirements first and producing complete, detailed design documents are features of the plan-driven waterfall model, and building the whole backend before any user-facing feature delays the feedback agile methods rely on.

Your Answer : (Not Answered)

Correct Answer : C

ASD's framework activities are speculation, collaboration, learning.

Jim Highsmith's Adaptive Software Development replaces the plan-design-build cycle with a speculate-collaborate-learn cycle. Speculation is adaptive cycle planning using the mission and constraints; collaboration brings motivated people together to build the components; learning reviews the results through focus groups, technical reviews and postmortems, feeding the next cycle.

Analysis, design and coding are the activities of a conventional linear model. Feasibility study and functional model iteration belong to DSDM. Adaptive cycle planning is part of speculation, not one of the three activities as a list.

Your Answer : (Not Answered)

Correct Answer : C

The units are software units.

The formula is the coupling metric proposed by Fenton and Melton for a pair of modules x and y. i is the worst (highest) type of coupling relationship found between the two, on an ordinal scale running from no coupling up to content coupling, and n is the number of interconnections between them. The units being measured are therefore software modules in general, whatever language or paradigm they come from.

The metric is not restricted to classes, objects or methods; those are particular kinds of unit in object-oriented design, and the measure applies to any pair of software units.

Your Answer : (Not Answered)

Correct Answer : A

The factor is iterative and incremental development.

The Rational Unified Process divides a project into four phases, inception, elaboration, construction and transition, each carried out in a series of iterations. Every iteration passes through requirements, analysis, design, implementation and testing and adds a further increment of working software. RUP is also described as use-case driven and architecture-centric.

'Continuous' and 'validations' are not the terms in which the RUP framework is defined; validation happens within each iteration but is not its organising principle.

Your Answer : (Not Answered)

Correct Answer : C

The aspect is the requirement - design - code - integrate cycle.

In continuous integration, developers integrate their work into a shared mainline frequently, often several times a day, and each integration is built and tested automatically. Every small piece of work therefore passes quickly through the full cycle of requirement, design, coding and integration, and errors are caught early rather than at a final 'big bang' integration.

The other options either leave out coding or design, or put coding before design, which is not the order of the cycle.

Your Answer : (Not Answered)

Correct Answer : A

Only statement i is true for the Waterfall Model. Because the model moves from one phase to the next in order, it works badly when issues are left unsolved at a previous step. Statement ii describes iterative or cyclic models, statement iii (consideration of risk) is a feature of the spiral model, and testing at each stage in a reverse manner (iv) is the V-model. So the options with ii, iii or iv are wrong. In the waterfall model the stages (requirements, design, coding, testing and maintenance) follow one another in a line, with little return to an earlier stage.

Your Answer : (Not Answered)

Correct Answer : B

Project management software is used across industries for project planning, resource allocation and scheduling. CRM software manages customer relationships, a word processor prepares documents and a firewall program protects a network from unauthorised access, so none of these does the planning and scheduling named in the question. Examples of such software are Microsoft Project and Primavera, which use charts and timelines to schedule tasks and resources.