A-Level Computer Science: Key Stages of System Design | A-Level 计算机：系统设计的关键环节

📚 A-Level Computer Science: Key Stages of System Design | A-Level 计算机：系统设计的关键环节

The design stage is one of the most important phases in the systems life cycle. It transforms the requirements identified during analysis into a detailed technical blueprint that can be implemented by developers. A well-structured design ensures that the final system meets user needs, is reliable, and is maintainable.

设计阶段是系统生命周期中最重要的环节之一。它将分析阶段确定的需求转化为可供开发人员实施的技术蓝图。良好的设计能够确保最终系统满足用户需求、运行可靠且易于维护。

1. The System Life Cycle and Design | 系统生命周期与设计

A typical system life cycle includes feasibility study, requirements analysis, design, implementation, testing, installation, documentation, and maintenance. The design stage follows analysis and precedes coding. Its purpose is to specify exactly what needs to be built — the software architecture, data structures, interfaces, and algorithms.

典型的系统生命周期包括可行性研究、需求分析、设计、实施、测试、安装、文档编写和维护。设计阶段位于分析之后、编码之前，其目的是精确地规定需要构建的内容——软件架构、数据结构、界面和算法。

Design activities are broadly grouped into logical design and physical design. Logical design describes what the system will do, while physical design describes how it will be done using specific hardware and software. Both must be aligned with the requirements specification.

设计活动大致分为逻辑设计和物理设计。逻辑设计描述系统将要做什么，而物理设计描述如何使用具体的硬件和软件来实现。两者都必须与需求规格说明书保持一致。

Logical design: data flows, entity relationships, processing rules

逻辑设计：数据流、实体关系、处理规则
Physical design: file structures, storage media, input/output formats

物理设计：文件结构、存储介质、输入/输出格式

2. Requirements Analysis | 需求分析

Before designing a system, it is essential to fully understand what stakeholders need. Requirements analysis involves collecting, clarifying, and documenting the functions and constraints of the proposed system. This is often performed through interviews, questionnaires, observation, and examination of existing documents.

在设计系统之前，必须充分理解相关方的需求。需求分析包括收集、澄清并记录拟建系统的功能和约束条件。通常通过访谈、问卷、观察和查阅现有文件来进行。

Requirements are usually divided into functional requirements and non-functional requirements. Functional requirements describe specific behaviours such as “the system must calculate the total price automatically”. Non-functional requirements define quality attributes such as response time, security, and usability.

需求通常分为功能需求和非功能需求。功能需求描述具体行为，例如“系统必须自动计算总价”。非功能需求定义质量属性，如响应时间、安全性和易用性。

The output of this stage is a requirements specification, which serves as a contract between the client and the developers. A clear specification prevents misunderstandings during later design and testing phases.

本阶段的输出是需求规格说明书，它作为客户与开发人员之间的契约。清晰的规格说明书可以避免在后续设计和测试阶段产生误解。

3. Feasibility Study | 可行性研究

A feasibility study evaluates whether a proposed system is practical and worthwhile before significant resources are invested. It typically considers technical feasibility, economic feasibility, operational feasibility, and legal feasibility.

可行性研究在投入大量资源之前评估拟建系统是否切实可行、是否值得实施。它通常考虑技术可行性、经济可行性、运行可行性和法律可行性。

Technical feasibility: whether the required hardware, software, and skills are available

技术可行性：所需硬件、软件和技能是否具备
Economic feasibility: whether the benefits outweigh the costs over the system’s lifetime

经济可行性：系统整个生命周期内收益是否大于成本
Operational feasibility: whether the system can be integrated into current working practices

运行可行性：系统能否融入当前工作流程
Legal and social feasibility: whether the system complies with data protection and accessibility laws

法律与社会可行性：系统是否符合数据保护和无障碍相关法律

The results are presented in a feasibility report. If the study is favourable, the project proceeds to detailed requirements analysis and design.

研究结果以可行性报告的形式呈现。如果结论有利，项目便进入详细的需求分析和设计阶段。

4. Designing Inputs and Outputs | 输入与输出的设计

Input design focuses on how data will be captured and entered into the system. Good input design reduces errors and speeds up data entry. Designers must decide on input devices, screen layouts, data entry forms, and validation rules that will be applied to each field.

输入设计关注数据如何被采集并输入系统。良好的输入设计能够减少错误并加快数据录入速度。设计人员必须决定输入设备、屏幕布局、数据录入表单以及应用于每个字段的验证规则。

Output design determines the content, format, and medium of information produced by the system. Outputs can be screen-based (online reports) or paper-based (printed invoices), and should be designed to suit their audience.

输出设计决定了系统所产生信息的内容、格式和媒介。输出可以是基于屏幕的（如在线报告），也可以是纸质的（如打印发票），其设计应当适应不同的受众。

Design principle: inputs and outputs should be clear, consistent, and matched to the user’s skill level.

设计原则：输入和输出应清晰、一致，并与用户的技能水平相匹配。

5. Data Design and Normalisation | 数据设计与规范化

Data design involves deciding how data will be organised, stored, and related. In a relational database, this includes choosing tables, fields, primary keys, and foreign keys. Proper data design reduces redundancy and prevents anomalies during insertion, update, and deletion.

数据设计涉及决定数据如何组织、存储和关联。在关系型数据库中，这包括选择表、字段、主键和外键。合理的数据设计能够减少冗余，并防止插入、更新和删除时出现异常。

Normalisation is a systematic process that eliminates duplicate data and ensures each fact is stored only once. The main stages are First Normal Form (1NF), Second Normal Form (2NF), and Third Normal Form (3NF).

规范化是一个消除重复数据、确保每个事实只存储一次的系统化过程。主要阶段包括第一范式（1NF）、第二范式（2NF）和第三范式（3NF）。

Normal form	Requirement	范式	要求
1NF	No repeating groups; each cell holds a single atomic value	第一范式	没有重复组；每个单元格保存单一原子值
2NF	In 1NF and all non-key attributes depend on the whole primary key	第二范式	满足1NF，且所有非键属性依赖整个主键
3NF	In 2NF and no transitive dependencies on the primary key	第三范式	满足2NF，且没有对主键的传递依赖

A data dictionary is often created during data design. It records the name, data type, size, validation rules, and purpose of every data item, ensuring consistency across the whole system.

数据设计阶段通常会创建数据字典。它记录每个数据项的名称、数据类型、大小、验证规则和用途，确保整个系统的一致性。

6. User Interface Design | 用户界面设计

The user interface (UI) is the part of the system that users interact with directly. A well-designed interface improves productivity and reduces training costs. Common interface types include command-line interfaces, graphical user interfaces, menu-driven interfaces, and form-based interfaces.

用户界面（UI）是用户直接交互的系统部分。设计良好的界面能够提高生产力并降低培训成本。常见的界面类型包括命令行界面、图形用户界面、菜单驱动界面和基于表单的界面。

Key principles of interface design include consistency, clear feedback, reducing the user’s memory load, and providing short cuts for experienced users. For example, buttons and menus should use consistent wording and placement across all screens.

界面设计的关键原则包括一致性、清晰的反馈、减轻用户记忆负担，以及为熟练用户提供快捷操作。例如，按钮和菜单在所有屏幕上应使用一致的措辞和位置。

Designers must also consider human-computer interaction (HCI) factors such as font size, colour contrast, and keyboard accessibility. Involving users in usability testing during the design phase can reveal serious design flaws before implementation begins.

设计人员还必须考虑人机交互（HCI）因素，如字号、颜色对比度和键盘无障碍操作。在设计阶段让用户参与可用性测试，可以在实施开始前发现严重的设计缺陷。

7. Validation and Verification | 验证与确认

Validation and verification are two different strategies used to reduce data entry errors. Validation checks whether data is reasonable and complies with predefined rules before it is accepted by the system. Verification checks whether data has been entered correctly by comparing two versions of the same data.

验证（Validation）和确认（Verification）是减少数据录入错误的两种不同策略。验证在数据被系统接受之前检查其是否合理并符合预定义规则。确认则通过比较同一数据的两个版本来检查输入是否正确。

Common validation checks include range checks, type checks, length checks, presence checks, format checks, and check digit calculations. For example, an age field might use a range check to reject values below 0 or above 120.

常见的验证检查包括范围检查、类型检查、长度检查、存在性检查、格式检查和校验位计算。例如，年龄字段可以使用范围检查来拒绝小于0或大于120的值。

Verification techniques include double entry, where a user types the data twice and the system compares the two entries, and visual proofreading, where the user checks the entered data against the original document on the screen.

确认技术包括双重输入——用户输入两次数据，系统比较两次输入；以及目视校对——用户将屏幕上输入的数据与原始文档进行核对。

8. Testing Strategies | 测试策略

Testing is essential to ensure that the system works correctly and meets its requirements. Test data is typically divided into normal data, boundary data, and erroneous data. Boundary data tests values at the extreme ends of an acceptable range, such as 0 and 100 for a percentage field.

测试对于确保系统正确运行并满足需求至关重要。测试数据通常分为正常数据、边界数据和错误数据。边界数据测试可接受范围两端的数据值，例如百分比字段中的0和100。

Testing is performed at several levels. Unit testing checks individual modules, integration testing checks interactions between modules, system testing checks the whole system, and acceptance testing is carried out by the client to confirm that the system meets the agreed requirements.

测试分多个层次进行。单元测试检查各模块，集成测试检查模块间的交互，系统测试检查整个系统，验收测试由客户执行以确认系统满足约定的需求。

A test plan identifies what will be tested, the test data to use, the expected outcomes, and the person responsible

测试计划确定要测试的内容、使用的测试数据、预期结果以及负责人
Test logs record actual outcomes so that discrepancies can be traced and fixed

测试日志记录实际结果，以便追踪并修复差异

A test strategy should be designed during the design stage, not deferred until after coding. Early planning of tests helps to clarify expected behaviour and makes the implementation phase more focused.

测试策略应在设计阶段就制定，而不是推迟到编码之后。提前规划测试有助于明确预期行为，使实施阶段更具针对性。

9. Documentation | 文档编写

Documentation is a vital part of the system design process because it supports future development, testing, and maintenance. Two main types of documentation are produced: user documentation and technical documentation.

文档是系统设计过程的重要组成部分，因为它支持后续的开发、测试和维护。主要产生两类文档：用户文档和技术文档。

User documentation explains how to operate the system. It includes installation guides, tutorials, step-by-step instructions, and frequently asked questions. Clear user documentation reduces the need for support and training.

用户文档说明如何操作系统，包括安装指南、教程、分步说明和常见问题解答。清晰的用户文档可以减少对支持和培训的需求。

Technical documentation describes the internal architecture of the system. It includes system architecture diagrams, algorithms, data structures, database schemas, and the requirements specification. This documentation is essential for programmers who will maintain the system later.

技术文档描述系统内部架构，包括系统架构图、算法、数据结构、数据库模式以及需求规格说明书。这类文档对于将来维护系统的程序员至关重要。

10. System Conversion | 系统转换

System conversion is the process of changing from the old system to the new one. The main conversion strategies are direct changeover, parallel running, pilot conversion, and phased conversion.

系统转换是从旧系统切换到新系统的过程。主要的转换策略包括直接切换、并行运行、试点转换和分阶段转换。

Strategy	Advantage	Disadvantage
Direct changeover 直接切换	Cheapest and quickest 最便宜、最快	High risk if the new system fails 新系统若失败则风险高
Parallel running 并行运行	Old and new run together, reducing risk 新旧并行，降低风险	Expensive and labour intensive 成本高、劳动强度大
Pilot conversion 试点转换	Live test in one location first 先在一个地点实际测试	May not suit all sites equally 可能不适用于所有地点
Phased conversion 分阶段转换	Modules are introduced gradually 模块逐步引入	Interfaces between phases must be handled 需处理阶段间的接口

Data conversion, including cleaning and transferring existing data, must also be planned. Backups and fallback procedures are essential so that the organisation can return to the old system if the new system encounters a serious fault.

数据转换（包括清理和迁移现有数据）也需要进行规划。备份和回退程序至关重要，以便在新系统遇到严重故障时组织可以回退到旧系统。

11. Maintenance and Evaluation | 维护与评估

After a system is installed, it enters the maintenance phase. Maintenance is often more expensive than the initial development, so design decisions made early — such as modular structure and clear documentation — directly affect long-term cost.

系统安装后进入维护阶段。维护的费用往往高于最初开发，因此早期做出的设计决策（如模块化结构和清晰的文档）会直接影响长期成本。

Maintenance can be corrective, to fix bugs; adaptive, to respond to changes in the environment; or perfective, to improve performance and add new features. A well-designed system is easier to adapt and extend.

维护可分为纠错性维护（修复错误）、适应性维护（响应环境变化）和完善性维护（改进性能并增加新功能）。设计良好的系统更容易调整和扩展。

Evaluation compares the completed system against the original acceptance criteria. Performance indicators such as response time, user satisfaction, reliability, and cost efficiency are measured. The results may lead to further iterations of the system life cycle.

评估将完成的系统与最初的验收标准进行比较。可测量响应时间、用户满意度、可靠性和成本效益等性能指标。评估结果可能导致系统生命周期的进一步迭代。

The key stages of system design form a structured framework that turns vague user ideas into a working, reliable computer system. A careful design process not only reduces development cost and risk but also creates systems that are secure, maintainable, and genuinely useful for their intended users.

系统设计的关键环节构成了一个结构化的框架，将用户模糊的想法转化为可运行、可靠的计算机系统。周到的设计过程不仅能降低开发成本和风险，还能创建安全、可维护且对目标用户真正有用的系统。

Published by TutorHao | Computer Science Revision Series | aleveler.com

更多咨询请联系16621398022（同微信）

A-Level Computer Science: Key Stages of System Design | A-Level 计算机：系统设计的关键环节