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

Slides:



Advertisements
Similar presentations
CS 411W - Notes Product Development Documentation.
Advertisements

RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
WKES 3202 SOFTWARE REQUIREMENTS ENGINEERING SEMESTER 1 SESSION 2004/2005.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Introduction to ISO 9001:2000 Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
RequisitePro (2) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Software Requirements Specification (SRS) Complete description of external behavior of software system Complete description of external behavior.
Managing Software Quality
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1Welcome! Rational Requirements Management.
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Software Requirements Engineering CSE 305 Lecture-2.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
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
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Software quality factors
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.
Quality Factors Chapter Three. Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
Requirements Specification Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
TOTAL QUALITY MANAGEMENT
Software Quality Control and Quality Assurance: Introduction
Requirements Engineering Lecture 13
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
Requirements Engineering Lecture 2
Software Quality Assurance Software Quality Factor
McCall’s Quality Factors
Lecture 15: Technical Metrics
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
Introduction to Software Testing
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Software Requirements Specification (SRS) Template.
Requirements Document
Requirement Analysis.
Requirements Engineering Lecture 6
Presentation transcript:

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

J. Nawrocki, Quality Manag. (5) McCalls Quality Factors Correctness – tst Reliability (precision, accuracy) – tst Efficiency – tst Integrity (security) – tst Usability ? Maintainability – insp Flexibility ? Testability ? Portability (interoperability) – spec Reusability x

J. Nawrocki, Quality Manag. (5) McCalls Quality Factors Communication commonality ? Completeness – tst report Conciseness ? Consistency – doc c.: audits Data commonality ? Error tolerance ? Instrumentation – spec + tst Security – tst Self documentation: spec?, audits

J. Nawrocki, Quality Manag. (5) Requirements document (1) 1. Introduction 1.1 Purpose of the document 1.2 Scope of the product 1.3 Definitions, acronyms and abbreviations 1.4 References 1.5 Overview of the document

J. Nawrocki, Quality Manag. (5) Requirements document (2) 2. General description 2.1 Product perspective 2.2 Viewpoints Stakeholders Users Domain Components 2.3 System architecture and use cases in UML 2.4 General constraints 2.5 Assumptions and dependencies

J. Nawrocki, Quality Manag. (5) Requirements document (3) 3. Technical requirements 3.1 Functional requirements Requirement Introduction Viewpoint and source(s) Firmness and importance Verifiability and clarity Inputs Processing Outputs

J. Nawrocki, Quality Manag. (5) Requirements document (4) Requirement External interface requirements User interfaces Hardware interfaces Software interfaces Communication interfaces 3.3 Performance requirements

J. Nawrocki, Quality Manag. (5) Requirements document (5) 3.4 Design constraints Standards compliance Hardware limitations Attributes Security Maintainability...

J. Nawrocki, Quality Manag. (5) Requirements document (6) 3.6 Other requirements Database Operations Site adaptation Training Non-technical requirements Appendixes Index

J. Nawrocki, Quality Manag. (5) Plan of the lecture Introduction Hello and Good-bye Creating a project Opening a project and docs Closing a project and docs Adding a project to the project list Modifying password and

J. Nawrocki, Quality Manag. (5) SummarySummary Basic activities concerning Requiste Pro: starting a session closing a session...

J. Nawrocki, Quality Manag. (5) Further readings Introducing Rational Suite (60) Getting Started with Rational Suite (80) Using Rational RequisitePro 

J. Nawrocki, Quality Manag. (5) HomeworkHomework Get familiar with ClearQuest. How to organise audits for Software Baseline Library maintained with Rational Suite tools?

J. Nawrocki, Quality Manag. (5) Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how?