📚 People in Organisations: Roles and Impact in Computing | 组织中的人：计算中的角色与影响
Computing is often perceived as a purely technical discipline, yet the success of any software or hardware solution depends heavily on the people within the organisations that conceive, build, and use these systems. From top-level executives to end users, each individual plays a distinct role that shapes how technology is designed, deployed, and maintained. This article explores the key human roles in computing-related organisations, examining their responsibilities, interactions, and the impact they have on project outcomes.
计算常常被视为纯粹的技术学科，但任何软硬件解决方案的成功在很大程度上取决于构思、构建和使用这些系统的组织中的人员。从高层管理者到最终用户，每个人都扮演着独特的角色，影响着技术的设计、部署和维护方式。本文探讨了与计算相关的组织中的关键人员角色，分析他们的职责、互动以及对项目成果的影响。
1. Introduction to People in Computing Organisations | 计算组织中的人员概述
A computing organisation is a structured group of individuals who collaborate to achieve common goals related to information technology. These goals may include developing software, managing networks, providing IT services, or using computing systems to support business functions. People in such organisations can be broadly categorised into technical and non-technical roles, each contributing to the successful integration of technology and human activity.
计算组织是一个结构化的群体，成员们共同协作以实现与信息技术相关的共同目标。这些目标可能包括开发软件、管理网络、提供IT服务，或使用计算机系统支持业务功能。这类组织中的人员大致可分为技术类和非技术类角色，每个角色都为技术与人类活动的成功融合做出贡献。
Understanding the human side of computing is essential for A-Level students because it highlights why communication, project management, and user-centred design are just as critical as coding skills. Organisations that neglect the people factor often face project delays, budget overruns, or systems that fail to meet user needs.
理解计算中的人的因素对于A-Level学生至关重要，因为它揭示了为何沟通、项目管理和以用户为中心的设计与编程技能同样关键。忽视人员因素的组织常常遭遇项目延误、预算超支或系统无法满足用户需求的情况。
2. System Stakeholders and Users | 系统利益相关者与用户
A stakeholder is any person or group who has an interest in or may be affected by a computing project. Stakeholders include not only the direct users but also managers, customers, regulatory bodies, and even the public. Identifying all stakeholders early helps to capture requirements accurately and avoid conflicts later in the development cycle.
利益相关者是指任何对计算项目感兴趣或可能受其影响的个人或群体。利益相关者不仅包括直接用户，还包括管理者、客户、监管机构乃至公众。尽早识别所有利益相关者有助于准确捕获需求，避免在开发后期出现冲突。
Users are a subset of stakeholders who interact directly with the system to accomplish tasks. They can range from expert technical staff to members of the public with minimal digital literacy. Designing a system without a clear profile of the intended user often leads to poor usability and rejection of the technology.
用户是直接与系统交互以完成任务的一部分利益相关者。他们可能是专业的技术人员，也可能是数字素养微弱的公众成员。在没有明确目标用户画像的情况下设计系统，常会导致可用性差和技术被拒绝使用。
| Stakeholder / 利益相关者 | Typical Concern / 典型关切 |
|---|---|
| End-user | Ease of use, efficiency, error tolerance |
| Project sponsor | Return on investment, alignment with business goals |
| Regulator | Compliance with data protection and security laws |
| Developer | Clear specifications, manageable technical complexity |
3. The Role of the Systems Analyst | 系统分析师的角色
The systems analyst acts as a bridge between the business side and the technical team. Their primary responsibility is to investigate an organisation's current processes, identify problems and opportunities, and define the requirements for a new or improved information system. They employ techniques such as interviews, questionnaires, observation, and document analysis to gather information.
系统分析师充当业务方与技术团队之间的桥梁。他们的主要职责是调查组织的现有流程，识别问题与机会，并定义新系统或改进系统的需求。他们采用访谈、问卷调查、观察和文档分析等技术来收集信息。
Once requirements are gathered, the analyst documents them using tools like data flow diagrams (DFDs), entity-relationship diagrams, and structured English. This documentation must be precise enough for developers to implement yet accessible for stakeholders to validate. The analyst's ability to translate user needs into functional and non-functional requirements directly influences project success.
一旦收集到需求，分析师会使用数据流图、实体关系图和结构化英语等工具进行文档化。这些文档既要足够精确以供开发人员实现，又要易于理解以便利益相关者验证。分析师将用户需求转化为功能和非功能需求的能力直接影响项目成败。
4. The Role of the Project Manager | 项目经理的角色
The project manager (PM) is responsible for planning, executing, and closing a computing project while balancing the triple constraint of scope, time, and cost. The PM defines milestones, allocates resources, and monitors progress using tools such as Gantt charts and critical path analysis. Effective risk management is also a core duty, as unanticipated problems can derail even well-designed projects.
项目经理负责规划、执行和收尾计算项目，同时平衡范围、时间和成本这三重约束。项目经理定义里程碑、分配资源，并使用甘特图和关键路径分析等工具监控进展。有效的风险管理也是一项核心职责，因为意外问题可能使精心设计的项目脱轨。
Leadership and communication skills are vital for a PM. They must coordinate between cross-functional teams, resolve interpersonal conflicts, and keep senior management informed. In agile environments, the PM's role may be replaced by a scrum master or product owner, but the fundamental need for coordination and accountability remains.
领导力和沟通能力对项目经理至关重要。他们必须协调跨职能团队，解决人际冲突，并向高层管理汇报。在敏捷环境中，项目经理的角色可能被敏捷教练或产品负责人替代，但对协调和问责的基本需求依然存在。
5. The Role of the Programmer/Developer | 程序员/开发者的角色
Programmers are the individuals who write, test, and maintain the source code of a software system. They take the design specifications produced by the analyst and translate them into working programs using appropriate programming languages and development environments. A professional developer follows coding standards, conducts unit testing, and participates in code reviews to ensure quality.
程序员是编写、测试和维护软件系统源代码的人。他们根据分析师提供的设计规范，使用合适的编程语言和开发环境将其转化为可运行的程序。专业开发者遵循编码标准，进行单元测试，并参与代码评审以确保质量。
Modern programmers often work within a version control system, contribute to shared code repositories, and collaborate in cross-functional teams. Soft skills such as attention to detail, logical thinking, and the ability to give and receive constructive feedback are just as important as technical expertise.
现代程序员通常在版本控制系统中工作，为共享代码仓库做贡献，并在跨职能团队中协作。注重细节、逻辑思维以及给予和接受建设性反馈等软技能与技术知识同等重要。
6. Support and Technical Staff | 支持与技术人员
Beyond development, a computing organisation relies on support staff such as database administrators, network engineers, security analysts, and help-desk technicians. These professionals ensure that systems remain operational, data is secure, and users receive prompt assistance when issues arise. Their work often goes unnoticed until a failure occurs, making proactive maintenance essential.
除开发工作外，计算组织还依赖于数据库管理员、网络工程师、安全分析师和帮助台技术人员等支持人员。这些专业人员确保系统持续运行、数据安全，并在问题出现时为用户提供及时帮助。他们的工作往往在出现故障时才会引起注意，因此主动维护至关重要。
The help-desk, in particular, serves as a direct point of contact for end users. Technicians who can communicate complex solutions in simple terms greatly enhance user satisfaction and reduce system downtime. Training end users is another function often carried out by technical support staff.
尤其是帮助台，是最终用户的直接联系点。能用简单语言解释复杂解决方案的技术人员能极大提升用户满意度并减少系统停机时间。培训最终用户也是技术支持人员经常承担的另一项职能。
7. End-User Engagement and Feedback | 最终用户的参与与反馈
End users are the ultimate judges of a system's usability and effectiveness. Involving them throughout the development lifecycle – from requirements elicitation to user acceptance testing – drastically reduces the risk of building the wrong product. Techniques such as prototyping, usability testing, and beta releases allow users to provide early feedback that can be fed back into the design process.
最终用户是系统可用性和有效性的最终评判者。在开发生命周期的各个阶段（从需求获取到用户验收测试）让用户参与进来，可大幅降低开发错误产品的风险。原型设计、可用性测试和Beta发布等技术使用户能提供早期反馈，并将这些反馈融入设计过程。
User resistance is a common reason for system failure. People naturally dislike change, especially when they are not consulted or trained properly. Effective change management, including clear communication of benefits and comprehensive training programs, helps to smooth the transition to new systems.
用户抵制是系统失败的常见原因。人们天生不喜欢变化，尤其是在没有充分征询意见或得到妥善培训的情况下。有效的变更管理，包括清晰传达好处和制定全面的培训计划，有助于平稳过渡到新系统。
8. Team Dynamics and Communication | 团队动态与沟通
Computing projects are rarely completed by individuals working in isolation. Teams bring together diverse skills, but they also introduce challenges such as groupthink, conflict, and coordination overhead. Recognising different team development stages – forming, storming, norming, and performing – helps managers address issues before they become critical.
计算项目很少由单独工作的个人完成。团队汇聚了多样化的技能，但也带来了诸如群体思维、冲突和协调成本等挑战。认识到团队发展的不同阶段——形成期、震荡期、规范期和成熟期，有助于管理者在问题变得严重之前加以解决。
Clear communication channels and regular meetings prevent misunderstandings. Stand-ups in agile projects, for example, keep everyone informed of progress and blockers. Tools like shared documentation and instant messaging platforms support asynchronous collaboration, but they cannot replace the human elements of empathy and active listening that are necessary for a healthy team environment.
清晰的沟通渠道和定期会议可以防止误解。例如，敏捷项目中的站立会议让每个人都能了解进展和障碍。共享文档和即时消息平台等工具支持异步协作，但它们不能取代健康团队环境所必需的共情和积极倾听等人为因素。
9. Ethical and Legal Considerations | 伦理与法律考量
People in computing organisations must navigate a complex landscape of ethical and legal obligations. Data protection laws, such as the GDPR, impose strict rules on how personal data may be collected, stored, and processed. Computer professionals have a duty to respect user privacy and to design systems that minimise data collection by default.
计算组织中的人员必须在复杂的伦理与法律义务中寻找方向。数据保护法（如GDPR）对个人数据的收集、存储和处理方式施加了严格规定。计算机专业人员有责任尊重用户隐私，并设计默认最小化数据收集的系统。
Beyond legal compliance, ethical behaviour includes honesty about system limitations, fairness in algorithmic decisions, and accountability for one's code. Professional bodies like the BCS and IEEE publish codes of conduct that guide members to place public interest above personal or corporate gain.
除法律合规外，伦理行为还包括诚实说明系统局限性、算法决策的公平性以及对自身代码的责任心。BCS和IEEE等专业机构发布的行为准则指导其成员将公共利益置于个人或企业利益之上。
10. Impact of Organisational Structure | 组织结构的影响
The way an organisation is arranged – hierarchical, flat, matrix, or networked – significantly influences how computing projects are initiated and managed. In a rigid hierarchy, decisions may be slow and developers may have little direct contact with users. A flatter structure can encourage innovation but may lack clear accountability.
组织的架构方式——层级式、扁平式、矩阵式或网络式——显著影响计算项目的启动和管理方式。在严格的层级结构中，决策可能缓慢，且开发人员与用户直接接触的机会很少。扁平结构可以鼓励创新，但可能缺乏明确的问责制。
Matrix organisations, where individuals report to both a functional manager and a project manager, are common in IT firms. They provide flexibility but require excellent communication to prevent conflicting priorities. Understanding organisational structure helps computing professionals navigate internal politics and deliver value more effectively.
矩阵组织在IT公司中很常见，员工需同时向职能经理和项目经理汇报。这种结构提供了灵活性，但需要出色的沟通来防止优先级冲突。理解组织结构有助于计算机专业人员应对办公室政治，更有效地交付价值。
11. People in Agile and Traditional Environments | 敏捷与传统环境中的人员
Traditional methodologies such as the waterfall model emphasise upfront planning, documentation, and sign-offs. In these settings, roles are well-defined and changes are difficult to accommodate once the project is underway. People interact through formal meetings and paperwork, which can create distance between developers and users.
传统的瀑布式方法强调前期规划、文档和签字确认。在这种情况下，角色定义明确，项目一旦启动就很难容纳变更。人员通过正式会议和文书工作互动，这可能造成开发人员与用户之间的隔阂。
Agile approaches prioritise individuals and interactions over processes and tools. Daily stand-ups, pair programming, and iterative feedback loops require team members to communicate constantly and to adapt quickly. These environments demand a higher degree of personal accountability, shared ownership, and trust among all participants.
敏捷方法则优先考虑个体和互动，而非流程和工具。每日站立会议、结对编程和迭代反馈循环要求团队成员持续沟通并快速适应。这样的环境要求更高程度的个人责任感、共享所有权以及所有参与者之间的信任。
12. Conclusion: People as the Core of Computing | 结论：人是计算的核心
Technology may be built from code and circuits, but it is shaped by human vision, collaboration, and decision-making. Every computing professional – from systems analyst to support technician – contributes to the socio-technical system that delivers value to users. Recognising the importance of people in organisations enables students to approach computing with greater empathy, ethical awareness, and professional maturity.
技术或许由代码和电路构建，但它是由人类的愿景、协作和决策塑造的。每一位计算专业人员——从系统分析师到支持技师——都在为向用户递价值的社会技术系统做出贡献。认识到组织中人的重要性，能使学生以更强的同理心、伦理意识和职业成熟度来学习计算。
For A-Level candidates, mastering the technical syllabus is necessary but not sufficient. The ability to understand and work within the human context of computing will ultimately distinguish successful professionals in an ever-evolving digital world.
对于A-Level考生而言，掌握技术大纲固然必要，但还不够。理解计算领域的人力环境并能在其中有效工作，最终将是在不断发展的数字世界中脱颖而出的关键。
Published by TutorHao | Computer Science Revision Series | aleveler.com
更多咨询请联系16621398022（同微信）
或截图后用「扫一扫 → 相册」选择本图