1. Functional Requirement vs Non-functional Requirement
1.1. Functional Requirements
1.1.1. Help understand the functions of the system.
1.1.2. Explain 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. Usually defined by the user.
1.2. Non Functional Requirements
1.2.1. The system will not work with non-functional requirements alone.
1.2.2. Define the system or an element of it.
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. Help understand the performance of the system.
1.2.6. Harder to define and agree on.
1.2.7. Explain the way in which the product should work (how it should behave).
1.2.8. Outline quality attributes of the system.
1.2.9. Usually defined by software engineers, developers, software architects or other technical experts.
1.2.10. Can be documented and understood as a quality attribute.
1.2.11. Identify how the system SHOULD do it.
2. Activity 1
2.1. Functional Req. for Blue
2.2. Non-Functional Req. for Red
2.3. Q1: Which of these are functional requirements?
2.3.1. Users of the library will be either normal or staff
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. Chu Quang Huy (2001040095)
2.3.3.1.1. Defines a functional aspect of how the system should manage user requests for borrowed books
2.3.3.2. Pham Thi Phuong Chi
2.3.3.2.1. This describes what the system should do
2.3.3.3. Bui Tuan Nam
2.3.3.3.1. describe a specific behavior that the system must exhibit
2.3.3.4. Luong Duc Minh
2.3.3.4.1. Ensures the system will meet user requirements.
2.3.3.5. Le Vu Minh
2.3.3.5.1. This describes a function related to handling book requests and waiting lists when a user borrows a book
2.3.3.6. Le Tat Thanh
2.3.3.6.1. Help understand the functions of the system.
2.3.3.7. Nguyen Huu Dang
2.3.3.7.1. Help understand the performance of the system.
2.3.3.7.2. Help understand the performance of the system
2.3.3.8. Nguyen Minh Phuc
2.3.3.8.1. the requirement specifies the behavior that the system should exhibit when a user requests a book that is currently borrowed – the system should insert the user's request into a waiting list for that book
2.3.3.9. Vu Thanh Cong
2.3.3.9.1. Defines a specific behavior of the system in handling user requests
2.3.3.10. Do Yen Nhi
2.3.3.10.1. It describes a specific behavior of the system – handling requests for books that are currently borrowed by inserting them into a waiting list.
2.3.3.11. Vu Van Lam
2.3.3.11.1. This requirement ensures fair access to popular books when multiple users want to borrow them.
2.3.3.11.2. Ensures the system will meet user requirements.
2.3.3.12. Nguyen Thi Lua
2.3.3.12.1. Ensures the system will meet user requirements.
2.3.3.13. Ngo Thi Huyen Trang
2.3.3.13.1. this requirement oulines a specific functionality.
2.3.3.14. Do Huu Dat
2.3.3.14.1. Specify condition and the corresponding functionality or behavior that the system must exhibit
2.3.3.15. Truong Ha Huynh Thai
2.3.3.15.1. Explain the way in which the product should work (how it should behave).
2.3.3.16. Pham Thuy Anh
2.3.3.16.1. This describes a system response to a specific event (book unavailable), defining a function the system must perform.
2.3.3.17. Chu Quang Huy (2001040096)
2.3.3.17.1. Handle a specific action of user
2.3.3.18. Nguyen Thi Diep Anh
2.3.3.18.1. This requirement describe particular behavior that the system is required to demonstrate
2.3.3.19. Nguyen Thi Duyen
2.3.3.19.1. help understand the function of the system
2.3.4. Staff shall have no priority in borrowing books
2.3.4.1. Nguyen Minh Quang
2.3.4.1.1. Define a constraint on the system behavior, how the library system should behave in terms of user interactions
2.3.4.2. Bui Tuan Nam
2.3.4.2.1. Specifies a rule or constraint regarding the borrowing process within the library system
2.3.4.3. Chu Quang Huy (2001040095)
2.3.4.3.1. Specifies a rule or behavior that the system must adhere to regarding the borrowing of books by staff members
2.3.4.4. Vu Van Lam
2.3.4.4.1. This requirement establishes equality in borrowing privileges between staff and regular users.
2.3.4.4.2. This requirement ensures fair access to popular books when multiple users want to borrow them.
2.3.4.5. Do Yen Nhi
2.3.4.5.1. It specifies a constraint on the system's behavior – that staff should not have priority in borrowing books.
2.3.4.6. Nguyen Thi Lua
2.3.4.6.1. It definees a limit on the system's behavior – that staff should not have priority in borrowing books.
2.3.4.7. Ngo Thi Huyen Trang
2.3.4.7.1. Specifies a rule or constraint regarding the borrowing process within the library system
2.3.4.8. Nguyen Thi Diep Anh
2.3.4.8.1. This requirement specifies that staff members should not receive any special priority or privileges when it comes to borrowing books. It ensures that all users, regardless of their role within the library, are treated equally and have an equal opportunity to borrow books
2.3.5. A user will be able to borrow a book
2.3.5.1. Bui Le Minh Quang
2.3.5.1.1. This describe what the system does (in this case, the user is able to borrow a book), so this is a function of the system, and therefore, a functional system.
2.3.5.2. Vu Thanh Cong
2.3.5.2.1. it defines a specific function or action that the system must be able to perform
2.3.5.3. Le Tat Thanh
2.3.5.3.1. Ensures the system will meet user requirements.
2.3.5.4. Dong Trung Anh
2.3.5.4.1. describes a specific action that the system should support - allowing a user to borrow a book.
2.3.5.5. Do Huu Dat
2.3.5.5.1. Explain the characteristics that a system is expected to have.
2.3.5.6. Lê Vũ Minh
2.3.5.6.1. This describes a function that allows a user to borrow books from the library
2.3.5.7. Nguyễn Hữu Đăng
2.3.5.7.1. Explain the characteristics that a system is expected to have.
2.3.5.8. Dao Tuyet Le
2.3.5.8.1. Explain the characteristics that a system is expected to have.
2.3.5.9. Phạm Thúy Anh
2.3.5.9.1. This directly states a specific action that the system must enable, making it a functional requirement.
2.3.5.10. Vu Quoc Huy
2.3.5.10.1. describe what the task of system
2.3.5.11. Luong Duc Minh
2.3.5.11.1. Meeting these requirements is obligatory.
2.3.5.12. Nguyen Minh Phuc
2.3.5.12.1. It outlines a specific function or capability that the system must provide, which is the ability for a user to borrow a book.
2.3.5.13. Do Yen Nhi
2.3.5.13.1. the system provide the ability for user to borrow book
2.3.5.14. Le Quoc Vu
2.3.5.14.1. Specifies a particular operation that the system must facilitate - enabling a user to loan a book.
2.3.5.15. Bui Tuan Nam
2.3.5.15.1. Specifies a fundamental functionality that the library system must provide – the capability for users to borrow books
2.3.5.16. Vu Van Lam
2.3.5.16.1. This requirement outlines a core function of the library system, enabling users to borrow books.
2.3.5.17. Pham Thi Phuong Chi
2.3.5.17.1. This describes a function of the system
2.3.5.18. Le Anh Phan
2.3.5.18.1. Outline a user action and the system's response, making it a functional requirement
2.3.5.19. Nguyen Thi Diep Anh
2.3.5.19.1. ensures that users of the library have the ability to borrow books. It implies that there should be a mechanism in place that allows users to check out books from the library's collection
2.3.5.20. Nguyen Thi Duyen
2.3.5.20.1. Ensure the system will meet the user's requirement.
2.3.5.21. Truong Ha Huynh Thai
2.3.5.21.1. Ensures the system will meet user requirements.
2.3.6. A staff person will be able to borrow a book
2.3.6.1. Le Tat Thanh
2.3.6.1.1. Straightforward to define and agree on.
2.3.6.2. Dong Trung Anh
2.3.6.2.1. describes the action of a staff person being able to borrow a book.
2.3.6.3. Nguyen Huu Dang
2.3.6.3.1. Explain the characteristics that a system is expected to have.
2.3.6.4. Vu Quoc Huy
2.3.6.4.1. describe the task of system
2.3.6.5. Ngo Tuan Anh
2.3.6.5.1. Details the capability for a staff member to borrow a book.
2.3.6.6. Do Huu Dat
2.3.6.6.1. Explain the characteristics that a system is expected to have.
2.3.6.7. Do Yen Nhi
2.3.6.7.1. It specifies a capability related to staff members, indicating that they can borrow books
2.3.6.8. Vu Thanh Cong
2.3.6.8.1. define a specific function that allow a staff to borrow a book
2.3.6.9. Bui Tuan Nam
2.3.6.10. Pham Thuy Anh
2.3.6.10.1. This defines a specific action, it applies to a particular user type (staff), further specifying system behavior.
2.3.6.11. Nguyen Thi Diep Anh
2.3.6.11.1. This requirement acknowledges that staff members of the library should also have the capability to borrow books. It means that the library system should provide staff members with the necessary privileges and functionality to borrow books like any other user
2.3.6.12. Nguyen Ngoc Nam Phuong
2.3.6.12.1. Describe a specific functionality related to staff member
2.3.6.13. Vu Van Lam
2.3.6.13.1. This requirement extends borrowing functionality to staff members as well.
2.3.6.14. Truong Ha Huynh Thai
2.3.6.14.1. Straightforward to define and agree on.
2.4. Q2: Which of these are non-functional requirements
2.4.1. If the room is dark, pressing the switch it shall get lightened
2.4.1.1. This statement specifies a time constraint for the system's response.
2.4.1.2. Chu Quang Huy (2001040095)
2.4.1.2.1. Sets a standard for the quality of the light, defines a quality or attribute that the system (lighting in the room) must possess rather than specifying a particular function or behavior
2.4.2. Pressing the switch, the room shall get lightened in less than one second
2.4.2.1. Vu Thanh Cong
2.4.2.1.1. Help understand the performance of the system.
2.4.2.2. Nguyen Huu Dang
2.4.2.2.1. Identify how the system SHOULD do it.
2.4.2.3. Luong Duc Minh
2.4.2.3.1. Meeting these requirements is not obligatory but may be desirable.
2.4.2.4. Pham Thi Phuong Chi
2.4.2.4.1. This statement is related to the performance of the system
2.4.2.5. Chu Quang Huy (2001040095)
2.4.2.5.1. Specifies a constraint related to the performance or response time of the system
2.4.2.6. Pham Thuy Anh
2.4.2.6.1. This specifies a performance attribute of the action "lighten the room". It states that the system must perform this action within a certain time period.
2.4.2.7. Nguyen Thi Diep Anh
2.4.2.7.1. This requirement specifies a performance aspect of the lighting system.
2.4.2.8. Nguyen Minh Phuc
2.4.2.8.1. It specifies a particular function that the system (in this case, a lighting system) must perform when a switch is pressed – namely, the room should be illuminated, and this action should occur in less than one second
2.4.2.9. Do Yen Nhi
2.4.2.9.1. It specifies a performance criterion (less than one second) for how quickly the light should be turned on.
2.4.2.10. Bui Tuan Nam
2.4.2.10.1. specifying the time it takes for the room to get lightened
2.4.2.11. Nguyen Thi Duyen
2.4.2.11.1. Meeting this requirement is not obligatory but essential.
2.4.3. If someone is reading then the light must stay on
2.4.3.1. This describes a quality attribute (sufficient light for reading).
2.4.3.2. Bui Tuan Nam
2.4.3.2.1. specifying the requirement for the light to stay on when someone is reading
2.4.4. After two minutes that the room is empty the light must switch off
2.4.4.1. Le Vu Minh
2.4.4.1.1. This specifies a condition for the system's behavior (automatic light switch-off after a certain time of inactivity).
2.4.4.2. Dao Tuyet Le
2.4.4.2.1. Explain the way in which the product should work (how it should behave).
2.4.4.3. Do Yen Nhi
2.4.4.3.1. It specifies a timing criterion (two minutes) for when the system should perform a certain action (switch off the light).
2.4.4.4. Chu Quang Huy (2001040095)
2.4.4.4.1. Specifies a timing condition for when the light should turn off based on the room being empty
2.4.4.5. Nguyen Huu Dang
2.4.4.5.1. Identify how the system SHOULD do it.
2.4.4.6. Vu Thanh Cong
2.4.4.6.1. nearly like a func-re but it contain time constraint
2.4.4.7. Bui Tuan Nam
2.4.4.7.1. specifying the time delay for turning off the light after the room is empty
2.4.4.8. Nguyen Thi Duyen
2.4.4.8.1. Ensure the product meets user expectations.
2.4.4.9. luong Duc Minh
2.4.4.9.1. Identify how the system SHOULD do it.
2.4.4.10. Nguyen Thi Lua
2.4.4.10.1. nearly like a func-re but it contain time constraint
2.4.5. Pressing the switch, the room shall get lightened
2.4.6. The light in the room must be sufficient to read
2.4.6.1. Le Tat Thanh
2.4.6.1.1. it describes a quality (sufficient light) related to the performance or characteristics of the system
2.4.6.2. Dong Trung Anh
2.4.6.2.1. specifies a quality or attribute of the light (sufficient brightness for reading)
2.4.6.3. Le Vu Minh
2.4.6.4. Vu Thanh Cong
2.4.6.5. Do Huu Dat
2.4.6.5.1. focus on a quality attribute (sufficient light for reading) rather than a specific function
2.4.6.6. Vu Quoc Huy
2.4.6.6.1. It specifies a quality criterion (sufficient light for reading) that the system must meet.
2.4.6.7. Nguyen Thi Diep Anh
2.4.6.7.1. This requirement addresses the usability aspect of the lighting system. It states that the light provided by the system should be of sufficient quality and intensity to support reading activities
2.4.6.8. Nguyen Huu Dang
2.4.6.8.1. Ensures the product meets user expectations.
2.4.6.9. Ngo Tuan Anh
2.4.6.9.1. Defines a characteristic or property of the light
2.4.6.10. Le Quoc Vu
2.4.6.10.1. Guarantees that the product satisfies user requirements.
2.4.6.11. Bui Tuan Nam
2.4.6.11.1. specifying the quality of light required for reading
2.4.6.12. Luong Duc Minh
2.4.6.13. Truong Ha Huynh Thai
2.4.6.13.1. Identify how the system SHOULD do it.
2.5. Q3: Which of these are functional requirements?
2.5.1. A person can enroll in a course
2.5.1.1. Dong Trung Anh
2.5.1.1.1. describes the action of a person enrolling in a course.
2.5.1.2. Le Tat Thanh
2.5.1.2.1. Explain the characteristics that a system is expected to have.
2.5.1.3. Le Vu Minh
2.5.1.3.1. Describes the ability for a person to enroll in a course when using the system
2.5.1.4. Nguyen Thi Diep Anh
2.5.1.4.1. This requirement indicates that the system should provide the functionality for individuals to enroll in a course
2.5.1.5. Vu Thanh Cong
2.5.1.5.1. Ensures the system will meet user requirements.
2.5.1.6. Ngo Tuan Anh
2.5.1.6.1. Details the process of an individual registering for a course.
2.5.1.7. Nguyen Huu Dang
2.5.1.7.1. Explain the characteristics that a system is expected to have
2.5.1.8. Chu Quang Huy (2001040095)
2.5.1.8.1. Describes a specific functionality or action that the system should support, which is allowing individuals to enroll in a course
2.5.1.9. Do Yen Nhi
2.5.1.10. Bui Tuan Nam
2.5.1.10.1. describes a specific functionality or action that the system must support
2.5.1.11. Le Quoc Vu
2.5.1.11.1. Illustrates the process of person who can enroll in a course
2.5.1.12. Nguyen Thi Lua
2.5.1.12.1. It describes the capability of the system to allow a person to enroll in a course.
2.5.2. Only 10 persons max can enroll to this course
2.5.2.1. Do Yen Nhi
2.5.2.1.1. It specifies a constraint on the system's behavior – limiting the maximum number of persons who can enroll in a course.
2.5.2.2. Pham Thi Phuong Chi
2.5.2.2.1. This defines a feature of the system
2.5.2.3. Do Huu Dat
2.5.2.3.1. Specify a limit on the enrollment functionality of the system
2.5.3. A course is taught by a professor
2.5.3.1. Le Vu MInh
2.5.3.1.1. Specifies a relationship between course and professor management.
2.5.3.2. Chu Quang Huy (2001040095)
2.5.3.2.1. Specifies a relationship and a specific functionality of the system: the ability of a course to be taught by a professor
2.5.4. A professor is not a student
2.5.4.1. Bui Le Minh Quang
2.5.4.1.1. This describe what the system does (i.e, define what a product must do and what its features and functions are.) In this case, this requirements describes the "what is (or is not): A professor is NOT a students.
2.5.5. Each course terminates with an exam
2.5.5.1. Le Tat Thanh
2.5.5.1.1. Meeting these requirements is obligatory.
2.5.5.2. Le Vu Minh
2.5.5.2.1. Describes a specific phase in the course lifecycle, which is taking an exam
2.5.5.3. Do Huu Dat
2.5.5.3.1. Define a specific characteristic or behavior that the system must exhibit
2.5.5.4. Vu Quoc Huy
2.5.5.4.1. It describes a specific behavior of the system – the termination of each course with an exam.
2.5.5.5. Nguyen Huu Dang
2.5.5.6. Vu Thanh Cong
2.5.5.6.1. describe a specific event or action associated with the termination of a course (exam)
2.5.5.7. Nguyen Thi Lua
2.5.5.7.1. Explain the characteristics that a system is expected to have
2.5.5.8. Define the system or an element of it.
2.5.6. Every exam produces a ranking of all participants
2.5.6.1. Le Tat Thanh
2.5.6.1.1. Usually defined by the user.
2.5.6.2. Le Vu Minh
2.5.6.2.1. Specifies a result from exams
2.5.6.3. Nguyen Huu Dang
2.5.6.3.1. Identify what the system MUST do.
2.5.6.4. Do yen Nhi
2.5.6.4.1. It specifies a behavior of the system – producing a ranking of all participants after every exam.
2.5.6.5. Do Huu Dat
2.5.6.5.1. Specify a capability or behavior that the system must provide
2.5.6.6. Pham Thi Phuong Chi
2.5.6.6.1. This describes what the system should do
2.5.7. A student is a person
2.6. Q4: Which of these are functional requirements? The iPhone.....
2.6.1. can function as a camera
2.6.1.1. Hoang Thai Duong-2101040066
2.6.1.1.1. It describes the iphone's functionality
2.6.1.2. Dong Trung Anh
2.6.1.2.1. describes one of the functions of the iPhone - functioning as a camera.
2.6.1.3. Le Vu Minh
2.6.1.3.1. Describes how an iPhone can be used as a camera
2.6.1.4. Ngo Tuan Anh
2.6.1.4.1. Details one of the capabilities of the iPhone - serving as a camera.
2.6.1.5. Vu Thanh Cong
2.6.1.5.1. describe one of the function of the phone
2.6.1.6. Nguyen Huu Dang
2.6.1.6.1. Explain the characteristics that a system is expected to have
2.6.1.7. Bui Tuan Nam
2.6.1.7.1. Descibe the function of the phone
2.6.2. has a camera with 2.0 megapixels with geo-tagging
2.6.2.1. Hoang Thai Duong 2101040066
2.6.2.1.1. Explain the characteristics that a system is expected to have.
2.6.2.2. Do Yen Nhi
2.6.2.2.1. It specifies the features and capabilities of the camera on the iPhone.
2.6.3. is a portable media player
2.6.3.1. Hoang Thai Duong 2101040066
2.6.3.1.1. Usually defined by the user.
2.6.4. includes a digital compass in the 3GS model
2.6.4.1. Hoang Thai Duong 2101040066
2.6.4.1.1. Explain the characteristics that a system is expected to have.
2.6.4.2. Le Vu Minh
2.6.4.2.1. Describes the digital compass feature in the iPhone 3GS model
2.6.4.3. Pham Thi Phuong Chi
2.6.4.3.1. Describe the intended feature of the product
2.6.4.4. Bui Tuan Nam
2.6.4.4.1. It describes a specific functionality or component that should be present in the 3GS model
2.6.4.5. Nguyen Huu Dang
2.6.4.5.1. Explain the characteristics that a system is expected to have
2.6.4.6. Vu Quoc Huy
2.6.4.6.1. It specifies a feature of the iPhone 3GS model – the inclusion of a digital compass.
2.6.5. renders a virtual keyboard by its multi-touch screen
2.6.5.1. Le Tat Thanh
2.6.5.1.1. Straightforward to define and agree on.
2.6.5.2. Hoang Thai Duong 2101040066
2.6.5.2.1. Explain the characteristics that a system is expected to have.
2.6.5.3. Le Vu Minh
2.6.5.3.1. Describes a feature to use a virtual keyboard via multi-touch screen
2.6.5.4. Bui Tuan Nam
2.6.5.4.1. Characteristic of the system
2.6.5.5. Do Yen Nhi
2.6.5.5.1. It specifies how the iPhone provides a virtual keyboard through its multi-touch screen.
2.6.5.6. Nguyen Thi Lua
2.6.5.6.1. Describes a feature to use a virtual keyboard via multi-touch screen
2.6.6. offers an Internet client
2.6.6.1. Hoang Thai Duong
2.6.6.1.1. Ensures the system will meet user requirements.
2.6.6.2. Nguyen Minh Quang
2.6.6.2.1. Describe that the iPhone should have the capability to serve as an Internet client
2.6.6.3. Bui Le Minh Quang
2.6.6.3.1. Describe a function of a system (in this case, these requirements describe the function of offering an Internet connection) to its customers.
2.6.6.4. Pham Thi Phuong Chi
2.6.6.4.1. Describe what the phone is expected to have
2.6.6.5. Le Vu Minh
2.6.6.5.1. Describes the ability to connect to the Internet with an iPhone
2.6.6.6. Bui Tuan Nam
2.6.6.6.1. the capability to function as an Internet client
2.6.7. is connected to a PC via a USB plug
2.6.7.1. Hoang Thai Duong
2.6.7.1.1. Are essential to system operations.
2.6.7.2. Le Vu Minh
2.6.7.2.1. Describes the ability to connect with a computer
2.7. Q5: Ticket Sales System
2.7.1. Searching for events by keywords should also be possible
2.7.1.1. Usability - ease of learning, ease of use
2.7.2. User will select ticket price from those offered and also specify the number of tickets they require.
2.7.3. Users must be able to browse for events by name or date or venue.
2.7.3.1. Usability - ease of learning, ease of use
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.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. The system should display availability of the tickets within five seconds.
2.7.8.1. Performance - speed of processing transactions
2.7.8.2. Availability - timeframe for availability of functionality
2.7.9. It should not be possible to double-book tickets (i.e. buy a ticket that has already been sold).
2.7.9.1. Capacity - Data volumes, transaction volumes, user volumes
2.7.10. Daily reports of ticket sales must be generated. These must be retained for two years.
2.7.11. Categories of Non-Functional Req.
2.7.11.1. Capacity - Data volumes, transaction volumes, user volumes
2.7.11.2. Backup & recovery - protection against loss of data
2.7.11.3. Availability - timeframe for availability of functionality
2.7.11.4. Usability - ease of learning, ease of use
2.7.11.5. Performance - speed of processing transactions
2.7.11.6. Robustness - reliability, data integrity, user error
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