Software Evolution Approach for the Development of Command and Control Systems

2000 Command and Control Research and Technology Symposium (CCRTS), June 11-13, 2000, Naval Postgraduate School, Monterey, CAThis paper addresses the problem of how to produce reliable software that is also flexible and cost effective for the DoD distributed software domain. DoD software systems fall into two categories: information systems and war fighter systems. Both types of systems can be distributed, heterogeneous and network-based, consisting of a set of components running on different platforms and working together via multiple communication links and protocols. We propose to tackle the problem using prototyping and a “wrapper and glue” technology for interoperability and integration. This paper describes a distributed development environment, CAPS (Computer- Aided Prototyping System), to support rapid prototyping and automatic generation of wrapper and glue software based on designer specifications. The CAPS system uses a fifth-generation prototyping language to model the communication structure, timing constraints, I/O control, and data buffering that comprise the requirements for an embedded software system. The language supports the specification of hard real-time systems with reusable components from domain specific component libraries. CAPS has been used successfully as a research tool in prototyping large war-fighter control systems (e.g. the command-and-control station, cruise missile flight control system, missile defense systems) and demonstrated its capability to support the development of large complex embedded software.This research was supported in part by the U. S. Army Research Office under contract/grant number 35037-MA and 40473-MA

A flexible architecture for manufacturing planning software maintenance

Computer software systems took on a new role in manufacturing planning with the introduction of Material Requirement Planning (MRP) system in 1965. The MRP system generates material requirement lists in response to given production requirements. In this way, inventory management, purchasing, and shipping activities are linked to manufacturing. In 1979, Manufacturing Resource Planning (MRP II) systems were introduced [VerDuin 1995]. MRP II typically includes planning applications, customer order entry, finished goods inventory, forecasting, sales analysis, production control, purchasing, inventory control, product data management, cost accounting, general ledger processing, payables, receivables, and payroll [Turbide 1995]. An emerging market is developing for software systems that expand the scope of\u27MRP II farther to encompass activities for the entire organization. Among these systems are Enterprise Resource Planning (ERP), Customer-Oriented Manufacturing Management System (COMMS), and Manufacturing Execution Systems (MES). These systems integrate marketing, manufacturing, sales, finance, and distribution to move beyond optimizing production alone, to optimizing the organization\u27s multiple objectives of low cost, rapid delivery, high quality, and customer satisfaction [VerDuin 1995]. MRP II is still the dominant solution for manufacturing in tens of thousands of companies. These companies range in size from less than a million dollars in sales right up to the top of Fortune 500 companies. However, this is a market penetration of only 11% which clearly shows the size and potential of the opportunity for MRP II development. Yet, despite the commonality of needs across the scope of manufacturing, there are distinct differences when comparing plant to plant, company to company, and industry to industry. Often MRP II has to be modified to adapt to a particular industry [Turbide 1993]. This modification often pushes the cost even higher and makes MRP II more out-of-reach for many companies. Therefore, it would be highly beneficial for the overall scope of manufacturing if a highly flexible low-cost MRP II system can be developed. This research presents a flexible architecture for development and maintenance of manufacturing planning software, especially MRP II. The architecture uses the concept of software reuse and is built on top of run-time object-oriented framework

Systems integration using Siemens\u27 PC based automation technology

Manufacturing Systems Integration is the progressive linking and combination of the various components of the system to merge their functional and technical characteristics into a comprehensive interoperable unit. It requires one to work with different hardware and software. There are a number of vendors providing a large number of products. Integrating these varieties of products provides a greater value than the sum of the value provided by the individual products. What hinders the effective integration of these components is the diversity in the design and the use of these products. Systems Integration is eased by well-established standards in data communication, programming languages, application development environments and computer operating systems. Many vendors have attempted to come up with standards that are relatively open. However, when one has to integrate data among multiple vendors\u27 architecture, a new set of challenges emerge. The Siemens\u27 PC-based automation technology is an emerging technology that appears to provide robust architecture for integrating all elements of the manufacturing environment. Applications ranging from simple control to distributed control and full-fledged Manufacturing Execution Systems can be developed using Siemens\u27 architecture. The primary focus of this applied research work is to develop a Manufacturing Execution System to control a flexible manufacturing system using Siemens PC-based automation technology. This technology is implemented in a Flexible Manufacturing cell named the CAMCELL. The CAMCELL consists of two CNC machining centers, assembly robots, and a vision system, all of which are interlinked by a material handling system. The software architecture of the CAMCELL is based on NIST\u27s five level hierarchy, discussed briefly in the report. Specifically it contains functional modules for order entry, scheduling and routing. In addition to these functional modules, there are various support modules such as order entry module, scheduler, router etc, two of which named the Inquire and the Pallet Controller that are implemented in this study. Siemens\u27 Step 7 and WTNCC software are used for the control and monitoring of the cell

A Modular, Real-Time Fieldbus Architecture for Mobile Robotic Platforms

Cataloged from PDF version of article.The design and construction of complex and reconfigurable embedded systems such as small autonomous mobile robots is a challenging task that involves the selection, interfacing, and programming of a large number of sensors and actuators. Facilitating this tedious process requires modularity and extensibility both in hardware and software components. In this paper, we introduce the universal robot bus (URB), a real-time fieldbus architecture that facilitates rapid integration of heterogeneous sensor and actuator nodes to a central processing unit (CPU) while providing a software abstraction that eliminates complications arising from the lack of hardware homogeneity. Motivated by our primary application area of mobile robotics, URB is designed to be very lightweight and efficient, with real-time support for Recommended Standard (RS) 232 or universal serial bus connections to a central computer and inter-integrated circuit (I(2)C), controller area network, or RS485 bus connections to embedded nodes. It supports automatic synchronization of data acquisition across multiple nodes, provides high data bandwidth at low deterministic latencies, and includes flexible libraries for modular software development both for local nodes and the CPU. This paper describes the design of the URB architecture, provides a careful experimental characterization of its performance, and demonstrates its utility in the context of its deployment in a legged robot platform

Flexible Global Software Development (GSD): Antecedents of Success in Requirements Analysis

Globalization of software development has resulted in a rapid shift away from the traditional collocated, on-site development model, to the offshoring model. Emerging trends indicate an increasing interest in offshoring even in early phases like requirements analysis. Additionally, the flexibility offered by the agile development approach makes it attractive for adaptation in globally distributed software work. A question of significance then is what impacts the success of offshoring earlier phases, like requirements analysis, in a flexible and globally distributed environment? This article incorporates the stance of control theory to posit a research model that examines antecedent factors such as requirements change, facilitation by vendor and client site-coordinators, control, and computer-mediated communication. The impact of these factors on success of requirements analysis projects in a “flexible” global setting is tested using two quasi-experiments involving students from Management Development Institute, India and Marquette University, USA. Results indicate that formal modes of control significantly influence project success during requirements analysis. Further, facilitation by both client and vendor site coordinators positively impacts requirements analysis success

Building Programmable Wireless Networks: An Architectural Survey

In recent times, there have been a lot of efforts for improving the ossified Internet architecture in a bid to sustain unstinted growth and innovation. A major reason for the perceived architectural ossification is the lack of ability to program the network as a system. This situation has resulted partly from historical decisions in the original Internet design which emphasized decentralized network operations through co-located data and control planes on each network device. The situation for wireless networks is no different resulting in a lot of complexity and a plethora of largely incompatible wireless technologies. The emergence of "programmable wireless networks", that allow greater flexibility, ease of management and configurability, is a step in the right direction to overcome the aforementioned shortcomings of the wireless networks. In this paper, we provide a broad overview of the architectures proposed in literature for building programmable wireless networks focusing primarily on three popular techniques, i.e., software defined networks, cognitive radio networks, and virtualized networks. This survey is a self-contained tutorial on these techniques and its applications. We also discuss the opportunities and challenges in building next-generation programmable wireless networks and identify open research issues and future research directions.Comment: 19 page

Proceedings of the ECSCW'95 Workshop on the Role of Version Control in CSCW Applications

The workshop entitled "The Role of Version Control in Computer Supported Cooperative Work Applications" was held on September 10, 1995 in Stockholm, Sweden in conjunction with the ECSCW'95 conference. Version control, the ability to manage relationships between successive instances of artifacts, organize those instances into meaningful structures, and support navigation and other operations on those structures, is an important problem in CSCW applications. It has long been recognized as a critical issue for inherently cooperative tasks such as software engineering, technical documentation, and authoring. The primary challenge for versioning in these areas is to support opportunistic, open-ended design processes requiring the preservation of historical perspectives in the design process, the reuse of previous designs, and the exploitation of alternative designs. The primary goal of this workshop was to bring together a diverse group of individuals interested in examining the role of versioning in Computer Supported Cooperative Work. Participation was encouraged from members of the research community currently investigating the versioning process in CSCW as well as application designers and developers who are familiar with the real-world requirements for versioning in CSCW. Both groups were represented at the workshop resulting in an exchange of ideas and information that helped to familiarize developers with the most recent research results in the area, and to provide researchers with an updated view of the needs and challenges faced by application developers. In preparing for this workshop, the organizers were able to build upon the results of their previous one entitled "The Workshop on Versioning in Hypertext" held in conjunction with the ECHT'94 conference. The following section of this report contains a summary in which the workshop organizers report the major results of the workshop. The summary is followed by a section that contains the position papers that were accepted to the workshop. The position papers provide more detailed information describing recent research efforts of the workshop participants as well as current challenges that are being encountered in the development of CSCW applications. A list of workshop participants is provided at the end of the report. The organizers would like to thank all of the participants for their contributions which were, of course, vital to the success of the workshop. We would also like to thank the ECSCW'95 conference organizers for providing a forum in which this workshop was possible