R Requirements Analysis Part I Copyright © 2001 Patrick McDermott University of California Berkeley Extension The most critical phase.

Slides:



Advertisements
Similar presentations
FT228/4 Knowledge Based Decision Support Systems Knowledge Engineering Ref: Artificial Intelligence A Guide to Intelligent Systems, Michael Negnevitsky.
Advertisements

System Development Life Cycle (SDLC)
© Gerald Kotonya and Ian Sommerville Viewpoint-Oriented Requirements Methods.
Project leaders will keep track of team progress using an A3 Report.
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
Evaluating Requirements. Outline Brief Review Stakeholder Review Requirements Analysis Summary Activity 1.
CS305: HCI in SW Development Evaluation (Return to…)
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Computer Related Issues IC3 Chapter 5 Computer Fundamentals.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Introduction To System Analysis and Design
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
CHAPTER 17 Building Software to Support an Agile Organization
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Agile Acceptance Testing Closing the communication gap in software projects Gojko Adzic
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
S/W Project Management
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Gaining Full-Time Employment Unit 2 – Task 20 Abbie Llewellyn.
1 Advanced Computer Programming Project Management: Software Life Cycle Copyright © Texas Education Agency, 2013.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Use Cases College of Alameda Copyright © 2007 Patrick McDermott.
Requirements Analysis Part II Copyright © 2001 Patrick McDermott University of California Berkeley Extension
Software Quality Assurance Activities
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Higher Computing Software Development. Software Development Process There are 7 main stages involved in developing a new software program: Analysis Design.
Facts and Fallacies of Software Engineering (Rob Glass) CSE301 University of Sunderland Discussed by Harry R. Erwin, PhD.
Introduction To System Analysis and Design
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Computer Calamities The University of California Berkeley Extension Copyright © 2007 Patrick McDermott Field, Tom, “When Bad Things.
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.
Design Step 2: Research the Problem. Knowledge Base Does a similar product already exist? Are there regulatory and standards issues? –intellectual property.
1 f02kitchenham5 Preliminary Guidelines for Empirical Research in Software Engineering Barbara A. Kitchenham etal IEEE TSE Aug 02.
CS 350, slide set 5 M. Overstreet Old Dominion University Spring 2005.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
1 Introduction to Software Engineering Lecture 1.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Justice Robert Beaudoin November 16 th,  Most disputes are solved as a result of the negotiation process.  Our rules prepare every case for an.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Systems Development Life Cycle
Software Engineering Project.  Why User involvement?  Requirements Gathering statistics.  Ways of Gathering user requirements.  One-on-One Interviews.
Forms Analysis Copyright © 2007 Patrick McDermott University of California Berkeley Extension
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Contracting. The contracting process typically begins during or shortly after the assessment. Skills applicable to this phase of practice include the.
Herriman High Computer Programming 1A Software Development Cycle Things to Know.
Reading TCP/IP Protocol. Training target: Read the following reading materials and use the reading skills mentioned in the passages above. You may also.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Evaluating Requirements
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
Etreme rogramming (XP) eXtreme Programming (XP). 2 A Typical XP Project All programmers in a room together Work in a series of fixed iteration cycles.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Requirements Engineering
Systems Analysis and Design
About the Presentations
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
Unit 6: Application Development
Work Breakdown Structure
Requirements Management - I
Requirements Validation – I
Presentation transcript:

R Requirements Analysis Part I Copyright © 2001 Patrick McDermott University of California Berkeley Extension The most critical phase for Systems Analysis!

A Requirement is… A Specific Thing your System has to do to Work Correctly. –Specific: A single thing you can test –System: The complete app or project –Correctly: “The customer decides when a system works correctly. So if you leave out a requirement or even if they forget to mention something to you, the system isn’t working correctly.” “A requirement is a singular need detailing what a particular produce or service should be or do.” —H1OOAD, p. 62.

Domain Analysis “The process of identifying, collecting, organizing, and representing the relevant information of a domain, based upon the study of existing systems and their development histories, knowledge captured from domain exerts, underlying theory, and emerging technology within a domain.” —H1 st OOA&D McLaughlin, Brett D., Gary Pollice & David West, Head First Object-Oriented Analysis & Design, Sebastopol, California: O’Reilly ( ), 2007.

Robert L. Glass  Fact 23. One of the two most common causes of runaway projects is unstable requirements. (The other is poor estimation)  Fact 24. Requirements errors are the most expensive to fix during production.  Fact 25. Missing requirements are the hardest requirements errors to correct.  Fact 26. Explicit requirements “explode” as implicit (design) requirements for a solution evolve. Glass, Robert L., Facts and Fallacies of Software Engineering, Boston: Addison-Wesley ( ), 2003.

Analyze Analyze—Find the details of the situation Synthesize—Put together for understanding, communication and improvement Investigate Data Models Use Cases Other Models Béla Uitz Analysis on a Violet Background 1922

Focus on Requirements Listen to the Customer : “ When it comes to requirements, the best thing you can do is let the customer talk. And pay attention to what the system needs to do; you can figure out how the system will do those things later.” —H1OOAD Don’t worry about your code at this stage—just make sure you know what the system should do.

Communicate Question Listen Negotiate Present Sell Gause, Donald C. & Gerald M. Weinberg, Exploring Requirements: Quality Before Design, New York: Dorset House ( ), TALK LISTEN!

You Must Ensure All relevant rules within the Scope are –Discovered –Defined –Verified The Participants (“users”, “SMEs”, “clients”, …) agree that these are the Rules The Rules are documented in such a way that –they are unambiguous –participants can verify them They are useful to both audiences –IT - analysts, designers, programmers … –Business - sponsor, management, subject experts, …

Business Rules A Purchase Order can specify several Items A Purchase Order must specify at least one delivery location Mailing addresses must include a zip code The format of a zip code is nnnnn-nnnn An approved vendor must be reviewed every three years Late fees are calculated by adding 1% Exercise: What are the Business Rules for Enrolling in this class?