Requirements Engineering. Csaba Veres
|
|
- Robert Murphy
- 5 years ago
- Views:
Transcription
1 Requirements Engineering Csaba Veres
2 utline What is requirements engineering? Why is it important? How can you do it (properly)?
3 an Requirements engineering, P11 overview quality evaluation (validation) Using objects for Systems Analysis, P10, P13 differences in problem analysis, requirements, and design different objects in different phases Requirements engineering and COTS, P14 special methods Use cases, P12 motivation for use cases in requirements engineering how to write good use cases
4 oday s lecture Reading from Kotonya/Sommerville: Requirements Engineering: Processes and Techniques Processes Intro Requirements processes Techniques well known techniques
5 hy are requirements important? Many systems are delivered late and over budget. they often don t do what users wanted often not used to full effectiveness Proper requirements definition can ease the problems. Each stage of development can multiply he problem by 10 times discovering problems at requirements: cost 1 discovering after design: cost 10 discovering after implementation: cost 100 discovering after rollout to client: cost 1000
6 hat are requirements? Requirements define what the system is require to do, and the circumstances under which it mus operate. e.g. 1. The system shall maintain records of all library mater including books, serials, newspapers and magazines video and audio tapes, reports, collections of transparencies, computer disks and CD-ROMS. 2. The system shall allow the users to search for an item by title, author, or ISBN. 3. The system s user interface shall be implemented us WWW browser. 4. The system shall support at least 20 transactions per second. 5. The system facilities which are available to public use shall be demonstrable in 10 minutes or less.
7 hat sorts of requirements? The previous list contained different types of requirement: 1. Very general requirements that set out in broad terms what the system should do 2. Functional requirements 3. Implementation requirements 4. Performance requirements to specify minimum acceptable performance 5. Usability requirements
8 complex web of needs... Functional requirements Non functional requirements security speed usability (?) Organisational standards Other interacting systems
9 can lead to many problems Requirements don t reflect real needs Requirements are inconsistent/incomplete e.g. requirement 1) above... CDs don t have ISBN.. author? Misunderstandings between customers, users, developers... Requirements engineering aims at concrete epeatable methods for doing the job as we as possible
10 AQs about requirements hat are requirements? In addition to what we already talked about, requirements can relate to: user-level facility (e.g. word processor should have s checker ). general system property (e.g. the system should nev make personal information available ) i. specific constraint on the system (e.g. the sensor mu be polled 10 times a second ) v. business rules (specific computations, formulas). constraint on development (e.g. the system must be developed using Ada)
11 AQ Requirements can be about what the system has to do functional, non-functional how it has to do it domain experts
12 AQ hat is requirements engineering? Discovering, documenting, and maintaining equirements Systematic, repeatable techniques to make sure requirements are complete consistent relevant
13 AQ ow much does RE cost? Depends on the project Around 10% to 15% of total cost
14 AQ hat happens when the requirements are wrong? Late delivery and inflated cost End-users not satisfied with the system modification, abandoning Unreliable High cost of maintenance and modification
15 AQ hat is a requirements engineering process? Structured set of activities to derive, validate, and maintain requirements document elicitation analysis negotiation validation deally should include timelines, tools, esponsibilities, etc.
16 AQ there an ideal RE process? Yes. Only joking... System, organizational culture, etc. The few existing standards relate to proces outputs, not processes themselves
17 AQ hat is a requirements document? THE official statement of the system equirements Describes a number of lower level entities functional specifications, etc.)
18 AQ hat are stakeholders? Anyone who has a direct or indirect bearing on the system requirements end users, managers, development and maintenance engineers, customers who rely on the system, external bodies (e.g. tax departmen Make sure ALL stakeholders are consulted, or there will be trouble!
19 AQ w do requirements relate to design? Seperate activities? specification vs. solution what vs. how n reality, often there are overlaps system has to fit within existing environment (e.g. data h to be read from ORACLE DB ) large systems decompose into subsystems which have their own requirements re use of existing software re use of approved patterns or solutions
20 AQ hat is requirements management? The process of managing changes to equirements document Change control collect, verify, and assess changes Change impact management how does the change impact the whole system? economic feasability
21 ystems engineering Software requirements involves properties of the system as a whole software hardware operational processes Computer systems are either: user-configured no explicit system requirements COTS? custom made all stakeholders participate in requirements
22 ifferent types of system nformation systems process information typically database access standard hardware RE: primarily software requirements Embedded systems software used as a controller special purpose hardware and OS RE: hardware and software Command and control systems combined information and embedded special purpose systems to aide decision making e.g. air traffic control, railway traffic control, military RE: software, hardware, operational processes
23 mergent properties non constuctive aspects of information systems follwing subsystem integration reliability maintainability performance usability security
24 eneral systems engineering ocesses stem ements eering Syst valida Architectural design System integration Requirements partitioning Sub-system development Software requirements engineering
25 he requirements document A text based document containing the services and functions the system should provide the constraints under which the system must operate overall properties (i.e. constraints on the system s emergent properties) definitions of other systems which the system must integrate with information about the application domain of the system, e.g. how to carry out particular types of computation constraints on the process used to develop the system
26 tandards No single standard exists, but several large organizations have proposed them DOD, IEEE One of the simplest is IEEE/ANSI (IEEE, 1993)
27 EE, 1993 Introduction. Purpose of the requirements document. Scope of the product. Definitions, acronyms and abbreviations. References. Overview of the remainder of the document General description. Product perspective. Product functions. User characteristics. General constraints. Assumptions and dependencies
28 EE, 1993 Specific requirements unctional, non functional, and interface requirements. Also external interfaces, performance requirements, logical database requirements, design constraints, system attributes, and quality characteristics Appendices Index
29 sers of the document System customers Specify the requirements and read them to check that they me their needs. They specify changes to the requirements. Managers Use the requirements document to plan a bid for the system development process. System engineers Use the requirements to understand what system is to be developed System test engineers Use the requirements to develop validation tests for the system System maintanence engineers Use the requirements to help understand the system and the relationship between its parts
30 riting requirements Natural language is often used Some common problems complex conditional statements are confusing terminology often not precise or inconsistent writers assume too much knowledge and leave out essential detail
31 essentials for requirements ocumentation writers Requirements are read more often than they are written Readers come from different backgrounds... do not leave out essential detail It takes a long time. Leave time to write, review, revise.
Requirements Engineering
Requirements Engineering An introduction to requirements engineering Gerald Kotonya and Ian Sommerville G. Kotonya and I. Sommerville 1998 Slide 1 Objectives To introduce the notion of system requirements
More informationRequirements Engineering. Objectives. System requirements. Types of requirements. FAQS about requirements. Requirements problems
Reqirements Engineering Objectives An introdction to reqirements Gerald Kotonya and Ian Sommerville To introdce the notion of system reqirements and the reqirements process. To explain how reqirements
More informationMathematics and Computing: Level 2 M253 Team working in distributed environments
Mathematics and Computing: Level 2 M253 Team working in distributed environments SR M253 Resource Sheet Specifying requirements 1 Overview Having spent some time identifying the context and scope of our
More informationRE Process. Lawrence Chung Department of Computer Science The University of Texas at Dallas
1 RE Process Lawrence Chung Department of Computer Science The University of Texas at Dallas 2 RE Process: What is a Process? Given input, transforms it into output Consist of a set of activities Process
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 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 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 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 informationFundamentals: Software Engineering. Objectives. Last lectures. Unit 2: Light Introduction to Requirements Engineering
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science University of Birmingham r.bahsoon@cs.bham.ac.uk Unit 2: Light Introduction to Requirements Engineering Dr R Bahsoon 1 Objectives
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 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 Engineering
Dr. Michael Eichberg Software Engineering Department of Computer Science Technische Universität Darmstadt Software Engineering Engineering The following slides are primarily based on the contents of the
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 informationSecurity Risk Management Domain Model
Lecture 2: Security Modelling Understanding security goals and secure business activities Dr. Raimundas Matulevičius email: rma@ut.ee 1" Security Risk Management Domain Model "2"" Goals and Questions What
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 information(Team Name) (Project Title) Software Design Document. Student Name (s):
(Team Name) (Project Title) Software Design Document Student Name (s): TABLE OF CONTENTS 1. INTRODUCTION 2 1.1Purpose 2 1.2Scope 2 1.3Overview 2 1.4Reference Material 2 1.5Definitions and Acronyms 2 2.
More information<<Subsystem>> Software Architecture Document
Ref Contract Number: Contractor: Copy SAD TEMPLATE of Software Architecture Document SAD Template Page 1 of 21 Software Architecture Document Prepared by: Title Name Signature
More information(c) Addison Wesley Chapter 3. ! Interviewing customers and domain experts. ! Questionnaires. ! Observation. ! Study of documents and software systems
MACIASZEK, L.A. (2001): Analysis and System Design. Developing Information Systems with UML, Addison Wesley elicitation Domain Expert Customer Chapter 3 Determination Domain Knowledge Business Analyst
More informationRequirement Specification Document Template
Abstract: This document outlines projects requirements for the . This is a controlled document and should be maintained in a configuration environment. Requirement Specification Document Template
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 informationSE351a: Software Project & Process Management. 11 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa
SE351a: Software Project & Process Management W4.1: Requirements Engineering 11 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa SE351 Roadmap Introduction to Software Project Management Project Management
More informationSOFT 423: Software Requirements
SOFT 423: Software Requirements Week 1 Class 3 Requirements Process SOFT 423 Winter 2015 1 Last Class What are Requirements Requirements Eng vs. System Analysis Requirements Eng vs. Design Classes of Custom
More informationSEG3201 Basics of the Requirements Process
SEG3201 Basics of the Requirements Process Based on material from: I Bray: An introduction to Requirements Engineering Gerald Kotonya and Ian Sommerville: Requirements Engineering Processes and Techniques,
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 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 informationIntroduction to Software Specifications and Data Flow Diagrams. Neelam Gupta The University of Arizona
Introduction to Software Specifications and Data Flow Diagrams Neelam Gupta The University of Arizona Specification A broad term that means definition Used at different stages of software development for
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 informationQuestionnaire Specification Database for Blaise Surveys
Questionnaire Specification Database for Blaise Surveys Lilia Filippenko, Valentina Grouverman, Joseph Nofziger, RTI International 1 Introduction Developing large scale, complex Computer Assisted Interview
More informationProject 3-I. System Requirements Specification Document
Project 3-I System Requirements Specification Document Interrogue Polling Company, Inc. Penn State Harrisburg COMP413W Fall 2007 Version 1.0 COMP413W Consulting Group Page 1 of 14 [This page intentionally
More informationPUTTING THE CUSTOMER FIRST: USER CENTERED DESIGN
PUTTING THE CUSTOMER FIRST: USER CENTERED DESIGN icidigital.com 1 Case Study DEFINE icidigital was chosen as a trusted creative partner to design a forward-thinking suite of sites for AICPA, one of the
More informationCh 4: Requirements Engineering. What are requirements?
Ch 4: Engineering What are? Functional and non-functional The software document specification engineering processes elicitation and analysis validation management The descriptions of what the system should
More informationSoftware Design Document (SDD) Template (summarized from IEEE STD 1016)
Software Design Document (SDD) Template (summarized from IEEE STD 1016) Software design is a process by which the software requirements are translated into a representation of software components, interfaces,
More informationLecture 5: Requirements Specifications
Lecture 5: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
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 informationConcepts of Usability. Usability Testing. Usability concept ISO/IS What is context? What is context? What is usability? How to measure it?
Concepts of Usability Usability Testing What is usability? How to measure it? Fang Chen ISO/IS 9241 Usability concept The extent to which a product can be used by specified users to achieve specified goals
More informationLecture 7 (3-April-2013)
SOFTWARE QUALITY ASSURANCE Lecture 7 (3-April-2013) Instructor: Mr. Natash Ali Mian Department of CS and IT Department of CS and IT The University of Lahore ` Switch off mobile phones during lectures,
More informationSoftware Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>
Software Requirements Specification for Version 1.0 approved Prepared by Software Requirements Specification for Page 2 Table of Contents Revision
More informationNEW TRAFFIC SOURCE Very affordable CHEAP! High quality!
NEW TRAFFIC SOURCE Very affordable CHEAP! High quality! LEGAL TERMS Disclaimer & Terms of Use The information contained in this material (including, but not limited to any manuals, CDs, recordings, MP3s
More informationUsing the Web in Your Teaching
Using the Web in Your Teaching November 16, 2001 Dirk Morrison Extension Division, University of Saskatchewan Workshop Outline What will we cover? Why use the Web for teaching and learning? Planning to
More informationSoftware Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created>
Software Requirements Specification for Version 1.0 approved Prepared by Copyright 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute
More informationOO Requirements to OO design. Csaba Veres Alan M. Davis (1995), Colorado
OO Requirements to OO design Csaba Veres Alan M. Davis (1995), Colorado Alan Davis? Guru? Academic and professional www.omni-vista.com? Controversial article on research into requirements engineering Requirements
More informationWhat are Embedded Systems? Lecture 1 Introduction to Embedded Systems & Software
What are Embedded Systems? 1 Lecture 1 Introduction to Embedded Systems & Software Roopa Rangaswami October 9, 2002 Embedded systems are computer systems that monitor, respond to, or control an external
More informationChapter 4 Requirements Elicitation
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 4 Requirements Elicitation Outline Today: Motivation: Software Lifecycle Requirements elicitation challenges Problem statement
More informationDelimited. Interfaced. Readable. Modifiable. Verifiable. Prioritized* Endorsed
15 quality goals for requirements Justified Correct Complete Consistent Unambiguous Feasible Abstract Traceable Delimited Interfaced Readable Modifiable Verifiable Prioritized* Endorsed Marked attributes
More informationResponse to the CCSDS s DAI Working Group s call for corrections to the OAIS Draft for Public Examination
Response to the CCSDS s DAI Working Group s call for corrections to the OAIS Draft for Public Examination Compiled on behalf of the members of the Digital Curation Centre and the Digital Preservation Coalition
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 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 informationBCS International Diploma in Consultancy Syllabus & Guidelines Version 1.2 December 2016
BCS International Diploma in Consultancy Syllabus & Guidelines Version 1.2 December 2016 This qualification is not regulated by the following United Kingdom Regulators - Ofqual, Qualification in Wales,
More informationHUMBOLDT COUNTY Website Accessibility Policy
SECTION: Information Technology ORIGINAL ISSUE DATE: 11/08/2016 REVISION DATE: 02/27/2018 10/16/2018 PAGE 1 OF 4 HUMBOLDT COUNTY Website Accessibility Policy I. PURPOSE The purpose of this policy is to
More informationATTENTION TO COME/ISE 491/492 STUDENT
ATTENTION TO COME/ISE 491/492 STUDENT 151 As a part of your requirement analysis section in your final report, you should write a requirement analysis document (RAD). The details of the document, and a
More informationCompTIA Project+ (2009 Edition) Certification Examination Objectives
CompTIA Project+ (2009 Edition) Certification Examination Objectives DRAFT INTRODUCTION The Project + examination is designed for business professionals involved with projects. This exam will certify that
More informationSMK SEKSYEN 5,WANGSAMAJU KUALA LUMPUR FORM
SMK SEKSYEN 5,WANGSAMAJU 53300 KUALA LUMPUR FORM 5 LEARNING AREA 4 MULTIMEDIA Ramadan, SMK Pekan 2007 MULTIMEDIA LESSON 21 MULTIMEDIA CONCEPTS DEFINITION OF MULTIMEDIA Multimedia has been used in many
More informationExample of Focus Group Discussion Guide (Caregiver)
Example of Focus Group Discussion Guide (Caregiver) MHealth Self-Management and Support System for Chronic and Complex Health Conditions (Phase 1-Development and Refinement) 1) Welcome, consent process,
More informationCS 160: Evaluation. Professor John Canny Spring /15/2006 1
CS 160: Evaluation Professor John Canny Spring 2006 2/15/2006 1 Outline User testing process Severity and Cost ratings Discount usability methods Heuristic evaluation HE vs. user testing 2/15/2006 2 Outline
More informationSome popular Operating Systems include Linux Operating System, Windows Operating System, VMS, OS/400, AIX, z/os, etc.
An Operating System (OS) is an interface between computer user and computer hardware. An operating system is software which performs all the basic tasks like file management, memory management, process
More informationCS 160: Evaluation. Outline. Outline. Iterative Design. Preparing for a User Test. User Test
CS 160: Evaluation Professor John Canny Spring 2006 2/15/2006 1 2/15/2006 2 Iterative Design Prototype low-fi paper, DENIM Design task analysis contextual inquiry scenarios sketching 2/15/2006 3 Evaluate
More informationUNIT-II REQUIREMENTS ANALYSIS AND SPECIFICATION
UNIT-II REQUIREMENTS ANALYSIS AND SPECIFICATION The for a system are the descriptions of what the system should do the services that it provides and the constraints on its operation. User are statements,
More informationStep-by-Step Localization Eva Müller
Step-by-Step Localization Eva Müller Questions, answers and procedures for a successful localization process Steps in localization projects range from what is to be localized, who performs the localization
More informationArchitecture of Business Systems Views and Viewpoints
Sandro Schwedler Wolfram Richter Architecture of Business Views and Viewpoints Lecture Outline Introduction (W) Lecture Overview Role of the Architect Views and Viewpoints Process of Software Architecting,
More informationSOFTWARE REQUIREMENT SPECIFICATION
SOFTWARE REQUIREMENT SPECIFICATION AIM The aim of the experiment is to prepare and document the Software Requirements Specification for the project Library Management System 1. INTRODUCTION 1.1 Purpose
More informationJapan s Common Vocabulary Policy. Takashi Wada Ministry of Economy, Trade and Industry May 2015
Japan s Common Vocabulary Policy Takashi Wada Ministry of Economy, Trade and Industry May 2015 WHY 1 Fragmentation of Japan s government IT system 26 thousand Administrative procedures 42.8% FTTH user
More informationTAP RETAIL CHANGE REQUESTS
TAP RETAIL CHANGE REQUESTS Project: TAP Phase One Release: 1.0 To DG MOVE, ERA, TAP Steering Committee Date: 13 May 2012 Author: Owner: Client: Document Ref: Ugo Dell Arciprete (Work Stream Leader) TAP
More informationSoftware Architecture
Software Architecture Does software architecture global design?, architect designer? Overview What is it, why bother? Architecture Design Viewpoints and view models Architectural styles Architecture asssessment
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 informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationDATA Act Information Model Schema (DAIMS) Architecture. U.S. Department of the Treasury
DATA Act Information Model Schema (DAIMS) Architecture U.S. Department of the Treasury September 22, 2017 Table of Contents 1. Introduction... 1 2. Conceptual Information Model... 2 3. Metadata... 4 4.
More informationStandard Setting and Revision Procedure
Better Cotton Initiative Standard Setting and Revision Procedure BCI-PRO-01 (V2-0) EN Title: Document reference code: Standard Setting and Revision Procedure BCI-PRO-01-V2 Approval : BCI Council, January
More informationINTERNATIONAL STANDARD
ISO/IEC 24775-1 INTERNATIONAL STANDARD Edition 1.0 2014-10 colour inside Information technology Storage management Part 1: Overview INTERNATIONAL ELECTROTECHNICAL COMMISSION PRICE CODE D ICS 35.200 ISBN
More informationKick-off Meeting DPIA Test phase
Kick-off Meeting DPIA Test phase Directorate General for European Commission Brussels, 05/03/2015 Content Welcome and Introduction Upcoming Data Protection Reform Commission Recommendation Test Phase of
More informationIntroduction to Service Availability Forum
Introduction to Service Availability Forum Sasu Tarkoma (sasu.tarkoma@cs.helsinki.fi) Seminar on High Availability and Timeliness in Linux University of Helsinki, Department of Computer Science Spring
More informationEE/CprE/SE 491 Senior Design I and Professionalism. Design Document
EE/CprE/SE 491 Senior Design I and Professionalism Design Document Joseph Zambreno Electrical and Computer Engineering Iowa State University www.ece.iastate.edu/~zambreno rcl.ece.iastate.edu Always design
More informationPart 5. Verification and Validation
Software Engineering Part 5. Verification and Validation - Verification and Validation - Software Testing Ver. 1.7 This lecture note is based on materials from Ian Sommerville 2006. Anyone can use this
More informationLATIHAN Identify the use of multimedia in various fields.
LATIHAN 4.1 1. Define multimedia. Multimedia is the presentation of information by using a combination of text, audio, graphic, video and animation. Multimedia has played an important role in other fields,
More informationReliability Coordinator Procedure PURPOSE... 1
No. RC0550 Restriction: Table of Contents PURPOSE... 1 1. RESPONSIBILITIES... 2 1.1.1. CAISO RC... 2 1.1.2. RC Working Groups... 2 1.1.3. Operationally Affected Parties... 2 1.1.4. RC Oversight Committee...
More informationThe software lifecycle and its documents
The software lifecycle and its documents Supplementary material for Software Architecture course B. Meyer, May 2006 Lifecycle models Origin: Royce, 1970, Waterfall model Scope: describe the set of processes
More informationSoftware Requirements Specification
Software Requirements Specification For livemechanic-clickmechanic.com Version 1.0 approved Prepared by Ngangbam Indrason Registration: 11401214 Section: K1421 Roll Number: RK1421A20 Lovely Professional
More information1 von 5 13/10/2005 17:44 high graphics home search browse about whatsnew submit sitemap Factors affecting the quality of an information source The purpose of this document is to explain the factors affecting
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 informationSOFTWARE ENGINEERING DECEMBER. Q2a. What are the key challenges being faced by software engineering?
Q2a. What are the key challenges being faced by software engineering? Ans 2a. The key challenges facing software engineering are: 1. Coping with legacy systems, coping with increasing diversity and coping
More informationThe Transaction Log under the Kyoto Protocol
Working Paper No. 9 (2003), Annex II Pre-sessional consultations on registries Bonn, Germany, 2 June 2003 The Transaction Log under the Kyoto Protocol Functional Specification Draft version Page
More informationWHAT IS SOFTWARE ARCHITECTURE?
WHAT IS SOFTWARE ARCHITECTURE? Chapter Outline What Software Architecture Is and What It Isn t Architectural Structures and Views Architectural Patterns What Makes a Good Architecture? Summary 1 What is
More informationRequirements Specification with the IEEE 830 Standard
Requirements Specification with the IEEE 830 Standard Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE 830-1998 Standard, Daniel
More informationOnline Marketing: Circle or Funnel?
Online Marketing: Circle or Funnel? Ruben Timmerman r.timmerman@searchresult.nl Please consult me before using or spreading anything from this presentation. Usually I m more then happy to approve any use
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 information3Lesson 3: Web Project Management Fundamentals Objectives
3Lesson 3: Web Project Management Fundamentals Objectives By the end of this lesson, you will be able to: 1.1.11: Determine site project implementation factors (includes stakeholder input, time frame,
More informationChapter 5 INTRODUCTION TO MOBILE AGENT
Chapter 5 INTRODUCTION TO MOBILE AGENT 135 Chapter 5 Introductions to Mobile Agent 5.1 Mobile agents What is an agent? In fact a software program is containing an intelligence to help users and take action
More informationBusiness Requirements Document (BRD) Template
Business Requirements Document (BRD) Template Following is a template for a business requirements document (BRD). The document includes many best practices in use today. Don t be limited by the template,
More informationAgency Guide for FedRAMP Authorizations
How to Functionally Reuse an Existing Authorization Version 1.0 August 5, 2015 Revision History Date Version Page(s) Description Author 08/05/2015 1.0 All Initial Publication FedRAMP PMO 06/06/2017 1.0
More informationInfrastructure and Asset Management. and Asset Management
Infrastructure and Asset Management 18/09/2015 Emad Elbeltagi 1 W elcome to Infrastructure and Asset Management 18/09/2015 Emad Elbeltagi 2 1 About Emad Elbeltagi Structure and delivery Assessment Course
More informationStudent Guide. Short: Electronic Facility Clearance System (e-fcl): A Review for Industrial Security Representatives. 10 minutes
Short: Electronic Facility Clearance System (e-fcl): A Review for Industrial Security Representatives Objective Estimated completion time Demonstrate knowledge of the e-fcl process 10 minutes Overview
More informationSOME TYPES AND USES OF DATA MODELS
3 SOME TYPES AND USES OF DATA MODELS CHAPTER OUTLINE 3.1 Different Types of Data Models 23 3.1.1 Physical Data Model 24 3.1.2 Logical Data Model 24 3.1.3 Conceptual Data Model 25 3.1.4 Canonical Data Model
More informationSoftware Design Document
SCSJ2203: Software Engineering Software Design Document Project Title Version 1.0 Printing Date Department and Faculty Prepared by: Revision Page a. Overview Describe the content
More informationGuide to Simple Network Design PCATS Recommendation, April 14, 2011
Guide to Simple Network Design PCATS Recommendation, April 14, 2011 Abstract This document provides guidance on simple network design for typical C-Store environments. In addition, this document provides
More informationSystems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, Fourth Edition Systems Analysis and Design in a Changing World, 4th Edition Learning Objectives Explain the purpose and various phases of the systems development
More informationUnit 1 Introduction to Software Engineering
Unit 1 Introduction to Software Engineering João M. Fernandes Universidade do Minho Portugal Contents 1. Software Engineering 2. Software Requirements 3. Software Design 2/50 Software Engineering Engineering
More informationToday. Lecture 17: Reality Mining. Last time
Today We will introduce the idea of a relational database, discuss its underlying data model and present a slightly simplified view of how to access its information Lecture 17: As with all new technologies
More informationMei Nagappan. How the programmer wrote it. How the project leader understood it. How the customer explained it. How the project leader understood it
Material and some slide content from: - Software Architecture: Foundations, Theory, and Practice - Elisa Baniassad - Reid Holmes How the customer explained it How the project leader understood it How the
More informationSoftware Requirements Specification
SCSJ2203: Software Engineering Software Requirements Specification Project Title Version 1.0 Printing Date Department and Faculty Prepared by: Revision Page a. Overview Describe
More informationFPA and Portfolio Counting
FPA and Portfolio Counting Size for Application Maintenance projects the easy way Christine Green CFPS EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS is an equal
More informationCS350 Lecture 2 Requirements Engineering. Doo-Hwan Bae
CS350 Lecture 2 Requirements Engineering Doo-Hwan Bae bae@se.kaist.ac.kr Contents Overview of Requirements Engineering OO Analysis: Domain modeling, Use-case, sequence, class Structured Analysis: Dataflow
More information