Scribd
Upload
8 views

CS 619 prototype assignment Solution

Uploaded by

bc210206522
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
8 views

CS 619 prototype assignment Solution

Uploaded by

bc210206522
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

CS 619 prototype assignment Solution

iD. Bc210206522

Name Asif Naseem

Functional Requirements
Donor Functional Requirements
Registration:

Donors must provide personal details, blood type, and contact information during registration.
Login/Logout:
Donors can log in to access their profiles and application features.
Profile Management:
The profile should include the donor’s last donation date and frequency of donations.
Search Records:
Donors can search for patients in need of blood based on blood type and location.
Notifications:
Donors receive notifications about upcoming donation opportunities based on their blood type
and location.
View Patient Requests:
Donors can view requests from patients needing blood, filtered by relevant blood groups and
areas.
Patient Functional Requirements
Registration:
Patients must provide necessary personal and medical details during registration.
Login/Logout:
Patients can log in to access their profiles and application features.
Profile Management:
Patients can update their personal and medical information.
Generate Blood Requests:

Patients can create and submit blood requests specifying the required blood type and location.
Requests are published for donors after administrator verification.
Search Active Donor Records:
Patients can search for active donors based on blood type and location.
Request Blood:
Patients can request blood for themselves or others by specifying any required blood group.
Administrator Functional Requirements
Login/Logout:
Administrators can log in to manage the system and user accounts.
Secure logout functionality to ensure system integrity.

Profile Management:

Administrators can update their profiles and manage their account settings.
User Management:
Administrators can add, delete, or block donor and patient accounts.
Administrators must verify and approve donor registrations before activation.
Approve Blood Requests:
Administrators review and approve blood requests submitted by patients before
they are published for donors.
Send Notifications:
Administrators can send messages and notifications to registered donors and
patients to facilitate communication.
Database Management:
Administrators maintain the database, ensuring data accuracy and security.
They can generate reports on donation activities, donor eligibility, and patient
requests.
Non Functional :-

 Performance:

 Response time: The system should respond to user interactions within 2


seconds.
 Throughput: The system should handle at least 1000 concurrent user
requests per minute.
 Scalability: The system should be able to scale horizontally to
accommodate increasing user loads.
 Resource usage: The system should not consume more than 50% of CPU
and memory resources under normal operation.

 Reliability:

 Availability: The system should be available 99.99% of the time, excluding


scheduled maintenance.
 Fault tolerance: The system should continue to operate in the event of
hardware or software failures.
 Security:

 Authentication: Users should be required to authenticate with a username


and password.
 Authorization: Access to sensitive data should be restricted based on user
roles and permissions.

 Usability:

 User interface: The user interface should be intuitive and easy to navigate.

 Scalability:
 The system should be able to handle a tenfold increase in user traffic without
significant performance degradation.

Use Case Diagram(s):

You might also like