Tracking of Relationship Between Requirements

An important aspect of requirements management is the ability to trace the relationships between requirements and other artifacts (including other requirements). The ability to track relationships supports the process of software development in the following aspects: Verity: Tracking the relationship between requirements and other artifacts allows you to verify whether the requirements have been implemented. …

Tracking of Relationship Between Requirements Read More »

Requirements Management – Best Practices

Ian Sommerville and Pete Sawyer in “Requirements Engineering: A Good Practice Guide” described, over 15 years ago, the method of assessing and improving requirements engineering processes. It is based on the identification of good practices, activities that are desirable elements of the model process of requirements engineering. The authors tried to cover the entirety of …

Requirements Management – Best Practices Read More »

User Stories vs Requirements

When writing any specification of requirements and the product register and sprint register, non-functional requirements should be included in this specification. While the user’s story itself usually represents functional requirements, in my opinion a small problem is with non-functional requirements that represent system-level expectations. Lack of non-functional requirements or their insufficient quantity are often a …

User Stories vs Requirements Read More »

Implementation of the Methodology – Selection of a Modeling Tool

In many companies there is a discussion about formalizing the software development process. Spontaneous creation of diagrams by broadly understood analysts and designers does not build the value of documentation. The value is created when the whole team adds a diagram to the diagram as a brick to a brick. The added business process models …

Implementation of the Methodology – Selection of a Modeling Tool Read More »

Registration of Problems Identified During the Analysis

I received an interesting question by e-mail: According to your knowledge, is there an object in EA that would be best suited for registering problems identified during business or system analysis (AS-IS)? I mean an object in which the parameters of the problem identified during the workshop would be registered, e.g. name, description, connection to …

Registration of Problems Identified During the Analysis Read More »

Scroll to Top