Product Owner and team typically detail requirements together.
产品负责人要和团队一起确认详细的需求。
It also USES the vendor name and the order ID for the detail requirements.
它还为detail的需要使用了商家名以及订单id。
The size of the LED Light Box can follow the customer's detail requirements!
水晶灯箱尺寸可按照客人提要求任意定做!
Give the detail requirements for welding spot, welding equipment and product inspection during welding.
给出了产品施焊中对施工现场、设备及产品检验的具体要求。
This procedure makes detail requirements on every step of steady state analysis for catalytic converter gas flow distribution.
现行的实用化计算规程对催化转化器流动计算的详细细节都做出了要求。
Either way we can refine our estimate for the next iteration and plan a better number of use cases for the team to detail requirements.
用任一种方式我们都能够为下一次迭代提出评估并为团队规划更大量的用例以详述需求。
If the software development team needs to clarify or detail requirements, they will make the changes directly on the baseline bl1 (main branch).
如果软件开发团队需要辨别以及将需求具体化,他们将会对基线b11(主要分组)直接做出改变。
Finally, the formulas for the ductility of RLCSW are proposed, and some detail requirements to guarantee the ductility of RLCSW are recommended.
并在以上分析的基础上,提出了轻骨料混凝土剪力墙位移延性系数的估算公式,给出了保证其延性性能的构造建议。
To understand the detail requirements in the EU standards is the first step we should take for exporting our electronic products to Europe market.
了解欧共体标准中的具体要求,是我国电子产品出口欧洲市场的第一步。
In fact, that is one of the weaknesses of traditional requirements gathering - it can never gather enough detail to eliminate implementation questions that inevitably arise.
实际上,这正是传统的需求收集过程的缺点之一—无法收集足够的细节,所以无法消除不可避免的实现问题。
Many product managers transitioning into the product owner role find it challenging not to write down all requirements and not to detail them straightaway-even if they could.
很多正在过渡到产品负责人的产品经理发现,不写下所有的需求,不去定义细节是很有挑战性的——即使他们本可以这么做。
If you need more detail on user requirements, having a connection with the business customer makes getting that information much easier.
如果你需要更多用户需求的细节,那么与业务客户联系会让你更易于获得相关的信息。
Many traditionalists struggle with this concept, thinking that they need to document the requirements in detail early in the project.
许多传统主义者与此概念对抗,认为它们需要在项目早期编制出需求细节。
After the requirements analysts are satisfied, they can go back and detail more of the remaining eight flows, turning over each one as it is completed.
在需求分析人员满意之后,他们可以回去并详述更多余下的八个流,将每一个都按照完成的那个处理。
In this section, we look at the requirements for SOAD in more detail, and start to define its themes and elements.
在这一部分中,我们将更详细地描述SOAD的需求,并且开始确定它的主题和原理。
Once you know your program's security objectives, you can identify the security requirements by filling in more detail.
一旦知道了程序的安全性目标,就可以通过更详细地填充其内容来确定安全性需求。
This is the same kind of information that you needed to capture for the business requirements; except that the subject area and level of detail are different.
这是您需要为业务需求捕获的同一类信息;除了主题区域和细节级别是不同的之外。
Most important, it articulates its academic requirements in exquisite detail, and focuses on those measures of institutional performance that are most germane to its mission.
更重要的是,它非常详细的阐述了其学术要求,还表明自己关注那与其学术任务最密切相关的机构表现。
During business analysis, requirements gathering, and use-case design, the model deliberately lacks detail, showing only the information concepts that are most important for the business.
在业务分析、需求收集和用例设计期间,有意忽略模型的细节,只显示对业务最重要的信息概念。
Then you would restate the requirements to make them clear and unambiguous, providing enough detail to support a design.
这样你就可以重述需求,使之清晰和无二义性,提供足够的细节以支持设计。
Many times, they don't talk in detail with all the project teams to understand their unique project requirements, timelines, and business drivers.
他们往往不会把细节告诉所有的项目团队,以使后者理解他们独特的项目需求、时间安排和业务驱动因素。
Tasks are refined or expanded as the detail expands or requirements change.
在细节展开或需求变更时细化或展开任务。
Each level of decomposition forces design decisions, providing ongoing synthesis, coupling of requirements and design specifications, and increasing system detail.
每个分解级别都强制进行设计决策,提供正在进行的合成,连接需求和设计规格说明,并增加系统详细内容。
Even technical folks might not even know the level of detail until the requirements and capabilities are more defined, and many unknowns have been researched.
在详细定义需求和功能以及研究许多未知问题之前,甚至技术人员都不了解详细级别。
Updated WHO guidelines for global surveillance reflect in greater detail these recommended changes, in line with reporting requirements set out in the International Health Regulations.
按照《国际卫生条例》规定的报告要求,更新后的世卫组织全球监测指南会更加详细地体现这些建议做出的变更情况。
Now I'll succinctly detail the functional requirements to consider in a cloud billing module.
现在,简要地介绍在云账单模块中要考虑的功能性需求。
Planning poker has been discussed in other places (including the Software Education "Agile Requirements - Stories" course) so we will not discuss it in detail here. However we will discuss.
规划扑克已经在其他地方讨论过了(包括软件教育“敏捷需求-故事”课程),因而在此不会讨论它的细节。
Let's start by reviewing the business requirements and the identified services that are intended to meet them, as we described in detail in "Modeling SOA: Part 1. Service identification."
我们首先回顾业务需求以及满足它们的被识别的服务,正如我们在“soa建模第1部分服务识别”中所详细描述的那样。
Smart with requirements - Base early decisions on lightweight requirements and detail as and when needed - requirements are negotiable and priorities will change.
需求(明智)——在轻量级的需求上做先期决策,在需要的时候再增加细节——需求是可以协商的,优先级是可以变化的。
But many of the requirements are not spelled out in as much detail as one would hope. For example, rule 4.5 states that.
但是,许多要求没有按照读者期望的那样尽可能详细地阐述。
应用推荐