Advertisement

Model-Centric Approach to Software Design and Stakeholder-Specific Architecture Views in Scope of a Financial Institution

Conference paper
  • 396 Downloads
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 35)

Abstract

This paper presents a model-centric approach to software architecture & design in the scope of a large financial institution. One challenge in large organizations is the creation, aggregation and dissemination of architecture and design specifications by multiple stakeholders and outsourcing partners, at different times during the lifecycle of a software application. Lacking a common design language and format, the submission of manually written reports is common, which in turn facilitates redundancies in content and causes specifications at large to become cluttered, inconsistent and difficult to maintain. Manually written reports also tend to focus designers on producing nicely arranged diagrams and prosaic description, rather than on applying sound principles of software engineering. In turn, such specifications frustrate their subsequent use for coding, effectively rendering the design effort questionable. The approach presented defines a model-centric approach to enable different architecture views, based on models maintained by a team of designers. Employing a single-source concept, the same models serve the purpose of software design, coding and stakeholder-specific reports.

Keywords

UML in Software Engineering Stakeholder Views Architecture Documentation 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    IEEE: ANSI/IEEE Std 1471–2000 Recommended Practice for Architectural Description of Software-Intensive Systems (2000)Google Scholar
  2. 2.
    The Open Group: The Open Group Architectural Framework (TOGAF), http://www.opengroup.org/architecture/togaf
  3. 3.
    Kruchten, P.B.: The 4+1 view model of architecture. IEEE Software 28(11), 42–50 (1995)CrossRefGoogle Scholar
  4. 4.
    Hill, R.: An ISO/IEC 42010 (IEEE Std 1471) Annotated Bilbiography, Version 1.5 (2008)Google Scholar
  5. 5.
    Zachman, J.A.: A framework for information systems architecture. IBM Systems Journal 26(3), 276–292 (1987)CrossRefGoogle Scholar
  6. 6.
    Kruchten, P.B.: The Rational Unified Process: an introduction. Addison-Wesley, Reading (1999)Google Scholar
  7. 7.
    Clements, P.C., Bachmann, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., Stafford, J.: Documenting Software Architectures: views and beyond. Addison Wesley, Reading (2003)Google Scholar
  8. 8.
    Egyed, A., Medvidovic, N.: Architectural Representation in UML with View Integration. In: 2nd International Conference on the Unified Modelling Language (October 1999)Google Scholar
  9. 9.
    Hilliard, R.: Using the UML for Architectural Description. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  10. 10.
    Hofmeister, C., Nord, R.L., Soni, D.: Describing Software Architecture with UML. Siemens Corporate Research. Kluwer Academic Publishers, Dordrecht (1999)Google Scholar
  11. 11.
    Murer, S., Worms, C., Furrer, F.J.: Managed Evolution. Informatik-Spectrum. Springer, Heidelberg (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  1. 1.Senior Software Engineer CREDIT SUISSE AGIT Private BankingZurichSwitzerland

Personalised recommendations