Categorization of Requirements According to the Kano Model

Defining the requirements that will increase the satisfaction of stakeholders from the system being created is crucial for the process of acquiring requirements. Implementation of too many functionalities will make the application less intuitive and more difficult to use. During the process of acquiring requirements, you should choose those requirements that will be crucial for …

Categorization of Requirements According to the Kano Model Read More »

Requirement Prioritization Techniques

Today, it is time to describe the requirement prioritization techniques. We can transmit them using a number of techniques. Those are as follows: Ranking This technique consists in a selected group of stakeholders determining the available priorities for the requirements according to the adopted criteria. Top-Ten This technique consists in stakeholders selecting the most important …

Requirement Prioritization Techniques Read More »

Modeling of Business Processes in the Software Development Process

Business process modeling is relatively common today. In many organizations, it is even done in two places :-). In a cell responsible for improving or supervising processes and in IT, where software is made. The BPMN notation is the commonly used description language. The modeling of business processes in the software development process was, in …

Modeling of Business Processes in the Software Development Process Read More »

Managing Relationships Between Requirements

Requirements management is an important element of the software development process. One of its elements is building and managing relationships between requirements. The most common is the approach used or even promoted by Sparx Systems. Enterprise Architect in its documentation proposes that the requirements be combined with each other using aggregation or composition. This is …

Managing Relationships Between Requirements Read More »

Requirements Documentation

Requirements specification is a systematic representation of a set of requirements for a system or component that meets specific criteria. Requirements are like contract. All information collected and agreed during the requirements engineering activities must be documented. Each type of requirement affects, directly or indirectly, all phases of software life cycle. The quality of the …

Requirements Documentation Read More »

System Requirements – the Context and Boundary of the System

The main tasks of requirements engineering is acquisition and documentation of system requirements. To do this, identify those parts of the real world that will affect system requirements. The part of the reality that affects the definition of system requirements is called the system context. Incorrect or incomplete definition of the system context during requirements …

System Requirements – the Context and Boundary of the System Read More »

Scroll to Top