Requirements Engineering for Cloud Computing
|
|
- Jesse Rodgers
- 8 years ago
- Views:
Transcription
1 Journal of Communication and Computer 8 (2011) Holger Schrödl and Stefan Wind Chair of Business Informatics and Systems Engineering, University of Augsburg, Augsburg 86159, Germany Received: March 24, 2011 / Accepted: May / Published: September 30, Abstract: Cloud computing gets increasingly established in industrial practice as an option for modeling cost-efficient and demand-oriented information systems. Despite the increasing acceptance of cloud computing within the industry many important questions remain unanswered. Issues related to the best architectures, legal issues and pricing models, suppliers of cloud-based solutions are faced with the question of appropriate engineering. This means eliciting optimum understanding of the customer s and implementing this into appropriate of the solution to be realized. This contribution evaluates selected engineering methods in terms of their applicability to the specific of cloud-based solutions. Therefore a comparison framework containing the features of cloud computing is developed suitable for a structured comparison of different engineering methods. This comparison framework is applied to four established process models for engineering followed by recommendations for a engineering system adapted to cloud computing. Key words: Requirements engineering, cloud computing, V-model, volere, XP, RUP. 1. Introduction While cloud computing has already found its way into industrial practice, there continue to be considerable deficits in the scientific basis [1]. One such shortfall is engineering for cloud computing. While some initial research initiatives have been carried out under the sub-domain of Software as a Service (SaaS) [2, 3], none has yet been carried out for cloud computing overall. Because of its specific characteristics and the various fields, it is necessary to make a distinction between specific and traditional. Forrester Research Consultants has investigated eleven different cloud computing vendor offers with regard to fields of application, costs and commercial benefits, and has drawn as conclusion: Many offers do not meet-or only partially meet-customers [4]. The success of cloud computing therefore depends on how Stefan Wind, research assistant, research fields: cloud computing, engineering, Stefan.wind@wiwi.uni-augsburg.de. Corresponding author: Holger Schrödl, research assistant, research fields: value chain management, cloud computing. holger.schroedl@wiwi.uni-augsburg.de. well customers and other stakeholders and wishes are met. The basis for developing successful offers is a engineering system adapted to cloud computing. The success of development processes and projects essentially depends on whether the results meet the of stakeholders (such as the customer, executive management, legislators, etc.). A central factor here is the implementation of an appropriate and professional engineering tool [5-7]. Errors concerning the are one of the main reasons why development projects fail [8]. Evidence of this is provided on a regular basis by the CHAOS study carried out by the American consultancy company, the Standish Group. In a recent study carried out in 2009 almost 48% of the problems or shortcomings in software development could be traced back to poor engineering [9]. Moreover, studies carried out in a wide variety of domains (product development, software engineering, etc.) show that errors made while determining have a major influence on the development process [10]. And the work and costs involved in eliminating the errors
2 708 increase disproportionately to the time at which they occur [11]. The reason for this is the early point in time within the process at which the are defined. It means than any errors occurring at that early stage will affect all the future phases (such as design, implementation etc.) [7]. In his error pyramid Leffingwell works on the basis that fixing an error at the implementation stage is up to 100 times more difficult, and at the maintenance stage, up to 1000 times more difficult than at the start of development stage [12]. Cloud computing is a subject in which, in general, company IT managers are showing a great deal of interest. According to the latest survey carried out by Sterling Commerce GmbH, a software supplier in Dusseldorf, 87% of all senior IT managers in Germany are planning to move to cloud-based information systems in the B2B sector [13]. The main driver of such considerations is the survey on cost pressures: most companies intend to reduce costs by implementing cloud-based IT structures, caused by services accounting dependent on utilisation. Other aspects are: improved deployment of in-house IT staff, a reduction in manual processes, and improvement to transparency of processes. However, when considering cloud-based systems, the most important feature is to be found in the areas of security and trust [14]. The paper is organized as follows: Section 2 discusses different engineering models. In section 3, a comparison framework for engineering in cloud computing is developed. In section 4, the comparison framework is applied to different engineering models to conduct a structured comparison. Section 5 concludes the paper and gives an outlook to future research. 2. Requirements Engineering Models Various process models were investigated within a broad literature research framework to find out the extent to which they are suitable to provide general support for engineering. To this end basically differing groups of models and approaches were identified, which have come about on the basis of different philosophies, traditions and viewpoints. This included a consideration of monumental and agile process models [15]. Added to these models are approaches developed especially for engineering purposes [6]. These claim to avoid the weaknesses of existing process models. 2.1 V Model The V model produced by the German Federal Ministry of Internal Affairs (BMI) is intended to support the execution of (software)- projects in every size [16]. The model is one of the most well known system development models in Germany [6]. It follows the concept of successively dividing the overall system, refining it down from the rough to the fine detail, until realizable components emerge. Requirements engineering is one of the fourteen activities included in the V model, each of which provides a recommendation for handling the execution of the various project management processes. The model distinguishes depending on the type of project certain decision points need to be met. The V model provides the following steps in the engineering process: description of initial situation and objectives, drawing up functional, drawing up non-functional, establishing risk acceptance, drawing up draft of life cycle and overall system architecture, analyzing quality of, drawing up scope of supply and acceptance criteria. The name given to this component is fairly misleading because not all activities are combined here in connection with. Rather, only some of the are considered, and the contracting client then summarizes these into a set of specifications. In this regard the component dealing with setting up the system is much more comprehensive, because in this case documents and activities for continued handling are made available to the contractor [16].
3 Rational Unified Process (RUP) The Rational Unified Process (RUP) is a software development process model and it consists of two process dimensions [17]. The time dimension indicates a sub-division into a rough structure (phases) and a refined structure (iterations). The second dimension is concerned with the technical side and divides these into disciplines, of which there are six primary process disciplines (including requirement) and three infrastructure disciplines. Each discipline has its own defined workflow. The engineering discipline pursues the objective of enabling reliable specifications and development, as well as modifications to a system. For example this means drawing up a uniform picture about the functionality that the system is to perform for all stakeholders, and creating a basis for estimating costs and time parameters [17]. Essentially, engineering in the RUP consists of the six following principle activities [18]: analyzing the problem, understanding the stakeholders needs, defining the system, managing the scope of the system, changing, refining the system definition. These activities are logically connected to one another and should not be viewed as being purely sequential. 2.3 Volere The Volere approach was developed by Atlantic Systems Guild and is derived from the Italian verb volere (to want, wish) [17]. The process was developed especially for engineering and, besides techniques for determining, also provide templates for structuring specifications [19]. The approach is organized as follows: Motivation (the purpose of the project or product); Restrictions and specifications for the project (conditions and assumptions); Functional (such as Use Case models); Non-functional (usability etc.); Project information (e.g., risks, costs, task lists). Volere provides users with a systematic, structured and very comprehensive engineering template. All the information in the template is held in a single document (monolithic), conversely to RUP. In order to develop, Volere prefers a template. Quality assurance is an intermediate step (so-called gateway) which is used between specification and analysis [19]. The process should also be considered as being iterative. 2.4 Extreme Programming (XP) XP was developed by Kent Beck, Ward Cunningham and Ron Jeffries and was launched in 1999 with the publication of their book: extreme Programming ex-plained [15]. Extreme Programming is a lightly-weighted development method which was positioned as a counter-movement to heavily-weighted methods such as the V-model [20]. XP pursued the objective of formulating software development projects more efficiently by slimming them down greatly and aligning them to the customer as well as to quality issues [21]. As with RUP, XP has an iterative and incremental character. At first glance XP and a fundamental analysis seem to contradict one another, but XP is concerned with getting an implementable system onto the market [15, 21]. However in this model too there are approaches that are well supplemented by analysis. These are User Stories, the Planning Game and the System Metaphor. For example, User Stories are short reports made by users, which are initially gathered together in an informal manner; details are gradually added and they are then evaluated. It is possible to consider these in comparison with. 3. A Comparison Framework for Requirements Engineering in Cloud Computing A classification system has been drawn up in cloud
4 710 computing in order to develop a comparison framework for engineering models, to provide optimum support in this area. In general we speak of a classification system if an object under consideration is first categorized according to certain characteristics, and the relevant specifications are determined for these characteristics [22]. No link is made between the various criteria [23]. Cloud computing makes use of a four-part conceptual model for the classification developed here (Fig. 1). 3.1 Characteristics Relating to the Cloud Offer, from the Customer s Viewpoint The topmost level of developing a Cloud offer from the customer s viewpoint does not differ greatly from the traditional software engineering field. For this reason, to develop a cloud offer, the following established characteristics from the software domain are significant. The first characteristic is understood to be the specification for the entire cloud offer, which is often subsumed under the term Requirements Elicitation [24]. This is important firstly in order to understand the background and motivation of the stakeholders, and secondly to understand the objectives that the cloud solution has to meet. The requirement specification must be supported by means of efficient techniques such as interviews, workshops, scenarios, as well as transaction analyses, and must be able to take into consideration several stakeholders at once [6, 8]. A crucial characteristic is the analysis and agreement. During this phase the need to be firmed and consensus obtained from all stake-holders. The model must therefore be in a position to deal with conflicts between the different types of requirement, to help to find the solution, and then to contribute towards producing a base supported by all stakeholders [8, 24]. This is particularly important due to the special situation in cloud computing, with many different stakeholders and, to an extent, competing. The third characteristic is the formal documentation Fig. 1 Conceptual cloud architecture.
5 711 and description of the, and this represents the basis of all further activities [7]. Only once the have been described is it possible to assign them to their various sources and monitor them. The documentation can be implemented in various ways, including essays, use cases or style guides [6]. 3.2 Characteristics Relating to the Cloud Offer, from Supplier s Viewpoint Suppliers of Cloud offers record the customer s offered within the Cloud, using them to implement a solution. For this reason the supplier must be able to formulate appropriately the of the individual components to be used. The first characteristic is considered to be the possibility of validating. This is intended to check whether the documentation actually expresses the stakeholders [25]. The validation process can be helped by using techniques such as reviews, check-lists, prototypes and walkthroughs. A further important characteristic is the capacity to take account of non-functional. Rupp stresses that this type of requirement is often forgotten, and is awarded less value than functional properties [6]. Meeting such criteria opens up many opportunities, such as satisfied customers, increased legal security, and more complete specifications. It is precisely in such complex structures as cloud computing that this is given great importance [24]. 3.3 Characteristics Relating to Orchestration Orchestration is of central importance when the Cloud offer is implemented [26]. It represents the connecting element between the individual application components, and can therefore be described as the implementation of the solution architecture. The first characteristic in this area is the architectural capacity of engineering. It must be possible to elicit the of complete information sys-tem architecture. In particular this includes support for formal modeling forms for information system architectures such as ARIS or UML [27]. A second characteristic is identified as being the structured elicitation of infrastructure. These infra-structure must be allocated into areas of service quality, security, and economic dimension [14]. 3.4 Characteristics Relating to SaaS and Applications Components Within the framework of developing SaaS it is necessary to take into account specific characteristics such as the integration of multi-discipline components from different domains, or different sources, which affect the engineering process [3]. From this can be derived the following characteristics for engineering models. The first characteristic is a coordinated and integrated engineering process for individual components such as software and services, which are mutually dependent upon one another during and after development [3, 6-7]. A crucial characteristic for the comparison framework is the comprehensive inclusion of the customer into the entire development process during every phase. Even where this can be difficult [28, 29], due to different language bases and differing levels of understanding by developers, this must not be abandoned. Third, in the framework of SaaS it is crucial to prepare an optimally functioning change management system for the phase following delivery, in order to be able to implement any modifications in the service area [3]. A clear traceability system for the when implemented is of special importance here in order to avoid undesirable counter-effects. A further important characteristic is the capacity to be able to elicit the source of the requirement when it is recorded. A more detailed differentiation is necessary be-cause not every elicitation method (workshops,
6 712 interviews, scenario techniques, etc.) [7] is appropriate in equal extent for every type of source (customer, provider, etc.). In particular, when ascertaining in the sense of a comprehensive view, it is necessary to consider every possible source, in order, as already mentioned, to assure traceability, validation and a functioning change management system. The above-mentioned capability is equally important within the change management framework. The reason for this is the two-way dependency of the system components, which can have an effect on software and services. These must therefore be considered carefully before making any changes. 4. Applying the Comparison Framework The characteristics deduced from the above paragraphs are set out in Table 1. It can be seen from the comparison that, at the current state of development, there is no universal and ideal support for engineering in the development of cloud computing solutions. 4.1 V-Model The V-model does not offer universal engineering support in the development of cloud computing solutions. A basic criticism here is that it is seen as the task of the contracting client to establish the [15]. Since the model is kept very general and is intended to cover any type of project [16], it fails to a large extent to provide support in SaaS. One of the indications of this is that there is no supra-disciplinary coordination of emanating from the software and service areas. Furthermore no support whatsoever is offered for change management in the phase following delivery; the core process of problem and change management is applied only while the project is in progress. The customer is partially included into the development process because it has to accept documents issued at the various phases of the project. A better picture emerges in the area of the total solution. On one hand the model aids the process of Table 1 Comparison framework. Area Characteristic V-Model RUP XP Volere Support with ascertaining ( ) Support with analysing and agreeing Validating Taking account of non-functional Cloud offering (Customer viewpoint) Cloud offering (Supplier viewpoint) Orchestration SaaS / Application Components Management methods and change ( ) management Architectural capability ( ) Structured elicitation of infrastructure ( ) Coordinated and integrated RE for all single components of SaaS Better customer integration into the ( ) ( ) RE-process Consideration of changes of ( ) ( ) after/during delivery Consideration of the source of ( ) during elicitation Consideration of the source of during ( ) ( ) change management Key: Characteristic met, ( ) Characteristic partially met, Characteristic not met. determining non-functional as a separate process step. Since the V-model is based on documentation [16], it also offers good support for documentation. 4.2 Rational Unified Process (RUP) Since RUP was originally designed for software development, it indicates system problems in other areas, such as in the service environment [18]. For this reason it is unable to offer universally optimum support for SaaS. For example, it lacks a coordinated and
7 713 integrated engineering process for individual components, a change management process for the phase after delivery, and support for managing after the development process is completed in full. It offers only partial support for the inclusion of the customer into the entire development process (this tending to be at the start of the project). In general, the model offers good support in the traditional areas of engineering, including the consideration of non-functional [17]. Nevertheless it cannot help in the SaaS framework, and particularly not in ascertaining the source of. RUP is also lacking orchestration characteristics, particularly in its description of the agility of architecture. 4.3 Extreme Programming (XP) The XP model, one of the most well-known representatives of agile methods [20], was originally used for software development. However, as opposed to RUP it offers better support for SaaS which can be traced back to the agile values on which it is based (e.g. strong weighting on customer). There is partial support for customer choices that go outside the boundaries of the domain, because XP provides for various roles such as customer, contracting Client etc.. Customer integration throughout the entire development process is one of XP s strengths and is supported by the On-site customer practice [21]. Because of XP s objective of delivering executable increments as fast as possible and then to consider the customer s feedback when planning the next increment, a rudimentary change management does take place after delivery. But this only applies up until the project has been concluded. For this reason it provides no management process for after final delivery (e.g., in the form of a library). The capability to ascertain the source of exists in principle, because the are often ascertained in a joint planning game. It offers the option of going into the source in explicit detail. However, in the change management process, consideration of the source is provided only partial. In the total solution area the defined characteristics are met only partially as a result of XP s properties. The elicitation of is assisted by means of the planning game [21]. There is no support for validation or for change management. Adaptations to the product are made only until the customer is satisfied. However, due to the specific characteristics of cloud computing, this appears to be difficult. Nor is considering the relevant architectural one of XP s strengths. It is due to this shortfall in its options for offering opportunities to elicit agile architecture, along with a structured elicitation of infrastructure, that XP indicates unsatisfactory possibilities for implementing RE for cloud computing. 4.4 Volere Compared with those described above, the Volere model was developed especially to handle engineering [19]. However, it has weaknesses in the area of SaaS. It does not support a coordinated and integrated engineering system beyond the domains, because this is not provided within the model. After delivery the model also offers partial support for change management by means of an active feedback system between customer and supplier. The, together with their sources, are collected into a library, and are also subject to rudimentary management after the development work is completed. But there is a lack of specific methods for efficient application. Other lacking areas are in the architecture capacity and in architecture agility. As expected, it fully supports the traditional tasks of engineering such as eliciting, coordinating, prioritising and documentating, validating and managing, and also considering the non-functional. 5. Conclusions The objective of this article was to validate
8 714 established process models for engineering in terms to their suitability for cloud computing. A comparison framework was developed on a broad literature study. This comparison framework covers 12 characteristics in four categories and represents an opportunity to compare process models in a structured manner. The V-model, RUP, XP and Volere process models were evaluated and discussed in more detail. The results enabled us to show that none of the established models is suitable to cover the needs of a specific engineering for cloud computing. Existing shortfalls were identified, and, building on these, recommendations have been derived for cloud computing engineering. Within the context of this article cloud computing is understood to be component-based applications development. Since the term cloud computing includes other aspects, the results are seen as limited. If the term cloud computing is extended to include the provision of infrastructure and application, the result could be that the comparison framework be expanded. A second limitation consists in the choice of the models under consideration. This might be extended to compare not only typical representatives of a particular type of engineering models but also more specific models. This article represents a first step for engineering in cloud computing. It is intended to set the foundation for a reference model for engineering for cloud-based solutions, which in practice will result in a considerable improvement in the development of customer-specific information systems based on cloud architecture. References [1] S. Leimeister, C. Riedl, M. Böhm, H. Krcmar, The business perspective of cloud computing: actors, roles, and value networks, 18th European Conference on Information Systems (ECIS), [2] M. Berkovich, S. Esch, J.M. Leimeister, H. Krcmar, Requirements engineering for hybrid products as bundles of hardware, software and service elements: a literature review, Internationale Tagung Wirtschaftsinformatik, Wien, Österreich, [3] M. Berkovich, S. Esch, J.M. Leimeister, H. Krcmar, Torwards Requirements Engineering for, Software as a Service, MKWI Göttingen, [4] Forrester, TechRadar for infrastructure & operations professionals, Cloud Computing, Forrester (2009). [5] U. Lindemann, Methodische Entwicklung Technischer Produkte: Methoden Flexibel UND Situationsgerecht Anwenden. 2. Aufl., Springer Verlag, Berlin, [6] C. Rupp, Requirements-Engineering UND Management, 4. Aufl., Carl Hanser Verlag, München, Wien, [7] K. Pohl, Requirements Engineering, 2. Aufl., dpunkt Verlag, Heidelberg, [8] A. Aurum, C. Wohlin, Engineering and Managing Software Requirements, Springer Verlag, Berlin, [9] Standish Group: CHAOS Report, available online at: [10] T. Hall, S. Beecham, A. Rainer, Requirements problems in twelve software companies: an empirical analysis, IEE Proceedings Software 149 (2002) [11] M. Berkovich, J.M. Leimeister, H. Krcmar, Ein Bezugsrahmen für Requirements Engineering hybrider Produkte, Multikonferenz Wirtschaftsinformatik, Göttingen, [12] H. Dörnemann, R. Meyer, Anforderung Management Kompakt Mit Checklisten, Spektrum Akademischer Verlag, Heidelberg, Berlin, [13] Sterling Commerce: 87 Prozent Deutscher Unternehmen Planen Investitionen in Cloud-Services, available online at: [14] C. Weinhardt, A. Anandasivam, B. Blau, N. Borissov, Th. Meinl, W. Michalk, J. Stößer, Cloud-Computing-Eine Abgrenzung, Geschäftsmodelle und Forschungsgebiete, in: Wirtschaftsinformatik, 2009, pp [15] H. Balzert, Lehrbuch der Softwaretechnik: Softwaremanagement, 2. Aufl., Spektrum Akademischer Verlag, Heidelberg, [16] M. Reinhold, V-modell XT und anforderungen, in: Rupp, Chris (Hrsg.): Requirements-Engineering und Management, 4. Aufl., Carl Hanser Verlag, München, Wien, [17] H. Dörnemann, R. Meyer, Anforderungs Management Kompakt-mit Checklisten, Spektrum Akademischer Verlag, Heidelberg, Berlin, [18] G. Versteegen, A. Heßeler, C. Hood, C. Missling, R. Stücka, Anforderungs Management, Springer Verlag, Berlin u. a., [19] S. Robertson, J. Robertson, Mastering the Requirements Process, 2. Aufl., ACM Press Inc., [20] H. Wolf, S. Roock, M. Lippert, extreme Programming, 2. Aufl., dpunkt Verlag, Heidelberg, 2005.
9 715 [21] K. Beck, Extreme Programming Explained, Embrace Change, Addison-Wesley Reading, MA, [22] G. Engelien, Der Begriff der Klassifikation, Buske Verlag, Hamburg, [23] H. Knoblich, Die typologische Methode in der Betriebswirtschaftslehre, Wirtschaftswissenschaftliches Studium 1, 1972, pp [24] I. Sommerville, G. Kotonya, Requirements Engineering: Processes and Techniques, Wiley & Sons, [25] B.H.C. Cheng, J.M. Atlee, Research Directions in Requirements Engineering, Future of Software Engineering, [26] S. Ried, Market Overview: The Middleware Software Market, Forrester, [27] M.A. Vouk, Cloud computing-issues, research and implementations, Journal of Computing and Information Technology 16 (2008) [28] M. Abramovici, S. Schulte, Optimizing customer satisfaction by integrating the customer s voice into product development, ICED'07 Paris, France, [29] Agilemanifesto: Manifesto for Agile Software Development, available online at:
Please quote as: Berkovich, M.; Esch, S.; Leimeister, J. M. & Krcmar, H. (2010): Towards Requirements Engineering for "Software as a Service".
Please quote as: Berkovich, M.; Esch, S.; Leimeister, J. M. & Krcmar, H. (2010): Towards Requirements Engineering for "Software as a Service". In: Multikonferenz Wirtschaftsinformatik (MKWI) 2010, Göttingen,
More informationTowards Requirements Engineering for Software as a Service *
MKWI 2010 Software-Industrie 517 Towards Requirements Engineering for Software as a Service * Marina Berkovich 1, Sebastian Esch 1, Jan Marco Leimeister 2, Helmut Krcmar 1 1Lehrstuhl für Wirtschaftsinformatik,
More informationPlease quote as: Kortler, S.; Helms, B.; Berkovich, M.; Lindemann, U.; Shea, K.; Leimeister, J. M. & Krcmar, H. (2010): Using MDM-methods in order to
Please quote as: Kortler, S.; Helms, B.; Berkovich, M.; Lindemann, U.; Shea, K.; Leimeister, J. M. & Krcmar, H. (2010): Using MDM-methods in order to improve managing of iterations in design processes.
More informationFamily: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to
Unified Process Family: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to various application domains different organizations
More informationSoftware Engineering
1 Software Engineering Lecture 2: Software Life Cycles Stefan Hallerstede Århus School of Engineering 25 August 2011 2 Contents Naive Software Development Code & Fix Towards A Software Process Software
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationAn Integrated Quality Assurance Framework for Specifying Business Information Systems
An Integrated Quality Assurance Framework for Specifying Business Information Systems Frank Salger 1, Stefan Sauer 2, Gregor Engels 1,2 1 Capgemini sd&m AG, Carl-Wery-Str. 42, D-81739 München, Germany
More informationInvestigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations
Investigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations Mennatallah H. Ibrahim Department of Computers and Information Sciences Institute
More informationA UML 2 Profile for Business Process Modelling *
A UML 2 Profile for Business Process Modelling * Beate List and Birgit Korherr Women s Postgraduate College for Internet Technologies Institute of Software Technology and Interactive Systems Vienna University
More informationIT3205: Fundamentals of Software Engineering (Compulsory)
INTRODUCTION : Fundamentals of Software Engineering (Compulsory) This course is designed to provide the students with the basic competencies required to identify requirements, document the system design
More informationWeb Application Development Processes: Requirements, Demands and Challenges
Web Application Development Processes: Requirements, Demands and Challenges THAMER AL-ROUSAN 1, BASEM HADIDI 2, SHADI ALJAWARNEH 3 1, 3 Faculty of Science and Information Technology, Isra University, Amman,
More informationStory Card Based Agile Software Development
Story Card Based Agile Software Development Chetankumar Patel, and Muthu Ramachandran Leeds Metropolitan University, UK c.patel@leedsmet.ac.uk Abstract The use of story cards for user stories in many Extreme
More informationV-Modell XT. Part 1: Fundamentals of the V-Modell
V-Modell XT Part 1: Fundamentals of the V-Modell THE V-MODELL XT IS PROTECTED BY COPYRIGHT. BUNDESREPUBLIK DEUTSCHLAND 2004. ALL RIGHTS RESERVED. COPYRIGHT RESERVED BUNDESREPUBLIK DEUTSCHLAND 2004.THE
More informationAgile Usability Engineering by Thomas Memmel
1 von 4 02.07.2007 10:28 Agile Usability Engineering by Thomas Memmel Agile Usability Engineering is a concept to describe a combination of methods and practices of agile development and usability engineering.
More informationTOGAF usage in outsourcing of software development
Acta Informatica Pragensia 2(2), 2013, 68 76, DOI: 10.18267/j.aip.25 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky
More information6 Contracts and Scenarios in the Software Development Process
6 Contracts and Scenarios in the Software Development Process Summary: Software development processes play an important role in the successful and timely delivery of software. There are different approaches
More informationMulti-Dimensional Success Factors of Agile Software Development Projects
Multi-Dimensional Success Factors of Agile Software Development Projects Nagy Ramadan Darwish Department of Computers and Information Sciences Institute of Statistical Studies and Research Cairo University
More informationSOFTWARE PROCESS MODELS
SOFTWARE PROCESS MODELS Slide 1 Software Process Models Process model (Life-cycle model) - steps through which the product progresses Requirements phase Specification phase Design phase Implementation
More informationTraceability Patterns: An Approach to Requirement-Component Traceability in Agile Software Development
Traceability Patterns: An Approach to Requirement-Component Traceability in Agile Software Development ARBI GHAZARIAN University of Toronto Department of Computer Science 10 King s College Road, Toronto,
More information11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
More informationCS4507 Advanced Software Engineering
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
More informationApplying Agile Methods in Rapidly Changing Environments
Applying Agile Methods in Changing Environments 7/23/2002 1 Applying Agile Methods in Rapidly Changing Environments Peter Kutschera IBM Unternehmensberatung GmbH Am Fichtenberg 1, D-71803 Herrenberg Steffen
More informationA Framework for Software Product Line Engineering
Günter Böckle Klaus Pohl Frank van der Linden 2 A Framework for Software Product Line Engineering In this chapter you will learn: o The principles of software product line subsumed by our software product
More informationTowards Collaborative Requirements Engineering Tool for ERP product customization
Towards Collaborative Requirements Engineering Tool for ERP product customization Boban Celebic, Ruth Breu, Michael Felderer, Florian Häser Institute of Computer Science, University of Innsbruck 6020 Innsbruck,
More informationBuild the Right Software First Time
Build the Right Software First Time are the most misunderstood part of systems development, and yet the most crucial. must be correct if the rest of the development effort is to succeed. This workshop
More informationSoftware Engineering and Scientific Computing
Software Engineering and Scientific Computing Barbara Paech, Hanna Valtokari Institute of Computer Science Im Neuenheimer Feld 326 69120 Heidelberg, Germany http://se.ifi.uni-heidelberg.de paech@informatik.uni-heidelberg.de
More informationSoftware Quality Development and Assurance in RUP, MSF and XP - A Comparative Study
Software Quality Development and Assurance in RUP, MSF and XP - A Comparative Study Wolfgang Zuser Vienna University of Technology wolfgang.zuser@inso.tuwien.ac.at Stefan Heil Capgemini Consulting Austria
More informationRequirements Engineering and Agile Software Development
1 Requirements Engineering and Agile Software Development Frauke Paetsch Fachhochschule Mannheim frauke.paetsch@web.de Dr. Armin Eberlein University of Calgary eberlein@enel.ucalgary.ca Dr. Frank Maurer
More informationBUSINESS RULES AS PART OF INFORMATION SYSTEMS LIFE CYCLE: POSSIBLE SCENARIOS Kestutis Kapocius 1,2,3, Gintautas Garsva 1,2,4
International Conference 20th EURO Mini Conference Continuous Optimization and Knowledge-Based Technologies (EurOPT-2008) May 20 23, 2008, Neringa, LITHUANIA ISBN 978-9955-28-283-9 L. Sakalauskas, G.W.
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationSoftware Development Process and Activities. CS 490MT/5555, Fall 2015, Yongjie Zheng
Software Development Process and Activities CS 490MT/5555, Fall 2015, Yongjie Zheng Software Process } A set of activities that leads to the production of a software product } What product we should work
More informationOpen S-BPM: Goals and Architecture
Open S-BPM: Goals and Architecture Albert Fleischmann Werner Schmidt Table of Content 1 Introduction... 2 2 Mission, Vision and Objectives... 2 3 Research and Development Areas... 3 4 Open S-BPM Architecture...
More informationDEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES Robert M. Bruckner Vienna University of Technology bruckner@ifs.tuwien.ac.at Beate List Vienna University of Technology list@ifs.tuwien.ac.at
More informationDevelopment models. 1 Introduction. 2 Analyzing development models. R. Kuiper and E.J. Luit
Development models R. Kuiper and E.J. Luit 1 Introduction We reconsider the classical development models: the Waterfall Model [Bo76], the V-Model [Ro86], the Spiral Model [Bo88], together with the further
More informationRequirement Engineering
Requirement Engineering Carsten Schmoll & Horst Rechner Fraunhofer FOKUS - FOKUSforum - Best Practices May 6., 2008 Requirement A requirement is " a singular documented need of what a particular product
More informationBest-Practice Software Engineering: Software Processes to Support Project Success. Dietmar Winkler
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
More informationRequirements Engineering Process Models in Practice
AWRE 2002 141 Engineering Process Models in Practice Sacha Martin 1, Aybüke Aurum 1, Ross Jeffery 2, Barbara Paech 3 1 School of Information Systems, Technology and Management, University of New South
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationAgile Software Engineering, a proposed extension for in-house software development
Journal of Information & Communication Technology Vol. 5, No. 2, (Fall 2011) 61-73 Agile Software Engineering, a proposed extension for in-house software development Muhammad Misbahuddin * Institute of
More informationBEYOND LEARNING PLATFORMS: INFRASTRUCTURES FOR THE DIGITAL CAMPUS
BEYOND LEARNING PLATFORMS: INFRASTRUCTURES FOR THE DIGITAL CAMPUS Michael Kerres University of Duisburg-Essen, Duisburg Learning Lab, Germany Fellow, Swiss Center for Innovations in Learning, University
More informationA Pattern-Based Method for Identifying and Analyzing Laws
A Pattern-Based Method for Identifying and Analyzing Laws Kristian Beckers, Stephan Faßbender, Jan-Christoph Küster, and Holger Schmidt paluno - The Ruhr Institute for Software Technology University of
More informationInternationalization Processes for Open Educational Resources
Internationalization Processes for Open Educational Resources Henri Pirkkalainen 1, Stefan Thalmann 2, Jan Pawlowski 1, Markus Bick 3, Philipp Holtkamp 1, Kyung-Hun Ha 3 1 University of Jyväskylä, Global
More informationPlease quote as: Berkovich, M.; Esch, S.; Leimeister, J. M.; Krcmar, H. (2009): Requirements Engineering for Hybrid Products as Bundles of Hardware,
Please quote as: Berkovich, M.; Esch, S.; Leimeister, J. M.; Krcmar, H. (2009): Requirements Engineering for Hybrid Products as Bundles of Hardware, Software and Service Elements a Literature Review. In:
More informationPlease quote as: Berkovich, M.; Leimeister, J. M. & Krcmar, H. (2009): An empirical exploration of requirements engineering for hybrid products.
Please quote as: Berkovich, M.; Leimeister, J. M. & Krcmar, H. (2009): An empirical exploration of requirements engineering for hybrid products. In: 27. European Conference on Information Systems (ECIS)
More information1 Business Modeling. 1.1 Event-driven Process Chain (EPC) Seite 2
Business Process Modeling with EPC and UML Transformation or Integration? Dr. Markus Nüttgens, Dipl.-Inform. Thomas Feld, Dipl.-Kfm. Volker Zimmermann Institut für Wirtschaftsinformatik (IWi), Universität
More informationHuman Aspects of Software Engineering: The Case of Extreme Programming
1 Human Aspects of Software Engineering: The Case of Extreme Programming Orit Hazzan 1 and Jim Tomayko 2 1 Department of Education in Technology and Science, Technion - IIT, Haifa 32000, Israel oritha@tx.technion.ac.il
More informationA CONCEPTUAL MODEL FOR REQUIREMENTS ENGINEERING AND MANAGEMENT FOR CHANGE-INTENSIVE SOFTWARE
A CONCEPTUAL MODEL FOR REQUIREMENTS ENGINEERING AND MANAGEMENT FOR CHANGE-INTENSIVE SOFTWARE Jewgenij Botaschanjan, Andreas Fleischmann, Markus Pister Technische Universität München, Institut für Informatik
More informationSoftware Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering
Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Overview Phases during Software Development
More informationNew Business Models for the Software Industry: The Emergence of Cloud Computing and Software Ecosystems
New Business Models for the Software Industry: The Emergence of Cloud Computing and Software Ecosystems Prof. Dr. Peter Buxmann Technische Universität Darmstadt Wirtschaftsinformatik Software Business
More informationDeveloping Collaborative Environments A Holistic Software Development Methodology Marge Petersen and John Mitchiner Sandia National Laboratories
Developing Collaborative Environments A Holistic Software Development Methodology Marge Petersen and John Mitchiner Sandia National Laboratories mbpeter@sandia.gov jlmitch@sandia.gov Abstract Sandia National
More informationRapid software development. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1
Rapid software development Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 Objectives To explain how an iterative, incremental development process leads to faster delivery of
More informationEvaluating Tools that Support Pair Programming in a Distributed Engineering Environment
Evaluating Tools that Support Pair Programming in a Distributed Engineering Environment Dietmar Winkler Stefan Biffl Andreas Kaltenbach Institute of Software Technology and Interactive Systems, Vienna
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationInfluence of Business Process on the ERP Project Effectiveness
Influence of Business Process on the ERP Project Effectiveness Jun-Der Leu*, Wen-Hsien Tsai*, Ping-Yu Hsu*, Julian Cheng*, Yi-Wen Fan** *Institute of Business Administration, National Central University
More informationImproving Traceability of Requirements Through Qualitative Data Analysis
Improving Traceability of Requirements Through Qualitative Data Analysis Andreas Kaufmann, Dirk Riehle Open Source Research Group, Computer Science Department Friedrich-Alexander University Erlangen Nürnberg
More informationIT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3
Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document
More information55. IWK Internationales Wissenschaftliches Kolloquium International Scientific Colloquium
PROCEEDINGS 55. IWK Internationales Wissenschaftliches Kolloquium International Scientific Colloquium 13-17 September 2010 Crossing Borders within the ABC Automation, Biomedical Engineering and Computer
More informationTowards an Integration of Business Process Modeling and Object-Oriented Software Development
Towards an Integration of Business Process Modeling and Object-Oriented Software Development Peter Loos, Peter Fettke Chemnitz Univeristy of Technology, Chemnitz, Germany {loos peter.fettke}@isym.tu-chemnitz.de
More informationTRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
More informationChapter 4 Software Lifecycle and Performance Analysis
Chapter 4 Software Lifecycle and Performance Analysis This chapter is aimed at illustrating performance modeling and analysis issues within the software lifecycle. After having introduced software and
More informationSoftware Engineering and Scientific Computing
Software Engineering and Scientific Computing Barbara Paech, Hanna Valtokari Institute of Computer Science Im Neuenheimer Feld 326 69120 Heidelberg, Germany http://se.ifi.uni-heidelberg.de paech@informatik.uni-heidelberg.de
More informationSyllabus. REQB Certified Professional for Requirements Engineering. Advanced Level Requirements Manager
Syllabus REQB Certified Professional for Requirements Engineering Requirements Manager Version 1.0 2011 The copyright to this edition of the syllabus in all languages is held by the Global Association
More informationWeb Application Development Process
Web Engineering Web Application Development Process Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements
More informationThis is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 15447
Open Archive TOULOUSE Archive Ouverte (OATAO) OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited
More informationExperience Report: Appropriateness of the BCI-Method for Identifying Business Components in large-scale Information Systems
Experience Report: Appropriateness of the BCI-Method for Identifying Business Components in large-scale Information Systems Bernhard Selk 1, Sebastian Kloeckner 1, Bettina Bazijanec 1, Antonia Albani 2
More informationAgile Software Engineering Practice to Improve Project Success
Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems dietmar.winkler@qse.ifs.tuwien.ac.at
More informationMarkus Dick, Stefan Naumann {m.dick, s.naumann}(at)umwelt-campus.de
Markus Dick, Stefan Naumann {m.dick, s.naumann}(at)umwelt-campus.de Trier University of Applied Sciences, Umwelt-Campus Birkenfeld Campusallee, D-55768 Hoppstädten-Weiersbach, Germany http://www.green-software-engineering.de/
More informationAPPLICATION OF A SALES-TOOL FOR AN OPTIMIZED TENDER PREPARATION IN SMALL AND MEDIUM-SIZED COMPANIES
URN (Paper): urn:nbn:de:gbv:ilm1-2011iwk-014:9 56 TH INTERNATIONAL SCIENTIFIC COLLOQUIUM Ilmenau University of Technology, 12 16 September 2011 URN: urn:nbn:gbv:ilm1-2011iwk:5 APPLICATION OF A SALES-TOOL
More informationHistory of Agile Methods
Agile Development Methods: Philosophy and Practice CPSC 315 Programming Studio Fall 2010 History of Agile Methods Particularly in 1990s, some developers reacted against traditional heavyweight software
More informationPlease quote as: Berkovich, M.; Leimeister, J. M.; Hoffmann, A. & Krcmar, H. (2012): A requirements data model for product service systems.
Please quote as: Berkovich, M.; Leimeister, J. M.; Hoffmann, A. & Krcmar, H. (2012): A data model for product service systems. In: Engineering, Ausgabe/Number: 2, Vol. 19, Erscheinungsjahr/Year: 2012.
More informationUsing Simulation to teach project management skills. Dr. Alain April, ÉTS Montréal alain.april@etsmtl.ca
Using Simulation to teach project management skills Dr. Alain April, ÉTS Montréal alain.april@etsmtl.ca Agenda of the workshop 1 The software project management theory overview (40 minutes) 2 Why use SDLC
More informationSoftware Quality and Assurance in Waterfall model and XP - A Comparative Study
Software Quality and Assurance in Waterfall model and XP - A Comparative Study Dr. Sana a Jawdat Khalaf Sana_j_11@hotmail.com Dr. Mohamed Noor Al-Jedaiah m_aljedaiah@ammanu.edu.jo Abstract: -Dealing with
More informationCloud Computing Business Case Study - A Practical Analysis
Lohnt sich Computing? Überreicht durch die WiB Solutions AG Identity Management Business Process Management Qualitäts Management WiB BRINGT THEMEN AUF DEN PUNKT. W W W. W I B. CH WiB Solutions AG, Aarburgerstrasse
More informationStakeholders, Goals, Scope: The Foundation for Requirements and Business Models
Stakeholders, Goals, Scope: The Foundation for Requirements and Business Models Suzanne Robertson The Atlantic Systems Guild Ltd Suzanne Robertson is a principal and founder of The Atlantic Systems Guild.
More informationDevelopment Methodologies
Slide 3.1 Development Methodologies Prof. Dr. Josef M. Joller jjoller@hsr.ch Development Methodologies Prof. Dr. Josef M. Joller 1 Session 3 Slide 3.2 SOFTWARE LIFE-CYCLE MODELS Development Methodologies
More informationWhat is a life cycle model?
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
More informationDeveloping Web-based Applications through e-prototyping
Developing Web-based Applications through e-prototyping Wolf-Gideon Bleek, Martti Jeenicke, Ralf Klischewski Hamburg University, Department for Informatics, Software Engineering Group Vogt-Koelln-Str.
More informationA Software Engineering Model for Mobile App Development
APPENDIX C A Software Engineering Model for Mobile App Development As we mentioned early in the book (see Chapter 1), to successfully develop a mobile software solution you should follow an engineering
More informationPrinciples of IT Governance
Principles of IT Governance Governance of enterprise IT focuses on delivering services to support top line growth while moving operational savings to the bottom line. The management of IT services has
More informationA Business Model Approach for Service Engineering in the Internet of Services
A Business Model Approach for Service Engineering in the Internet of Services Holger Kett Competence Center Electronic Business Fraunhofer-Institut für Arbeitswirtschaft und Organisation IAO Nobelstr.
More informationAgile Planet. A Travel Guide to the Agile Universe Fabian Schiller. This book is for sale at http://leanpub.com/agileplanet
Agile Planet A Travel Guide to the Agile Universe Fabian Schiller This book is for sale at http://leanpub.com/agileplanet This version was published on 2014-11-02 This is a Leanpub book. Leanpub empowers
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Management and to describe the practice overview, requirements, best practices, activities, and key
More informationRedesigned Framework and Approach for IT Project Management
Vol. 5 No. 3, July, 2011 Redesigned Framework and Approach for IT Project Management Champa Hewagamage 1, K. P. Hewagamage 2 1 Department of Information Technology, Faculty of Management Studies and Commerce,
More informationSoftware Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Not this life cycle SE, Software Lifecycle, Hans van Vliet, 2008 2 Introduction software development
More informationHamid Faridani (h.faridani@rogers.com) March 2011
Hamid Faridani (h.faridani@rogers.com) March 2011 Introduction Methodologies like Waterfall, RUP and Agile have all become key tools for software developers and project manager s to aid them in delivering
More informationObject-Oriented Systems Analysis and Design
Object-Oriented Systems Analysis and Design Noushin Ashrafi Professor of Information System University of Massachusetts-Boston Hessam Ashrafi Software Architect Pearson Education International CONTENTS
More informationExtreme Programming and Rational Unified Process Contrasts or Synonyms?
Extreme Programming and Rational Unified Process Contrasts or Synonyms? Per Runeson and Peter Greberg Lund University, Sweden per.runeson@telecom.lth.se Abstract The agile movement has received much attention
More informationApplying Lean on Agile Scrum Development Methodology
ISSN:2320-0790 Applying Lean on Agile Scrum Development Methodology SurendRaj Dharmapal, Dr. K. Thirunadana Sikamani Department of Computer Science, St. Peter University St. Peter s College of Engineering
More informationPersona driven agile development
Persona driven agile development Build up a vision with personas, sketches and persona driven user stories Dominique Winter GreenPocket GmbH Cologne, Germany dominique.winter@greenpocket.de Eva-Maria Holt
More informationLeading 20,000+ employees by a process-oriented management system
Leading 20,000+ employees by a process-oriented management system Insights to process management at Lufthansa Technik Group Mirko Kloppenburg 1, Janina Kettenbohrer 2, Daniel Beimborn 3, and Michael Bögle
More informationRequirements Management Practice Description
Requirements Management Practice Description 1. REQUIREMENTS MANAGEMENT (RM) 1.1 Description of the practice TRASYS provide solutions to effectively manage critical issues and reduce risks in project related
More informationChallenges to an Integrated Cost Management during Early Phases of Product Development
Challenges to an Integrated Cost Management during Early Phases of Product Development Dr.-Ing. Markus Mörtl Lehrstuhl für Produktentwicklung / Institute of Product Development Technische Universität München
More informationInternational Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research)
International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research) International Journal of Engineering, Business and Enterprise
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 15 Agile Methodologies: AUP 1 Agile Unified Process (AUP) Proposed by Ambler as a simplified version of the Rational Unified Process (RUP).
More informationProcess-Family-Points
Process-Family-Points Sebastian Kiebusch 1, Bogdan Franczyk 1, and Andreas Speck 2 1 University of Leipzig, Faculty of Economics and Management, Information Systems Institute, Germany kiebusch@wifa.uni-leipzig.de,
More informationComputing & Communications Services
2010 Computing & Communications Services 2010 / 10 / 04 Final Kent Percival, M.Sc., P.Eng. Defining the Value of the Business Analyst In achieving its vision, key CCS partnerships involve working directly
More informationThe use of Trade-offs in the development of Web Applications
The use of Trade-offs in the development of Web Applications Sven Ziemer and Tor Stålhane Department of Computer and Information Science Norwegian University of Technology and Science {svenz, stalhane}@idi.ntnu.no
More informationSoftware Development Process
Software Development Process 台 北 科 技 大 學 資 訊 工 程 系 鄭 有 進 教 授 2005 copyright Y C Cheng Software development process Software development process addresses requirements, expectations and realities simultaneously
More informationService Engineering, Business Process Management and Design
7 th INTERNATIONAL MULTIDISCIPLINARY CONFERENCE Baia Mare, Romania, May 17-18, 2007 ISSN-1224-3264 BUSINESS PROCESS MANAGEMENT SOFTWARE IN THE FIELD OF SERVICE ENGINEERING Helmut, Aschbacher DI (FH), university
More informationSoftware Construction
Software Construction Staff Faculty: Univ.-Prof. Dr. rer. nat. Horst Lichter lichter@informatik.rwth-aachen.de Secretary: Bärbel Kronewetter Phone: +49 241 80 21 330 Fax: +49 241 80 22 352 Research Assistants:
More information