51,931 research outputs found

    The GENESIS platform, its distribution, and web services

    Get PDF
    The GENESIS project is developing an Open Source platform that supports co-operation and communication among software engineers belonging to distributed development teams involved in modeling, controlling, and measuring software development and maintenance processes. The GENESIS platform is made up of three main elements: a distributed workflow management system, a resource management system, and an artefact management system (OSCAR, developed at Durham). The platform is designed to be non-invasive and have a low barrier to entry (in terms of the effort required to begin using the system). This is accomplished, as far as possible, by adapting the platform to the workflow processes and tools already in place in an organisation. OSCAR (Open-Source Component Artefact Repository) is the artefact management system, used to store and retrieve any item produced by any member of a software engineering team. Traditional artefacts (documents and code, for example) as well as non-traditional items (such as informal annotations, mailing list postings, and personnel profiles) are managed by the system, which has the capability to maintain a rich set of relationships between the artefacts (for traceability and comprehension purposes). Each instance of OSCAR contains a software configuration management system (currently, a plugin is provided to use CVS). Currently, OSCAR is slightly distributed: the workflow management system can use more than one instance of a repository, but a single instance of OSCAR can use only one repository. There are a few known systems which provide some form of real distributed software configuration management, which, it is hoped, can be used to inspire further development of the distribution of OSCAR and its associated services. Initially, OSCAR and the rest of the GENESIS platform communicated using RMI, but a web service interface is currently under development. As an initial attempt at realising this, the RMI interface is simply wrapped to provide servlets. The web services approach allows for a single instance of an OSCAR repository to serve many projects, and for potential global distribution of a single instance of the GENESIS platform. Possible avenues for future work include: applications to e-learning and e-science (applying OSCAR to the Grid, in order to support educational and scientific collaboration); using OSCAR as a basis for supporting collaborative design work; instrumenting the tools in the GENESIS platform to provide data for studies of software engineering practices; and studying process models (for example, determining the difference between the ideal models defined in the literature and the real processes of software engineering)

    Pattern-based software architecture for service-oriented software systems

    Get PDF
    Service-oriented architecture is a recent conceptual framework for service-oriented software platforms. Architectures are of great importance for the evolution of software systems. We present a modelling and transformation technique for service-centric distributed software systems. Architectural configurations, expressed through hierarchical architectural patterns, form the core of a specification and transformation technique. Patterns on different levels of abstraction form transformation invariants that structure and constrain the transformation process. We explore the role that patterns can play in architecture transformations in terms of functional properties, but also non-functional quality aspects

    Quality-aware model-driven service engineering

    Get PDF
    Service engineering and service-oriented architecture as an integration and platform technology is a recent approach to software systems integration. Quality aspects ranging from interoperability to maintainability to performance are of central importance for the integration of heterogeneous, distributed service-based systems. Architecture models can substantially influence quality attributes of the implemented software systems. Besides the benefits of explicit architectures on maintainability and reuse, architectural constraints such as styles, reference architectures and architectural patterns can influence observable software properties such as performance. Empirical performance evaluation is a process of measuring and evaluating the performance of implemented software. We present an approach for addressing the quality of services and service-based systems at the model-level in the context of model-driven service engineering. The focus on architecture-level models is a consequence of the black-box character of services

    Semantic business process management: a vision towards using semantic web services for business process management

    Get PDF
    Business process management (BPM) is the approach to manage the execution of IT-supported business operations from a business expert's view rather than from a technical perspective. However, the degree of mechanization in BPM is still very limited, creating inertia in the necessary evolution and dynamics of business processes, and BPM does not provide a truly unified view on the process space of an organization. We trace back the problem of mechanization of BPM to an ontological one, i.e. the lack of machine-accessible semantics, and argue that the modeling constructs of semantic Web services frameworks, especially WSMO, are a natural fit to creating such a representation. As a consequence, we propose to combine SWS and BPM and create one consolidated technology, which we call semantic business process management (SBPM

    A Taxonomy of Workflow Management Systems for Grid Computing

    Full text link
    With the advent of Grid and application technologies, scientists and engineers are building more and more complex applications to manage and process large data sets, and execute scientific experiments on distributed resources. Such application scenarios require means for composing and executing complex workflows. Therefore, many efforts have been made towards the development of workflow management systems for Grid computing. In this paper, we propose a taxonomy that characterizes and classifies various approaches for building and executing workflows on Grids. We also survey several representative Grid workflow systems developed by various projects world-wide to demonstrate the comprehensiveness of the taxonomy. The taxonomy not only highlights the design and engineering similarities and differences of state-of-the-art in Grid workflow systems, but also identifies the areas that need further research.Comment: 29 pages, 15 figure

    Integration of BPM systems

    Get PDF
    New technologies have emerged to support the global economy where for instance suppliers, manufactures and retailers are working together in order to minimise the cost and maximise efficiency. One of the technologies that has become a buzz word for many businesses is business process management or BPM. A business process comprises activities and tasks, the resources required to perform each task, and the business rules linking these activities and tasks. The tasks may be performed by human and/or machine actors. Workflow provides a way of describing the order of execution and the dependent relationships between the constituting activities of short or long running processes. Workflow allows businesses to capture not only the information but also the processes that transform the information - the process asset (Koulopoulos, T. M., 1995). Applications which involve automated, human-centric and collaborative processes across organisations are inherently different from one organisation to another. Even within the same organisation but over time, applications are adapted as ongoing change to the business processes is seen as the norm in today’s dynamic business environment. The major difference lies in the specifics of business processes which are changing rapidly in order to match the way in which businesses operate. In this chapter we introduce and discuss Business Process Management (BPM) with a focus on the integration of heterogeneous BPM systems across multiple organisations. We identify the problems and the main challenges not only with regards to technologies but also in the social and cultural context. We also discuss the issues that have arisen in our bid to find the solutions

    Component Based System Framework for Dynamic B2B Interaction

    Get PDF
    Business-to-business (B2B) collaboration is becoming a pivotal way to bring today's enterprises to success in the dynamically changing, e-business environment. Though many business-to-business protocols are developed to support B2B interaction, none are generally accepted. A B2B system should support different B2B protocols dynamically to enable interaction between diverse enterprises. This paper proposes a framework for dynamic B2B interaction. A B2B transaction is divided into the interaction part and business implementation part to support flexible interaction. A component based system framework is proposed,to support the B2B transaction execution. To support. dynamic B2B services, dynamic component composition is required. Service and component notions are combined into a composable service component. The composition architecture is also presented
    • 

    corecore