Electronic contracting with COSMOS-how to establish, negotiate and execute electronic contracts on the Internet

Griffel, Frank; Boger, Mark; Weinreich, Harald; Lamersdorf, Winfried; Merz, Michael

doi:10.1109/edoc.1998.723241

Cited by 73 publications

(35 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In the COSMOS project, a contract object model is presented [25]. As we have already discussed in Section 1, a contract model contains only a subset of the concepts identified in our framework.…”

Section: T He Co Sm Os P Rojectmentioning

confidence: 99%

The 4W framework for B2B e-contracting

Angelov¹,

Grefen²

2003

IJNVO

View full text Add to dashboard Cite

Section: T He Co Sm Os P Rojectmentioning

confidence: 99%

The 4W framework for B2B e-contracting

Angelov¹,

Grefen²

2003

IJNVO

View full text Add to dashboard Cite

“…Evaluating the extent to which ERA provides functionalities for the support of the e-contracting concept serves as an additional indication for completeness of ERA. We analyzed ERA from the perspective of the ''4W e-contracting framework" (Angelov and Grefen, 2003b), which compared to other contracting frameworks (e.g., Greunz et al, 2000;Griffel et al, 1998) provides higher level of detail and covers a larger set of concepts (Angelov and Grefen, 2003b). To familiarize the reader with the ''4W econtracting framework", we provide a brief summary of it.…”

Section: Theoretical Evaluation Of Era For Completenessmentioning

confidence: 99%

“…The architecture qualities are qualities that are important for the design of a ''good" e-contracting reference architecture. Initially, as an inspiration for the definition of non-functional qualities required in an e-contracting reference architecture, we used the list of non-functional qualities on information systems presented in Bass et al (2003) and existing publications on e-contracting (Angelov and Grefen, 2002, 2003b, 2004aGrefen et al, 2003;Griffel et al, 1998;Hoffner et al, 2001b;Merz et al, 1998). Based on our initial list of requirements, we defined a draft version of ERA.…”

Section: Required Qualities In a Reference Architecture For Econtractingmentioning

confidence: 99%

“…Many of these efforts propose concrete e-contracting architectures that are suitable for specific business situations and software solutions (e.g., Dan et al, 1998;Hoffner et al, 2001a;Ludwig et al, 2004). Efforts that are independent of concrete technology and business scenarios lack sufficient level of detail and completeness (e.g., Boulmakoul and Salle, 2002;Chiu et al, 2003;Griffel et al, 1998;Milosevic and Bond, 1995).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An e-contracting reference architecture

Angelov

Grefen

2008

Journal of Systems and Software

View full text Add to dashboard Cite

Business-to-business e-contracting aims at automating the contracting process between companies. It improves the efficiency of the contracting process and enables the introduction of new business models that can be supported by companies. For the development of an e-contracting system, an architecture is required that describes the system components and the communication channels between them. This paper presents a reference architecture for the development of e-contracting systems. The architecture is designed on the basis of a requirement analysis of e-contracting systems. Established architectural principles are used in its design. The architecture can serve as a foundation in the analysis and design of concrete architectures of e-contracting systems. Furthermore, it can be used as a standardization model that facilitates system integration and communication of ideas. Its value for both software architects and business professionals makes it an important tool in the analysis and implementation of e-contracting systems.

show abstract

“…To the extent allowed by the level of information technology, there have been many attempts to realize information systems that can support contracting processes [6,7,17,18,24]. Unfortunately, none of these systems has the fl exibility to support the complete range of contracting processes.…”

mentioning

confidence: 99%

Supporting the Diversity of B2B E-Contracting Processes

Angelov

Grefen

2008

International Journal of Electronic Commerce

View full text Add to dashboard Cite

Contracts specify the rights and obligations of the contracting parties. Information technologies can make e-contracting more effi cient and effective. A process model for fl exible B2B e-contracting is proposed that separates concerns by distinguishing function and communication perspectives of e-contracting processes supplemented with activity constraints. The model supports the elaboration of fully detailed e-contracting process specifi cations, coherent communication between contracting parties, and seamless coupling between the internal and external activities of a company.KEY WORDS AND PHRASES: Business-to-business e-contracting, e-contracting process model, fl exible e-contracting.Business process modeling aims at improving the effi ciency and effectiveness of business processes executed in a company. Software applications with different levels of complexity are provided to coordinate and automate intraorganizational processes. Until recently, software applications modeling and supporting business processes were intra-organizational and thus limited to the scope of one company. With the rapid development of information technology, the possibility for supporting cross-organizational business processes has emerged. Research and standardization efforts have concentrated on modeling and realizing cross-organizational processes by supporting information systems [1, 9,17,26].Business-to-business (B2B) contracting encompasses a collection of coherent intra-and cross-organizational activities. To the extent allowed by the level of information technology, there have been many attempts to realize information systems that can support contracting processes [6,7,17,18,24]. Unfortunately, none of these systems has the fl exibility to support the complete range of contracting processes. This is mainly because of their reliance on fi xed, structured models of the contracting process for automated contracting support. Contracting processes are far too complex and variable to be addressed through traditional process specifi cations. Consequently existing systems only support context-specifi c contracting processes and provide little fl exibility in business relations.This paper defi nes a general model for B2B e-contracting that can specify diverse and fl exible e-contracting processes. The proposed model has three elements: a function perspective, a communication perspective, and constraint operators. The function perspective provides descriptions of e-contracting activities at multiple levels of abstraction. It supports process designers in the selection and specifi cation of contracting activities. Case PresentationThe The contracting process is not strictly defi ned and allows fl exibility to each party. A client will perform a number of activities. Figure 1 lists 12 activities typically performed by clients. The UML activity diagram shows one of the possible control fl ows for these activities.In parallel, Telegraaf also performs a number of activities. Figure 2 lists 13 activities typically performed by Te...

show abstract

Electronic contracting with COSMOS-how to establish, negotiate and execute electronic contracts on the Internet

Cited by 73 publications

References 5 publications

The 4W framework for B2B e-contracting

The 4W framework for B2B e-contracting

An e-contracting reference architecture

Supporting the Diversity of B2B E-Contracting Processes

Contact Info

Product

Resources

About