The Object is Reuse

<div class="section abstract"><div class="htmlview paragraph">Object-oriented programing has been around for more than 50 years and has changed the way we develop computational algorithms. Although the concept of objects in programming was introduced with a physical systems modeling tool, most modelling is done today with procedural programming. This paper aspires to show the benefits of object-oriented programming in contrast to procedural programming. This was done by taking a case study in which we analyze the model of the vehicle electric system. The system was partially modelled using Simulink for procedural programming and using Simscape for object-oriented programming. As a result, the object-oriented model was simpler to read and understand. It also provided an interface that facilitates expansion, whereas the procedural model needed to be rebuilt to accommodate changes in the structure and presented higher complexity. The analysis of these two models clearly demonstrates the advantages of using object-oriented programming in physical systems modelling. With this approach, engineering time and cost can be significantly reduced leading to faster time-to-market and improved development documentation.</div></div>

Now a day's object oriented program is the strongest tool in programming. Many factors such as code reusability, garbage handling and exception handling makes this approach stand out. So in the real field of development and maintenance object oriented program is heavily used. While static slicing of object oriented program is lengthy dynamic slicing approach gives upper hand mainly in debugging and software testing and maintenance. Dynamic slicing process extracts statements in the practical scenario, means having required input values. As code reusability and communication in object oriented program(OOP) is mainly achieved through inheritance and friend function, which are complex in nature we have presented methods in the paper which deals with these problem mainly in C++ language. We have used program dependency as the medium of finding slices. Here we have discussed slicing a C++ program in case of friend function and single inheritance.

Software testing allows programmers to determine and guarantee the quality of software system. It is one of the essential activities in software development process. Mutation analysis is a branch of software testing. It is classified as a fault-based software testing technology. Unlike other software testing technologies, mutation analysis assesses the quality of software test cases and therefore improves the efficiency of software testing by measuring and improving the quality of test cases set. Mutation analysis works by generating mutants, which describe the faults that may occur in the software programs, from original program. Mutants are generated by applying mutation operators on original software program. Mutation operator is a rule that specifies the syntactic variations of strings. There have been several works about mutation analysis support system for conventional languages such as C and FORTRAN. However, there are a few for object-oriented languages such as C++ and Java. This article aims to propose a novel approach to design and implement mutation operators for object-oriented programming language. The essential idea of proposed method is the usage of JavaML language as the intermediate representation to implement mutation operators: it first converts the original program into JavaML document; then implements mutation operator for JavaML document and gets the mutated JavaML document with the help of DOM — a tool to process JavaML document; finally it converts the mutated JavaML document into mutant program.

<div class="htmlview paragraph">This paper describes the development process for acceleration sensors used on automobiles and acceleration evaluation system especially for the acceleration in super low range frequency.</div> <div class="htmlview paragraph">Acceleration sensor is indispensable not only for good vehicle motion control system, for example, active suspension control system, antiskid control system and four wheel steering control system, but also for safety system like air bag control system. This work focused on the development process of acceleration sensor which applied piezo ceramics.</div> <div class="htmlview paragraph">Features of newly developed sensor are as follows.</div> <div class="htmlview paragraph"> <ol class="list nostyle"> <li class="list-item"> <span class="li-label">1)</span> <div class="htmlview paragraph">Achievement of self-diagnostic function to detect sensor failure utilizing the characteristics of piezo ceramics</div> </li> <li class="list-item"> <span class="li-label">2)</span> <div class="htmlview paragraph">Addition of piezo ceramic to cancel the pyro-effect achieved stabilization of sensor characteristics and enabled to detect acceleration of 0.0025G in super low range frequency of 0.05Hz.</div> </li> <li class="list-item"> <span class="li-label">3)</span> <div class="htmlview paragraph">Incorporates impedance conversion, filtering and temperature characteristics compensation circuitry.</div> </li> </ol> </div> <div class="htmlview paragraph">Frequency range of acceleration for good vehicle motion control is considered to be from DC to about 50Hz.</div> <div class="htmlview paragraph">But the measurement of acceleration in thus super low range frequency near DC had been difficult because of its mechanical and electrical noise interruption.</div> <div class="htmlview paragraph">This had delayed the development of acceleration sensor for automotive use.</div> <div class="htmlview paragraph">We succeeded in the development of acceleration measurement system for super low range frequency from 0.01Hz to 2Hz with detecting acceleration range from 0.0002 (0.2 gal) G to 1G as well as the development of piezo type acceleration sensor for automotive use.</div>

<div class="htmlview paragraph">Combi-Road is a container road transport system with high capacity. The system uses specially designed tracks which can be constructed as separate roads or as extra lanes alongside existing motorways. The containers are pulled on semi-trailers by unmanned automatically controlled electrical vehicles. The system allows to reduce the amount of vertical handlings in the transport chain. On so-called transfer stations containers are exchanged with sea shipping, road, railway and inland shipping.</div> <div class="htmlview paragraph">The Combi-Road project started January 1994. During the process of development the innovative technological nature of the concept has been strongly emphasized. In an early stage the implementation strategy has been paid attention to.</div> <div class="htmlview paragraph">This paper describes the basic technical details of the Combi-Road system, as well as the results of the initial test phase which has been completed by the end of 1996. Furthermore the follow-up phase is discussed which includes a broadening of the logistical concept in a concrete situation of introduction of the system in the Netherlands. Starting from so-called Logistical City Parks at the edge of a city, goods are distributed via tubes with unmanned vehicles to District Distribution Depots with a service area of approximately 500 metres.</div> <div class="htmlview paragraph">The supply of goods to the Logistical City Parks can be via the traditional transport modes road, water and rail or, for example, Combi-Road.</div> <div class="htmlview paragraph">In the concrete situation maritime containers as well as continental unitised cargo are transported between the following origin and destination points:</div> <div class="htmlview paragraph"> <ul class="list disc"> <li class="list-item"><div class="htmlview paragraph">on the one hand the container terminal on the Maasvlakte in Rotterdam, and,</div></li> <li class="list-item"><div class="htmlview paragraph">on the other hand the District Distribution depot in a city such as Utrecht,</div></li> <li class="list-item"><div class="htmlview paragraph">utilising the SHIFT-infra (Specific Highway Infrastructure for Freight Transport) as basic network,</div></li> <li class="list-item"><div class="htmlview paragraph">which, in the Logistical City Parks, is linked to the tube network for urban freight transport, and,</div></li> <li class="list-item"><div class="htmlview paragraph">en route at transfer stations such as the Multimodal Transport centre Valburg along the river Rhine exchanges with other modes take place or connections are made to systems such as the Underground Logistical System (ULS) at Amsterdam Airport Schiphol.</div></li> </ul> </div> <div class="htmlview paragraph">This is an ambitious approach which could lead to a break-through in automatic goods transportation in densely populated urban and interurban areas with intense traffic congestion problems.</div>

Software reusability is believed to be the key to improving software development productivity, while specification plays an important part in software reuse. From a modern object oriented view, the reusable software components can be grouped into three categories. Procedural components, abstract data types and concrete data objects. Both procedural components and abstract data types can be parameterized in many Object-Oriented languages. Specifications for reuse of these components are discussed in detail in this paper. The reusable software components and their specifications will form a reusable software library, and the information extracted from the specifications forms a knowledge base. Based on the knowledge base and the reusable software library, a new software development paradigm with software reusability can be realized.

<div class="section abstract"><div class="htmlview paragraph">Using a Model-based approach to the embedded software development process contributed significantly in reducing the development time while also supporting a high quality level of the software code implementation. However, based on our experience with CNH Industrial application scenarios, involving multiple suppliers from vehicle ECU to the engine ECU, it only addressed the need of the implementation phase without any consistent influence in other software development life-cycle phases such as requirements and specification.</div><div class="htmlview paragraph">Mandatory functional safety requirements, new complex functionalities, and reducing time to delivery while maintaining high quality level of software are driving factors in our new software development projects. Ideally the adoption of international standards, as for example the ISO 12007, and the safety standards, as the ISO 26262, ISO 25119 and ISO 13849, should represent a consistent guide to develop software. In this approach, the adoption of them should satisfy both the development guidelines and recommendations while at the same time to meeting application scenario requirements. A new way of thinking of functional safety projects is based on the concept that the software is the evolution of semi-finished product, on which each actor, System Engineer and Software Engineer, introduces added value. Further the exchange between phases (roles) will allow for a more fluid, iterative exchange of work products avoiding a ridge formal structure.</div><div class="htmlview paragraph">Therefore, the model-based approach should be extended to other areas such as System Engineering, that today seems to be an island where the time is stopped. In other words, Model-Based is important, even mandatory, for the full application of the concept of executable specification. For the adoption of external automation tools each tool should have an internal sponsor who balances the timing and budget constraints of adoption against the eventual cost reduction. An appropriate customization timeline should be evaluated before their introduction in the current Sw development process.</div></div>

Performance and power evaluation of C++ object-oriented programming in embedded processors

<div class="section abstract"> <div class="htmlview paragraph">This Recommended Practice provides a procedure for measuring and documenting the aerodynamic performance in a full-scale wind tunnel of passenger vehicles, i.e., mass-produced cars and light-duty trucks intended primarily for individual consumers. Testing or numerical modeling of pre-production and/or reduced-scale models is outside the scope of this document. Aerodynamic <i>development</i> procedures, i.e., methods to improve or optimize aerodynamic performance, are also excluded.</div> <div class="htmlview paragraph">It is well-known that aerodynamic performance results depend significantly on vehicle content and loading, as well as the wind tunnel itself (type, scale, and simulation qualities of the wind tunnel). Publication of non-standard test results causes unnecessary additional development work and incorrect perception of a vehicle’s anticipated aerodynamic performance by government, academia, and the general public.</div> <div class="htmlview paragraph">The intent of this document is to promote uniformity and traceability of published aerodynamic performance data acquired in a wind tunnel, thereby enhancing the public reputation and credibility of the aerodynamics discipline in the total vehicle development process.</div> <div class="htmlview paragraph">Measurement of the aerodynamic performance according to this Recommended Practice requires a full-scale wind tunnel test on a production-ready, full-scale vehicle according to specifications for vehicle loading, content, and wind tunnel conditions.</div> <div class="htmlview paragraph">The measurement and resulting documentation for a particular vehicle shall be reported only by the company that intends to produce the vehicle. Whenever there is an opportunity for interpretation of the document, a good faith effort shall be made to obtain the vehicle’s typical in-service performance and avoid finding the best possible performance under the best possible circumstances.</div> <div class="htmlview paragraph">Use of and compliance with this Recommended Practice is voluntary; however, it is mandatory for those advertising or otherwise publishing aerodynamic performance as “measured according to SAE J2881.” Conversely, any advertised or otherwise published result carrying this or a substantially similar designation must have the necessary documentation accepted by and on file with the SAE in accordance with the procedures defined in this Recommended Practice.</div> <div class="htmlview paragraph"><span class="xref">Appendices B</span> and <span class="xref">C</span> contain the necessary submittal documents for compliance with this Recommended Practice. When a submittal is made, the chairman of the Road Vehicle Aerodynamics Forum Committee (RVAC) or his/her designee shall review the submittal for proper completion according to the requirements herein, but without consideration of the technical merit of the claimed performance. After the chairman’s review, SAE will maintain an electronic database of all submittals.</div> <div class="htmlview paragraph">The database shall be available only to members and liasion members of the RVAC. Any RVAC member who retrieves information from the database shall do so with the understanding that the information is to be considered confidential within his or her company.</div></div>

<div class="section abstract"><div class="htmlview paragraph">The development and the test of complex electronic control units for power train control systems (with focus on DCT transmission control) requires a well established, functional and feasible development process and modern development tools to fulfil all target requirements including cost and project time requirements. This development tasks are no longer imaginable without the usage of simulation tools. Whereat simulation has been used for Hardware-In-Loop (HIL) testing and the software has been and hand-written for years, simulation tools become more important in all areas of development. In fields like system development, software development, software testing and software calibration, simulation tools are used to improve the execution of development tasks.</div><div class="htmlview paragraph">This paper describes the implementation of a tool-driven and model-based software development process with focus on the model-based software design and testing possibilities as well as the usage of profound simulation capabilities and the preparation of the development process for the development of functional safety according ISO 26262. Based on examples from existing development projects for double clutch transmission control systems, the implementation of the development process and the usage of software tools will be shown.</div></div>

<div class="htmlview paragraph">The design objective of the Spicer S400-S axle program was to develop a light weight, lower torsional vibration, long life tandem drive axle for the heavy truck industry. This was accomplished with the incorporation of a number of new product features and technical advancements, both in design and manufacturing. These include:</div> <div class="htmlview paragraph"> <ul class="list disc"> <li class="list-item"> <div class="htmlview paragraph">reduced standouts for improved interaxle driveline angles</div> </li> <li class="list-item"> <div class="htmlview paragraph">use of finite element analysis</div> </li> <li class="list-item"> <div class="htmlview paragraph">fixed pinion mounting</div> </li> <li class="list-item"> <div class="htmlview paragraph">optimization of lube flow and direction of lubrication</div> </li> <li class="list-item"> <div class="htmlview paragraph">optimized gear design for improved strength and noise reduction.</div> </li> </ul> </div> <div class="htmlview paragraph">This paper focuses on these features and also on the development process for the axle, including the use of simultaneous engineering. Utilizing simultaneous engineering, the S400-S was developed from concept to full production in fifteen months.</div>

Smalltalk is an object-oriented language (Ingalls78, KayGoldberg77, Hewitt73). PIE is a subsystem that extends Smalltalk's descriptive power by supporting the creation, storage, retrieval and manipulation of network structures (GoldsteinBobrow80a,b,c; BobrowGoldstein80). These networks have been employed to represent software, documentation, electronic mail, calendars, people, addresses, bibliographic references and other items that together comprise the personal information space of a user of an office information system. By employing a common network representation, PIE supports an integrated environment for software development and office-related tasks. PIE has been developed collaboratively with Dan Bobrow, and is presently being used on an experimental basis by a small community at Xerox PARC. Smalltalk represents entities in the external world as objects. An object has a state—i.e. an assignment of values to a set of state variables—and a class. The class of an object defines the behavior of the object in terms of a set of methods. Thus the class is a generic description of a collection of objects, while the objects associated with a class provide a particular description of the state of individual instances.

<div class="htmlview paragraph">Variable Valve Timing (VVT) strategy on both intake and exhaust valves has a pivotal influence on the specific fuel consumptions and engine performance. In addition to this, fuel economy can also be enhanced by the application of Variable Compression Ratio (VCR) strategy.</div> <div class="htmlview paragraph">This paper presents three possible strategies to enhance fuel economy improvement:</div> <div class="htmlview paragraph"> <ul class="list disc"> <li class="list-item"><div class="htmlview paragraph">A possible VVT strategy Early Intake Valve Opening (EIVO) and Late Exhaust Valve Closure (LEVC) that alters the valve overlap to reduce fuel consumption</div> </li> <li class="list-item"><div class="htmlview paragraph">A two-position VCR system that improves fuel conversion factor to realize fuel economy</div> </li> <li class="list-item"><div class="htmlview paragraph">A strategy that combines above two technologies to produce a complementary effect on fuel economy</div> </li> </ul> </div> <div class="htmlview paragraph">All three strategies have been tested on a 1.8L DOHC four cylinder PFI engine. AVL BOOST a 1D engine gas exchange and cycle simulation code was used to model this engine to get fuel economy gains at part-load points. Therefore, the simulation provided essential information to understand engine thermodynamic process and VVT system development.</div>

Object-oriented programming is a practical and useful programming methodology that encourages modular design and software reuse. Most object-oriented programming languages support data abstraction by preventing an object from being manipulated except via its defined external operations. In most languages, however, the introduction of inheritance severely compromises the benefits of this encapsulation. Furthermore, the use of inheritance itself is globally visible in most languages, so that changes to the inheritance hierarchy cannot be made safely. This paper examines the relationship between inheritance and encapsulation and develops requirements for full support of encapsulation with inheritance.

The software development process (SDP) contains many variables depending on the methodology chosen. Software development methodologies such as Agile or Waterfall can specify how and in what sequence software is developed. However, the SDP remains a hot topic among practitioners and academics, who seek to clarify the key aspects that influence the successful implementation of the SDP. As the SDP is a dynamic and knowledge-intensive business process (BP), one of its most impact components is the human factor (HF). It is difficult to predict how the HF impacts the sequence and results of SDP implementation. This paper proposes a new approach to investigate the impact of the HF on the SDP through the perspectives of different software development methodologies. The advantages and novelties of this approach include modelling HF uncertainties through their fuzzification in SDP activities, modelling different SDP methodologies using a case-handling approach, and simulating a dynamic, case-based SDP with real HF-related data collected from several IT organizations. The results show that the impact of the HF on SDP performance differs across the Waterfall and Agile methodologies. The results also allow researchers and practitioners working on software development projects to familiarize themselves with the impact of the HF on different SDPs, and to assess the degree of development risk associated with the SDP depending on the methodology chosen.