Feature-Oriented Nonfunctional Requirement Analysis for Software Product Line Mats Hofman.

Slides:



Advertisements
Similar presentations
Web Services Architecture An interoperability architecture for the World Wide Service Network.
Advertisements

Adaptive Processes Software Processes Adaptive Processes.
Software Reuse SEII-Lecture 28
FORM: Feature-Oriented Reuse Method Kaan Kaynar. Domain Analysis and Engineering Domain: a family of related systems Domain analysis: examining a family.
Software Requirements
L ITERATURE REVIEW RESEARCH METHOD FOR ACADEMIC PROJECT I.
Adaptation of Evolving Requirements : A Managed approach for Non-functional requirements Tanya Kudchadker Nivedita Angadi Guides: Dr. A. Serebrenik (TU/e)
SWE Introduction to Software Engineering
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Writing the Research Report The purpose of the written report is to present the results of your research, but more importantly to provide a persuasive.
Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Requirement Engineering.
Template.
درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت Dealing with NFR : Three Experimental Studies of a Process-Oriented Approach.
Software Engineering General Project Management Software Requirements
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Dealing.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Information Modeling: The process and the required competencies of its participants Paul Frederiks Theo van der Weide.
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 Goal.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Dealing with NFRs Vahid Jalali Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory,
D. Pandey, A. K. Ramani and U. Suman.  D. Pandey  assistant professor at the Department of Information Technology of the BBA University in India. 
Software Engineer Report What should contains the report?!
Requirements Engineering
Software Product Line Engineering Andrew Burmester SE 4110 Section 2 4/14/11.
NON-FUNCTIONAL PROPERTIES IN SOFTWARE PRODUCT LINES: A FRAMEWORK FOR DEVELOPING QUALITY-CENTRIC SOFTWARE PRODUCTS May Mahdi Noorian
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
Problems in handling NFR Term Paper (as-is) problem statement BY AJAYKUMAR ASWATHAPPA CS/SE 6361 EXECUTIVE.
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.
CHINA An Environmental Report Card By James Jiang April 2015.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
CMSC 345, Version 1/11 Software Requirements 1. 2 CMSC 345, Version 1/11 What’s the big deal about requirements? The Tree Swing Project.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Design.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
SDMS Project Phase Ⅰ Duk-Jin Kim Tu Peng Yan Shi.
Requirements validation through viewpoint resolution By Julio Cesar Sampaio do Prado Leite Peter A. Freeman.
On the perception of software quality requirements during the project lifecycle Roald van der Valk.
Loc-based Variability for Mobile Information Systems Raian Ali, Fabiano Dalpiaz, Paolo Giorgini CAiSE’ June 2008.
Software Requirements Engineering CSE 305 Lecture-2.
How to read a scientific paper
Goal and Requirement Change Management in Enterprise Architecture Abelneh Teka 13, June 2012.
1 Introduction to Software Engineering Lecture 1.
BY BART KLEIN COMPAS – A METHOD ENGINEERING APPROACH.
Requirements Elicitation and Validation with Real World Scenes Peter Haumer, Klaus Pohl and Klaus Weidenhaupt Rens van Erk
Raian Ali, Fabiano Dalpiaz, Paolo Giorgini Location-based Software Modeling and Analysis: Tropos-based Approach.
How to write a professional paper. 1. Developing a concept of the paper 2. Preparing an outline 3. Writing the first draft 4. Topping and tailing 5. Publishing.
CS532 TERM PAPER MEASUREMENT IN SOFTWARE ENGINEERING NAVEEN KUMAR SOMA.
RE’05 The 13 th International conference on Requirements Engineering Reverse Engineering Goal Models from Legacy Code Yijun Yu 1 Yiqiao Wang 1 John Mylopoulos.
Advanced Science and Technology Letters Vol.28 (NT 2013), pp Constructing Domain Feature Models Based.
 “look again" (re + view) at what others have done  describes theoretical per­spectives and previous research findings regarding the problem.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Integrating FRs and NFRs: A Use Case and Goal Driven Approach Presented by Chin-Yi Tsai.
SOLICITING CUSTOMER REQUIREMENTS FOR PRODUCT CONCEPTUALIZATION ASSIGNMENT OF THE COURSE -METHOD ENGINEERING.
Research topic here Name Surname Faculty Research Proposal CS10A0862 INTRODUCTION TO RESEARCH METHODS.
Method engineering [infome] paper presentation Rodi heijbom
 Authors  Purpose  Main Phases  Related Literature  PDD  Examples  Conclusions.
A Use Case Based Approach to Feature Models’ Construction Jeroen Eissens
Contextual Text Cube Model and Aggregation Operator for Text OLAP
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
© 2011 Pearson Education, Inc. All rights reserved. This multimedia product and its contents are protected under copyright law. The following are prohibited.
A Method for Extracting and Modeling Product Line Functional Requirements Stijn van Esveld - Group I - 10th April, 2013.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
Software Requirements Engineering Session: 1 Topics: Chapters 1 – 3.
RES 723 Enthusiastic Study/snaptutorial.com
Reverse Engineering Goal Models from Legacy Code
1. Hook Introductions Integrated Quote
An Introduction to Embedded Software Architecture and Design
Presentation transcript:

Feature-Oriented Nonfunctional Requirement Analysis for Software Product Line Mats Hofman

Content Introduction to the topic Related literature PDD Example Questions?

Introduction to the topic “Feature-oriented nonfunctional requirement analysis for software product line” Written by: Peng (Fundan Uni- versity, China) Lee (Uni- versity of North Carolina) Published in: 2009.

Introduction: Goal The goal is to effectively deal with NFRs at different levels depending on the stakeholders preferences

Introduction: Phases Construction of the feature context model: How does a feature behave in the domain? Creating NFR Templates Discovering all the NFRs Goal Presence Analysis Analyse which goals are present Variability integrated non-functional perspective Contains every NFR goal + their operationalization Integrate NFRs into feature model Contains all the feature with the NFR NFR-integrated feature decision model

Related literature Requirements engineering for software product lines no big distinction between functional and non-functional requirements. (Pohl, Bckle & Van Der Linden, 2005, Kang, Donohoe, Koh, Lee & Lee 2002) A paper by Lee, Kang and Lee (2002) describes how the feature model. Cysneiros and Sampaio do Prado Leite (2004) propose a technique to get NFRs and incorporate them together with functional requirements. Sutcliffe and Minocha (1998) propose an analysis method for the NFR templates. The paper itself has been cited almost never

Example A generic application validation SPL. For example for a university to apply to a program.

Example A generic application validation SPL. For example for a university to apply to a program. Applications from different sources: Email, Paper, HTML Form Different NFRs possible: Has to work with slow internet High security

Example

PDD Construct Feature Context Identify non-fucntional variability Integrate NFRs Model NFR-oriented decisions

Questions?