Adoption of Unified Modeling Language

Unified Modeling Language (UML) is a standardized general purpose language with graphical expressions for visualisation, specification, construction, and documentation of models (Booch et al, 2005). Reinhardt (2011) highlights that; UML is developed with the intention of creating a platform independent of particular programming languages. Diagrams are the key enablers for graphically representing a system via UML approach. UML diagrams represent two different views of a system model comprising structure and behavioural aspects, therefore the stated diagrams are clustered as structure diagrams and behaviour diagrams. The structure diagrams depict static structure of a system by using objects, attributes, operations, and

134

relationships. On the other hand, behaviour diagrams depict dynamic behaviour of the system by indicating collaborations between objects. Given Figure 6.x gives a picture of UML diagrams and their breakdown among clusters.

Figure 6.11 UML Diagrams (Booch et al, 2005)

UML diagrams do not only differ from each other by their systematic functions, but also by their purpose of utilization. Given Table 6.x below shows how UML diagrams are categorized and how their purposes vary.

135

Table 6.1 UML Diagrams explained (Booch et al, 2005)

Structure wise software intensive modelling for the proposed system is beyond the scope of this study. Therefore structure diagrams are not handled for conceptualisation of the model. Intention of conceptualising the proposed SDSS is to represent it as lean as possible and make it comprehensible for the potential users and developers alike. In the light of stated argument, dynamic behaviour of the system emerges as the point that needs to be explored in order to make apparent the interactions of actors and operations taking part within the system. Therefore UML behaviour diagrams are chosen as the key enablers of conceptualisation in this study. The proposed system comprises functions (different operations within activities), and actors interacting with the system. For that reason, utilizing use case diagrams and activity diagrams comes to the forefront for conceptualization of the proposed model (See Table 6.1).

136 6.4.2.2 UML Use Case Diagrams

Use cases capture the functional requirements of a system and describe interactions between various actors and the system. The term “actor” means an individual, a system, or an organisation that has a goal in using the system.

The following figure 6.12 depicts the use case diagram for the proposed model.

Figure 6.12 Use Case Diagram for Smart Grid Applicability decision making mechanism

Actors defined in the abovementioned Use Case Diagram are i) Utilities, and ii) Sustainability officers of decision making stakeholders (in this case governmental certifying bodies).

Role of Utilities is to identify alternative areas for smart grid applicability, and supplying relevant data to run the proposed model. Additionally, as it is well agreed that DSS extends decision makers capabilities but it does not replace their judgment, deciding on the most suitable location among alternatives is the last but not least duty of the utility actor.

137

The other actor involved in the stated use case is the “Sustainability Officer”. Mentioned actor is a staff or division of an organization that is in charge of certifying/accrediting/approving the smart grid transition projects. Stated actor in given use case is involved in phases of identification of alternative locations, and approval of the projects.

6.4.2.3 UML Activity Diagrams

A UML Activity Diagram is a special case that is used for describing internal behaviour of a method or system, and it represents a flow driven by internally generated actions. Activity diagrams represent processes and sequential activities taking place in a system. Given Figure 6.13 illustrates the UML Activity Diagram of proposed GDSM4SGA.

138

In given activity diagram of the system, the design is divided into two main partitions by lines that are known as swim lanes. These partitions depict the responsibility area of the systems and actors. In GDSM4SGA system design, actor (utility) and GDSM4SGA assessment mechanism are two main responsible players. GDAM4SGA system is also divided into two subsystems as geospatial subsystem and AHP subsystem. Workflows are depicted in the figure given above.

“Utility” is an actor whose duty is to feed the mechanism with relevant data. If the actor chooses to use the proposed model, than predefined priority weights needed to be assigned to data. On the other hand, actor might choose to assign its own priorities and make judgements on the alternatives regarding stated “own priorities” in order to make a final decision. In the event of proposed model is being used, than it is time to describe the stated subsystems. Geospatial subsystem is responsible for forming the aggregate criterion maps that are vital for the AHP procedures to be carried out. Responsibility of AHP subsystem is to conduct linear algebraic computations in order to obtain ranking of alternatives which is a solid indicator of the priory of alternative locations.

6.5 Concluding Remarks

The main concern of this chapter is the conceptualisation of the proposed Geospatial Decision Making for Smart Grid Applicability – GDSM4SGA. In this respect, proposed system is discussed from functionality and data requirements perspectives, and suitability of proposed Smart Grid applicability assessment mechanism is elaborated for site selection problems. Additionally, embedded AHP algorithm and decision ontology are examined thoroughly. Two different approaches are developed for clarifying the structure of the proposed model. The first approach is the

139

“component” approach that breaks down the main components of the model. The second approach is the “conceptual model” that comprises overall data flows, and highlights the embedded mechanisms.

In order to offer more comprehensible and systematically standardized representation of the proposed model, modeling effort has been carried out via Unified Modeling Language (UML). In this regard, Use Case Diagram (illustrates relations of actors and actions within the system) and Activity Diagram (illustrates flow of operations) are produced.

In a nutshell, conceptualisation of the proposed model has been investigated in a rational way.

The following chapter handles mastering of the proposed model. Additionally, location characteristics in terms of the identified criteria are presented, and the assessment mechanism is run accordingly. Lastly, output of the system is displayed.

140

CHAPTER 7: MASTERING THE PROPOSED