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,…
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….
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…
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,…
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,…
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…
Data Scientist is one of the sexiest jobs of the 21st century. This impression is confirmed when you take a look at relevant online job portals. According to a study by the McKinsey Global Institute [7], in the USA demand…
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.
Blockchain is a heavily overloaded term, both in discussions of practitioners and in literature. This ambiguity is dangerous as it leads to a lot of misunderstandings and can compromise the quality of blockchain-based applications being developed. Thus, we delineate in this article key terms of blockchain. To make understanding as simple as possible, we use Ethereum as an example.
Blockchain is a hype topic that already led to some disillusionment. The development of blockchain-based applications is often technology-driven and with a trial-and-error approach. We provide guidance for architecting blockchain-based applications. We put structure on foundations and terms around blockchain, we outline architecture drivers that benefit from using blockchain technology, and we guide architects with numerous questions through the design space of blockchain-based applications.
