<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><PerformancePlanOrReport><Name>Goal-oriented Requirements Discovery Sub-process</Name><Description>Self-Adaptive Systems (SAS) can adapt their own behavior in response to context information or changes in the environment and also in response to their own behavior. The interest in requirements engineering for SAS has grown in recent years, but despite this, some works involving requirements specification of these systems do not guide requirements elicitation. Goal-oriented requirements engineering (GORE) modeling languages are widely used to specify requirements for SAS. There are GORE modeling languages specifically proposed for the SAS domain and each of them presents a fixed and small set of concepts. Ontologies can be used to overcome the limitation of concepts, since they can help in the representation of concepts within a domain, as well as in the communication and specification of requirements. The purpose of this thesis is to provide a richer set of SAS concepts to guide the elicitation and specification of requirements for such systems. An ontology for SAS is proposed, as well as a process to guide the use of the ontology for eliciting and specifying requirements for SAS. The unique core ontology for requirements for SAS in literature does not cover all main concepts that SAS involves, like the modeling dimensions and a feedback loop.</Description><OtherInformation>The sub-process requirements discovery has five sequence activities to discover the goal-oriented requirements of a self-adaptive systems. We introduce the sub-process as a guidance for elicitation for SAS requirements. There is no goal-oriented requirements elicitation guide for SAS on literature (to the best of our knowledge). The specification approaches proposed to SAS do not explicit how to elicit the goal-oriented requirements, they just allow the specification of SAS on a predefined group of characteristics, without making it clear how the characteristics were found.It is not our purpose to discover goal-oriented requirements for SAS in an automatic way. We intend to guide the requirements engineer on the goal-oriented requirements discovery activity on this kind of system, facilitating the activities on requirements elicitation for SAS phase, rendering them on practical and organized activities. For this, we propose a guide that can be followed through some activities. The sub-process presents five activities to be followed and performed. These activities present guidelines to requirements engineer. Each sub-process activity presents:• a name;• an objective;• a description;• expected results;• a set of questions (in order to facilitate the performing of the activity);• concepts and competence questions of Onto4SASGORE ontology (that the activitywas based on).</OtherInformation><StrategicPlanCore><Organization><Name>Monique Conceição Soares</Name><Acronym>MCS</Acronym><Identifier>_5d072d74-ac5c-11ea-8393-f6681583ea00</Identifier><Description/><Stakeholder StakeholderTypeType="Person"><Name>Jaelson Freire Brelaz de Castro</Name><Description>Advisor</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Carla T.L.L. Silva Schuenemann, Ph.D.</Name><Description>Co-Advisor</Description></Stakeholder></Organization><Vision><Description>Self-Adaptive Systems (SAS)</Description><Identifier>_5d072eb4-ac5c-11ea-8393-f6681583ea00</Identifier></Vision><Mission><Description>To provide a richer set of SAS concepts to guide the elicitation and specification of requirements for such systems.</Description><Identifier>_5d072f72-ac5c-11ea-8393-f6681583ea00</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Goals</Name><Description>Find the goals of the system.</Description><Identifier>_5d073076-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>Activity 1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Name: Define the goals of the system.Objective: With this activity, we aim to find the goals of the system.Description: The engineer should answer a set of questions to the system description based on some concepts of Onto4SASGORE and some competence questions by using the knowledge offered by information present in Table 16, in order to discovery all goals of the system.Expected results: In the end of this activity, the requirements engineer will obtain the goals of the system.Questions:</OtherInformation><Objective><Name>Main Goal</Name><Description>Determine the main goal.</Description><Identifier>_5d073166-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>1. What is the main goal of the system?</OtherInformation></Objective><Objective><Name>Secondary Goals</Name><Description>Determine the secondary goals.</Description><Identifier>_5d073238-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>2. What are the secondary goals of the system?</OtherInformation></Objective><Objective><Name>Characteristics</Name><Description>Determine the characteristics of each goal.</Description><Identifier>_5d0732d8-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>3. What are the characteristics of each goal?</OtherInformation></Objective><Objective><Name>Functional Goals</Name><Description>Determine the functional goals.</Description><Identifier>_5d073396-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>4. What are the functional goals of the system?</OtherInformation></Objective><Objective><Name>Non-Functional Goals</Name><Description>Determine the non-functional goals.</Description><Identifier>_5d073468-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>5. What are the non-functional goals of the system?</OtherInformation></Objective><Objective><Name>Constraints</Name><Description>Identify the constraints.</Description><Identifier>_5d07354e-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>1.6</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>6. What are the constraints of the system?</OtherInformation></Objective></Goal><Goal><Name>Characteristics</Name><Description>Find the sensors and effectors of the system.</Description><Identifier>_5d0735ee-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>Activity 2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Name: Identify the physical characteristics of the system.Objective: In this activity, we intend to find the sensors and effectors of the system.Description: Some systems may have a software or service actuating as a sensor or effector, not necessarily a physical component. Therefore, this activity involves mechanism or resource concepts from the ontology. The requirements engineer should answer the set of questions based on the system description and according to the Onto4SASGORE concepts.Expected results: The identification of the sensor(s) and effector(s) of the system.Questions:</OtherInformation><Objective><Name>Sensors</Name><Description>Identify the sensor.</Description><Identifier>_5d073684-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>1. What is the sensor of the system?</OtherInformation></Objective><Objective><Name>Effectors</Name><Description>Identify the effector.</Description><Identifier>_5d07372e-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>2. What is the effector of the system?</OtherInformation></Objective><Objective><Name>Resources</Name><Description>Identify the resources used.</Description><Identifier>_5d0737ce-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>3. What are the resources used by system?</OtherInformation></Objective></Goal><Goal><Name>Context &amp; Environment</Name><Description>Find the context to be considered by the system and the characteristics from the environment where the system is operating.</Description><Identifier>_5d073864-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>Activity 3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Name: Identify the context and environment characteristics of the system.Objective: In this activity, we can find the context to be considered by the system and the characteristics from the environment where the system is operating.Description: With the Onto4SASGORE ontology and the description of the system, the requirements engineer will answer the set of questions of this activity.Expected results: In the end of this activity, the requirements engineer will have the context and environmental information of the system.Questions:</OtherInformation><Objective><Name>Contexts</Name><Description>Identify the contexts.</Description><Identifier>_5d07390e-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>1. What are the contexts considered by the system?</OtherInformation></Objective><Objective><Name>Users</Name><Description>Identify the users.</Description><Identifier>_5d0739b8-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>2. What are the users of the system?</OtherInformation></Objective><Objective><Name>Environment</Name><Description>Define the environment.</Description><Identifier>_5d073a9e-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>3. What is the environment where the system is operating?</OtherInformation></Objective></Goal><Goal><Name>Adaptation &amp; Change</Name><Description>Find all goal-oriented requirements related to adaptation and change of the system.</Description><Identifier>_5d073c92-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>Activity 4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Name: Define the goal-oriented requirements related to adaptation and change of the system.Objective: In this activity, we intend to find all goal-oriented requirements related to adaptation and change of the system.Description: To accomplish the objective, the requirements engineer will answer the questions of this activity based on the system description and the Onto4SAS ontology.This activity also involves goal, mechanism and effect concepts.Expected results: After performing this activity, the requirements engineer will have the information about the adaptation of the system.Questions:</OtherInformation><Objective><Name>Actions</Name><Description>Identify the actions.</Description><Identifier>_5d073d5a-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>1. What are the actions of the system?</OtherInformation></Objective><Objective><Name>Effects</Name><Description>Identify the effects.</Description><Identifier>_5d073e0e-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>2. What are the effects by action?</OtherInformation></Objective><Objective><Name>Changes</Name><Description>Identify the changes.</Description><Identifier>_5d073ecc-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>4.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>3. What are the changes of the system?</OtherInformation></Objective><Objective><Name>Causes</Name><Description>Identify the cause.</Description><Identifier>_5d073f80-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>4.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>4. What is the cause of the change?</OtherInformation></Objective><Objective><Name>Mechanisms</Name><Description>Identify the mechanisms of change.</Description><Identifier>_5d07402a-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>4.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>5. What is the mechanism used to perform a change?</OtherInformation></Objective></Goal><Goal><Name>Interfaces</Name><Description>List the goal-oriented requirements related to interface of the system.</Description><Identifier>_5d0740e8-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>Activity 5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Name: Identify the interface characteristics of the system.Objective: In this activity, we intend to list the goal-oriented requirements related to interface of the system. The objective of this activity is identifying to whom or to what the system communicates or interacts, as well as the communication interface to realize it.Description: The requirements engineering will identify all the actors of the system based on the system description and guided by the Onto4SASGORE. He or she will answer the questions for this activity using the Onto4SASGORE concepts and competence questions ...Expected results: Find the actors of the system.Questions:</OtherInformation><Objective><Name>Actors</Name><Description>Identify the actors.</Description><Identifier>_5d0741a6-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>5.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>1. Who are the actors of the system?</OtherInformation></Objective><Objective><Name>Inputs</Name><Description>Identify the inputs for each action.</Description><Identifier>_5d07425a-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>5.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>2. What is the input of each action of the system?</OtherInformation></Objective><Objective><Name>Outputs</Name><Description>Identify the outputs of each action.</Description><Identifier>_5d074322-ac5c-11ea-8393-f6681583ea00</Identifier><SequenceIndicator>5.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>3. What is the output of each action of the system?</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2017-12-31</StartDate><EndDate/><PublicationDate>2020-06-11</PublicationDate><Source>https://repositorio.ufpe.br/bitstream/123456789/30492/1/TESE%20Monique%20Concei%C3%A7%C3%A3o%20Soares.pdf</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>
