Performance management work: Difference between revisions

m DragonflySixtyseven moved page Performance Management Work to Performance management work
added two internal links to wikipedia articles
Line 1: Line 1:
'''Performance Management Work''' ('''PMW''') describes all activities that are necessary to ensure that [[IT performance management|performance]] requirements of application systems (AS) can be met. Therefore, PMW integrates software performance engineering (SPE)<ref name="WoodsideFranks2007"/> and application performance management (APM)<ref name="Menasce2002"/> activities. SPE and APM are part of different lifecycle phases of an AS namely [[system development]] and [[IT operations]]. PMW supports a comprehensive coordination of all SPE and APM activities, which is inevitable due to an increased complexity of AS [[Systems architecture|architectures]].<ref name="BrunnertVoegele2014">{{cite journal|last1=Brunnert|first1=Andreas|last2=Vögele|first2=Christian|last3=Danciu|first3=Alexandru|last4=Pfaff|first4=Matthias|last5=Mayer|first5=Manuel|last6=Krcmar|first6=Helmut|title=Performance Management Work|journal=Business & Information Systems Engineering|volume=6|issue=3|pages=177|year=2014|issn=1867-0202|doi=10.1007/s12599-014-0323-7}}</ref>
'''Performance Management Work''' ('''PMW''') describes all activities that are necessary to ensure that [[IT performance management|performance]] requirements of application systems (AS) can be met. Therefore, PMW integrates software performance engineering (SPE)<ref name="WoodsideFranks2007"/> and [[application performance management]] (APM)<ref name="Menasce2002"/> activities. SPE and APM are part of different lifecycle phases of an AS namely [[system development]] and [[IT operations]]. PMW supports a comprehensive coordination of all SPE and APM activities, which is inevitable due to an increased complexity of AS [[Systems architecture|architectures]].<ref name="BrunnertVoegele2014">{{cite journal|last1=Brunnert|first1=Andreas|last2=Vögele|first2=Christian|last3=Danciu|first3=Alexandru|last4=Pfaff|first4=Matthias|last5=Mayer|first5=Manuel|last6=Krcmar|first6=Helmut|title=Performance Management Work|journal=Business & Information Systems Engineering|volume=6|issue=3|pages=177|year=2014|issn=1867-0202|doi=10.1007/s12599-014-0323-7}}</ref>


The term Performance Management Work was first introduced by Brunnert et al. (2014) in ''Business & Information Systems Engineering''<ref name="BrunnertVoegele2014"/> as well as in the German ''WIRTSCHAFTSINFORMATIK'' <ref name="BrunnertVoegele20142">{{cite journal|last1=Brunnert|first1=Andreas|last2=Vögele|first2=Christian|last3=Danciu|first3=Alexandru|last4=Pfaff|first4=Matthias|last5=Mayer|first5=Manuel|last6=Krcmar|first6=Helmut|title=Performance Management Work|journal=Wirtschaftsinformatik|volume=56|issue=3|pages=197|year=2014|issn=0937-6429|doi=10.1007/s11576-014-0414-6}}</ref>
The term Performance Management Work was first introduced by Brunnert et al. (2014) in ''Business & Information Systems Engineering''<ref name="BrunnertVoegele2014"/> as well as in the German ''WIRTSCHAFTSINFORMATIK'' <ref name="BrunnertVoegele20142">{{cite journal|last1=Brunnert|first1=Andreas|last2=Vögele|first2=Christian|last3=Danciu|first3=Alexandru|last4=Pfaff|first4=Matthias|last5=Mayer|first5=Manuel|last6=Krcmar|first6=Helmut|title=Performance Management Work|journal=Wirtschaftsinformatik|volume=56|issue=3|pages=197|year=2014|issn=0937-6429|doi=10.1007/s11576-014-0414-6}}</ref>


== Context ==
== Context ==
The dependency on AS increases in many areas such as in critical infrastructures like traffic control or power supply. Therefore, AS have to meet growing functional and non-functional requirements. An essential non-functional quality factor is called ''performance'', which is described by the [[Performance metric|metrics]] response times, resource usage and throughput. Such metrics are used to define performance goals. In order to ensure performance of AS, these metrics have to be constantly measured and assessed.
The dependency on AS increases in many areas such as in critical infrastructures like traffic control or power supply. Therefore, AS have to meet growing functional and non-functional requirements. An essential non-functional quality factor is called ''performance'', which is described by the [[Software metric|metrics]] response times, resource usage and throughput. Such metrics are used to define performance goals. In order to ensure performance of AS, these metrics have to be constantly measured and assessed.


Guaranteeing appropriate performance is a major challenge since AS have evolved to complex [[system of systems]].<ref name="Jamshidi2009"/> Furthermore, different subsystems of AS undergo a continuous [[Systems development life cycle|life cycle]] and lie within the responsibility of different organizations. The resulting complexity requires new approaches for performance management of such system of systems architectures with a multilateral [[IT governance]]. Existing approaches such as SPE or APM focus on certain stages of a life cycle. However, a comprehensive approach is missing, which not only addresses the complexity of systems and organizations but also integrates their life cycles.
Guaranteeing appropriate performance is a major challenge since AS have evolved to complex [[system of systems]].<ref name="Jamshidi2009"/> Furthermore, different subsystems of AS undergo a continuous [[Systems development life cycle|life cycle]] and lie within the responsibility of different organizations. The resulting complexity requires new approaches for performance management of such system of systems architectures with a multilateral [[IT governance]]. Existing approaches such as SPE or APM focus on certain stages of a life cycle. However, a comprehensive approach is missing, which not only addresses the complexity of systems and organizations but also integrates their life cycles.