Efficiency Of Software Development Research Articles

Objects-First Vs. Structures-First Approaches To 00 Programming Education: A Replication Study

One of the essential elements of a successful organization is information technology, which has as its basis effective and efficient software development. The foundation of software development is computer programming. The last decade of computer programming education has been dominated by the object-oriented paradigm. While recent anecdotal accounts among computer science and computer information systems educators have often favored the objects-first approach to programming instruction (vis-a-vis the structures-first approach), very little empirical evidence has been offered. A field study by Johnson and Moses (2008) suggested that the objects-first approach is superior, but the experimental design was open to criticism. This replication study significantly improves upon the experimental design yielding results that indicate neither the objects-first or the structures-first approach is preferred. While an inconclusive result may seem unimportant, it does provide needed guidance to educators to make pedagogical decisions based on other perhaps more important factors to help ensure the students' success. On the positive side, the study does suggest that learning object-oriented programming is more difficult for novices than learning procedural programming, which is also important for programming educators.

A reusable design of geophysical data acquisition software

This article analyzes the level and variability of abstract models in geophysical data acquisition system, and designs a cross-platform and reusable geophysical data acquisition software framework using the pipe-filter pattern and abstract factory pattern, based on the modern software engineering, and improves the efficiency of such software development. The framework has been firstly applied in the wide filed electromagnetic system and got a good result. It has a great prospect and application value.

On Data Integration, Warehousing and Software Reuse in the Construction of Digital Campus: A Review on Performance

Construction of digital campus can greatly enhance the resource planning and management in universities and colleges. Performance is important for the construction of digital campus as well as the modeling of process. This paper analyzed the utilizing of the portal and systems in a typical digital campus system. Technologies in the software engineering process such as warehousing and software reuse are analyzed in the aspect of performance. It's concluded that although appropriate reuse in software engineering can enhance the efficiency of software development, abusing of reusing can cause the low efficiency of the whole software system. At the other hand, good data integration and warehousing can greatly improve the efficiency of such a global system in a university.

Design of the management system of university projects based on UML sequence diagram

Analysis and design of the management system of university projects is based on UML sequence diagram. It is usercentric. It describes the object from the dynamic point of view and illustrates the interaction process of the objects with the time change. This design can support all intermediate program language. At the same time, the correct use of it will reduce system complexity and improve software development efficiency and portability.

New method for component reuse

Component Object Model (COM) defines two approaches: Containment and aggregation concentrating on the consumer perspectives for component reuse,which is not favorable to the self-evolution of component and separation of concerns. A new method for component reuse was proposed. First,a new component class was derived directly from an old component. The derived class reused base class's interfaces and events,overloaded virtual interface methods,and defined new interfaces and events. Second,identifiable features were as taken the well defined semantic entities,so that they could be bound to other component at compile or run time. The design and implementation methods on middleware platform were presented. The mobile telephone projects experiments show that the new method contributes to improving software development efficiency and increasing the quality of software systems.

Business Rule Management Framework for Enterprise Web Services

Making a business rule extraction more dynamic is an open issue, and we think it is feasible if we decompose the business process structure in a set of rules, each of them representing a transition of the business process. As a consequence the business process engine can be realized by reusing and integrating an existing Rule Engine. We are proposing a way for extracting the business rules and then to modify it at the runtime. Business rules specifies the constraints that affect the behaviors and also specifies the derivation of conditions that affect the execution flow. The rules can be extracted from use cases, specifications or system code. But since not many enterprises capture their business rules in a structured, explicit form like documents or implicit software codes, they need to be identified first, before being captured and managed. These rules change more often than the processes themselves, but changing and managing business rules is a complex task beyond the abilities of most business analysts. The capturing process focuses on the identification of the potential business rules sources. As business logic requirements change, business analysts can update the business logic without enlisting the aid of the IT staff. The new logic is immediately available to all client applications. In current trend the rules are modified or changed in the static time phase. But this paper provides to change the rules at the run time. Here the rules are extracted from the services and can be a changed dynamically. The existing rules are modified and attached to source code without hindering service to the end user which can be achieved with source control systems. When the rules are revised, it provides a path in budding new business logic. This new business logic can be adopted for the efficient software development.

객체지향모델링 과정에서 계층적 유즈케이스(Use Case) 분석을 통한 클래스 도출 및 정의

Use case diagram is used for defining inter-action between users and systems in object-oriented modeling. It is very important to defining users` requirements for efficient software development. In this paper, we propose a object-oriented modeling process using hierarchical use case analysis for designing class model. First, We define many use case diagrams by several hierarchical modeling level. And next, we can also design class model using the use case diagrams. Our proposed modeling process provides interaction between use case model and class model. That can make us to check the modeling process during the software development. Using the proposed object-oriented modeling we can develop software based on users` requirements. It is very useful for class modeling.

From integration to composition: On the impact of software product lines, global development and ecosystems

Three trends accelerate the increase in complexity of large-scale software development, i.e. software product lines, global development and software ecosystems. For the case study companies we studied, these trends caused several problems, which are organized around architecture, process and organization, and the problems are related to the efficiency and effectiveness of software development as these companies used too integration-centric approaches. We present five approaches to software development, organized from integration-centric to composition-oriented and describe the areas of applicability.

Efficient software development and verification in an Autosar tool chain

The Autosar standard, which has now been successfully introduced, defines an exchange format that simplifies the interactions between tools used for behavior modeling and architecture design. Drawing on practical experi- ence with the Autosar standard, this article will demonstrate how an efficient Autosar development process can be set up by using a precisely coordinated tool chain and well-defined workflows. dSpace provides the System- Desk and TargetLink tools for this.

Understanding the effectiveness of Capability Maturity Model Integration by examining the knowledge management of software development processes

Capability Maturity Model Integration (CMMI) is one of the well-known models that provide best practices for software quality improvement. Many articles praise the benefits of CMMI adoption, such as enhanced knowledge management of software development, improved software quality and increased efficiency of software development. However, these intangibles, especially those relating to knowledge management, have not been investigated yet. To build a deeper understanding of CMMI this paper intends to investigate the effectiveness of CMMI by examining the impact of quality management on the knowledge management of software development processes. A case study approach was employed to collect complete information of the impact of CMMI on software knowledge management from different aspects. The results reveal that the incongruence between managing the knowledge of software development and managing the process of software knowledge management has created blind points in the adoption of the CMMI programme. In addition to complying with the CMMI prescriptive guidelines CMMI-adoption organisations would need to integrate knowledge from both internal and external customers.

Modeling genomic data with type attributes, balancing stability and maintainability

BackgroundMolecular biology (MB) is a dynamic research domain that benefits greatly from the use of modern software technology in preparing experiments, analyzing acquired data, and even performing "in-silico" analyses. As ever new findings change the face of this domain, software for MB has to be sufficiently flexible to accommodate these changes. At the same time, however, the efficient development of high-quality and interoperable software requires a stable model of concepts for the subject domain and their relations. The result of these two contradictory requirements is increased complexity in the development of MB software.A common means to reduce complexity is to consider only a small part of the domain, instead of the domain as a whole. As a result, small, specialized programs develop their own domain understanding. They often use one of the numerous data formats or implement proprietary data models. This makes it difficult to incorporate the results of different programs, which is needed by many users in order to work with the software efficiently. The data conversions required to achieve interoperability involve more than just type conversion. Usually they also require complex data mappings and lead to a loss of information.ResultsTo address these problems, we have developed a flexible computer model for the MB domain that supports both changeability and interoperability. This model describes concepts of MB in a formal manner and provides a comprehensive view on it. In this model, we adapted the design pattern "Dynamic Object Model" by using meta data and association classes.A small, highly abstract class model, named "operational model," defines the scope of the software system. An object model, named "knowledge model," describes concrete concepts of the MB domain. The structure of the knowledge model is described by a meta model. We proved our model to be stable, flexible, and useful by implementing a prototype of an MB software framework based on the proposed model.ConclusionStability and flexibility of the domain model is achieved by its separation into two model parts, the operational model and the knowledge model. These parts are connected by the meta model of the knowledge model to the whole domain model. This approach makes it possible to comply with the requirements of interoperability and flexibility in MB.

Refactoring C++ Programs Physically

This paper proposes physical refactoring and digs into its process and methods. Physical refactoring is a disciplined technique for restructuring the physical structure of a software system, to improve the efficiency of software development, while preserving the system’s external behavior. It follows the best practices of refactoring to change the system in small and iterative steps, and applies refactorings according to the standards of physical design. Case studies demonstrate that physical refactoring may continuously improve software quality from the viewpoint of the physical structure.

Efficient software development

Still today there is a hard break between development and testing processes of ECU software. Lifecycle Management can make a contribution to close this process gap for a more efficient development. Berner & Mattner features an approach which includes all processes from the specification of an ECU function to its test at the test bench. In doing so, the company deals with projects that already exist in part at German premium OEMs and their suppliers. Production vehicles launched in 2009 profit from the Lifecycle Management methods for the first time.

The Bazaar inside the Cathedral: Business Models for Internal Markets

Software product-line development lets organizations better optimize software development efficiency by building a shared set of assets for reuse in multiple products. This process introduces many challenges, not least of which is creating the initial set of reusable software assets. To accomplish this, organizations often establish a central software platform group. Such a group faces a serious problem: existing systems groups already have a large set of software components that they use to build their products. If companies are to successfully transition to product-line development, these systems groups must shift their investments from existing software components to the new reusable product-line assets. One way to encourage this is to create an internal open source software community that lets systems groups actively contribute their existing components to the platform. In OSS, a community works together to develop software. Because the software's users are part of the community, they can add the assets they need. Inner-source-software (ISS) development applies OSS within a limited environment that has a closed border (such as a company, a division, or a consortium). So, companies using the ISS approach essentially establish an OSS community within the confines of their organization.

The impact of knowledge delivery factors on New Product Development teams: a quantitative analysis of software development efficiency

This paper investigates the effects of knowledge delivery factors on New Product Development (NPD) teams with emphasis on software development efficiency and also examines the effects of company size and knowledge worker's experience on the knowledge delivery factors. Data were collected from 82 software development companies with headquarters in Canada and the USA and branches in Europe, Asia and Africa. Results obtained show that there is correlation between knowledge delivery factors and software development team efficiency; that the team efficiency could be increased if knowledge is delivered close to the time it is needed.

Impact of aspect-oriented programming on software development efficiency and design quality: an empirical study

The aspect-oriented programming (AOP) approach is supposed to enhance a system's features such as modularity, readability and simplicity. Owing to a better modularisation of crosscutting concerns, the developed system implementation would be less complex, and more readable. Thus, software development efficiency would increase, so the system would be created faster than its object-oriented programming (OOP) equivalent. An empirical study of a web-based system development is carried out to examine AOP against OOP approach with regard to software development efficiency and design quality. The study reveals that the AOP approach appears to be a fullfledged alternative to the pure OOP approach. Nevertheless, the impact of AOP on software development efficiency and design quality was not confirmed. In particular, it appeared that design quality metrics were not significantly associated with using AOP, instead of OOP. It is possible that the benefits of AOP will exceed the results obtained in the present study for experiments with larger number of subjects.

Desenvolvimento de software: uso da prototipação na fase de concepção do modelo de processo de software rup

Nowadays, to produce software with quality and efficiency is not just a desirable characteristic, but also a necessity for a software produst. The use of formalized software development process guarantee quality and efficiency to the software during the whole production life cycle of a system. This work has aimed at studing and applying a formalized appoach for software development, in this case, the RUP (Rational Unified Process), highlighting its advantages and main characteristic.

On the iterative solution of KKT systems in potential reduction software for large-scale quadratic problems

Iterative solvers appear to be very promising in the development of efficient software, based on Interior Point methods, for large-scale nonlinear optimization problems. In this paper we focus on the use of preconditioned iterative techniques to solve the KKT system arising at each iteration of a Potential Reduction method for convex Quadratic Programming. We consider the augmented system approach and analyze the behaviour of the Constraint Preconditioner with the Conjugate Gradient algorithm. Comparisons with a direct solution of the augmented system and with MOSEK show the effectiveness of the iterative approach on large-scale sparse problems.

What we learn from the study of ubiquitous processes

AbstractSoftware engineering has come to recognise the value of software processes as vehicles for addressing such goals as improved efficiency in software development, the achievement of improved product quality, and better coordination and communication of the members of software teams. Greater clarity, completeness, and precision in defining these processes seem to lead to greater effectiveness in pursuing these goals. The languages and notations used to support definition of such processes seem to be relatively successful in supporting these definitions, but more progress towards better languages and notations seems indicated. This article suggests that processes are also central to the effective pursuit of essential goals in a broad spectrum of other domains of human endeavour. We suggest that the study of how processes are used in those other domains to pursue goals that are essential in those domains can help us to reflect on our goals for the use of process in software development. Further, we suggest that observing the process language features that seem to facilitate the pursuit of goals in these other domains can similarly suggest features that would seem analogously important in languages used to support the definition of software processes. This article examines the use of processes in domains other than software development and uses observations about these processes to suggest desiderata for software development processes, and the languages used to define them. Copyright © 2007 John Wiley & Sons, Ltd.

EXTRACTING RELATIONS AMONG EMBEDDED SOFTWARE DESIGN PATTERNS

Pattern is a reusable description of knowledge. Efficient software development can be achieved by sharing and reusing knowledge using patterns and their relations. Because the manual analysis of re...