software Engineering required documents for you
- 1. Ontologi es Reasonin g Components Agents Simulati Introduction to Software Reuse Riya Yadav
- 2. What is software reuse? 🖝Act: reuse of previously built software artifact/asset to fulfill need in new development task or sub-task 🖝Field: study of methodologies, practices, processes, techniques, languages, frameworks, CASE tools that foster and facilitate reuse 🖝Motivation: 🖝 Avoiding wasting time and money redoing same task over and over 🖝 Quality standard of previously completed task carries over to new occurrences of same need
- 3. Requirements of reusable software artifacts 🖝Common to special-purpose artifacts: 🖝 Usable: user-friendly 🖝 Reliable: conform to functional and non-functional requirements 🖝Additional for reuse: 🖝 Pervasively useful: 🖝 Fulfills a need that recurs across projects, domains, applications, concerns or platforms 🖝 Adaptable: 🖝 Modular: useful by separable parts 🖝 Generic: useful as a whole in many different context 🖝 Understandable: documented, 🖝 Portable: platform independent
- 4. Reuse issues and dimensions 🖝Asset composition vs. asset mapping with meta-assets (generative) 🖝 ex. composing existing DLL vs. generating DLL from precise UML model 🖝 Transformations can be use for both 🖝Asset abstraction level 🖝Asset executability level: 🖝 ex, model, source code, bytecode, binary code 🖝Asset granularity level 🖝 ex. package, class, method 🖝Asset process stage 🖝Asset visibility 🖝 Black-box, i.e. reuse “as is” based on specification vs. 🖝 White-box, i.e. reuse with modifications based on realization/implementation 🖝Asset built with reuse x asset built for reuse 🖝Asset reuse scope: 🖝 Across domains, across applications, within same application
- 5. Reuse sub-tasks 🖝Define boundaries of reusable assets (knowledge units with reuse potential) 🖝Organize and structure reusable assets together with descriptive and operational meta-data in searchable, persistent repositories 🖝Retrieve reusable assets 🖝Assemble/integrate reusable assets 🖝Adapt/modify reusable assets
- 6. Technical reuse inhibitors 🖝Current lack of: 🖝 Comprehensively reuse-oriented CASE tool 🖝 Model-level component libraries ready to reuse across platforms 🖝Immaturity of: 🖝 Comprehensive methodologies integrating multiple reuse techniques 🖝 KobrA 2002 integrates MDA, full-life cycle components with built-in contract testing, product lines, patterns, object-orientation, top-down recursive development 🖝 Only applied to a few real-world development projects 🖝 Standard languages to support model-level reuse: 🖝 UML2, OCL2, MOF2, XMI2 2003-2004 🖝 QVT for model-level mapping-based reuse 2005 🖝 Distributed architecture for third-party component publication, search and access 🖝 Web services 2003
- 7. Non-technical inhibitors 🖝 Economical: 🖝 Cut-throat competition of software industry, especially start-up survival 🖝 Leads to obsession with time-to-market of next product or product release 🖝 Reuse ROI only long-term and almost impossible to precisely or objectively estimate 🖝 Lack of business models for providers of components, non-code artifacts, non- code abstract artifact mappings and generators 🖝 Organizational and managerial: 🖝 Effective leveraging of reuse requires costly software house organization re- engineering, changing team structures, roles, incentives, productivity measures, 🖝 Educational and human resource: 🖝 Design for reuse and design from existing assets (as opposed to from scratch) heavily under-taught 🖝 Developers with reuse skills hard to find 🖝 Psychological: 🖝 “Not invented here” syndrome 🖝 Hacker mentality: code worship, autistic character structure 🖝 Resistance to change habits
- 8. Reuse metrics 🖝Overcoming non-technical reuse inhibitors, especially economic ones, requires estimating the cost-benefit of: 1. Reuse an available asset in an application development project 2. Pro-actively develop reusable assets for current and future projects 3. Launch an organization-wide systematic reuse program 🖝Pitfalls of the line of code metric: 🖝 Manually designed for reuse assets and automatically generated assets larger than manually design for one-shot use assets with equivalent functionalities for the application at hand 🖝 Versatile, multiple functionality components underused in any given application
- 9. Thank You