tailieunhanh - Lecture Software requirements engineering - Lecture­ 25: Requirements management

After this chapter the student should have acquired the following knowledge and skills: Threads, exclusive resource access, cooperation between threads, concurrent programming example. | Requirements Management Lecture-25 Recap 2 Requirements management Why requirement management? CASE tools to manage requirements A generic tool Stable and volatile requirements Reasons for change in requirements Identifying requirements Today’s lecture 3 Requirements management 4 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Requirements change factors Requirements errors, conflicts and inconsistencies As requirements are analysed and implemented, errors and inconsistencies emerge and must be corrected. These may be discovered during requirements analysis and validation or later in the development process. Evolving customer/end-user knowledge of the system As requirements are developed, customers and end-users develop a better understanding of what they really require from a system. Technical, schedule or cost problems Problems may be encountered in implementing a requirement. It may be too expensive or take too long to implement . | Requirements Management Lecture-25 Recap 2 Requirements management Why requirement management? CASE tools to manage requirements A generic tool Stable and volatile requirements Reasons for change in requirements Identifying requirements Today’s lecture 3 Requirements management 4 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Requirements change factors Requirements errors, conflicts and inconsistencies As requirements are analysed and implemented, errors and inconsistencies emerge and must be corrected. These may be discovered during requirements analysis and validation or later in the development process. Evolving customer/end-user knowledge of the system As requirements are developed, customers and end-users develop a better understanding of what they really require from a system. Technical, schedule or cost problems Problems may be encountered in implementing a requirement. It may be too expensive or take too long to implement certain requirements. Requirements change factors Changing customer priorities Customer priorities change during system development as a result of a changing business environment, the emergence of new competitors, staff changes, etc. Environmental changes The environment in which the system is to be installed may change so that the system requirements have to change to maintain compatibility Organisational changes The organisation which intends to use the system may change its structure and processes resulting in new system requirements Word processor documents Advantages Requirements are all stored in the same place Requirements may be accessed by anyone with the right word processor It is easy to produce the final requirements document Disadvantages Requirements dependencies must be externally maintained Search facilities are limited Not possible to link requirements with proposed requirements changes Not possible to have version control on individual requirements No automated navigation .

• Kỹ thuật lập trình
• Requirement engineering
• Requirement engineering process
• Software requirements engineering
• Lecture Software requirements engineering
• Software engineering
• Requirements engineering
• Lecture Requirement engineering
• Software requirement
• Requirement specification
• System requirement specification
• External interface requirement
• Requirement analysis
• Data flow diagram
• Use case modelling
• Requirement validation
• Requirements verification
• Requirement management
• Risks in requirements engineering
• Risks management
• Software life cycle process
• Types of requirements
• Structured design
• Product vision
• Project scope
• Problem analysis
• Business requirement
• Software elicitation
• Requirements elicitation
• Requirements elicitation techniques