Assignment – 5

Classify the requirement into func onal and non-func onal

requirements.

1. ATM machine shall validate PIN of the user during login along with biometric

verifica on.

The requirement "ATM machine shall validate PIN of the user during login along with
biometric verifica on" can be classified as follows:

Func onal Requirement:

 The ATM machine must validate the PIN of the user during login.

 The ATM machine must perform biometric verifica on.

Non-Func onal Requirement:

 The system should perform PIN and biometric valida on within a specified
me limit (e.g., the valida on should occur within 5 seconds).

 The system should ensure security by using encrypted communica on for PIN
and biometric data.

2. “Peak transac on Volume(s)- 20,000 calls in a busy hour, average dura on 20

Secs, grade of services 99.98%”

The requirement "Peak transac on Volume(s)- 20,000 calls in a busy hour, average
dura on 20 Secs, grade of services 99.98%" can be classified as follows:

Func onal Requirement:

 The system should support transac on processing (calls) during a busy hour.

Non-Func onal Requirement:

 The system should handle 20,000 transac on calls in a busy hour.

 The average dura on for processing each transac on should be 20 seconds.

  The system should maintain a grade of service of 99.98%, ensuring high
availability and performance.

3. “Brake System Shall sounds the alarm for 10 seconds at frequency of 100H when
the brake is applied”.

The requirement "Brake System shall sound the alarm for 10 seconds at a frequency
of 100Hz when the brake is applied" can be classified as follows:

Func onal Requirement:

 The brake system must sound an alarm when the brake is applied.

 The alarm must sound for a dura on of 10 seconds.

 The alarm must operate at a frequency of 100Hz.

Non-Func onal Requirement:

 The alarm should sound clearly and audibly in all environmental condi ons
(e.g., varying levels of ambient noise).

4. “Mean Time to failure (MTTF) -There should be no more than three Severity-1
outage per month”.

The requirement "Mean Time to Failure (MTTF) - There should be no more than three
Severity-1 outages per month" can be classified as follows:

Func onal Requirement:

 The system must monitor and track Severity-1 outages.

Non-Func onal Requirement:

 The system must ensure that no more than three Severity-1 outages occur per
month, indica ng a performance or reliability goal.

● Iden fy func onal and non-func onal requirements of your mini project.

Mini Project: Task Management System

Project Descrip on:

This is a simple task management system that allows users to create, update, and
manage tasks. The system will enable users to set deadlines, mark tasks as
completed, and categorize them by priority (low, medium, high).

Func onal Requirements:

1. User Registra on and Login:

o Users must be able to register with their email and password.

o Registered users must be able to log in using their creden als.

2. Task Crea on:

o Users must be able to create tasks by entering a tle, descrip on,

deadline, and priority (low, medium, high).

3. Task Management:

o Users must be able to edit the tle, descrip on, deadline, and priority
of an exis ng task.

o Users must be able to delete a task.

4. Task Status:

o Users must be able to mark a task as "completed" or "pending."

5. Task Filtering and Sor ng:

o Users must be able to filter tasks by their status (completed or

pending).

o Users must be able to sort tasks by priority or deadline.

6. No fica ons:

o Users should receive no fica ons for upcoming deadlines of tasks.

Non-Func onal Requirements:

1. Performance:

o The system must be able to handle up to 1000 tasks without no ceable

delays.

2. Usability:
 o The user interface (UI) must be simple and intui ve, allowing users to
easily add, edit, and track their tasks.

3. Security:

o User data, including passwords, must be securely stored using

encryp on (e.g., hashing for passwords).

o User sessions must be protected with proper authen ca on

mechanisms (JWT or sessions).

4. Availability:

o The system should be available 99.9% of the me, excluding planned

maintenance.

5. Scalability:

o The system should be able to scale if more users and tasks are added
(e.g., increasing database capacity).

6. Backup and Recovery:

o The system should back up user data periodically and allow data
recovery in case of failure.

7. Response Time:

o Ac ons like task crea on, edi ng, and dele on should complete within
3 seconds.

Technology Stack:

 Frontend: React.js or Angular for crea ng the user interface.

 Backend: Node.js with Express.js for the server-side logic.

 Database: MongoDB (NoSQL) for storing tasks and user data.

 Authen ca on: JWT (JSON Web Token) for user authen ca on and session
management.

 Hos ng: You could use services like Heroku for deployment or DigitalOcean if
scaling is required.
Future Enhancements:

1. Task Reminders: Set up reminders for tasks based on their deadlines.

2. Collabora ve Tasks: Allow users to share tasks with other users and
collaborate.

3. Task Comments: Users can add comments to tasks to discuss details with team
members.