TAILIEUCHUNG - Lecture Software requirements engineering - Lecture­ 21: Specification process

After this chapter the student should have acquired the following knowledge and skills: Specifying non-functional requirements, specifying functional requirements, good/bad requirements, specifying non-functional requirements, types of NFRs, classification of NFRs. | Specification Process Lecture-21 Recap 2 Specifying functional requirements Good/bad requirements Specifying non-functional requirements Types of NFRs Classification of NFRs Today’s lecture 3 Specifying non-functional requirements Classification of NFRs (contd.) Examples of product requirements The System service X shall have an availability of 999/1000 or 99%. This is a reliability requirement which means that out of every 1000 requests for this service, 999 must be satisfied. System Y shall process a minimum of 8 transactions per second. This is a performance requirement. The executable code of System Z shall be limited to 512Kbytes. This is a space requirement which specifies the maximum memory size of the system. The request for the user's PIN shall be issued within 5 seconds of the card being entered in the card reader. This is a performance requirement. We can do some brainstorming when specifying the section special requirements in Use case development. Examples of process .

• Kỹ thuật lập trình
• Software requirements engineering
• Lecture Software requirements engineering
• Software engineering
• Requirements engineering
• Specification process
• Requirements specification
• Software requirements engineering
• Lecture Software requirements engineering
• Specifying NFRs
• Requirements validation
• Requirements engineering process tasks
• Negotiation task
• Requirements management
• Requirement engineering
• Requirement engineering process
• System engineering
• Software requirements document
• Requirements elicitation process
• Inception process
• Elicitation process
• Requirements negotiation
• negotiation meetings