Section A

    In this section Fill in the gap with the term that corresponds to the definition


  2. Blank


  4. Test automation, "Test automation means that tests are written as executable components before the task is implemented
    These testing components should be stand-alone, should simulate the submission of input to be tested and should check that the result meets the output specification. An automated test framework (e.g. Junit) is a system that makes it easy to write executable tests and submit a set of tests for execution.
    As testing is automated, there is


  6. Blank


  8. In XP, a customer or user is part of the XP team and is responsible for making decisions on requirements.
    User requirements are expressed as user stories or scenarios.
    These are written on cards and the development team break them down into implementation tasks. These tasks are the basis of schedule and cost estimates.
    The customer chooses the stories for inclusion in the next release based on their priorities and the schedule estimates.


  10. Programming team look for possible software improvements and make these improvements even where there is no immediate need for them.
    This improves the understandability of the software and so reduces the need for documentation.
    Changes are easier to make because the code is well-structured and clear.
    However, some changes requires architecture refactoring and this is much more expensive.


  12. A very influential agile method, developed in the late 1990s, that introduced a range of agile development techniques.
    Extreme Programming (XP) takes an  extreme approach to iterative development.
    New versions may be built several times per day;
    Increments are delivered to customers every 2 weeks;
    All tests must be run for every build and the build is only accepted if tests run successfully.


    Section B

    In this section you have 4 options, select the one option that corresponds with the question stated

  14. Scrum is an agile method that focuses on managing iterative development rather than specific agile practices.
    There are three phases in Scrum.
    The initial phase is an outline planning phase where you establish the general objectives for the project and design the software architecture.
    This is followed by a series of sprint cycles, where each cycle develops an increment of the system.
    The project closure phase wraps up the project, completes required documentation such as system help

  15. Examples of task cards for prescribing medication , Refactoring, "Conventional wisdom in software engineering is to design for change. It is worth spending time and effort anticipating changes as this reduces costs later in the life cycle.
    XP, however, maintains that this is not worthwhile as changes cannot be reliably anticipated.
    Rather, it proposes constant code improvement (refactoring) to make changes easier when they have to be implemented.

  16. Programmers prefer programming to testing and sometimes they take short cuts when writing tests. For example, they may write incomplete tests that do not check for all possible exceptions that may occur.
    Some tests can be very difficult to write incrementally. For example, in a complex user interface, it is often difficult to write unit tests for the code that implements the  display logic and workflow between screens.
    It is difficult to judge the comple

  17. Re-organization of a class hierarchy to remove duplicate code.
    Tidying up and renaming attributes and methods to make them easier to understand.
    The replacement of inline code with calls to methods that have been included in a program library.

  18. Blank

  19. The role of the customer in the testing process is to help develop acceptance tests for the stories that are to be implemented in the next release of the system.
    The customer who is part of the team writes tests as development proceeds. All new code is therefore validated to ensure that it is what the customer needs.
    However, people adopting the customer role have limited time available and so cannot work full-time with the development team. They may feel that providing

  20. Testing is central to XP and XP has developed an approach where the program is tested after every change has been made.
    XP testing features:
    Test-first development.
    Incremental test development from scenarios.
    User involvement in test development and validation.
    Automated test harnesses are used to run all component tests each time that a new release is built.

  21. Agile method applicability, "Product development where a software company is developing a small or medium-sized product for sale.
    Virtually all software products and apps are now developed using an agile approach
    Custom system development within an organization, where there is a clear commitment from the customer to become involved in the development process and where there are few external rules and regulations that affect the software.
    Term: Influential XP practices

  22. Blank
    Term: he requirements was enough of a contribution and so may be reluctant to get involved in the testing process. "

  23. In pair programming, programmers sit together at the same computer to develop the software.
    Pairs are created dynamically so that all team members work with each other during the development process.
    The sharing of knowledge that happens during pair programming is very important as it reduces the overall risks to a project when team members leave.
    Pair programming is not necessarily inefficient and there is some evidence that suggests that a pair working together is more effic
    Term: Plan-driven and agile development

  24. Extreme programming practices (a) , Extreme programming practices (b), XP and agile principles, "Incremental development is supported through small, frequent system releases.
    Customer involvement means full-time customer engagement with the team.
    People not process through pair programming, collective ownership and a process that avoids long working hours.
    Change supported through regular system releases.
    Maintaining simplicity through constant refactoring of
    Term: Agile development

  25. Agile methods
    Agile development techniques
    Agile project management
    Scaling agile methods
    Term: ally reduce the delivery time for working software systems"

  26. Blank
    Term: Test-driven development