Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Software Requirements Engineering (SE2223) : Ibrar Arhsad Ibrar - Arshad@cust - Edu.pk

    Uploaded by

    Hydra Purifier
    This document provides an introduction to a course on Software Requirements Engineering. The course covers topics like requirements elicitation, analysis, documentation and management. It aims to help students understand the requirements engineering process and apply techniques to elicit, model and analyze software requirements. Over 15 weeks, students will learn about requirements-related processes, quality attributes, modeling techniques, and requirements engineering in software product lines. Evaluation includes quizzes, assignments, projects, mid-term and final exams, and class participation. Required textbooks are also listed.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Software Requirements Engineering (SE2223) : Ibrar Arhsad Ibrar - Arshad@cust - Edu.pk

    Uploaded by

    Hydra Purifier
    23 views19 pages
    This document provides an introduction to a course on Software Requirements Engineering. The course covers topics like requirements elicitation, analysis, documentation and management. It aims to help students understand the requirements engineering process and apply techniques to elicit, model and analyze software requirements. Over 15 weeks, students will learn about requirements-related processes, quality attributes, modeling techniques, and requirements engineering in software product lines. Evaluation includes quizzes, assignments, projects, mid-term and final exams, and class participation. Required textbooks are also listed.

    Original Title

    Lecture0

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides an introduction to a course on Software Requirements Engineering. The course covers topics like requirements elicitation, analysis, documentation and management. It aims to help students understand the requirements engineering process and apply techniques to elicit, model and analyze software requirements. Over 15 weeks, students will learn about requirements-related processes, quality attributes, modeling techniques, and requirements engineering in software product lines. Evaluation includes quizzes, assignments, projects, mid-term and final exams, and class participation. Required textbooks are also listed.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    23 views19 pages

    Software Requirements Engineering (SE2223) : Ibrar Arhsad Ibrar - Arshad@cust - Edu.pk

    Uploaded by

    Hydra Purifier
    This document provides an introduction to a course on Software Requirements Engineering. The course covers topics like requirements elicitation, analysis, documentation and management. It aims to help students understand the requirements engineering process and apply techniques to elicit, model and analyze software requirements. Over 15 weeks, students will learn about requirements-related processes, quality attributes, modeling techniques, and requirements engineering in software product lines. Evaluation includes quizzes, assignments, projects, mid-term and final exams, and class participation. Required textbooks are also listed.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 19

    Software Requirements Engineering

    (SE2223)
    Ibrar arhsad
    ibrar.arshad@cust.edu.pk
    COURSE INTRODUCTION

    • Title
    Software Requirements Engineering (SE 3513 )
    • Pre-req
    Software Engineering (SE 2223 )

    SE 3513 – Software Requirements Engineering 2


    COURSE OBJECTIVE

    • The objective of this course is to help the students to


    understand software requirements engineering
    process, issues faced during this process and how to
    apply it for elicitation, modeling and analysis of
    software requirements

    SE 3513 – Software Requirements Engineering 3


    COURSE LEARNING OUTCOMES

    • At the end of this course, the students should be able to


     CLO-1: Understand of the importance of following a systematic
    requirements engineering process
     CLO-2: Effectively gather and analyze software requirements for the
    development of cost-effective and efficient technical solutions
     CLO-3: Use system modeling techniques for requirements analysis
    and requirements presentation

    SE 3513 – Software Requirements Engineering 4


    BOOKS

    • Requirements Engineering: Processes and Techniques, Kotonya


    and Sommerville, John Wiley
    • Software Requirements Engineering, 2nd Edition by Richard H.
    Thayer and Merlin Dorfman
    • Requirements Engineering: From System Goals to UML Models to
    Software Specifications by A. van Lamsweerde, Wiley; 1st Edition
    • Requirements Engineering: Fundamentals, Principles, and
    Techniques by Klaus Pohl, Springer; 1st Edition

    SE 3513 – Software Requirements Engineering 5


    Week # Class Topics
    CONTENTS Introduction to Software Requirements Engineering
    Week 1
    Types of software requirements
    Software requirements engineering process
    Week 2 SRE Players
    Human, Social and Cultural Factors
    Week 3
    Requirements Elicitation Process and Techniques
    Requirements Elicitation Techniques
    Week 4
    Requirements analysis Process
    Requirements analysis Techniques
    Week 5
    Requirements Negotiation Process
    Requirements Negotiation Process, Common Errors in
    Week 6 Requirements
    Requirements Validation Processes
    Requirements Validation Techniques
    Week 7
    Requirements Management Processes
    Requirements Management Techniques
    Week 8
    Requirements Management Techniques
    SE 3513 – Software Requirements Engineering 6
    Week # Class Topics
    CONTENTS Software Requirements Documentation Process
    Week 9
    Standard Templates for Requirements Documentation
    Software Requirements Quality attributes
    Week 10
    Software Requirements Quality attributes
    Team Skills: Six Team Skills required to address requirement
    Week 11 challenges
    From Requirements to Use Cases
    From Use cases to Domain Model
    Week 12
    From Use cases to Domain Model
    From Use cases to SSD
    Week 13
    From Use cases to SSD
    Software Requirement Engineering in Software Product Line
    Week 14
    Software Requirement Engineering in Software Product Line
    Software Requirement Engineering in Software Product Line
    Week 15
    Software Requirement Engineering in Software Product Line
    Student Presentations
    Week 16
    Student Presentations
    SE 3513 – Software Requirements Engineering 7
    EVALUATION CRITERIA

    Exam Type Percentage(%)


    Quiz 10
    Assignments 10
    Project-Presentation 10
    Mid Term 20
    Final Term 40
    Class Participation 10

    SE 3513 – Software Requirements Engineering 8


    SOFTWARE DEVELOPMENT LIFECYCLE

    SE 2223 Software Requirements Engineering 9


    SOFTWARE REQUIREMENTS

    • Something required, something wanted or


    needed
    (Webster’s dictionary)
    • There is a huge difference between wanted and
    needed and it should be kept in mind all the time

    SE 3513 – Software Requirements Engineering 10


    SOFTWARE REQUIREMENTS CONT..

    • A complete description of what the software system


    will do without describing how it will do it is
    represented by the software requirements
    • Software requirements are complete specification of
    the desired external behavior of the software system to
    be built

    SE 3513 – Software Requirements Engineering 11


    SE 3513 – Software Requirements Engineering 12
    SE 2223 Software Requirements Engineering 13
    SE 2223 Software Engineering 14
    SOFTWARE REQUIREMENTS CONT..

    SE 3513 – Software Requirements Engineering 15


    WHY REQUIREMENTS?

    • When 38 IT professionals in the UK were asked


    about which project stages caused failure,
    respondents mentioned “requirements definition”
    more than any other phase

    SE 3513 – Software Requirements Engineering 16


    REQUIREMENTS CHALLENGES

    • Success criteria is not defined clearly


    • Stakeholders change their minds
    • Stakeholders are not willing to speak up or they are being too
    expressive
    • Stakeholders imply or insist on a particular technical solution
    • Stakeholders have Conflicting priorities

    SE 3513 – Software Requirements Engineering 17


    SOFTWARE REQUIREMENTS

    • The hardest single part of building a software system


    is deciding what to build...No other part of the work
    so cripples the resulting system if done wrong. No
    other part is difficult to rectify later
    Fred Brooks

    SE 2223 Software Requirements Engineering 18


    SOURCES OF REQUIREMENTS

    • Stakeholders
     Entities affected in some way by the system
    • Documents
    • Existing Systems
    • Application Domain

    SE 2223 Software Engineering 19

    You might also like