Academic literature on the topic 'BSS/OSS Integration'

Industry 4.0 (I4.0) is a term first introduced in 2011 at the Hanover Fair and selectively adopted by other countries to promote various programs to modernize their manufacturing industries around integrated vertical and horizontal services. Germany's program to implement a smart factory included the following goals for the factories converting to Industry 4.0, including the development of Cyber-Physical Systems, Internet of Things, reusable, self-configurable units, Artificial Intelligence/machine learning, big data, and a functional ecosystem for SMEs. Other I4.0 initiatives include various programs from China, the US, Korea, Singapore, and Japan, for example, the National Network for Manufacturing Innovation. Since those initial discussions, I4.0 comprises the deep penetration of automation in all sectors of manufacturing, creating intelligent operations that are digitally connected and integrated horizontally (between enterprises and suppliers) and vertically (between all levels of operations in the enterprise, linked to the supply chain and the market). The time span from autonomous robots, 3D printing, and automation to a digital supply chain with augmented reality, artificial Intelligence, blockchain, big data analytics, IIoT, modeling, simulation, and high-level integration has gone from a few decades to deep concerns and pains about labor replacement and what do digital workers do, especially since the pandemic of 2020. Discussions include a rework of the social contracts that allow these changes to happen, so we do not end up with the work of the lower-skilled.

As organizations must continually drive down costs of software-driven projects, they need to evaluate the Systems Development Life Cycle (SDLC) and other software-based design methodologies. These methodologies include looking at software-based alternatives that could save a significant amount of money by reducing the amount of proprietary software. This chapter explores the use and integration of Open Source Software (OSS) in software-driven projects to include in enterprise organizations. Additionally, the legalities of the GNU General Public License (GPL), Lesser General Public License (LGPL), Berkeley Software Distribution (BSD), and Creative Commons are explored with the integration of these OSS solutions into organizations. Lastly, the chapter covers the software assurance and cyber security controls to associate with OSS to deploy a hardened product that meets the needs of today's dynamically evolving global business enterprise.

As organizations must continually drive down costs of software-driven projects, they need to evaluate the Systems Development Life Cycle (SDLC) and other software-based design methodologies. These methodologies include looking at software-based alternatives that could save a significant amount of money by reducing the amount of proprietary software. This chapter explores the use and integration of Open Source Software (OSS) in software-driven projects to include in enterprise organizations. Additionally, the legalities of the GNU General Public License (GPL), Lesser General Public License (LGPL), Berkeley Software Distribution (BSD), and Creative Commons are explored with the integration of these OSS solutions into organizations. Lastly, the chapter covers the software assurance and cyber security controls to associate with OSS to deploy a hardened product that meets the needs of today's dynamically evolving global business enterprise.

With the growing trend of global competitiveness and business complexity, the need arises for integrating BDTs in the design of ODSS. BDTs enable ODSS to deal with data of volume, variety, and velocity beyond the capability of traditional databases and data-warehouses in ODSS. The basic modules of updated ODSS with BDT are presented as a conceptual design, which provides a general foundation for the detailed design and implementation of an application. The validation of the proposed conceptual design is conducted on a test-case based upon the BSC perspectives as well as requirements common for ODSS scenarios. The results show that each requirement of the system is supported by a set of integrated modules in a balanced way. The modules of the highest contribution in the conceptual design are the modules most related to BDT. The initial stages of the implementation of the system are given.

With the growing trend of global competitiveness and business complexity, the need arises for integrating BDTs in the design of ODSS. BDTs enable ODSS to deal with data of volume, variety, and velocity beyond the capability of traditional databases and data-warehouses in ODSS. The basic modules of updated ODSS with BDT are presented as a conceptual design, which provides a general foundation for the detailed design and implementation of an application. The validation of the proposed conceptual design is conducted on a test-case based upon the BSC perspectives as well as requirements common for ODSS scenarios. The results show that each requirement of the system is supported by a set of integrated modules in a balanced way. The modules of the highest contribution in the conceptual design are the modules most related to BDT. The initial stages of the implementation of the system are given.

Abstract This chapter defines and illustrates the use of between-session homework (BSH) in individual psychotherapy. Whereas previous reviews have demonstrated a positive association between client compliance with BSH and distal treatment outcomes, this chapter pays particular attention to therapist behaviors that may promote client engagement with BSH assessed as immediate (in-session) and intermediate (session-to-session) outcomes, and moderators of these effects. For the systematic review, 25 studies with 1,304 clients and 118 therapists were identified, mostly on cognitive–behavioral therapy and exposure-based treatments with depression and anxiety disorders. A box-score approach was utilized to summarize findings. Results for immediate outcomes were mixed but neutral. Results for intermediate outcomes were positive. Therapist behaviors that may promote client engagement with BSH include presenting a convincing rationale; being flexible in collaboratively designing, planning, and reviewing homework tasks in accordance with the clients’ goals; aligning BSH with the clients’ takeaways from the session; and providing a written summary of homework and rationale. The chapter concludes with research limitations, diversity considerations, training implications, and therapeutic practices.

In the experiment scenario described in the previous chapter, control integration was accomplished through inter-tool communication via messages. In this approach, tools interact by passing messages (through a message system) requesting services of each other and notifying each other of their actions. This eliminates the need to duplicate functionality among tools, and the need to coordinate and operate via a shared tool database. Many influential vendors have considered this approach as a basis for control integration in CASE environment applications. To this end, Hewlett-Packard, Sun Microsystems, IBM, Unix Systems Laboratories (USL), The Santa Cruz Operation (SCO), and Univel formed the Common Open Software Environment (COSE) alliance. Hewlett-Packard already uses the “control integration via messaging” approach in its SoftBench framework product. Therefore, the original experiment used the message passing capabilities of SoftBench (particularly, the SoftBench Encapsulator and Broadcast Message Server (BMS)) as the primary means of tool-activity synchronization in the scenario. While analyzing the results of the initial set of experiments, we determined that the use of BMS as the message passing component of the experiment framework could (at least in principle) be replaced by an equivalent product such as Sun’s ToolTalk or Digital’s FUSE. This is significant in that one of the premises of the work of the SEI CASE Environments Project, and of the experiments in particular, is that different implementations of similar services can be easily interchanged to provide a degree of interoperability. The ability to interchange control-oriented integration framework mechanisms is an important part of that premise. While it would have been possible to hypothesize about the feasibility of the message service replacement by comparing and contrasting the services and their inherent functionality, it was decided to demonstrate better the practicality of the operation by example. An extension to the experiment was undertaken then, not to see if the message service replacement was theoretically possible, but to examine the process of actually performing (or attempting to perform) the replacement.

Abstract The inclusion of women in the Border Security Force (BSF) has foregrounded several long-standing concerns around adequate infrastructures, professional development, and soldiers’ welfare, as well as raised important issues about the BSF’s functional effectiveness and gender equality in the future. This chapter draws on ethnographic research with members of the BSF to examine the inclusion of women in the BSF, why it was considered necessary, how it affects the institution, and what kinds of internal institutional debates and material conditions of work impact the recruitment, deployment, and integration of women in the BSF. Emphasizing the importance of connecting questions of gender equality with broader issues of labor and welfare for all soldiers in the Force, the chapter concludes with critical reflections on the transformative potential of this policy for shifting patriarchal military culture inside and outside security institutions.

In assembling a CASE environment from a collection of commercial off-theshelf (COTS) tools, tool users must find ways to connect the tools such that they provide adequate support for their particular software development approach. This task takes place in the context of limited knowledge of the tools, limited access to the source or internal structures of the tools, limited resources with which to perform and maintain the tool connections, and evolving understanding of the needs of the tool users. This places severe restrictions on what can be attempted in terms of tool interconnection. Environment framework technologies (e.g., ECMA PCTE, ATIS, BMS, ToolTalk, or CORBA) claim to provide a set of common integration services that aid in the tool integration process. There have been numerous discussions about the value, maturity, and complexity of these framework technologies. Such discussions are characterized by three points: general agreement that framework technology per se is a valuable goal to pursue; moderate disagreement as to whether the current level of framework technology is a sufficient basis for production quality CASE environments; and considerable disagreement about which of the current technologies are the most likely to mature and succeed. Notable about these discussions, however, is that there has not been extensive use of the technologies in question. This stems from several sources: their expense, their unfamiliarity and complexity to current tool users, and a widespread concern about their immaturity. This lack of use is perhaps understandable, but it has had the additional effect that partisans of one or another technology have made assertions based on little factual information about the relative merits of the technology in question. To expand our own expertise in tool integration and framework technologies, and to answer the question, “What tool integrations are possible for third-party tool users given the current state of COTS tools and integration technology?” we performed a set of experiments involving the integration of a collection of common COTS tools with environment framework technologies in support of a typical development scenario. Our selection of these tools and technologies was based on common availability and application to the development scenario(s) of interest.