A comparison of approaches to reuse investment analysis

Favaro, John

doi:10.1109/icsr.1996.496121

Cited by 28 publications

(18 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3. Reuse Investment Analysis-Analyze the measurements and estimates to gauge the state of the reuse business and identify what corrections might be needed [4]. If these steps are applied to SOA (Figure 1), mutual support between the Application Generator and Service Provider communities is necessary.…”

Section: Lesson: Quantify Return On Investmentmentioning

confidence: 99%

“…Similar to today's system administrators, they provide a middle ground recomposition of applications that doesn't require in-depth programming skills at the level of an Application Generator. 4 SOA Enterprises are business entities that leverage SOA techniques for commercial or other value-adding justifications.…”

Section: Terminology and Contextmentioning

confidence: 99%

“…The paper draws heavily from the reuse literature, which is directly associated with COTS and COTS-Based Systems (CBS) due to the strong reliance on reuse to generate COTS markets. After some background context setting, the paper reflects on SOA challenges as lessons learned in three key areas: (1) markets and business incentives, (2) software engineering process, and (3) organizational relationships (in sections [3][4][5]. In Section 6 a summary checklist of considerations, for those that are targeting SOA as their architecture of choice, is provided.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

What COTS and Software Reuse Teach Us about SOA

Anderson

2007

2007 Sixth International IEEE Conference on Commercial-Off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)

View full text Add to dashboard Cite

Many organizations are increasingly looking for techniques that can lead to large-scale (and often dynamic) integration and interoperation of new and existing components, services, or systems. Service0riented architecture (SOA) holds great promise as an approach that can facilitate these desires.Over the past decades, organizations have tried various development software reuse approaches, such as commercial off-the-shelf (COTS) based systems, product line engineering, and frames. As we move into this new world of highly interoperable systems, we should take advantage of the lessons taught by the development of these approaches. This paper identifies key lessons from COTS and software reuse that can be applied to SOA.

show abstract

Section: Lesson: Quantify Return On Investmentmentioning

confidence: 99%

Section: Terminology and Contextmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

What COTS and Software Reuse Teach Us about SOA

Anderson

2007

2007 Sixth International IEEE Conference on Commercial-Off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)

View full text Add to dashboard Cite

show abstract

“…al., 2002) and (Clements et. al., 2002); the concurrent system and software engineering approach in Chapter 15; the software traceability techniques in Chapter 31; and the value-based software product line analyses in (Favaro, 1996) and (Faulk et. al., 2000).…”

Section: Value-based Software Engineering (Vbse) Background and Agendamentioning

confidence: 99%

Value-Based Software Engineering: Overview and Agenda

Boehm¹

2006

Value-Based Software Engineering

View full text Add to dashboard Cite

Much of current software engineering practice and research is done in a value-neutral setting, in which every requirement, use case, object, test case, and defect is equally important. However most studies of the critical success factors distinguishing successful from failed software projects find that the primary critical success factors lie in the value domain.The value-based software engineering (VBSE) agenda discussed in this chapter and exemplified in the other chapters involves integrating value considerations into the full range of existing and emerging software engineering principles and practices. The chapter then summarized the primary components of the agenda: value-based requirements engineering, architecting, design and development, verification and validation, planning and control, risk management, quality management, people management, and an underlying theory of VBSE. It concludes by approaches for going toward VBSE at the project, organization, national, or global level.

show abstract

“…A comparative analysis in 1996 illustrated how the Present Value approach is superior to other techniques for project valuation such as "time to payback" or "cost-benefit ratio" [14]. Option theoretic techniques that augment Present Value techniques to capture the value of strategic options have been introduced in VBIM and were discussed at length in [6].…”

Section: Valuationmentioning

confidence: 99%