1. Security - security levels for protection of data
2. Functional Requirement vs Non-functional Requirement
2.1. Functional Requirements
2.1.1. Help understand the functions of the system.
2.1.2. Explhaveain the characteristics that a system is expected to have.
2.1.3. Identify what the system MUST or MUST NOT do.
2.1.4. Will allow the system to perform, even if the non-functional requirements are not met.
2.1.5. Ensures the system will meet user requirements.
2.1.6. Are essential to system operations.
2.1.7. Straightforward to define and agree on.
2.1.8. Meeting these requirements is obligatory.
2.1.9. Define the system or an element of it.
2.1.10. Usually defined by the user.
2.1.11. Can be documented and understood through a use case.
2.2. Non Functional Requirements
2.2.1. Help understand the performance of the system.
2.2.2. The system will not work with non-functional requirements alone.
2.2.3. Ensures the product meets user expectations.
2.2.3.1. Meeting these requirements is not obligatory but may be desirable.
2.2.4. May be desirable but are not always essential.
2.2.5. Harder to define and agree on.
2.2.6. Explain the way in which the product should work (how it should behave).
2.2.7. Outline quality attributes of the system.
2.2.8. Usually defined by software engineers, developers, software architects or other technical experts.
2.2.9. Can be documented and understood as a quality attribute.
2.2.10. Identify how the system SHOULD do it.
3. Activity 1
3.1. Non-Functional Req. for Pink
3.2. Functional Req. for Blue
3.3. Q1: Which of these are functional requirements?
3.3.1. Users of the library will be either normal or staff
3.3.2. The library contains one million books
3.3.3. If a user asks a book that has been borrowed, her request shall be inserted in a waiting list
3.3.3.1. Đỗ Thành Đạt
3.3.3.1.1. Identify what the system MUST or MUST NOT do.
3.3.3.2. Nguyễn Mai Hương
3.3.3.2.1. It details what can be tracked from sys when borrowing book
3.3.3.3. Đoàn Diệu Linh
3.3.3.3.1. The requirement ensures that users can request borrowed books and be added to a waiting list for future availability.
3.3.3.4. Le Manh Toan
3.3.3.4.1. Details of request of book must be tracked in the book system
3.3.3.5. Nguyễn Thế Thành
3.3.3.5.1. It describes what the product do, borrowed book will be inserted in waiting list
3.3.3.6. Nguyễn Thùy Dương
3.3.3.6.1. It details how the system MUST react to a specific situation
3.3.3.7. Kiều Hoàng Minh Hiếu
3.3.3.7.1. It outlines how the system should handle a particular situation
3.3.3.8. Vũ Thị Anh Thư
3.3.3.8.1. defines a specific behavior of the system in handling user requests
3.3.3.9. Trần Minh Đức
3.3.3.9.1. It describes how the system should handle a specific situation and what action it should take
3.3.3.10. Nguyễn Hoàng Tuấn
3.3.3.10.1. Details of what must be tracked in the system
3.3.3.11. Nguyễn Thị Thanh Thủy
3.3.3.11.1. Are essential to system operations.
3.3.3.12. Dương Thế Công
3.3.3.12.1. Behavior relate to managing user requests and wating lists
3.3.3.13. Nguyen Thi Lan Nhi
3.3.3.13.1. The system should handle such requests by inserting them into a waiting list, indicating that the user is requesting the book and should be notified or given priority once the book becomes available.
3.3.4. Staff shall have no priority in borrowing books
3.3.4.1. Dương Thế Công
3.3.4.1.1. The statement specifies a behavior related to the borrowing process, indicating that staff should not have priority.
3.3.5. A user will be able to borrow a book
3.3.5.1. Đinh Vũ Thanh Huyền
3.3.5.1.1. the requirement describe the action that the library system must support
3.3.5.2. Đoàn Diệu Linh
3.3.5.2.1. it describes a specific action or capability that the library system should provide
3.3.5.3. Nguyễn Hoàng Tuấn
3.3.5.3.1. A function that a library system should have
3.3.5.4. Phạm Quang Hải
3.3.5.4.1. it outlines a functionality that the library system needs to provide
3.3.5.5. Nguyễn Thị Lan Nhi
3.3.5.5.1. Explain the characteristics that a system is expected to have.
3.3.5.6. Nguyễn Thùy Dương
3.3.5.6.1. It states that a user should be able to borrow a book.
3.3.5.7. Trần Văn Sỹ
3.3.5.7.1. Ensures the system will meet user requirements.
3.3.5.8. Đỗ Thành Đạt
3.3.5.8.1. Explain the characteristics that a system is expected to have.
3.3.5.9. Phạm Thị Khánh Ly
3.3.5.9.1. It describe what the library system/book management system is supposed to do
3.3.5.10. Nguyễn Mai Hương
3.3.5.10.1. It outlines the function that a user can have in sys
3.3.5.11. Trịnh Tố Uyên
3.3.5.11.1. fundamental functionality of a library system
3.3.5.12. Vũ Thị Anh Thư
3.3.5.12.1. Specifies a capability that the system must provide
3.3.5.13. Kiều Hoàng Minh Hiếu
3.3.5.13.1. It describes a specific function or capability that the system must have
3.3.5.14. Đoàn Thị Phương Hồng
3.3.5.14.1. It specifies a service the system should provide: allowing a user to borrow a book.
3.3.5.15. Lê Phương Thảo
3.3.5.15.1. Because it describes a specific action or capability that the system must provide. System should allow a user to borrow a book.
3.3.5.16. Hồ Thúy Hiền
3.3.5.16.1. it states the functionality of the system
3.3.5.17. Trần Minh Đức
3.3.5.17.1. It specifies an action that the system must support.
3.3.5.18. Cấn Thị Bích Thuỷ
3.3.5.18.1. It ensure that library resources are accessible to all users
3.3.5.19. Nguyễn Thị Thanh Thủy
3.3.5.19.1. the capability that system can do
3.3.5.20. Le Manh Toan
3.3.5.20.1. A core function the book system should have, for all user in system
3.3.5.21. Dương Thế Công
3.3.5.21.1. The stathement describes a specific behavior that the system must support
3.3.6. A staff person will be able to borrow a book
3.3.6.1. Lê Phương Thảo
3.3.6.1.1. it specifies a capability the system must have, namely, allowing staff members to borrow books.
3.3.6.2. Nguyễn Quang Thanh
3.3.6.2.1. It outlines a specific functionality that the library system should support
3.3.6.3. Dương Thế Công
3.3.6.3.1. The stathement describes a specific behavior that the system must support, which is allowing staff borow a book
3.3.6.4. Đỗ Thành Đạt
3.3.6.5. Triệu Trường Giang
3.3.6.5.1. it describes a specific funtion or capability that the system must have
3.3.6.6. Le Manh Toan
3.3.6.6.1. A core function the book system should have and outline the level of users (staff)
3.3.6.7. Nguyễn Tiến Dũng
3.3.6.7.1. It specifies a certain functionality that the library system should support.
3.3.6.8. Nguyễn Hoàng Tuấn
3.3.6.8.1. Specification of what system must do
3.4. Q2: Which of these are non-functional requirements
3.4.1. Pressing the switch, the room shall get lightened in less than one second
3.4.1.1. Trịnh Tố Uyên
3.4.1.1.1. This only specifies a performance characteristic
3.4.1.2. Nguyễn Thị Thanh Thủy
3.4.1.2.1. Explain the way in which the product should work (how it should behave).
3.4.1.3. Phạm Thị Khánh Ly
3.4.1.3.1. Because in this case, the requirement is related to the performance or responsiveness of the system
3.4.1.4. Nguyễn Quang Thanh
3.4.1.4.1. It specifies a constraint on the response time of the system
3.4.1.5. Le Manh Toan
3.4.1.5.1. Specifies the time taken for a specified switch to press
3.4.1.6. Trần Minh Đức
3.4.1.6.1. It specifies a performance characteristic (response time) that the system should meet
3.4.1.7. Nguyễn Mai Hương
3.4.1.7.1. It specifies the amount of time that the system must perform
3.4.1.8. Hồ Thúy Hiền
3.4.1.8.1. it states the performance of the system
3.4.1.9. Vũ Thị Anh Thư
3.4.1.9.1. defines a performance characteristic (response time) of the system
3.4.1.10. Nguyễn Thùy Dương
3.4.1.10.1. It specifies a performance characteristic rather than a specific function.
3.4.1.11. Cấn Thị Bích Thuỷ
3.4.1.11.1. It is concerned with the performance or responsiveness of the system.
3.4.1.12. Phạm Quang Hải
3.4.1.12.1. indicating a non-functional requirement that pertains to the performance or timing aspects of the lighting system
3.4.1.13. Đỗ Thành Đạt
3.4.1.13.1. help understand the performance of the system.
3.4.1.14. Dương Thế Công
3.4.1.14.1. specifies a performance characteristic (response time) and is therefore a non-functional requirement
3.4.1.15. Nguyễn Hoàng Tuấn
3.4.1.15.1. The time taken for a light to turn on
3.4.1.16. Kiều Hoàng Minh Hiếu
3.4.1.16.1. a constraint on the system's performance
3.4.1.17. Nguyen Thi Lan Nhi
3.4.1.17.1. This requirement specifies the expected behavior of the system, stating that when the switch is pressed, the room should be illuminated within a specific time frame (less than one second).
3.4.1.18. Đoàn Diệu Linh
3.4.1.18.1. This requirement specifies a performance characteristic, specifically the response time of the system
3.4.2. If the room is dark, pressing the switch it shall get lightened
3.4.3. The light in the room must be sufficient to read
3.4.3.1. Trần Minh Đức
3.4.3.1.1. It specifies a quality attribute (sufficient light for reading) that the system should achieve.
3.4.3.2. Le Manh Toan
3.4.3.2.1. usability - system facilitates sufficient light for user
3.4.3.3. Lê Phương Thảo
3.4.3.3.1. It does not describe the main function of the system,it describes the environmental factor (light) necessary to perform a specific activity (reading).
3.4.3.4. Dương Thế Công
3.4.3.4.1. specifies a quality criterion related to the performance of the light (sufficiency for reading),
3.4.3.5. Vũ Thị Anh Thư
3.4.3.5.1. specifies a quality (sufficiency of light) that the system must possess
3.4.3.6. Triệu Trường Giang
3.4.3.6.1. specifies a state of light that fulfill the requirement of the user ( suffcient to read)
3.4.3.7. Phạm Thị Khánh Ly
3.4.3.8. Trần Văn Sỹ
3.4.3.8.1. Ensures the product meets user expectations.
3.4.3.9. Kiều Hoàng Minh Hiếu
3.4.3.9.1. a quality attribute related to the light produced by the system
3.4.3.10. Mai Đức Đạt
3.4.3.10.1. states a specific criteria (sufficient light for reading) that the system must meet.
3.4.3.11. Đỗ Thành Đạt
3.4.3.12. Cấn Thị Bích Thủy
3.4.3.12.1. It is concerned with the usability or user experience aspect of the system (related to the level of lighting in the room).
3.4.3.13. Nguyen Thii Lan Nhi
3.4.3.13.1. This requirement specifies a desired outcome for the system, stating that the light in the room should be of sufficient intensity to enable reading.
3.4.4. If someone is reading then the light must stay on
3.4.4.1. Le Manh Toan
3.4.4.1.1. Available light whenever someone reading (overnight,..)
3.4.4.2. Mai Đức Đạt
3.4.4.2.1. defines a certain condition and the resulting action.
3.4.5. After two minutes that the room is empty the light must switch off
3.4.5.1. Nguyễn Thị Thanh Thủy
3.4.5.1.1. Explain the way in which the product should work (how it should behave).
3.4.5.2. Trần Văn Sỹ
3.4.5.2.1. Explain the way in which the product should work (how it should behave).
3.4.5.3. Vũ Thị Thơm
3.4.5.4. Phạm Bảo Ngọc
3.4.5.4.1. define how a system should perform its functions.
3.4.5.5. Nguyễn Hoàng Tuấn
3.4.5.5.1. Availability of the light when the room is empty
3.4.5.6. Nguyễn Thế Thành
3.4.5.6.1. explain the way that the product should perform
3.4.5.7. Trịnh Tố Uyên
3.4.5.7.1. This is an efficiency requirement
3.4.5.8. Vũ Thị Anh Thư
3.4.5.8.1. It specifies a timing condition (two minutes) for a system behavior
3.4.5.9. Hồ Thúy Hiền
3.4.5.9.1. it states the availlability of the system
3.4.5.10. Nguyễn Thùy Dương
3.4.5.10.1. It specifies a condition and time frame
3.4.5.11. Đinh Vũ Thanh Huyền
3.4.5.11.1. it defines the behavior and timing expectation of the system
3.4.5.12. Kiều Hoàng Minh Hiếu
3.4.5.12.1. a constraint on the behavior of the system based on certain conditions
3.4.5.13. Dương Thế Công
3.4.5.13.1. specifies a time-based criterion (two minutes of room being empty)
3.4.5.14. Mai Đức Đạt
3.4.5.14.1. sets a time-based condition (two minutes of the room remaining vacant).
3.4.5.15. Le Manh Toan
3.4.5.15.1. the limit of time are of how long the system is able to handle
3.4.5.16. Cấn Thị Bích Thủy
3.4.5.16.1. It is concerned with the efficiency or energy-saving aspect of the system (related to the behavior of the light in the room).
3.5. Q3: Which of these are functional requirements?
3.5.1. A person can enroll in a course
3.5.1.1. Only 10 persons max can enroll to this course
3.5.1.1.1. Trịnh Tố Uyên
3.5.1.1.2. Trần Minh Đức
3.5.1.1.3. Nguyễn Hoàng Tuấn
3.5.1.1.4. Nguyễn Thị Thanh Thủy
3.5.1.1.5. Nguyễn Mai Hương
3.5.1.1.6. Nguyễn Thế Thành
3.5.1.1.7. Dương Thế Công
3.5.1.1.8. Le Manh Toan
3.5.2. A course is taught by a professor
3.5.2.1. Nguyễn Quang Thanh
3.5.2.1.1. It describes a relationship between two entities in the system (course and professor) and their expected interaction (teaching).
3.5.2.2. Dương Thế Công
3.5.2.2.1. defines a relationship and a role (teaching) that must be supported by the system
3.5.2.3. Đoàn Diệu Linh
3.5.2.3.1. The requirement specifies a specific action that the system should support
3.5.2.4. Kiều Hoàng Minh Hiếu
3.5.2.4.1. defines a relationship between entities within the system
3.5.2.5. Nguyễn Thị Lan Nhi
3.5.2.5.1. it establishes the relationship and responsibility between a course and a professor.
3.5.2.6. Nguyễn Tiến Dũng
3.5.2.6.1. outlines a relationship and a role (teaching) that the system should support.
3.5.3. A professor is not a student
3.5.4. Each course terminates with an exam
3.5.4.1. Phạm Thị Khánh Ly
3.5.4.1.1. it defines a specific action that the system needs to provide, ensuring that there is an exam at the end of each course
3.5.4.2. Hồ Thúy Hiền
3.5.4.2.1. define what the system must do
3.5.4.3. Vũ Thị Anh Thư
3.5.4.3.1. It specifies a mandatory component in the system
3.5.4.4. Phạm Bảo Ngọc
3.5.4.4.1. Defines system behavior
3.5.4.5. Nguyễn Hoàng Tuấn
3.5.4.5.1. Mandatory function of the system
3.5.4.6. Nguyễn Thùy Dương
3.5.4.6.1. It states that each course terminates with an exam, indicating a required system function.
3.5.4.7. Đinh Vũ Thanh Huyền
3.5.4.7.1. This requirement indicates a specific action that should be supported by the system
3.5.4.8. Nguyễn Thị Thanh Thủy
3.5.4.8.1. Meeting these requirements is obligatory.
3.5.4.9. Triệu Trường Giang
3.5.4.9.1. it describe what system must do to ensure the quality of course
3.5.4.10. Dương Thế Công
3.5.4.10.1. specifies a required component at the end of each course (an exam)
3.5.4.11. Kiều Hoàng Minh Hiếu
3.5.4.11.1. a specific event or action that occurs within the system
3.5.4.12. Đỗ Thành Đạt
3.5.4.12.1. specific function related to the termination of a course
3.5.4.13. Lê Phương Thảo
3.5.4.13.1. a specific capability of the system ( indicates how each course ends)
3.5.4.14. Đoàn Diệu Linh
3.5.4.14.1. it specifies the expected outcome or action that signifies the end of a course.
3.5.5. Every exam produces a ranking of all participants
3.5.5.1. Phạm Thị Khánh Ly
3.5.5.1.1. it defines a particular behavior or outcome that the system needs to achieve
3.5.5.2. Vũ Thị Anh Thư
3.5.5.2.1. It outlines a specific outcome that the system must produce
3.5.5.3. Hồ Thúy Hiền
3.5.5.3.1. define the functionality
3.5.5.4. Le Manh Toan
3.5.5.4.1. This is a reporting requirements of the system
3.5.5.5. Kiều Hoàng Minh Hiếu
3.5.5.5.1. a specific event or action that occurs within the system
3.5.5.6. Đỗ Thành Đạt
3.5.5.7. Dương Thế Công
3.5.5.7.1. describes a specific functionality (producing a ranking) that the system must perform after each exam
3.5.6. A student is a person
3.6. Q4: Which of these are functional requirements? The iPhone.....
3.6.1. can function as a camera
3.6.1.1. Phạm Quang Hải
3.6.1.1.1. outlines a capability of the iPhone to serve as a camera,
3.6.1.2. Nguyễn Hoàng Tuấn
3.6.1.2.1. A very basic function of smartphone this day
3.6.1.3. Nguyễn Thị Thanh Thủy
3.6.1.3.1. A specific function of Iphone
3.6.1.4. Đinh Vũ Thanh Huyền
3.6.1.4.1. It specifies a specific functionality of the iphone
3.6.1.5. Phạm Bảo Ngọc
3.6.1.5.1. A specific ability to capture photos and videos
3.6.1.6. Nguyễn Mai Hương
3.6.1.6.1. Specify a basic function of Iphone
3.6.1.7. Dương Thế Công
3.6.1.7.1. describes a specific functionality of the iPhone – the ability to function as a camera.
3.6.1.8. Cấn Thị Bích Thủy
3.6.1.8.1. define a specific functionality that product have
3.6.1.9. Hồ Thúy Hiền
3.6.1.9.1. It states the function
3.6.2. has a camera with 2.0 megapixels with geo-tagging
3.6.2.1. Le Manh Toan
3.6.2.1.1. A specific configuration of camera component
3.6.2.2. Dương Thế Công
3.6.2.2.1. The statement provides detailed specifications about the camera feature
3.6.3. is a portable media player
3.6.4. is connected to a PC via a USB plug
3.6.5. includes a digital compass in the 3GS model
3.6.5.1. Nguyễn Quang Thanh
3.6.5.1.1. It details a specific feature present in the 3GS model.
3.6.5.2. Trịnh Tố Uyên
3.6.5.2.1. a functional requirement using a hardware feature of a specific iPhone model
3.6.5.3. Trần Minh Đức
3.6.5.3.1. It describes a specific feature (digital compass) in a particular model of the iPhone.
3.6.5.4. Hồ Thúy Hiền
3.6.5.4.1. it states a function of the system
3.6.5.5. Nguyễn Thị Lan Nhi
3.6.5.5.1. it describes a specific feature or functionality that the 3GS model of a device should have
3.6.5.6. Dương Thế Công
3.6.5.7. Kiều Hoàng Minh Hiếu
3.6.5.7.1. a particular feature or functionality that the iPhone 3GS model must have
3.6.6. renders a virtual keyboard by its multi-touch screen
3.6.6.1. Nguyễn Thị Thanh Thủy
3.6.6.1.1. defines a fuction that iphone must have
3.6.6.2. Dương Thế Công
3.6.6.2.1. describes a specific functionality – the rendering of a virtual keyboard through the multi-touch screen
3.6.7. offers an Internet client
3.6.7.1. Nguyễn Hoàng Tuấn
3.6.7.1.1. A very basic function of smartphone this day
3.6.7.2. Đoàn Diệu Linh
3.6.7.2.1. It specifies a specific functionality of the iphone
3.6.7.3. Nguyễn Thế Thành
3.6.7.3.1. this is mandatory for a smart phone these days
3.6.7.4. Nguyễn Thùy Dương
3.6.7.4.1. It describes a feature of the iPhone
3.6.7.5. Vũ Thị Anh Thư
3.6.7.5.1. It specifies the capability of the iPhone to provide internet access.
3.6.7.6. Le Manh Toan
3.6.7.7. Dương Thế Công
3.6.7.7.1. describes a specific functionality – the provision of
3.6.8. specifies a feature (digital compass) that is part of the iPhone's functionality
3.7. Q5: Ticket Sales System
3.7.1. Users must be able to browse for events by name or date or venue.
3.7.2. Searching for events by keywords should also be possible
3.7.2.1. Capacity - Data volumes, transaction volumes, user volumes
3.7.2.2. Usability - ease of learning, ease of use
3.7.3. User will select ticket price from those offered and also specify the number of tickets they require.
3.7.4. Users must be able to choose their seats and purchase tickets 24/7.
3.7.5. Only registered customers can buy tickets.
3.7.5.1. Access - permissions, who has access to which functionality and how
3.7.6. All data is to be backed up nightly.
3.7.6.1. Availability - timeframe for availability of functionality
3.7.6.2. Backup & recovery - protection against loss of data
3.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
3.7.8. Daily reports of ticket sales must be generated. These must be retained for two years.
3.7.9. The system should display availability of the tickets within five seconds.
3.7.9.1. Availability - timeframe for availability of functionality
3.7.9.2. Performance - speed of processing transactions
3.7.9.3. Archiving and retention - duration, methods, eventual deletion
3.7.10. It should not be possible to double-book tickets (i.e. buy a ticket that has already been sold).
3.7.11. Categories of Non-Functional Req.
3.7.11.1. Usability - ease of learning, ease of use
3.7.11.2. Capacity - Data volumes, transaction volumes, user volumes
3.7.11.3. Robustness - reliability, data integrity, user error
3.7.11.4. Availability - timeframe for availability of functionality
3.7.11.5. Backup & recovery - protection against loss of data
3.7.11.6. Performance - speed of processing transactions
3.7.11.7. Access - permissions, who has access to which functionality and how
3.7.11.8. Archiving and retention - duration, methods, eventual deletion
3.7.11.9. Security - Security levels for protection of data