Skip to main content

Designing in a Logical/Functional Viewpoint

  • Chapter
  • First Online:
Effective Model-Based Systems Engineering

Abstract

This chapter describes the next phase of the MBSAP process, showing how the top-level architecture from the Operational Viewpoint (OV) is transformed into a functional design of the system in a Logical/Functional Viewpoint (LV). We familiarize the reader with the concepts and techniques involved in carrying the five Perspectives of the OV to the level of a functional architecture, using the E-X example for illustration. We discuss design patterns, making the point that although these arose in the world of software, they have great applicability and payoff when applied to entire systems. For example, we show how Domains are decomposed to the level of actual system components, modeled as Blocks. Similarly, we will take the representation of system behaviors down to individual Blocks or groups of Blocks and begin to look at the timing of system functions. In the Data Perspective, we illustrate the use of Inheritance to specialize Foundation Classes from the Conceptual Data Model into actual system data entities in a Logical Data Model. We introduce the key subject of layered architectures that are organized on the basis of services to create a computing platform on which applications software and user interfaces can be hosted. Next, we show what the LV looks like in the Smart Microgrid. When the LV is complete and fully documented, the system architect can furnish a set of functional specifications and other architecture artifacts to hardware and software developers, procurement and material management specialists, and others to use in implementing, integrating, testing, producing, and sustaining the system. We end the chapter with a discussion of executable architectures and a summary of key points in the LV. Chapter objective: the reader will be able to transform the high-level architecture of an OV into a functional design in an LV with supporting implementation documentation.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 109.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 139.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 159.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    For present purposes, “Logical” and “Functional” are equivalent, and both are in common use; we use the abbreviation LV for conciseness.

  2. 2.

    Continuing the convention of the previous chapter, we use “systems” generically to also refer to enterprises, nodes, subsystems, or any other levels of the Axis of Organization.

  3. 3.

    This use of the term “collaboration” should not be confused with the UML Collaboration Diagram, which is a behavior diagram. It was retitled a Communication Diagram in UML Version 2 and is not used in MBSAP.

  4. 4.

    This and other Applied Design Patterns in this chapter were developed by the authors and their colleagues and are being published openly here for the first time.

  5. 5.

    Technology refreshment is the common term for a process of replacing components that have become obsolete, are no longer available, or threaten to become so, with newer or more capable products to maintain system performance, reliability, and supportability.

  6. 6.

    The original term “World Wide Web” is now universally contracted to just “Web.”

References

  1. Gamma E et al (1995) Design patterns: elements of reusable object-oriented software. Addison-Wesley, Boston, MA

    Google Scholar 

  2. Shalloway A, Trott J (2001) Design patterns explained: a new perspective on object-oriented design. Addison-Wesley, Boston, MA

    Google Scholar 

  3. Constant JN (1972) Introduction to defense radar systems engineering. Spartan Books, New York

    Google Scholar 

  4. Stimson GW (1998) Introduction to airborne radar, 2nd edn. Scitech, Mendham, NJ

    Google Scholar 

  5. World-Wide Web Consortium (W3C) (2015) eXtensible Markup Language (XML). http://www.w3.org/XML/. Accessed 20 May 2017

  6. Maier MW (2006) System and software architecture reconciliation. Syst Eng 9(2):146–159

    Article  Google Scholar 

  7. IEEE (2011) Std 2030-2011. http://standards.ieee.org/findstds/standard/2030-2011.html. Accessed 21 May 2017

  8. MeshPower (2016) Connecting communities with clean energy. https://www.meshpower.co.uk/how-it-works.html. Accessed 20 May 2017

  9. Mellor SJ (2013) Executable UML. http://www.stephenmellor.com/uploads/XTU,%20doc,%20 Executable%20UML.pdf. Accessed 6 Feb 2013

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer International Publishing AG, part of Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Borky, J.M., Bradley, T.H. (2019). Designing in a Logical/Functional Viewpoint. In: Effective Model-Based Systems Engineering. Springer, Cham. https://doi.org/10.1007/978-3-319-95669-5_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-95669-5_5

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-95668-8

  • Online ISBN: 978-3-319-95669-5

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics