See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/383857673

Model‐Based Architectural Patterns for Teaching Systems Engineering

Article in INCOSE International Symposium · September 2024

DOI: 10.1002/iis2.13221

CITATIONS READS

0 52

2 authors, including:

Bhushan Lohar
University of South Alabama
18 PUBLICATIONS 22 CITATIONS

SEE PROFILE

All content following this page was uploaded by Bhushan Lohar on 09 September 2024.

The user has requested enhancement of the downloaded file.

 Model-Based Architectural Patterns for Teaching
Systems Engineering

Bhushan Lohar (Ph.D.) Robert Cloutier (Ph.D.)

University of South Alabama University of South Alabama
150, Student Services Drive, 150, Student Services Drive,
Mobile, AL 36688 Mobile, AL 36688
682-313-4665 251-259-7826
[email protected] [email protected]

Copyright © 2024 by Bhushan Lohar. Permission granted to INCOSE to publish and use.

Abstract. Systems Engineering (SE) may be one of the fastest-evolving engineering disciplines today.
With each technological innovation, the practice of systems engineering is challenged to adapt. Two
such practices that have been appearing in university curricula are Model-Based Systems Engineering
(MBSE) and Architectural Patterns. The combination of MBSE and patterns has proven to be a power-
ful construct. This paper looks at the use of a space-based patterns library (language) in a graduate-level
system engineering curriculum to teach MBSE. The International Council On Systems Engineering
(INCOSE) “Systems Engineering Vision 2035” defines, that by 2035, the systems engineering practices
will be based on a set of theoretical foundations and other general principles that are continuously taught
as part of a systems engineering curriculum. This paper provides an approach and a solution to the needs
of academic coursework for teaching model-based systems engineering. The method presented in this
paper details the usage of the pattern library concept developed for NASA and its usage by the systems
engineering graduate students that eases the development of new space-based systems architectures.
Again, our objective is to incorporate INCOSE Vision 2035 in academia using Model-Based Architec-
tural Patterns for Teaching SE.

Keywords. model-based system engineering (MBSE), model-based systems architecture (MBSA),

model-based pattern language (MBPL), SysML patterns, pattern library, pattern language.

Introduction
Patterns for architecting were first introduced by Alexander (1977) to demonstrate reusable constructs
for civil architectures. Patterns used in systems engineering (SE) were introduced to SE over 20 years
ago (Cloutier, Fickle, Watson, & Winkler, 2003), (Haskins & Cecilia, 2005) (Cloutier, 2005), and
(Cloutier, Verma, & Boardman, 2006). The first known prominent public usage of the term "Model-
Based Systems Engineering" is found in a book by Wayne Wymore (1993). The ICAM Definition, later
shortened to IDEF (Interim Data Exchange Format) was an early graphical modeling approach devel-
oped by the U.S. Air Force and was formalized in an IEEE standard (IEEE1320). IDEF is supported by
tools such as Vitech Core and Spec Innovation’s Innoslate (Skipper, 2003). The term MBSE was further
publicized by the Systems Modeling Language (SysML) Partners Consortium (OMG) during the form-
ative years of their SysML open-source specification project during 2003-2005. The standardization of
SysML in 2006 resulted in widespread graphical modeling tool support. In September 2007, the support
for an MBSE approach was further generalized by INCOSE with the introduction of the "MBSE 2020
Vision", which was not restricted to SysML, and supported other known modeling languages.

1
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Approximately 50 systems engineering attended the first INCOSE-sponsored MBSE workshop, which
was held the days before the International Workshop in January 2007 (INCOSE, 2007). Since then,
SysML has continued to mature and is approaching the release of version 2.0 of the SysML specifica-
tion. Today, there are more than fifteen companies and open-source projects that support SysML. This
represents a far greater application of graphical modeling using SysML. INCOSE initiated a Patterns
Based Systems Engineering (PBSE) challenge team in 2014 (OMG 2013) which later matured into the
OMG/INCOSE MBSE Patterns Working Group. INCOSE’s Vision 2035 states, that “system engineer-
ing education is part of the standard engineering curriculum and is supported by a continuous learning
environment”. This paper describes an approach taken by incorporating guidelines defined in INCOSE
Vision 2035 and using model-based architectural patterns for teaching systems engineering.

A pattern language, first introduced by Alexander (1979), is a collection of patterns that complement
each other and can be used to create an architecture in which the sum is better than the individual parts.
The broader (beyond systems engineering) patterns community attributes Christopher Alexander as the
originator and inventor of the pattern language concept. Alexander (1977) portrayed a pattern language
as a network of larger patterns comprised of smaller patterns. According to Alexander, there is no single
way to capture patterns and pattern language. Rising (1999) suggests ways to generate new patterns.
The INCOSE considered three of them for their applications: Mining by Interviewing, Mining by
Teaching Patterns Writing, and Mining by Borrowing (from the literature). An example of borrowing
from literature is given in Haskins (2005). Many forms apply to writing the patterns (Rising, 1998;
Simpson & Simpson, 2006; Cloutier & Verma, 2006, 2007). Lohar (2022) extended the same notions
by defining how to mine patterns from the public domain knowledge and developed a working-level
space system pattern language from the commonalities found in the existing space system architectures.

In Feb 2019, NASA (the advanced architecture concepts group) noted that industry and government
were in the process of increasingly embracing MBSE to manage system complexity. However, it still
took too long for systems engineers and architects to explore new systems architecture from scratch.
Familiar with the work of Dr. Cloutier, NASA reached out to the University of South Alabama to pro-
pose a research project that would use patterns to explore advanced concepts. The research task was to
identify space-based patterns from the public domain knowledge. The result of this project was a work-
ing-level space system pattern language from the knowledge found in the existing space system archi-
tectures. NASA was looking for an approach to create, then reuse, patterns to meet fast turnaround
design explorations. This became an opportunity to develop and prove a methodology for using patterns
for fast architecting using a patterns library.

The research aimed to provide a framework and methodology to document, develop, and use crucial
implicit information from the existing space system architectures and mission engineering patterns.
Studying the open literature, patterns within space systems were “mined” by capturing the “essence” of
the design. These patterns were documented in individual SysML models and named. The collection of
these patterns became the pattern language (or library). The language comprises subsystems, and prod-
uct/subassembly/assembly-level alternatives that can be imported into a new system model. The indi-
vidual patterns are organized into a functional ontology which can then be imported and connected with
other imported patterns to construct a logical architecture. Constructing a logical architecture in this
manner, using the SysML pattern language, is intended to improve new model construction. The main
benefit of the pattern language is to reduce the time and validation required to generate a new space-
based system architecture; this approach develops top-level system requirements in the initial phase of
the system development (Cloutier & Verma, 2007). This paper presents an incremental addition to the
existing published work by the authors and describes an extended novel application of space-based
pattern library and architectural patterns for teaching systems engineering in the classroom. Lastly, this
paper addresses the use of an applicable MBSE based pattern library, and its concepts, appear useful in
teaching systems architecting.

2
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Scope and Methods

To easily adapt the space systems pattern library in the classroom and further ease the process of new
space-based architectural development the subject pattern library is categorized into three preliminary
levels of individual SysML models. The first is the top level, also referred to as the system level. The
next level is the subsystem level, and the final level is the product/subassembly/assembly level; Com-
bining all three levels results in a high-level logical architecture. Alternatively, parts of the pattern can
be used independently and in combination with other patterns in the library or used as a standalone to
be combined with new work (Lohar, 2022). Figure 1 represents the organization of the pattern library;
each subsystem and its elements are organized as shown for the power subsystem in Figures 2 and 3.

Figure 1. Patterns Library Organization

Each pattern has its own set of requirements. Combining the small patterns into a larger pattern should
identify the requirements that can only be satisfied by the specific interface of the patterns (Lohar &
Cloutier, 2022). When applying the pattern in an architectural development, the architect has the re-
sponsibility to delete the options that are not considered necessary or relevant for the final architecture.

Figure 2. Power Subsystem Pattern Organization

3
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Figure 3. Power Generation Pattern Organization

To date, there are seventy-four patterns in this pattern library, forming the space systems pattern lan-
guage. Any collection of these patterns may be used to create a logical architecture of a spacecraft, with
the power to regenerate such spacecraft in hundreds of forms, with thousands of varieties in all the
details. It is also true that any small series of patterns from this language is itself a language for an even
smaller model of architecture (Lohar & Cloutier, 2022). This small list of models is then capable of
architecting thousands of habitats, satellites, rovers, and gateways. The benefit of this approach to a
pattern library is that neither the patterns themselves, nor the collection of patterns (the pattern li-
brary/language) should not remain stagnant, but instead be improved through continuous application
(Cloutier & Verma, 2006). As proof of concept, a logical architecture of a planetary surface habitat was
developed out of the pattern library for NASA. The various patterns helped develop the multi-level
architecture of the habitat with supporting systems like Power (EPS), Avionics, Thermal Management,
Environmental Control and Life Support (ECLS), Propulsion, Robotic, Structural, and Radiation
Shielding (Lohar, 2022).

Application to Academia and Curriculum

The authors developed an advanced graduate-level SE course using the subject space systems architec-
tural pattern library for the systems engineering students who are building their careers learning systems
engineering principles, MBSE methods, and tools. The students must have already taken a systems
architecting graduate course and learned SysML. Over the Summer of 2023, the Systems Engineering
Doctoral program at the University of South Alabama offered this graduate-level “special topics” course
titled “Space Systems Architecture”. Five graduate students registered and successfully completed the
course. Space systems architectures are an integral part of systems engineering; The course covered a
process-oriented approach using the NASA SE Handbook. Students studied mission objectives, and
mission requirements, understood key space systems engineering concepts, applied critical systems
thinking, set up the models, analyzed mission & stakeholder requirements, and defined flight and
ground systems and subsystems for their system of interest (SoI). The course combined lectures, and
readings from (Friedenthal & Oster, 2017) on developing a space mission product using SysML, and
used the subject space system pattern library to produce and deliver logical architectures. A well-written
individual practicum allowed students to integrate their systems engineering learning knowledge and
describe the overall functionality of the SoI. The students designed a logical spacecraft architecture by
combining all the required systems and subsystem patterns from the pattern library. The following sec-
tion discusses the student's work and the outcomes of the course.

Student 1. Figure 4 illustrates a Space Truck (spacecraft) top-level logical architecture developed by
student 1 using the pattern library. The patterns allowed the students to speed up the selection of re-
quired architectural elements for the stakeholders' desirements and mission-specific requirements. Each
pattern lies at the center of a similar network, and it is the network of these connections between patterns
that creates the language. Figure 5 is the power subsystem model by Student 1 for the Space Truck
mission. As proposed in Lohar (2022), the proposed pattern language could be extended by adding the

4
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

high-level system requirements to the SysML models. Individual requirements and technical specifica-
tions can be added to the object (block) of the patterns. Students added “values” and “properties” to the
pattern element block. These values are driven by mission-specific requirements, stakeholders' desire-
ments, and technical specifications.

Figure 4. Space Truck (Spacecraft) Top-Level Logical Architecture by Student 1

The top-level logical architecture of the Space Truck illustrated in Figures 4 and 5 suggests that a space-
craft as a system will have Robotics, Structure, Propulsion, Power, Thermal Management, Environment
Control and Life Support, Avionics subsystems, and a ground-based system control. Then each block
provides parts options that are necessary or optional for that sub-system. The student then applied Mass
Rollup and Power Roll-Up patterns to these models, the “values” provided to each block represent the
mass, total mass, power, and total desired mass of each system; followed by the watts required to work,
watts consumed, and total power consumed in watt-hour (Wh).

Figure 5. Space Truck (Spacecraft) Power Subsystem by Student 1

5
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Student 2. Using the NASA pattern library provided in this course, the subsystem, and components
down to the fourth level of decomposition could be defined. Due to the size of the model, the overall
system was broken down into several portions to gather the full depiction of the system. Figure 8 is the
system logical architecture for the Orion spacecraft.

“With the help of the NASA pattern library, all critical parts were identified. For ex-
ample, one of the essential items for the Orion spacecraft is the avionics subsystem.
The avionics subsystem is broken down into six different areas of focus underneath
this area. Within this area, there the control systems, electronics and communication
systems, sensors and instrumentation systems, guidance systems, navigation systems,
and data processing systems. These six areas are considered to be a third-level de-
composition. Below the third level of decomposition is the fourth level. This level goes
more into the depth of the six-third level breakdown” (Student 2, 2023).

Student 2 also applied a generic SysML Mass Roll Up pattern to the top-level logical architecture and
generated an instance table shown in Figure 6. This helps to further study the mass trade analysis be-
tween different subsystems and validate the mass requirements pluralizable throughout all the levels of
the Orion Spacecraft architecture.

Figure 6. Mass Roll-Up Pattern - Orion Spacecraft Logical Architecture by Student 2

Figure 7. Orion Spacecraft Model Organization (Containment Tree) by Student 2

Figure 7 illustrates the Orion Spacecraft model Containment Tree with an imported pattern library
package. This allows students (users, mission architects) to develop desired system logical architecture
by selecting a variety of elements <<Blocks>> for each mission and system requirement.

6
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Figure 8. Orion Spacecraft Top-Level Logical Architecture by Student 2

Student 3 - 5. Student 3 used the combination of the pattern library with NASA taxonomy to develop
a conceptual framework for an X-ray observatory ‘Cygwin’. The study demonstrated benefits by allow-
ing Cygwin to explore the same orbit as “Chandra” which allows cross-reference to any targets that
were missed during each observation (Student 3, 2023). Student 4 developed a logical architecture of
Asteroid Mineral Analysis Laboratory (AMAL), a spacecraft capable of landing on an asteroid, collect-
ing a mineral sample and analyzing it locally to determine the composition, sending the results back to
NASA, and then moving on to a different asteroid to repeat this process.

“As the logical architecture for AMAL began to take shape by using the pattern library,
it became clear that the original propulsion system that I had in mind would no longer
work” (Student 4, 2023).

Student 5 used a model of a NASA Tracking and Data Relay Satellite (TDRS) spacecraft. TDRS is a
geostationary orbit relay spacecraft used by NASA to support many missions. The system is well known
as variations have been flying since the early 80’s, student was able to demonstrate variability in the
different variants of TDRS just by simply adding and removing level three and four logical architectural
components used from the pattern library (Student 5).

Analytically, all 5 students used the majority of top-level patterns from the pattern library, with a min-
imum of four top-level patterns for Cygwin spacecraft (Student 3) and all seven for AMAL (Student 4)
and Orion spacecraft (Student 2). The most common four top-level system patterns are power, structure,
propulsion, and avionics systems. A total of fifty-six patterns were used in a complete or partial form
in the development of all five spacecraft architectures. Nineteen patterns are common among all space-
craft, including some of them are guidance, navigation, control, power generation, power storage, in-
space propulsion, communications, etc.

7
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

JAGSAT I and JAGSAT II. JAGSAT I was a NASA-supported 2U CubeSat being designed and
developed at the University of South Alabama for the scientific purpose of measuring plasma electron
density at submeter-level resolution. The science payload is a fast Time Domain Impedance Probe
(TDIP), a new instrument design. The technological objective was to develop a fully functional CubeSat
specifically with power, attitude control, and telemetry specifications sufficient to support the science
objective. (Spencer, Russ, Latif, & Montalvo, 2019). The JAGSAT I was launched on July 15, 2022,
by SpaceX Falcon-9 V1.2 from Block 5. After the successful launch and data collection of the JAGSAT
I mission, the team at the University of South Alabama is now working on the JAGSAT II mission
development.

The JAGSAT II team has decided to take a Systems Engineering approach in developing a 3U CubeSat
and is currently using the space-based pattern library (Lohar, 22) to analyze different possible logical
architectures for the CubeSat. The pattern library has been extremely helpful in the initial system anal-
ysis phase to quickly analyze the changes in the architectural models and their implication on CubeSat's
various requirements and technical specifications. The architectural models developed using the pattern
library are also helping the team with trade analysis and making decisions on subsystem, product, sub-
assembly, or assembly selections. The JAGSAT team is also going back to JAGSAT I and capturing
the “as-built” architecture in SysML to verify its original architecture and requirements. This analysis
will assist the team further in cross-verifying the lessons learned from the mission and implementing
improvements to the JAGSAT II architecture.

As proposed by Shaun Terrence Luther (2016) and illustrated in Figure 9, the team then will apply
numerical values describing critical aspects of each component to verify and validate the system spec-
ifications and requirements using various SysML simulations.

Figure 9. ExoCube Power Subsystem BDD (Luther, 2016)

8
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Conclusion
Increasing competitiveness in space missions is driving the need to develop new systems architectures
within a short period while accomplishing the verification, validation, and testing requirements. The
authors understand that the subject pattern library does not precisely match the physical architectures
and NASA taxonomy, but the objective is to develop an academic course using Model-Based Architec-
tural Patterns for Teaching Systems Engineering. The learning from this research is to define and gen-
erate a working-level pattern library and the top-level system requirements that are further used to de-
velop a space systems architecture by the systems engineering students. The teaching methods used and
outcomes produced from the space system architecture graduate coursework are also in line with the
INCOSE Future of Systems Engineering (FuSE) program's mission and streams of vision & roadmap,
foundations, methodologies, and application extensions.

This paper addresses the use of a pattern library to augment the understanding and value of model-
based systems engineering. During this process, we learned the benefits of adopting Model-Based Ar-
chitectural Patterns for teaching systems engineering. The initial data and outcomes identified from the
first class of graduate students provides initial results on a primary objective of pattern library develop-
ment of easing the process of new space-based systems architectural development. The authors plan to
continue evolving the space-based architectural pattern library and to continue to collect data from fu-
ture course offerings. The next step in this journey is to find ways to incorporate it into the Fundamentals
of Systems Engineering course and the Systems Architecting course curriculum. Given the rapidly
evolving technologies, and the need to evolve the practice of systems engineering, it is important, and
incumbent on academia to update the systems engineering curricula. Our systems engineering students
should be learning techniques that will help them in the future, not practices that are being retired. This
paper demonstrates one example of applying research to graduate curricula as well as extracurricular
activities in academia. Authors agree with the list of the implications for education and lifelong learning
by 2035 described in the INCOSE Vision 2035, the academia certainly offers an educational, training,
mentoring, and life-long learning pipeline to empower more systems engineers with strong multi- and
transdisciplinary competencies. As defined in INCOSE Vision 2035, MBSE supported by Artificial
Intelligence/Machine Learning (AI/ML) will aid the development of solutions, this approach is one of
the initial steps in developing a robust architectural pattern library that can be used by the AI and ML
to develop most viable products/solutions.

Other future work is to develop (mine and document) pattern libraries from other domains, such as
defense systems, biomedical, aeronautical, automobile, cancer treatments, and fire protection and sup-
puration systems, and for any large-scale heavy industries. Currently, the author is working with another
colleague to develop a pattern library for the fire protection and suppuration systems, this future work
presents a solution to minimize the efforts in deciding the most viable fire protection system options for
industrial applications while maximizing the performance. This future work will result in a Model-
Based Patterns Library for Fire protection systems translatable to multiple industries. Additionally, the
work will assist in developing a generic taxonomy and ontology of Fire Protection Engineering (Lohar,
2022) that could be used to analyze socio-technical applications and constraints not only for existing
industries but also for emerging industries such as Sustainable Aviation Fuels, Aerospace, and non-
military hangers and container ports.

Acknowledgments, Funding, and Conflicts of Interest This original work was supported and
funded by NASA Marshall Spaceflight Center (MSFC), Advanced Concepts Office (ACO) under the
Engineering Services and Sciences Capability Augmentation contract partnered with Jacobs Space Ex-
ploration Group (JSEG). NASA Prime Contract No. 80MSFC18C0011. The authors declare no conflict
of interest. The views expressed in this document are those of the authors and do not reflect the official
policy or position of the Jacobs Space Exploration Group (JSEG) and the NASA Marshall Space Flight
Center (MSFC) Advanced Concepts Office (ACO). The strategy and implementation concepts that are
defined in this paper should not be viewed as constituting a formal plan for NASA.

9
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

References
Alexander, C. (1977). A Pattern Language. New York, NY. Oxford University Press.
Alexander C. (1979). The Timeless Way of Building. Center for Environmental Structure, Berkeley,
CA.
Cloutier, R., Fickle, C., Watson, J., & Winkler, A. (2003). Modeling a System of Systems Using UML.
Conference on Systems Engineering Research (CSER), Stevens Institute of Technology,
Hoboken, NJ.
Cloutier, R. (2005). Toward the Application of Patterns to Systems Engineering. Conference on
Systems Engineering Research (CSER), Hoboken, NJ. March 23-25
Cloutier, R., Verma, D., & Boardman, J. (2006). Application of Patterns to Systems Engineering and
Architecting. Proceedings of the 16th Annual International Symposium of INCOSE, July 9-
13.
Friedenthal, S., & Oster, C. (2017). Architecting Spacecraft with SysML: A Model-Based Systems
Engineering Approach. CreateSpace Independent Publishing Platform.
Haskins, Cecilia. (2005). 11.2.2 Application of Patterns and Pattern Languages to Systems
Engineering. INCOSE International Symposium. 15. 1619-1627. 10.1002/j.2334-5837.
2005.tb00776.
IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0, Software
Engineering Standards Committee of the IEEE Computer Society, IEEE-SA Standards Board,
The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York,
NY 10017-2394, USA, IEEE Std 1320.1-1998, 25 June 1998
INCOSE MBSE Pattern Working Group. https://www.incose.org/communities/working-groups-
initiatives/mbse-patterns.
INCOSE (2007) International Workshop. https://www.incose.org/incose-member-
resources/chaptersgroups/ChapterSites/central-savannah-river-area/chapter-
news/2006/12/12/call-for-participation-incose-mbse-workshop.
INCOSE, MBSE Vision 2020.
INCOSE Vision 2035.
Lohar, B. (2022). Development of New Space Systems Architecture in SYSML Using Model-Based
Pattern Language. https://jagworks.southalabama.edu/theses_diss/75.
Lohar, B., & Cloutier, R. J. (2022). Towards A Model-Based Pattern Language for New Space-Based
Systems. https://doi.org/10.20944/preprints202208.0177.v1
Object Management Group (OMG). System Modeling Language (SysML).
https://www.omgsysml.org/what-is-sysml.htm
Rising L. (1998). The Patterns Handbook: Techniques, Strategies, And Applications. Cambridge
University Press.
Rising L. (1999b). Patterns: a way to reuse expertise. IEEE Communications Magazine. Volume: 37,
Issue: 4.
Shaun Terrence Luther (2016). SysML Based CubeSat Model Design and Integration with The
Horizon Simulation Framework. Theses Master of Science in Aerospace Engineering,
California Polytechnic State University, San Luis Obispo.
Skipper, J. (2003). A System Engineer’s Position on the Unified Modeling Language. Vitech
Corporation.
Spencer, E. A., Russ, S., Latif, S., & Montalvo, C. (2019, December). JAGSAT I: A NASA USIP
CubeSat to Perform Measurements of Plasma Density Irregularities in The Ionosphere for
Scintillation Studies. In AGU Fall Meeting Abstracts (Vol. 2019, pp. ED24B-01).
Student 1 - 5. Summer 2023. Space Systems Architecture. University of South Alabama, Mobile AL.
Wymore, A. Wayne (1993). Model-based systems engineering: an introduction to the mathematical
theory of discrete systems and to the tricotyledon theory of system design. Boca Raton: CRC
Press. ISBN 0-8493-8012-X. OCLC 26850986.

10
 23345837, 2024, 1, Downloaded from https://incose.onlinelibrary.wiley.com/doi/10.1002/iis2.13221 by University Of South Alabama, Wiley Online Library on [09/09/2024]. See the Terms and Conditions (https://onlinelibrary.wiley.com/terms-and-conditions) on Wiley Online Library for rules of use; OA articles are governed by the applicable Creative Commons License
Lohar & Cloutier

Biography

Dr. Bhushan Lohar is an Assistant Professor in Systems Engineering at the

University of South Alabama (USA). He is a President of the INCOSE Blues
Chapter and faculty advisor of the INCOSE student division at the USA. He has
over 10 years of experience combining the automobile and aerospace industry,
working on systems engineering, research & development, project management,
and quality management. His research interests include MBSE, Model-Based
Patterns, Space Systems Engineering, SysML modeling and simulation, and
Model-Based Machine Learning and Artificial Intelligence. He received his
B.Tech. from MIT India, MS from the University of Texas Arlington, and Ph.D.
from the University of South Alabama.

Dr. Robert Cloutier is a retired Research Professor at the University of South

Alabama (USA). His research interests include system architecture patterns,
model-based systems architecture improvements, and systems engineering for
AI. Before joining the USA, Dr. Cloutier was an Associate Professor and Direc-
tor of Systems & Software Programs at Stevens Institute of Technology in Ho-
boken NJ. Before Stevens, he spent over 20 years at Lockheed Martin and The
Boeing Company and served eight years in the U.S. Navy & Navy Reserve. He
received his BS from the US Naval Academy, MBA from Eastern University,
and Ph.D. from Stevens Institute of Technology.

11

View publication stats