1 Presented By: Sonya Hawkins.  Discuss Scope  Discuss Requirements 2.

Slides:



Advertisements
Similar presentations
Presentation by Prabhjot Singh
Advertisements

© 2000 Technology Builders, Inc. All rights reserved. A Requirements-Based Approach To Delivering E-business and Enterprise Applications Scott Jefferies.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Properties of Good Requirements Chapter 8. Understandable by end users End-users are not often software engineers. Terminology used must agree with end-
HTML5 and CSS3 Illustrated Unit B: Getting Started with HTML
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
Requirements and Design
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Overview of Software Requirements
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Requirement engineering for an online bookstore system
Chapter 17 Acquiring and Implementing Accounting Information Systems
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
The Software Development Life Cycle: An Overview
S/W Project Management
MSIS 630: Week 13 System Implementation and Support
Requirements Development VIASYS Healthcare. What is a requirement? 1) A condition or a capability needed by a user to solve a problem or achieve an objective.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Writing Quality Requirements Karl E. Wiegers Presented by: Ricardo Carlos.
End HomeWelcome! The Software Development Process.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
What are Requirements?. "The hardest single part of building a system is deciding what to build... No other part of the work so cripples the resulting.
IT Requirements Management Balancing Needs and Expectations.
Testing Requirements What are the requirements for a ripe apple?
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Requirements Reference: Chapters 5, 6, & 8. CMSC 345, Fall Objectives To introduce the concepts of user and system requirements To explain functional.
Test and Review chapter State the differences between archive and back-up data. Answer: Archive data is a copy of data which is no longer in regular.
This class cannot be shared or copied without the written permission of PracticeWorks Systems, LLC.
6/6/01 1 Copyright 2001 by Ralph R. Young Effective Requirements Practices Designed to improve individual, project, and organizational effectiveness. Based.
Requirements Specification. Welcome to Software Engineering: “Requirements Specification” “Requirements Specification”  Verb?  Noun?  “Specification”
Chapter 4 Software Requirements
The Web Wizard’s Guide to HTML Chapter One World Wide Web Basics.
Project management Topic 1 Project management principles.
Requirements / Specifications. 01/18/10CS-499G2 Requirements Determine what the customer needs (wants) the software to do  What are requirements?  An.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Lecture 4: Requirements Engineering COSI 120b, Principles of Software Engineering.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirements Quality Quality Measures Verification Validation.
Invitation to Computer Science 6 th Edition Chapter 10 The Tower of Babel.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
CS628 - Object Oriented Analysis And Design. The Four Pillars of Successful Software Development -Avoid Classic Mistakes -Apply Development Fundamentals.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 Modern Systems Analysis and Design Hoffer, George & Valacich Chapter 13 Finalizing Design Specifications Course: Physical System Design and Implementation.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
System Development Life Cycle (SDLC). Activities Common to Software Projects Planning : Principles Principle #1. Understand the scope of the project.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
 System Requirement Specification and System Planning.
CHAPTER ELEVEN Information System Development and Programming Languages Copyright © Cengage Learning. All rights reserved.
IS Development Methodology
CSE-862 Requirement Engineering
Systems Analysis and Design
Software Requirements
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
UNIT II.
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
Data Validation in the ESS Context
Software Verification, Validation, and Acceptance Testing
Business and IT Architecture for ESS validation
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
UNIT No- III- Leverging Information System ( Investing strategy )
Requirements Engineering
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
Software Reviews.
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

1 Presented By: Sonya Hawkins

 Discuss Scope  Discuss Requirements 2

“The work that needs to be accomplished to deliver a product or results with the specified features and functions.” Project Scope

4 TIMECOST SCOPE Quality Resources

5 TIMECOST SCOPE Quality Resources

 Thoroughly understand the project vision  Understand your priorities and the priorities of the project drivers.  Define your deliverables and have them approved by the project drivers.  Break the approved deliverables into actual work requirements. 6

The purpose of doing the project. 7

Steve McConnell Software Project Survival Guide. Redmond, Washington. :Microsoft Press,

9

 The cost of rework is typically 45% of a project's cost.  There is as much as a 2000:1 cost savings from finding errors in the requirements stage vs. in the maintenance stage of the life cycle  Reducing requirements errors is the single most effective action developers can take to improve project outcomes. 10 Young, Ralph R., 2001

Separate the “What” from the “How” The “what” refers to the requirements – what is needed to solve the problem The “how” refers to how the solution will be designed and implemented. 11

 Attainable  Complete  Correct  Feasible  Necessary  Traceable  Understandable  Consistent  Measurable and testable  Prioritized  Unambiguous  Verifiable  Does not define solution 12

UUnclear, imprecise, incomplete CConflicting DDifficult to predict impact and feasibility 13

 “The product shall switch between displaying and hiding non-printing characters instantaneously” OR  “The user shall be able to toggle between displaying and hiding all HTML markup tags in the document being edited with the activation of a specific triggering condition” 14

 “Charge numbers should be validated online against the master corporate charge number list, if possible.” OR  “The system shall validate the charge number entered against the online master corporate charge number list. If the Charge number is not found on the list, an error message shall be displayed and the order shall not be accepted.” 15

 The website shall be user friendly and load fast. How would you re-write…………..? ◦ Can you measure? ◦ Can you test? ◦ Can you verify you satisfied this requirement? 16

 Understand the Scope of the project  Define the Requirements for the project to be a success 17

18