Optimizing software and methods for resource management
(2024) In CODEN:LUTEDX/TEIE EIEL05 20241Industrial Electrical Engineering and Automation
- Abstract
- In 2014 during an organisational restructuring of Sony Electronics in Lund, an
ongoing inhouse project to develop a resource management software was
rushed to completion. The software had at the time been in active development
by a team of software engineers for over a year but was quickly brought to
completion to meet the new directives. Without clear product ownership and
review, the software and its usage gradually stagnated and resulted in a shroud
of uncertainty surrounding the workflow.
Ten years later with only minor changes to the code base and workflow,
questions are being raised by the project management office about the efficacy
of the current solution. This thesis is a case study in the consequences of
... (More) - In 2014 during an organisational restructuring of Sony Electronics in Lund, an
ongoing inhouse project to develop a resource management software was
rushed to completion. The software had at the time been in active development
by a team of software engineers for over a year but was quickly brought to
completion to meet the new directives. Without clear product ownership and
review, the software and its usage gradually stagnated and resulted in a shroud
of uncertainty surrounding the workflow.
Ten years later with only minor changes to the code base and workflow,
questions are being raised by the project management office about the efficacy
of the current solution. This thesis is a case study in the consequences of
legacy software and how inefficacies form from accommodating shortcomings
of internal software tools.
The workflow was investigated and information surrounding the resource
management software at Sony in Lund was compiled and analysed. With
stakeholder interviews and literature studies several ways forward are
ultimately put forward. In order of increasing potential cost and risk they were
concluded to be:
1. Maintaining the current software
2. Middleware-based solution preserving as much of the current software
implementation as possible.
3. Clean slate project for future maintainability and adaptability to change.
Due to complexity and cost, commercial enterprise resource planning
solutions were deemed not viable for Sony Electronics in Lund and therefore
not presented as a possible solution. (Less)
Please use this url to cite or link to this publication:
http://lup.lub.lu.se/student-papers/record/9169756
- author
- Björklund, Alex LU
- supervisor
- organization
- course
- EIEL05 20241
- year
- 2024
- type
- M2 - Bachelor Degree
- subject
- keywords
- Optimization, legacy code, stakeholder demands, project management, cost estimation, database interfacing
- publication/series
- CODEN:LUTEDX/TEIE
- report number
- 3133
- language
- English
- id
- 9169756
- date added to LUP
- 2024-10-02 15:48:44
- date last changed
- 2024-10-02 15:48:44
@misc{9169756, abstract = {{In 2014 during an organisational restructuring of Sony Electronics in Lund, an ongoing inhouse project to develop a resource management software was rushed to completion. The software had at the time been in active development by a team of software engineers for over a year but was quickly brought to completion to meet the new directives. Without clear product ownership and review, the software and its usage gradually stagnated and resulted in a shroud of uncertainty surrounding the workflow. Ten years later with only minor changes to the code base and workflow, questions are being raised by the project management office about the efficacy of the current solution. This thesis is a case study in the consequences of legacy software and how inefficacies form from accommodating shortcomings of internal software tools. The workflow was investigated and information surrounding the resource management software at Sony in Lund was compiled and analysed. With stakeholder interviews and literature studies several ways forward are ultimately put forward. In order of increasing potential cost and risk they were concluded to be: 1. Maintaining the current software 2. Middleware-based solution preserving as much of the current software implementation as possible. 3. Clean slate project for future maintainability and adaptability to change. Due to complexity and cost, commercial enterprise resource planning solutions were deemed not viable for Sony Electronics in Lund and therefore not presented as a possible solution.}}, author = {{Björklund, Alex}}, language = {{eng}}, note = {{Student Paper}}, series = {{CODEN:LUTEDX/TEIE}}, title = {{Optimizing software and methods for resource management}}, year = {{2024}}, }