Glossary
Copyright © 2015 University of Alberta.
Word | Definition |
---|---|
Ad Hoc Development | Developing software reactively, without a plan. |
Agile | A philosophy for developing software that is based on the values and principles of the Manifesto for Agile Software Development. |
Analyze | Examine methodically and in detail to discover insights or potential improvements. |
Change Friendly | A product that is easily adaptable to change. |
Design and Implementation Phase | The phase of a software process where you design the organization of the software and implement that design. |
Managed | That processes and practices are followed to organize the work of everyone involved in the software project. |
Monitoring | The tracking of a project’s progress and the product’s quality. |
Planning | The preparatory work to define tasks and schedules to take software requirements through development activities to a software solution. |
Process | An organization of the development of software into distinct phases or stages. |
Requirement | A condition or capability that must be implemented in a product based on your client’s request. |
Review | To reflect on something and determine what was good and what can be improved upon. |
Risk Plan | A course of action that outlines the solution if an issue should occur. Also known as an action plan. |
Scrum | An iterative and incremental Agile methodology for managing product development. |
Specification Phase | The phase of a software process where the idea for the product is conceived and also where you define what the product should do. |
Validated | That the released software product satisfies the client. |
Velocity | The units of work that can be completed over a given time interval. |
Verified | That the released software product meets all the specified requirements. |
Verification and Validation Phase | The phase of a software process where you are testing whether requirements are met and reviewing whether the product satisfies the client. |
Waterfall Model | A software development process, typified by a linear arrangement of phases. |
中文术语
以下内容为本人自译,若有纰漏,还请多多指正。
中文 | 释义 |
---|---|
临时开发 | 无计划地被动开发软件。 |
敏捷 | 基于敏捷软件开发宣言的价值观和原则的软件开发哲学。 |
分析 | 有条不紊地进行详细检查,以发现更多见解或潜在的改进。 |
改变友善 | 易于适应变化的产品。 |
设计和实施阶段 | 软件过程的阶段,您可以在其中设计软件的组织并实施该设计。 |
管理 | 组织参与软件项目的每个人的工作所遵循的过程和实践。 |
监控 | 跟踪项目的进度和产品的质量。 |
规划 | 定义任务和时间表的准备工作,以通过开发活动将软件需求化为软件解决方案。 |
流程 | 将软件开发分为不同阶段的组织构架。 |
需求 | 必须根据用户需求在产品中实现的条件或功能。 |
复盘 | 反思某件事,确定什么是好的,哪些可以改进。 |
风险计划 | 面临突发问题,概述解决方案的操作过程。也称为行动计划。 |
Scrum(橄榄球运动中争球的意思) | 一种敏捷软件开发的方法学,用于迭代式增量软件开发过程。 |
规范阶段 | 在软件搭建过程中构思产品的概念,并在其中定义产品应执行的操作。 |
已验证 | 发行的软件产品满足用户需求。 |
速度 | 在给定时间间隔内可以完成的工作单位。 |
已确认 | 发行的软件产品符合所有指定要求。 |
验证和确认阶段 | 测试产品是否满足要求,检查用户是否满意的过程阶段。 |
瀑布模型 | 一个软件开发过程,以阶段的线性排列为代表。 |