Software architecture development
Heinonen, Joonas (2023)
2023
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2023090525347
https://urn.fi/URN:NBN:fi:amk-2023090525347
Tiivistelmä
The objective of this thesis was to make a design for automation system architecture. The architecture is for a tool unit which is being used in the semiconductor industry. Task of the system in development is to collect data from all parts of the tool and to push them into a database. In the system design the database can be accessed by authorized personnel through a central user interface by the end users.
The design was started with investigation of what is wanted information from the system. This was done with interviews on personnel that would be using the feature in design. Conversation was also done with the product lead of the tool and the contractor which provides the central user interface program.
The development of the architecture and the database relies on literature about respective topics. Architecture designing requires the architect to make selection between wanted and unwanted features, and to be able to justify the selections made. Architecture is also more than just technical solutions. It includes values and attributes for the system which are not selectable choices like characteristics and principles for development.
Database designing on the other hand requires the designer to understand the problem thoroughly. Once the problem is understood then only is the designer able to understand what information and in which kind of format is required out of the database.
To understand underlying issues in any automation system tool which is part of industrial scale production is the key to be a successful provider. Making the product more efficient with less variations in end product quality is the only way of being acknowledged and a wanted company to buy solutions from.
The design was started with investigation of what is wanted information from the system. This was done with interviews on personnel that would be using the feature in design. Conversation was also done with the product lead of the tool and the contractor which provides the central user interface program.
The development of the architecture and the database relies on literature about respective topics. Architecture designing requires the architect to make selection between wanted and unwanted features, and to be able to justify the selections made. Architecture is also more than just technical solutions. It includes values and attributes for the system which are not selectable choices like characteristics and principles for development.
Database designing on the other hand requires the designer to understand the problem thoroughly. Once the problem is understood then only is the designer able to understand what information and in which kind of format is required out of the database.
To understand underlying issues in any automation system tool which is part of industrial scale production is the key to be a successful provider. Making the product more efficient with less variations in end product quality is the only way of being acknowledged and a wanted company to buy solutions from.