@phdthesis{Sen2013,
  author    = {Sen, Surath},
  title     = {Character Analysis and Numerical Computations of Standard M.I. Probability Distributions},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-78623},
  school      = {Universit{\"a}t W{\"u}rzburg},
  year      = {2013},
  abstract  = {Development and character analysis of software programs, which compute minimum information probability distributions.},
  subject      = {Newton-Verfahren},
  language  = {en}
}
@misc{Hochmuth2022,
  type      = {Master Thesis},
  author    = {Hochmuth, Christian Andreas},
  title     = {Innovative Software in Unternehmen: Strategie und Erfolgsfaktoren f{\"u}r Einf{\"u}hrungsprojekte},
  doi       = {10.25972/OPUS-28841},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-288411},
  school      = {Universit{\"a}t W{\"u}rzburg},
  year      = {2022},
  abstract  = {Innovative Software kann die Position eines Unternehmens im Wettbewerb sichern. Die Einf{\"u}hrung innovativer Software ist aber alles andere als einfach. Denn obgleich die technischen Aspekte offensichtlicher sind, dominieren organisationale Aspekte. Zu viele Softwareprojekte schlagen fehl, da die Einf{\"u}hrung nicht gelingt, trotz Erf{\"u}llung technischer Anforderungen. Vor diesem Hintergrund ist das Forschungsziel der Masterarbeit, Risiken und Erfolgsfaktoren f{\"u}r die Einf{\"u}hrung innovativer Software in Unternehmen zu finden, eine Strategie zu formulieren und dabei die Bedeutung von Schl{\"u}sselpersonen zu bestimmen.},
  subject      = {Innovationsmanagement},
  language  = {de}
}
@phdthesis{Hennermann2001,
  author    = {Hennermann, Frank},
  title     = {Betriebswirtschaftliche Wissenspakete als Informationstr{\"a}ger der Softwareadaption},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-3418},
  school      = {Universit{\"a}t W{\"u}rzburg},
  year      = {2001},
  abstract  = {Moderne betriebswirtschaftliche Softwarel{\"o}sungen speichern in den Systemeinstellungen und Tabelleneintr{\"a}gen eine sehr große Menge des unternehmensspezifischen Wissens {\"u}ber Gesch{\"a}ftsabl{\"a}ufe und Organisationsstrukturen. Der vermehrte Einsatz unterschiedlicher L{\"o}sungen zur Abbildung der internen Prozesse auf der einen und zur {\"O}ffnung der Gesch{\"a}ftst{\"a}tigkeiten im Bereich des Electronic Business (e-Business) auf der anderen Seite stellt neue Heraus-forderungen an die Methoden und Konzepte zur Einf{\"u}hrung bzw. Betreuung der eingesetzten Systeme. Im Rahmen der Arbeit wird untersucht, welche Schritte notwendig sind, um eine transparente Speicherung und Nutzung des vorhandenen Wissens sowie der gesammelten Informationen system- bzw. methoden{\"u}bergreifend sicherzustellen und wie die bestehenden Ans{\"a}tze aus dem Bereich der Softwareadaption in den Gesamtkontext integriert werden k{\"o}nnen. Kernpunkte sind die methodische Unterst{\"u}tzung einer zielgerichteten Navigation durch die Informationsflut und die Entwicklung eines geeigneten Instrumentariums, das in der Lage ist, heterogene Softwarelandschaften abzubilden und als Dokumentationsbasis f{\"u}r zuk{\"u}nftige Systemmodifikationen zu dienen.},
  subject      = {Softwareentwicklung},
  language  = {de}
}
@phdthesis{Dorin2022,
  author    = {Dorin, Michael},
  title     = {The Relationship Between Software Complicacy and Software Reliability},
  doi       = {10.25972/OPUS-28308},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-283085},
  school      = {Universit{\"a}t W{\"u}rzburg},
  year      = {2022},
  abstract  = {An enduring engineering problem is the creation of unreliable software leading to unreliable systems. One reason for this is source code is written in a complicated manner making it too hard for humans to review and understand. Complicated code leads to other issues beyond dependability, such as expanded development efforts and ongoing difficulties with maintenance, ultimately costing developers and users more money. There are many ideas regarding where blame lies in the reation of buggy and unreliable systems. One prevalent idea is the selected life cycle model is to blame. The oft-maligned "waterfall" life cycle model is a particularly popular recipient of blame. In response, many organizations changed their life cycle model in hopes of addressing these issues. Agile life cycle models have become very popular, and they promote communication between team members and end users. In theory, this communication leads to fewer misunderstandings and should lead to less complicated and more reliable code. Changing the life cycle model can indeed address communications ssues, which can resolve many problems with understanding requirements. However, most life cycle models do not specifically address coding practices or software architecture. Since lifecycle models do not address the structure of the code, they are often ineffective at addressing problems related to code complicacy. This dissertation answers several research questions concerning software complicacy, beginning with an investigation of traditional metrics and static analysis to evaluate their usefulness as measurement tools. This dissertation also establishes a new concept in applied linguistics by creating a measurement of software complicacy based on linguistic economy. Linguistic economy describes the efficiencies of speech, and this thesis shows the applicability of linguistic economy to software. Embedded in each topic is a discussion of the ramifications of overly complicated software, including the relationship of complicacy to software faults. Image recognition using machine learning is also investigated as a potential method of identifying problematic source code. The central part of the work focuses on analyzing the source code of hundreds of different projects from different areas. A static analysis was performed on the source code of each project, and traditional software metrics were calculated. Programs were also analyzed using techniques developed by linguists to measure expression and statement complicacy and identifier complicacy. Professional software engineers were also directly surveyed to understand mainstream perspectives. This work shows it is possible to use traditional metrics as indicators of potential project bugginess. This work also discovered it is possible to use image recognition to identify problematic pieces of source code. Finally, this work discovered it is possible to use linguistic methods to determine which statements and expressions are least desirable and more complicated for programmers. This work's principle conclusion is that there are multiple ways to discover traits indicating a project or a piece of source code has characteristics of being buggy. Traditional metrics and static analysis can be used to gain some understanding of software complicacy and bugginess potential. Linguistic economy demonstrates a new tool for measuring software complicacy, and machine learning can predict where bugs may lie in source code. The significant implication of this work is developers can recognize when a project is becoming buggy and take practical steps to avoid creating buggy projects.},
  subject      = {Softwareentwicklung},
  language  = {en}
}