Scope of Systems Requirements: Definition o f Requirements Not to define the full system Not to define the full system Describe or define the essential.

Slides:



Advertisements
Similar presentations
Problem solving methodology Information Technology Units Adapted from VCAA Study Design - Information Technology Byron Mitchell, November.
Advertisements

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Types of Requirements  Functional Requirements  Descriptions of actions or processes that create or update information.  Outlines of reports or on-line.
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Fact-Finding Fact-Finding Overview
Systems Analysis and Design in a Changing World, 6th Edition
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
7M822 Software Requirements Introduction 7 September 2010.
Requirements Modeling
The Software Development Cycle Defining and understanding the problem.
Continuation From Chapter From Chapter 1
Chapter 10 Systems Planning, Analysis, and Design.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Approaches to Investigating a System “Who knows what’s happening now?”
Requirements Analysis
Module 4: Systems Development Chapter 13: Investigation and Analysis.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Investigating System Requirements
PRJ566 Project Planning and Management
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
1 Chapter 10 Fact-Finding Techniques Transparencies.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
1 Introduction to Software Engineering Lecture 1.
ICT IGCSE.  Introducing or changing a system needs careful planning  Why?
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.
The techniques involved in systems analysis Explanation of a feasibility study:Explanation of a feasibility study: –economic, –legal, –technical, –time.
Project Management Cross lifecycle Activity
Systems Development Life Cycle
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Week 3: Requirement Analysis & specification
Requirements Analysis
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 Systems Analysis & Design 7 th Edition Chapter 2.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
Systems Development Life Cycle
Pepper modifying Sommerville's Book slides
Investigating System Requirements
Types and Characteristics of Requirements
Chapter 4 – Requirements Engineering
Economics-VII (Research Methodology) Topic-Data Collection
TIM 58 Chapter 3: Requirements Determination
Systems Analysis and Design
EKT 421 SOFTWARE ENGINEERING
SYSTEMS ANALYSIS Chapter-2.
Requirement Engineering
SNS College of Engineering Coimbatore
Requirements Elicitation – 1
Systems Analysis and Design in a Changing World, 6th Edition
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Campus Locator – Definition Phase (May04-04)
Software Requirements analysis & specifications
Essentials of Systems Analysis and Design Fourth Edition
CLINICAL INFORMATION SYSTEM
Introduction to Systems Analysis and Design
Requirements Analysis
Overview Characteristics for gathering requirements.
Members: Keshava Shiva Sanjeeve Kareena
Systems Development Life Cycle
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Public Management Information Systems System Analysis Thursday, August 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

Scope of Systems Requirements: Definition o f Requirements Not to define the full system Not to define the full system Describe or define the essential properties or attributes Describe or define the essential properties or attributes Definition Definition An abstract description of services, which the system is expected to provide, and constraints under which the system must operate.

TYPES OF REQUIREMENTS User Requirements User Requirements System Requirements System Requirements Functional Requirements Functional Requirements Non – Functional Requirements Non – Functional Requirements

User requirements User requirements are the statements, User requirements are the statements, in a natural language and diagrams, in a natural language and diagrams, what services the system is expecting to providing and constraints under it which what services the system is expecting to providing and constraints under it which it should operate it should operate

System Requirements System services and constraints in detail System services and constraints in detail

Functional Requirements How the system should react to the particular inputs How the system should react to the particular inputs How the system should behave to the particular situations How the system should behave to the particular situations What the system should not do What the system should not do

Non - Functional Requirements Constraints on the services or functions Constraints on the services or functions Time constraints Time constraints Constraints on the development process Constraints on the development process

Fact – Finding Techniques By Investigating The Current System  Interviews – Used to collect information verbally, from managers/employees.  Unstructured – a free question answer session  Structured questioning- use standard questioning  Open-response- Interviewees are allowed to answer in their own words.  Closed-response- selects from a given set of answers

Fact – Finding Techniques By Investigating The Current System  Open- feeling, opinions, experiences; good for exploring a process/problem Questionnaire- a useful alternative to interviews. May be the only feasible way to contact a large group Questionnaire- a useful alternative to interviews. May be the only feasible way to contact a large group Record Review- Examine the written Record Review- Examine the written

Fact – Finding Techniques By Investigating The Current System  Observation- provides information that could not be obtained in any other way. Most useful processes are carried out and whether specified steps actually occur. Observation can change what people do

System Model --- Context Model  which lack information about detailed system functionality. A more detailed system model should  Details of the system inputs  Details of the system outputs  Details of the system data processing  Details of control in the system

Analyzing the Current System Determine Info. Requirements Determine Info. Requirements  Information Architecture  Objective  Data modeling

Analyzing the Current System Document & Analyze Existing Information System Document & Analyze Existing Information System  Data Flow Diagram  Other Graphic Techniques  System flowchart  Rich pictures  Simulation

Analyzing the Current System Isolate Deficiencies in the System Isolate Deficiencies in the System  Information  Technology  Process  Personnel

Identifying requirements Data from analysis of current system Data from analysis of current system Prototyping Prototyping Joint Application Design Joint Application Design Research Research

Without Prototype Feasibility study Feasibility study Requirement Analysis and capture Requirement Analysis and capture Requirement definition (end – user) Requirement definition (end – user) Requirements Specification Requirements Specification requirements is set out and acts as a basic foundation between user and software developer requirements is set out and acts as a basic foundation between user and software developer

Output: Project Proposal Project definition/description Project definition/description Justification Justification Cost (resource requirements) Cost (resource requirements) Time schedule Time schedule Objectives Objectives Constraints Constraints