English

Fraunhofer IESE - Teil 4 Agiler Anforderungen in der Anforderungsdokumentation

Requirements Specification (4/5): Containing Document Size in Agile Requirements Documentation

The documentation of requirements is an important means within requirements engineering. In projects with few requirements changes over their runtime, good documentation can be achieved with relative ease. For agile projects, however, it is in their nature that their requirements…

Fraunhofer IESE - Teil 3 Anforderungsdokuemntation: Welche Herausforderungen gibt es bei der Dokumentation agiler Anforderungen?

Requirements Specification (3/5): Typical Challenges with Agile Requirements Documentation

Documenting requirements is one of the key activities performed in requirements engineering. Even though projects using traditional development approaches naturally perform documentation, many practitioners in agile development projects avoid practicing the documentation of requirements because it is considered too much…

Fraunhofer IESE - Teil 2 Anforderungsdokumentation- agile Entwicklung und Anforderungsdokumentation

Requirements Specification (2/5): The No-Documentation Myth of Agile Requirements

Documenting requirements is a key activity in requirements engineering. However, despite the ubiquitous role of requirements documents, in agile settings the term “documentation” has a rather negative connotation. Poor documentation practice is often the result of an aversion to documenting,…

Fraunhofer IESE - Teil 1 Anforderungsdokumentation

Requirements Specification (1/5): Why Should You Perform Requirements Documentation?

In requirements engineering (RE), the documentation of requirements and related artifacts plays a central role. However, practitioners often experience challenges in this particular RE activity. This blog post is the first in a five-part series of articles on requirements documentation….

CrowdRE’s Achievements, Opportunities and Pitfalls according to Prof. Dr. Martin Glinz

A groundbreaking keynote on Crowd-based Requirements Engineering (CrowdRE) was recently held by the renowned Prof. Dr. Martin Glinz, and we are excited to be able to share a video recording of his 39-minute talk with you. Fraunhofer IESE introduced CrowdRE…

Autonomous or merely highly automated – what is actually the difference?

Autonomy, automation, autarky, networking… many terms are used in the context of  “autonomous systems”. For example, we already speak about autonomous driving if the vehicle takes over certain driving tasks on its own and without human intervention. Strictly speaking, however,…

How agile is your company? How to make the transition to an agile organization step by step

Agile Transition – Let’s have end-to-end agility! What exactly does this mean, and what does Agile mean in the context of software and systems engineering? Fraunhofer IESE has many years of experience with »Agile« in the area of software engineering,…

What does Paul Bocuse (French three-star-decorated chef) have to do with Data Science?

You wonder how a Data Scientist works? The data science process (i.e., building data-driven products such as recommendations systems, fraud detection systems, chatbots, etc.) is, in some sense, similar to what a chef like Paul Bocuse in a restaurant does…

Blockchain Architecture Design Guidelines – Architecting Blockchain-Based Applications (3/3)

Although (or because) blockchain is a hype topic, careful analysis is necessary to check whether blockchain is an adequate solution for an envisioned application. Designing the architecture of blockchain-based applications is challenging and requires an significant amount of aligned architecture decisions. We support architects with guidance for the decision whether blockchain could be an adequate solution and guide decision making for blockchain-based applications by outlining the architecture design space with numerous relevant questions.