Requirements Prioritization Based on Benefit and Cost Prediction: A Method Classification Framework

In early phases of the software development process, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper induces a conceptual model of requirements prioritization based on benefit and cost. For this purpose, it uses Grounded Theory. We provide a detailed account of the procedures and rationale of (i) how we obtained our results and (ii) how we used them to form the basis for a framework for classifying requirements prioritization methods

Priority Assessment of Software Requirements from Multiple Perspectives

The development of complex software systems involves collecting software requirements from various stakeholders. Often stakeholder perceptions conflict during the requirements elicitation phase. An effective technique to resolve such a conflict is needed. We presented a framework that prioritizes software requirements gathered from multiple stakeholders by incorporating inter-perspective relationships, which is not addressed by existing priority assessment techniques. We use a relationship matrix to analyze the impact between requirements and facilitate the integration process which assesses their priorities based on their relationships from multiple perspectives. It allows the development team to resolve conflicts effectively and concentrate their valuable time and resources on the critical few requirements from multiple perspectives that directly contribute to high customer satisfaction

Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research

In early phases of the software cycle, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper presents results of a systematic review of literature, which investigates how existing methods approach the problem of requirements prioritization based on benefit and cost. From this review, it derives a set of under-researched issues which warrant future efforts and sketches an agenda for future research in this area

Модели управления качеством обработки требований к программному обеспечению

В статье предлагается подход к управлению качеством обработки требований к программному обеспечению, который основывается на системном подходе и стандартах ISO. Выделены цели функционирования процесса анализа и обработки требований, рассмотрены его основные свойства, особенности взаимодействия с другими процессами жизненного цикла программных систем. Предложена концепция управления качеством входной, выходной информацией и самим процессом анализа и обработки требований.An approach to quality requirements management for software is outlined. This approach is based on system approach and ISO standards. Purposes of the system requirements analysis process activity were defined; its main properties and specific of interaction with other lifecycle processes were considered. The concept of quality control of the input, output information and the process of the system requirements analysis process was proposed

Модели управления качеством обработки требований к программному обеспечению

В статье предлагается подход к управлению качеством обработки требований к программному обеспечению, который основывается на системном подходе и стандартах ISO. Выделены цели функционирования процесса анализа и обработки требований, рассмотрены его основные свойства, особенности взаимодействия с другими процессами жизненного цикла программных систем. Предложена концепция управления качеством входной, выходной информацией и самим процессом анализа и обработки требований.An approach to quality requirements management for software is outlined. This approach is based on system approach and ISO standards. Purposes of the system requirements analysis process activity were defined; its main properties and specific of interaction with other lifecycle processes were considered. The concept of quality control of the input, output information and the process of the system requirements analysis process was proposed

A cognitive approach to improve software engineering processes

Cognitive Informatics is a new research area that combines concepts from cognitive sciences and informatics. Particularly, classification according to cognitive styles or learning styles is a common practise in educational and business areas in order to obtain better performance from people involved in learning and collaborative tasks. Humanintensive processes in software engineering make it similar to those areas. In this paper, we propose using a kind of people classification to improve those processes of software engineering where human behaviour is a critical influence on their success.Eje: Ingeniería en SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Integrating IVHM and Asset Design

Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable effective and efficient maintenance and operation of the target vehicle. It accounts for the collection of data, conducting analysis, and supporting the decision-making process for sustainment and operation. The design of IVHM systems endeavours to account for all causes of failure in a disciplined, systems engineering, manner. With industry striving to reduce through-life cost, IVHM is a powerful tool to give forewarning of impending failure and hence control over the outcome. Benefits have been realised from this approach across a number of different sectors but, hindering our ability to realise further benefit from this maturing technology, is the fact that IVHM is still treated as added on to the design of the asset, rather than being a sub-system in its own right, fully integrated with the asset design. The elevation and integration of IVHM in this way will enable architectures to be chosen that accommodate health ready sub-systems from the supply chain and design trade-offs to be made, to name but two major benefits. Barriers to IVHM being integrated with the asset design are examined in this paper. The paper presents progress in overcoming them, and suggests potential solutions for those that remain. It addresses the IVHM system design from a systems engineering perspective and the integration with the asset design will be described within an industrial design process

Issue Starvation in Software Development: A Case Study on the Redmine Issue Tracking System Dataset

In computing, starvation refers to the scenario when a process does not get required resources to complete its work. This mainly happens due to very simple priority based scheduling algorithms. Issues in software development require resources too and which issue will get the required resources depend on its priority. So the question is: Does starvation occur in Software Development too? The authors tried to answer the question with the help of their prepared dataset named as “Redmine Dataset”. Redmine is one of the popular web-based project management tool as well as an Issue Tracking Systems which also provide role-based access control. Currently, the Redmine ITS has more than 13000 issues and the number of issues is increasing time to time being. The authors have analyzed the Redmine dataset and found that starvation also occurred for issues in Software Development. The authors believe that this finding will steer the Software Engineering community for conducting research on advanced prioritization techniques which will resolve Issue starvation. Furthermore, the authors have provided few future research directions where this dataset can be used

Software Engineering: Factors Affect on Requirement Prioritization

Software engineering research is yet in its early stages hence it needs evaluation. So, software engineers think about experimental research and try to adopt analytical approaches to validate results like in other sciences. It should be asserting that requirement engineering process is to use requirements prioritization. The use of requirements prioritization helps the anatomy of requirements and isolates the most important requirements. A lot of prioritization techniques, practices and methodologies are used in software requirements. But lack of empirical search program and proficient methodology, was not decide which should be implemented. In this research, the requirement prioritization for systematical reviews was carried out. Based on systematic review, a framework is introduced for further research within requirement prioritization. This paper described a framework for scrutinize the discussion that take place during requirements elicitation and requirements prioritization. The survey presented in the paper gives a practical view how to prioritize the requirements. It also reflects the requirements prioritization in the industries needs. Which factors of the requirements engineering affect the requirements prioritization