Program Development Life cycle (Cambridge (CIE) A Level Computer Science): Flashcards

Exam code: 9618

1/47

0Still learning

Know0

  • Define program development life cycle (PDLC).

Cards in this collection (47)

  • Define program development life cycle (PDLC).

    The PDLC is a structured process used to design, build and test software solutions.

  • What does the program development life cycle ensure?

    That programs are developed systematically, efficiently and to a high standard.

  • Name the five stages of the program development life cycle.

    Analysis, design, coding, testing and maintenance.

  • What is the purpose of the analysis stage?

    To understand the problem that the program is being created to solve.

  • How is abstraction used in the analysis stage?

    To ignore unnecessary detail and focus only on what the program must do and the limitations it must work within.

  • True or False?

    The analysis stage decides which programming language to use.

    False.

    The analysis stage is about understanding the problem. The programming language is chosen at the coding stage.

  • A                          document is created during the analysis stage.

    A requirements document is created during the analysis stage.

  • What does a requirements document do?

    It breaks the problem into manageable parts, labels each requirement, and describes what success looks like for each feature.

  • What happens in the design stage?

    Developers plan how the program will work, creating a blueprint for the solution.

  • Name the three design tools used in the design stage.

    Structure diagrams, flowcharts and pseudocode.

  • What does a structure diagram do?

    It breaks the program down into smaller components.

  • What does a flowchart show?

    The logical flow of processes.

  • What happens in the coding stage?

    Developers write the program in a suitable programming language, in modules that work together to solve the full problem.

  • What is iterative testing in the coding stage?

    Each module is tested and debugged individually as it is created.

  • Why are modules retested whenever changes are made?

    To ensure that no new errors are introduced.

  • True or False?

    Testing is only carried out once the whole program has been written.

    False.

    Iterative testing happens during the coding stage on each module, as well as in the full testing stage once the program is complete.

  • What three things does the testing stage check?

    That the program meets all the original requirements, handles valid and invalid input correctly, and performs reliably under different conditions.

  • When does the maintenance stage begin?

    After the program has been delivered to the client or end users.

  • Name three activities in the maintenance stage.

    Fixing bugs that were not discovered during testing, updating features to meet new requirements, and improving performance or adapting to new systems.

  • Software maintenance ensures the program remains useful and                  over time.

    Software maintenance ensures the program remains useful and reliable over time.

  • Define Waterfall model.

    The Waterfall model is a sequential software development process divided into distinct phases, where each phase must be completed before the next one begins.

  • The Waterfall model is a                      software development process.

    The Waterfall model is a sequential software development process.

  • Name the six phases of the Waterfall model.

    Requirement gathering and analysis, system design, implementation, integration and testing, deployment, and maintenance.

  • What happens in the system design phase of the Waterfall model?

    The requirements are translated into a design, defining the overall architecture and identifying the main components.

  • What happens at deployment in the Waterfall model?

    The product is released or handed over to the client, which may involve installation, customisation and training.

  • True or False?

    In the Waterfall model, phases can overlap.

    False.

    Each phase must be completed before the next one begins.

  • Name two benefits of the Waterfall model.

    It is simple and linear, it has clear stages and milestones so progress is easy to track, and it is ideal for well-defined projects.

  • Name two drawbacks of the Waterfall model.

    It is inflexible once development begins, it is expensive to fix late problems, and it has a long development cycle.

  • When is the Waterfall model most suitable?

    When requirements are well understood and unlikely to change, and where high quality and compliance are essential.

  • Define iterative model.

    The iterative model is a type of Agile software development methodology that promotes adaptability and high customer involvement.

  • Define sprint.

    A sprint is a short time-boxed development period, usually 1 to 4 weeks.

  • How are requirements often written in the iterative model?

    As user stories.

  • What happens in a sprint review?

    The working software is demonstrated to stakeholders, and feedback is collected to identify changes or improvements.

  • What happens in a sprint retrospective?

    The team reflects on what went well and what needs improving, focusing on team performance and process optimisation.

  • How is testing handled in the iterative model?

    Testing is ongoing throughout the sprint, not saved for the end.

  • Name two benefits of the iterative model.

    It is highly adaptable, it promotes frequent communication, it focuses on quality, and it ensures customer collaboration.

  • Name two drawbacks of the iterative model.

    It requires experienced team members, carries a risk of burnout, may lack documentation, and risks scope creep.

  • When is the iterative model most suitable?

    For small to medium-sized projects where requirements can change and customer involvement is high.

  • Define Rapid Application Development (RAD).

    RAD is a software development methodology that emphasises fast and iterative development.

  • Name the five steps of RAD.

    Requirement planning, user design and prototyping, construction or iterative development, cutover or deployment, and maintenance and updates.

  • What happens in the user design and prototyping step of RAD?

    Developers collaborate with users to develop prototypes, ensuring alignment with user needs.

  • What happens at cutover in RAD?

    The product is transitioned into the live environment, including user training, support and documentation.

  • Name two benefits of RAD.

    Speed of development and delivery at relatively low cost, user involvement, flexibility, and incremental development in small testable parts.

  • Name two drawbacks of RAD.

    It requires strong team collaboration, risks quality issues because speed may reduce testing and documentation, is not ideal for small projects, and carries a scope creep risk.

  • True or False?

    RAD is best suited to small, simple projects.

    False.

    RAD is not ideal for small projects, because it may be too complex for simple systems.

  • When is RAD most suitable?

    When rapid delivery is required and where requirements can be developed and refined on the go.

  • Both the iterative model and RAD carry a risk of            creep, where flexibility leads to ever-expanding requirements.

    Both the iterative model and RAD carry a risk of scope creep, where flexibility leads to ever-expanding requirements.

Sign up to unlock flashcards

or