1. TUTORIAL 2 Class 1
2. TUTORIAL 2 Class 1
2.1. Functional Requirement vs Non-Functional Requirement
2.1.1. Functional Requirements
2.1.1.1. Help understand the functions of the system.
2.1.1.2. Explhaveain the characteristics that a system is expected to have.
2.1.1.3. Identify what the system MUST or MUST NOT do.
2.1.1.4. Will allow the system to perform, even if the non-functional requirements are not met.
2.1.1.5. Ensures the system will meet user requirements.
2.1.1.6. Are essential to system operations.
2.1.1.7. Straightforward to define and agree on.
2.1.1.8. Meeting these requirements is obligatory.
2.1.1.9. Define the system or an element of it.
2.1.1.10. Usually defined by the user.
2.1.1.11. Can be documented and understood through a use case.
2.1.2. Non Functional Requirements
2.1.2.1. Help understand the performance of the system.
2.1.2.2. The system will not work with non-functional requirements alone.
2.1.2.3. Ensures the product meets user expectations.
2.1.2.3.1. Meeting these requirements is not obligatory but may be desirable.
2.1.2.4. May be desirable but are not always essential.
2.1.2.5. Harder to define and agree on.
2.1.2.6. Explain the way in which the product should work (how it should behave).
2.1.2.7. Outline quality attributes of the system.
2.1.2.8. Usually defined by software engineers, developers, software architects or other technical experts.
2.1.2.9. Can be documented and understood as a quality attribute.
2.1.2.10. Identify how the system SHOULD do it.
2.2. Activity 1
2.2.1. Functional Req. for Blue
2.2.2. Non-functional Req. for Red
2.2.3. Q1: Which of these are functional requirements?
2.2.3.1. Users of the library will be either normal or staff
2.2.3.1.1. Nam
2.2.3.1.2. f
2.2.3.2. The library contains one million books
2.2.3.3. If a user asks a book that has been borrowed, her request shall be inserted in a waiting list
2.2.3.3.1. Trung
2.2.3.4. Staff shall have no priority in borrowing books
2.2.3.5. A user will be able to borrow a book
2.2.3.5.1. Trung
2.2.3.6. A staff person will be able to borrow a book -
2.2.3.6.1. Trung
2.2.3.6.2. DuyHN
2.2.3.7. Traanf
2.2.4. Q2: Which of these are non-functional requirements
2.2.4.1. Pressing the switch, the room shall get lightened in less than one second - Trung
2.2.4.2. If the room is dark, pressing the switch it shall get lightened
2.2.4.2.1. Trung
2.2.4.3. The light in the room must be sufficient to read
2.2.4.4. If someone is reading then the light must stay on
2.2.4.5. After two minutes that the room is empty the light must switch off
2.2.5. Q3: Which of these are functional requirements?
2.2.5.1. A person can enroll in a course
2.2.5.2. A course is taught by a professor
2.2.5.3. A professor is not a student
2.2.5.4. Each course terminates with an exam
2.2.5.5. Every exam produces a ranking of all participants
2.2.5.6. A student is a person
2.2.6. Q4: Which of these are functional requirements? The iPhone.....
2.2.6.1. can function as a camera
2.2.6.2. has a camera with 2.0 megapixels with geo-tagging
2.2.6.3. is a portable media player
2.2.6.4. is connected to a PC via a USB plug
2.2.6.5. includes a digital compass in the 3GS model
2.2.6.6. renders a virtual keyboard by its multi-touch screen
2.2.6.7. offers an Internet client
2.2.7. Q5: Ticket Sales System
2.2.7.1. Users must be able to browse for events by name or date or venue.
2.2.7.2. Searching for events by keywords should also be possible
2.2.7.3. User will select ticket price from those offered and also specify the number of tickets they require.
2.2.7.4. Users must be able to choose their seats and purchase tickets 24/7
2.2.7.5. Only registered customers can buy tickets.
2.2.7.6. All data is to be backed up nightly.
2.2.7.7. Ad hoc reporting will be required, showing ticket sales over a week. It should be possible to vary that time span and look at any duration up to six months
2.2.7.8. Daily reports of ticket sales must be generated. These must be retained for two years.
2.2.7.9. The system should display availability of the tickets within five seconds.
2.2.7.10. It should not be possible to double-book tickets (i.e. buy a ticket that has already been sold).
2.2.7.11. Categories of Non-Functional Req.
2.2.7.11.1. Usability - ease of learning, ease of use
2.2.7.11.2. Capacity - Data volumes, transaction volumes, user volumes
2.2.7.11.3. Robustness - reliability, data integrity, user error
2.2.7.11.4. Availability - timeframe for availability of functionality
2.2.7.11.5. Backup & recovery - protection against loss of data
2.2.7.11.6. Performance - speed of processing transactions
2.2.7.11.7. Access - permissions, who has access to which functionality and how
2.2.7.11.8. Archiving and retention - duration, methods, eventual deletion
2.2.7.11.9. Security - Security levels for protection of data