Results 1 - 10
of
10
Process-Centered Software Engineering Environments - A Brief History and Future Challenges
, 2002
"... Software engineering environments have a history of about two decades. Early environments provided support for small fragments of the software process (usually focusing on programming-in-the small). Then there was a trend towards support for more complete software processes (from early phases like r ..."
Abstract
-
Cited by 21 (0 self)
- Add to MetaCart
Software engineering environments have a history of about two decades. Early environments provided support for small fragments of the software process (usually focusing on programming-in-the small). Then there was a trend towards support for more complete software processes (from early phases like requirements analysis and design down to testing and configuration management). Ten years ago the notion of process-centered software engineering environments initiated a new field in software engineering: software process research. The key idea is to use a model of a software process as input parameter for a software engineering environment. The environment is supposed to "behave" in accordance to the process model. Some aspects of this vision became true, others turned out to be of little practicability. In this article, we discuss the history of software engineering environments with a particular focus on process-centered software engineering environments (PCSEEs). We discuss the notion of distributed software processes (as one of the most substantial current trends in software process research) and we motivate the notion of a software process middleware which serves as basis of real-world software processes spread over various sites. In addition, we discuss some other trends in the software process research arena.
Logically Central, Physically Distributed Control in a Process Runtime Environment
, 1999
"... An effective process definition language must be powerful, yet clear. It must also have well defined semantics to support powerful and definitive analysis. End users require that a runtime interpreter for the language faithfully implement the semantics used in analysis of process definitions, and th ..."
Abstract
-
Cited by 19 (13 self)
- Add to MetaCart
(Show Context)
An effective process definition language must be powerful, yet clear. It must also have well defined semantics to support powerful and definitive analysis. End users require that a runtime interpreter for the language faithfully implement the semantics used in analysis of process definitions, and that the interpreter be efficient and scalable. In addition to all of the above, the language, and its interpreter must also be readily evolvable. In this paper, we describe the architecture of Juliette, a process execution environment designed to address all of these requirements. We outline the tensions posed by these strong objectives and describe Juliette’s modular approach and its novel distribution strategy, indicating how they address the tensions set by our objectives. While we explain the Juliette architectural approach in the context of the interpretation of Little-JIL, the approach applies to the interpretation of a broad class of process definition languages.
Structuring Complex Software Processes by "Process Landscaping"
- EWSPT European Workshop on Software Process Technology, Kaprun, Austria. Lecture Notes in Computer Science
, 2000
"... Process Landscaping is a method, which supports modelling of related processes. These processes can be modelled on different levels of abstraction. Interfaces between processes are considered as first class process entities. It prevents loosing an overview of the whole framework of processes and ..."
Abstract
-
Cited by 7 (5 self)
- Add to MetaCart
Process Landscaping is a method, which supports modelling of related processes. These processes can be modelled on different levels of abstraction. Interfaces between processes are considered as first class process entities. It prevents loosing an overview of the whole framework of processes and ensures that decisions about processes are not burdened out by an overwhelming amount of details. In this article we discuss the approach of Process Landscaping by developing a real-world software process.
Specifying coordination in processes using Little-JIL
- ICSE 2000
, 2000
"... Little-JIL, a new language for programming coordination in processes is an executable, high-level process language with a formal (yet graphical) syntax and rigorously defined operational semantics. The central abstraction in Little-JIL is the “step. ” Little-JIL steps serve as foci for coordination ..."
Abstract
-
Cited by 6 (4 self)
- Add to MetaCart
Little-JIL, a new language for programming coordination in processes is an executable, high-level process language with a formal (yet graphical) syntax and rigorously defined operational semantics. The central abstraction in Little-JIL is the “step. ” Little-JIL steps serve as foci for coordination and provide a scoping mechanism for control, data, and exception flow and for agent and resource assignment. Steps are composed hierarchically, but Little-JIL processes can have highly dynamic structures and can include recursion and concurrency. Little-JIL is based on two main hypotheses. The first is that the specification of coordination control structures is separable from other process programming language issues. Little-JIL provides a rich set of control structures while relying on
Designing and Building Software Federations
- 1st Conference on Component Based Software Engineering. (CBSE
, 2001
"... Commercial Off The Shelf tools (COTS) are now widely distributed, of good quality, relatively cheap and cover most of the application domains. It is thus a surprise to consider that it is uncommon to reuse COTS when building large applications. At least it is recognized that building a large applica ..."
Abstract
-
Cited by 5 (4 self)
- Add to MetaCart
(Show Context)
Commercial Off The Shelf tools (COTS) are now widely distributed, of good quality, relatively cheap and cover most of the application domains. It is thus a surprise to consider that it is uncommon to reuse COTS when building large applications. At least it is recognized that building a large application based on COTS is a tough issue.
Process-Orchestrated Software: Towards a Workflow Approach to the Coordination of Distributed Systems
, 2000
"... As the Internet turns into an essential business and production infrastructure, networked business and work in general become more and more common; for instance, virtual enterprises emerge as an innovative way to launch, organize and carry out initiatives, either within a large, global corporation, ..."
Abstract
-
Cited by 4 (1 self)
- Add to MetaCart
As the Internet turns into an essential business and production infrastructure, networked business and work in general become more and more common; for instance, virtual enterprises emerge as an innovative way to launch, organize and carry out initiatives, either within a large, global corporation, or as dynamic joint ventures between geographically dispersed organizations. In such a
Process-Orchestrated Software: Towards a Workflow Approach to the Coordination of Distributed Systems
"... Distributed workflow supports collaborative processes composed of activities, in which the synchronization and coordination of the activities and the people having a part in them (the stakeholders of the process) is an essential characteristic. Workflow is based on the concept of a process model, de ..."
Abstract
- Add to MetaCart
(Show Context)
Distributed workflow supports collaborative processes composed of activities, in which the synchronization and coordination of the activities and the people having a part in them (the stakeholders of the process) is an essential characteristic. Workflow is based on the concept of a process model, describing the process to be followed, and on facilities (collectively termed the process enactment engine) for supporting and guiding the work of stakeholders according to that model. Distributed workflow technology nowadays provides many of the necessary paradigms, techniques and tools to support the management of complex, dynamic and decentralized business practices, their stakeholders, and their processes. There are a number of dimensions concurring to workflow distribution, which interact- and sometimes conflict- with one other in various, complex ways, such as distribution of the workflow information, the workflow actors, tools employed to carry out the work, and the work itself Complete decentralization of WF along all of its distribution dimensions is still a challenge. On the other hand approaches and techniques that have been established for and have become typical of distributed workflow show great potential towards the coordination of various kinds of distributed software systems, which require the execution of some kind of process: two important domains are the run-time monitoring and control of functional and non-functional properties of the components of a distributed system, and the dynamically determined cooperation within a group of software agents towards some common goal. This proposal intends to investigate the characteristics of those software coordination problems and how they can be tackled with distributed workflow models and techniques. We intend to carry out our investigation in
Extensible Process Support System
- in 9th European Workshop on Software Process Technology (EWSPT
, 2003
"... The issue of building a Process Support System Environment (PSSE), or a family of PSEE, to make them interoperate or to use them to pilot applications or services requires new solutions; there is almost no hope for a single system to address correctly all the issues. ..."
Abstract
- Add to MetaCart
The issue of building a Process Support System Environment (PSSE), or a family of PSEE, to make them interoperate or to use them to pilot applications or services requires new solutions; there is almost no hope for a single system to address correctly all the issues.
