【24h】

Software requirement prioritization based on non-functional requirements

机译:基于非功能需求的软件需求优先级

获取原文
获取原文并翻译 | 示例

摘要

Requirements can be characterized as needs or demands. In software, requirements are a portrayal of what a system is ought to do. Software requirements describe what must be produced and delivered [1]. System may have few to many requirements. In case of shortage of time or budget prioritizing requirements become a necessity. It not only helps the developer comprehend, which requirements are essential, important or urgent but also proves to be useful in decision making in every phase of software development lifecycle. A lot of techniques have emerged over time to prioritize requirements, each with a set of strengths and weaknesses. In this paper, we present an approach by combining a few of existing techniques that will help the software engineers prioritize requirements.
机译:需求可以描述为需求或需求。在软件中,需求是系统应该做什么的写照。软件需求描述了必须生产和交付的产品[1]。系统的需求可能很少。在时间紧迫或预算不足的情况下,有必要优先考虑需求。它不仅可以帮助开发人员理解哪些需求是必不可少,重要或紧急的,而且在软件开发生命周期的每个阶段的决策中都证明是有用的。随着时间的推移,出现了许多技术来对需求进行优先级排序,每种技术都有其优点和缺点。在本文中,我们通过结合一些现有技术来提供一种方法,这将帮助软件工程师确定需求的优先级。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号