Welcome to the InfoSci Platform
Reference Hub3
Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture

Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture

Masahide Nakamur, Hiroshi Igaki, Takahiro Kimura, Kenichi Matsumoto
Copyright: © 2011 |Volume: 3 |Issue: 4 |Pages: 19
ISSN: 1935-5688|EISSN: 1935-5696|EISBN13: 9781613507780|DOI: 10.4018/jisss.2011100104
Cite Article Cite Article

MLA

Nakamur, Masahide, et al. "Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture." IJISSS vol.3, no.4 2011: pp.54-72. http://doi.org/10.4018/jisss.2011100104

APA

Nakamur, M., Igaki, H., Kimura, T., & Matsumoto, K. (2011). Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture. International Journal of Information Systems in the Service Sector (IJISSS), 3(4), 54-72. http://doi.org/10.4018/jisss.2011100104

Chicago

Nakamur, Masahide, et al. "Identifying Services in Procedural Programs for Migrating Legacy System to Service Oriented Architecture," International Journal of Information Systems in the Service Sector (IJISSS) 3, no.4: 54-72. http://doi.org/10.4018/jisss.2011100104

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

In order to support legacy migration to the service-oriented architecture (SOA), this paper presents a pragmatic method that derives candidates of services from procedural programs. In the SOA, every service is supposed to be a process (procedure) with (1) open interface, (2) self-containedness, and (3) coarse granularity for business. Such services are identified from the source code and its data flow diagram (DFD), by analyzing data and control dependencies among processes. Specifically, first the DFD must be obtained with reverse-engineering techniques. For each layer of the DFD, every data flow is classified into three categories. Using the data category and control among procedures, four types of dependency are categorized. Finally, six rules are applied that aggregate mutually dependent processes and extract them as a service. A case study with a liquor shop inventory control system extracts service candidates with various granularities.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.