Problems and Frames IV Heuristics. Heuristics? Serving or helping to find out or discover; Guidelines; But connotations of trial and error.

Slides:



Advertisements
Similar presentations
VSMC MIMO: A Spectral Efficient Scheme for Cooperative Relay in Cognitive Radio Networks 1.
Advertisements

Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
Systems Analysis and Design 9th Edition
Introduction to Software Engineering Dr. Basem Alkazemi
Input/Output Management and Disk Scheduling
Problem Frames 8 - Variant frames. Variants Model Operator Description Connection Control.
Model Domains and Real Worlds Book: Problem Frames: Analyzing and structuring software development problems Author: Michael Jackson Presenter: Ryan Waggoner.
1 Objectives To introduces the concept of software Design. To introduce the concept of Object- Oriented Design (OOD). To Define various aspects about object.
1 Institute for Software Research, International Methods of Software Development Problem Frames 1 (This lecture is largely based on material graciously.
Reza Gorgan Mohammadi AmirKabir University of Technology, Department of Computer Engineering & Information Technology, Intelligent.
IMSE Week 18 White Box or Structural Testing Reading:Sommerville (4th edition) ch 22 orPressman (4th edition) ch 16.
Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap The Meaning Of Requirements.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 91 Formal Specification l Techniques for the unambiguous specification of software.
Problem Frames 10 & 111 Decomposition and Composition Problem Frames: Ch. 10,11.
7M822 Software Requirements A Use Case Approach 14 September 2010.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 4.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 10 Slide 1 Formal Specification.
User interface design. Recap User Interface GUI Characteristics (Windows, Icons, Menus, Pointing, Graphics) User Centered Design User Interface Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
Ivan Marsic Rutgers University LECTURE 12: Problem Frames Part I: Decomposition.
Chapter 7 Structuring System Process Requirements
UW CSE 503 ▪ Software Engineering ▪ Spring 2004 ▪ Rob DeLine1 CSE 503 – Software Engineering Lecture 2: Jackson Problem Frames Rob DeLine 31 Mar 2004 Thanks.
WEBINAR SERIES: ACCESSIBLE INTERACTIVE DOCUMENTS Week 3: Accessible Web Forms Norman Coombs
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
Dr. Pedro Mejia Alvarez Software Testing Slide 1 Software Testing: Building Test Cases.
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Problem Analysis and Structure II Multi-frame problems.
Data and Process Modeling
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 9 Slide 1 Formal Specification l Techniques for the unambiguous specification of software.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
October 2002J. B. Wordsworth: J2ISDPPS1 Information Systems Development Problem Frames: Problems and Subproblems.
-0- Problem Frames Project - #3 Problem Frames analysis PathFinder - Hyundai team Wangbong Lee, Jihye Eom, Youngseok Oh, Ilseok Suh Oct
Problem Analysis and Structure Models and Frames.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor.
Functional Modeling – Requirement Patterns (Problem Frames)
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
TELE202 Lecture 5 Packet switching in WAN 1 Lecturer Dr Z. Huang Overview ¥Last Lectures »C programming »Source: ¥This Lecture »Packet switching in Wide.
Input & Output In Java. Input & Output It is very complicated for a computer to show how information is processed. Although a computer is very good at.
WXGE6103 Software Engineering Process and Practice Formal Specification.
1 Institute for Software Research, International Methods of Software Development Problem Frames 2 (This lecture is largely based on material graciously.
Selected Topics in Software Engineering - Distributed Software Development.
Analysis Modeling. Function Modeling & Information Flow  Information is transformed as it flows through a computer-based system. The system accepts input.
Requirements validation Csaba Veres. What is it? Validation is the process of checking the requirements document for –completeness –consistency –accuracy.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
Requirements Engineering Methods for Requirements Engineering Lecture-30.
Math – What is a Function? 1. 2 input output function.
Finite Element Analysis
Problem Frames 7 - Model domains and real worlds.
HCI Meeting 23 Thurs, November 18. Looking Ahead Tuesday, 11/23Exam Reprise due Tuesday, 11/30 Thursday, 12/2Research Paper due Tuesday, 12/7Research.
Net Flow Network Protocol Presented By : Arslan Qamar.
RESPONSE TIME CS3xx3 Human Computer Interaction. Response Time [Deborah J. Mayhew] Task Time = System Response Time + System Display Rate + User Scan/Read.
Modern Systems Analysis and Design Fifth Edition
Systems Analysis and Design 8th Edition
Problems and Frames III Recap and More Concepts. Definition “A problem frame is a kind of pattern. It define an intuitively identifiable problem in terms.
5 February 2016M253 Team working in distributed environments 1.
Object and Class Structuring Chapter 9 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
1/10 Problem Frame Analysis Eunyoung Cho Kyu Hou Minho Jeung Heejoon Jung Oct. 25, 2005.
PHYSICS – Digital electronics. LEARNING OBJECTIVES Core Supplement Explain and use the terms analogue and digital in terms of continuous variation and.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
1 Ivan Marsic Rutgers University LECTURE 13: Problem Frames Part II: Modeling & Recombination.
Formal Specification.
Requirements Engineering (continued)
Basic Filters: Basic Concepts
Hierarchical Architecture
Plan of the talk Basic Specification blocks
DFD Process & Examples.
Presentation transcript:

Problems and Frames IV Heuristics

Heuristics? Serving or helping to find out or discover; Guidelines; But connotations of trial and error.

Heuristics Principal steps: –Identify the core problem –Identify the ancillary problems –Standard decompositions of sub problems –Identify concerns and difficulties

More heuristics Different tempi More than two moods Complex domain or requirement Modelling the user

Different tempi When one part of your problem is in a slow tempo and one in a fast tempo, treat them as different sub problems. Look at Tennis Court Lights handout What are the different tempi?

More than two moods Every frame has at least 1 description (of domain properties) in the indicative mood And at least two (req. and spec.) in the optative mood. Sometimes you need 3 moods which indicates presence of at least two subproblems Look at Air Traffic Control

Complex domain or environment In each basic frame a clear expectation of relative complexities of the domains and requirement complexity –Req. Beh. Frame: controlled domain may be complex, but you expect the requirement to be satisfiable by simple control law. –Commanded Beh. Frame: Controlled domain complex, but controller simple.

Continued –Info. Display Frame: RW complex, display domain quite simple. Req. = simple relationship between req and specification phenomena of RW –Workpieces: w/pieces may be complex, user domain simple –Transformation: inputs & outputs of roughly equal complexity. I/O relation satisfiable by traversal of both domains

Continued An unusually complex domain indicates a possible further decomposition Package router: core problem was Required Behaviour. –Complexity = destinations not available to sensors, so introduce a model domain = new subproblem

Modelling user In workpieces frame, user domain is unstructured stream of commands Where user domain is of interest for its own sake, this indicates a subproblem –If we need to know who edited a workpiece, we need a model of each user to record individual editing activities. This is a separate problem

Exercises What are the different tempi in the Home Heating Control problem? What are the moods in the Package Router problem? What are the subproblems in the University Administration system?