English

Continuous Engineering (Continuous Planning and Continuous Budgeting)

Continuous Engineering for Industrie 4.0 (Part 2)

Future-proof decision making can be enabled by Continuous Planning and Continuous Budgeting with Continuous Integration of Digital Twins: Today we continue the series Continuous Engineering for Industrie 4.0, where we are exploring how continuous engineering practices should be instantiated to the automation domain to support Industrie 4.0 principles.

Continuous Engineering for Industrie 4.0

Continuous Engineering for Industrie 4.0 (Part 1)

Rolling out changes in complex systems is always a challenge. Regardless of whether a software component needs to be modified or whether a change in the communication network needs to be made, any change may lead to unexpected behavior. Continuous…

Building the Industry 4.0 IT Infrastructure for Digital Twins

Industry 4.0 and Digital Twins promise many benefits, such as an efficient lot size 1 or various optimizations. However, successfully implementing these concepts requires a sophisticated IT infrastructure. What are the requirements on this infrastructure and how can it be…

Requirements Specification (5/5): What kind of tool do I need for Requirements Documentation?

This is the final article in a series of five blog posts on requirements documentation. Where documenting requirements is considered a de facto standard in classical projects, Agile contexts tend to avoid it, as it is seen purely as unreasonable…

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…

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…

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,…

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,…