Lecture 6 – Requirement Analysis

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

Requirements Engineering Process
Chapter 27 Software Change.
Chapter 3: Requirements Determination
Day 11 – UML and Use Case Diagrams
Lecture 2 – Systems development life cycle
L ECTURE 5 – G ANTT C HART GANTT Charts Constructing GANTT Charts Staffing and Re-scheduling Project Management Software Software Project Management Maria.
Systems Analysis Chapter 4.
Lecture 8 – USE CASE ANALYSIS
© Copyright 2011 John Wiley & Sons, Inc.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
Chapter 2 Succeeding as a Systems Analyst
Systems Analysis and Design
Identifying needs and establishing requirements Chapter 7b.
Systems Analysis Chapter 4
L ECTURE 3 – P LANNING - P ROJECT I NITIATION Opportunity Identification System Request Feasibility Analysis Project Management The Project Plan Software.
L ECTURE 9 – PROCESS MODELLING PART 1 Data Flow Diagrams for Process Modelling Multi-level Data Flow Diagrams Logical Vs Physical DFDs Steps to Construct.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Office of Information Technology (OIT) PROJECT INITIATION DOCUMENTS - BUSINESS CASE, ALTERNATIVE ANALYSIS AND STATEMENT OF WORK (SOW)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 4th Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
University of Nottingham School of Computer Science Large Scale Systems Design Dr Dario Landa-Silva 1 Large Scale Systems Design G52LSS Semester 1 of session.
CIS 321—IS Analysis & Design Chapter 1: The World of the Modern Systems Analyst.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Systems Analysis and Design CHAPTER 1
Systems Analysis Strategies Chapter 4
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 14 Information System Development
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
IT Job Roles & Responsibilities Shannon Ciriaco Unit 2:
IS2210: Systems Analysis and Systems Design and Change Twitter:
Introduction to Project Management. Projects A unique process, consisting of a set of coordinated and controlled activities with start and finish dates,
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Slide 1 Requirements Analysis - What is a Requirement? - Business requirements -> System requirements - Functional Requirements: _______________ - Nonfunctional.
Modern Systems Analysis and Design Third Edition Chapter 11 Selecting the Best Alternative Design Strategy 11.1.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Prof. Salim Arfaoui 1-0© Copyright 2011 John.
Multimedia Industry Knowledge CUFGEN01A Develop And Apply Industry Knowledge CUFMEM08A Apply Principles Of Instructional Design To A Multimedia Product.
CASE Tools and their Effect on Software Quality
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Roberta Roth, Alan Dennis, and Barbara Haley.
Name/Title of Your App Prepared by: …… For the 5 th National ICT Innovation Competition.
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Roberta Roth, Alan Dennis, and Barbara Haley.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Project Management PTM721S
Information Systems Development
© Copyright 2011 John Wiley & Sons, Inc.
Embedding CRM in HEIs Graham Hackney Kate Jackson Rupert Frankum
Requirements Determination
Updating the Value Proposition:
Identify the Risk of Not Doing BA
Requirement Management
SYSTEMS ANALYSIS Chapter-2.
Information Systems Development
Chapter 1 Introduction.
Systems Analysis and Design Chapter1: Introduction
Tour VII: Change Management
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Introduction Chapter 1 Copyright ©2016 Pearson Education, Inc.
Session 3 The Strategic Position
Systems Development An Overview of Systems Development
Internet Marketing Planning
Presentation transcript:

Lecture 6 – Requirement Analysis System Requirements Requirements Analysis Techniques Software Project Management Maria Petridou

University of Nottingham 3/31/2017 System Requirements System Requirements are all of the capabilities that the new system must have. From Planning Phase The systems request produced in the planning phase lists the high-level business requirements of the proposed system. Software Project Management Maria Petridou Maria Petridou

University of Nottingham 3/31/2017 System Requirements Analysis Phase The first step in the analysis phase is to develop an analysis strategy in order to define the system requirements. The aim is to turn the precise business requirements into precise system requirements. Software Project Management Maria Petridou Maria Petridou

University of Nottingham 3/31/2017 System Requirements The purpose of defining requirements is to provide information for the next steps in the analysis phase (use cases, process model, data model, etc.) and to define the scope of the system. The analysis phase involves: 1. Understanding current system 2. Identifying improvements 3. Define requirements for new system Software Project Management Maria Petridou Maria Petridou

University of Nottingham 3/31/2017 System Requirements Stakeholders and system analysts should work in co-operation in order to determine the system requirements. Stakeholders – users, sponsors, technical staff. An analysis strategy consists of requirements analysis techniques and information gathering techniques. System requirements are divided in Functional: Activities the system MUST perform. ( Information & Process) Non-functional: Characteristics of the system other than activities ( Performance, Operational, Security, Cultural, Political) Software Project Management Maria Petridou Maria Petridou

University of Nottingham 3/31/2017 System Requirements Exercise 1: Determine which in the following are functional requirements and which ones are non-functional requirements. (Dennis&Wixom, Ch.4). Be accessible to web users Include the company standard logo and colour scheme Restrict access to profitability information Provide management reports Have 2-second maximum response time for predefined queries, and 10-minute maximum response time for ad-hoc queries. Include sales information that is updated at least daily. Print additional reports in other languages. Include actual and budgeted cost information. Software Project Management Maria Petridou Maria Petridou

Requirements Analysis Techniques University of Nottingham 3/31/2017 Requirements Analysis Techniques Main requirements analysis techniques are the following: Business process automation (BPA) The basic way in which the organisation operates is left unchanged and computer systems are used to automate some of the work. Focus on automate processes. No changes to organisation. Business process improvement (BPI) Moderate changes to the way in which the organisation operates in order to achieve improvements. Focus on improve processes. Moderate changes to organisation. Business process re-engineering (BPR) Uses new ideas and technology to make major changes to the way in which the organisation operates. Focus on innovation. Major changes to organisation. Software Project Management Maria Petridou Maria Petridou

Requirements Analysis Techniques University of Nottingham 3/31/2017 Requirements Analysis Techniques Some other requirement analysis techniques are: Software Project Management Maria Petridou Maria Petridou

Requirements Analysis Techniques University of Nottingham 3/31/2017 Requirements Analysis Techniques Software Project Management Maria Petridou Maria Petridou

Requirements Analysis Techniques University of Nottingham 3/31/2017 Requirements Analysis Techniques Software Project Management Maria Petridou Maria Petridou

Requirements Analysis Techniques University of Nottingham 3/31/2017 Requirements Analysis Techniques Each requirements analysis technique has different impact on the project: Reading: (Dennis&Wixom, chapter 4). Software Project Management Maria Petridou Maria Petridou