In 1985, we were looking at many different ways to define a problem by writing good requirements, and a software requirements specification (SRS) was the main vehicle programmers used to record them.
在1985年，我们一直在寻找许多不同的方法来定义问题，如书面写好需求，软件需求说明书(SRS)是用来记录它们的主要载体。
For example, let's say you are a software architect who has always described project functional requirements as a list of unrelated "shall have" items in a Software Requirement Specification (SRS).
例如，让我们假设您是软件架构师，总是按照软件需求规范（Software Requirement Specification，SRS）来将项目功能需求描述成一列不相干的“应该有”的条目。
When a team creates their requirements, they need to create both the breadth view of requirements (RUP Vision) and the depth view of requirements (the Software requirement Specification, or SRS).
当团队创建了他们的需求时，他们需要生成对需求的宽度视角(rup远景)和深度视角(Soft wareRequirementSpecification，或SRS)。
For example, the artifact Software Requirements Specification (SRS) is owned by the Requirements Specifier.
例如，软件需求规格说明书(SRS)工件是需求详细说明人负责的。
For example, the artifact Software Requirements Specification (SRS) is owned by the Requirements Specifier.
例如，软件需求规格说明书(SRS)工件是需求详细说明人负责的。
应用推荐