Operation and Project Management in Computer Science | 计算机科学中的运营与项目管理

📚 Operation and Project Management in Computer Science | 计算机科学中的运营与项目管理

In computing, ‘operations’ refers to the continuous, repetitive activities that keep systems, networks, databases and digital services running day to day. Common operational tasks include monitoring server performance, applying security patches, managing backups, responding to user support tickets, and controlling access rights. ‘Project management’ refers to the temporary, unique work carried out to create a new product, service or result within a defined start and end date. For example, developing a new mobile app, migrating a school network to cloud storage, or replacing a database system are all IT projects.

在计算领域中，“运营”是指让系统、网络、数据库和数字服务在日常运行中保持稳定的持续性、重复性活动。常见的运营任务包括监控服务器性能、安装安全补丁、管理备份、响应用户支持工单以及控制访问权限。“项目管理”则是指在明确的开始和结束日期内，为创造新产品、新服务或新成果而开展的临时性、独特性工作。例如，开发一款新的手机应用、将学校网络迁移到云存储，或更换数据库系统，都属于 IT 项目。

Cambridge A-Level Computer Science candidates meet both concepts in the syllabus. The systems development life cycle requires planning, execution and evaluation, while Paper 4 practical project work expects candidates to show evidence of project planning, time management, risk awareness and final evaluation. This article explains the key ideas of operation and project management with computing examples.

剑桥 A-Level 计算机科学考生在学习大纲中会同时接触这两个概念。系统开发生命周期要求进行规划、执行和评估，而 Paper 4 实践项目则要求考生展示项目规划、时间管理、风险意识和最终评估的证据。本文以计算领域的实例解释运营与项目管理的关键概念。

1. Operations vs Projects | 运营与项目的区别

Operations are ongoing and repetitive, aiming for stability and efficiency. A network administrator who monitors the same servers every day is carrying out operations. Projects are temporary and unique, aiming to deliver change. Building a new computer lab is a project because it has a defined end point and produces a new result. The two are closely linked: a successful project often changes how operations are performed.

运营是持续性和重复性的工作，目标是稳定和高效。网络管理员每天监控相同的服务器就是在执行运营工作。项目是临时性和独特性的工作，目标是交付变革。建设一个新的计算机实验室就是一个项目，因为它有明确的结束时间，并且会产生新的结果。两者密切相关：一个成功的项目通常会改变运营的执行方式。

Feature 特征	Operations 运营	Project 项目
Duration 持续时间	Ongoing, repetitive 持续性、重复性	Temporary, defined end 临时性、有明确终点
Output 输出	Stable service 稳定的服务	Unique product or change 独特产品或变更
Focus 目标	Efficiency and reliability 效率和可靠性	Achieving specific objectives 达成特定目标
Risk 风险	Usually lower, routine 通常较低、常规	Higher, uncertain 较高、不确定
Example in IT IT 实例	Managing a live server 管理在线服务器	Building a new website 建设新网站

2. Why Project Management Matters in Computing | 项目管理在计算中的重要性

IT projects frequently fail due to unclear requirements, poor planning, scope creep, resource shortages or weak communication. Project management provides a structured way to define objectives, allocate resources, monitor progress and control changes. In the Cambridge A-Level Computer Science course, students who plan their practical project carefully are more likely to produce a complete, testable system and an effective evaluation report.

IT 项目失败往往是因为需求不清晰、规划不善、范围蔓延、资源不足或沟通不畅。项目管理提供了一种结构化的方法，用来定义目标、分配资源、监控进展和控制变更。在剑桥 A-Level 计算机科学课程中，认真规划实践项目的学生更有可能完成一个可测试的系统，并写出有效的评估报告。

Clear scope prevents extra features from being added without control (明确的范围可以防止未经控制地增加额外功能)
Time plans help meet coursework deadlines (时间计划有助于满足课程作业截止日期)
Risk registers allow early action against technical problems (风险登记表允许针对技术问题提前采取行动)
Evaluation compares final outcomes with original objectives (评估将最终结果与最初目标进行比较)

3. Project Lifecycle in Software Development | 软件开发中的项目生命周期

A project lifecycle breaks work into phases. In computing, a common lifecycle is: initiation, planning, execution, monitoring and control, and closure. At initiation, the project idea is outlined and feasibility is checked. Planning defines tasks, time, cost, quality and risk. Execution builds the software or system. Monitoring and control track progress against the plan. Closure delivers the final product, documents lessons learned and releases resources.

项目生命周期将工作分为多个阶段。在计算领域中，常见的生命周期包括：启动、规划、执行、监控与控制、收尾。在启动阶段，概述项目想法并检查可行性。规划阶段定义任务、时间、成本、质量和风险。执行阶段构建软件或系统。监控与控制阶段对照计划跟踪进展。收尾阶段交付最终产品、记录经验教训并释放资源。

In software development, two broad models are often compared. The waterfall model follows linear phases such as requirements, design, implementation, testing and maintenance. Agile methods use short iterations, frequent feedback and adaptive planning. For A-Level coursework, a simplified waterfall or an iterative approach can both be valid, but the choice must be justified in the report.

在软件开发中，常常比较两种主要模型。瀑布模型遵循线性阶段，如需求、设计、实现、测试和维护。敏捷方法使用短迭代、频繁反馈和自适应规划。对于 A-Level 课程作业，简化的瀑布模型或迭代方法都可行，但必须在报告中对选择加以论证。

4. Planning Tools: Gantt Charts and Critical Path Analysis | 规划工具：甘特图与关键路径分析

A Gantt chart displays tasks on a horizontal timeline. Each task is shown as a bar from its start date to its finish date. Gantt charts are useful for visualising project schedules, seeing overlapping tasks and tracking whether the project is on time. For example, a student project might show analysis, design, coding, testing and documentation as separate bars, with some bars overlapping where testing runs alongside documentation.

甘特图在水平时间轴上显示任务。每个任务用一条从开始日期到结束日期的横条表示。甘特图有助于直观展示项目进度、查看重叠任务并跟踪项目是否按时完成。例如，学生项目可以将分析、设计、编码、测试和文档分别显示为不同的横条，其中测试和文档可部分重叠。

Critical path analysis (CPA) uses a network diagram to show task dependencies. The critical path is the longest sequence of dependent tasks that determines the shortest possible project duration. Any delay on the critical path delays the whole project. Tasks with spare time are said to have float. Understanding the critical path helps a project manager know where delays matter most.

关键路径分析使用网络图显示任务之间的依赖关系。关键路径是决定项目最短可能工期的、由相互依赖任务组成的最长路径。关键路径上的任何延误都会延误整个项目。有富余时间的任务称为具有浮动时间。了解关键路径有助于项目经理判断哪些延误影响最大。

5. Time Management and Network Calculations | 时间管理与网络计算

In critical path analysis, the earliest start time (EST) is the soonest a task can begin. The latest finish time (LFT) is the latest a task can finish without delaying the project. Total float is the amount of time a task can be delayed without affecting the project end date. If a task has zero float, it is critical.

在关键路径分析中，最早开始时间是指任务可以开始的最早时间。最晚完成时间是指任务在不延误项目的前提下可以完成的最晚时间。总浮动时间是指任务可以延误而不影响项目结束日期的最大时间量。如果任务的浮动时间为零，它就是关键任务。

Total float = LFT − duration − EST

For estimation, the PERT (Programme Evaluation and Review Technique) formula uses three time estimates: optimistic (O), most likely (M) and pessimistic (P). The expected duration is a weighted average that gives more importance to the most likely estimate. This reduces the risk of relying on only one guess.

在进行估算时，PERT（计划评审技术）公式使用三个时间估计值：乐观时间、最可能时间和悲观时间。期望工期是一种加权平均值，更重视最可能的估计值。这样可以降低仅依赖单一猜测所带来的风险。

Expected time = (O + 4M + P) ÷ 6

6. Risk Management in IT Projects | IT 项目中的风险管理

Risk management identifies what could go wrong, assesses how likely it is and how serious the impact would be, and then plans responses. In computing projects, risks include hardware failure, data loss, software bugs, security vulnerabilities, changing requirements and team illness. A simple risk register lists each risk, likelihood, impact, owner and planned response.

风险管理要识别可能出现的问题，评估其发生概率和影响严重程度，然后规划应对措施。在计算项目中，风险包括硬件故障、数据丢失、软件缺陷、安全漏洞、需求变更和团队成员生病。简单的风险登记表会列出每个风险、发生概率、影响、负责人和计划应对措施。

Common risk responses are avoid, transfer, mitigate and accept. Avoidance removes the risk by changing plans. Transfer shifts the risk to another party, such as using cloud backup. Mitigation reduces likelihood or impact, such as regular testing. Acceptance is used when the risk is small or the cost of response is too high.

常见的风险应对策略包括规避、转移、减轻和接受。规避通过改变计划来消除风险。转移将风险交给另一方，例如使用云备份。减轻降低风险发生的可能性或影响，例如进行定期测试。当风险较小或应对成本过高时，则采用接受策略。

7. Resource and Cost Estimation | 资源与成本估算

Resources in an IT project include people, time, hardware, software licences, network access and physical space. Accurate estimation helps ensure that a project is feasible and that enough resources are available when needed. Poor estimation can lead to over-budget projects, missed deadlines or incomplete deliverables.

IT 项目中的资源包括人员、时间、硬件、软件许可证、网络访问和物理空间。准确的估算有助于确保项目可行，并在需要时提供足够的资源。估算不佳可能导致项目超支、错过截止日期或交付物不完整。

Estimation techniques include bottom-up estimation, where each small task is estimated and then totals are added; analogous estimation, which uses similar past projects as a basis; and parametric estimation, which uses a mathematical model. A simple cost formula can combine fixed setup costs with variable costs per unit.

估算技术包括自下而上估算，即对每个小任务进行估算后相加；类比估算，即使用类似的过去项目作为基础；以及参数估算，即使用数学模型。一个简单的成本公式可以结合固定设置成本和每单位可变成本。

Total cost = fixed cost + (unit cost × quantity)

8. Operational Management of Computer Systems | 计算机系统的运营管理

Operational management in computing focuses on keeping services available, secure and performant. Core activities include monitoring systems for faults, applying patches, managing user accounts, taking backups, controlling access and responding to incidents. An operations team often works with a service desk to handle user-reported issues.

计算领域的运营管理侧重于保持服务的可用性、安全性和性能。核心活动包括监控系统故障、安装补丁、管理用户账户、执行备份、控制访问以及响应事件。运营团队通常与服务台合作，处理用户报告的问题。

Key performance indicators for operations include uptime, mean time between failures (MTBF) and mean time to repair (MTTR). Availability is often expressed as a percentage. A system that is down for a long time has lower availability, so operations teams aim to reduce downtime through redundancy, monitoring and quick recovery.

运营的关键绩效指标包括正常运行时间、平均故障间隔时间和平均修复时间。可用性通常用百分比表示。系统停机时间越长，可用性越低，因此运营团队通过冗余、监控和快速恢复来减少停机时间。

Availability = uptime ÷ (uptime + downtime) × 100%

9. Service Level Agreements and Capacity Planning | 服务级别协议与容量规划

A service level agreement (SLA) is a formal commitment between a service provider and its users. It defines expected uptime, response times, support hours and performance targets. For example, a cloud provider may promise 99.9% availability, meaning about 8.76 hours of downtime per year is allowed. Recovery time objective (RTO) specifies how quickly a service must be restored after failure, while recovery point objective (RPO) specifies how much data loss is acceptable.

服务级别协议是服务提供者与用户之间的正式承诺。它规定了预期的正常运行时间、响应时间、支持时间和性能目标。例如，云服务提供商可能承诺 99.9% 的可用性，这意味着一年的允许停机时间约为 8.76 小时。恢复时间目标规定了故障后必须多快恢复服务，恢复点目标则规定了可接受的数据丢失量。

Capacity planning ensures that the computing resources can meet current and future demand. It involves monitoring CPU, memory, storage, network bandwidth and database size. If demand grows faster than capacity, performance degrades and users experience slow responses or failures. Capacity planning helps operations teams decide when to add servers, upgrade storage or optimise software.

容量规划确保计算资源能够满足当前和未来的需求。它涉及监控 CPU、内存、存储、网络带宽和数据库大小。如果需求增长速度超过容量增长速度，性能就会下降，用户会感到响应缓慢或发生故障。容量规划帮助运营团队决定何时增加服务器、升级存储或优化软件。

10. Incident, Change and Problem Management | 事件、变更与问题管理

IT operational frameworks often separate incident management, problem management and change management. Incident management restores normal service as quickly as possible when a fault occurs, such as rebooting a crashed server or resetting a password. Problem management investigates the root cause of repeated incidents to prevent them from happening again.

IT 运营框架通常将事件管理、问题管理和变更管理分开。事件管理在故障发生时尽快恢复正常服务，例如重启崩溃的服务器或重置密码。问题管理调查重复事件的根本原因，以防止其再次发生。

Change management controls modifications to IT systems. Every change, such as installing a new software version or altering firewall rules, should be logged, tested and approved before implementation. This reduces the risk that a well-intentioned change causes a major outage. For example, a failed patch roll-out can be rolled back if proper change control is used.

变更管理控制对 IT 系统的修改。每一次变更，例如安装新软件版本或修改防火墙规则，都应在实施前进行记录、测试和批准。这可以降低善意变更引发重大中断的风险。例如，如果使用了正确的变更控制，失败的补丁部署可以回滚。

11. Monitoring, Evaluation and Quality Assurance | 监控、评估与质量保证

Monitoring uses system logs, dashboards and alerts to observe performance in real time. It can detect high CPU usage, failed login attempts, disk space shortages or unusual network traffic. Effective monitoring allows operations staff to react before small problems become service outages. In a project, monitoring compares actual progress with the plan, using tools such as Gantt charts or meeting notes.

监控使用系统日志、仪表板和警报来实时观察性能。它可以检测到 CPU 使用率过高、登录尝试失败、磁盘空间不足或网络流量异常。有效的监控使运营人员能够在问题扩大为服务中断之前做出反应。在项目中，监控通过甘特图或会议记录等工具将实际进展与计划进行比较。

Evaluation occurs after a project is delivered. It asks whether the objectives were met, whether the product works as intended, and what could be improved next time. Quality assurance focuses on processes to prevent defects, while quality control checks outputs. In software, testing is a form of quality control: unit tests check individual modules, integration tests check module interactions, and acceptance tests check whether the system meets user needs.

评估在项目交付后进行。它要回答目标是否达成、产品是否按预期工作、以及下次可以改进什么。质量保证侧重于通过流程预防缺陷，而质量控制则检查输出结果。在软件中，测试是一种质量控制形式：单元测试检查单个模块，集成测试检查模块之间的交互，验收测试检查系统是否满足用户需求。

12. Conclusion and Exam Tips | 结论与考试建议

Operation and project management are two related but distinct disciplines in computing. Operations keep existing systems running, while projects deliver change. Cambridge A-Level Computer Science candidates should be able to compare these concepts and apply project management tools to their own practical work. A well-managed project shows planning, risk awareness, monitoring and evaluation.

运营与项目管理是计算领域中两个相关但不同的学科。运营保持现有系统运行，而项目交付变革。剑桥 A-Level 计算机科学考生应能够比较这些概念，并将项目管理工具应用在自己的实践工作中。一个管理良好的项目应展示规划、风险意识、监控和评估。

For exams, be ready to explain Gantt charts and critical path analysis, calculate float or expected time, describe the stages of a project lifecycle, and discuss operational measures such as availability, SLA, RTO and RPO. In Paper 4 coursework, include a project plan, risk assessment and a clear evaluation against original objectives. Use specific examples from your own computing project to support your answers.

在考试中，要准备好解释甘特图和关键路径分析，计算浮动时间或期望工期，描述项目生命周期的阶段，并讨论可用性、SLA、RTO 和 RPO 等运营指标。在 Paper 4 课程作业中，应包括项目计划、风险评估和对照最初目标的清晰评估。使用自己计算项目中的具体实例来支持答案。

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

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

Operation and Project Management in Computer Science | 计算机科学中的运营与项目管理