📚 A-Level Computer Science: Software Development, Programming, Testing & Installation | A-Level 计算机：软件开发、编程、测试与安装流程
Software development is far more than writing code: it is a disciplined, systematic process that transforms a user's need into a working, tested and deployed system. For CIE A-Level Computer Science, you must understand every stage of this lifecycle, from initial analysis through design, programming, testing, installation and finally maintenance, and you must be able to discuss the techniques and tools used at each stage.
软件开发远不止编写代码：它是一个有纪律、系统化的过程，将用户的需求转化为可用、经过测试并部署的系统。对于 CIE A-Level 计算机科学考试，你必须理解这一生命周期的每个阶段，从最初的分析，经过设计、编程、测试、安装，直至最后的维护，并且必须能够讨论每个阶段所使用的技术和工具。
1. The Software Development Life Cycle | 软件开发生命周期
The software development life cycle (SDLC) is an idealised model describing the stages involved in creating a software system. A common model used in the CIE syllabus is: analysis, design, programming (implementation), testing, installation and maintenance. Each stage produces a deliverable that becomes the input to the next stage, and because software continues to evolve, maintenance can trigger an entirely new cycle of analysis and design.
软件开发生命周期（SDLC）是描述创建软件系统所涉及阶段的理想化模型。CIE 教学大纲中常用的一种模型是：分析、设计、编程（实现）、测试、安装和维护。每个阶段产出的交付物成为下一阶段的输入，而由于软件会持续演变，维护可能触发一个全新的分析设计循环。
In examination answers, you should always link a stage to its purpose and its outputs. For example, the analysis stage outputs a requirements specification, while the design stage outputs a detailed design specification. Examiners reward candidates who can explain why each stage matters, not merely list stage names in order. You should also recognise that the lifecycle is not a rigid sequence; in practice stages overlap and developers often return to earlier stages when problems are discovered.
在考试作答中，你应该始终将阶段与目的和输出联系起来。例如，分析阶段输出需求规格说明书，而设计阶段输出详细设计规格说明书。考官更青睐能够解释每个阶段为何重要的考生，而不仅仅是按顺序罗列阶段名称。你还应该认识到生命周期不是僵化的序列；在实践中阶段会重叠，开发人员发现问题时经常会回到更早的阶段。
2. The Analysis Stage | 分析阶段
The analysis stage begins with a feasibility study to determine whether the proposed project is technically, economically and operationally possible. The analyst then collects detailed requirements using a variety of methods, including interviews with stakeholders, questionnaires distributed to many users, direct observation of current working practices and examination of existing documentation and transaction logs.
分析阶段始于可行性研究，以确定拟议项目在技术上、经济上和操作上是否可行。随后，分析师通过多种方法收集详细需求，包括与利益相关者进行访谈、向众多用户分发问卷、直接观察当前工作方式以及查阅现有文档和交易日志。
Each data collection method has trade-offs. Interviews allow detailed probing and clarification but are time-consuming and expensive. Questionnaires reach a large sample quickly and can be analysed statistically, but responses may be incomplete or ambiguous. Observation shows what users actually do rather than what they say they do, yet users may behave differently when watched. You must be prepared to recommend a method for a specific scenario and justify your choice.
每种数据收集方法都有权衡。访谈允许深入追问和澄清，但耗时且成本高。问卷能快速覆盖大样本并可用统计方法分析，但回答可能不完整或不明确。观察能展示用户实际行为而非口头描述的行为，但用户在被观察时可能会表现不同。你必须准备好为特定场景推荐一种方法并证明你的选择。
The key deliverable of the analysis stage is the requirements specification, stating what the system must do from the user's perspective. This differs from the system specification, which describes how the system will achieve those requirements in technical terms. Examiners frequently ask you to distinguish these two documents.
分析阶段的关键交付物是需求规格说明书，从用户角度陈述系统必须做什么。这不同于系统规格说明书，后者以技术术语描述系统将如何实现这些需求。考官经常要求你区分这两份文档。
3. The Design Stage | 设计阶段
In the design stage, the system is planned in detail before any program code is written. The most common approach is top-down (modular) design, in which the problem is decomposed into smaller, more manageable modules. Each module has a single well-defined task, and modules communicate through carefully specified interfaces. This approach makes the system easier to code, test and maintain because each module can be developed and verified independently.
在设计阶段，系统在编写任何程序代码之前进行详细规划。最常用的方法是自顶向下（模块化）设计，将问题分解为更小、更易管理的模块。每个模块承担单一明确定义的任务，模块之间通过仔细规定的接口通信。这种方法使系统更易于编码、测试和维护，因为每个模块可以独立开发和验证。
Design covers not only the program structure but also the algorithms, data structures, database schemas and the user interface. Pseudocode and flowcharts are the standard tools for representing algorithms at this stage. For CIE Paper 2, you are expected to trace through pseudocode, identify errors in it and produce your own pseudocode for a given problem, so you must follow the syllabus conventions for sequence, selection and iteration constructs.
设计不仅涵盖程序结构，还包括算法、数据结构、数据库模式和用户界面。伪代码和流程图是此阶段表示算法的标准工具。对于 CIE Paper 2（试卷二），你被要求追踪伪代码、识别其中的错误并为给定问题编写自己的伪代码，因此你必须遵循教学大纲中顺序、选择和循环结构的约定。
A strong design makes implementation straightforward; a weak or rushed design leads to confusing code, duplicated logic and difficult maintenance. Examiners may ask why modularity is beneficial, so remember: it supports parallel development, simplifies testing, improves readability and localises the impact of changes.
好的设计使实现变得直接；而薄弱或仓促的设计会导致代码混乱、逻辑重复且难以维护。考官可能会问模块化的好处，请记住：模块化支持并行开发、简化测试、提高可读性并将修改影响局部化。
4. The Programming Stage | 编程阶段
Implementation, or coding, is the stage where the design is converted into an executable program. A key decision is the choice of programming language. High-level languages are portable across platforms, closer to the problem domain and far easier to read, write and maintain; low-level languages such as assembly give fine-grained control over hardware and maximum execution efficiency, but they are tedious, error-prone and machine-specific.
实现（编码）阶段是将设计转换为可执行程序的阶段。一个关键决策是编程语言的选择。高级语言具有跨平台可移植性，更贴近问题域，且更易于阅读、编写和维护；低级语言（如汇编语言）能对硬件进行细粒度控制并获得最大执行效率，但繁琐、易出错且依赖特定机器。
Structured programming is built on just three constructs: sequence, selection and iteration. Programs are decomposed into subroutines, procedures and functions, each performing a single logical task. Parameters allow data to be passed into and out of subroutines, and local variables keep each subroutine independent. Writing programs in this style reduces errors and makes testing far simpler.
结构化编程仅基于三种结构：顺序、选择和循环。程序被分解为子程序、过程和函数，每个执行单一逻辑任务。参数允许数据传入和传出子程序，局部变量保持每个子程序的独立性。以这种方式编写的程序能减少错误，并大大简化测试。
An integrated development environment (IDE) supports the programmer with several tools. The editor provides syntax highlighting and autocompletion; the compiler or interpreter translates the source code and reports syntax errors; the debugger allows breakpoints, step-by-step execution and inspection of variable values. You should know which IDE facility to use for each task, for example using the debugger to set a breakpoint to examine the value of a variable at a specific line.
集成开发环境（IDE）通过多种工具为程序员提供支持。编辑器提供语法高亮和自动补全；编译器或解释器翻译源代码并报告语法错误；调试器支持设置断点、单步执行和检查变量值。你应该了解每项 IDE 功能对应的用途，例如，使用调试器设置断点，在特定代码行检查变量的值。
5. Types of Programming Errors | 程序错误类型
Every programmer makes mistakes, and a significant part of the implementation process is finding and removing them. There are three categories of error. Syntax errors violate the grammar rules of the programming language; they are detected immediately by the compiler or interpreter, and the program cannot run
Published by TutorHao | A-Level Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图