Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software engineering: Lecture 3 - Ivan Marsic

Lecture 3: Requirements engineering. The main contents of this chapter include all of the following: Requirements engineering components, requirements and user stories, types of requirements, effort estimation (agile methods). | Ivan Marsic Rutgers University LECTURE 3: Requirements Engineering http://office.microsoft.com/clipart/default.aspx Topics Requirements Engineering Components Requirements and User Stories Types of Requirements Effort Estimation (Agile Methods) Requirements Process Requirements analysis Requirements gathering Requirements specification Agile Development User Stories Aspect-Oriented Requirements Object-Oriented Analysis & Design Structured Analysis & Design Requirements Engineering Components Requirements gathering (a.k.a. “requirements elicitation”) helps the customer to define what is required: what is to be accomplished, how the system will fit into the needs of the business, and how the system will be used on a day-to-day basis Requirements analysis refining and modifying the gathered requirements Requirements specification documenting the system requirements in a semiformal or formal manner to ensure clarity, consistency, and completeness Requirements and . | Ivan Marsic Rutgers University LECTURE 3: Requirements Engineering http://office.microsoft.com/clipart/default.aspx Topics Requirements Engineering Components Requirements and User Stories Types of Requirements Effort Estimation (Agile Methods) Requirements Process Requirements analysis Requirements gathering Requirements specification Agile Development User Stories Aspect-Oriented Requirements Object-Oriented Analysis & Design Structured Analysis & Design Requirements Engineering Components Requirements gathering (a.k.a. “requirements elicitation”) helps the customer to define what is required: what is to be accomplished, how the system will fit into the needs of the business, and how the system will be used on a day-to-day basis Requirements analysis refining and modifying the gathered requirements Requirements specification documenting the system requirements in a semiformal or formal manner to ensure clarity, consistency, and completeness Requirements and Specification Problem domain Specifi cation Customer Software Engineer Describes Specifies Requirements Program Software (Solution) domain Analyzes Develops Example System Requirements Identifier Priority Requirement REQ1 5 The system shall keep the door locked at all times, unless commanded otherwise by authorized user. When the lock is disarmed, a countdown shall be initiated at the end of which the lock shall be automatically armed (if still disarmed). REQ2 2 The system shall lock the door when commanded by pressing a dedicated button. REQ3 5 The system shall, given a valid key code, unlock the door and activate other devices. REQ4 4 The system should allow mistakes while entering the key code. However, to resist “dictionary attacks,” the number of allowed failed attempts shall be small, say three, after which the system will block and the alarm bell shall be sounded. REQ5 2 The system shall maintain a history log of all attempted accesses for later review. REQ6 2 The system .