1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements.

Slides:



Advertisements
Similar presentations
Expediting the Software RFP Process: The CTS EZ RFP.
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Software Requirements Analysis and Specification C.Eng 491 Fall
Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.
UI Standards & Tools Khushroo Shaikh.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
SWE Introduction to Software Engineering
Software Requirements
Requirements (recap)‏
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
SYS366 Week 3, Lecture 2 Introduction to Requirements Gathering:
Microsoft ® Official Course Monitoring and Troubleshooting Custom SharePoint Solutions SharePoint Practice Microsoft SharePoint 2013.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
1 BTS330 Vision & Scope. 2 IT Projects What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of.
Chapter 2 Introduction to Requirements Management
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management greene.com 1 Applied Software.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
ITEC 370 Lecture 8 Requirements. Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
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.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Requirements. Terminology: Requirements XYZ Requirements gathering (also known as “requirements elicitation”) : what is to be accomplished, how the system.
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
Lecture: The Importance of Stakeholders.  Objective of the requirements capture and analysis phases is to understand business processes and develop requirements.
Chapter 14 Part II: Architectural Adaptation BY: AARON MCKAY.
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
Lecture 7: Requirements Engineering
1 BTS330 Introduction to Stakeholders & Business Areas.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
SYS466 Casual Use Case Specifications. Systems Use Case Diagrams and Specifications Based on the dialog metaphor Based on the dialog metaphor The process.
SYS366 Week 7, Lecture 1 Introduction to Requirements Gathering:
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
1 SYS366 Lecture Requirements Gathering: Stakeholders.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Module 1 Introduction to Designing a Microsoft® Exchange Server 2010 Deployment.
Lecture: The Importance of Stakeholders SYS366. Identifying Requirements Objective of the requirements capture and analysis phases is to understand business.
1 Week 7 - System analyst IT2005 System Analysis & Design.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirement Engineering
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
SERVICE REQUEST MANAGEMENT IMPLEMENTATION Rev Mar 11, 2008.
CSC480 Software Engineering Lecture 7 September 16, 2002.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
1 Software Requirements Descriptions and specifications of a system.
1 SYS366 More on (Systems) Use Cases. 2 Identifying Actors and Systems Use Cases Requirements Gathering Need to find out what the user requires in the.
Applied Software Testing
Classifications of Software Requirements
Chapter 5 – Requirements Engineering
SYSTEM ANALYSIS AND DESIGN
The Next Stage in Analysis: Systems Use Case Diagrams
Classical Waterfall Model
CSC480 Software Engineering
Applied Software Implementation & Testing
WEB 407 knowledge is divine-- snaptutorial.com. WEB 407 Week 1 Individual Creating an HTML5 Document For more classes visit WEB 407.
Software Design Lecture : 15.
CSE 403, Software Engineering Lecture 2
Introduction to Requirements Management
Presentation transcript:

1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements

2 Requirements Needs and Features are informal. Needs, Features and Requirements represent different views of the system.

3 Identifying Requirements The Requirements view is provided by the product feature set and other high-level product requirements definitions.* Bitner & Spence, p.74

4 Identifying System Requirements “A requirement is a desired feature, property or behavior of a system.” * * Unified Modeling Language

5 Features “Features are not useful for defining the behavior of the system in precise enough terms to design, develop, or test the system.” * * Use Case Modeling, by Bittner & Spence, page 6.

6 Identifying System Requirements A requirement “is either derived directly from stakeholder or user needs Or stated in a contract, standard, specification, or other formally imposed document.” * * Use Case Modeling, by Bittner & Spence, page 5.

7 Requirements Gathering For an existing system, analyst needs to find out: – Functionality what functionality of the existing system will be included in the new system – Data needs what data from the existing system will need to be migrated into the new system

8 Requirements Gathering For a new system, analyst needs to find out: – Functionality What are the activities the system needs to perform? How is the user to interact with the system? Are other systems to interact with the system? – Data needs What information is needed?

9 Operating Requirements “the product (from the Product Position statement) to be produced results in requirements being placed on the operating environment in which it will be deployed” * These operating requirements that must be met by the operating environment if the solution is to be successfully deployed.* * Use Case Modeling, by Bittner & Spence, page 79.

10 Operating Requirements Operating requirements include 1. System Requirements 2. Operating Environment requirements * Use Case Modeling, by Bittner & Spence, page 79.

11 System Requirements System requirements necessary to support the application, such as – Host operating systems – Network platforms – Configurations – Memory – Peripherals – Companion software – performance Use Case Modeling, by Bittner & Spence, page 79.

12 Operating Environment Requirements For hardware-based systems – Location – Temperature – shock – Humidity Use Case Modeling, by Bittner & Spence, page 80.

13 Operating Environment Requirements For software applications – Usage conditions – User environment – Resource availability – Maintenance issues – Error handling – Back up and Recovery Use Case Modeling, by Bittner & Spence, page 80.

Operating Environment for one Business Area: Customer Support

Operating Environment Requirements Exercise Each group member is to develop 3 operating environment requirements for their Business area The team is to develop 3 overall operating environment requirements for JAT. The individual operating requirements plus the overall operating requirements are to be added to section II, E, of the PID. The team is responsible for ensuring that there is no duplication in the PID.