Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.

Slides:



Advertisements
Similar presentations
Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Advertisements

Lecture # 2 : Process Models
Process Improvement.
Object-Oriented Analysis and Design
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Requirements.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Eliciting Goals for Business Process Models with Non-Functional Requirements Catalogues Evellin C. S. Cardoso, João Paulo A. Almeida, Giancarlo Guizzardi.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
The Architecture Design Process
Four Dark Corners of Requirements Engineering
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Dealing.
PPA 502 – Program Evaluation
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Effectiveness.
IT Planning.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Introduction to Software Engineering Dr. Basem Alkazemi
University of Sunderland CSEM04 ROSCO Unit 13 Unit 13: Risk Methods CSEM04: Risk and Opportunities of Systems Change in Organisations Dr Lynne Humphries.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Requirements.
SE 555 – Software Requirements & Specifications Introduction
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
Management Roles, Functions, and Skills
Dealing with NFRs Vahid Jalali Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory,
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Towards.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Management Roles, Functions, and Skills
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
FLCC knows a lot about assessment – J will send examples
Codex Guidelines for the Application of HACCP
Management Roles, Functions, and Skills
The 2nd International Conference of e-Learning and Distance Education, 21 to 23 February 2011, Riyadh, Saudi Arabia Prof. Dr. Torky Sultan Faculty of Computers.
Decision Making Dr Vasuprada Kartic NAC Batch IX PGDCPM.
Software Project Management Introduction to Project Management.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Business Analysis and Essential Competencies
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
A Framework of Mathematics Inductive Reasoning Reporter: Lee Chun-Yi Advisor: Chen Ming-Puu Christou, C., & Papageorgiou, E. (2007). A framework of mathematics.
SOFTWARE DESIGN.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
Lecture 7: Requirements Engineering
1 Introduction to Software Engineering Lecture 1.
System Context and Domain Analysis Abbas Rasoolzadegan.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Smart Home Technologies
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Organizations of all types and sizes face a range of risks that can affect the achievement of their objectives. Organization's activities Strategic initiatives.
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Stages of Research and Development
TechStambha PMP Certification Training
Communicate the Impact of Poor Cost Information on a Decision
Communicate the Impact of Poor Cost Information on a Decision
Goal, Question, and Metrics
Communicate the Impact of Poor Cost Information on a Decision
Communicate the Impact of Poor Cost Information on a Decision
Technology Planning.
Shazna Buksh, School of Social Sciences
Goal-Driven Continuous Risk Management
Goal-Driven Software Measurement
Presentation transcript:

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal Driven requirements Engineering: Evaluation of Current Methods Abbas Rasoolzadegan Evangelia Kavakli & Pericles Loucopoulos

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 2 Purposes Identify the uses of goal modeling approaches in different contexts of requirements analysis phases Examine goal modeling in terms of five methodological orientations Define a framework for their analysis to evaluate them in a systematic and consistent manner

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 3 Introduction Since the mid-1970s RE was established as a distinct field of investigation and practice Its definition has evolved From: being concerned with software system To: a broader perspective that extends to also incorporate aspects of systems and organizations RE addresses the problems associated with business goals, plans, processes, etc and systems to be developed or to be evolved in order to achieve organizational objectives

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 4 Introduction (Cont.) Goal-driven view is based on the premise that in collaborative work situations, people do not strictly follow rules or procedures, rather they are aware of the personal and group goals and act accordingly Especially: When people are not faced with well structured and repetitive processes Rather they tackle ill-structured problems where both the intended outcome and the possible routes that can be followed to reach this outcome need be specified

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 5 Introduction (Cont.) In most cases, goal analysis itself is not the main focus of the goal oriented approaches, however explicit identification and management of goals is an integral part of their method and plays an essential role in achieving the aims of the approaches

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 6 Goal oriented approaches in RE Four tasks to be performed in RE Process Elicitation Negotiation Specification Validation

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 7 The role of goal analysis in relation to RE activities Goal Oriented approachGoal Analysis ContributionRE Activity GOMS, Goal-based Workflow, i*, ISAC 1- understanding the current organizational situation 2- understanding the need for change elicitation SIBYL, REMAP, The reasoning loop model 3- providing the deliberation context of the RE process negotiation KAOS, GBRAM, the NFR framework, the goal-scenario coupling framework 4- relating business goals to functional and non-functional system components specification GSN,GQM 5- validating system specifications against stakeholders’ goals validation

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 8 1- Understanding the current organizational situation 1. Enterprise modeling techniques Describe the business environment as co-operation among different organizational actors based on the assumption that these actors share common goals and act towards their fulfillment Implicitly or explicitly represent the goals of individuals, groups, or organizations, whereby a goal is a desired condition potentially attained at the end of an action The i* approach: Provides a description of work organization in terms of dependency relationships among actors Actors have freedom of action, within the social constraints, called strategic dependencies Actor is an active entity that carries out actions to achieve goals Goals to be achieved, tasks to be accomplished, resources to be produced and soft goals (non-functional requirements) to be satisfied are made specific embedded in the dependencies between actors Goal based workflow approach An organization is seen as a tuple [G,A,R] Actors (A) act collaboratively using resources (R) to attain their goals (G)

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 9 1- Understanding the current organizational situation (Cont.) 2. Cognitive task analysis techniques Are focused on human tasks A goal (external task) is defined as a state of a system that the human wishes to achieve A goal is achieved using some instrument, method, agent, tool, techniques, skills or generally, some devices which is able to change the system to the desired state A task (internal task) is defined as the activities required, used or believed to be necessary to achieve a goal using a particular devise

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh Understanding the need for change Work in this area focuses on methodologies for planning, organization and control of enterprise Discussion of goals in this context is considered not at an individual level but at a broader organizational level ISAC approach Goal analysis is considered during the early stages of requirements engineering, namely during the business change analysis phase The purpose of the analysis is to ensure that the business problems to be solved are identified and diagnosed correctly The relation between problems and goals can be represented by means of a problem/goal matrix Identification of clusters of similar problems that relate to similar goals Each cluster defines a change need that will act as a goal of the development process

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh Providing the deliberation context of the RE process Work in this area Aims at providing appropriate conceptualization of the RE process as well as supplying methods for improving activities such as problem solving and decision making during RE In this context, goals have been used to document and subsequently trace the history of the rational of decisions concerning either the system which is being designed, or the design process itself SIBYL is a system designed to help users represent and manage the qualitative elements of the decision making process is organized around decision graphs, which record the pros and cons of choosing from a set of alternatives to satisfy a goal

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh Relating business goals to functional and non-functional system components Including three broad processes: Goal elaboration KAOS  Highlights the importance of explicitly representing and modeling organizational goals and state explicitly their relations to operational system components  Support this process  from the high level goals that should be achieved by the composite system  to the operations, objects and constraints to be implemented by the software Scenario definition Use of goals to structure scenarios by connecting every action in a scenario to a goal assigned to an actor A goal is defined as something a stakeholder hope to achieve in the future A scenario expresses a possible way in which the goal can be achieved By assigning goals to scenarios and organizing the goals using three types of relations (refine, AND, OR) a structure for managing scenarios is established Result:  Just as goals can help in structuring scenarios, scenarios are also used to discover new goals Non-functional requirements definition Define a framework which provides for the representation of non-functional requirements in terms of interrelated goals

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh Validating system specifications against stakeholders’ goals Certifying that the produced system specification is in accordance with the uses’ needs by Define a set of metrics (qualitative or quantitative) against which system properties can be measured GQM (Goal-Question-Metrics) approach  Supports the identification of metrics from goals through the use of appropriate questions

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 14 A framework for understanding goal oriented approaches What does goal modeling achieve? How are goals expressed (informal/semi-formal/formal)? Goal-oriented approach Development Representation Subject Usage How are goal models developed and used (tools)? What is the nature of goals?

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 15 Subject View Types of goal Enterprise Current enterprise goals  What the organization currently whishes to achieve Future enterprise goals  Desired situations whishes to reach in the future Process Goals using to  understand the need for change  provide the deliberation context within the RE process Evaluation Signify the stakeholders’ criteria against which a system specification can be assessed

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 16

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 17 Conclusions Stakeholder goals and their role in defining and solving design problems are topics of longstanding interest in the field of RE Goal analysis approaches emphasize the use of goal notion in order to understand or describe aspects of the real world There is a variety of purposes and uses of goal models in RE

Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 18