Development of Power System Analysis Software Using Object Components
Khalil Md Nor, Hazlie Mokhlis, Hadi Suyono, Mamdouh Abdel‐Akher, Awais Rashid, T.A. Gani
Abstract
Khalil Md Nor, Hazlie Mokhlis, Hadi Suyono, Mamdouh Abdel‐Akher, Awais Rashid, T.A. Gani
Abstract
This paper presents experiences of developing a power system analysis software using a combination of Object Oriented Programming (OOP) and Component Based Development (CBD) methodologies. In this development, various power system analyses are developed into software components. These components are integrated with graphical user interface components to build up a power system analysis application. By using both OOP and CBD methodologies, updating or adding new algorithm can be done to any specific component without affecting other components inside the software. The component also can be replaced with any other better component whenever necessary. Hence, the software can be maintained and updated continuously with minimum resources. The performance of the components is described in comparison with the non-component applications in terms of reuse as well as execution time.
OpenAlex reports 4 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This paper presents experiences of developing a power system analysis software using a combination of Object Oriented Programming (OOP) and Component Based Development (CBD) methodologies. In this development, various power system analyses are developed into software components. These components are integrated with graphical user interface components to build up a power system analysis application. By using both OOP and CBD methodologies, updating or adding new algorithm can be done to any specific component without affecting other components inside the software. The component also can be replaced with any other better component whenever necessary. Hence, the software can be maintained and updated continuously with minimum resources. The performance of the components is described in comparison with the non-component applications in terms of reuse as well as execution time.
Key concepts: Component (thermodynamics), Computer science, Component-based software engineering, Object-oriented programming, Reuse, Software, Software development, Graphical user interface