Chapter 6 Software Engineering 6.1.1 The Cycle as a whole The Traditional Development Phase Analysis The development phase of the software life cycle begins with analysis--a major goal being to identify the needs of the user of the proposed system. If the system is to be a generic product sold in a competitive market, this analysis would involve a broad-based investigation to identify the needs of potential customers. If, however, the system is to be designed for a specific user, then the process would be a more narrow investigation 分析软件生命周期的开发阶段以分析开始——主要目标是确定用户对所 提出系统的需求。如果系统是一个在竞争的市场上销售的通用产品,这个 分析将会包括一个广泛的调查来发现潜在用户的需要。但是,如果系统是 为特殊用户设计的,那么这个过程就是一个更专业的调查。 计算机专业英语 SG6
Chapter 6 Software Engineering 计算机专业英语 6-11 6.1.1 The Cycle as a Whole The Traditional Development Phase Analysis The development phase of the software life cycle begins with analysis--a major goal being to identify the needs of the user of the proposed system. If the system is to be a generic product sold in a competitive market, this analysis would involve a broad-based investigation to identify the needs of potential customers. If, however, the system is to be designed for a specific user, then the process would be a more narrow investigation. 分析 软件生命周期的开发阶段以分析开始——主要目标是确定用户对所 提出系统的需求。如果系统是一个在竞争的市场上销售的通用产品，这个 分析将会包括一个广泛的调查来发现潜在用户的需要。但是，如果系统是 为特殊用户设计的，那么这个过程就是一个更专业的调查
Chapter 6 Software Engineering 6.1.1 The Cycle as a whole The Traditional Development Phase As the needs of the potential user are identified, they are com piled to form a set of requirements that the new system must satisfy These requirements are stated in terms of the application rather than in the technical terminology of the data processing community. One requirement might be that access to data must be restricted to authorized personnel. Another might be that the data must reflect the current state of the inventory as of the end of the last business day or that the arrangement of the data as displayed on the com puterscreen must adhere to the format of the paper forms currently in use. 当潜在用户的要求被确定之后,要将这些要求汇编成新系统必须满足的需 求。这些需求是从应用的角度来表述,而不是用数据处理界的技术术语来 表达。一种需求可能是对数据的存取必须限制在有权限的人员,另一种可 能是当一个工作日结束时,数据必须反映目前的清单状态,或者可能是在 计算机屏幕上的数据必须按照用户目前使用的格式来显示。 计算机专业英语 6-12
Chapter 6 Software Engineering 计算机专业英语 6-12 6.1.1 The Cycle as a Whole The Traditional Development Phase As the needs of the potential user are identified, they are compiled to form a set of requirements that the new system must satisfy. These requirements are stated in terms of the application rather than in the technical terminology of the data processing community. One requirement might be that access to data must be restricted to authorized personnel. Another might be that the data must reflect the current state of the inventory as of the end of the last business day or that the arrangement of the data as displayed on the computer screen must adhere to the format of the paper forms currently in use. 当潜在用户的要求被确定之后，要将这些要求汇编成新系统必须满足的需 求。这些需求是从应用的角度来表述，而不是用数据处理界的技术术语来 表达。一种需求可能是对数据的存取必须限制在有权限的人员，另一种可 能是当一个工作日结束时，数据必须反映目前的清单状态，或者可能是在 计算机屏幕上的数据必须按照用户目前使用的格式来显示
Chapter 6 Software Engineering 6.1.1 The Cycle as a whole The Traditional Development Phase After the system requirements are identified, they are converted into more technical system specifications. For example, the requirement that data be restricted to authorized personnel might become the specification that the system will not respond until an approved eight digit password has been typed at the keyboard or that data will be displayed in encrypted form unless preprocessed by a routine known only to authorized personne 系统的需求被确定以后,它们就转化为更具技术性的说明书。例如,关于 数据须限制在某些有权限的人的需求,就可能转化为以下规范直到从 键盘输入一个被认可的8位密码,系统才开始响应,或者除非经过只有授 权的人才知道的例程预处理,否则数据将以加密的形式显示在屏幕上。 计算机专业英语 6-13
Chapter 6 Software Engineering 计算机专业英语 6-13 6.1.1 The Cycle as a Whole The Traditional Development Phase After the system requirements are identified, they are converted into more technical system specifications. For example, the requirement that data be restricted to authorized personnel might become the specification that the system will not respond until an approved eightdigit password has been typed at the keyboard or that data will be displayed in encrypted form unless preprocessed by a routine known only to authorized personnel. 系统的需求被确定以后，它们就转化为更具技术性的说明书。例如，关于 数据须限制在某些有权限的人的需求，就可能转化为以下规范——直到从 键盘输入一个被认可的8位密码，系统才开始响应，或者除非经过只有授 权的人才知道的例程预处理，否则数据将以加密的形式显示在屏幕上
Chapter 6 Software Engineering 6.1.1 The Cycle as a whole The Traditional Development Phase Design Whereas analysis concentrates on what the proposed system should do, design concentrates on how the system will accomplish those goals. It is here that the structure of the software system is established 设计分析关注这个系统应该做什么,而设计关注这个系统应 该怎样来实现目标。正是通过设计建立了软件系统的结构 计算机专业英语 6-14
Chapter 6 Software Engineering 计算机专业英语 6-14 6.1.1 The Cycle as a Whole The Traditional Development Phase Design Whereas analysis concentrates on what the proposed system should do, design concentrates on how the system will accomplish those goals. It is here that the structure of the software system is established. 设计 分析关注这个系统应该做什么，而设计关注这个系统应 该怎样来实现目标。正是通过设计建立了软件系统的结构
Chapter 6 Software Engineering 6.1.1 The Cycle as a whole The Traditional Development Phase It is a well-established principle that the best structure for a large software system is a modular one. Indeed it is by means of this modular decomposition that the implementation of large systems becomes a possibility Without such a breakdown the technical details required in the implementation of a large system would exceed a human's comprehensive powers 大型软件系统最好的结构是模块化系统,这是一条被充分证实 的原则。确实,正是借助模块化的分解方法,大型系统的实现 才成为可能。没有这样的分解,在大型系统实现过程中所需要 的技术细节可能会超过一个人的理解能力。 计算机专业英语 6-15
Chapter 6 Software Engineering 计算机专业英语 6-15 6.1.1 The Cycle as a Whole The Traditional Development Phase It is a well-established principle that the best structure for a large software system is a modular one. Indeed, it is by means of this modular decomposition that the implementation of large systems becomes a possibility. Without such a breakdown, the technical details required in the implementation of a large system would exceed a human's comprehensive powers. 大型软件系统最好的结构是模块化系统，这是一条被充分证实 的原则。确实，正是借助模块化的分解方法，大型系统的实现 才成为可能。没有这样的分解，在大型系统实现过程中所需要 的技术细节可能会超过一个人的理解能力