SOS Systems Engineering, Integration, and Architecting

SOS Systems Engineering, Integration, and Architecting Many people would concur that the world is currently an intricate place to live. Much of this assertion is attributed to two events that have begun to dictate our lives in recent years.Advertising We will write a custom essay sample on SOS Systems Engineering, Integration, and Architecting specifically for you for only $16.05 $11/page Learn More First, human beings are deeply immersed in unparalleled levels of assimilation and are engrossed in an intricate web of interacting processes and technologies brought about by improvements in information and communication technologies. Second, rapid change is now a common phenomenon with novel practices, organizations and technologies being launched incessantly into this extremely assimilated web (Calvano and John 29). According to Chen and Clothier, the Systems of joint evolution include assimilation of the warship and the current SOS, and improvement of interoperability between the air defense missile and the surve illance plan. Emergent Evolution: A new system is to be developed in relation to or based upon the current systems with new capabilities. Example includes designing an assimilated air picture in relation to the current defense capability systems (Chen and Clothier 4). SOS Challenges The adoption of system engineering for SOS evolution and development brings about various challenges attributed principally to the changes within the SE context: Engineering object change: The object being engineered during the SOS lifecycle differs with respect to evolution circumstances. The object is frequently restricted to a precise part of an SOS. Engineering focus change: With respect to a particular evolution situation, the engineering focus can be replicated in various evolution needs (i.e. from integration, evolutionary development, redevelopment and redesign). Engineering environmental change: In addition to SOS evolution, various evolution circumstances require dissimilar engineering contex ts according to supporting instruments, information and knowledge resources, and terms of stakeholders (Chen and Clothier 5). Architecture in Practice Architecture stands out as one of the principal constituents of contemporary SE (Kopetz 112). The main goal of Architecture practice is to help an organization develop architecture capability by harmonizing architectural related processes. In the absence of a harmonized architecture practice, system architecting becomes complicated and exasperating within the SOS evolution backdrop as it cannot be executed effectively without dealing with other architecture problems.Advertising We will write a custom essay sample on SOS Systems Engineering, Integration, and Architecting specifically for you for only $16.05 $11/page Learn More Thus, a methodical examination of architecture practice provides a wonderful prospect for SE community to collaborate with other related fields such as architecture issues of SOS and so ftware engineering and information systems (Chen and Clothier 11). The current immaturity with respect to architecture practice has brought about uncertainty regarding the appropriate use of architecture methodologies and structures. Nonetheless, SE can be augmented in a number of ways by redefining the functions of architecture within the context of SE for SOS development and integrating architecture production with SE activities. As a subset of system engineering field, architecture practice can be planned, streamlined and integrated successfully with SE processes in the entire system life-cycle needed for SOS. Thus, the maturation process of architecture will generate a variety of architecture-related processes and products deemed as components of an engineering field. For example, project-based system engineering has an element of architecting which is a component of architecture practice of an organization. Therefore, SE teams require architecture assistance from all pertinent spheres of architecture practice in order to successfully execute this activity for different evolutions within the context of SOS. In nutshell, SE teams must employ architecture capabilities created via the architecture practice in the entire organization (Chen and Clothier 12). Recent works in SOS and the lead systems integrator concept The Technical Cooperation Program (TTCP) Joint System Analysis (JSA) technical Panel 4 (TP-4) aspires to shape national acquisition processes and strategies in order to realize efficient joint coalition capability. For example, current TP-4 initiatives consist of case studies on applications of system engineering in latest defense capability development among coalition member states with an emphasis on SOS. As of now, the TTCP TP-4 is engaged in designing a Coalition Systems Engineering Process (CSEP) with the intention of setting up synchronized and integrated SE processes across defense organization. This will result in enhanced defense capabilit ies of the coalition in future, especially in the sphere of interoperability and architecture practice (Chen and Clothier 13). Force Levels Systems Engineering (FLSE) is another program of Defense Science Technology Organization (DSTO) designed for use by Australian Defense Organization (ADO). The main aim of FLSE is to assist the ADO set up system engineering structure that can be used to augment and implement the Defense Capability Systems Life Cycle Management (DCSLCM). It is expected that this structure will ultimately envelop all areas related to DCSLCM (such as In Service, Acquisition, Capability Development and Strategic Planning).Advertising Looking for essay on engineering? Let's see if we can help you! Get your first paper with 15% OFF Learn More As opposed to other SE teams engaged in development projects or acquisition, the main objective of FLSE initiative is to design techniques and solutions for system engineering (SE) application to DCSLCM (Chen and Clothier 13). Some of the processes relevant to FLSE program include: Defining a conceptual SE structure that encloses DCSLCM Illuminating and streamlining working surroundings of the processes with respects to their techniques, tools, references and inputs/outputs employed. Defining a mutually shared Defense Capability Architecture Information Model (DCAIM) as a foundation for Systems-of-Systems SE data administration that openly facilitates business processes management within the DCSLCM framework Developing an SOS system engineering supporting environment that is assimilated with SE and architecture tools to offer a DCAIM-based SE knowledge warehouse (Chen and Clothier 13). In essence, FLSE program is projected to assist the ADO employ System Thinking and system engine ering at an organizational level and within the entire context of DCSLCM. Thus, ADO is expected to use FLSE to offer a superior engineering atmosphere for enhanced application of SE at conventional project level (Chen and Clothier 13). Calvano, Charles and Philip John. â€Å"Systems Engineering in an Age of Complexity.† IEEE Engineering Management Review, 32.4(2004): 29-38. Print. Carlock, Paul and Fenton Robert. â€Å"System-of-Systems (SoS) enterprise systems engineering for information-intensive organizations.† Sys Eng 4.4(2001): 242 261. Print. Chen, Pin and Jennie Clothier. â€Å"Advancing Systems Engineering for Systems-of Systems Challenges. System Engineering 6.3(2003): 1-14. Print. Flood, Scott and Paul Richard. â€Å"An Assessment of the Lead Systems Integrator Concept as applied to the Future Combat System Program.† Defense Acquisition Review Journal (2006): 355-373. Print. Grossman, Claudia and A. Goolsby. Engineering A Learning Healthcare System: A Look at the Future, Washington, D.C: The National Academies Press. 2011. Print. Kopetz, Hermann. â€Å"The Time-Triggered Architecture.† Proceedings of the IEEE 91.1(2003): 112-126. Print. Lane, Ann. Systems of Systems Lead Systems Integrators: Where do they spend their time and what make them more/less efficient? Southern Carolina: University of Southern Carolina: 2005. Print.