Fifteen Years of Service-Oriented Architecture at Credit Suisse

Murer, Stephan; Hagen, Claus

doi:10.1109/ms.2013.137

Cited by 12 publications

(7 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3). Besides IT consulting firms, other companies have reported similar use of SRAs without using a corporate reference model, such as Volvo [43]), Océ [30], Credit Suisse [44], and the Dutch e-government [38]. It is also important to note that all aforementioned SRAs are based on practical experience in industry.…”

Section: Limitations Of the Studymentioning

confidence: 99%

Benefits and drawbacks of software reference architectures: A case study

Martnez-Fernndez

Ayala

Franch

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

Context:\ud Software Reference Architectures (SRAs) play a fundamental role for organizations whose business greatly depends on the efficient development and maintenance of complex software applications. However, little is known about the real value and risks associated with SRAs in industrial practice. \ud Objective:\ud To investigate the current industrial practice of SRAs in a single company from the perspective of different stakeholders. Method An exploratory case study that investigates the benefits and drawbacks perceived by relevant stakeholders in nine SRAs designed by a multinational software consulting company. \ud Results: The study shows the perceptions of different stakeholders regarding the benefits and drawbacks of SRAs (e.g., both SRA designers and users agree that they benefit from reduced development costs; on the contrary, only application builders strongly highlighted the extra learning curve as a drawback associated with mastering SRAs). Furthermore, some of the SRA benefits and drawbacks commonly highlighted in the literature were remarkably not mentioned as a benefit of SRAs (e.g., the use of best practices). Likewise, other aspects arose that are not usually discussed in the literature, such as higher time-to-market for applications when their dependencies on the SRA are managed inappropriately. \ud Conclusions:\ud This study aims to help practitioners and researchers to better understand real SRAs projects and the contexts where these benefits and drawbacks appeared, as well as some SRA improvement strategies. This would contribute to strengthening the evidence regarding SRAs and support practitioners in making better informed decisions about the expected SRA benefits and drawbacks. Furthermore, we make available the instruments used in this study and the anonymized data gathered to motivate others to provide similar evidence to help mature SRA research and practice.Peer ReviewedPostprint (author's final draft

show abstract

Section: Limitations Of the Studymentioning

confidence: 99%

Benefits and drawbacks of software reference architectures: A case study

Martnez-Fernndez

Ayala

Franch

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…This amounts to 27 Java statements per function point. The system was changing at a rate of only 9% per annum, but even at 9% this adds up to 16 At least three persons were required to maintain this system, three Java specialists who were not available for developing newer applications elsewhere. We do not take business-criticality into account, for then more than three persons might be needed for the sake of operational continuity.…”

Section: The Increasing Burden Of Software Maintenancementioning

confidence: 99%

“…The maintenance of the core solution is left to the solution providers and the users can concentrate their limited capacity on configuring the delivered solution to fit their needs. Cloud services make this possible as demonstrated by recent reports on their usage [16]. Users can build wrappers around the services they use to manipulate the in-going requests and the out-coming responses.…”

Section: The Issue Of Customized Versus Standard Softwarementioning

confidence: 99%

From Software Development to Software Assembly

Sneed

Verhoef

2016

IEEE Softw.

View full text Add to dashboard Cite

The growing burden of maintaining customized software together with the lack of skilled programming personnel is forcing IT users to look for other ways to produce software. It is no longer feasible for every user to develop one's own software including the nuts and bolts. There are simply not enough skilled developers around. The IT labor shortage exposes the weaknesses in the current preindustrial mode of production. It is high time that users stop developing their own customized software and turn to ready-made, standard components to fulfill their business requirements. Cloud services may be one way of achieving that goal.

show abstract

“…The common scenario is that these RAs provide common services that then may be reused in the different front-ends or channels (e.g., desktop applications, web client applications, mobile applications, ATMs and so on). An example is Credit Suisse (Murer and Hagen 2013).…”

Section: Similar Contexts Of Ras In Practicementioning

confidence: 99%

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Martínez‐Fernández

Ayala

Franch

et al. 2014

J Softw Eng Res Dev

View full text Add to dashboard Cite

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results:The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.

show abstract

Fifteen Years of Service-Oriented Architecture at Credit Suisse

Cited by 12 publications

References 1 publication

Benefits and drawbacks of software reference architectures: A case study

Benefits and drawbacks of software reference architectures: A case study

From Software Development to Software Assembly

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Contact Info

Product

Resources

About