Tag Archives: Requirements Analysis

Separation of Analysis & Design wrt. Abstraction

Posted on 2020 August 12 by modelpractice

Summing up separation of concerns of analysis and design wrt. abstraction, inspired by: Turner (2018) Computational Artifacts. Continue reading →

Posted in Software_Engineering | Tagged , , , , , , , , , , , , | Leave a comment

Practical Software Analysis vs. Design Modelling

Posted on 2017 October 2 by modelpractice

Practical modelling in software analysis differs significantly from design. The IMHO main differences are highlighted here. Continue reading →

Posted in Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , | 2 Comments

The Killer Application of Software Modelling

Posted on 2017 August 12 by modelpractice

From my experience as a business analyst (BA) I would say: checking or transforming models is interesting and important, but the real killer application of a model in software development is (simply) talking about it. Continue reading →

Posted in Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , | 1 Comment

Software Requirements Analysis: From the Art of Tidying Up to the Art of Abstraction

Posted on 2015 January 8 by modelpractice

Requirements analysis is more than just tidying up, it’s about understanding the complexity of structures. An explanation inspired by the art of Ursus Wehrli: Continue reading →

Posted in Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , , , | 1 Comment

Making use of IEEE 830 for Requirements Engineering

Posted on 2011 July 22 by modelpractice

IEEE 830 provides eight quite abstract characteristics for good requirements, like correctness, completeness, traceablity etc. Continue reading →

Posted in Software_Engineering | Tagged , , , , , , , , , , , , , , | Leave a comment

Model Transformation in Analysis

Posted on 2011 May 6 by modelpractice

An analyst has two main ways of making use of Model Transformation in requirements analysis: applying rules to models and keeping views consistent. Continue reading →

Posted in Software_Engineering | Tagged , , , , , , , , , , , , , , | Leave a comment

Are your Requirements complete?

Posted on 2011 April 27 by modelpractice

Completeness is one big issue in requirements engineering. Here’s how this can be approached by systematic analysis. To me this is already a basic application of modeling and its benefits. Continue reading →

Posted in Epistemology, Software_Engineering | Tagged , , , , , , , , , , , | 4 Comments