! To solve problems. ! To take up new opportunities. ! Requirements - descriptions of. " Behavior. " Data. " Constraints (eg. cost and schedule)
|
|
- Margery Brooks
- 5 years ago
- Views:
Transcription
1 COMP3110/6311, Software Analysis and Design Why do we Develop Software? To solve problems To take up new opportunities The value of Requirements "#$"%&'(%)#*+"%#)&),'$&+)& '()#-&)'$./,0.&+%/&.%1"*(%2.%# In order to select and use appropriate methods for Requirements Analysis, we must first understand the value of requirements SE Projects - The value of requirements and design Shayne R Flint Slide 1 SE Projects - The value of requirements and design Shayne R Flint Slide 2 What do people value in software? Its ability to " Solve problems " Help users to take advantage of new opportunities Cost and Schedule Quality factors " Reliability, maintainability, portability, efficiency " Human/Computer interaction, testability " Marketability, profitability How do we capture stakeholders values? Requirements - descriptions of " Behavior " Data " Constraints (eg. cost and schedule) " Properties (eg. Reliability, portability, maintainability) " Interfaces (to hardware and other software) To be of value to stakeholders, software needs to satisfy stakeholder requirements SE Projects - The value of requirements and design Shayne R Flint Slide 3 SE Projects - The value of requirements and design Shayne R Flint Slide 4
2 What groups of people have requirements? Anyone or any organisation that influences requirements " Users, maintainers, supporters, trainers " Analysts, designers, programmers, testers, managers " Regulators, unions, professional bodies Stakeholders Why bother with requirements? They tell us what stakeholders value A basis for agreement between stakeholders " What to build (scope) " Schedule and Cost " Acceptance criteria Failure to reach and maintain such agreement is a major cause of project failure Good requirements lead to improved agreement between stakeholders and increased likelihood that software will please the stakeholders SE Projects - The value of requirements and design Shayne R Flint Slide 5 SE Projects - The value of requirements and design Shayne R Flint Slide 6 What do we value in requirements? Characteristics of good requirements " Complete, consistent, unambiguous " Relevant, necessary " Testable, traceable " Measurable " Feasible How can we best ensure that our requirements have these characteristics? " Requirements Engineering What is Requirements Engineering? A systematic and repeatable approach to the creation and maintenance of requirements Requirements Engineering is not about light weight vs heavy weight processes. " It is not about XP vs Agile vs 'traditional' SE Projects - The value of requirements and design Shayne R Flint Slide 7 SE Projects - The value of requirements and design Shayne R Flint Slide 8
3 What activities do we need to think about? What do we value in each RE Activity? Elicitation Elicitation Analysis and Negotiation Documentation There is nothing here about life-cycle models or how these activities are conducted They all need to be done in some way irrespective of life-cycle Ability to identify purpose and constraints Ability to identify all stakeholders Ability to collect and organise all stakeholder needs Ability to abstract and deal with aspects/viewpoints Analysis and Negotiation Ability to reduce conflicts Ability to ensure completeness Ability to ensure compatibility Validation SE Projects - The value of requirements and design Shayne R Flint Slide 9 SE Projects - The value of requirements and design Shayne R Flint Slide 10 What do we value in each RE Activity? Documentation Ability to present requirements in an understandable, complete, and unambiguous way Ability to deliver an appropriate level of detail for all stakeholders (users, designers, testers, maintainers, trainers, managers etc.) Validation Ability to detect requirements problems (consistency, correctness and completeness) Ability to impart confidence in the requirements How do we conduct each activity? We need to select methods that best deliver the value expected by stakeholders " Based on evidence and understanding of characteristics (if we have any) Stakeholder values are often shaped by " Criticality of the software " Requirement volatility " Quality requirements " Stakeholder cultures and politics (supplier, client etc.) " Schedule and budget One size does not fit all SE Projects - The value of requirements and design Shayne R Flint Slide 11 SE Projects - The value of requirements and design Shayne R Flint Slide 12
4 Some methods Elicitation " Interviews " Scenarios " Soft Systems Methodologies " Observation and Social Analysis Analysis and Negotiation " Structured Analysis Data Flow, Entity Relationship and State Diagrams " Object-Oriented Analysis Class, State, Collaboration, and Sequence diagrams " Prototypes Many of the approaches listed on this slide apply to elicitation, analysis and negotiation COMP3110/6311 Some methods Documentation " Natural language and diagrams " IEEE and MIL standards " Supported and formalised by Models Tools Verification " Inspection and Reviews " Prototypes " Requirements Testing " Executable specifications (xtuml) SE Projects - The value of requirements and design Shayne R Flint Slide 13 SE Projects - The value of requirements and design Shayne R Flint Slide 14 So, what are the main challenges? Requirements value Selecting the right methods " There are many to choose from " Little evidence as to how they work in various situations Dealing with diverse groups of people " Conflict and Viewpoints " Culture and Politics Dealing with change " Learning (wrong and incomplete requirements) " Environment (the world changes) " Technology (we may be able to do new things) Understanding this chain of stakeholder values provides a basis for choosing appropriate methods Developing a 'toolbox' of methods is the easy bit. Choosing the right methods for each project is the hard bit Problem or Opportunity Software Software Development Requirements Requirements Engineering RE Activities RE Methods Design etc SE Projects - The value of requirements and design Shayne R Flint Slide 15 SE Projects - The value of requirements and design Shayne R Flint Slide 16
5 Recap - What do people value in software? Its ability to " Solve problems " Help users to take advantage of new opportunities Cost and Schedule Quality factors The value of Software Design " Reliability, maintainability, portability, efficiency " Human/Computer interaction, testability " Marketability, profitability SE Projects - The value of requirements and design Shayne R Flint Slide 17 SE Projects - The value of requirements and design Shayne R Flint Slide 18 Who might be interested in design? End users don't care? " They may, in the sense that if they believe a design is 'good', they may gain increased confidence that the software will satisfy their needs Designs are mainly used by development and maintenance stakeholders What do we value in a design? Completeness " Implementation of all requirements " Traceability Uniformity Reuse Readability, understandability Flexibility SE Projects - The value of requirements and design Shayne R Flint Slide 19 SE Projects - The value of requirements and design Shayne R Flint Slide 20
6 What design concepts do we know about? How do we deliver stakeholder value? Abstraction " Structural, Procedural, Data, Control Refinement Modularity Software Architecture Information Hiding Cohesion Coupling Engineering - A systematic and repeatable approach to the creation and maintenance of software designs that provide value to their stakeholders " And, again, it is not about light weight vs heavy weight processes. SE Projects - The value of requirements and design Shayne R Flint Slide 21 SE Projects - The value of requirements and design Shayne R Flint Slide 22
version NDIA CMMI Conf 3.5 SE Tutorial RE - 1
Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria
More informationRequirements Engineering: Part I. Software Requirements & Project Management CITS3220
Requirements Engineering: Part I Software Requirements & Project Management CITS3220 The Problems of Requirements What goal(s) are we trying to satisfy? How do we identify the scope and properties of the
More informationRequirements Engineering
Requirements Engineering Professor Ray Welland Department of Computing Science University of Glasgow E-mail: ray@dcs.gla.ac.uk The Importance of Requirements Identifying (some) requirements is the starting
More informationSoftware Development Life Cycle (SDLC) Tata Consultancy Services ltd. 12 October
Software Development Life Cycle (SDLC) Tata Consultancy Services ltd. 12 October 2006 1 Objectives (1/2) At the end of the presentation, participants should be able to: Realise the need for a systematic
More informationVANCOUVER Chapter Study Group. BABOK Chapter 6 Requirements Analysis
VANCOUVER Chapter Study Group BABOK Chapter 6 Requirements Analysis February 24, 2016 Hossam Saleh, CBAP Introduction PD Hours Presentation and quizzes at IIBA Vancouver Chapter website Certification Update
More informationREQUIREMENTS ENGINEERING
1 REQUIREMENTS ENGINEERING Chapter 4- by Ian Sommerville TOPICS COVERED Functional and non-functional requirements The software requirements document Requirements specification Requirements engineering
More informationIntroduction to Software Engineering
Introduction to Software Engineering 2. Requirements Collection Mircea F. Lungu Based on a lecture by Oscar Nierstrasz. Roadmap > The Requirements Engineering Process > Functional and non-functional requirements
More informationRequirements Engineering Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1
Requirements Engineering Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1 Objectives To describe the principal requirements engineering activities and their relationships
More informationRequirements Engineering
Requirements Engineering Software Engineering Andreas Zeller Saarland University Requirements Engineering The Real World Requirements Engineering A description of what the system should do (but not how)
More informationRequirements Engineering. Andreas Zeller Saarland University
Requirements Engineering Software Engineering Andreas Zeller Saarland University Communication project initiation requirements gathering Planning estimating scheduling tracking Waterfall Model (1968) Modeling
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More informationRequirements Verification and Validation
SEG3101 (Fall 2010) Requirements Verification and Validation SE502: Software Requirements Engineering 1 Table of Contents Introduction to Requirements Verification and Validation Requirements Verification
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering
More informationRequirements Engineering
Requirements Engineering Minsoo Ryu Hanyang University Topics covered Requirements Engineering Requirements Elicitation Requirements Validation Requirements Management 2 2 Requirement Engineering The goal
More informationBusiness Analysis for Practitioners - Introduction
Business Analysis for Practitioners - Introduction COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module 3 Requirements Elicitation and
More informationEngineering. CMMI for Development V.1.2 Module 3. M03/Engineering/v1.2
Engineering CMMI for Development V.1.2 Module 3 M03/Engineering/v1.2 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process
More informationVerification and Validation
System context Subject facet Usage facet IT system facet Development facet Validation Core activities Elicitation Negotiation Context of consideration Execution of RE activities Created requirements artefacts
More informationLecture 2: Software Quality Factors, Models and Standards. Software Quality Assurance (INSE 6260/4-UU) Winter 2016
Lecture 2: Software Quality Factors, Models and Standards Software Quality Assurance (INSE 6260/4-UU) Winter 2016 INSE 6260/4-UU Software Quality Assurance Software Quality Quality Assurance Factors and
More information8/30/2010. Lecture 1. Topics covered. Functional and non-functional requirements The software requirements document Requirements specification
Topics covered Functional and non-functional requirements The software requirements document Chapter 4 Requirements Engineering Requirements specification Requirements engineering processes Lecture 1 Requirements
More informationProduct Requirements. Requirements. Get it Right ASAP. Why Requirements are Difficult. Levels of S/W Requirements. Types of S/W Requirements
Requirements Overview importance of getting right difficulty of getting right types and levels of characteristics of good the Requirements Development Process inception gathering, classification actors
More informationNDIA Test and Evaluation Conference
NDIA Test and Evaluation Conference Model Based Systems Engineering (MBSE) and Modeling and Simulation (M&S) adding value to Test and Evaluation (T&E) March 16, 2011 Larry Grello High Performance Technologies,
More informationProduct Requirements. Requirements. Get it Right ASAP. Why Requirements are Difficult. Types of S/W Requirements. Levels of S/W Requirements
Requirements Overview importance of getting right difficulty of getting right types and levels of characteristics of good the Requirements Development Process inception gathering, classification evaluation
More informationSyllabus. REQB Certified Professional for Requirements Engineering. Advanced Level Requirements Manager
Syllabus REQB Certified Professional for Requirements Engineering Requirements Manager Version 1.0 2011 The copyright to this edition of the syllabus in all languages is held by the Global Association
More informationCritical Skills for Writing Better Requirements (Virtual Classroom Edition)
Critical Skills for Writing Better Requirements (Virtual Classroom Edition) Eliminate Costly Changes and Save Time by Nailing Down the Project Requirements the First Time! Critical Skills for Writing Better
More informationCHAPTER 2 LITERATURE SURVEY
10 CHAPTER 2 LITERATURE SURVEY This chapter provides the related work that has been done about the software performance requirements which includes the sub sections like requirements engineering, functional
More informationPrerequisites It is recommended that the participants have a working knowledge of traditional Business Analysis tasks and techniques.
BA31 - Unified Modeling Language (UML) for Business Analysts This course will provide Business Analysts with new capabilities to improve their skills with using visual modeling techniques to document requirements.
More informationThe pink lines detail the updating made. Dim 1 Dimension 2 Dimension 3
European e-competence Framework (e-cf) Version 3.0 - DRAFT CWA The white lines contain the e-cf v 2.0 content, The green lines contain the update. Changes are highlighted in red. The pink lines detail
More informationGlobal Journal of Engineering Science and Research Management
SW REQUIREMENT ENGINEERING IN PRACTICE Smita Raj* * C-204, Shiksha Niketan, Vasundhara, Sec-5, Ghaziabad 201012 DOI: 10.5281/zenodo.199474 KEYWORDS: Requirement, Requirement engineering, process models,
More informationQuestions on Business Analysis Planning and Monitoring. analysis plan is compatible with the project plan?
Questions on Business Analysis Planning and Monitoring 1. Who is responsible for ensuring that the business analysis plan is compatible with the project plan? a. Business analyst b. Project manager c.
More informationFunctional and non functional requirements. Requirements elicitation Requirements analysis Requirements validation Requirements management
Requirements Engineering Eduardo Rodriguez Tello, PhD Cinvestav Tamaulipas 2009 2012 1 Content Requirements engineering Functional and non functional requirements Requirements engineering processes Requirements
More informationComp435 Object-Oriented Design. Requirements and Use Cases. Requirements Analysis. Outline. Requirements Analysis. Requirements change
Comp435 Object-Oriented Design Requirements and Use Cases Week 2 Computer Science PSU HBG 1 3 Outline Requirements Analysis Types of Requirements Requirements in Iterative Development Requirements Artifacts
More informationIt will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.
Functional Specification / Requirement Document (FSD / FRD) The Functional Specification Document (FSD) in software development is a formal document that describes the functions of the software/system
More informationCSE 435 Software Engineering. Sept 14, 2015
CSE 435 Software Engineering Sept 14, 2015 What is Software Engineering Where Does the Software Engineer Fit In? Computer science: focusing on computer hardware, compilers, operating systems, and programming
More informationObjectives. Rapid software development. Topics covered. Rapid software development. Requirements. Characteristics of RAD processes
Objectives Rapid software development To explain how an iterative, incremental development process leads to faster delivery of more useful software To discuss the essence of agile development methods To
More informationCS 351 Requirements Engineering
CS 351 Requirements Engineering Instructor: Joel Castellanos e-mail: joel@unm.edu Web: http://cs.unm.edu/~joel/ 4/13/2017 2 1 Designing Large Programs: Essence & Accidents "The hardest single part of building
More informationSoftware Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationChapter 1. Contents. 1.1 What is Software Engineering! Solving Problems. Objectives. What is Software Engineering
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationRequirements Elicitation. Software Requirements & Project Management CITS3220
Requirements Elicitation Software Requirements & Project Management CITS3220 Lecture Overview What is requirements elicitation? Underlying difficulties Generic Techniques Specific Techniques Requirements
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationRequirement Engineering. L3 The requirement study. Change is constant. Communication problem? People are hard to understand!
Requirement Engineering L3 The requirement study Fang Chen Requirement are ubiquitous part of our lives Understand the requirement through communication Requirement Creation Communication problem? People
More information7. Project Management
Subject/Topic/Focus: 7. Project Management Management of Systems Engineering Processes Summary: Project management Systems engineering Maturity model and process improvement Literature: Ian Sommerville:
More informationOi Requirements Communication in New Product Development
Steer Your Development! Goal-Oriented Oi Requirements Communication in New Product Development September 9, 2008 Samuel Fricker, Tony Gorschek, Martin Glinz Product Manager in Context: Simplified, Stylized
More information2068 I. Attempt any ten questions. (10x6=60)
2068 I 1. Differentiate between software process and software process model. 2. What are the key challenges facing in Software Engineering? Explain. 3. Explain the system design process. 4. Why program
More informationWhy Document the Architecture? EEC 421/521: Software Engineering. Design Process. Thinking About Design. Stakeholder Communication.
Why Document the Architecture? EEC 421/521: Software Engineering Architectural Design Stakeholder Communication High-level presentation of system System Analysis Big effect on performance, reliability,
More informationBABOK v2.0 Snapshots
BABOK v2.0 Snapshots Hi, As we know, each knowledge area of BABOK v 2.0 has several parts which provide details about the knowledge area. For this reason, I have developed a snapshot package for BABOK
More informationSoftware Development
Software Development Requirement Analysis 1 Process Step: Requirements Requirements define the function of the system from the client's viewpoint. The requirements establish the system's functionality,
More informationChapter 1. What is Software Engineering. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationOrganising Requirements
Requirements Organisation, Analysis and Evolution Software Requirements and Design CITS 4401 Lecture 20 CITS4401 Software Requirements and Design 2 Viewpoints Organising Requirements Interactor viewpoints:
More informationRequirements engineering
Requirements engineering Paul Jackson School of Informatics University of Edinburgh What are requirements? Traditional to distinguish functional from non-functional requirements. Functional requirements
More informationSYLLABUS. What is Agility, What is an Agile Process, Agile Process Models.
Contents i SYLLABUS UNIT - I CHAPTER - 1 : INTRODUCTION TO Introduction to Software Engineering. CHAPTER - 2 : A GENERIC VIEW OF PROCESS Software Engineering, Process Framework, CMMI, Process Patterns,
More informationRequirements Elicitation. Software Requirements and Design CITS 4401 Lecture 17
Requirements Elicitation Software Requirements and Design CITS 4401 Lecture 17 Lecture Overview What is requirements elicitation? Underlying difficulties Generic Techniques Specific Techniques Requirements
More informationTest Workflow. Michael Fourman Cs2 Software Engineering
Test Workflow Michael Fourman Introduction Verify the result from implementation by testing each build Plan the tests in each iteration Integration tests for every build within the iteration System tests
More informationSE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics E-mail: Keti@ii.edu.mk What is Software Engineering? SE is the discipline concerned
More informationRequirements Elicitation
Elicitation Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical factors such as political, social, and organizational
More informationFunctional requirements and acceptance testing
Functional requirements and acceptance testing Lecture 3 Software Engineering TDDC88/TDDC93 autumn 2007 Department of Computer and Information Science Linköping University, Sweden Message from the course
More informationBABOK v3 Task to Technique Mapping
BABOKv3 Task Technique # Technique Name Knowledge Area Business Planning and Monitoring Plan Business Approach 10.18 Document 10.20 Financial Plan Stakeholder Engagement 10.9 Business Rules 10.18 Document
More informationWhen Does Requirements Volatility Stop All Forward Progress?
When Does Requirements Volatility Stop All Forward Progress? Practical Software and Systems Measurement User s Group Conference Golden, Colorado July 2007 Jo Ann Lane and Barry Boehm University of Southern
More informationMotivations. Case Study. Reference documents for the presentation
Case Study Basic V Introduction &V Case Engineering Study Engineering approach for the design of commercial aircraft AGENDA Motivation SYSTEMS ENGINEERING concerns Presentation of the INCOSE document describing
More informationChapter 1. Contents. What is Software Engineering 9/9/13. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationWho Am I? Project Basics. Project. Why Project? Alternative (names) Poloya s Method. Computer Science program ISD Datasystem AB (6 years)
Project Basics Anders Hessel Department of Information Technology Uppsala University Who Am I? Computer Science program ISD Datasystem AB (6 years) Developer Technical Project Manager 1 ½ year Ericsson
More informationLecture 5: Requirements Engineering II. COSI 120b, Principles of Software Engineering
Lecture 5: Requirements Engineering II COSI 120b, Principles of Software Engineering Your Requirements Customer UI Designer Tester Sales End User Your Requirements What did they look like? How specific
More informationRequirements Engineering and SCRUM. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 13, 2007
Requirements Engineering and SCRUM Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 13, 2007 2 Scrum Larman Ch. 7 3 Scrum Model Start A small group is responsible for picking
More informationWhat are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.
What are requirements? Basics of Requirement Engineering Muzaffar Iqbal Farooqi A requirement is a necessary attribute in a system, a statement that identifies a capability, characteristic, or quality
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More informationDr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 21 st, Requirements Engineering
Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 21 st, 2003 Requirements Engineering Class Objectives Students will be able to define the two process areas associated with the Requirements
More informationSuitability of the Requirements Abstraction Model (RAM) Requirements for High Level System Testing
Master Thesis Software Engineering Thesis no: MSE-2007:27 October 2007 Suitability of the Requirements Abstraction Model (RAM) Requirements for High Level System Testing Naeem Muhammad School of Engineering
More informationCore Design Requirements At the start of a project, it is important to specify those parameters and properties that:
Design & Innovation Fundamentals Lecture 3 Requirements Analysis Design Process Expression of need Engineer translates need into a definition of problem, including statement of desired outcome Engineer
More informationSystems Analysis for Business Analysts (3 Day)
www.peaklearningllc.com Systems Analysis for Business Analysts (3 Day) This is a basic course to help business analysts understand the basics of systems analysis. This course is ideal for people who are
More informationBasics of Software Engineering. Carmen Navarrete
Basics of Software Engineering Carmen Navarrete Basics of Software Engineering Outline: Overview Software Development Life Cycle Project management Requirements Analysis and design Implementation Testing
More informationChange is constant. Obstacle to RE: Why requirement study? Limitation of the designers Different knowledge domains Not expertise Ubiquitous nature
Design the right thing! Fang Chen Change is constant Requirement Design Creation What makes the change? Human nature Society Organization i Competitors Human nature: never satisfy ) 4 Why requirement study?
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2014/2015 Dr. Sebastian Adam Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects
More informationL2 The requirement study. Requirement Engineering. Fang Chen
L2 The requirement study Fang Chen Requirement Engineering Requirement are ubiquitous part of our lives Understand the requirement through communication People are hard to understand! Requirement Creation
More informationComparison Matrix ISO 9001:2015 vs ISO 9001:2008
Comparison Matrix ISO 9001:2015 vs ISO 9001:2008 Description: This document is provided by American System Registrar. It shows relevant clauses, side-by-side, of ISO 9001:2008 standard and the ISO 9001:2015
More informationCSEB233: Fundamentals of Software Engineering. Software Requirements Part 1 Understanding Requirements Engineering
CSEB233: Fundamentals of Software Engineering Software Requirements Part 1 Understanding Requirements Engineering Objectives Discuss the concept of requirements and the types of requirements Explain what
More informationDefining Requirements
Defining Requirements The scope of any project should represent the minimum amount of work needed to fulfil the customer s, or end user s requirements. Doing more work is wasteful; doing less means the
More informationUnit: Information Systems Analysis Assignment title: Popular Portables June Marking Scheme
Unit: Information Systems Analysis Assignment title: Popular Portables June 2015 Marking Scheme Markers are advised that, unless a task specifies that an answer be provided in a particular form, then an
More informationRequirements Knowledge Model. Business. Event. Business. responding. Business. Use Case 1.. Business tracing * * * * Requirement
Requirements Knowledge Model This model provides a language for communicating the knowledge that you discover during requirements-related activities. We present it here as a guide to the information you
More informationThe software lifecycle and its documents
Lifecycle models The software lifecycle and its documents Supplementary material for Software rchitecture course Origin: Royce, 1970, Waterfall model Scope: describe the set of processes involved in the
More informationSoftware Engineering QUESTION BANK
Software Engineering QUESTION BANK UNIT - 1 1. What is software? Explain the two fundamental types of software products. 2. What is software engineering? What is the difference between software engineering
More informationREQB Foundation Level Sample Exam paper
REQ Foundation Level Sample Exam paper 1 Which of the following statements is NOT true? Requirements may be related to the development process and the software product. One of the most important sources
More informationIntroduction to Software Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016
Introduction to Software Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016 1 Goals Present an introduction to the topic of software life cycles concepts and terminology benefits
More informationChapter 26. Quality Management
Chapter 26 Quality Management - Quality concepts - Software quality assurance - Software reviews - Statistical software quality assurance - Software reliability, availability, and safety - SQA plan (Source:
More informationRequirement Error Taxonomy
Requirement Error Taxonomy Loan arranger system (LA): The LA application supports the business of a loan consolidation organization. This type of organization makes money by purchasing loans from banks
More informationRequirements Organisation, Analysis. Software Requirements & Project Management CITS3220
Requirements Organisation, Analysis and Negotiation Software Requirements & Project Management CITS3220 Organising Requirements Viewpoints Interactor viewpoints: people or other systems that interact
More informationResearch on software systems dependability at the OECD Halden Reactor Project
Research on software systems dependability at the OECD Halden Reactor Project SIVERTSEN Terje 1, and ØWRE Fridtjov 2 1. Institute for Energy Technology, OECD Halden Reactor Project, Post Box 173, NO-1751
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationRequirements Engineering with Use Cases
Requirements Engineering with Use Cases Csaba Veres Outline What are use cases? What do they tell us? How can you write them (properly)? What is a use case? A use case specifies the behavior of a system
More informationRequirements Engineering
Requirements Engineering Software Engineering CS 130 Donald J. Patterson Content adapted from Essentials of Software Engineering 3rd edition by Tsui, Karam, Bernal Jones and Bartlett Learning Requirements
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers UNIT 1 1. What are software myths Answer: Management myths: We already have a book
More informationMajor attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationChapter 8 Understanding Requirements
Chapter 8 Understanding Requirements Software Engineering: A Practitioner s Approach, 8th edition by Roger S. Pressman 1 Outline What is RE? RE Tasks RE Process Eliciting Requirements( 需求获取 ) Developing
More informationManagement of Projects
of Projects Giuseppe Lami Page 1 Course Outline! Part 1: The Project (PM) Framework! Part 2: The PM as a Process! Part 3: Techniques, Methods and Tools Supporting the PM! Part 4: Requirements Engineering
More informationFocus Area Level Report Including Knowledge and Skills, and Performance Indicators
Including Knowledge and Skills, and CSPB01.01 Identify and analyze customer software needs and requirements. CSPB01.01.01.00 Gather data to identify customer requirements. CSPB01.01.01.01 Gather information
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationRE Activities, Bespoke RE, Stakeholders. Lecture 2, DAT230, Requirements Engineering Robert Feldt,
RE Activities, Bespoke RE, Stakeholders Lecture 2, DAT230, Requirements Engineering Robert Feldt, 2011-09-07 Recap Software Engineering is more than technology RE mistakes very costly Constant battle -
More informationCCU 2010 / Identifying User Needs and Establishing Requirements. Lesson 7. (Part1 Requirements & Data Collection)
CCU 2010 / 2011 Lesson 7 Identifying User Needs and Establishing Requirements (Part1 Requirements & Data Collection) Previous Lesson (1) Participative Design Users are active in Developing Discussing and
More informationArchitecture. By Glib Kutepov Fraunhofer IESE
Architecture By Glib Kutepov Glib.kutepov@iese.fraunhofer.de Outline 1. Why Architecture? 2. What is Architecture? 3. How to create an Architecture? Alignment Modeling and Structuring Architectural Views
More information