Software components-a scalable solution to platform independent software development for commercial applications

2003 ◽  
Author(s):  
D.E. Donzelli ◽  
D.R. Greening
Keyword(s):  
Software Development ◽  
Software Components ◽  
Commercial Applications

Recent trends in Component Based software development and Efficiency analysis of Semantic search based component retrieval Technique

2018 ◽  
pp. 105-113 ◽  
Author(s):  
Vishnu Sharma ◽  
Vijay Singh Rathore
Keyword(s):  
Software Development ◽  
Efficiency Analysis ◽  
Software Components ◽  
High Demand ◽  
Component Retrieval ◽  
Software Developer ◽  
Software Libraries ◽  
Retrieval Technique ◽  
Executable File ◽  
Recent Trends

In these days most of the software development uses preexisting software components. This approach provides plenty of benefits over the traditional development. Most of the software industries uses their own domain based software libraries where components resides in the form of modules, codes, executable file, documentations, test plans which may be used as it is or with minor changes. Due to shrinking time and high demand of software development it is necessary to use pre tested software components to ensure high functionality in software developed. Software components can be used very easily and without having the worries of errors and bugs because these are developed under expert supervision and well tested. What we have to do is just embed these components in our project. In this paper a survey got conducted over 112 software developer,testers and freelancers. In survey several issues in CBSD were identified. An efficient repository along with a component search engine is developed. All the component retrieval techniques were evaluated and compared with precise and recall method.

THE DEVELOPMENT OF AN OBJECT-ORIENTED SYSTEM WHICH INTEGRATES SIMULATION AND RECONSTRUCTION WITHIN A COMMON FRAMEWORK

1995 ◽  
Vol 06 (04) ◽  
pp. 481-488
Author(s):  
PAUL FUCHS
Keyword(s):  
Software Development ◽  
Object Oriented ◽  
Real Data ◽  
Design Strategy ◽  
Interface Problems ◽  
Software Components ◽  
Overall Design ◽  
Common Framework ◽  
Development Phases ◽  
Oriented System

A common problem for small experiments is that the design of the data acquisition, the simulation of the experiment and the reconstruction and analysis of real data is broken up into several disjoint development phases. Software development is necessary in all phases, yet continuity and an overall design strategy is lacking. This leads to duplication of software components and interface problems from one phase to the next and prohibits the generation of code which is reusable over the lifetime of many experiments. We address this problem within an object-oriented paradigm.

A REPOSITORY FOR COMPONENT-BASED EMBEDDED SOFTWARE DEVELOPMENT

2006 ◽  
Vol 16 (04) ◽  
pp. 523-552 ◽  
Author(s):  
TONG GAO ◽  
HUI MA ◽  
I-LING YEN ◽  
LATIFUR KHAN ◽  
FAROKH BASTANI
Keyword(s):  
Software Development ◽  
Code Generation ◽  
Embedded Software ◽  
Software Systems ◽  
Software Components ◽  
Search Results ◽  
Component Based Development ◽  
Specification Method ◽  
On Line ◽  
Effective Component

The rapid growth in the demand for embedded systems and the increased complexity of embedded software pose an urgent need for advanced embedded software development techniques. Software technology is shifting toward semi-automated code generation and integration of systems from components. Component-based development (CBD) techniques can significantly reduce the time and cost for developing software systems. Furthermore, effective component retrieval is a fundamental issue in CBD. In this paper, we address the issues in designing software repositories for embedded software components. We develop an On-line Repository for Embedded Software (ORES) to facilitate component management and retrieval. ORES uses an ontology-based approach to facilitate repository browsing and effective search. To allow easy browsing of ORES, we analyze the typical ontology relations for software components and develop a Merging and Echoing technique to convert the ontology into a hierarchy suitable for browsing, but without the loss of any critical semantic information contained in the ontology. We also develop an algorithm for grouping search results based on the ontology. Thus, we can display search result groups to avoid having to display a large number of search results or having to prune the results and risk reducing the recall factor. Another important aspect in embedded software is the set of nonfunctional requirements and properties. In ORES, we develop an XML-based specification method to capture nonfunctional properties as well as functional characteristics of components and enable retrieval of relevant components based on these specifications.

INTERACTION-ORIENTED SOFTWARE DEVELOPMENT

2001 ◽  
Vol 11 (03) ◽  
pp. 259-279 ◽  
Author(s):  
MICHAEL N. HUHNS
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Components ◽  
New Approach ◽  
Reusable Software ◽  
Current State ◽  
Computational Paradigm ◽  
And Behavior

This paper describes a new approach to the production of robust software. We first motivate the approach by explaining why the two major goals of software engineering — correct software and reusable software — are not being addressed by the current state of software practice. We then describe a methodology based on active, cooperative, and persistent software components, i.e., agents, and show how the methodology produces robust and reusable software. We derive requirements for the structure and behavior of the agents, and report on preliminary experiments on applications based on the methodology. We conclude with a roadmap for development of the methodology and ruminations about uses for the new computational paradigm.

scholarly journals General guidelines for biomedical software development

F1000Research ◽  
2017 ◽  
Vol 6 ◽  
pp. 273 ◽  
Author(s):  
Luis Bastiao Silva ◽  
Rafael C. Jimenez ◽  
Niklas Blomberg ◽  
José Luis Oliveira
Keyword(s):  
Software Development ◽  
Biomedical Applications ◽  
Development Process ◽  
Software Components ◽  
Specific Topic ◽  
Software Developers ◽  
Vast Number ◽  
Software Applications ◽  
New Strategies

Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

scholarly journals Improvement of the Two-Hemisphere Model-Driven Approach for Generation of the UML Class Diagram

2013 ◽  
Vol 14 (1) ◽  
pp. 19-30 ◽  
Author(s):  
Oksana Nikiforova ◽  
Konstantins Gusarovs ◽  
Olegs Gorbiks ◽  
Natalja Pavlova
Keyword(s):  
Software Development ◽  
Business Process ◽  
Automatic Generation ◽  
Class Diagram ◽  
Software Components ◽  
The Real ◽  
Model Driven ◽  
Uml Class Diagram ◽  
Model Driven Approach ◽  
The Way

Abstract In this paper an ability to apply the two-hemisphere model-driven approach for creation of the UML class diagram is discussed and the way to avoid the limitations of the approach is offered. The result of the proposed improvement of the twohemisphere model-driven approach is the increased number of elements of the UML class diagram available for automatic generation and several statements for semi-automatic transformation of business process diagram and the concept diagram into software components. As a result, the authors can ascertain that it is possible to apply the improved twohemisphere model-driven approach in practice in the real software development, and not only for academic purpose.

A Case Study of Ontology-Driven Development of Intelligent Educational Systems

2011 ◽  
pp. 79-94
Author(s):  
Gordon Deline ◽  
Fuhua Lin ◽  
Dunwei Wen ◽  
Dragan Gaševic ◽  
Kinshuk N/A
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Ontology Development ◽  
Educational Systems ◽  
Software Components ◽  
Review Of Literature ◽  
Driven Systems ◽  
Model Driven ◽  
Development Methodology

This article presents a case study of ontology-driven development of intelligent educational systems. Following a review of literature related to ontology development, ontology-driven software development, and traditional software engineering, we developed an ontology-driven software development methodology appropriate for intelligent ontology-driven systems which have ontologies as key execution components, such as e-Advisor, and which is biased toward an integration of incremental and iterative ontology development and downstream Model Driven Architecture for development of software components.

Requirements to Products and Processes for Software of Safety Important NPP I&C Systems

2022 ◽  
pp. 212-246
Author(s):  
Vladimir Sklyar ◽  
Andriy Volkoviy ◽  
Oleksandr Gordieiev ◽  
Vyacheslav Duzhyi
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Verification ◽  
Software Requirements ◽  
Software Components ◽  
Software Life Cycle ◽  
Regulatory Documents ◽  
And Control

Features of software as a component of instrumentation and control (I&C) systems are analyzed. Attention is paid to the importance of functions performed by software and hazards of such software. Requirements for characteristics of software as a component of I&C systems are analyzed. Different regulatory documents are considered in order to disclose common approaches to the use of dedicated software and off-the-shelf software components. Classification of software, as well as classification of requirements, is described. Criteria of selection and structuring of requirements, as well as criteria for software verification, are defined. As long as the characteristics of software components directly depend on the quality of the processes of software development and verification, requirements for software life cycle processes are considered.

Component-based software development for integrated construction management software applications

2001 ◽  
Vol 15 (2) ◽  
pp. 173-187 ◽  
Author(s):  
FENIOSKY PEÑA-MORA ◽  
SANJEEV VADHAVKAR ◽  
SIVA KUMAR DIRISALA
Keyword(s):  
Software Development ◽  
Construction Management ◽  
Design Patterns ◽  
Development Process ◽  
Software Components ◽  
Design Rationale ◽  
Software Development Process ◽  
Software Application ◽  
Software Applications ◽  
Specific Implementation

This paper presents a framework and a prototype for designing Integrated Construction Management (ICM) software applications using reusable components. The framework supports the collaborative development of ICM software applications by a group of ICM application developers from a library of software components. The framework focuses on the use of an explicit software development process to capture and disseminate specialized knowledge that augments the description of the ICM software application components in a library. The importance of preserving and using this knowledge has become apparent with the recent trend of combining the software development process with the software application code. There are three main components in the framework: design patterns, design rationale model, and intelligent search algorithms. Design patterns have been chosen to represent, record, and reuse the recurring design structures and associated design experience in object-oriented software development. The Design Recommendation and Intent Model (DRIM) was extended in the current research effort to capture the specific implementation of reusable software components. DRIM provides a method by which design rationale from multiple ICM application designers can be partially generated, stored, and later retrieved by a computer system. To address the issues of retrieval, the paper presents a unique representation of a software component, and a search mechanism based on Reggia's setcover algorithm to retrieve a set of components that can be combined to get the required functionality is presented. This paper also details an initial, proof-of-concept prototype based on the framework. By supporting nonobtrusive capture as well as effective access of vital design rationale information regarding the ICM application development process, the framework described in this paper is expected to provide a strong information base for designing ICM software.

Sign in / Sign up

Export Citation Format

Share Document