Information Systems Engineering 2008
DOI: 10.4018/978-1-59904-567-2.ch005
|View full text |Cite
|
Sign up to set email alerts
|

Pragmatic-Driven Approach for Service-Oriented Analysis and Design

Abstract: This chapter presents a pragmatic-driven approach for service-oriented information system analysis and design. Its uniqueness is in exploiting a design foundation for graphical description of the semantic and pragmatic aspects of business processes that is based on the service-oriented principles. Services are viewed as dynamic subsystems. Their outputs depend not only on inputs, but on a service state as well. Intentions of business process experts are represented in terms of a set of pragmatic dependencies, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Year Published

2010
2010
2017
2017

Publication Types

Select...
5
3

Relationship

4
4

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 14 publications
0
9
0
Order By: Relevance
“…To maintain a holistic and systematic view of the whole IS and in order to understand its functionality, a three-level approach is important, independent of the fact what kind of IS is designed. In order to understand why and how technical system components are useful and how they fit into organizational systems, three modeling levels of IS specifications are necessary: a pragmatic level, a semantic level and a syntactic level (Gustas & Gustiené, 2008).…”
Section: A Multilevel Approach Towards Eliciting Requirementsmentioning
confidence: 99%
“…To maintain a holistic and systematic view of the whole IS and in order to understand its functionality, a three-level approach is important, independent of the fact what kind of IS is designed. In order to understand why and how technical system components are useful and how they fit into organizational systems, three modeling levels of IS specifications are necessary: a pragmatic level, a semantic level and a syntactic level (Gustas & Gustiené, 2008).…”
Section: A Multilevel Approach Towards Eliciting Requirementsmentioning
confidence: 99%
“…Actors are represented by subsystems that are non-overlapping in functionality. Active concepts can be related by the static dependencies such as inheritance, composition and classification (Gustas, 2010;Gustas & Gustiene, 2009;Gustas & Gustiene, 2008). The graphical notation of semantic dependencies is presented in Figure 5.…”
Section: Dependencies Between Actorsmentioning
confidence: 99%
“…A small case study will be used for illustration of the tacit structural and behavioral dependencies in the relationship Send. In terms of EM approach, the relationship Send is viewed as a communication action (Gustas & Gustiene, 2008). Action names are verbs, which bind together service requester (Person), service flow (E-mail) and service provider (E-mail System).…”
Section: Representation Of Objects and Their Propertiesmentioning
confidence: 99%
“…In this article we analyze several theoretical enhancements to achieve semantic integrity of conceptualizations. The proposed solutions are illustrated by using our enterprise modeling (EM) approach (Gustas & Gustiene, 2008). It helps us to theoretically investigate the semantic power of various diagram types.…”
mentioning
confidence: 99%