1 / 15

Criteria Based Software Product Integration Architecture (2007)

Criteria Based Software Product Integration Architecture (2007). F. Tsui Kennesaw State University (Southern Polytechnic State University). Software Product Integration. Product A. Product B. integration. Packaged together. Functionally integrated. Product A. Product A&B. Product B.

ashtonk
Download Presentation

Criteria Based Software Product Integration Architecture (2007)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

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

  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 Financial distribution Human Resource inventory . . . . . . Sales procurement

  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. Coupling Content Common Control Stamp Data Cohesion Functional Sequential Communicational Procedural Temporal Logical Coincidental Application of Traditional “modular” Coupling and Cohesion Concepts high low

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

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

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

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

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

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

  14. Implications of Coupling & Cohesion forSoftware Product Family Architecture Co- Exist Low Inter- mediate Strong

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

More Related