G&W Preface Software Specification Lecture 4

Slides:



Advertisements
Similar presentations
The Pragmatic Programmer I. About the textbook The Pragmatic Programmer is full of helpful suggestions for surviving programming It’s also enjoyably written.
Advertisements

Software Engineering Session 14 INFM 603. Software Software represents an aspect of reality –Input and output represent the state of the world –Software.
You could spend years and years figuring out how to take three steps at once. Or you could simply take one step, and then the next, and then the next.
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
SWE Introduction to Software Engineering
CSC 402 Requirements Engineering 1. 2 Problem Definition Requirements Definition informal statement of need for system natural language statement of what.
Lecture 2 Teams Principles What makes a good project Project Definition Project Plan.
CS 235: User Interface Design February 17 Class Meeting Department of Computer Science San Jose State University Spring 2015 Instructor: Ron Mak
Introduction to Engineering and Urban Planning How to be a Successful Engineer.
Chapter 4 – Requirements Engineering
Agile Modeling Theory. 2 Agile Modeling (AM) AM is a chaordic, practices-based process for modeling and documentation AM is a collection of practices.
Valentin Razmov, CSE403, Sp'05 CSE403 Section 1: The Fate of Software Projects Learning = Practice + Feedback Desirable Qualities in Teammates Team-Building.
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering Foundations.
Requirements and Specifications Prepared by Stephen M. Thebaut, Ph.D. University of Florida Software Testing and Verification Lecture 3.
CS251 – Software Engineering Lecture 9: Software Design Slides by Mohammad El-Ramly, PhD
CS 174: Web Programming November 25 Class Meeting Department of Computer Science San Jose State University Fall 2015 Instructor: Ron Mak
Requirements and Specifications Prepared by Stephen M. Thebaut, Ph.D. University of Florida Software Testing and Verification Lecture 3.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Software Engineering Session 12 INFM 603. Software Software represents an aspect of reality –Input and output represent the state of the world –Software.
A Design Process © 2012 Project Lead The Way, Inc.Introduction to Engineering Design.
Introduction to CSCI 1311 Dr. Mark C. Lewis
Problem Solving Methodology 1
G&W Chapter 5: Starting Points Software Specification Lecture 12
End to End Testing– Are we doing too Much?
G&W Chapter 22: Test Cases Software Specification Lecture 29
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Project Points Software Specification Lecture 8
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Requirements Analysis and Specification
Quality Quality is “a characteristic or attribute of something.”
Software Quality Engineering CS- 449
Critical Thinking.
Chapter 1 Introduction.
Requirements and Specifications
G&W Chapter 12: The Project’s Name Software Specification Lecture 19
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 24: Making Agreements Software Specification Lecture 31
G&W Chapter 17: Preferences Software Specification Lecture 24
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Lecture # 3 Software Development Project Management
Thebaut’s Guaranteed Method Software Specification Lecture 5
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 19: Ambiguity Metrics Software Specification Lecture 26
G&W Chapter 25: Ending Software Specification Lecture 32
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 16: Constraints Software Specification Lecture 23
G&W Chapter 20: Technical Reviews Software Specification Lecture 27
Notetaking Skills.
Axiomatic Verification I
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 11: Software Specification Lecture 18
Krug Chapter 2 How We Really Use the Web and Web Site Design
An Introduction to Software Engineering
G&W Chapter 14: Functions Software Specification Lecture 21
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Chemistry.
Getting Along With Others
G&W Chapter 15: Attributes Software Specification Lecture 22
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Project management Initiative & Self Learning Confidence in leadership
5 WHY A method for rapidly determining the root cause of a problem
System Development Methods
Presentation transcript:

G&W Preface Software Specification Lecture 4 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Software Specification: G&W Preface Gause & Weinberg’s book “...is about the requirements process – the part of development in which people attempt to discover what is desired.” “desired” or “needed”? Determining who the “people” are is a major part of the process. Why “attempt to discover” instead of just “discover”? We don’t know how to figure out what is NEEDED, but by clarifying DESIRES, people sometimes clarify what they really need and what they really don’t need. One reason desires can be complex: they come from many people. When creating a product to meet our personal desires (garden, bookcase), no explicit requirements process in needed: we simply build something, look at it, and make adjustments until we are satisfied. (cf. agile development) Why “attempt”? Software development (and RE) is not an exact discipline... Software Specification: G&W Preface

Software Specification: G&W Preface “If people don’t know what they want, no development process – no matter how exact, how clever, or how efficient – will satisfy them.” “...we do requirements work...(in order NOT to build) systems that people don’t want.” “Anything not worth doing is not worth doing well." In other words… It’s a waste of time to build an (efficient, robust, user-friendly, reliable, ...) system that nobody wanted in the first place.” Software Specification: G&W Preface

Software Specification: G&W Preface “The plan in nothing; the planning is every-thing.”(D. Eisenhower) “The discovery is nothing; the discovering (exploring) is everything." “The requirements document is nothing; the requirements process is everything.” Software Specification: G&W Preface

Software Specification: G&W Preface Gause & Weinberg concentrate on “three critical but neglected” human aspects of the requirements process: Developing a consistent understanding of requirements among all participants, Developing the desire to work as a team on the project, and Developing the necessary skills and tools for working effectively as a team to define requirements. Software Specification: G&W Preface

Software Specification: G&W Preface “Exploring Requirements can be used as a supplement to any requirements process that you now use, formal or informal.” Software Specification: G&W Preface

G&W Preface Software Specification Lecture 4 Prepared by Stephen M. Thebaut, Ph.D. University of Florida