Parallel TPS design and application based on software architecture, components and patterns

The application of AI technology in architectural software has brought various innovations and changes to the industry. By introducing convolutional neural networks and deep neural networks, architectural design software is expected to automatically identify and generate complex architectural images, optimize the design process, and provide intelligent design assistance. Through literature research, this paper aims to discuss the specific application of CNN and DNN in parametric design and the innovation brought by them, and analyzes the application of these technologies in architectural image recognition, generation, design optimization and other aspects. This paper aims to provide a comprehensive reference for researchers in related fields and promote the innovative application of AI technology in architectural design. The application of AI technology in architectural software has brought numerous innovations and changes to the industry. By introducing convolutional neural networks and deep neural networks, architectural design software is expected to automatically identify and generate complex architectural images, optimize the design process, and provide intelligent design assistance. Through literature research, this paper aims to discuss the specific application of CNN and DNN in parametric design and the innovation brought by them; it also analyzes the application of these technologies in architectural image recognition, generation, design optimization, and other aspects. This paper aims to provide a comprehensive reference for researchers in related fields and promote the innovative application of AI technology in architectural design.

The purpose of this paper is to present a framework from which Automated Test Equipment (ATE) manufacturers can use to help them develop, integrate, and deliver ATE cloud-based applications to the consumers of their products. In order to create these applications, the developer can utilize Commercial Web Services (CWS) as a means to help access compute power, storage devices, and other services that provide the flexibility to choose a development platform or programming model that makes the most sense in trying to resolve the problem at hand. CWS provides a flexible environment from which to choose various programming models, operating systems, databases, and architectures to serve the consumers needs. CWS is highly cost-effective in that the developers and consumers pay only for what they use. Using CWS makes it extremely easy to create scalable and elastic systems as the developers can quickly add and subtract resources to their applications in order to meet current or future consumer needs. Furthermore, security is always a concern so CWS builds services in accordance with security best practices by providing the appropriate security features in those services. Using a CWS provides a level of scale, security, reliability, and privacy that are often cost prohibitive for most organizations to meet. This paper will examine available CWS cloud service platforms that organizations can potentially use to help deploy applications and services in a cost effective manner. The CWS platform consists of the following six main services, which will be discussed in more detail in this paper - (1) Computational/Networking, (2) Storage/Content Delivery, (3) Databases, (4) Analytics, (5) Applications, and (6) Deployment and Management services. One or more of these services may be utilized to help develop, integrate, and deliver ATE cloud-based applications to the consumer. The goals of ATE are to (1) quickly and accurately detect and isolate each fault, (2) provide software tools for analyzing historical data, (3) gather, manage, and distribute accurate and reliable maintenance information for the failed Unit Under Test (UUT). The CWS cloud platform will aid in the development of cloud based tools and applications that are cost effective, flexible, scalable, and secure that can be used by multiple end users to aid in the development of ATE system software tool sets. One example of a cloud-based application is a diagnostic reasoner that could be used to aid in diagnosing UUT repair actions. This paper will show how developers can use CWS to develop ATE cloud-based applications and tools that will help improve the overall ATE testing throughput, thus resulting in bottom line improvements to ATE life cycle costs.

Recently, one can recognize an increased awareness in the object-oriented research community with respect to the role of software architectures. Examples of this can, among others, be found in object-oriented frameworks and design patterns. In the call for papers for the workshop, the following topics were identified where software architecture, patterns and frameworks should be studied in more detail: Building OO software architectures: How can design patterns, frameworks and components be included in the traditional object-oriented analysis and design? How are architecture constraints processed to build OO software architectures? Which techniques can help to build an OO architecture that supports reuse and is scalable? Language role in architecture: What is the role of a particular object-oriented language when designing an architecture? Architecture documentation: It has been suggested that design patterns can be used to document the design and rationale of an object-oriented architecture. How well does this work in practice? OO architectural styles: What is the relation between the architectural styles of Garlan and Shaw and OO design? Composition of architectures: Since object-oriented frameworks are an accepted technology within the software industry, the composition of two or more frameworks in an application occurs increasingly often. The composition may be far from trivial and the problems that may appear as well as solutions should be investigated.

This paper illustrates an approach for architectural design of a Learning Management System (LMS), which is verifiable against the Learning Technology System Architecture (LTSA) conformance rules. We introduce a new method for software architectural design that extends the Unified Modeling Language (UML) component diagram with the formal architectural style of Acme, hence, combines the advantages of the visual appeal of a graphical method and preciseness of a formal method. We propose some new stereotypes for UML component-connector style to incorporate Acme style within UML. A UML meta-model for the design components is also proposed to elucidate the relationships between the components. We also propose a verification method to ensure that the design artifact is holding conformance with LTSA standard. The design process as well as the verification process entails additional knowledge about the domain, which is supplied by the domain Ontology. The LTSA conformance rules, written in natural language, are represented more formally with help of Conceptual Graph representation, before using them in the verification process. Finally, we introduce a verification method that tries to find out a design pattern in the architectural design that conforms to the particular conformance rule intended to check. The verification process also introduces a goodness measure of the conformance.

Software reusability is always the goal for the software people. It can improve the productivity and quality of software. Software architecture, design patterns, framework and components are the bases of application software reuse. Design patterns impenetrate into the whole process of software reuse, which is the important experience reference from software architecture to framework, form domain model to components. There are different domain models and frameworks in different domains. Referred to the shopping mall domain, the method of component design is introduced that domain model and framework can be obtained by domain analysis and then the design of components that are extracted from domain model could implement optimization to gain good system framework by the use of Strategy Pattern, Bridge Pattern and Abstract Factory Pattern.

The dial gauge is used widely in the production line at present. The dial gauge has many types and huge quantity. At present, testing this type of instrument is mainly used manual observation method. By man-made factors, the testing efficiency and accuracy is low. In order to improve the test efficiency and accuracy, it is required to use the automatic test methods for dial gauge. Although the control algorithm of control system in automatic test system is simple, the control accuracy is high demanding. So the design of control systems is essential. This paper takes the dial gauge automatic test method for the object and studied on the control system in the automatic test system. It presents the design principles, methods in fully automatic test system and studied on the design of control systems, mechanical drive parts and the software architecture. Finally, through experimental results verify the test system design is reasonable. Practical application results show that the system is feasible, and the motion control system is high precision and higher intellectualized. It also has good application prospect, especially for some special environment which is not suitable for testing by human eye, this system shows its superiority.

This paper provides an introduction to the field of software engineering requires facility in architectural software design. The goal is to demonstrate the current state of the discipline and examine the ways in which architectural design can impact soft-ware design. Software architecture is used to describe a high level design methodology of large software systems. It provides the overall structure of a system in an abstract and structured fashion. A smart architectural demonstration holds the key to the effectiveness of a software architecture description and usage. This paper focuses on criterion to select appropriate architecture style for software system. It also gives overview of definition, goals and requirements of software architecture with various architecture styles, their benefits and applications. The authors have also described the requirements and goals of robotic software architecture. The proposal for layered robotic software architecture for a distributed system is also presented.

Based on the words about why we must study software architecture, this article analyzed what the idea of building software architecture based on design patterns acts on the process of software development, discussed the development trend of software architecture and design patterns, and pointed to the problems which need to pay your attention during the term of building software architecture based on design patterns. In addition this paper described how the MVC pattern works in J2EE and explained what responsibilities the various parts in MVC have.

The DoD has achieved success with recent automatic test equipment (ATE) families, as evidenced by the navy's consolidated automated support system (CASS) and the army's integrated family of test equipment (IFTE) programs. However, as these systems age, the increased requirements for technology insertion due to instrument obsolescence and the demands of advanced electronics are becoming evident. Recent advances in test technology promise to yield reduced total ownership costs (TOC) for ATE which can incorporate the new technology. The DoD automatic test system (ATS) executive agent office (EAO) objective is to significantly reduce total ownership cost. Several objectives have been identified including use of synthetic instruments, support for legacy test product sets (TPSs), and more efficient ways of developing TPSs. The NxTest software architecture will meet the objectives by providing an open systems approach to the system software. This will allow for the incorporation of commercial applications in the TPS development and execution environments and support current advances in test technology.

A major cause of many complications in the field of software architectures is the lack of appropriate abstractions for separating, combining and encapsulating concerns of various kinds in architectural descriptions. Architectures of most complex software-intensive systems involve concerns that inherently crosscut the natural boundaries of the elements composing the architecture descriptions. Crosscutting concerns intersect the common modularity of systems as prescribed by their architecture descriptions, by traversing both the components and connectors, i.e., the relationships among the components. Crosscutting concerns are critical aspects of many architectural problems. However, architectural descriptions written in special-purpose languages (ADLs) like Wright, Darwin, Rapide and Acme should support descriptions of multiple structures, which include diagrams, models and views, that intentionally address different kinds of concerns. ADLs should show how various concerns affect each other in architectural designs; they should also allow one to identify, analyze and elaborate architectural concerns that cut across several software components, such as transactions, security, load balancing, synchronization, reuse, customization, scalability, etc.; they should, but they do not. This dissertation presents a new approach to software architecture that is suitable for supporting concern-oriented development and documentation of architectures for software-intensive systems. This approach allows for creating and documenting a multidimensional software structure that is referred to as concern-oriented software architecture; it provides new mechanisms for encapsulating individual concerns into independent architectural constructs. The ultimate goal of this new approach is to provide support for achieving design by concerns all through the development and description of software architectures. Moving towards this goal, we present a particular concern-oriented architectural framework called Perspectival Concern-Spaces (PCS). The PCS Framework offers a flexible and extensible means a) for supporting advanced separation of concerns in architectural design, and in the construction and evolution of software-intensive systems; and b) for filling the gap between architectural descriptions and modern software development artifacts. To show the feasibility of the proposed approach, we provide new modeling techniques that are used to describe and apply an aspect-oriented architectural pattern, called the On-demand Remodularization pattern. We give several examples of how the PCS Framework can be used to integrate concern-oriented architectural documentations with mainstream software development artifacts.

Present day software engineering concept gives emphasis on the use of design patterns for developing software which are recurring in nature. Detection of design pattern is one of the emerging field of Software Reverse Engineering. In this work, an attempt has been made to present an approach for design pattern detection with the help of Graph Isomorphism and Normalized Cross Correlation techniques. In this study, system and design pattern are presented in the form of graphs. The Graph Isomorphism technique finds the pattern subgraph in the system graph and Normalized Cross Correlation provides a way to formulate the percentage existence of the design pattern in the system. An Eclipse Plug-in i.e., ObjectAid is used to extract Unified Modeling Language (UML) class diagrams as well as eXtensible Markup Language (XML) files from the software system and design patterns. An algorithm is proposed to identify relevant information from the XML files. Then Graph Isomorphism and Normalized Cross Correlation techniques are used to find the pattern subgraph and its percentage existence in the system. This approach has been applied on four open source software tools for the evaluation of five design patterns, such as Composite, Facade, Flyweight, State, and Template Method.

Much work in software architecture has been inspired by work in physical architecture, in particular Alexander's work on 'design patterns'. By contrast, Alexander's work is little-used in town planning and architecture. In this paper, we examine some of the reasons that this is so, describe some parallels and differences between the fields of physical and software architecture, and identify areas in which future collaboration may be fruitful. The notion of 'participatory design' is important in software engineering and in urban regeneration, but the participatory mechanisms in each field are quite different.

To address practical challenges in teaching "Software Design Patterns" courses-including complex content, disconnect between theory and practice, and implementation difficulties-this study explores an OBE (Outcome-Based Education) approach. Through discovery-based exploration with classroom implementation as the ultimate goal, we developed implementation-oriented projects that integrate software design patterns with commercial software development. These projects enable students to learn the advantages of modular programming through software development, cultivating design pattern thinking. By adopting OBE principles in teaching "Software Design Patterns," students gain precise understanding of design patterns' value in commercial software development, enhancing learning engagement and improving course effectiveness.

The electronics industry and the Department of Defense (DoD), has thousands of obsolete legacy automated test systems (ATS). There are many systems, with different hardware and software architectures, that cannot be upgraded. The inability to reliably test products, diagnose faults, and collect historical data is having an effect on mission readiness. This paper describes a test and diagnostic system model that provides a means to use historical test and repair data from all levels of operation. The process reduces rework costs and decreases maintenance and repair costs through earlier and more accurate fault isolation. This work recoups the efforts of the original developer and captures test and diagnostic knowledge for the future. Consequently, the concept has been proposed for implementation within the Army ATS/TPS centers for use at the Army maintenance depots. Additional benefits from this work: development of a reliability database for system, subsystem, component by test type and ATS; tracking system reliability and mission performance data for use in developing requirements for new or upgrade system procurement specifications; and for pushing diagnostic knowledge and support from the sustainment level to the field and vice versa. The work presented will change the process of developing, maintaining and migrating diagnostic test now and into the future.

Software Design Patterns (SDPs) are core solutions to the recurring problems in software. However, adopting SDPs without taking into account their value implications may result in breach of social values and ultimately lead to user dissatisfaction, lack of adoption, and financial loss. An example is the airline system that overcharged people who were trying to escape from the Hurricane Irma. Although not intentional, overlsight of social values in the design of the airline system resulted in significant customer dissatisfaction and loss of trust. To mitigate such value breaches in software design we propose taking social values into account in SDPs explicitly. To achieve this, we outline a collaborative framework that allows for (i) specifying the value implications of SDPs, (ii) developing or extending SDPs for integrating social values, (iii) providing guidance on the value-conscious adoption of design patterns, (iv) collecting and analyzing insights from collaborators, (v) maintaining an up-to-date library of the valufied design patterns, and (vi) incorporating lessons learned from the real-world adoption of the valuefied design patterns into the proposed framework for its continuous improvement in integrating social values into software.