Lecture Notes Of Class 2: Requirements Gathering and Analysis
Lecture Notes Of Class 2:
Requirements Gathering and Analysis
Objective:
- To
introduce students to the concept of requirements gathering for software
projects.
- To
explain how to document functional and non-functional requirements.
- To
guide students in creating use case diagrams using UML (Unified Modeling
Language).
1.
Introduction to Requirements Gathering
In software development, requirements
gathering is the process of collecting the necessary details for designing
and developing a software system. The aim is to understand what the users
expect from the system, what problem the system should solve, and how it should
behave.
Why is
Requirements Gathering Important?
- Clarifies
project scope: Ensures that the development team understands
exactly what needs to be built.
- Minimizes
rework: Properly understood and documented
requirements reduce misunderstandings that could lead to costly changes
during development.
- Improves
user satisfaction: By aligning the system’s features with user
needs, the system is more likely to meet expectations.
Key
Techniques for Gathering Requirements:
1. Interviews:
o
Conduct one-on-one meetings with stakeholders to
gather their insights.
o
Effective for obtaining detailed, qualitative
information.
2. Surveys/Questionnaires:
o
Useful for gathering feedback from a larger group
of users.
o
Helps collect both qualitative and quantitative
data.
3. Workshops:
o
Facilitated meetings where stakeholders collaborate
to define the system's features and constraints.
o
Often involves brainstorming and group discussions.
4. Observation:
o
The developer observes users performing tasks to
understand their needs and how they interact with current systems.
o
Helps in identifying hidden requirements that might
not be expressed verbally.
5. Document
Analysis:
o
Reviewing existing documents such as business
plans, system specifications, or help manuals to gather information.
o
Useful for understanding the context of the system
or integrating with existing systems.
6. Prototyping:
o
Building a prototype of the software that
demonstrates basic functionality to gather feedback.
o
Helps stakeholders visualize how the system will
function.
2.
Documentation of Functional and Non-Functional Requirements
Once requirements are gathered,
they need to be documented clearly to ensure that all stakeholders have a
shared understanding of the system’s expectations.
Functional
Requirements:
Functional requirements specify what
the system should do. They describe the behaviors, features, and
interactions of the system. These are the core functionalities that will be
implemented in the system.
- Example:
- "The
system shall allow users to log in with a username and password."
- "The
system shall generate a report of student grades."
Functional requirements often
focus on:
- Inputs
and outputs
- User
interactions
- Business
rules
- Data
handling
Non-Functional
Requirements:
Non-functional requirements
describe how the system should perform rather than what it should do.
These requirements often define the system's quality attributes.
- Example:
- "The
system shall load within 3 seconds."
- "The
system shall support 1000 concurrent users."
Non-functional requirements often
include:
- Performance
(e.g., response time, load time)
- Security
(e.g., user authentication)
- Scalability
(e.g., ability to handle more users over time)
- Usability
(e.g., ease of use)
3. Use
Case Diagram Creation Using UML
A Use Case Diagram is a
visual representation of the functionality provided by the system from the
perspective of external actors (such as users or other systems). It helps to
identify the system's users and their interactions with the system’s functions.
Key
Elements of a Use Case Diagram:
1. Actors:
o
An actor represents any external entity that
interacts with the system. It can be a user, another system, or even a hardware
device.
o
Example: A "Student" who
interacts with a "Student Management System."
2. Use
Cases:
o
A use case represents a specific function or
feature that the system provides to its users.
o
Example: "Add Student,"
"Generate Report."
3. Associations:
o
An association shows the relationship between an
actor and a use case, indicating that the actor participates in the use case.
4. System
Boundary:
o
The system boundary defines the scope of the system
and shows the use cases inside it.
5. Generalization:
o
Represents an actor or use case that inherits the
behavior or characteristics of another.
4.
Exercise: Create a Use Case Diagram for a “Student Management System”
Now, let’s apply what we've
learned by creating a use case diagram for a Student Management System.
Step-by-Step
Process to Create a Use Case Diagram:
1. Identify
the Actors:
o
Student: Can view their details, check grades,
etc.
o
Teacher: Can add or update student
records, assign grades, etc.
o
Admin: Manages the system, adds
teachers, generates reports, etc.
2. Identify
the Use Cases:
o
For Student:
§ View
Student Profile
§ View
Grades
§ Update
Profile
o
For Teacher:
§ Add
Student
§ Update
Student Grades
§ View
Class List
o
For Admin:
§ Manage
Users
§ Generate
Reports
§ Set
System Configuration
3. Create
Relationships:
o
Draw lines to associate the actors with their
respective use cases.
4. Draw the
Diagram: Use a tool like Lucidchart, Microsoft Visio, or even pen and paper to
draw the use case diagram. Start by drawing actors outside the system boundary,
then draw use cases inside the system boundary, and connect them with
appropriate lines.
Example
Use Case Diagram for a Student Management System:
- Actors:
- Student:
View Profile, View Grades
- Teacher:
Add Student, Assign Grades
- Admin:
Generate Report, Manage Users
The diagram will show the actors
on the outside of the system boundary, and their interactions with the system’s
use cases inside the boundary.
Conclusion:
- Requirements
Gathering is the first step in any software project and
is essential to ensure that the system aligns with the users' needs.
- Functional
Requirements describe what the system should do, and Non-Functional
Requirements describe how the system should perform.
- Use
Case Diagrams help visually represent the interactions
between the system and its users, making it easier to understand system
requirements.
By the end of this class,
students should be able to understand how to gather requirements and create use
case diagrams as part of the software development lifecycle.
Homework/Assignment:
1. Create a
use case diagram for a “Library Management System” with at least three actors
and five use cases.
2. Write
functional and non-functional requirements for the same system.
4o mini
You said:
write solution:
Homework/Assignment: Create a use case diagram for a “Library Management
System” with at least three actors and five use cases. Write functional and
non-functional requirements for the same system.
ChatGPT
said:
ChatGPT
Solution:
Library Management System
1. Use
Case Diagram for Library Management System
Actors:
1. Librarian: Manages
the library's operations.
2. Member
(User): The person who borrows and returns books.
3. Admin: Manages
users, books, and system settings.
Use
Cases:
1. Librarian:
o
Add New Book
o
Issue Book to Member
o
Return Book from Member
o
View Borrowed Books
2. Member:
o
Search for Books
o
Borrow Book
o
Return Book
o
View Borrowing History
3. Admin:
o
Manage Members
o
Add/Edit Book Information
o
Generate Reports
Use Case
Diagram:
Here's how you can visualize the
use case diagram:
sql
CopyEdit
+-----------------------------+
|
Library Management |
|
System |
| |
|
+-------------------+ |
|
| Search for Books|<----|-->
(Member)
|
+-------------------+ |
|
+-------------------+ |
|
| Borrow Book |<----|--> (Member)
|
+-------------------+ |
|
+-------------------+ |
|
| Return Book |<----|--> (Member)
|
+-------------------+ |
|
+-------------------+ |
|
| View History |<----|--> (Member)
|
+-------------------+ |
|
+-------------------+ |
|
| Add New Book |<----|-->
(Librarian)
|
+-------------------+ |
|
+-------------------+ |
|
| Issue Book |<----|-->
(Librarian)
|
+-------------------+ |
|
+-------------------+ |
|
| Return Book |<----|-->
(Librarian)
|
+-------------------+ |
|
+-------------------+ |
|
| View Borrowed Books|<----|--> (Librarian)
|
+-------------------+ |
|
+-------------------+ |
|
| Manage Members |<----|-->
(Admin)
|
+-------------------+ |
|
+-------------------+ |
|
| Add/Edit Book Info|<----|--> (Admin)
|
+-------------------+ |
|
+-------------------+ |
|
| Generate Reports |<----|-->
(Admin)
|
+-------------------+ |
+-----------------------------+
2.
Functional Requirements for the Library Management System
1. Book
Management:
o
The system shall allow the librarian to add new
books.
o
The system shall allow the librarian to update or
remove books from the inventory.
2. Book
Borrowing:
o
The system shall allow members to search for books
by title, author, or genre.
o
The system shall allow members to borrow books if
they are available.
o
The system shall allow the librarian to issue books
to members.
3. Book
Return:
o
The system shall allow members to return borrowed
books.
o
The system shall update the availability of books
once returned.
4. Member
Management:
o
The system shall allow the admin to add, edit, or
remove members.
o
The system shall store member information such as
name, address, and contact details.
5. History
and Reports:
o
The system shall allow members to view their
borrowing history.
o
The system shall allow the admin to generate
reports on the most borrowed books and overdue books.
3.
Non-Functional Requirements for the Library Management System
1. Performance:
o
The system shall allow at least 100 concurrent
users without noticeable performance degradation.
o
Search functionality shall return results within 3
seconds.
2. Usability:
o
The system shall have a user-friendly interface
with easy navigation.
o
The system shall support English as the primary
language.
3. Security:
o
The system shall require users to log in with a
valid username and password to access the system.
o
The system shall ensure that only the admin can
manage members and generate reports.
4. Scalability:
o
The system shall be able to scale to support more
than 10,000 books and 5,000 members as the library grows.
5. Backup
and Recovery:
o
The system shall perform automatic backups of all
data every 24 hours.
o
The system shall allow the restoration of data in
case of a system failure.
Conclusion
In this solution:
- We
created a use case diagram showing the interactions between three
actors (Librarian, Member, Admin) and five use cases.
- We
outlined both functional and non-functional requirements that
describe the system's expected behavior and performance.
This diagram and set of
requirements provide a solid foundation for the development of the Library
Management System.
4o mini
You said:
WRITE 10 ASSIGNMENTS FROM ABOVE
CONCEPT WITH STEP BY STEP SOLUTIONS with proper explanation in details
ChatGPT
said:
ChatGPT
10
Assignments on Requirements Gathering and Use Case Diagrams with Detailed
Solutions
Assignment
1: Interview Stakeholders to Gather Requirements for a Student Management
System
Objective: Conduct
an interview with a stakeholder (e.g., teacher, administrator) to gather
functional and non-functional requirements for a Student Management System.
Steps:
1. Prepare
Questions:
o
Functional:
§ What
features should the system have for student registration?
§ How
should the grades be recorded and displayed?
§ What
actions should be allowed for teachers and students?
o
Non-functional:
§ How fast
should the system respond when retrieving student records?
§ What
security measures should the system have?
2. Conduct
Interview:
o
Record answers from the stakeholder. Note the
different types of requirements based on their responses.
3. Document
the Requirements:
o
Write down functional and non-functional
requirements based on the interview.
Solution
Example:
- Functional
Requirements:
- The
system shall allow students to register with basic details (name,
contact).
- The
system shall allow teachers to assign grades to students.
- The
system shall allow students to view their grades.
- Non-Functional
Requirements:
- The
system shall respond within 2 seconds when searching for student records.
- The
system shall encrypt student data for security purposes.
Assignment
2: Create a Use Case Diagram for a "Library Management System"
Objective: Create a
use case diagram for a Library Management System with three actors and
five use cases.
Steps:
1. Identify
Actors:
o
Librarian
o
Member
o
Admin
2. Identify
Use Cases:
o
Add New Book
o
Borrow Book
o
Return Book
o
View Borrowing History
o
Generate Reports
3. Draw the
Use Case Diagram:
o
Use tools like Lucidchart or draw it manually.
Solution:
(Refer to the solution provided
earlier in this document for the complete use case diagram.)
Assignment
3: Functional Requirements Documentation for an E-commerce Website
Objective: Write
functional requirements for an E-commerce Website with features for
product listing, cart management, and payment processing.
Steps:
1. Identify
the Core Features:
o
Product Search
o
Add to Cart
o
Checkout and Payment
2. Write
Functional Requirements:
o
The system shall allow customers to search for
products by name or category.
o
The system shall allow users to add items to their
shopping cart.
o
The system shall allow users to complete the
purchase through a payment gateway.
Solution:
- Functional
Requirements:
- The
system shall allow users to search products based on category.
- The
system shall allow users to add products to the shopping cart.
- The
system shall calculate the total amount, including tax and shipping.
Assignment
4: Create a Use Case Diagram for an E-commerce Website
Objective: Create a
use case diagram for the E-commerce Website you documented in Assignment
3.
Steps:
1. Identify
Actors:
o
Customer
o
Admin
2. Identify
Use Cases:
o
Browse Products
o
Add to Cart
o
Checkout
o
Manage Products (Admin)
3. Draw the
Use Case Diagram:
o
Use actors and use cases to create the diagram.
Solution:
- Use
Case Diagram: (Refer to the earlier diagram example, with
the actors "Customer" and "Admin" and their respective
use cases.)
Assignment
5: Write Non-Functional Requirements for a Mobile Application
Objective: Write
non-functional requirements for a Mobile Application that provides
weather updates.
Steps:
1. Performance:
o
The app should load the weather data within 3
seconds of a user request.
2. Security:
o
The app should ensure user privacy by not sharing
location data without permission.
3. Usability:
o
The app interface should be user-friendly, with
large buttons and clear navigation.
4. Reliability:
o
The app should function properly even with limited
network connectivity.
Solution:
- Non-Functional
Requirements:
- The
app shall be responsive, loading weather data within 3 seconds.
- The
app shall protect user data by requiring a login before saving personal
information.
- The
app shall display weather information clearly with minimal design
clutter.
Assignment
6: Create a Use Case Diagram for a Bank Management System
Objective: Create a
use case diagram for a Bank Management System that includes account
management, transactions, and reporting.
Steps:
1. Identify
Actors:
o
Customer
o
Teller
o
Admin
2. Identify
Use Cases:
o
Open Account (Customer)
o
Deposit Funds (Customer)
o
Withdraw Funds (Customer)
o
Generate Reports (Admin)
3. Draw the
Use Case Diagram:
o
Use appropriate tools to design the diagram.
Solution:
- Use
Case Diagram: (Create the diagram with actors and use cases
similar to the format shown earlier.)
Assignment
7: Create a Use Case Diagram for a "Hospital Management System"
Objective: Create a
use case diagram for a Hospital Management System with actors like
doctor, patient, and admin.
Steps:
1. Identify
Actors:
o
Patient
o
Doctor
o
Admin
2. Identify
Use Cases:
o
Book Appointment (Patient)
o
View Patient Record (Doctor)
o
Generate Reports (Admin)
3. Draw the
Use Case Diagram:
o
Create the diagram to show how the actors interact
with the system.
Solution:
- Use
Case Diagram: (Refer to the previous examples for how to
lay out actors and use cases.)
Assignment
8: Create a Use Case Diagram for a "Hotel Reservation System"
Objective: Create a
use case diagram for a Hotel Reservation System with actors like guest,
receptionist, and admin.
Steps:
1. Identify
Actors:
o
Guest
o
Receptionist
o
Admin
2. Identify
Use Cases:
o
Make Reservation (Guest)
o
Check-In (Receptionist)
o
View Reservation History (Admin)
3. Draw the
Use Case Diagram:
o
Ensure to properly connect the actors to their use
cases.
Solution:
- Use
Case Diagram: (Follow the steps from previous examples for
the layout.)
Assignment
9: Conduct a Survey for Requirement Gathering
Objective: Create a
survey questionnaire to gather requirements for an Event Management System.
Steps:
1. Prepare
Questions:
o
Functional:
§ What
features would you like the event system to have (e.g., event creation,
ticketing)?
o
Non-functional:
§ How much
time are you willing to wait for the system to process your ticket booking?
2. Distribute
Survey:
o
Send the survey to stakeholders (event managers,
users, etc.).
3. Analyze
Responses:
o
Document functional and non-functional requirements
based on survey data.
Solution
Example:
- Functional
Requirements:
- The
system shall allow users to view upcoming events.
- The
system shall allow event organizers to create and manage events.
- Non-Functional
Requirements:
- The
system shall respond within 2 seconds after submitting a booking request.
- The
system shall ensure that event data is backed up every day.
Assignment
10: Draw a Use Case Diagram for a "Social Media Application"
Objective: Create a
use case diagram for a Social Media Application with actors like user,
admin, and system.
Steps:
1. Identify
Actors:
o
User
o
Admin
2. Identify
Use Cases:
o
Create Post (User)
o
Like Post (User)
o
Manage Users (Admin)
3. Draw the
Use Case Diagram:
o
Visualize the system and interactions with actors.
Solution:
- Use
Case Diagram: (Follow similar patterns to the diagrams
above.)
These assignments help students
learn to effectively gather requirements, document them, and visually represent
interactions in a system using use case diagrams. Each solution follows a
step-by-step approach, ensuring clarity and hands-on experience in system
design.
4o mini
You said:
WRITE 50 no of MCQs only FROM
ABOVE CONCEPT with explanation
ChatGPT
said:
ChatGPT
Here are 50 multiple-choice
questions (MCQs) based on the concept of Requirements Gathering and
Analysis with detailed explanations.
1. Which
of the following is a primary goal of requirements gathering?
A) To design the software
B) To understand the needs of stakeholders
C) To write the code for the system
D) To create a user interface design
Answer: B) To understand the
needs of stakeholders
Explanation:
Requirements gathering is the process of identifying and documenting the needs
and expectations of stakeholders to ensure the developed system meets their
requirements.
2. What
type of requirement deals with system performance, security, and usability?
A) Functional requirements
B) Technical requirements
C) Non-functional requirements
D) User interface requirements
Answer: C) Non-functional
requirements
Explanation:
Non-functional requirements define system qualities such as performance,
security, scalability, and usability, unlike functional requirements that focus
on what the system should do.
3. Which
technique is commonly used for gathering requirements from stakeholders?
A) Prototyping
B) Interviewing
C) Data mining
D) Regression testing
Answer: B) Interviewing
Explanation:
Interviews with stakeholders are a common method for gathering requirements as
they allow for direct interaction and understanding of their needs.
4. Which
of the following describes a "Use Case"?
A) A process flow of the system
B) A description of how the system will be developed
C) A model of how the system should behave from the user’s perspective
D) A testing method used during implementation
Answer: C) A model of how the
system should behave from the user’s perspective
Explanation: A use
case describes a specific way users interact with the system and the system’s
response to those interactions.
5. What
is the primary purpose of creating a Use Case Diagram?
A) To identify actors and their
roles
B) To show system architecture
C) To document project timelines
D) To visualize the interaction between users and the system
Answer: D) To visualize the
interaction between users and the system
Explanation: A use
case diagram visually represents the interaction between users (actors) and the
system, outlining key use cases.
6. Which
of the following is a functional requirement?
A) The system should process
payments in less than 3 seconds.
B) The system should support at least 1000 users simultaneously.
C) The system should allow users to register an account with a username and
password.
D) The system should be accessible via mobile devices.
Answer: C) The system should
allow users to register an account with a username and password.
Explanation:
Functional requirements define specific behavior and functions that the system
should perform, such as allowing users to register accounts.
7. Which
is an example of a non-functional requirement?
A) The system shall allow users
to create an account.
B) The system shall allow users to reset their passwords.
C) The system shall ensure that data is encrypted.
D) The system shall process orders in 10 seconds.
Answer: C) The system shall
ensure that data is encrypted.
Explanation:
Non-functional requirements specify constraints like security, performance, and
reliability. Encrypting data is a non-functional requirement focusing on
security.
8. A use
case diagram can be created using which of the following?
A) Microsoft Word
B) UML (Unified Modeling Language)
C) SQL queries
D) Java programming language
Answer: B) UML (Unified Modeling
Language)
Explanation: Use case
diagrams are a part of UML, a standardized modeling language used to represent
the structure and behavior of systems.
9. Which
of the following is NOT a common method for gathering requirements?
A) Surveys
B) Workshops
C) Code reviews
D) Focus groups
Answer: C) Code reviews
Explanation: Code
reviews are performed during the development phase, not during requirements
gathering. Requirements are typically gathered through surveys, workshops, and
focus groups.
10. What
is the first step in the requirements gathering process?
A) Define project milestones
B) Identify and engage stakeholders
C) Start system design
D) Begin coding
Answer: B) Identify and engage
stakeholders
Explanation: The
first step is to identify the stakeholders who will provide input about the
system's requirements. Engaging them early is crucial to understand the
project’s needs.
11. Which
document contains a detailed description of a system’s functionalities?
A) Project plan
B) Requirement specification document
C) Use case diagram
D) System architecture document
Answer: B) Requirement
specification document
Explanation: The
requirement specification document provides a detailed list of all functional
and non-functional requirements for the system.
12. Who is
responsible for validating the functional requirements of a system?
A) Developers
B) End-users
C) Testers
D) Project managers
Answer: B) End-users
Explanation:
End-users validate functional requirements to ensure that the system meets
their needs and expectations.
13. Which
of the following is NOT an actor in a use case diagram?
A) User
B) System
C) Database
D) Application
Answer: C) Database
Explanation: An actor
in a use case diagram is typically a user or another system interacting with
the system. A database is not considered an actor.
14. What
is the main purpose of conducting a stakeholder interview during requirements
gathering?
A) To create a project plan
B) To understand the user's needs and expectations
C) To design the system architecture
D) To write code for the system
Answer: B) To understand the
user's needs and expectations
Explanation:
Stakeholder interviews are conducted to gather insights into the specific
needs, expectations, and requirements for the system.
15. What
is a "use case"?
A) A database table
B) A step-by-step interaction between the user and the system
C) A set of coding instructions
D) A design pattern
Answer: B) A step-by-step
interaction between the user and the system
Explanation: A use
case is a detailed description of how users interact with a system to achieve
specific goals.
16. What
is typically the focus of non-functional requirements?
A) How the system performs its
tasks
B) What tasks the system performs
C) How the system handles errors
D) The user interface layout
Answer: A) How the system
performs its tasks
Explanation:
Non-functional requirements focus on system performance, security, and
reliability, rather than what the system does.
17. Which
of the following is a common tool used to create Use Case Diagrams?
A) Microsoft Excel
B) Lucidchart
C) Notepad
D) PowerPoint
Answer: B) Lucidchart
Explanation:
Lucidchart is a popular tool used for creating use case diagrams and other UML
diagrams.
18. What
does a use case diagram represent in a system?
A) The physical hardware required
B) The interaction between actors and the system
C) The detailed design of the system
D) The system’s internal data structure
Answer: B) The interaction
between actors and the system
Explanation: A use
case diagram shows how actors (users or other systems) interact with the system
to achieve specific objectives.
19.
Functional requirements are concerned with:
A) System's external appearance
B) What the system should do
C) The security of the system
D) The system's performance under load
Answer: B) What the system should
do
Explanation:
Functional requirements specify the behaviors, features, and functions the
system should have.
20. Which
of the following is an example of a performance-related non-functional
requirement?
A) The system should allow users
to register for an account.
B) The system should load pages in under 2 seconds.
C) The system should support user authentication.
D) The system should have a search function.
Answer: B) The system should load
pages in under 2 seconds.
Explanation: This is
a non-functional requirement related to the system’s performance, specifically
page load time.
21. Which
of the following tools can help in gathering requirements from users via
surveys?
A) Google Forms
B) Microsoft Paint
C) Eclipse IDE
D) GitHub
Answer: A) Google Forms
Explanation: Google
Forms is an effective tool for creating surveys and gathering feedback from
users to collect requirements.
22. What
is the purpose of a Use Case Diagram?
A) To visualize system components
B) To describe the system architecture
C) To show the relationships between actors and use cases
D) To write detailed code for the system
Answer: C) To show the
relationships between actors and use cases
Explanation: Use case
diagrams illustrate the interactions between users (actors) and the system,
focusing on the use cases that define those interactions.
23. Which
type of requirements defines how a system should behave under specific
conditions?
A) Functional requirements
B) Non-functional requirements
C) System constraints
D) Design requirements
Answer: A) Functional
requirements
Explanation:
Functional requirements define the specific tasks and behaviors a system must
exhibit under various conditions.
24. Which
of the following describes a non-functional requirement related to security?
A) The system shall allow users
to search for products.
B) The system shall encrypt sensitive data.
C) The system shall be able to process 100 transactions per second.
D) The system shall allow users to track their order history.
Answer: B) The system shall
encrypt sensitive data.
Explanation:
Encryption of sensitive data is a non-functional requirement focused on the
system’s security.
25. What
is the role of an actor in a Use Case Diagram?
A) To represent a user or system
that interacts with the system
B) To represent a component of the system
C) To define the structure of the system
D) To represent a database used by the system
Answer: A) To represent a user or
system that interacts with the system
Explanation: An actor
represents any external entity (user or system) that interacts with the system
in a use case diagram.
26. Which
of the following is an example of a technical requirement?
A) The system should allow users
to add products to the cart.
B) The system should be compatible with both desktop and mobile browsers.
C) The system should have an easy-to-use interface.
D) The system should allow users to reset their password.
Answer: B) The system should be
compatible with both desktop and mobile browsers.
Explanation:
Technical requirements deal with the technical aspects such as platform
compatibility.
27. Which
of the following can be considered as a functional requirement?
A) The system should allow users
to view their balance.
B) The system should encrypt user passwords.
C) The system should support up to 5000 concurrent users.
D) The system should have a user-friendly interface.
Answer: A) The system should
allow users to view their balance.
Explanation: Viewing
balance is a specific functionality the system must provide, making it a
functional requirement.
28. A Use
Case Diagram primarily helps in understanding which aspect of a system?
A) Detailed class structure
B) Interactions between users and the system
C) System’s database design
D) System’s network architecture
Answer: B) Interactions between
users and the system
Explanation: A use
case diagram illustrates how users (actors) interact with the system’s
functionalities (use cases).
29. Which
of the following is an example of a non-functional requirement related to
usability?
A) The system shall allow users
to login using an email and password.
B) The system shall allow users to track orders.
C) The system’s interface shall be easy to navigate.
D) The system shall handle up to 1000 transactions per second.
Answer: C) The system’s interface
shall be easy to navigate.
Explanation:
Usability concerns how easy and intuitive the system’s interface is for users.
30. A
requirement that specifies how fast the system should process a user request is
called a:
A) Functional requirement
B) Non-functional requirement
C) Design requirement
D) Security requirement
Answer: B) Non-functional
requirement
Explanation: This is
a performance-related non-functional requirement, specifying the speed at which
the system should respond.
31. The process
of gathering requirements from multiple stakeholders and documenting them is
known as:
A) Testing
B) Coding
C) Requirements analysis
D) System design
Answer: C) Requirements analysis
Explanation:
Requirements analysis involves collecting and documenting the needs and
expectations of stakeholders to ensure the system meets those needs.
32. A
system’s ability to function correctly under high user traffic is an example
of:
A) Functional requirement
B) Non-functional requirement
C) User interface requirement
D) Database requirement
Answer: B) Non-functional
requirement
Explanation: This is
an example of scalability, which is a non-functional requirement related to the
system’s performance under load.
Comments
Post a Comment