Process modeling

Curtis, Bruce; Kellner, Marc I.; Over, Jim

doi:10.1145/130994.130998

Cited by 1,222 publications

(595 citation statements)

References 29 publications

Supporting

Mentioning

556

Contrasting

Unclassified

Order By: Relevance

Section: Interpersonal Interactions In Isdmentioning

confidence: 99%

“…Indeed, team coordination is improved by shared mental models (Espinosa et al 2001); however, Curtis et al (1992) found that such documentation did not reduce the amount of communication required. Instead, "Artificial (often political) barriers to communication among project teams created a need for individuals to span team boundaries and to create informal communication networks" (Curtis et al 1992(Curtis et al , p. 1282. This partly explains designers' need for both vertical coordination (coordination between developers and users, through authorized entities including project managers) and horizontal coordination (between developers and users directly) (Nidumolu 1995).…”

Section: Interpersonal Interactions In Isdmentioning

confidence: 99%

“…Put another way, long-recognized problems with the Rational Model (cf. Brooks 2010; Curtis et al 1992;Gladden 1982;McCracken and Jackson 1982) have remained for decades partly because no comprehensive alternative with which to challenge it was available. Therefore, formulating a comprehensive process theory of software design practice consistent with the Empirical Model may stimulate innovation, lead to more broadly-applicable theory and further our collective understanding of practice in information systems development (ISD) and software engineering (SE).…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

The Sensemaking-Coevolution-Implementation Theory of software design

Ralph

2015

Science of Computer Programming

View full text Add to dashboard Cite

Understanding software design practice is critical to understanding modern information systems development. New developments in empirical software engineering, information systems design science and the interdisciplinary design literature combined with recent advances in process theory and testability have created a situation ripe for innovation. Consequently, this paper utilizes these breakthroughs to formulate a process theory of software design practice: SensemakingCoevolution-Implementation Theory explains how complex software systems are created by collocated software development teams in organizations. It posits that an independent agent (design team) creates a software system by alternating between three activities: organizing their perceptions about the context, mutually refining their understandings of the context and design space, and manifesting their understanding of the design space in a technological artifact. This theory development paper defines and illustrates Sensemaking-Coevolution-Implementation Theory, grounds its concepts and relationships in existing literature, conceptually evaluates the theory and situates it in the broader context of information systems development.

show abstract

Section: Interpersonal Interactions In Isdmentioning

confidence: 99%

Section: Interpersonal Interactions In Isdmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

The Sensemaking-Coevolution-Implementation Theory of software design

Ralph

2015

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…Many researchers focused on development of models or ontologies cataloguing an appropriate scope of information on companies that should be considered when describing organizations or their processes e.g. [2][3]. For instance [2] highlighted that a process model should provide information on what is going to be done (i.e.…”

Section: Related Workmentioning

confidence: 99%

Organisational Ontology Framework for Semantic Business Process Management

Filipowska

Hepp

Kaczmarek

et al. 2009

Business Information Systems

View full text Add to dashboard Cite

Abstract. The field of Semantic Business Process Management (SBPM) has refuelled interest in using ontologies for the representation of the static and dynamic aspects of an enterprise and value chains. Putting the SBPM vision into practice, however, requires a consistent and operational network of ontologies reflecting the various spheres of enterprise structures and operations. Consistent means that the ontologies are based on compatible paradigms, have a compatible degree of detail, and include at least partial sets of alignment relations which allow data interoperability. Operational means that the ontology specifications are available in a single, current ontology formalism for which scalable repositories, reasoning support, APIs, and tools are available. In this paper, we describe a set of ontologies for SBPM that follows the mentioned requirements, and compare our work with the related efforts.

show abstract

“…Others include Object-Oriented Database Systems such as GemStone (Bretl, Otis et al, 1989) and O 2 (Bancilhon, Barbedette et al, 1988), which have at their core a persistent object store, and process modelling systems, which use a persistent base to preserve their modelling activities over execution sessions (Bruynooghe, Parker et al, 1991;Curtis, Kellner et al, 1992;Han and Welsh, 1993). Some persistent programming systems allow software engineering environments to be completely supported within the persistent system (Currie, 1985;Bretl, Otis et al, 1989;Morrison, Brown et al, 1994).…”

Section: Introductionmentioning

confidence: 99%

Exploiting Persistent Linkage in Software Engineering Environments

Morrison

Connor

Cutts

et al. 1995

The Computer Journal

View full text Add to dashboard Cite

Abstract. Persistent programming systems are designed to provide technology for the construction and maintenance of large, long-lived object-based application systems. Many successful prototypes have been constructed and a large body of application building experience is emerging. Three common attributes of persistent systems are persistent linkage, strong typing and the referential integrity of data. Persistent linkage allows persistent objects to be included in the binding process. Strong typing guarantees that objects are only manipulated in a manner consistent with their type system descriptions. Referential integrity ensures that once a link (reference) to an object is established, its identity is unique and it persists over time. As a consequence no object can be deleted while another refers to it. Here we examine some of the advantages of providing software engineering environments within a persistent object system with strong typing and referential integrity. It is shown how the integration of system specifications, programs, configuration management tools and documentation all within a single persistent environment leads to powerful new techniques. This new power is achieved by sharing structured persistent data across the hitherto enclosing boundaries of system components.

show abstract

Process modeling

Cited by 1,222 publications

References 29 publications

The Sensemaking-Coevolution-Implementation Theory of software design

The Sensemaking-Coevolution-Implementation Theory of software design

Organisational Ontology Framework for Semantic Business Process Management

Exploiting Persistent Linkage in Software Engineering Environments

Contact Info

Product

Resources

About