1,545 research outputs found

    Reuse of use cases diagrams: an approach based on ontologies and semantic web technologies

    Get PDF
    Software reuse is defined as the use of any artifact, or part thereof, created before, on a new Project. This practice has significant benefits in reducing costs and increasing quality and productivity in software development. Numerous approaches have been proposed aimed mostly at the source code reuse, but this type of reuse has its limitations because development platforms and technologies are constantly changing. Then, it is necessary to apply reuse over software artifacts created at higher levels of software life cycle such as requirements specification. This paper presents a tool for the reuse of use case diagrams by storing their information in OWL ontology and the use of Semantic Web technologies.Software reuse is defined as the use of any artifact, or part thereof, created before, on a new Project. This practice has significant benefits in reducing costs and increasing quality and productivity in software development. Numerous approaches have been proposed aimed mostly at the source code reuse, but this type of reuse has its limitations because development platforms and technologies are constantly changing. Then, it is necessary to apply reuse over software artifacts created at higher levels of software life cycle such as requirements specification. This paper presents a tool for the reuse of use case diagrams by storing their information in OWL ontology and the use of Semantic Web technologies

    Towards a re-engineering method for web services architectures

    Get PDF
    Recent developments in Web technologies – in particular through the Web services framework – have greatly enhanced the flexible and interoperable implementation of service-oriented software architectures. Many older Web-based and other distributed software systems will be re-engineered to a Web services-oriented platform. Using an advanced e-learning system as our case study, we investigate central aspects of a re-engineering approach for the Web services platform. Since our aim is to provide components of the legacy system also as services in the new platform, re-engineering to suit the new development paradigm is as important as re-engineering to suit the new architectural requirements

    The Bioperl toolkit: Perl modules for the life sciences

    Get PDF
    The Bioperl project is an international open-source collaboration of biologists, bioinformaticians, and computer scientists that has evolved over the past 7 yr into the most comprehensive library of Perl modules available for managing and manipulating life-science information. Bioperl provides an easy-to-use, stable, and consistent programming interface for bioinformatics application programmers. The Bioperl modules have been successfully and repeatedly used to reduce otherwise complex tasks to only a few lines of code. The Bioperl object model has been proven to be flexible enough to support enterprise-level applications such as EnsEMBL, while maintaining an easy learning curve for novice Perl programmers. Bioperl is capable of executing analyses and processing results from programs such as BLAST, ClustalW, or the EMBOSS suite. Interoperation with modules written in Python and Java is supported through the evolving BioCORBA bridge. Bioperl provides access to data stores such as GenBank and SwissProt via a flexible series of sequence input/output modules, and to the emerging common sequence data storage format of the Open Bioinformatics Database Access project. This study describes the overall architecture of the toolkit, the problem domains that it addresses, and gives specific examples of how the toolkit can be used to solve common life-sciences problems. We conclude with a discussion of how the open-source nature of the project has contributed to the development effort

    Developing Engineering Learning Objects Online Portal with LabVIEW and an Open Source Web Content Management System

    Get PDF
    Learning objects (LOs) are independent chunks of knowledge normally used for instructional or learning purposes. LOs are normally reusable in the sense that they can be adopted and adapted for various learning and instructional scenarios. They are also tagged with metadata which includes descriptive information allowing them to be used and searched easily. LOs are sometimes metaphored as being a LEGO. Examples of LOs could contain multimedia content, instructional content, learning objectives, instructional software and software tools, and computer simulations. Many LOs are designed to be mediated online. In engineering education, computer simulations based learning objects could be the most beneficial for conveying hard engineering concepts for the engineering science learner. Computer simulations have been reported to facilitate conceptual understanding and leaving positive impact on students learning in numerous number of engineering education research articles. In the last two decades, many software packages have been developed for enhancing the engineering design and analysis process, examples are Matlab/Simulink, PSpice, LabVIEW, etc. These has been used consequently by academics for enhancing their students learning. LabVIEW is one of the most versatile computer software packages. It is used comprehensively in the industry as well as in academia. LabVIEW started as computer software interface of PC based data question equipments, however, it has grown much beyond that offering comprehensive toolkits and already implemented functions. Also it has great connectivity facilities with Matlab/Simulink, C++, and Visual Basic allowing communicating already developed codes in the latter with its core engine. The other important specification of LabVIEW is its embedded internet tools enabling publishing its programmed GUIs on the world wide web in easy and handy way. Web content management systems is the third generation of web publishing applications after HTML and web authoring software packages such as FrontPage and Dreamweaver. It is used to manage and control a large, dynamic collection of Web material (HTML documents and their associated images). A WCMS facilitates content creation, content control, editing, and many essential Web maintenance functions. In contrast with the web development tools such as HTML, FrontPage, Dreamweaver, etc., a CMS enables faster development, cost effectiveness, and online flexibility. The basic idea of any web content management system is that a non-technical person often needs to be able to keep their own website up-to-date without having to call on a web developer to make changes every time. Of course there are some things that can only be done by a web developer, but for simpler tasks such as changing the wording of a paragraph, it is an unnecessary burden and expense for both parties if you have to get a developer to make the changes. This paper provides an A to Z prescription of implementing a standardized Learning Objects online portal. This describing in detail a LabVIEW based Learning Object architecture, using a proper IEEE LOM metadata generation tool, and finally how on the top of that a Joomla web content management system can be used for developing the online portal

    Constructing and Validating Feature Models Using Relational, Document, and Graph Databases

    Get PDF
    Building a software product line (SPL) is a systematic strategy for reusing software within a family of related systems from some application domain. To define an SPL, a domain analyst must identify the common and variable aspects of a family of systems and capture them for later use in construction of specific products. To do so, Feature-Oriented Domain Analysis (FODA) introduced the feature model as an abstraction to represent the common and variable aspects, using a feature diagram to depict the model visually. However, this abstraction is often difficult for developers to use because most tools rely on specialized theories, notations, or technologies

    Web service composition: A survey of techniques and tools

    Get PDF
    Web services are a consolidated reality of the modern Web with tremendous, increasing impact on everyday computing tasks. They turned the Web into the largest, most accepted, and most vivid distributed computing platform ever. Yet, the use and integration of Web services into composite services or applications, which is a highly sensible and conceptually non-trivial task, is still not unleashing its full magnitude of power. A consolidated analysis framework that advances the fundamental understanding of Web service composition building blocks in terms of concepts, models, languages, productivity support techniques, and tools is required. This framework is necessary to enable effective exploration, understanding, assessing, comparing, and selecting service composition models, languages, techniques, platforms, and tools. This article establishes such a framework and reviews the state of the art in service composition from an unprecedented, holistic perspective

    XML Integrated Environment for Service-Oriented Data Management

    Get PDF
    The proliferation of XML as a family of related standards including a markup language (XML), formatting semantics (XSL style sheets), a linking syntax (XLINK), and appropriate data schema standards have emerged as a de facto standard for encoding and sharing data between various applications. XML is designed to be simple, easily parsed and self-describing. XML is based on and support the idea of separation of concerns: information content is separated from information rendering, and relationships between data elements are provided via simple nesting and references. As the XML content grows, the ability to handle schemaless XML documents becomes more critical as most XML documents do not have schema or Document Type Definitions (DTDs). In addition, XML content and XML tools are often required to be combined in effective ways for better performance and higher flexibility. In this research, we proposed XML Integrated Environment (XIE) which is a general-purpose service-oriented architecture for processing XML documents in a scalable and efficient fashion. The XIE supports a new software service model that provides a proper abstraction to describe a service and divide it into four components: structure, connection, interface and logic. We also proposed and implemented XIE Service Language (XIESL) that can capture the creation and maintenance of the XML processes and the data flow specified by the user and then orchestrates the interactions between different XIE services. Moreover, XIESL manages the complexity of XML processing by implementing an XML processing pipeline that enables better management, control, interpretation and presentation of the XML data even for non-professional users. The XML Integrated Environment is envisioned to revolutionize the way non-professional programmers see, work and manage their XML assets. It offers them powerful tools and constructs to fully utilize the XML processing power embedded in its unified framework and service-oriented architecture

    A Software Reuse Paradigm for the Next Generation Network (NGN)

    Get PDF
    MSc thesis - Faculty of EngineeringService creation in the Next Generation Network (NGN) is focused around software creation and borrows heavily from the Software Engineering community. In the NGN, telecommunication companies demand simple, rapid and economical service creation. The key to this type of service creation is software re-use. Software re-use is a conundrum where limited, dedicated solutions exists. These solutions include amongst others Enterprise JavaBeansTM (EJBs), design patterns and object-oriented programming. The Telecommunications Information Networking Architecture- Conformance And Testing (TINA-CAT) workgroup has done work on a functionality centric concept called RP-facets. This report proposes a redefinition of RP-facets, as Facets, for software re-use across the design and code level. We redefine Facets as functionality centric reusable components. A Facet is independent of the implementation language and the execution platform. Facets allow containment in a structured manner via a user defined Facet Hierarchy. Facets are resource, context and data agnostic. They also introduce a structured way to allow source code to be changed based on design level decisions. Also, possessing the ability to allow the simultaneous use of other reuse solutions and programming paradigms. Abstraction of detail from developers and platform migration can be achieved by using Facets. Facets are composed of a Generic definition and any number of Implementation definitions. The definitions are supported by an underlying informational model called meta-¼. Meta- ¼ is a model at the M3 meta-level that focuses on describing entities. Most of the Facet’s capabilities are enabled by the meta-¼ model. An environment for developing Facets is created, called the Facet Development Environment (FDE). The Facet Developer (FD) role is introduced to develop and maintain Facets. The FD verifies programmes from programmers to be included into the catalogue of Facets via the FDE. The FD interacts with service creation teams to determine which Facets can be used in the service they wish to develop. Facets prove their capability in targeted areas, yet lack in other categories. It is recommended that the underlying informational model should be revised to form a more robust and flexible entity describing model. In addition, a cataloging capability to easily find Facets with particular functionality should be appended to the capabilities of the facet. It is proposed, for future work, that a development environment be created that encompasses a process for using Facets to create services

    JDBC demonstration courseware using Servlets and Java Server Pages

    Get PDF
    corecore