ETS170 Requirements Engineering

Relevanta dokument
Inför labb. Föreläsning 5 Funktionella krav forts Validering. Övningarna. Fortsättning. Christin Lindholm

Olika typer av krav. Funktionella krav (FR) Kvalitetskrav (NFR) Användbarhet. Olika typer av kvalitetskrav. ETS672 Requirements Engineering

Föreläsning 4: Marknadsdriven kravhantering. Funktionella krav. Olika typer av krav Funktionella krav (FR) Kvalitetskrav (NFR)

Isolda Purchase - EDI

RUP är en omfattande process, ett processramverk. RUP bör införas stegvis. RUP måste anpassas. till organisationen till projektet

Adding active and blended learning to an introductory mechanics course


Support Manual HoistLocatel Electronic Locks

Support for Artist Residencies

Workplan Food. Spring term 2016 Year 7. Name:

Information technology Open Document Format for Office Applications (OpenDocument) v1.0 (ISO/IEC 26300:2006, IDT) SWEDISH STANDARDS INSTITUTE

ETSN15 Kravhantering

FÖRBERED UNDERLAG FÖR BEDÖMNING SÅ HÄR

LARS. Ett e-bokningssystem för skoldatorer.

SWESIAQ Swedish Chapter of International Society of Indoor Air Quality and Climate

The present situation on the application of ICT in precision agriculture in Sweden

ETS672 Requirements Engineering L5: Validation

Immigration Studying. Studying - University. Stating that you want to enroll. Stating that you want to apply for a course.

EVALUATION OF ADVANCED BIOSTATISTICS COURSE, part I

Schenker Privpak AB Telefon VAT Nr. SE Schenker ABs ansvarsbestämmelser, identiska med Box 905 Faxnr Säte: Borås

Michael Q. Jones & Matt B. Pedersen University of Nevada Las Vegas

A metadata registry for Japanese construction field

Kursplan. MT1051 3D CAD Grundläggande. 7,5 högskolepoäng, Grundnivå 1. 3D-CAD Basic Course

The Swedish National Patient Overview (NPO)

Om oss DET PERFEKTA KOMPLEMENTET THE PERFECT COMPLETION 04 EN BINZ ÄR PRECIS SÅ BRA SOM DU FÖRVÄNTAR DIG A BINZ IS JUST AS GOOD AS YOU THINK 05

Examensarbete Introduk)on - Slutsatser Anne Håkansson annehak@kth.se Studierektor Examensarbeten ICT-skolan, KTH

Klicka här för att ändra format

Biblioteket.se. A library project, not a web project. Daniel Andersson. Biblioteket.se. New Communication Channels in Libraries Budapest Nov 19, 2007

CM FORUM. Introduktion till. Configuration Management (CM) / Konfigurationsledning. Tobias Ljungkvist

Preschool Kindergarten

Tomas Stålnacke Huvudprojektledare Project Manager Stadsomvandlingen City in transformation Kirunabostäder AB

The Finite Element Method, FHL064

Protokoll Föreningsutskottet

1. Unpack content of zip-file to temporary folder and double click Setup

- den bredaste guiden om Mallorca på svenska! -

Datasäkerhet och integritet

Design för användbarhet

SVENSK STANDARD SS-EN ISO 19108:2005/AC:2015

SVENSK STANDARD SS :2010

Introduktion ICAO-EASA.

3rd September 2014 Sonali Raut, CA, CISA DGM-Internal Audit, Voltas Ltd.


Eventuella felaktiga svar kanselerar motsvarande mängd rätta svar

Kvalitetsarbete I Landstinget i Kalmar län. 24 oktober 2007 Eva Arvidsson

Quality-Driven Process for Requirements Elicitation: The Case of Architecture Driving Requirements

Health café. Self help groups. Learning café. Focus on support to people with chronic diseases and their families

Innovation in the health sector through public procurement and regulation

Affärsmodellernas förändring inom handeln

Nya möjligheter med M3 Technology. Björn Svensson, Björn Torold

Accomodations at Anfasteröd Gårdsvik, Ljungskile

Ei R2015:15. Figure 1. An information model based on all-to-all communication. Source: Sweco. Kund = Customer. Elhandlare = Electricity supplier

Questionnaire for visa applicants Appendix A

Authentication Context QC Statement. Stefan Santesson, 3xA Security AB

Privacy Notice Ålö Group. Customers Integritetspolicy Sverige Privacy Notice UK, North America and International

PRODUCT MANAGEMENT. Klicka här för att ändra format. Klicka här för att ändra format på underrubrik i bakgrunden

ICRI International Child Resource Institute, Ghana November 2013 Prepared for Tolvskillingshjälpen

Translation Changes in Swedish EBSCOhost Interface

Schenker Privpak AB Telefon VAT Nr. SE Schenker ABs ansvarsbestämmelser, identiska med Box 905 Faxnr Säte: Borås

Vässa kraven och förbättra samarbetet med hjälp av Behaviour Driven Development Anna Fallqvist Eriksson

Metodprov för kontroll av svetsmutterförband Kontrollbestämmelse Method test for inspection of joints of weld nut Inspection specification

Swedish CEF Transport Secretariat. Connecting Europe Facility

EXTERNAL ASSESSMENT SAMPLE TASKS SWEDISH BREAKTHROUGH LSPSWEB/0Y09

Att fastställa krav. Annakarin Nyberg

Stad + Data = Makt. Kart/GIS-dag SamGIS Skåne 6 december 2017

Arbetsplatsträff 5 april, 2017 Workplace meeting April 5, 2017

Surfaces for sports areas Determination of vertical deformation. Golvmaterial Sportbeläggningar Bestämning av vertikal deformation

Vätebränsle. Namn: Rasmus Rynell. Klass: TE14A. Datum:

icore Solutions. All Rights Reserved.

Signatursida följer/signature page follows

Inkvarteringsstatistik. Göteborg & Co

Configuration Management

Boiler with heatpump / Värmepumpsberedare

Studieteknik för universitetet 2. Books in English and annat på svenska

BOENDEFORMENS BETYDELSE FÖR ASYLSÖKANDES INTEGRATION Lina Sandström

Exercise 1a: Requirements and Project Kick-off ETSA01 INGENJÖRSPROCESSEN 1 - METODIK VT15

The Academic Career Path - choices and chances ULRIKKE VOSS

Manhour analys EASA STI #17214

Semantic and Physical Modeling and Simulation of Multi-Domain Energy Systems: Gas Turbines and Electrical Power Networks

COPENHAGEN Environmentally Committed Accountants

Byggdokument Angivning av status. Construction documents Indication of status SWEDISH STANDARDS INSTITUTE

Taking Flight! Migrating to SAS 9.2!

Quick Start Guide Snabbguide

University of Nottingham ett internationellt campus med många inriktningar

3 rd October 2017

Grafisk teknik IMCDP IMCDP IMCDP. IMCDP(filter) Sasan Gooran (HT 2006) Assumptions:


Urban Runoff in Denser Environments. Tom Richman, ASLA, AICP

Custom-made software solutions for increased transport quality and creation of cargo specific lashing protocols.

RADIATION TEST REPORT. GAMMA: 30.45k, 59.05k, 118.8k/TM1019 Condition D

Materialplanering och styrning på grundnivå. 7,5 högskolepoäng

Datavetenskap. Beteendevetenskap MDI. Design

PFC and EMI filtering

Sara Skärhem Martin Jansson Dalarna Science Park

Viktig information för transmittrar med option /A1 Gold-Plated Diaphragm

Beijer Electronics AB 2000, MA00336A,

Grafisk teknik IMCDP. Sasan Gooran (HT 2006) Assumptions:

- den bredaste guiden om Mallorca på svenska!

SweLL & legal aspects. Elena Volodina

The reception Unit Adjunkten - for newly arrived pupils

Course evaluation SMD098, Lp2 2001

Transkript:

ETS170 Requirements Engineering Lecture 4: Specification, part 3: Special interfaces: Lau:5 Requirements in the life cycle: Lau: 7 Björn Regnell http://www.cs.lth.se/ets170/

Overview of styles for specifying functional requirements (Swedish terminology) Datakravstilar: Datamodell ( =E/R-diagr.) Dataordlista Reguljära uttryck Virtuella fönster Funktionella kravstilar: Kontextdiagram Händelse- & Funktionslistor Produktegenskapskrav Skärmbilder & Prototyper Uppgiftsbeskrivningar Egenskaper från uppgifter Uppgifter och stöd (Levande) Scenarier Högnivåuppgifter Användningsfall Uppgifter med data Dataflödesdiagram Standardkrav Krav på utvecklingsprocessen Funktionella detaljer: Enkla och sammansatta funktioner Tabeller & Beslutstabeller Textuella processbeskrivningar Tillståndsdiagram Övergångsmatriser Aktivitetsdiagram Klassdiagram Samarbetsdiagram Sekvensdiagram Speciella gränssnitt Rapporter Plattformskrav Produktintegration Tekniska gränssnitt

Special interfaces Summary Platform requirements Requirements on what the product shall run on now and in the future Dealing with existing and planned platforms Can be very complex and technically detailed depending on the product and contracting situation Technical interfaces Requirements on interactions with other systems Many different ways to specify technical interfaces Performance and capacity requirements can be very difficult to understand and validate Prototype and test the communication early Note that the recently recent research field of software product line engineering is not covered by Lauesen.

Variability modelling in software product lines with reqt

Fig 5.2 Platform requirements We have a platform R1: Product shall run on Pentíum PC s with 128 MB. Many older PC s still used, so tasks 2.1 to 2.5 must be supported on 80486 with 64 MB. R2: Our IT staff have expertice in Oracle. Product must use same database platform. R3: Product shall run on MS Windows release xx.yy. Supplier shall for 3 years port his product to new releases within months from release date. We want a new platform anyway R4: Customer expects to switch to client-server running OS zz. Supplier shall specify server memory and server speed needed to obtain capacity and response time for Rxx. We want software and hardware (maybe) R5: Supplier shall deliver hardware + software. Supplier shall upgrade if capacity becomes inadequate for the load specified in xx. R6: Product shall run on Pentium PC s with 128 MB. As an option, total delivery may include the PC s and hardware support. From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Fig 5.3A Who can integrate? Customer??? Customer s IT dept Hotel system Account system? Main contractor Product supplier?

Fig 5.4 Main contractor Embedded 3rd party product DB sys Hotel system Account system Visible 3rd party product Main contractor Telephone system Joint design work The optimal split. Exists? Willing? Cost vs. market Sub-contractor From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Fig 7.3 Comparing proposals Hotel system evaluation Proposals 0 (bad) - 5 (excellent) A B C Normal requirements 3 4 5 Weakest requirements 3 2 0 Total product points 6 6 5 Understand our problem 1 3 5 Track record 4 1 4 Solidity 5 4 4 Total points 16 14 18 Base price 25 20 15 Option 1: Floor map 10 6 - Option 2:... 8-8 From the buyers perspective Ideal evaluation Proposals A B C Business value (NPV) 100 100 90 Supplier s price 25 20 15 Internal investment costs 30 25 10 Net value 45 55 65 Perhaps better to do more systematic prioritization? From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Fig 7.4 Customer s rating Task: 1.2 Checkin Proposal B Purpose: Give guest a room... Rating: 3 Frequency:... Sub-tasks: 1. Find room. Problem: Guest wants neighbor rooms; price bargain. 2. Record guest as checked in. 3. Deliver key. Problem: Guests forget to return the key; want two keys. Variants: 1a. Guest has booked in advance. Problem: Guest identification fuzzy. Assessment: Floor map developed as an option. Very convenient display of bargain prices. If guest is not booked, cumbersome to switch to that task. No support for electronic keys. Tests show no tolerance for spelling errors. Very long search time for names. From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Fig 7.5 Supplier s proposal Task: 1.2 Checkin Purpose: Give guest a room... Frequency:... Sub-tasks: 1. Find room. Problem: Guest wants neighboor rooms; price bargain. 2. Record guest as checked in. 3. Deliver key. Problem: Guests forget to return the key; want two keys. Variants: 1a. Guest has booked in advance. Problem: Guest identification fuzzy. Proposal: Floor map developed as an option. See outline on page xx. See room screen p. yy. See guest screen and check-in screen, p. zz We provide no support for electronic keys. Planned for release 5 in 1.5 years. User may search for any field using wildcarding. From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

High risk requirements Quality("performance") has Spec("The response time shall be at most 0.5 seconds on average when moving from one screen to another. The response time shall never be above 2 seconds.") Suppler A: We didn't notice any problems. Our response time is of that magnitude. Supplier B: We don't care. We'll find a way out later. Suppler C: We state as an assumption that 95% of the cases will be sufficient. Supplier D: We fulfill the requirement although it will be expensive. Supplier E: We tell the customer what it would cost and why, and then offer a reasonable alternative. Eventually, we offer the full solution as an expensive option. [Lauesen: 7.5, p. 310]

Fig 5.5 Technical interfaces Hotel system Account system Communication channel Physical channel: File, TCP/IP, object calls... Message formats: Data descr, call params Protocol: State diagram, sequence diagram formal data descr, SDL... Semantics: about what? E/R, tasks, activity diagrams Verify early: Functional prototypes From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Fig 7. Requirements in product life cycle Inception Elicitation Formulation Checking Tender Writing proposal Design & program Contract Comparing proposals Next release Accept test Reqs management & release planning

Fig 7.6 Design and program R1: System shall store data according to this data model... R2: Product shall have screen pictures and menus as shown in... R3: Product shall record that a room is under repair... R4: Product shall support check-in according to task description... R5: At most 1 of 5 novices shall have critical usability problems during check-in. R6: Storing a booking shall take less than 1 second on average. R7: Pre-calculation of repair orders shall hit within 5% of actual costs. How to trace and verify these during development? From: Soren Lauesen: Software Requirements Pearson / Addison-Wesley 2002

Spårbarhet (Traceability) Ändringar i intressenternas behov, önskemål och tekniska antaganden kan kräva radikal omvärdering av kravens relevans. Ansvar för kravuppfyllelse behöver kopplas till systemkomponenter så att ansvarighet och påverkansanalys kan utrönas Framåt till krav Requirements document Req A1: Printing Framåt från krav package samples.simple; Källa Bakåt från krav Dependecy Req F8: Color Bakåt till krav public class Hello1 { public void printhello() { System.out.println( "Hello!" ); } } Design/ Kod/Test Hur intressenterna medverkat till kraven är viktig information vid validering. Kravuppfyllelse behöver verifieras och design utan krav ( gold-plating ) behöver undvikas.

To Do Read Lau: 5, 7 Exercise 3: Functional requirements (Lau:2-4) Lab 1: mandatory preparations (see tutorial on reqt) Start plan/work on bonus chance exam problem proposals: Follow instructions on slides from Lecture 2! Deadline: W4 & W6 Wednesday @ 23.59 PMv2 deadline was today 0900. Upcoming project deadlines: W4: meeting with project supervisor: discuss scope & plan W6: Release R2 Mon 0900 with draft release plan & check list W6: Validation Report Fri 0900 (see course program guidelines)