CC 2007, 2011 attribution - R.B. Allen Tasks and Activities.

Slides:



Advertisements
Similar presentations
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Chapter 1 Object Oriented Analysis and Design. UML, Patterns, and Object-Oriented Analysis and Design  The essential skills for the creation of well-designed,
Object-Oriented Analysis and Design
Chapter 1 Object-Oriented System Development
Introduction To System Analysis and Design
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
CS 425/625 Software Engineering System Models
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Traditional Approach to Requirements Data Flow Diagram (DFD)
USE Case Model.
Software Engineering 2003 Jyrki Nummenmaa 1 USE CASES In this lecture: Use cases - What are use cases? - Why to use use cases? - How to write.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Investigating System Requirements
Chapter 10 Information Systems Analysis and Design
Introduction To System Analysis and Design
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 11 Analysis Concepts and Principles
Approaching a Problem Where do we start? How do we proceed?
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Object-Oriented Analysis and Design Fall 2009.
UML-1 3. Capturing Requirements and Use Case Model.
UML-1 8. Capturing Requirements and Use Case Model.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 7 The Object-Oriented Approach to Requirements.
Summary of Task Analysis, social aspects, and alternative approaches: Chapters 9, 12, 13, (15) 16, A2 IST Olivier Georgeon and Frank Ritter 23 April.
Systems Analysis and Design in a Changing World, Fourth Edition
Unit-3 Identifying use cases Object Analysis Classification
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Summary of Task Analysis, social aspects, alternative approaches IST Olivier Georgeon April 27 th
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
 Problem solving involves a number of well- defined steps, which are as follows:  Define the problem.  Analyze the problem.  Identify and evaluate.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Basic Characteristics of Object-Oriented Systems
Object Oriented Analysis & Design By Rashid Mahmood.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
OCR A Level F453: High level languages Programming techniques a. identify a variety of programming paradigms (low-level, object- oriented,
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Abstract descriptions of systems whose requirements are being analysed
Object-Oriented Analysis
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
Presentation transcript:

CC 2007, 2011 attribution - R.B. Allen Tasks and Activities

CC 2007, 2011 attribution - R.B. Allen Using Information in Tasks Information is integral to completing tasks. The simplest model is to: –Find relevant information –Use that information to make a decision –Implement that decision We call this the Look-Decide-Do Model

CC 2007, 2011 attribution - R.B. Allen Information in Problem Solving Select Source Examine ResultsArticulate Problem Define Problem Extract Information Information access and use can be modeled in the context of problem solving.

CC 2007, 2011 attribution - R.B. Allen Creating Information Artifacts in Tasks External Information Resources Developer Artifact being created In many tasks, the task involves creating an information artifact. That is often an iterative process.

CC 2007, 2011 attribution - R.B. Allen Look: Tasks and Information Information is integral for tasks Role of Information in Tasks Look-Decide-Do More complex models are possible

CC 2007, 2011 attribution - R.B. Allen Information Needs When people ask a question, sometimes their true information needs are not obvious. –They may not know, or they may not want to admit, their own situation. –They may not know how to describe their situation We might try to find out more about what they are thinking with an reference interview.

CC 2007, 2011 attribution - R.B. Allen Complex Questions Complex questions still cant be answered by a search engine. Some of those complex questions can be decomposed into parts, each of which can be answered easily. Some other questions are so complex that they need to extended analysis and modeling.

CC 2007, 2011 attribution - R.B. Allen Relevance An information system should give user relevant information However, determining exactly what document is relevant can get complex –It depends on the content Is it on topic? –It depends on the task Is it trustworthy? –It depend on the user What have they already looked at? What languages do they understand? Is relevance all-or-none? Or, can there be partial relevance?

CC 2007, 2011 attribution - R.B. Allen How do we Measure Relevance? In order to evaluate the performance of information retrieval systems, we need to measure relevance. Usually the best we can do is to have an expert make ratings of the pertinence.

CC 2007, 2011 attribution - R.B. Allen Precision and Recall RelevantNot Relevant Retrieved Not Retrieved Hit False Alarm MissCorrect Rejection

CC 2007, 2011 attribution - R.B. Allen Precision and Recall (Contd) a P = (a+b) R = a (a+c) RelevantNot Relevant Retrieved Not Retrieved a b cd P = Hits + False Alarms Hits R = Hits Hits + Misses

CC 2007, 2011 attribution - R.B. Allen Precision and Recall (Contd) RelevantNot Relevant Retrieved Not Retrieved P = = (4+6) R = = (4+1)

CC 2007, 2011 attribution - R.B. Allen Decision Support Systems (DSS) Typically, a DSS is provides a set analysis tools to model a complex scenario such as financial projections or environmental impact.

CC 2007, 2011 attribution - R.B. Allen Group Decision Support Systems (GDSS) Group decisions support systems can be though of a multi-user DSS systems though they may emphasize support of group discussion and interaction more than providing complex analysis tools. Group interaction might range from brainstorming to Delphi Analysis.

CC 2007, 2011 attribution - R.B. Allen Making Decisions In the simple Look-Decide-Do Model, once information has been collected, we move to making a decision. Decision making can involve either informal or formal methods. A gut reaction would be informal Following a Decision Tree would be a formal method.

CC 2007, 2011 attribution - R.B. Allen Decision Trees Minimum systolic blood pressure > 93 yes no yes no Age > 62.5 Sinus Tachycardia Present LOW HIGH Rules for determining whether a patient has high risk for a heart attack.

CC 2007, 2011 attribution - R.B. Allen Game Theory for Multi-person Decisions Game Theory describes how a person might make evaluate alternatives in a multi-person task. Players may have different payoffs. The Prisoners Dilemma is a famous example. There are two prisoners who committed a crime together. They can go free (+3) if neither confesses, but if one confesses and the other doesnt they may get different penalties (-5/-1). What will they do? A Talks B Not Talk B Talks 5/5 -1/5 -5/-1-3/-3 A Not Talk

CC 2007, 2011 attribution - R.B. Allen Problem Solving Find a course of action to accomplish a goal. There are different level of problem solving –Relatively simple problems, such as arithmetic can be decomposed into part each of which can be easily solved. –More complex problems ma

CC 2007, 2011 attribution - R.B. Allen Planning Two levels of planning –Strategic planning –Scheduling Incorporating uncertainty in planning Even with careful planning there can be unexpected events and failures. In those cases, we can use: –Bricolage and Improvisation

CC 2007, 2011 attribution - R.B. Allen State Machines Several formal models have been developed for describing processes. The simplest of these are state machines. These describe activities as a sequence of states. In this representation, the activity must be in one of several states. The state machine is describes the transitions between states.

CC 2007, 2011 attribution - R.B. Allen System Analysis We want to better understand complex systems such as a large business. –One principle is to follow the data flow. This makes us emphasize the procedures. In other cases, we may want to build a complex system for scratch. In that case, we might use object-oriented design. Object- Oriented design follows representations which are also embodied in the Object- Oriented Data Model.

CC 2007, 2011 attribution - R.B. Allen Object-Oriented Data Model The OO model extends the ER model. The Classes have: –Methods Specific procedures associated with the data in a class. –Inheritance There can be a hierarchy of classes and attributes and methods can be inherited.

CC 2007, 2011 attribution - R.B. Allen Unified Modeling Language (UML) UML combines several types of models for modeling different aspects of systems. –Sequence Diagrams –Activity Diagrams –Use Case Diagrams –Statechart Diagrams Many applications including system analysis and object-oriented program development.