2008 IEEE Symposium on Advanced Management of Information for Globalized Enterprises (AMIGE) 2008
DOI: 10.1109/amige.2008.ecp.41
|View full text |Cite
|
Sign up to set email alerts
|

Searching and Finding Concepts in Service-Oriented Enterprise Software

Abstract: Error correction during application maintenance is a difficult activity. Finding a source code that implements certain real-world concepts is an essential part of maintenance and is called concept location. The research community has mainly addressed concept location in legacy systems. Nevertheless, the difficulty of concept location in serviceoriented software systems is as yet unknown, but thought to be seriously underestimated. This paper discusses characteristics of service-oriented enterprise software sys… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2010
2010
2010
2010

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 18 publications
0
1
0
Order By: Relevance
“…Source code is a collection of statements and declarations-a means of communication with the computing machine through structure and syntax. Analyzing the source code may reveal information about the structural aspects and the architecture of the system (i.e., how the code is working), but not about the reason for the existence of a particular piece of code (i.e., what the code is about) (Kuhn et al 2005;Panchenko and Zeier 2008). Unfortunately, without sufficient semantic knowledge on code functionality in the context of business processes, it would be impossible to utilize source code components in new services development.…”
Section: Introductionmentioning
confidence: 98%
“…Source code is a collection of statements and declarations-a means of communication with the computing machine through structure and syntax. Analyzing the source code may reveal information about the structural aspects and the architecture of the system (i.e., how the code is working), but not about the reason for the existence of a particular piece of code (i.e., what the code is about) (Kuhn et al 2005;Panchenko and Zeier 2008). Unfortunately, without sufficient semantic knowledge on code functionality in the context of business processes, it would be impossible to utilize source code components in new services development.…”
Section: Introductionmentioning
confidence: 98%