| 1. | As for other domains , there were no significant differences between variables . 3
就自我实现需求方面之自我决策而言，仅有中部区域及轻度障碍具预测力。 |
| 2. | The choice of requirements gathering process to implement depends on the greater context of the development project
实现需求收集过程的选择依赖于开发项目更大的环境。 |
| 3. | An exception - toss error condition is really an implementation requirement see below and should be listed in the " requirements " or " implementation notes " sections
异常抛出错误条件实际上是实现需求（见以下部分） ，应该在“需求”或“实现注意事项”部分中列出。 |
| 4. | The current 12 ( superscript th ) high school and vocational high school students with mental retardation scored high on the scale and had a good self - determination as a whole . 2
2 .除了在障碍等级方面，对自我实现需求方面之自我决策有达显著差异外（轻度中重度） ，其馀各因素均没有达显著差异。 |
| 5. | Requirements analysis and system design : developing information systems with uml . pearson education limited , 2001 . 6 jackson m . problem frames : analyzing and structuring software development problems
该方法将软件系统的需求看成是一组待实现的目标，通过目标的分解和操作化实现需求的精化和规约。 |
| 6. | To be successful , organizations must attain a solid understanding of each set of requirements , and then learn how to adapt their tools , methodologies , and application portfolios to implement the requirements
要想成功，组织必须对每组需求都了解得很透彻，并知道如何用工具、方法和应用程序投资组合来实现需求。 |
| 7. | The technical items dependencies , preconditions and postconditions , formal workflow analysis , implementation requirements and notes would come primarily from engineering , with the marketing organization in a consulting role
技术项（依赖性、前置条件和后置条件、正式工作流分析、实现需求和注解）将主要来自工程方，而市场营销组织起咨询角色。 |
| 8. | Whereas junit assumes that every aspect of testing is the domain of developers , the framework for integrated tests makes testing a collaboration between the business clients who write requirements and the developers who implement them
Junit假定测试的所有方面都是开发人员的地盘，而集成测试框架（ fit ）在编写需求的业务客户和实现需求的开发人员之间做了协作方面的试验。 |
| 9. | Communication errors between the client or the business department that authors application requirements and the development team that implements them are a frequent cause of friction , and sometimes the cause of downright failure in development projects
在客户、 （编写应用程序需求的）业务部门和（实现需求的）开发团队之间的沟通错误，通常是摩擦的原因，有时还是开发项目彻底失败的常见原因。 |
