SE 555 Software Requirements & Specification Requirements Quality Attributes.

Slides:

Advertisements

Similar presentations

Ch.21 Software Its Nature and Qualities. Ch.22 Outline Software engineering (SE) is an intellectual activity and thus human-intensive Software is built.

Advertisements

Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.

CS 411W - Notes Product Development Documentation.

Chapter 17 I.Omaima Al-Matrafi

Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.

Introduction to Software Engineering Lecture 5 André van der Hoek.

1/17 Non Functional Requirements by: Dr. Timothy Korson CPIS 443.

Software Architecture for DSD DSD Team. Overview What is software architecture and why is it so important? The role of architecture in determining system.

Moving from Analysis to Design. Overview ● What is the difference between analysis and design? ● Logical v. physical design ● System v. detailed design.

Ch2: Software: Its Nature and Qualities. 1 Introduction  Difference between a software and other engineering products.  Difference between software.

NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.

1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.

SE 555 – Software Requirements & Specifications Introduction

Requirements Specifications

Systems Design. Analysis involves understanding and documenting user requirements in a clear and unambiguous way. It focuses on the business side and.

Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.

Managing Software Quality

Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.

1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:

Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.

Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.

1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.

Software Quality Applied throughout SW Engineering Process Encompasses ▫ Analysis, design, coding, testing, tools ▫ Formal tech reviews ▫ Multi-tiered.

Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.

 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.

Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.

 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.

Chapter Five–Part III Object Oriented Design More Design issues.

Software Requirements Lecture # 3. 2 Kinds of Software Requirements Functional requirements Non-functional requirements Domain requirements Inverse requirements.

Requirements Engineering ments_analysis.

Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.

Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA

Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?

Lecture 7: Requirements Engineering

Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation

12.1 Introduction Checklists are used as a technique to give status information in a formalized manner about all aspects of the test process. This chapter.

Software Testing and Quality Assurance Software Quality Assurance 1.

Developing the Supplementary Specification 1. The Role of the Supplementary Specification  Some requirements can’t easily be expressed as use cases.

OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.

1 Software Quality Concepts SWENET Module SQA1. Software Quality: Topics u Defining software quality u Attributes of software quality u Quality trade-offs.

GBIF Mid Term Meetings 2011 Biodiversity Data Portals for GBIF Participants: The NPT Global Biodiversity Information Facility (GBIF) 3 rd May 2011.

3 September Sources of requirements  People Stakeholders ○ Who are the stakeholders? Issues: ○ Conflicting requirements ○ Wants vs. needs Helping.

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.

CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)

Quality Models in Software Engineering Literature: An Analytical and Comparative Study Rafa E. Al-Qutaish, PhD Al Ain University of Science and Technology.

Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.

Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.

1 آزمايشگاه سيستم های هوشمند ( معماری سيستمهای با مقياس بزرگ آزمايشگاه سيستمهای هوشمند پاييز 93.

Understanding Requirements Chapter 5 Applying UML and Patterns -Craig Larman.

CSE 303 – Software Design and Architecture

Overview of SAIP and LSSA. Software Architecture in Practice Provides a set of techniques, not a prescriptive method for architectural design. Based on.

Requirements Engineering ments_analysis.

System Testing 12/09. Hierarchy of Testing Testing Program Testing Top Down Bottom Up Integration TestingUnit Testing System Testing Big Bang Sandwich.

 System Requirement Specification and System Planning.

Why is Design so Difficult? Analysis: Focuses on the application domain Design: Focuses on the solution domain –The solution domain is changing very rapidly.

TOTAL QUALITY MANAGEMENT

Non-functional requirements as Gordian knot

A Survey on Software Architecture Analysis Methods

(Professional Business Analyst Training organisation)

The Development Process of Web Applications

Source & Courtesy: Doc. S. Dapkūnas

Software testing

SYSTEM ANALYSIS AND DESIGN

McCall’s Quality Factors

Software engineering.

مقدمه اي بر مهندسي نيازمنديها

Developing the Supplementary Specification

Charakteristiky kvality

Software Requirements

Presentation transcript:

SE 555 Software Requirements & Specification Requirements Quality Attributes

SE 555 Software Requirements & Specification Quality Attributes A superset of nonfunctional req. Drive architectural and design decisions Often not explicitly described by the customer Quality attributes may conflict with one another, and trade-offs may need to be explored (and possibly negotiated)

SE 555 Software Requirements & Specification Characterizing Requirements: FURPS+ One way to categorize requirements: FURPS+ Functionality Usability Reliability Performance Supportability “+” Design constraints Implementation requirements Interface requirements Physical requirements Quality requirements “-ilities” Non-functional Requirements [RUP]

SE 555 Software Requirements & Specification Another Way to Characterize Requirements: CRUPIC STMPL Operational categories Capability Reliability Usability Performance Installability Compatibility Developmental categories Supportability Testability Maintainability Portability Localizability Customer and user requirements Mostly visible at run-time Developer and support requirements Mostly visible at build-time [RUP]

SE 555 Software Requirements & Specification CRUPIC STMPL Capability. Can it perform the required functions? Reliability. Will it work well and resist failure in all required situations? Usability. How easy is it for a real user to use the product. Performance. How speedy and responsive is it? Installability. How easily can it be installed onto its target platform? Compatibility. How well does it work with external components &configurations?

SE 555 Software Requirements & Specification CRUPIC STMPL Supportability. How economical will it be to provide support to users of the product? Testability. How effectively can the product be tested? Maintainability. How economical will it be to build, fix or enhance the product? Portability. How economical will it be to port or reuse the technology elsewhere? Localizability. How economical will it be to publish the product in another language?

SE 555 Software Requirements & Specification Attaining balance to quality attributes Identify Specify Prioritize Assess conflicting goals

SE 555 Software Requirements & Specification Table 12-2 Translating Quality Attributes into Tech. Specs Quality Attribute TypesLikely Technical Information Category Integrity, Interoperability, Robustness, Usability, Safety Functional Req. Availability, Efficiency, Flexibility, Performance, Reliability System Architecture Interoperability, Usability Design Constraint Flexibility, Maintainabililty, Portability, Reliability, Reusability, Testability, Usability Design Guideline Portability Implementation Constraint