2008 · 61 citations · 9 references
EngineeringBusiness IntelligenceElementary Business ProcessEnterprise ModelingSoftware EngineeringBusiness Model CanvasBusiness ArchitectureSoftware AnalysisEnterprise Business ModelSoftware ArchitectureRight GranularityManagementSystems EngineeringEnterprise ModellingCandidate ServiceEnterprise ArchitectureE-business ModelService-oriented Software EngineeringComputer ScienceSoftware DesignService-oriented ComputingBusinessData Modeling
Service-oriented solutions require precise identification of architectural elements, yet current methods overlook performance metrics, semantic integrity, and process-based services. This paper proposes a new process for identifying and specifying enterprise software services and their architectural elements. The authors introduce EEAT, a clustering technique that analyzes affinity between elementary business processes and entities to identify candidate architectural elements. EEAT produces candidate services at appropriate granularity while ensuring low coupling, high cohesion, and low reuse cost, supporting reusable software services.
One of the key activities that are needed to construct a quality service-oriented solution is the identification of its architectural elements with the right granularity. The selection of an appropriate method for identification of services from business models of an enterprise is thus quite crucial to the success of any service-oriented solution for that enterprise. Existing methods for service identification ignore required performance metrics and semantics integrity of business elements; more importantly, they focus on entity-based services while ignoring process based ones. This paper proposes a new process for identification and specification of enterprise software services and their architectural elements. A novel clustering technique, named elementary business process and business entity affinity analysis technique (EEAT), is introduced for identifying candidate architectural elements. This technique identifies each candidate service with the right granularity, while satisfying low coupling, high cohesion, and low reuse cost principles for reusable software services.
9
Accomplishing software stability
Mohamed E. Fayad · Communications of the ACM · 2002 · 125 citations
Software Maintenance, Software Development Practice, Engineering +19
Component identification method with coupling and cohesion
Seung Jae Jung, Soo Dong Kim, Woo Hyun Jang et al. · 2005 · 97 citations
Engineering, Software Engineering, Computer-aided Design +23