1. Criteria Based Software Product Integration Architecture (2007) F. Tsui Kennesaw State University (Southern Polytechnic State University)

2. Software Product Integration Product A integration Product B Product A Product B Product A&B How much? Packaged together Functionally integrated

3. Software Integration Levels Internal Code Components Product software developers and support personnel software designers and support personnel software users, customers, trainers and support personnel internal external

4. Some Software Integration Issues at the code level –Inheritance (from OO) –code libraries –code patterns –etc at the component level –design patterns –component libraries, if available –etc at the product level –functionalities –platforms –database –user interface –user guides –etc

5. Why Do We Care? (A) Business is connected and needs to operate in an integrated fashion; thus the software it uses must also reflect that integrated world (B) Software industry continues to experience mergers and acquisitions ; thus the software product and services must also be integrated Human Resource Sales Financial procurement distribution inventory...

6. Traditional Software Engineering Guidelines : Low Coupling and High Cohesion Coupling is the degree of connectedness among modules: –Control passing –Data passing Coupling should be kept to minimum – low coupling in design Cohesion is the degree of relatedness of the parts within a module Cohesion should be maximized --- high cohesion in design

7. Application of Traditional “modular” Coupling and Cohesion Concepts Coupling –Content –Common –Control –Stamp –Data Cohesion –Functional –Sequential –Communicational –Procedural –Temporal –Logical –Coincidental low high

8. Software Product Family What are some of the issues that we should consider for software product family architecture?: 1.Terminology 2.Packaging & delivery 3.User interface 4.Product manuals and user guides 5.Application functionalities 6.Application flow and control 7.Data stored, processed, and shared 8.Systems, subsystems, and middleware platforms 9.Internationalization 10.Customer support and maintenance

9. A Software Product Integration Architecture Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration Increasing levels of product integration

10. A Software Product Integration Architecture Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration -Packaging & delivery -System, subsystem & middleware platform -internationalization

11. A Software Product Integration Architecture Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration -Packaging & delivery -System, subsystem & middleware platform -Internationalization -Terminology -Application UI -Product manuals -Product support& maintenance

12. A Software Product Integration Architecture Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration -Packaging & delivery -System, subsystem & middleware platform -Internationalization -Terminology -Application UI -Product manuals -Product support& maintenance - Data stored, processed & shared -Application flow & control

13. A Software Product Integration Architecture Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration -Packaging & delivery -System, subsystem & middleware platform -Internationalization -Terminology -Application UI -Product manuals -Product support& maintenance - Data stored, processed & shared -Application flow & control - Functionalities & features

14. Implications of Coupling & Cohesion for Software Product Family Architecture Architectural IssueCouplingCohesion Packaging & delivery Physically packaged togetherProduct may be at “coincidental” Cohesion level System, subsystem, middleware platform Using the same platforms Internationalization Same language across product family Terminology Commonalities in icons, terms, etc. and in their respective semantics Application’s UI Similar looks and navigational approach Product manuals Same in content and mode of presentation Product support & maintenance Release and fix physically packaged together and delivered together Same levels of support and same methodology of fix and release distribution Application flow & control Application is “control” and/or “stamp” coupled via data store Application is experiencing “procedural” or “communicational” cohesion Data stored, processed & shared Application is “ common” or “stamp” coupled via data store or global variable Functionalities Application is “ common” or “stamp” coupled via data store or global variable Application is at “sequential” cohesion and has no duplicative features Co- Exist Low Inter- mediate Strong

15. “Coupling” and “Cohesion” in Product-Line Integration Co-Existence Integration Strong Integration Intermediate Integration Low-Level Integration Increase in coupling Increase in cohesion low-coupling among products weak product family cohesion strong product family cohesion high-coupling among products (low)-coupling (high)-coupling