User Requirements: The user requirement(s) document (URD) or user requirement(s) specification is a document usually used in software engineering that.

Slides:



Advertisements
Similar presentations
Chapter 1 Overview of Databases and Transaction Processing.
Advertisements

IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 12 – 11 – 2011 College Of Computer Science and Information, Information Systems.
CSCI 1412 Tutorial 1 Introduction to Hardware, Software Parminder Kang Home:
1/17 Non Functional Requirements by: Dr. Timothy Korson CPIS 443.
CT1404 Lecture 2 Requirement Engineering and Use Cases 1.
NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.
1 Introduction Introduction to database systems Database Management Systems (DBMS) Type of Databases Database Design Database Design Considerations.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
Configuration Management
6 th Annual Focus Users’ Conference Application Editor and Form Builder Presented by: Mike Morris.
Problems in handling NFR Term Paper (as-is) problem statement BY AJAYKUMAR ASWATHAPPA CS/SE 6361 EXECUTIVE.
Component-level testing – Equivalence partitioning, boundary value analysis, path testing Navigation testing – Testing navigation syntax and semantics.
1 Welcome: To the second learning sequence “ Data Base (DB) and Data Base Management System (DBMS) “ Recap : In the previous learning sequence, we discussed.
Introduction to the Requirements Document
Chapter 7 Applying UML and Patterns -Craig Larman
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
MADALINA CROITORU Software Engineering week 3 Madalina Croitoru IUT Montpellier.
Chapter 1 Overview of Databases and Transactions.
Session 3 How to Approach the UML Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
Technology Vocabulary Matthew L. Morris. A-D Application- A program or group of programs designed for end users. Data- Distinct pieces of information.
Chapter 1 Overview of Databases and Transaction Processing.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
© 2016 Chapter 6 Data Management Health Information Management Technology: An Applied Approach.
Requirements Gathering and Capturing
Information and documentation media systems.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Configuration Management
Software Configuration Management
NOCTI Study Guide #1 March 15, 2016.
Classifications of Software Requirements
Discovering Computers 2010: Living in a Digital World Chapter 14
Application Software Chapter 6.
Evolutionary requirements
Chapter 4 – Requirements Engineering
IS 130 Information systems 1
Naming and Saving Files
Database Systems Chapter 3 1.
Software Quality Assurance Software Quality Factor
DATA MODELS.
Software Documentation
E5-Requirements? What requirements?
I494: Designing and Developing an Information System
CS & CS Capstone Project & Software Development Project
Incepting Enterprise Applications
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment.
UNIT II.
Overview of Databases and Transaction Processing
Section 14.1 Section 14.2 Identify the technical needs of a Web server
Requirements Analysis
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Chapter 11: Software Configuration Management
Lecture 1 File Systems and Databases.
Database (DB) and Database Management System (DBMS)
IoTSec Taxonomy Proposal
Metadata The metadata contains
FAIRTRADE TRAINING GUIDE FOR SMALL FARMERS’ ORGANIZATIONS
Software Requirements Specification (SRS) Template.
Software Requirements
Lecture # 7 System Requirements
Chapter 2 Database Environment Pearson Education © 2014.
NOCTI Study Guide #1 March 15, 2016.
Case study: A museum information system
Managing Change and Quality
Software Requirements
Chapter 2 Database Environment Pearson Education © 2009.
Database management systems
Presentation transcript:

User Requirements: The user requirement(s) document (URD) or user requirement(s) specification is a document usually used in software engineering that specifies what the user expects the software to be able to do. Once the required information is completely gathered it is documented in a URD, which is meant to spell out exactly what the software must do and becomes part of the contractual agreement. A customer cannot demand features not in the URD, while the developer cannot claim the product is ready if it does not meet an item of the URD. The URD can be used as a guide to planning cost, timetables, milestones, testing, etc. The explicit nature of the URD allows customers to show it to various stakeholders to make sure all necessary features are described.

User Requirements Functional requirements Non-functional requirements Describe how the system works. It specifies something the system should do. A functional requirement for a milk carton would be “ability to contain fluid without leaking”. Describe what the system should do. Specifies how the system should behave. Non-functional requirements cover all the remaining requirements which are not covered by the functional requirements. A non-functional requirement for a hard hat might be “must not break under pressure of less than 10,000 PSI”

Functional requirements Non-functional requirements http://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/ Functional requirements Non-functional requirements Some of the more typical functional requirements include: Business Rules Transaction corrections, adjustments and cancellations Administrative functions Authentication Authorization levels Audit Tracking External Interfaces Certification Requirements Reporting Requirements Historical Data Legal or Regulatory Requirements Some typical non-functional requirements are: Performance – for example Response Time, Throughput, Utilization, Static Volumetric Scalability Capacity Availability Reliability Recoverability Maintainability Serviceability Security Regulatory Manageability Environmental Data Integrity Usability Interoperability

Data Types What is it? Can exist in a variety of forms: Data is distinct pieces of information, usually formatted in a special way. All software is divided into two general categories: data and programs. Programs are collections of instructions for manipulating data. As numbers or text on pieces of paper As bits and bytes stored in electronic memory As facts stored in a person’s mind