Specifying process-oriented hypertext for organizational computing

Noll, John; Scacchi, Walt

doi:10.1006/jnca.2000.0122

Cited by 34 publications

(45 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To compose such pages, the designer relies on the application requirements, interpreted according to his/her personal experience and modeling taste. Thus, incorporating a process model in the Web application does not pose unnecessary restrictions on the Web application design, such as having exactly one Web page per process activity (this is the case, for instance, for the Web interfaces of commercial WfMS, as well as in some research-derived models such as PMS [Noll and Scacchi 2001]). This degree of freedom is similar to the one available to the designer of a regular data-intensive Web application.…”

Section: · 21mentioning

confidence: 99%

“…The Process Modeling language (PML) described in [Noll and Scacchi 2001] is a lightweight formalism for process description that allows describing workflow schemes similar to those expressible in BPMN. The authors show how a PML specification can be automatically compiled into a simple Web-based application that allows users to enact their participation to the process by following links, filling in forms etc.…”

Section: Integrated Hypertext and Process Modelingmentioning

confidence: 99%

“…The process-oriented hypertexts that they identify are conceptually close to our process-driven hypertexts. Three main differences distinguish the two proposals: (i) our approach relies on the WebML hypertext modeling language, endowed with a graphical notation, while the starting point in [Noll and Scacchi 2001] is a (simplified) process model, represented in an imperative programming-style syntax; (ii) the underlying process control mechanisms are different, because our proposal relies on a process reference model (coherent with the WebML data model based on Entity-Relationship), while PML delegates workflow control to an ad-hoc "lightweight process runtime"; (iii) finally, PML does not allow customizing the Web interface of a given activity: only one page is generated for each activity, regardless of how complex the activity is, whereas WebML allows arbitrarily structured activity interfaces.…”

Section: Integrated Hypertext and Process Modelingmentioning

confidence: 99%

See 2 more Smart Citations

Process Modeling in Web Applications

Ceri

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

While Web applications evolve towards ubiquitous, enterprise-wide or multi-enterprise information systems, they face new requirements, such as the capability of managing complex processes spanning multiple users and organizations, by interconnecting software provided by different organizations. Significant efforts are currently being invested in application integration, to support the composition of business processes of different companies, so as to create complex, multi-party business scenarios. In this setting, Web applications, which were originally conceived to allow the user-to-system dialogue, are extended with Web services, which enable system-to-system interaction, and with process control primitives, which permit the implementation of the required business constraints. This paper presents new Web engineering methods for the high-level specification of applications featuring business processes and remote services invocation. Process-and service-enabled Web applications benefit from the high-level modeling and automatic code generation techniques that have been fruitfully applied to conventional Web applications, broadening the class of Web applications that take advantage of these powerful software engineering techniques. All the concepts presented in this paper are fully implemented within a CASE tool.

show abstract

Section: · 21mentioning

confidence: 99%

Section: Integrated Hypertext and Process Modelingmentioning

confidence: 99%

Section: Integrated Hypertext and Process Modelingmentioning

confidence: 99%

See 1 more Smart Citation

Process Modeling in Web Applications

Ceri

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…PML: A language for modeling software processes Noll and Scacchi (2001) have developed and demonstrated the design of PML and its Web-based runtime environment. PML has been used to model a subset of acquisition processes at the US O ce of Naval Research in legacy as-is, redesigned to-be, and transitional here-to-there forms (Noll and Scacchi, 2001). The legacy processes span more than 120 problem-solving tasks as process steps that occur in multiple locations within/ between ONR's national and international o ces.…”

Section: Approaches To Modeling Software Process Architecturesmentioning

confidence: 99%

“…An excerpt from an acquisition process speci®ed in PML for submitting a software research or development proposal (Noll and Scacchi, 2001). …”

Section: Approaches To Modeling Software Process Architecturesmentioning

confidence: 99%

Modeling and simulating software acquisition process architectures

Choi

Scacchi

2001

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

In this paper, we describe our e orts to support the modeling and simulation of processes associated with software system acquisition activities. Software acquisition is generally a multi-organization endeavor concerned with the funding, management, engineering, system integration, deployment and long-term support of large software systems. We ®rst describe our approach supporting the modeling and simulation of software acquisition processes using a software process architecture (SPA). We then introduce how we support the distribution, concurrent execution and interoperation of multiple software process simulations using the high-level architecture (HLA) and run-time infrastructure (RTI) to address the complexity of software acquisition process architectures. To illustrate this, we provide examples from the design and prototyping of a Web-based environment that supports the modeling and simulation of acquisition process architectures. This environment thus serves as a new kind of software process test-bed that can demonstrate and support experiments incorporating multiple software process simulation systems that interoperate in a distributed and concurrent manner across a network. Ó

show abstract

Hypertext for Software Engineering

Scacchi¹

2002

Encyclopedia of Software Engineering

Self Cite

View full text Add to dashboard Cite

What is the power of hypertext in supporting software engineering? (The term “hypertext” is treated throughout as synonymous with “hypermedia,” which denotes the nonlinear representation of interrelated textual, graphic, filmic, or auditory information.) Power in other contexts usually refers to the ability of some entity or agent to affect the behavior of another or to achieve advantage over another in ways that the other cannot avoid. Following this, one might expect that as a technology , hypertext systems offer relative advantage over alternatives to automated text/document information systems, including conventional word processing systems, file systems, and database management systems. Hypertext systems offer a degree of information processing power that enables new kinds of applications, much like the advent of expert system shells enabled the creation of expert applications for domains such as computer configuration and diagnostic pathology. Similarly, as a medium for writing and reading electronic documents hypertext systems allow the redefinition of the structure and content of documents that alter the constraints and opportunities for conveying information in contrast to the linear print medium. Thus the power of hypertext in whatever form it exists is subtle and incremental; it is potential rather than kinetic. However, such power can accumulate in different application domains in the long run if effectively mobilized and integrated with domain‐specific tasks, processing mechanisms, and workflows. The power of hypertext technology in different application domains can be realized in a number of ways. In particular, technology that supports a unified view of the hypertext documents, production processes, processing mechanisms, and settings of use appears to offer the greatest power at this time. To see this, the concept of a domain‐specific hypertext environment (DSHE) is defined in the following section. Next, the domain of software production is examined in order to identify how hypertext tools and document production/consumption techniques can play a role to facilitate software engineering objectives. The focus then shifts to describe the structure of information to evolve within a DSHE in terms of product, task, and setting information for the domain of software production. Together, these sections then set the final stage for a discussion of the power of DSHE. Subsequently, seven ways the power of DSHE can be realized are identified, followed by an examination of the costs that are borne in order to realize this power.

show abstract

Specifying process-oriented hypertext for organizational computing

Cited by 34 publications

References 22 publications

Process Modeling in Web Applications

Process Modeling in Web Applications

Modeling and simulating software acquisition process architectures

Hypertext for Software Engineering

Contact Info

Product

Resources

About