{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Chapter 3- Requirements Engineering.pptx

Chapter 3- Requirements Engineering.pptx - COMP 2920...

Info icon This preview shows pages 1–12. Sign up to view the full content.

View Full Document Right Arrow Icon
COMP 2920 : Software Architecture & Design
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Chapter Topics Define requirements Requirements discovery Domain Analysis 4- 2
Image of page 2
4- 3
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Requirements Gathering The task of requirements gathering is to collect and define all features that the information system must have in order to fulfill the objectives that the customer has set. The reliability and the correctness of requirements is dependent on their sources, on the techniques that we employ to elicit and verify them, and on their effective management. 4- 4
Image of page 4
Requirements Discovery 4- 5
Image of page 5

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Requirements Discovery Requirements discovery identifies the scope and the major objectives of the system. Requirements gathering defines what is needed to reach those objectives. 4- 6
Image of page 6
4- 7
Image of page 7

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Classifying Requirements Requirements fall into two broad categories: functional (or behavioral) and non-functional. Since both relate to the same product, they are interrelated and affect each other: Functional Requirements Functional requirements specify the behavior of the system and the constraints on that behavior. Non-Functional Requirements Non-functional requirements specify non-behavioral properties of the system and the constraints on those properties. 4- 8
Image of page 8
Non-Functional Requirements Usability Reliability Performance Maintainability Security 4- 9
Image of page 9

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Techniques for Eliciting Requirements Interviews Questionnaires Elicitation Workshops Field Trips and Observation Modeling Mock-Ups 4- 10
Image of page 10
Managing Requirements Document and update requirements Document sources Separate requirements into distinct units Uniquely identify each requirement
Image of page 11

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 12
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern