درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت Dealing with NFR : Three Experimental Studies of a Process-Oriented Approach.

Slides:



Advertisements
Similar presentations
1 of 17 Information Strategy The Features of an Information Strategy © FAO 2005 IMARK Investing in Information for Development Information Strategy The.
Advertisements

Performance Assessment
Introduction to Monitoring and Evaluation
Centralize or Decentralize? A Requirements Engineering Perspective on Internet-Scale Architectures Eric Yu University of Toronto July 2000.
A UML Profile for Goal-Oriented and Use Case-Driven Representation of NFRs and FRs Sam Supakkul Titat Software LLC Lawrence Chung The.
Chapter 6 HCI in the software process. Software engineering and the design process for interactive systems Usability engineering Iterative design and.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Security Controls – What Works
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.
درس مهندسي نيازمندي ها استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت Requirement Engineering :A Roadmap.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت Meaning of Requirement.
IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer 2003.
Introduction to Research
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Dealing.
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.
Requirement Engineering – A Roadmap
Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap Dealing with Non-Functional.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت RE in The Year 00: A Research Perspective.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
Dealing with NFRs Vahid Jalali Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory,
HCI in the software process
Requirements Engineering Process – 1
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Software Architecture premaster course 1.  Israa Mosatafa Islam  Neveen Adel Mohamed  Omnia Ibrahim Ahmed  Dr Hany Ammar 2.
The phases of research Dimitra Hartas. The phases of research Identify a research topic Formulate the research questions (rationale) Review relevant studies.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
Problems in handling NFR Term Paper (as-is) problem statement BY AJAYKUMAR ASWATHAPPA CS/SE 6361 EXECUTIVE.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
ITEC224 Database Programming
CriteriaExemplary (4 - 5) Good (2 – 3) Needs Improvement (0 – 1) Identifying Problem and Main Objective Initial QuestionsQuestions are probing and help.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
1 Literature review. 2 When you may write a literature review As an assignment For a report or thesis (e.g. for senior project) As a graduate student.
Experimental Research Methods in Language Learning Chapter 16 Experimental Research Proposals.
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
1 Introduction to Software Engineering Lecture 1.
Designing software architectures to achieve quality attribute requirements F. Bachmann, L. Bass, M. Klein and C. Shelton IEE Proceedings Software Tzu-Chin.
The Role of Experience in Software Testing Practice Zahra Molaei Soheil Hedayatitezengi Comp 587 Prof. Lingard 1 of 21.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Part4 Methodology of Database Design Chapter 07- Overview of Conceptual Database Design Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Capturing and Reusing Functional and Non-functional Requirements Knowledge: A Goal-Object Pattern Approach Lawrence Chung and Sam Supakkul The University.
Systems Engineering Simulation Modeling Maintenance Analysis Availability Research Repair Testing Training Copyright © 2009, David Emery & D&S Consultants,
Formal Methods.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Human Computer Interaction
Environment and Disaster Planning Hari Srinivas, GDRC Rajib Shaw, Kyoto University Contents of the presentation: -What is the problem? -Precautionary Principles.
Research Methodology Class.   Your report must contains,  Abstract  Chapter 1 - Introduction  Chapter 2 - Literature Review  Chapter 3 - System.
Introduction to Research. Purpose of Research Evidence-based practice Validate clinical practice through scientific inquiry Scientific rational must exist.
Integrating FRs and NFRs: A Use Case and Goal Driven Approach Presented by Chin-Yi Tsai.
Integrating FRs and NFRs: A Use Case and Goal Driven Approach Sam Supakkul Network Surveillance Systems MCI Lawrence Chung Dept. of.
 Authors  Purpose  Main Phases  Related Literature  PDD  Examples  Conclusions.
Copyright © 2011 Wolters Kluwer Health | Lippincott Williams & Wilkins Chapter 1 Research: An Overview.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Stages of Research and Development
Introduction to Marketing Research
Master thesis: Automatic Extraction of Design Decision Relationships from a Task Management System Kick-Off Matthias Ruppel, 8th of May 2017, Munich.
Object-Oriented Software Engineering Using UML, Patterns, and Java,
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
HCI in the software process
HCI in the software process
Department of Computer Science Abdul Wali Khan University Mardan
Requirements Engineering Process – 1
Human Computer Interaction Lecture 14 HCI in Software Process
Presentation transcript:

درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت Dealing with NFR : Three Experimental Studies of a Process-Oriented Approach

Introduction In past, relatively little attention has been paid to the process of systematically dealing with NFR and developers have relied mostly on their own intuition in an ad-hoc way. To remedy the problems inherent in ad-hoc development, a framework has been developed to deal with non-functional requirements. The purpose of this paper is to give an initial evaluation of a recently proposed framework for dealing with non-functional requirements, by way of three studies of small portions of three information systems such as accuracy, security and performance. This paper attempts to evaluate the extent to which the frameworks’ objectives are met, namely representing NFR-specific requirements, considering design trade-off, relating design decisions to NFRs, justifying the decisions and assisting defects detection.

Three studies Credit Card Health Insurance Taxation User-friendliness Accuracy Ranging from commercial to governmental Considerable variation in domain charachteristics Performance Security

Process Vs. Product Quality of a product depends largely on the quality of the process that leads form high level NFRs to the product Complementary to the traditional product approach whose emphasis lies in product evaluation , usually involving metrics A little discussion about process oriented trend in QA and its reasons

NFR Framework Allows treating NFRs as potentially conflicting or synergic goals to achieve Considering development alternatives which could meet the stated NFRs Examining design tradeoffs Relating design decision to NFRs Justifying the decisions in relation to the needs of the intended application domain Assisting defect detection

Goal Graph Structure Used for record and structure NFRs Design alternatives Decisions rationale

Goal Graph Structure for Secure Document Security User Friendliness U U Accuracy Availability Confidentiality U U U External Confidentiality Identification Internal Confidentiality U U S Authentication IntConf (Small Accounts) Access Authorization U U IntConf (large Accounts) U U Vital Few Trivial Many S U S U Biometric Password IntConf Card Key

Sort Hierarchy NFR Sort User Friendliness Cost Security Performance Operating Cost Development Cost Time Availability Confidentiality Space Integrity Throughput Response Time Accuracy Completeness Main Memory Secondary Storage Internal Consistency External Consistency

Where Specific NFRs come from? Development knowledge about specific NFRs are to be taken from the literature and industrial experience and captured as methods, which are then presented for reuse to help the developers generate new goals and links

Methodology for Using NFR Framework Knowledge acquisition Acquisition of knowledge specific to NFRs Academic industrial Acquisition of domain knowledge organization Application of the NFR-Framework Identification of NFR-related concepts Identification of important NFR goals Identification of development techniques Identification of design rationale Linking NFR-related concepts Process, tools, output

Linking NFR-related Concepts Refining, clarifying and relating goals Identification of critical NFR goals Providing design rationale Assessing goal achievement

Refining, clarifying and relating goals Relating development techniques to NFR goals Identifying conflict and synergy Clarifying the meaning of goals Individually Associatively Identifying factors underlying correlations Development techniques - design and implementation

Identification of critical NFR goals Identifying what development techniques were repeatedly emphasized Identifying critical goals and critical dominant parts of the work load

Providing design rationale Locating applicable design rationale from either the source document or workload description Providing some design rationale from the basis of development tradeoffs present in goal graph structure under construction Design rationales are about choosing particular techniques

Internal Evaluation When developers made aware of quality concerns, that by itself helps improve the overall software quality When conflicts and synergy among NFR goals were explicitly described, it is possible to consider design tradeoffs in selecting among alternatives When competitive alternatives exist, expressing critical goals and the effect of each design decision helps resolving conflicts and record design rationale Relating design rationale back to source NFRs which could improve traceability

Internal Evaluation (Cont.) Detecting faults Ambiguity of goals Distinguishing goals into three types for detecting omissions Antagonistic correlation rules help detecting conflicts Detection of redundancies Synergic correlation helps in detecting opportunities

Negative Findings Need for new decomposition methods Design rationale Qualitative approach Scalability of goal graph

Experts Evaluation Framework would be helpful for developers Improvements in naming and presentation are needed to increase understandability Lack of consultation with domain people during the study left gaps in domain knowledge Applicability to broader domains Training costs and payoffs

Framework Findings Goal graph structures understandability Framework emphases Formality Process oriented approach Tradeoffs Determining main requirements Clarify requirement

Application Domain Findings Domain knowledge and proportionality Lack of contact with domain people Usage of framework Accuracy predominated security in spite of what NFR team thought

Conclusion NFR framework helps in presenting and using large numbers of NFRs NFR representation helps in considering design alternatives and their tradeoffs It is not clear that significantly larger studies could be handled by NFR-assistant tool It is important to find a cost effective way for training users work with framework

Reference Chung, L., Nixon, B.: Dealing with Non-Functional Requirements :Three Experimental Studies of a Process-Oriented Approach. In: Proc. of ICSE’95, pp. 25–37. ACM Press (1995)