Haasteet ja muunneltavuus ohjelmistotuoteperheiden rakentamisessa: rautateiden sähköenergian selvitysjärjestelmä

According to European Union, all member countries shall have a settlement system in use by 2020. The settlement system shall receive energy consumption data from meters installed in trains, validate the data and allocate it for the right user. In this way, the energy consumption can be invoiced from the right user precisely. Erex is a such energy settlement system. The system needs to be adopted for each country to meet their different needs with regards to laws, systems and practices. This means that the system shall allow at least some flexibility. When new partners have entered the partnership and new instances have been created and modified for them with ad-hoc methods, the manageability of the systems has decreased. For this reason, a need to improve the management of the systems as whole has been raised. It would be easier, if the systems would have a shared core and systematically managed variability. This would mean creating a product family with systematically managed commonality and variability. The objective of this thesis was to study, what are the challenges of creating such product family, where all systems share the same principles but some degree of flexibility is allowed. To achieve these objectives, experts from partner countries and the administration and developers of the systems were interviewed. Thereafter, challenges related to product families and their variability were studied from the literature. Then, the challenges found in empirical and theoretical parts were compared. The objective was to see if the results of empirical study support the current literature. The comparison had three key results. Firstly, many of the current challenges are rather typical for software that is derived with ad-hoc methods. These challenges were found both in empirical and theoretical parts. Secondly, there were a group of challenges that were found only in the theoretical part and did not appear in the interviews but were considered as potential for this case. Thus, these challenges can be of great worth when the product family is developed. Lastly, there were challenges discovered only in the empirical part. These challenges are highly case and domain specific and were not investigated in the theoretical part due to their subjects. Experience from domain should be used to address these case specific challenges as they may not be found from any literature. There were only three challenges that could have been addressed in theoretical part by their subject. Compared to the whole amount of challenges found, these three challenges had only little role. Overall, this means that challenges found in the case are rather typical for product families. Thus, experience from the literature and industry can be used to solve these challenges

Variability in software architecture - State of the art

status: publishe