Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند (http://ce.aut.ac.ir/islab) Requirements Engineering : A Roadmap Towards Modeling.

Slides:

Advertisements

Similar presentations

1 GRL Introduction Lin Liu University of Toronto April 2001.

Advertisements

Centralize or Decentralize? A Requirements Engineering Perspective on Internet-Scale Architectures Eric Yu University of Toronto July 2000.

© Eric Yu Strategic Actor Relationships Modelling with i* Eric Yu University of Toronto December 13-14, 2001 IRST, Trento, Italy.

Strategic Modelling for Enterprise Integration Eric Yu University of Toronto 14th World Congress International Federation of Automatic Control July 5-9,

May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,

© Eric Yu Agenda Session 1 – Introduction December 13, 14:30-16:30 Motivations Basic concepts –The Strategic Dependency Model –The Strategic Rationale.

Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.

University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Software Requirements.

Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Requirement Engineering.

Software engineering for supply chains:

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Effectiveness of.

Four Dark Corners of Requirements Engineering

1 Creativity and the Age-Old Resistance to Change Problem in RE Gil Regev Donald C. Gause Alain Wegman.

شهره کاظمی 1 آزمايشکاه سيستم های هوشمند ( A Simple Definition of Portal Shohreh kazemi

1 Integrating Creativity into RE Process: Experiences with an Aircraft Traffic Management System Neil Maiden Suzanne Robertson.

1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.

CSCI928 Software Engineering Requirements & Specifications Modeling System Interactions Tri A. Kurniawan, M.Eng. Ph.D Candidate

The Quiet Revolution in Building Design and Construction: BIM.

Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت.

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap The Meaning Of Requirements.

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Dealing with Non-Functional.

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

Requirements Engineering Process – 1

1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.

TDT4252/DT8802 Exam 2013 Guidelines to answers

1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 5: i*modelling.

Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.

1 From GORE (not the US presidential candidate) to AORE (Agent-Oriented Requirements Engineering) Eric Yu University of Toronto November 2000.

1 An Agent-Oriented Methodology for Requirements Elicitation Luiz Marcio Cysneiros Dept. of Math and Stat Information Technology Program York University.

SOFTWARE DESIGN.

© Eric Yu Strategic Actor Relationships Modelling with i* Eric Yu University of Toronto December 13-14, 2001 IRST, Trento, Italy.

© Eric Yu Agent Oriented Software Development References

1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.

1 Evolving System Architecture to Meet Changing Business Goals An Agent and Goal-Oriented Approach Daniel Gross & Eric Yu Faculty of Information Studies.

Creating a European entity Management Architecture for eGovernment CUB - corvinus.hu Id Réka Vas

A Goal Based Methodology for Developing Domain-Specific Ontological Frameworks Faezeh Ensan, Weichang Du Faculty of Computer Science, University of New.

Using Meta-Model-Driven Views to Address Scalability in i* Models Jane You Department of Computer Science University of Toronto.

Agent Oriented Software Development

SOFTWARE DESIGN. INTRODUCTION There are 3 distinct types of activities in design 1.External design 2.Architectural design 3.Detailed design Architectural.

MFI-8: Metamodel for Role & Goal Registration Peng Liang, Keqing He, Jian Wang Huafeng Chen, Chong Wang, Yangfan He SKLSE, Wuhan University, P.R. China.

1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a: Architectural Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a:

1 آزمايشگاه سيستم های هوشمند ( معماری سيستمهای با مقياس بزرگ آزمايشگاه سيستمهای هوشمند پاييز 93.

© Eric Yu Business Processes (from Steve Easterbrook RE slides)  Business Process Automation  Leave existing business processes as they are 

1 Structuring Knowledge for a Security Trade-offs Knowledge Base Golnaz Elahi Department of Computer Science Eric Yu Faculty of Information Study University.

 2001 John Mylopoulos STRAW’ Software Architectures as Social Structures John Mylopoulos University of Toronto First ICSE Workshop titled “From.

1 Database Environment. 2 Objectives of Three-Level Architecture All users should be able to access same data. A user’s view is immune to changes made.

Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.

Use Cases and Use Case Diagrams Reporter: 陳雅萍. Outline Use cases, actors Organizing use cases Modeling the behavior of an element Use case diagrams Common.

Requirements Analysis

Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.

Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Introduction to the Unified Modeling Language.

1 Intelligent Information System Lab., Department of Computer and Information Science, Korea University Semantic Social Network Analysis Kyunglag Kwon.

Copyright © 2014 Wolters Kluwer Health | Lippincott Williams & Wilkins Chapter 8 Theoretical and Conceptual Frameworks.

5/10/2002 How to describe Plan Recognition Plan Recognizer With Knowledge Observations Assumptions Plans explaining observations.

IEEE Input for the Regulatory SC Mission Statement

Writing Requirements Lecture # 23.

CHAPTER.2: Requirements Engineering Processes

IEEE Std 1074: Standard for Software Lifecycle

Requirements Elicitation – 1

Frameworks in Research

Introduction to the Unified Modeling Language

TDT4252 Modelling of Information Systems Advanced Course

What is Software? Software is: (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures.

Members: Keshava Shiva Sanjeeve Kareena

Requirements Engineering Process – 1

Requirements Document

Interoperability Leadership and Governance

Project Management By: Michael Pantazis.

Presentation transcript:

Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering Shiva Vafadar

2 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap  Eric S. K. Yu, "Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering," re, p. 226, Third IEEE International Symposium on Requirements Engineering (RE'97), 1997

Shiva Vafadar 3 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Stating the problem  Problems in Requirements Statement ambiguous incomplete inconsistent informal

Shiva Vafadar 4 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Why RE is Important  Having well-organized bodies of organizational and strategic knowledge would allow such knowledge to be shared  As more and more systems in organizations interconnect and interoperate, it is increasingly important to understand how systems cooperate  Dealing with change is one of the major problems

Shiva Vafadar 5 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap i* modelling  The i* framework for modelling and reasoning about organizational environments and their information systems The Strategic Dependency (SD) model The Strategic Rationale (SR) model  The central concept in i* is that of the intentional actor

Shiva Vafadar 6 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Strategic Dependency model for meeting scheduling, without computer based scheduler

Shiva Vafadar 7 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Strategic Dependency model for meeting scheduling with computer-based scheduler

Shiva Vafadar 8 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Modeling stakeholder interests  The Strategic Dependency model provides one level of abstraction for describing organizational environments and their embedded information systems Showing External relationships among actors Hiding the intentional constructs within each actor  the Strategic Rationale model provides a more detailed level of modeling by looking “inside” actors to model internal intentional relationships

Shiva Vafadar 9 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Strategic Rationale model for meeting scheduling

Shiva Vafadar 10 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Strategic Rationale model for a computer- supported meeting

Shiva Vafadar 11 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Support needs of early-phase RE  Knowledge representation and reasoning  Degree of formality  Incorporating intentionality  Multi-lateral intentional relationships  Distributed intentionality  Means-ends reasoning  Organizational actors