On the perception of software quality requirements during the project lifecycle Roald van der Valk.

Slides:



Advertisements
Similar presentations
SERVICE-ORIENTED DESIGN AND DEVELOPMENT METHODOLOGY Method Engineering Eline de Haan.
Advertisements

User Interface Design Main issues: What is the user interface How to design a user interface.
Outline About author. The problem that discussed in the article.
Software Engineering General Project Management Software Requirements
Shared Ontology for Knowledge Management Atanas Kiryakov, Borislav Popov, Ilian Kitchukov, and Krasimir Angelov Meher Shaikh.
Information Systems Development Lecture 2: the idea of the Life Cycle.
Heuristic Evaluation.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Phase Difference = Phase Difference = 0.05.
Information Modeling: The process and the required competencies of its participants Paul Frederiks Theo van der Weide.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Software Engineering 1 Therese Hume X361 Room 7, prefab (mon,wed)
Presenter : Zamarak. Agenda Overview Related Literature Process Deliverable Diagram An Example.
April, 2013By:Hareune Asfour Method Engineering individual presentation Goal Oriented Conceptual Database Design.
QUPER Paper Outline Yuri Sprockel. Update Unfortunate CCV date pick Cost view elaboration New QUPER PDD almost finished.
B. RAMAMURTHY Capstone Design June 6, 2015 CSE651 1.
Software Project Management
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
1 Phases in Software Development Lecture Software Development Lifecycle Let us review the main steps –Problem Definition –Feasibility Study –Analysis.
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
[ §3 : 1 ] 2. Life-Cycle Perspective Overview 2.1 Motivation 2.2 Waterfall Model 2.3 Requirements in Context.
Systems Development Lifecycle Testing and Documentation.
Use Cases 1. Last week  Introduction to software engineering  How is it different from traditional engineering?  Introduction to specification  Operational.
BUSINESS SENSITIVE 1 Annual Meeting of the AASHTO Subcommittee on Design Human Factors Guidelines (HFG) for Road Systems (NCHRP 17-41) July 22, 2009 John.
User Interface Design Main issues: What is the user interface How to design a user interface ©2008 John Wiley & Sons Ltd.
EXTRACTING AND STATING USER INTERFACE PROTOTYPE REQUIREMENTS Rares Sfirlogea Method Engineering.
Feature-Oriented Nonfunctional Requirement Analysis for Software Product Line Mats Hofman.
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Requirements Elicitation and Validation with Real World Scenes Peter Haumer, Klaus Pohl and Klaus Weidenhaupt Rens van Erk
Method Engineering Requirements Elicitation for telemedicine pain treatment trials method Thomas Katsikarelis,
Method comparison: for Situational Method Engineering Mohssen Ali.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
1 METHODOLODY FOR THE SELECTION OF REQUIREMENTS ENGINEERING TECHNIQUES (MRETS) Fabio Kornek.
This chapter is extracted from Sommerville’s slides. Textbook chapter
Rule-Based Baseline Ontology Method for Requirement Elicitation Research paper: A Domain Ontology Building Process for Guiding Requirements Elicitation.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 10 Slide 1 Chapter 13 Finalizing Design Specifications.
CASE Tools Union Palenshus. In the early days… ► Software engineering tools consisted solely of translators, compilers, assemblers, linkers, loaders,
Project – A Quick Tutorial Krishna Sainath Meda. PROJECT  A task assigned to a set of people or teams to be completed within a time frame  Any project.
R. Keeney—April 23,  It is expected that if you have a Purdue AGEC degree, you will be an effective communicator of economic rationale and ideas.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
1 Quality Attributes of Requirements Documents Lecture # 25.
Software Quality in Use Characteristic Mining from Customer Reviews Warit Leopairote, Athasit Surarerks, Nakornthip Prompoon Department of Computer Engineering,
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
What are non-functional requirements? What are some NFR taxonomies?
Topics to be presented Adv. Databases and Dataware Houses Topics to be presented by students 1.Indexing DW (Bitmap, MDX, X-Tree, UB-Tree, etc.) ( approx.
A Personal Data Audit Method through Requirements Engineering Thomas van Eerden.
Statement of the Work SOW By: Wilmer Arellano FIU Fall 2007.
Using Domain Ontology as Domain Knowledge for Requirements Elicitation Haruhiko Kaiya & Motoshi Saeki A model description by Roel Esten.
Embedded Lab. Park Yeongseong.  Introduction  Problem Formulation  Approach Overview  AOI(Area Of Interest) Extraction  CallStack Pattern Mining.
Method engineering [infome] paper presentation Rodi heijbom
 Authors  Purpose  Main Phases  Related Literature  PDD  Examples  Conclusions.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Methodology Review Chapter 7 Part 2: Design Methodology Object-Oriented Modeling and Design Byung-Hyun Ha
Software architecture is the high- level structure of a software system. It has no concrete definition but can be best described as an organizational.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
421 Review Questions 1.Does software engineering add documentation that slows down the project? 2.Is there one software process that is better than the.
A Method for Extracting and Modeling Product Line Functional Requirements Stijn van Esveld - Group I - 10th April, 2013.
Documents Authors Objectives Software Description Learning Areas Levels.
Requirements Analysis Requirements Engineering (CI 2323) Daniel Siahaan.
Product Support BCA Exercise – JRATS/JTAMS
Unified Process Source & Courtesy: Jing Zou.
VDM++ Tutorial Architecture.
Review of Related Literature and Studies
Introduction to UML.
Engineering Processes
Requirements Engineering Lecture 6
人間の二足歩行モデルにおけるシミュレーション
Presentation transcript:

On the perception of software quality requirements during the project lifecycle Roald van der Valk

Overview Method Description Related Literature PDD Example

The Method Meant to study when and how specific aspects of software development are handled. In this case: software quality requirements Consists of 4 main phases ▫Select documents ▫Find signifiers ▫Extract relevant messages ▫Evaluate results

The Method’s Origins Based on earlier work ▫Same Authors ▫Focussed on non-functional requirements Neil A. Ernst ▫Software requirements John Mylopoulos ▫Requirements engineering, conceptual modelling

Related Literature Non-functional requirements ▫“The process of discovering, documenting and managing the requirements for a computer-based system” (Sommerville and Sawyer, 1997) Mining documents for requirements ▫Cleland-Huang, Settimi, Zou and Sole (2006) Improved signifier selection ▫Hindle, Ernst, Godfrey and Mylopoulos (2011)

Example