Slides for: Software requirements - Styles and techniques Soren Lauesen 2. Data requirement styles January 2007 Slides covered by the compendium are omitted.

Slides:



Advertisements
Similar presentations
More Diagramming & Practice with Relationship Modeling
Advertisements

1. Show tasks with data for cheking. Design search windows Task:1.2 Checkin Start:A guest arrives. Sub-tasks:Virtual windows: 1.Find room.Rooms. Crit:
Anskaffelse og kravspecifikation UID16_Datamodels.
Software requirements 3. Functional requirement styles
Pennsylvania’s Voter ID Law
Anskaffelse og kravspecifikation SR9_Checking. SR9: Checking and validation Kilder SR: Soren Lauesen: Software requirements - Styles and techniques. Addison-Wesley,
Hotel Billing Instructions
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Slides for User interface design A software engineering perspective Soren Lauesen 6. Virtual windows design August 2006 © 2005, Pearson Education retains.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 1- 1.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 2- 1.
Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.
Table design screen Field name Data type Field size Other properties.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 9- 1.
Plancher til Anskaffelse og kravspecifikation, Forår 2007 Lauesen: Software requirements - Styles and techniques 4. Functional details Plancherne stammer.
Task Descriptions as Functional Requirements Soren Lauesen
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Anskaffelse og kravspecifikation SR4_FuncDetail. Russisk MIG.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 11 Object, Object- Relational, and XML: Concepts, Models, Languages,
Plancher til Anskaffelse og kravspecifikation, Forår 2007 Lauesen: Software requirements - Styles and techniques 9. Checking and validation De fleste af.
Anskaffelse og kravspecifikation SR3_Functions - undtagen tasks.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Table design screen Field name Data type Field size Other properties.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
Slides for: Software requirements - Styles and techniques Soren Lauesen 3. Functional requirement styles January 2007 Slides covered by the compendium.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide
T-Stats Online information system Immediate results Useful for both you and Cotswolds.
C C R e c f o r T R A M S for Windows. O v e r v i e w The purpose of the CC Rec program is for a travel agency to reconcile credit card charges with.
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Entity Relationship Modeling
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Slides for Software requirements Styles and techniques Soren Lauesen 9. Checking and validation August 2006 © 2002, Pearson Education retains the copyright.
IS550: Software requirements engineering
Florida Information Protection Act of 2014 (FIPA).
TradeMeSoft Hotel Welcome to Hotel Management Software Login Module: The secured Login screen enables you to authorize menu level accessibility of the.
Slides for User interface design A software engineering perspective Soren Lauesen 12. User documentation and support August 2006 © 2005, Pearson Education.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Limits.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling for the.
Slides for User interface design A software engineering perspective Soren Lauesen 7. Function design August 2006 © 2005, Pearson Education retains the.
Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.
Slides for User interface design A software engineering perspective Soren Lauesen 9. Reflections on user interface design August 2006 © 2005, Pearson Education.
Slides for User interface design A software engineering perspective Soren Lauesen 2. Prototyping and iterative design August 2006 © 2005, Pearson Education.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 11.5 Lines and Curves in Space.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 1 Functions.
CSE 3345 User interface design A software engineering perspective Chapter 6: Virtual Windows Design © 2005, Pearson Education retains the copyright to.
User interface design A software engineering perspective Soren Lauesen Slides for Chapter 1 November 2004 © 2005, Pearson Education retains the copyright.
CSC207 – Software Design Final Preparation. Structure of Exam Descriptive Qs. –5 each 4 marks Code understanding –1 for 10 marks Analysis / Implementation.
Chapter 7, Section 2. Revenue Management Increase Revenue by: Managing the number of rooms filed Managing the number of discounts offered Booking guests.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
IS550: Software requirements engineering Dr. Azeddine Chikh 5. Special interfaces - combined styles.
Slides for User interface design A software engineering perspective Soren Lauesen 13. More on usability testing August 2006 © 2005, Pearson Education retains.
Unit 3 Assignment 1 p2 Daniel Russell. How information is managed To begin with all of the hotels systems what deal with customers bookings and all that.
Anskaffelse og kravspecifikation SR4_FuncDetail. Russisk MIG.
Anskaffelse og kravspecifikation
A software engineering perspective
Anskaffelse og kravspecifikation
Chapter 9 Domain Models.
Florida Information Protection Act of 2014 (FIPA)
Software acquisition and requirements SR3_Functions - except tasks
Florida Information Protection Act of 2014 (FIPA)
A software engineering perspective
A software engineering perspective The Virtual Window method
Presentation transcript:

Slides for: Software requirements - Styles and techniques Soren Lauesen 2. Data requirement styles January 2007 Slides covered by the compendium are omitted © 2002, Pearson Education retains the copyright to the slides, but allows restricted copying for teaching purposes only. It is a condition that the source and copyright notice is preserved on all the material.

Fig 2.2A Data model R2: The system shall store the following data: Stay Room State Room Service Type date, #persons, state (booked|occupied|repair) name, address1, address2, address3, passport room#, #beds, type price1, price2 name, price date, count Guest stay#, paymethod, employee Stays Guests One-to-many (1:m) Each guest connected to zero or more stays Each stay connected to one guest record From: Soren Lauesen: Software Requirements © Pearson / Addison-Wesley 2002

D1:Class: Guest [Notes a, b... refer to guidelines] The guest is the person or company who has to pay the bill. A person has one or more stay records. A company may have none [b, c]. “Customer” is a synonym for guest, but in the database we only use “guest” [a]. The persons staying in the rooms are also called guests, but are not guests in database terms [a]. Examples a.A guest who stays one night. b.A company with employees staying now and then, each of them with his own stay record where his name is recorded [d]. c.A guest with several rooms within the same stay. Attributes 1. name:Text, 50 chars [h] 2. passport:Text, 16 chars [h] Attribute missing in data model Recorded for guests who are obviously foreigners [f, i]. Used for police reports in case the guest doesn’t pay [g]... The name stated by the guest [f]. For companies the official name since the bill is sent there [g]. Longer names exist, but better truncate at registration time than at print out time [g, j]. Fig 2.3 Data dictionary

(Fig 2.4A) Data expressions Notation with plus as concatenator booking request = guest data + period + room type guest data = guest name + address + paymethod + [passport number] passport number = letter + {digit}*8 room state = { free | booked | occupied | repair } account data = transfer + {account record}* + done XML John Simpson Westbank Tce... From: Soren Lauesen: Software Requirements © Pearson / Addison-Wesley 2002

Fig 2.5 Virtual Windows R1:The product shall store data corresponding to the following virtual windows: Rooms7/88/89/810/8 11DoubleBath800600OB 12SingleToil600OOBB 13DoubleToil600500BBB Service charges Breakf. rest.40 Breakf. room60... Stay#: 714 Guest Name:John Simpson Address:456 Orange Grove Victoria 3745 Payment:Visa Item#pers 7/8Room 12, sgl1600 8/8Breakf. rest140 8/8Room 11, dbl2800 9/8Breakf. room2120 9/8Room 11, dbl2800 Breakfast9/8In R#restroom From: Soren Lauesen: Software Requirements © Pearson / Addison-Wesley 2002 R2:The final screens shall look like the virtual windows ??

(Fig 2.5B) Existing screens as data requirements R1:The product shall store data corresponding to the existing screens: