schliessen

Filtern

 

Bibliotheken

Integration of performance management into the application lifecycle / Eduard Tudenhöfner

Inhaltsangabe:Introduction: Despite the widespread recognition that performance is important to the success of a project, many software products fail to respond fast enough to user requests or to handle a certain amount of parallel business transactions. This is because nowadays projects are result-... Ausführliche Beschreibung

PPN (Katalog-ID): 772716021
Personen: Tudenhöfner, Eduard [VerfasserIn]
Medienart: E-Book E-Book
Sprache: Englisch
Erschienen: Hamburg, Diplomica, 2011
Hochschule: Zugl.: Stuttgart, Hochsch. für Technik, Master-Thesis, 2011
Basisklassifikation: 54.52 Software engineering
85.03 Methoden und Techniken der Betriebswirtschaft
Schlagwörter:

Performance Management

Softwarelebenszyklus

Hochschulschrift

Online-Publikation

Formangabe: Hochschulschrift
Anmerkungen: Lizenzpflichtig
Umfang: Online-Ressource (PDF, 5818 KB, 125 S.), graph. Darst.
ISBN: 3-8428-2047-X
978-3-8428-2047-0

Ähnliche Einträge

Vorhandene Hefte/Bände

mehr (+)

Informationen zur Verfügbarkeit werden geladen

Internes Format
LEADER 18916nmm a2200613 c 4500
001 772716021
003 DE-601
005 20180324173442.0
007 cr uuu---uuuuu
008 131128s2011 gw o 000 0 eng d
015 |a 16O12  |2 dnb 
016 7 |a 111770565X  |2 DE-101 
020 |a 384282047X  |9 3-8428-2047-X 
020 |a 9783842820470  |9 978-3-8428-2047-0 
024 7 |a urn:nbn:de:101:1-2016110212519  |2 urn 
035 |a (DE-101)111770565X 
035 |a (DE-599)GBV772716021 
040 |b ger  |c GBVCP  |e rda 
041 0 |a eng 
082 0 0 |a 650 
082 0 9 |a 650 
084 |a 54.52  |9 Software engineering  |2 bkl 
084 |a 85.03  |9 Methoden und Techniken der Betriebswirtschaft  |2 bkl 
100 1 |a Tudenhöfner, Eduard  |e verfasserin  |4 aut  |0 (DE-601)705431800  |0 (DE-588)1015752195 
245 1 0 |a Integration of performance management into the application lifecycle  |h Elektronische Ressource  |c Eduard Tudenhöfner 
264 3 1 |a Hamburg  |b Diplomica  |c 2011 
300 |a Online-Ressource (PDF, 5818 KB, 125 S.)  |b graph. Darst. 
336 |a Text  |b txt  |2 rdacontent 
337 |a Computermedien  |b c  |2 rdamedia 
338 |a Online-Ressource  |b cr  |2 rdacarrier 
500 |a Lizenzpflichtig 
502 |a Zugl.: Stuttgart, Hochsch. für Technik, Master-Thesis, 2011 
520 |a Inhaltsangabe:Introduction: Despite the widespread recognition that performance is important to the success of a project, many software products fail to respond fast enough to user requests or to handle a certain amount of parallel business transactions. This is because nowadays projects are result-oriented where the focus is on functionality to be implemented. Such projects do not pay high attention to application performance because it still does not have the particular importance that unit testing for example has. Moreover today’s development models usually consider performance management only in a limited way within their lifecycle and often follow what is known as the fix it later approach. The fix it later approach concentrates on software correctness and defers performance considerations to the integration testing phase where additional hardware is added or a system is tuned when performance issues are detected. The problem of neglecting performance management is that performance issues often do not emerge until an application is put into production, where it is likely to suffer the consequences of a performance failure. The consequences of performance failures can be increased operational costs, increased development and hardware costs, and damaged customer relations. If severe performance issues are discovered during production, it may be too expensive to re-design a system or even impossible to add additional hardware in order to meet performance objectives. Such projects are likely to be canceled and their costs will be unrecoverable. To avoid such situations, performance management should be integrated into an application’s lifecycle from the beginning. This means that performance objectives have to be defined early within a project and continually verified as an application evolves. Having performance management integrated from the beginning allows to reduce overall project risk and costs because performance issues can be spotted and corrected early in the lifecycle and even before end users are affected. Furthermore an application is extensively tested for its ability of reaching performance objectives before it is deployed to a production environment and exposed to real users. NovaTec GmbH is a company providing IT-services in the area of consulting, project management, software engineering, application architectures, provisioning, performance management, and process engineering. The competences of NovaTec are logically grouped in so-called competence areas. This thesis is written in the competence area Application Performance Management, where the purpose is to support customers in performance engineering and analysis tasks in order to detect performance bottlenecks and stability issues. Additionally, this competence area helps customers in introducing performance management to their projects. Introducing performance management to customers is currently solely based on the experience of NovaTec experts. This experience is only partially documented and difficult to reuse. The problem is that no model is used for guiding the introduction of performance management to different types of projects. For that reason a well-documented performance management model is required that includes the experience of experts and is generally applicable to different development models. As there is currently no model available for guiding performance management, the objectives of this thesis are as follows: 1) Evaluation of Existing Approaches Existing approaches towards performance management have to be analyzed and evaluated in how far they are suitable for nowadays project circumstances. 2) Performance Activities and their Responsibilities It must be analyzed which performance activities are to be considered in an application’s lifecycle and by whom they have to be performed. Furthermore it has to be evaluated which performance artefacts are necessary and how they are related to particular performance activities. 3) Analysis of Development Models As nowadays development models are not considering performance management, two development models have to be analyzed in order to determine how far they already support performance considerations and how they can be enhanced for performance management. 4) Creation A performance management approach should be generally applicable for different development models, thus if the outcome of the analysis tasks indicate that an available approach is suitable for nowadays projects, it should be selected and adapted to the needs of NovaTec. Otherwise, an own approach that concludes the analysis results has to be created and documented. 5) Application Example As a final step, the performance management approach should be combined with one development model in order to show an example of how the approach can be used. The outcome of this master thesis serves as a starting point for a documented performance management approach that is used by NovaTec experts for introducing performance management to customer projects. This thesis is based on research that was done in the area of Software Performance Engineering (SPE), which is often used in the literature interchangeably with the term Application Performance Management (APM). Based on the literature, both disciplines encompass management and engineering activities, roles, and practices that are performed throughout an application’s lifecycle. Nevertheless, the competence area Application Performance Management differentiates between performance engineering and performance management. Performance engineering is about the technical aspect when executing performance activities, whereas performance management covers performance engineering activities and additionally comprises management activities. Due to the fact that most of the analyzed literature did not make any difference between SPE and APM, the second and third chapter will use both terms interchangeably in order to not falsify an author’s thoughts. Afterwards the terms APM and performance management will be used consequently until the end of the thesis. Chapter 2 describes Software Performance Engineering in general and shows how performance can be quantified. The problems of performance engineering are demonstrated and the differences between reactive and proactive performance management are explained. Chapter 3 analyzes a process towards performance engineering and evaluates which performance activities can be used in nowadays projects. Additionally, performance roles and artefacts are depicted and discussed in-depth. Moreover two different development models are analyzed for their suitability of performance integration. Chapter 4 depicts the selected solution approach and describes its structure and performance activities. Furthermore defined performance roles and artefacts with their interdependencies are specified. Chapter 5 applies the selected approach and integrates it into a development model in two different ways. The first way handles a best-case scenario, where performance management is integrated from the beginning of a project. The second way deals with an integration after performance issues were found. Chapter 6 reviews the results of this thesis and describes learned lessons. Additionally, an outlook for future work is provided.Inhaltsverzeichnis:Table of Contents: 1.Introduction1 1.1Motivation1 1.2Current Situation2 1.3Objectives2 1.4Definition of Terms3 1.5Outline3 2.Software Performance Engineering5 2.1Overview5 2.2Quantifying Performance6 2.2.1Interrelationships of Performance Characteristics7 2.2.2The Cost to Fix a Performance Problem9 2.3Problems of Performance Engineering9 2.4Reactive vs. Proactive Performance Management11 2.5Conclusion12 3.Analysis13 3.1Software Performance Engineering Process13 3.1.1Performance Activities14 3.1.2Summary22 3.2Performance Activities24 3.2.1Planning of Performance Management24 3.2.2Acquiring Performance Tools24 3.2.3Performance Education and Trainings25 3.2.4Identification of Performance Risks and Definition of Performance Objectives25 3.2.5Architecture Assessment.26 3.2.6Performance Testing27 3.2.7Performance Tuning31 3.2.8Capacity Mana... 
520 |a Despite the widespread recognition that performance is important to the success of a project, many software products fail to respond fast enough to user requests or to handle a certain amount of parallel business transactions. This is because nowadays projects are result-oriented where the focus is on functionality to be implemented. Such projects do not pay high attention to application performance because it still does not have the particular importance that unit testing for example has. Moreover today’s development models usually consider performance management only in a limited way within their lifecycle and often follow what is known as the fix it later approach. The fix it later approach concentrates on software correctness and defers performance considerations to the integration testing phase where additional hardware is added or a system is tuned when performance issues are detected. The problem of neglecting performance management is that performance issues often do not emerge until an application is put into production, where it is likely to suffer the consequences of a performance failure. The consequences of performance failures can be increased operational costs, increased development and hardware costs, and damaged customer relations. If severe performance issues are discovered during production, it may be too expensive to re-design a system or even impossible to add additional hardware in order to meet performance objectives. Such projects are likely to be canceled and their costs will be unrecoverable. To avoid such situations, performance management should be integrated into an application’s lifecycle from the beginning. This means that performance objectives have to be defined early within a project and continually verified as an application evolves. Having performance management integrated from the beginning allows to reduce overall project risk and costs because performance issues can be spotted and corrected early in the lifecycle and even before end users are affected. Furthermore an application is extensively tested for its ability of reaching performance objectives before it is deployed to a production environment and exposed to real users. NovaTec GmbH is a company providing IT-services in the area of consulting, project management, software engineering, application architectures, provisioning, performance management, and process engineering. The competences of NovaTec are logically grouped in so-called competence areas. This thesis is written in the competence area Application Performance Management, where the purpose is to support customers in performance engineering and analysis tasks in order to detect performance bottlenecks and stability issues. Additionally, this competence area helps customers in introducing performance management to their projects. Introducing performance management to customers is currently solely based on the experience of NovaTec experts. This experience is only partially documented and difficult to reuse. The problem is that no model is used for guiding the introduction of performance management to different types of projects. For that reason a well-documented performance management model is required that includes the experience of experts and is generally applicable to different development models. As there is currently no model available for guiding performance management, the objectives of this thesis are as follows: 1) Evaluation of Existing Approaches Existing approaches towards performance management have to be analyzed and evaluated in how far they are suitable for nowadays project circumstances. 2) Performance Activities and their Responsibilities It must be analyzed which performance activities are to be considered in an application’s lifecycle and by whom they have to be performed. Furthermore it has to be evaluated which performance artefacts are necessary and how they are related to particular performance activities. 3) Analysis of Development Models As nowadays development models are not considering performance management, two development models have to be analyzed in order to determine how far they already support performance considerations and how they can be enhanced for performance management. 4) Creation A performance management approach should be generally applicable for different development models, thus if the outcome of the analysis tasks indicate that an available approach is suitable for nowadays projects, it should be selected and adapted to the needs of NovaTec. Otherwise, an own approach that concludes the analysis results has to be created and documented. 5) Application Example As a final step, the performance management approach should be combined with one development model in order to show an example of how the approach can be used. The outcome of this master thesis serves as a starting point for a documented performance management approach that is used by NovaTec experts for introducing performance management to customer projects. This thesis is based on research that was done in the area of Software Performance Engineering (SPE), which is often used in the literature interchangeably with the term Application Performance Management (APM). Based on the literature, both disciplines encompass management and engineering activities, roles, and practices that are performed throughout an application’s lifecycle. Nevertheless, the competence area Application Performance Management differentiates between performance engineering and performance management. Performance engineering is about the technical aspect when executing performance activities, whereas performance management covers performance engineering activities and additionally comprises management activities. Due to the fact that most of the analyzed literature did not make any difference between SPE and APM, the second and third chapter will use both terms interchangeably in order to not falsify an author’s thoughts. Afterwards the terms APM and performance management will be used consequently until the end of the thesis. Chapter 2 describes Software Performance Engineering in general and shows how performance can be quantified. The problems of performance engineering are demonstrated and the differences between reactive and proactive performance management are explained. Chapter 3 analyzes a process towards performance engineering and evaluates which performance activities can be used in nowadays projects. Additionally, performance roles and artefacts are depicted and discussed in-depth. Moreover two different development models are analyzed for their suitability of performance integration. Chapter 4 depicts the selected solution approach and describes its structure and performance activities. Furthermore defined performance roles and artefacts with their interdependencies are specified. Chapter 5 applies the selected approach and integrates it into a development model in two different ways. The first way handles a best-case scenario, where performance management is integrated from the beginning of a project. The second way deals with an integration after performance issues were found. Chapter 6 reviews the results of this thesis and describes learned lessons. Additionally, an outlook for future work is provided.Inhaltsverzeichnis:Table of Contents: 1.Introduction1 1.1Motivation1 1.2Current Situation2 1.3Objectives2 1.4Definition of Terms3 1.5Outline3 2.Software Performance Engineering5 2.1Overview5 2.2Quantifying Performance6 2.2.1Interrelationships of Performance Characteristics7 2.2.2The Cost to Fix a Performance Problem9 2.3Problems of Performance Engineering9 2.4Reactive vs. Proactive Performance Management11 2.5Conclusion12 3.Analysis13 3.1Software Performance Engineering Process13 3.1.1Performance Activities14 3.1.2Summary22 3.2Performance Activities24 3.2.1Planning of Performance Management24 3.2.2Acquiring Performance Tools24 3.2.3Performance Education and Trainings25 3.2.4Identification of Performance Risks and Definition of Performance Objectives25 3.2.5Architecture Assessment.26 3.2.6Performance Testing27 3.2.7Performance Tuning31 3.2.8Capacity Management33 3.2.9Application Mo... 
583 |a lzar:   |k Langzeitarchivierung gewährleistet 
650 7 |0 (DE-601)64276512X  |0 (DE-588)7730862-1  |a Performance Management  |2 gnd 
650 7 |0 (DE-601)350739315  |0 (DE-588)4691865-6  |a Softwarelebenszyklus  |2 gnd 
653 |a Hochschulschrift 
653 |a Online-Publikation 
655 0 7 |0 (DE-588)4113937-9  |a Hochschulschrift  |2 gnd-content 
856 4 0 |u http://www.diplomica-verlag.de/ 
856 4 0 |u http://epub.sub.uni-hamburg.de/epub/volltexte/campus/2015/39721/  |z ZZ 
856 4 1 |u http://nbn-resolving.de/urn:nbn:de:101:1-2016110212519  |3 Volltext 
856 4 1 |u http://d-nb.info/111770565X/34  |3 Volltext 
856 4 1 |u http://www.diplom.de/e-book/228622/integration-of-performance-management-into-the-application-lifecycle  |q application/pdf  |3 Volltext 
856 4 2 |y Inhaltsbeschreibung & Leseprobe  |u http://www.diplom.de/e-book/228622/integration-of-performance-management-into-the-application-lifecycle 
912 |a SYSFLAG_1 
912 |a GBV_GVK 
912 |a GBV_ILN_22 
912 |a GBV-ODiss 
951 |a BO 
980 |2 22  |1 01  |b 1535258187  |x 0018  |y zu  |z 16-04-15 
981 |2 22  |1 01  |y Volltextzugang Campus  |y ZZ  |r http://epub.sub.uni-hamburg.de/epub/volltexte/campus/2015/39721/ 
995 |2 22  |1 01  |a SUBolrdow