Logo des Repositoriums

Auflistung nach Autor:in "Momm, Christof"

1 - 6 von 6
  • Zeitschriftenartikel
    Bericht und Beiträge des gemeinsamen Workshops Software-Reengineering und Design for Future vom 3. - 5. Mai 2010 in Bad Honnef
    (Softwaretechnik-Trends Band 30, Heft 2, 2010) Gimnich, Rainer; Kaiser, Uwe; Momm, Christof; Quante, Jochen
  • Konferenzbeitrag
    Design for future (DFF 2011) – Workshop Report
    (Software Engineering 2011 – Workshopband, 2011) Momm, Christof; Sauer, Stefan; Trifu, Mircea
    Software altert und erodiert, obwohl sie ein immaterielles Gut ist. Denn sowohl die Anforderungen an die Software als auch ihre Umgebung ändern sich mit der Zeit. Bei Informationssystemen ist dieses Phänomen als „Legacy“ wohlbekannt. Das Problem existiert aber auch bei eingebetteten Systemen, wo komplexe Software in langlebigen technischen Geräten eingesetzt wird. Die ökonomischen Auswirkungen der Software-Alterung sind beträchtlich. Wissenschaft und Industrie sind deshalb aufgefordert, neue Methoden der Softwaretechnik für zukunftsfähige Software zu entwickeln und die erheblichen Investitionen in große Softwaresysteme zu schützen. Beim 3. Workshop „Design for Future“ des Arbeitskreises „Langlebige Softwaresysteme“ (L2S2) diskutierten Wissenschaftler und Praktiker Herausforderungen, Erfahrungen und Lösungen aus praktischer wie aus wissenschaftlicher Sicht.
  • Konferenzbeitrag
    Dritter Workshop zu „Design For Future - Langlebige Softwaresysteme“
    (Software Engineering 2011 – Fachtagung des GI-Fachbereichs Softwaretechnik, 2011) Sauer, Stefan; Momm, Christof; Trifu, Mircea
  • Konferenzbeitrag
    Programming in the large based on the business process modelling notation
    (Informatik 2005 – Informatik Live! Band 2, 2005) Emig, Christian; Momm, Christof; Weisser, Jochen; Abeck, Sebastian
    A software application is related to the processes it supports. Today, UML diagrams esp. use case diagrams and activity diagrams are often used to model the relevant aspects of the processes within the analysis phase. In the design phase the models are manually mapped to the business layer of the software application. In the context of Service-oriented Architectures (SOA) Programming in the Large takes a different approach: Business processes are described in a programming language, i.e. a process language which can be automatically mapped to an execution language and executed by a process engine. In this article we show how Programming in the Large can be practically applied in a software engineering process. We use the Business Process Model Notation (BPMN) as process programming language. A BPMN description can be mapped to the Business Process Execution Language (BPEL) which is a widely accepted standard to compose Web services.
  • Konferenzbeitrag
    A qualitative discussion of different approaches for implementing multi-tenant SaaS offerings1
    (Software Engineering 2011 – Workshopband, 2011) Momm, Christof; Krebs, Rouven
    The upcoming business model of providing software as a service (SaaS) not only creates new challenges for service providers but also for software engineers. To enable a cost-efficient service management, the hosted application should support multi-tenancy. For implementing multi-tenancy, several options are available, whereas all of them to a certain degree require a reengineering of the application at hand. Since for many applications this represents the next big evolution step, this paper is devoted to discussing different options for implementing multi-tenancy regarding the initial reengineering effort required for meeting the customer expectations versus cost-saving potential.
  • Konferenzbeitrag
    Towards a service level management framework for service value networks
    (INFORMATIK 2010. Service Science – Neue Perspektiven für die Informatik. Band 1, 2010) Momm, Christof; Schulz, Frank
    The ongoing trend towards a global services economy creates considerable market opportunities and challenges for providers of Software-as-a- Service (SaaS). For meeting customer expectations, an on-demand business model and a service-oriented infrastructure capable of composing services into service networks are the primary approach. Ensuring quality of service and providing detailed guarantees via service level agreements (SLAs) will be a major differentiator of future service offerings. This paper describes the challenges of SLA management for SaaS, an integrated solution that takes economic risk into account, and the software architecture of the chosen approach.