1. Functional Requirement vs Non-functional Requirement
1.1. Functional Requirements
1.1.1. Help understand the functions of the system.
1.1.2. Explhaveain the characteristics that a system is expected to have.
1.1.3. Identify what the system MUST or MUST NOT do.
1.1.4. Will allow the system to perform, even if the non-functional requirements are not met.
1.1.5. Ensures the system will meet user requirements.
1.1.6. Are essential to system operations.
1.1.7. Straightforward to define and agree on.
1.1.8. Meeting these requirements is obligatory.
1.1.9. Define the system or an element of it.
1.1.10. Usually defined by the user.
1.1.11. Can be documented and understood through a use case.
1.2. Non Functional Requirements
1.2.1. Help understand the performance of the system.
1.2.2. The system will not work with non-functional requirements alone.
1.2.3. Ensures the product meets user expectations.
1.2.3.1. Meeting these requirements is not obligatory but may be desirable.
1.2.4. May be desirable but are not always essential.
1.2.5. Harder to define and agree on.
1.2.6. Explain the way in which the product should work (how it should behave).
1.2.7. Outline quality attributes of the system.
1.2.8. Usually defined by software engineers, developers, software architects or other technical experts.
1.2.9. Can be documented and understood as a quality attribute.
1.2.10. Identify how the system SHOULD do it.
2. Activity 1
2.1. Functional Req. for Blue
2.2. Non-Functional Req. for Pink
2.3. Q1: Which of these are functional requirements?
2.3.1. Users of the library will be either normal or staff
2.3.1.1. Vu Dinh The Nam
2.3.1.1.1. define user roles
2.3.1.2. LeThuTrang
2.3.1.2.1. Identify what the system MUST or MUST NOT do.
2.3.1.3. Chu Gia Long + Bach Quang Hung
2.3.1.3.1. Describe user responsibilities and permissions.
2.3.2. The library contains one million books
2.3.3. If a user asks a book that has been borrowed, her request shall be inserted in a waiting list
2.3.3.1. Luong Hai Yen
2.3.3.1.1. System has the ability to do this task
2.3.3.2. Nguyễn Công Tuấn
2.3.3.2.1. Defines a specific behavior of the system in handling user requests
2.3.3.3. DoHoangMinhDuc
2.3.3.3.1. help understand the function of the system
2.3.3.4. HoangVuMinh
2.3.3.4.1. Ensures the system will meet user requirements.
2.3.3.5. Le Thi Anh Ngoc
2.3.3.5.1. Will allow system to perform, system must do
2.3.3.6. VuTriNguyen
2.3.3.6.1. Identify what the system MUST or MUST NOT do.
2.3.3.7. D.T Kim Oanh + Dinh Thanh Hien
2.3.3.8. Chu Gia Long + Bach Quang Hung
2.3.3.8.1. Specify system requirements.
2.3.3.9. Vu Dinh The Nam
2.3.3.9.1. Describe system function
2.3.3.10. LeThuTrang
2.3.3.10.1. Ensures the system will meet user requirements.
2.3.3.11. Le Vu Dieu Thuy
2.3.4. Staff shall have no priority in borrowing books
2.3.4.1. Vu Dinh The Nam
2.3.4.1.1. Define a specific role
2.3.5. A user will be able to borrow a book
2.3.5.1. DoHoangMinhDuc
2.3.5.1.1. define the function of the system
2.3.5.2. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.3.5.2.1. This describes a specific action a user can perform within the library system.
2.3.5.3. HoangVuMinh
2.3.5.3.1. Ensures the system will meet user requirements.
2.3.5.4. Luong Hai Yen
2.3.5.4.1. The function which the system must do
2.3.5.5. VuTriNguyen
2.3.5.5.1. Help understand the functions of the system.
2.3.5.6. Duong Thi Kim Oanh + Dinh Thanh Hien
2.3.5.6.1. understand the system func
2.3.5.7. Luong Tien Thuan
2.3.5.7.1. it defines a specific function or action that the system must be able to perform
2.3.5.8. Vu Dinh The Nam
2.3.5.8.1. Define a system function
2.3.5.9. Chu Gia Long + Bach Quang Hung
2.3.5.9.1. Specify the function of a system.
2.3.5.10. Doan Thi Huong Nhai
2.3.5.10.1. ensure the system meet user's requirement
2.3.5.11. Le Vu Dieu Thuy
2.3.5.11.1. define the system function
2.3.5.12. Dao Thanh Hang, Dinh Thao Nguyen
2.3.5.12.1. Straightforward to define and agree on.
2.3.5.13. Lê Huyền Linh
2.3.5.13.1. this requirement define a specific function from the system that allow an user to borrow a book
2.3.5.14. Nguyen Thanh Trung
2.3.5.14.1. define a system function
2.3.6. A staff person will be able to borrow a book
2.3.6.1. Vu Dinh The Nam
2.3.6.1.1. Define a system function
2.3.6.2. Dao Thanh Hang, Dinh Thao Nguyen
2.3.6.2.1. define a specific function that allow a staff to borrow a book
2.4. Q3: Which of these are functional requirements?
2.4.1. A person can enroll in a course
2.4.1.1. Lê Huyền Linh
2.4.1.1.1. Because this requirement ask the system to have a function that a person can enroll a course
2.4.1.2. DoHoangMinhDuc
2.4.1.2.1. essential operation of the system.
2.4.1.3. Luong Hai Yen
2.4.1.3.1. help understand the functions of the system
2.4.1.4. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.4.1.4.1. This describes a specific action that a user can perform within the system.
2.4.1.5. Đào Thanh Hằng + Đinh Thảo Nguyên
2.4.1.5.1. Because it help understand the functions of the system: enroll in a course
2.4.1.6. HoangVuMinh
2.4.1.6.1. Ensures the system will meet user requirements.
2.4.1.7. Le Thi Anh Ngoc
2.4.1.7.1. Can be understood as the function of a system through an use case: enroll the course
2.4.1.8. LeThuTrang
2.4.1.8.1. Help understand the functions of the system.
2.4.1.9. Vu Dinh The Nam
2.4.1.9.1. specific function
2.4.1.10. VuTriNguyen
2.4.1.10.1. Ensures the system will meet user requirements.
2.4.1.11. Luong Tien Thuan
2.4.1.11.1. it outlines the system's functionality to allow user to enroll in a course
2.4.1.12. Doan Thi Huong Nhai
2.4.1.12.1. are essential to the system operation
2.4.1.13. Le Vu Dieu Thuy
2.4.1.13.1. Ensures the system will meet user requirements
2.4.1.14. Nguyen Thanh Trung
2.4.1.14.1. essential operation of the system
2.4.2. Only 10 persons max can enroll to this course
2.4.2.1. Pham Van Du
2.4.2.2. HoangVuMinh
2.4.2.2.1. set a limit on the maximum number of person who can enroll the course
2.4.3. A course is taught by a professor
2.4.3.1. Pham Van Du
2.4.3.1.1. Define the relationship between entities of this system
2.4.4. A professor is not a student
2.4.5. Each course terminates with an exam
2.4.5.1. DoHoangMinhDuc
2.4.5.1.1. essential operation of the system.
2.4.5.2. Luong Hai Yen
2.4.5.2.1. The function of the system
2.4.5.3. Pham Van Du
2.4.5.3.1. This indecates a specific action that should be supported by this system
2.4.5.4. HoangVuMinh
2.4.5.4.1. describe a specific event or action associated with the termination of a course (exam)
2.4.5.5. Đào Thanh Hằng + Đinh Thảo Nguyên
2.4.5.5.1. Because it is essential to system operations
2.4.5.6. Vu Dinh The Nam
2.4.5.6.1. specific function
2.4.5.7. Doan Kim Oanh+ Ngo Thi Nguyet+ Vuong Nguyet Ha
2.4.5.7.1. This defines a characteristic of how courses are structured within the system.
2.4.6. Every exam produces a ranking of all participants
2.4.7. A student is a person
2.5. Q2: Which of these are non-functional requirements
2.5.1. Pressing the switch, the room shall get lightened in less than one second
2.5.1.1. HoangVuMinh
2.5.1.1.1. specific a performance characteristic
2.5.1.2. DoHoangMinhDuc
2.5.1.2.1. Help understand the performance of the system.
2.5.1.3. LeThuTrang
2.5.1.3.1. Ensures the product meets user expectations.
2.5.1.4. Dinh Thanh Hien + D.T. Kim Oanh
2.5.1.5. Đào Thanh Hằng + Đinh Thảo Nguyên
2.5.1.5.1. Because it specifies a performance characteristic (less than one second)
2.5.2. If the room is dark, pressing the switch it shall get lightened
2.5.3. The light in the room must be sufficient to read
2.5.3.1. Lê Huyền Linh
2.5.3.1.1. This requirement related to the performance requirement, which is bright enough to read
2.5.3.2. Nguyễn Công Tuấn + Tú Uyên
2.5.3.2.1. It specifies a quality attribute (sufficient light for reading) that the system should achieve
2.5.3.3. HoangVuMinh
2.5.3.3.1. Specifies the characteristic of this light
2.5.3.4. DoHoangMinhDuc
2.5.3.4.1. Help understand the performance of the system.
2.5.3.5. Vu Dinh The Nam
2.5.3.5.1. Specifies the qualities or characteristic of this light
2.5.3.6. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.5.3.6.1. This defines a quality attribute of the system (lighting brightness) rather than its basic behavior.
2.5.3.7. Le Thi Anh Ngoc
2.5.3.7.1. Explain the way in which the product should work (how it should behave).
2.5.3.8. VuTriNguyen
2.5.3.8.1. Identify how the system SHOULD do it.
2.5.3.9. Luong Hai Yen
2.5.3.9.1. The quality attribution of the system
2.5.3.10. D.T.Kim Oanh + Dinh Thanh Hien
2.5.3.10.1. It outlines a trait or feature that the system (room) is required to possess
2.5.3.11. Luong Tien Thuan
2.5.3.11.1. it describes a quality attribute or characteristic that the system (room) must have
2.5.3.12. LeThuTrang
2.5.3.12.1. Explain the way in which the product should work (how it should behave).
2.5.3.13. Đào Thanh Hằng + Đinh Thảo Nguyên
2.5.3.13.1. it describes a quality (sufficient light) related to the performance or characteristics of the system
2.5.3.14. Le Vu Dieu Thuy
2.5.3.14.1. Special the qualities or charayeristic of the light
2.5.3.15. Doan Thi Huong Nhai
2.5.3.15.1. explain how the system works
2.5.3.16. Nguyen Thanh Trung
2.5.3.16.1. special the qualities of the light
2.5.4. If someone is reading then the light must stay on
2.5.5. After two minutes that the room is empty the light must switch off
2.5.5.1. Vu Dinh The Nam
2.5.5.1.1. nearly like a func-re but it contain time constraint
2.5.5.2. DoHoangMinhDuc
2.5.5.2.1. explain how the function should work
2.5.5.3. Đào Thanh Hằng + Đinh Thảo Nguyên
2.5.5.3.1. it specifies a timing characteristic (two minutes) related to how it should behave
2.5.5.4. Nguyễn Công Tuấn + Tú Uyên
2.5.5.4.1. It states the availability of the system
2.6. Q4: Which of these are functional requirements? The iPhone.....
2.6.1. can function as a camera
2.6.1.1. Dao Thanh Hang, Dinh Thi Thao Nguyen
2.6.1.1.1. Help understand the function of the system.
2.6.1.2. Pham Van Du
2.6.1.2.1. state the function of mobile phone nowadays
2.6.1.3. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.6.1.3.1. This describes a specific action the iPhone can perform.
2.6.1.4. DoHoangMinhDuc
2.6.1.4.1. define a function of the system, easy to agree on and it's obligatory
2.6.1.5. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.6.1.5.1. This defines a capability the iPhone offers.
2.6.1.6. HoangVuMinh
2.6.1.6.1. describe one of the function of the phone
2.6.1.7. Luong Hai Yen
2.6.1.7.1. The functions of the phone
2.6.1.8. Vu Dinh The Nam
2.6.1.8.1. phone function
2.6.1.9. Le Thi Anh Ngoc
2.6.1.9.1. define the function of phone
2.6.1.10. Dinh Thanh Hien+ D.T. Kim Oanh+ Luong Tien Thuan
2.6.1.10.1. define one of the function of phone
2.6.1.11. VuTriNguyen
2.6.1.11.1. define the phone function's
2.6.1.12. Le Vu Dieu Thuy
2.6.1.12.1. define the function of the phone
2.6.1.13. Nguyen Thanh Trung
2.6.1.13.1. describe the function of the phone
2.6.2. has a camera with 2.0 megapixels with geo-tagging
2.6.3. is a portable media player
2.6.3.1. Dao Thanh Hang, Dinh Thi Thao Nguyen
2.6.3.1.1. Define the system or an element of it.
2.6.3.2. DoHoangMinhDuc
2.6.3.2.1. define a function of the system, easy to agree on and it's obligatory
2.6.3.3. Luong Hai Yen
2.6.3.3.1. The function of the system
2.6.3.4. Vu Dinh The Nam
2.6.3.4.1. phone function
2.6.3.5. Dinh Thanh Hien+ D.T. Kim Oanh+ Luong Tien Thuan
2.6.3.5.1. phone function
2.6.3.6. Doan Thi Huong Nhai
2.6.3.6.1. phone function
2.6.4. is connected to a PC via a USB plug
2.6.4.1. Vu Dinh The Nam
2.6.4.2. Pham Van Du
2.6.5. includes a digital compass in the 3GS model
2.6.6. renders a virtual keyboard by its multi-touch screen
2.6.7. offers an Internet client
2.6.7.1. Dao Thanh Hang, Dinh Thi Thao Nguyen
2.6.7.1.1. Are essential to system operations.
2.6.7.2. Luong Hai Yen
2.6.7.2.1. The function of the system
2.6.7.3. Ngô Thị Nguyệt + Vương Nguyệt Hà + Đoàn Kim Oanh
2.6.7.3.1. This specifies a feature that allows users to access the internet.
2.6.7.4. DoHoangMinhDuc
2.6.7.4.1. define an essential function of the system
2.7. Q5: Ticket Sales System
2.7.1. Users must be able to browse for events by name or date or venue.
2.7.1.1. Usability - ease of learning, ease of use
2.7.2. Searching for events by keywords should also be possible
2.7.2.1. Usability - ease of learning, ease of use
2.7.3. User will select ticket price from those offered and also specify the number of tickets they require.
2.7.4. Users must be able to choose their seats and purchase tickets 24/7.
2.7.5. Only registered customers can buy tickets.
2.7.5.1. Access - permissions, who has access to which functionality and how
2.7.5.2. Access - permissions, who has access to which functionality and how
2.7.6. All data is to be backed up nightly.
2.7.6.1. Backup & recovery - protection against loss of data
2.7.6.2. Security - Security levels for protection of data
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.7.8. Daily reports of ticket sales must be generated. These must be retained for two years.
2.7.9. The system should display availability of the tickets within five seconds.
2.7.9.1. Archiving and retention - duration, methods, eventual deletion
2.7.10. It should not be possible to double-book tickets (i.e. buy a ticket that has already been sold).
2.7.10.1. Capacity - Data volumes, transaction volumes, user volumes
2.7.11. Categories of Non-Functional Req.
2.7.11.1. Usability - ease of learning, ease of use
2.7.11.2. Capacity - Data volumes, transaction volumes, user volumes
2.7.11.3. Robustness - reliability, data integrity, user error
2.7.11.4. Availability - timeframe for availability of functionality
2.7.11.5. Backup & recovery - protection against loss of data
2.7.11.6. Performance - speed of processing transactions
2.7.11.7. Access - permissions, who has access to which functionality and how
2.7.11.8. Archiving and retention - duration, methods, eventual deletion
2.7.11.9. Security - Security levels for protection of data