Autor: Barino Barsoum
-
Requirements Engineering Framework with 7 task areas
My proposal for a Requirements Engineering Framework with 7 task areas: Demand Analysis: Customer needs and demand situations must be analyzed and understood in close collaboration with the Product Owners. This yields insights into the target audience, audience-specific product quality characteristics, demand for new features, and the possibility of removing features no longer needed. The…
-
Does a non-tech enterprise like an insurance company need an engineering culture?
In a world increasingly shaped by digitalization, the adoption of a strong engineering culture is becoming more critical for non-tech enterprises. The increased complexity cannot be handled in the requirements and engineering process simply by managing a backlog with epics and user stories aimed at quickly developing and launching a minimum viable product. Established companies…
-
How can complexity in large IT projects be managed?
How can complexity in large IT projects be managed? A model-based requirements and software engineering approach that starts with the analysis of the business model, continues through processes and requirements, and culminates in a system design, is key. Does that sound complicated? It is! It requires engineering excellence. This is the only way to master…
-
Importance of Documentation in Agile Development
To achieve good software, documentation is essential – even in agile software development! I would like to highlight two functions of documentation here: (1) Creating a common understanding. (2) Sharpening one’s own thoughts. (Ad 1) You probably know this too: You talk about a matter and believe that the other person has understood you. However,…
-
Differentiating Requirements Engineering from IT Architecture
(My post was inspired by the excellent presentation by Gregor Hohpe) Where does Requirements Engineering end, and where does IT Architecture begin? The boundaries are sometimes fluid, but let’s examine this specific example. The integration between System A and System B, necessary to implement certain functional requirements, certainly falls within the scope of the responsibilities…
-
Architecture Vision with four slides
My approach to lay out an Architecture Vision with four slides: First, lay out the business and technical context and objectives. Second, lay out the core structures of the high-level target architecture. Third, justify strategic architectural decisions. Fourth, lay out a high-level roadmap that reflects the main dependencies. See the four slides here: