1.2.1 Use Cases and Non‐functional Requirements Presented in Compact System Description A3s

Abstract

Abstract. Translating stakeholder requirements into system requirements is important for guiding the detailed design towards a solution that meets the stakeholder needs. The methods typically used today in the company do not sufficiently capture performance requirements. We combined the functional and non-functional aspects of a system in one diagram. We used compact system description A3s to communicate the diagram and other system information to stakeholders. We showed that presenting functions through use cases, annotated with non-functional requirements, help capture the performance aspect of the system, and that compact system description A3s communicate the most important aspect of the system well.

Knowledge Reuse in a Small Company in the Water Treatment Industry: A Case Study

“…The authors concluded that DA3As facilitated communication, understanding, early validation, employee training and knowledge capture (Singh & Muller 2013). (Nilsen & Muller 2013) used Compact System Description A3s (CSDA3s) to communicate system information to stakeholders and concluded that different system viewpoints increased understanding of single viewpoints. (Svendsen & Haskins 2016) found A3s to be a reliable, simple and adaptable tool when used for problem solving.…”

“…The employees are able to navigate and understand the documents included in the KMS by using this model. (Nilsen & Muller 2013) presented a map that could be used to understand the relationship between a set of A3s and (Løndal & Falk 2018) a block to list relevant documents.…”

“…3D-models in A3 reports are included in the papers of (Singh & Muller 2013) and (Svendsen & Haskins 2016). (Nilsen & Muller 2013) included a 2D-model in the final A3 version.…”