Skip to topic
    ← Back to course topics

    Maintenance and development — OCR A-Level Computer Science

    Maintenance and development explained

    Maintenance and development covers 2 specification points, including (a) Discuss the maintainability of the solution.

    Read the full explanation

    and (b) Discuss potential further development of…. Open a point below for its explanation and revision guidance.

    (a) Discuss the maintainability of the solution.

    This criterion asks you to discuss how maintainable your solution is. Maintainability means how easily a future programmer can understand, correct and extend the code and documentation. Discuss means you weigh the strengths and weaknesses of the solution, linking each point to evidence from your own project, and reach a supported overall view. For example, state that well-named procedures and comments make a fault easier to locate, then note a section where one long, tangled function would make changes risky. Do not simply list features, and do not claim maintenance support that the code does not provide.

    (b) Discuss potential further development of the solution.

    This statement asks you to discuss potential further development of a software solution within the programming project evaluation. When completing a project, developers identify realistic opportunities to extend or refine the completed system. Begin by specifying clear, practical enhancements informed by stakeholder feedback, performance testing, or usability evaluations. Discuss what each development requires across data structures, algorithms, user interface, and system architecture. Weigh the benefits against the technical challenges, development time, and maintenance requirements. Conclude with a reasoned justification of which enhancement should take priority.

    Your focus

    1. Identify features of the solution that support or hinder future maintenance.
    2. Explain how a specific feature would help a future programmer make a particular change.
    3. Justify an overall judgement on the maintainability of the solution.
    Show all 6 objectives
    1. Identify realistic post-development enhancements for a completed software system.
    2. Analyze the architectural and algorithmic changes required by proposed developments.
    3. Evaluate and justify the prioritization of further developments based on user feedback and feasibility.

    Maintenance and development exam tips

    Marking Points
    • Identifies specific features of the solution, such as modular design, naming and commenting, that support maintenance.
    • Explains how each feature helps a future programmer, for example by making a fault easier to locate.
    • Considers weaknesses, such as hard-coded values or duplicated code, and their effect on future change.
    • Links each point to evidence from the project rather than offering general statements about good practice.
    • Reaches a supported overall judgement on how maintainable the solution is.
    • Identifies specific, realistic further developments informed by project testing and stakeholder feedback.
    • Explains the technical implications of proposed developments across system design, algorithms, and data structures.
    • Weighs the benefits of each development against the implementation effort, overhead, and ongoing maintenance requirements.
    • Provides a reasoned justification prioritizing which further development should be undertaken first.
    Examiner Tips
    • 💡Plan two or three strengths and one or two weaknesses before writing, so the discussion is balanced.
    • 💡Use specific names from your code, such as a named procedure or module, to anchor each point in evidence.
    • 💡Finish with one sentence of judgement that follows directly from the points you have discussed.
    • 💡Base potential further developments on tangible feedback gathered during user, robustness, and performance testing.
    • 💡Explain how proposed changes would integrate with existing data structures and modular program architecture.
    • 💡Justify recommended improvements using clear criteria such as usability gains, maintainability, and algorithmic efficiency.
    Common Mistakes
    • Lists generic good practices without relating them to the solution, so the answer lacks evidence; name the actual procedures, files or structures in your project.
    • Treats maintainability as only the user interface; consider the code, documentation and overall structure as well.
    • Describes weaknesses without judging their effect on future change; explain what would be harder to change and why.
    • Ends with a description rather than a judgement; finish with a supported overall view that follows from the points made.
    • Lists generic future ideas without detailing the technical changes needed in code, data structures, or interface design.
    • Describes features already implemented in the project instead of focusing strictly on potential post-submission developments.
    • Recommends changes without weighing technical feasibility, development overhead, or user impact.