Maintaining Traceability During Object-Oriented Software Evolution: A Case Study
ICSM '99 Proceedings of the IEEE International Conference on Software Maintenance
A Model-based Object-oriented Approach to Requirement Engineering (MORE)
COMPSAC '07 Proceedings of the 31st Annual International Computer Software and Applications Conference - Volume 01
Requirement Traceability in Software Development Process: An Empirical Approach
RSP '08 Proceedings of the 2008 The 19th IEEE/IFIP International Symposium on Rapid System Prototyping
Using Traceability to Support SOA Impact Analysis
SERVICES '11 Proceedings of the 2011 IEEE World Congress on Services
Behavioral and structural evolution of SOA from OO: an integrated approach
ACM SIGSOFT Software Engineering Notes
Engineering of requirements for a distributed teleteaching system: a conceptual graph-based approach
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
Service components are the key to the development of a serviceoriented solution as they provide the implementation of the services. The implementation of Service components provides the actual function of the component and can be defined with one or more Java classes. We propose a model named Service Component to Class (SC2C) that maps the service components of an application with that of the classes that implement the service components. We also propose a visual model as a part of SC2C that represents the classes and relationship among classes. This model helps to establish traceability among service components and classes. We also introduce some traceability metrics to measure traceability between the artifacts of Service Oriented Architecture (SOA) and Object Oriented (OO) paradigms. This work, along with our earlier work, help in Software Configuration Management of a SOA application. We provide an insurance system case study to illustrate our approach.