Chapter 14The FAS Method
The functional architecture is often mentioned in publications about systems engineering or in the context of real system projects. On the second view, you will realize that different terms are used like logical architecture, logical view, or functional view. And different artifacts are part of those architectures: set of functions, flow models, or functional models for simulation purposes. However, they all share the same notion: a technology-independent, function-oriented description of the system.
Jesko Lamm and Tim Weilkiens have observed a lack of concrete common methods for functional architectures in particular in the context of MBSE. Some years ago they described the FAS (Functional Architectures for Systems) method [83]. It was not a complete new method, but more a putting together of already existing puzzle pieces. The FAS method is a practice-proven method based on common MBSE practices. We describe FAS in this chapter and start with our view on the terminology and motivation of functional architectures.
Finally, we shine a light on different aspects of functional architectures like tool support, nonfunctional requirements or the role of technology in a technology-independent description.
Parts of this chapter are based on our article “Method for Deriving Functional Architectures from Use Cases” [84]. We omit the citation of the article at each statement that is taken unchanged or updated from that article.
14.1 Motivation
Functions are the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access