REQUIREMENTS ENGINEERING LECTURE 2017/2018. Dr. Jörg Dörr. Conceptual Modelling. Fraunhofer IESE
|
|
- Darleen Burke
- 6 years ago
- Views:
Transcription
1 REQUIREMENTS ENGINEERING LECTURE 2017/2018 Dr. Jörg Dörr Conceptual Modelling
2 AGENDA Analysis & Specification with Conceptual Models 2
3 Requirements Specification ANALYSIS & SPECIFICATION WITH CONCEPTUAL MODELS 3
4 Requirements Analysis as Part of Specification Requirements Analysis is performed in order to analyze certain quality characteristics of requirements Is Requirements Analysis then synonym to requirements V&V? No! Analysis is concerned with an incomplete set of requirements, not discussed by the stakeholder. Requirements Analysis can be a very early activity. Requirements validation should have a complete, agreed upon set of requirements as input. Therefore, it is also regarded as part of the specification. 4
5 Means for Requirements Analysis Analysis Checklists Conceptual Modeling 5
6 Requirements Analysis Checklists Typical Questions (1) Is the requirement adequate with the business goal of the project? Does the requirement conflict with some domain constraint, policies or regulation? Does the requirement include premature design or implementation information? Is the requirement necessary? Does the requirement require non-standard hardware or must software be used? Is the requirement ambiguous, could different persons read it in different ways? What are the different interpretations for the requirement? Is the requirement realistic given the technology that will used to implement the system? 6
7 Requirements Analysis Checklists Typical Questions (2) Does the description of a requirement describe a single requirement or could it be broken into several different requirements? Has each requirement been assigned a priority? Are the system boundaries well defined? Have the portability, reliability, usability and maintainability requirements for the system been respected? Did you develop a behavioral or structural model for the system? Is the Data Dictionary implemented and correctly updated? Is the requirement testable by the test engineers? 7
8 Conceptual Modeling Conceptual Modeling is performed by the requirements engineer (analyst) to understand the problem domain and the requirements. Various models can be created to find out whether a problem domain or the requirements are understood well, i.e., whether the understanding of the requirements engineer is complete, consistent, and correct: Goals Data Interaction Structure Note: The models created during conceputal modeling are not necessarily part of the requirements specification. But they can be part of the requirements specification. 8
9 Conceptual Models For the different models, also various notations can be used, e.g., i-star (i*) E/R Diagrams UML SysML Business Process Modelling Notations 9
10 Goal Modeling Definitions Goal Models are often the first models used as they are on a high abstraction level. Definition goal: A goal is a desirable state lying in the future, which is not reached automatically but by specific actions. Goals and their dependencies are often described in conceptual models that are based on modelling languages. Definition goal model: A goal model is a conceptual model. Its goals and decompositions are documented in sub-goals and as necessary further dependencies between (sub)-goals. 10
11 Goal Modeling: Why should one do goal modeling? Goals can be one of the very early starting points (besides current problems) for requirements elicitation Goals are a fundamental concept to understand why new software or systems or changes to these systems are needed Goal modeling can be the anchor (rationale) for the following requirements traceability from high level to lower level 11
12 Classification of Goals Subject that has a goal Organizations or organizational units Individual Persons or Roles Object affected by the goal Quality goals Functional goals 12
13 Representation of Goals Various notations exist for goal modeling i-star (i*) GRL SIG (Softgoal interdependency graphs) And / OR Trees Just text 13
14 i*-framework I*-Framework I*-Framework is a graphical modelling language that is used for analysing and documentation It can be used in an early phase of system modelling for detecting and understanding problems It consists of two different models: Strategic Dependency Model (SDM): The Strategic Dependency Model is used to describe the dependency relationships among various actors. Strategic Rationale Model (SRM): The Strategic Rationale Model is used to provide rationales for single dependencies in the SDM. 14
15 Objects in i* Objects in i* Actor Actor Boundary Resource An actor is a person or a system that is in contact with the system. (Agents, Roles, Positions) A resource is a result required or supplied by the actor for completing the goal Softgoal A soft-goal describes the wish of an actor to complete a function regarding the quality Goal A goal is the documented intention of an actor Task A task consists of a number of steps which an actor has to execute for completing a task 15
16 Connections in i* Dependencies in i* Depender Dependee D D Soft-goal Dependency The soft-goal dependency describes an actors (Depender) completion of a soft-goal depends on another actor (Dependee). D Goal Dependency D The goal dependency describes an actors (Depender) completion of a goal depends on another actor (Dependee) D Task Dependency D The task dependency describes that an actor (Depender) depends on a task and that task depends on another actor (Dependee) D Resource Dependency D The resource dependency describes an actors (Depender) depending on a resource for goal completion and the resource is supplied by another actor (Dependee) 16
17 Connections in i* Links Means-end-Link The means-ends-link expresses what soft-goals, tasks and/or resources are needed to complete a goal. A meansends-link documents the reason why an actor is able to complete a specific goal, execute a specific task or use a specific resource. Task-Decomposition-Link The task-decomposition-link describes more detailed a task though goals, soft-goals, resources and/or more specified tasks. A task-decomposition-link documents the essential elements of a task to complete sub-goals or softgoals an the needed resources. +/- Contribution-Link + pos. affected - neg. affected The contribution-link describes a positive or a negative affect on soft-goals through tasks or other soft-goals. A contribution-link describes in what extend a task or another soft-goal contributes the soft-goal. But it does not explain the precisely range of support. 17
18 Example SDM Example taken from Master Software Engineering for Embedded Systems, TU Kaiserslautern, Textbook E-M.2 18
19 Example SRM Example taken from Master Software Engineering for Embedded Systems, TU Kaiserslautern, Textbook E-M.2 19
20 And / OR Decompositions (Trees) And-decomposition of a goal, i.e., the coarse-grain goal G0 is refined into several fine-grain goals G1 Gn that all have to be fulfilled to achieve goal G0. Or-decomposition of a goal. Again, a coarse-grain goal G0 is refined into several fine-grain goals G1 Gn. To fulfill G0, one (or more) of G1 Gn have to be achieved. 20
21 Example Example taken from Master Software Engineering for Embedded Systems, TU Kaiserslautern, Textbook E-M.2 21
22 Usage of UML for Conceptual Modeling (1) Various Diagrams of the UML can be used for Requirements Analyis, e.g.: Activity Diagrams for business processes / workflows Class and Object Diagrams for modeling data User Interface Navigation Maps, Collaboration Diagrams, and Sequence Diagrams for Interaction between different systems and stakeholders and systems 23
23 Usage of UML for Conceptual Modeling (2) Use Case Diagrams for getting an overview on the system functionality State Diagrams for modeling intended system states and their transformation or the (business) object lifecycles 24
24 UML Class Diagram to show Object Relationships 25 Figures taken from: Dr. Darius Silingas, Prof. Rimantas Butleris UML-Intensive Framework for Modeling Software Requirements
25 UML Diagram for Object Lifecycle 26 Figures taken from: Dr. Darius Silingas, Prof. Rimantas Butleris UML-Intensive Framework for Modeling Software Requirements
26 UML Use Case Model for Functional Overview 27 Figures taken from: Dr. Darius Silingas, Prof. Rimantas Butleris UML-Intensive Framework for Modeling Software Requirements
27 UML Activity Diagram to refine a Use Case 28 Figures taken from: Dr. Darius Silingas, Prof. Rimantas Butleris UML-Intensive Framework for Modeling Software Requirements
28 UML Information Flow Diagram for System Context 29 Figures taken from: Dr. Darius Silingas, Prof. Rimantas Butleris UML-Intensive Framework for Modeling Software Requirements
29 Conceptual Models in Different RE-Approaches Armour Use Case Diagram [Armour & Miller, 01] Domain Object Modell Initial what-is System Use Case Initial what will be System Use Case Base System Use Case Internal Use Case Elaborated System Use Case Transaction Information Model Transaction Trees Analysis Object Model Many different models and tasks, but basic design decisions are in common Holtzblatt [Beyer & Holtzblatt, 98] Work Model Focus Area User Environment Design (UED) Storyboard Use Case Object Model Constantine [Constantine & Lockwood, 99] Task model Domain model Content model Context Navigation Map Essential Use Case Use Case Maps 30
30 Conceptual Models Summary Conceptual models help clarifying certain aspects of a system in more detail than just natural language Support requirements analysis For different aspects of a system, different notations can be used 31
Modeling Issues Modeling Enterprises. Modeling
Modeling Issues Modeling Enterprises SE502: Software Requirements Engineering Modeling Modeling can guide elicitation: It can help you figure out what questions to ask It can help to surface hidden requirements
More informationRequirements Specifications & Standards
REQUIREMENTS ENGINEERING LECTURE 2014/2015 Dr. Jörg Dörr Requirements Specifications & Standards AGENDA Standards & Templates Natural Language Requirements Specification with Conceptual Models Suitable
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Joerg Doerr Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More informationRequirements. CxOne Standard
Requirements CxOne Standard CxStand_Requirements.doc November 3, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 OVERVIEW... 1 1.2 GOALS... 1 1.3
More informationLecture 9 Requirements Engineering II
Lecture 9 Requirements Engineering II Software Engineering ITCS 3155 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte September 23, 2008 Announcements
More informationRequirement Analysis
Requirement Analysis Requirements Analysis & Specification Objective: determine what the system must do to solve the problem (without describing how) Done by Analyst (also called Requirements Analyst)
More informationRequirements Analysis. SE 555 Software Requirements & Specification
Requirements Analysis Goals of Requirements Analysis Create requirements containing sufficient detail and of high enough quality to allow realistic project planning as well as successful design and implementation.
More informationBusiness Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3)
Business Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3) COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module
More informationLecture 6: Requirements Engineering
Lecture 6: Requirements Engineering Software System Design and Implementation ITCS/ITIS 6112/8112 001 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte
More informationLecture 4: Goals and Scenarios. System context. Usage facet. IT system facet. Core activities. Negotiation. Requirements artefacts
Lecture 4: Goals and Scenarios Stakeholders Identifying the problem owners Goals Identifying the success criteria Scenarios Identifying how it works 1 System context Subject facet Usage facet IT system
More informationLecture 8 Requirements Engineering
Lecture 8 Requirements Engineering Software Engineering ITCS 3155 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte September 18, 2008 Lecture Overview
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2015/2016 Eddy Groen Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More informationThe Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements
Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed
More informationSoftware specification and modelling. Requirements engineering
Software specification and modelling Requirements engineering Requirements engineering (RE) Requirements engineering is the process of establishing the services that a customer requires from a system and
More informationLecture 16: (Architecture IV)
Lecture 16: (Architecture IV) Software System Design and Implementation ITCS/ITIS 6112/8112 091 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte Oct.
More informationAdaptability Evaluation at Software Architecture Level
The Open Software Engineering Journal, 2008, 2, 1-30 1 Adaptability Evaluation at Software Architecture Level Open Access Pentti Tarvainen* VTT Technical Research Centre of Finland, Kaitoväylä 1, P.O.
More informationNatural Language Specification
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Dr. Jörg Dörr Natural Language Specification Most Requirements are Described in Natural Language Free Text (Prose) In Word In Excel (Tabular) In RM-Tools In Sys-ML
More informationPerspectives on User Story Based Visual Transformations
Perspectives on User Story Based Visual Transformations Yves Wautelet 1, Samedi Heng 2, and Manuel Kolp 2 1 KU Leuven, Belgium yves.wautelet@kuleuven.be, 2 LouRIM, Université catholique de Louvain, Belgium
More informationBCS Certificate in Requirements Engineering Syllabus
BCS Certificate in Requirements Engineering Syllabus Version 2.3 March 2015 Change History Any changes made to the syllabus shall be clearly documented with a change history log. This shall include the
More information350 Index 2005 GOAL/QPC
Index abstract testing, 274 acceptance criteria, 270 acceptance tests, 270 activity diagrams, 113, 114, 174-175, 321 actor catalog, 144 actor description, 144 actor hierarchy, 148 actor map, 59, 114, 144,
More informationThe ATCP Modeling Framework
The ATCP 2+9+1 Modeling Framework Bobbi Underbakke Adaptive Team Collaboration, Inc. 800.837.0677 atcprocess.com Adaptive Team Collaboration, Inc. March 22, 2005 Chris Armstrong Armstrong Process Group,
More informationDarshan Institute of Engineering & Technology for Diploma Studies
REQUIREMENTS GATHERING AND ANALYSIS The analyst starts requirement gathering activity by collecting all information that could be useful to develop system. In practice it is very difficult to gather all
More informationEvidence-based Development coupling structured argumentation with requirements development.
Evidence-based Development coupling structured argumentation with requirements development Jeremy.Dick@integrate.biz integrate 2012 based on paper Paper: EVIDENCE-BASED DEVELOPMENT COUPLING STRUCTURED
More informationLesson 06. Requirement Engineering Processes
Lesson 06 Requirement Engineering Processes W.C.Uduwela Department of Mathematics and Computer Science Objectives To describe the principal requirements engineering activities and their relationships To
More informationBCS Certificate in Requirements Engineering Extended Syllabus Version 2.5 May 2017
BCS Certificate in Requirements Engineering Extended Syllabus Version 2.5 May 2017 This professional certification is not regulated by the following United Kingdom Regulators - Ofqual, Qualification in
More informationA Goal-Oriented Approach for Optimizing Non-Functional Requirements in Web Applications
A Goal-Oriented Approach for Optimizing Non-Functional Requirements in Web Applications José Alfonso Aguilar, Irene Garrigós, and Jose-Norberto Mazón Lucentia-DLSI University of Alicante, E-03080, San
More informationRequirements Elicitation
Requirements Elicitation Introduction into Software Engineering Lecture 4 25. April 2007 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline Motivation: Software Lifecycle
More information4.2.2 Usability. 4 Medical software from the idea to the finished product. Figure 4.3 Verification/validation of the usability, SW = software
4.2.2 Usability Intended purpose, Market Validation Usability Usability Risk analysis and measures Specification of the overall system SW SW architecture/ of SW SW design Software design & integration
More informationSoftware Architecture. Lecture 5
Software Architecture Lecture 5 Roadmap of the course What is software architecture? Designing Software Architecture Requirements: quality attributes or qualities How to achieve requirements : tactics
More informationScenario-Based Analysis. Scenario-Based Analysis (example) Form analysis
Scenario-Based Analysis Scenario-Based Analysis (example) Provides a more user-oriented view perspective on the design and development of an interactive system. The defining property of a scenario is that
More informationRequirements Engineering: Specification & Validation. Software Requirements and Design CITS 4401 Lecture 18
Requirements Engineering: Specification & Validation Software Requirements and Design CITS 4401 Lecture 18 The Problems of Requirements What goal(s) are we trying to satisfy? How do we identify the scope
More informationProgress Report. Object-Oriented Software Development: Requirements elicitation (ch. 4) and analysis (ch. 5) Object-oriented software development
Progress Report Object-Oriented Software Development: Requirements elicitation (ch. 4) and analysis (ch. 5) CS 4354 Summer II 2014 Jill Seaman So far we have learned about the tools used in object-oriented
More informationTo practice UCSD Usability Design
To practice UCSD from principles to process Adds essential UCSD activities and roles to any process. Easy to communicate. Easy to integrate: in organizations and projects. A subset of a development process.
More informationDesign. Introduction
Design Introduction a meaningful engineering representation of some software product that is to be built. can be traced to the customer's requirements. can be assessed for quality against predefined criteria.
More informationCo-evolution of complementary formal and informal requirements
University of Wollongong Research Online Faculty of Informatics - Papers (Archive) Faculty of Engineering and Information Sciences 2004 Co-evolution of complementary formal and informal requirements Aneesh
More informationRequirements. Chapter Learning objectives of this chapter. 2.2 Definition and syntax
Chapter 2 Requirements A requirement is a textual description of system behaviour. A requirement describes in plain text, usually English, what a system is expected to do. This is a basic technique much
More informationA Model Transformation from Misuse Cases to Secure Tropos
A Model Transformation from Misuse Cases to Secure Tropos Naved Ahmed 1, Raimundas Matulevičius 1, and Haralambos Mouratidis 2 1 Institute of Computer Science, University of Tartu, Estonia {naved,rma}@ut.ee
More informationExtension and integration of i* models with ontologies
Extension and integration of i* models with ontologies Blanca Vazquez 1,2, Hugo Estrada 1, Alicia Martinez 2, Mirko Morandini 3, and Anna Perini 3 1 Fund Information and Documentation for the industry
More informationLecture 8: Use Case -Driven Design. Where UML fits in
Lecture 8: Use Case -Driven Design The Role of UML in the Software Process E.g. ICONIX Domain Models Use Cases 2008 Steve Easterbrook. This presentation is available free for non-commercial use with attribution
More informationSystem Analysis and Design
System Analysis and Design Svatopluk Štolfa Department of Computer Science VŠB-TU Ostrava 2007 svatopluk.stolfa@vsb.cz Course Objectives After completing this course you will be able to: Perform all roles
More informationAADL Requirements Annex Review
Dominique Blouin Lab-STICC Université de Bretagne-Occidentale Université de Bretagne-Sud Bretagne, France 1 AADL Standards Meeting, April 23 th, 2013 Agenda Comments from Annex Document Review Motivations
More informationRequirements Engineering Process
Requirements Engineering Process Requirement A description of a service that the system is expected to provide and the constraints under which it must operate. 1 Requirement Types Functional Requirement
More informationSofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (Requirements Specification).
More informationRequirements Engineering. Establishing what the customer requires from a software system. Requirements Engineering. What is a Requirement?
Engineering Establishing what the customer requires from a software system Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 5 and 6 Slide 1 Engineering
More informationReducing the costs of rework. Coping with change. Software prototyping. Ways to Cope with change. Benefits of prototyping
Coping with change Change is inevitable in all large software projects. Business changes lead to new and changed system requirements New technologies open up new possibilities for improving implementations
More informationClass Meeting 04 (Lecture 03) Objectives for this class meeting
CSE1720 Click to edit Master Week text 02, styles Class Meeting 04 (Lecture 03) Second level Third level Fourth level Fifth level Winter 2013 Tuesday, January 15, 2013 1 Objectives for this class meeting
More informationSoftware Engineering Unit 4- Requirement Analysis and Specification
Software Engineering Unit 4- Requirement Analysis and Specification Requirement Engineering The process to gather the software requirements from client, analyze and document them is known as requirement
More informationSE 1: Software Requirements Specification and Analysis
SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 U Waterloo SE1 (Winter 2006)
More informationTHE USE OF PARTNERED USABILITY TESTING TO HELP TO IDENTIFY GAPS IN ONLINE WORK FLOW
THE USE OF PARTNERED USABILITY TESTING TO HELP TO IDENTIFY GAPS IN ONLINE WORK FLOW Dianne Davis Fishbone Interactive Gordon Tait Department of Surgery, University of Toronto Cindy Bruce-Barrett Strategic
More informationMASTER S THESIS INFORMATION SCIENCE
MASTER S THESIS INFORMATION SCIENCE BY ROGER USMANY CONCEPTUAL MODELING FOR BUSINESS PROCESS SEMANTICS RADBOUD UNIVERSITY NIJMEGEN FACULTY OF SCIENCE INSTITUTE OF COMPUTING AND INFORMATION SCIENCES July
More informationModelling Variation in Quality Attributes
Modelling Variation in Quality Attributes Leire Etxeberria, Goiuria Sagardui, Lorea Belategi Faculty of Engineering University of Mondragon Limerick 16.01.2007 Research group &3 ;078 9 4143/7, 43 Research
More informationUsing a Goal-Driven Approach to Structure User Story Sets
Using a Goal-Driven Approach to Structure User Story Sets UU/SIKS Symposium on Natural Language in Requirements Engineering Yves Wautelet KU Leuven Background: User Stories as Artefacts for Requirements
More informationArchitectural Blueprint
IMPORTANT NOTICE TO STUDENTS These slides are NOT to be used as a replacement for student notes. These slides are sometimes vague and incomplete on purpose to spark a class discussion Architectural Blueprint
More informationEnterprise Architect Training Courses
On-site training from as little as 135 per delegate per day! Enterprise Architect Training Courses Tassc trainers are expert practitioners in Enterprise Architect with over 10 years experience in object
More informationcopyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner s Approach, 6/e Chapter 7 Requirements Engineering copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationBUILDING GOOD-QUALITY FUNCTIONAL SPECIFICATION MODEL
BUILDING GOOD-QUALITY FUNCTIONAL SPECIFICATION MODEL A few words on Samares Engineering Research and Consultancy on Systems Engineering Requirement engineering Model-Based Systems Engineering Co-simulation
More informationVragen. Use case analysis. Use-Cases: describing how the user will Use cases
Vragen Use case analysis Welke problemen kunnen optreden bij het expliciet maken van het impliciete model bij conceptueel modelleren? Wat is het doel van elicitatie? Noem een aantal elicitatie technieken?
More informationUsing FDAF to bridge the gap between enterprise and software architectures for security
Science of Computer Programming 66 (2007) 87 102 www.elsevier.com/locate/scico Using FDAF to bridge the gap between enterprise and software architectures for security Lirong Dai, Kendra Cooper Seattle
More informationVANCOUVER Chapter Study Group. BABOK Chapter 9 Techniques
VANCOUVER Chapter Study Group BABOK Chapter 9 Techniques May 27, 2015 David Ghotbi, CBAP Agenda Chapter 8 Review Pop Quiz Break Chapter 9 Review Pop Quiz Q & A 2 Chapter 9 Techniques Techniques: Alter
More informationCS6502-OBJECT ORIENTED ANALYSIS AND DESIGN Two Marks Question with Answers Unit-I Introduction to OOAD
CS6502-OBJECT ORIENTED ANALYSIS AND DESIGN Two Marks Question with Answers Unit-I Introduction to OOAD 1. What is Object-Oriented Analysis? Nov/Dec 2016 During object-oriented analysis there is an emphasis
More informationAdministrivia. Wednesday: Requirements and Specification. CS169 Lecture 4. We assign teams and you start on Monday. Determining Stakeholders and Needs
Administrivia Requirements and Specification CS169 Lecture 4 Wednesday: Groups and one-sentence idea(s) due at class One per group If you have a small group, still submit so that you will be kept together.
More informationRequirements engineering
engineering Chapter 4 1 Engineering in the textbook 4.1 Functional and non-functional 4.2 The software document 4.4 engineering processes 4.5 elicitation and analysis 4.3 specification 4.6 validation 4.7
More informationSE351a: Software Project & Process Management. 13 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa
SE351a: Software Project & Process Management W4.2: Requirements Engineering 13 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa SE351 Roadmap Introduction to Software Project Management Project Management
More informationRequirements Validation and Negotiation (cont d)
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Joerg Doerr Requirements Validation and Negotiation (cont d) REQUIREMENTS VALIDATION AND NEGOTIATION Requirements Validation Techniques 2 Techniques Overview
More informationROEVER ENGINEERING COLLEGE DEPARTMENT OF INFORMATION TECHNOLOGY CS2353-OBJECT ORIENTED ANALYSIS AND DESIGN. Unit-I. Introduction to OOAD
ROEVER ENGINEERING COLLEGE CS2353-OBJECT ORIENTED ANALYSIS AND DESIGN 1. What is Object-Oriented Analysis? Unit-I Introduction to OOAD PART-A During object-oriented analysis there is an emphasis on finding
More informationCIS 890: Safety Critical Systems
CIS 890: Safety Critical Systems Lecture: Requirements Introduction Copyright 2011, John Hatcliff. The syllabus and all lectures for this course are copyrighted materials and may not be used in other course
More informationIndividual Project. Agnieszka Jastrzębska Władysław Homenda Lucjan Stapp
Individual Project Individual Project Target: 1. Improvement of software development skill 2. to industrial method of building application in practical way Individual Project Slide 2/50 Individual Project
More informationAn Ontology-Based Methodology for Integrating i* Variants
An Ontology-Based Methodology for Integrating i* Variants Karen Najera 1,2, Alicia Martinez 2, Anna Perini 3, and Hugo Estrada 1,2 1 Fund of Information and Documentation for the Industry, Mexico D.F,
More informationSoftware Engineering Fall 2015 (CSC 4350/6350) TR. 5:30 pm 7:15 pm. Rao Casturi 09/17/2015
Software Engineering Fall 2015 (CSC 4350/6350) TR. 5:30 pm 7:15 pm Rao Casturi 09/17/2015 http://cs.gsu.edu/~ncasturi1 Requirement Elicitation 2 Requirement Engineering First step for understanding the
More informationindex_ qxd 7/18/02 11:48 AM Page 259 Index
index_259-265.qxd 7/18/02 11:48 AM Page 259 Index acceptance testing, 222 activity definition, 249 key concept in RUP, 40 Actor artifact analysis and iterative development, 98 described, 97 136 in the
More informationLecture 13 Introduction to Software Architecture
Lecture 13 Introduction to Software Architecture Software Systems Design and Implementation ITCS/ITIS 6112/8112 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at
More informationREQUIREMENTS. Michael Weintraub Spring, 2016
REQUIREMENTS Michael Weintraub Spring, 2016 Unit Objective Understand what requirements are Understand how to acquire, express, validate and manage requirements Definitions A thing demanded or obligatory
More informationHuman Computer Interaction Lecture 06 [ HCI in Software Process ] HCI in the software process
Human Computer Interaction Lecture 06 [ HCI in Software Process ] Imran Ihsan Assistant Professor www.imranihsan.com aucs.imranihsan.com HCI06 - HCI in Software Process 1 HCI in the software process Software
More informationIntroduction to Software Engineering. ECSE-321 Unit 9 Architectural Design Approaches
Introduction to Software Engineering ECSE-321 Unit 9 Architectural Design Approaches Requirement Elicitation Analysis (Software Product Design) Architectural Design Detailed Design Architectural Design
More informationBasics : the Requirements Engineering Process
SEG3101 (Fall 2010) Basics : the Requirements Engineering Process Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides prepared by Gunter Mussbacher with material from: Sommerville & Kotonya
More informationTropos: Security. Agent-Oriented Software Engineering course Laurea Specialistica in Informatica A.A
Tropos: Security Paolo Giorgini Department of Information and Communication Technology University of Trento - Italy http://www.dit.unitn.it/~pgiorgio Agent-Oriented Software Engineering course Laurea Specialistica
More informationi* on ADOxx : A Case Study
Fourth International i* Workshop, Hammamet, 7 th -8 th of June 2010 i* on ADOxx : A Case Study an Open Models Project! Authors: Margit Schwab, Dimitris Karagiannis, Alexander Bergmayr Agenda The Open Model
More informationThe Tropos visual modeling language. A MOF 1.4 compliant meta-model.
The Tropos visual modeling language. A MOF 1.4 compliant meta-model. Davide Bertolini 1, Anna Perini 1, Angelo Susi 1 and Haralambos Mouratidis 2 1 ITC-IRST, Via Sommarive 18, I-38050, Trento, Italy {bertolini,perini,susi}@irst.itc.it
More informationCapturing Contextual Variability in i* Models
Capturing Contextual Variability in i* Models Alexei Lapouchnian 1 and John Mylopoulos 2 1 epartment of Computer Science, University of Toronto, Canada alexei@cs.toronto.edu 2 epartment of Information
More informationBest Practices for Collecting User Requirements
Federal GIS Conference February 9 10, 2015 Washington, DC Best Practices for Collecting User Requirements Gerry Clancy Glenn Berger Requirements Provide direction for program success Why Requirements are
More informationChapter : Analysis Modeling
Chapter : Analysis Modeling Requirements Analysis Requirements analysis Specifies software s operational characteristics Indicates software's interface with other system elements Establishes constraints
More informationUML, BPMN, UX and Database Design Solutions uml process diagrams learn enterprise uml technical systems build scope definition and.
DOWNLOAD OR READ : UML PROCESS DIAGRAMS LEARN ENTERPRISE UML TECHNICAL SYSTEMS BUILD SCOPE DEFINITION AND SOLUTIONS ELICIT CAPTURE AND COLLECT REQUIREMENTS RULES DELIVERABLES RESOURCESPROCESS SYSTEMS ENGINEERING
More informationModel-based Transition from Requirements to High-level Software Design
Model-based Transition from Requirements to High-level Software Institut für Computertechnik ICT Institute of Computer Technology Hermann Kaindl Vienna University of Technology, ICT Austria System overview
More informationSoftware Architectures
Software Architectures Richard N. Taylor Information and Computer Science University of California, Irvine Irvine, California 92697-3425 taylor@ics.uci.edu http://www.ics.uci.edu/~taylor +1-949-824-6429
More informationIndex. brief description section (Use Case Specification documents), 138 Browser window (Rational Rose), 257 Business Rules document, 212
Index A abstract requirements, 10 activity diagram section (Use Case -144 actors identifying, 130-131 relationships, generalization between, 137 use cases, 133-135 Actual completion date attribute actual
More informationSoftware Processes. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationLecture 19 Engineering Design Resolution: Generating and Evaluating Architectures
Lecture 19 Engineering Design Resolution: Generating and Evaluating Architectures Software Engineering ITCS 3155 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at
More informationTESTING SOFTWARE QUALITY CHARACTERISTICS
TESTING SOFTWARE QUALITY CHARACTERISTICS Zigmars Gailans TAPOST 2017 Agenda Introduction Quality Functionality Usability Accessibility https://kahoot.it Kahoot app 2 3 What is Quality? The standard of
More informationRequirements Analysis Method For Extracting-Transformation-Loading (Etl) In Data Warehouse Systems
Requirements Analysis Method For Extracting-Transformation-Loading (Etl) In Data Warehouse Systems Azman Taa, Mohd Syazwan Abdullah, Norita Md. Norwawi College of Arts and Sciences Universiti Utara Malaysia,
More informationLoosely-coupled consistency between agentoriented conceptual models and Z specifications
University of Wollongong Research Online Faculty of Informatics - Papers (Archive) Faculty of Engineering and Information Sciences 2005 Loosely-coupled consistency between agentoriented conceptual models
More informationRequirements. Requirements. Types of Requirement. What Is a Requirement?
Beatrice Åkerblom beatrice@dsv.su.se Everything else in software development depends on the requirements. If you cannot get stable requirements you cannot get a predictable plan... What Is a Requirement?!
More informationA Method for Data Minimization in Personal Information Sharing
A Method for Data Minimization in Personal Information Sharing Prima Gustiene and Remigijus Gustas Department of Information Systems, Karlstad University, Sweden {Prima.Gustiene, Remigijus.Gustas}@kau.se
More informationBridging User-Centered Design and Requirements Engineering with GRL and Persona Cases
Bridging User-Centered Design and Requirements Engineering with GRL and Persona Cases Shamal Faily Department of Computer Science, University of Oxford Wolfson Building, Parks Road, Oxford OX1 3QD UK shamal.faily@cs.ox.ac.uk
More informationINTRODUCTION TO THE USER REQUIREMENTS NOTATION
INTRODUCTION TO THE USER REQUIREMENTS NOTATION CSRS 03, May 27, 2003 Daniel Amyot ITU-T Q.18/17 Rapporteur SITE, University of Ottawa, Canada damyot@site.uottawa.ca http://www.usecasemaps.org/urn/ Introduction
More informationDiseño y Evaluación de Arquitecturas de Software. Architecture Based Design Method
Diseño y Evaluación de Arquitecturas de Software Architecture Based Design Method César Julio Bustacara Medina Facultad de Ingeniería Pontificia Universidad Javeriana 08/10/2015 1 Architecture Based Design
More informationBuilding the User Interface: The Case for Continuous Development in an Iterative Project Environment
Copyright Rational Software 2002 http://www.therationaledge.com/content/dec_02/m_uiiterativeenvironment_jc.jsp Building the User Interface: The Case for Continuous Development in an Iterative Project Environment
More informationBDSA08 Advanced Architecture
UI Swing not the Java Swing libraries, but our GUI classes based on Swing Web Domain Sales Payments Taxes Technical Services Persistence Logging RulesEngine BDSA08 Advanced Architecture Jakob E. Bardram
More informationProduct. e ss. P roc. so get the right requirements. Garbage in garbage out,
If software is simply for automation, what would a washing machine be like? 1 RE Process Lawrence Chung Department of Computer Science The University of Texas at Dallas 2 RE Process: What is a Process?
More informationModel-Based Requirements Engineering. Tutorial by Kristian Sandahl
Model-Based Requirements Engineering Tutorial 2010-02-09 by Kristian Sandahl Planned topics What are requirements? Modelling requirements in UML Requirement model traceability Non-functional software requirements
More informationProgress Report. Object-Oriented Software Development: Requirements elicitation and analysis. Object-oriented analysis, design, implementation
Progress Report Object-Oriented Software Development: Requirements elicitation and analysis CS 4354 Fall 2012 Jill Seaman So far we have learned about the tools used in object-oriented design and implementation
More information