This document provides a system requirements specification for a Blood Bank Management System. It outlines the scope, functional requirements, and non-functional requirements of the system. The system will allow users to search for blood groups available in their city, register as blood donors, and allow those in need of blood to contact matching donors. The functional requirements describe use cases for searching items, creating an account, ordering products, managing product details, making payments, and changing admin details. Non-functional requirements include security, reliability, performance, maintainability, and usability.
This document provides a system requirements specification for a Blood Bank Management System. It outlines the scope, functional requirements, and non-functional requirements of the system. The system will allow users to search for blood groups available in their city, register as blood donors, and allow those in need of blood to contact matching donors. The functional requirements describe use cases for searching items, creating an account, ordering products, managing product details, making payments, and changing admin details. Non-functional requirements include security, reliability, performance, maintainability, and usability.
This document provides a system requirements specification for a Blood Bank Management System. It outlines the scope, functional requirements, and non-functional requirements of the system. The system will allow users to search for blood groups available in their city, register as blood donors, and allow those in need of blood to contact matching donors. The functional requirements describe use cases for searching items, creating an account, ordering products, managing product details, making payments, and changing admin details. Non-functional requirements include security, reliability, performance, maintainability, and usability.
This document provides a system requirements specification for a Blood Bank Management System. It outlines the scope, functional requirements, and non-functional requirements of the system. The system will allow users to search for blood groups available in their city, register as blood donors, and allow those in need of blood to contact matching donors. The functional requirements describe use cases for searching items, creating an account, ordering products, managing product details, making payments, and changing admin details. Non-functional requirements include security, reliability, performance, maintainability, and usability.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 14
Advanced Technological Institute – Kurunegala
Higher National Diploma in Information Technology
Individual Project
System Requirment Specification
Document
Blood Bank Management System
Name-: M.A.M. Ahnaf
Index No-: KUR/IT/2017/F/0029 Supervisor-: Mrs. E.M.D.J.K Ekanayake
Page | 1 CONTENTS
1.Introduction .......................................................... Error! Bookmark not defined.
2. Scope of the project ...............................................................................................4 2.0 Characteristics product…………………………………………………………………………………………..4 2.1 Services provides by the end system ...................................................................................................................4 2.2 End result of the project .......................................................................................................................................4 2.3 Under which conditions the project will be executed ..........................................................................................5
3. Functional Requirements .................................... Error! Bookmark not defined.
The purpose of developing this system is to provide blood to the people who are in need of blood. The number persons who are in need of blood are increasing in large number day by day. Using this system user can search blood group available in the city and he can also get contact number of the donor who has the same blood. Using this blood bank management system people can register himself or herself who want to donate blood and if some want need blood, he or she can get blood by contacting the donors.
Page | 3 2. Scope of the project
2.0 Characteristics product
The user and admin can proceed his business avoiding cons in the general market and wide-up the own business from this web site.
2.1 Services provides by the end system
Admin gets the capability of adding new merchandises or remove the added item.
Give a detailed description about the commodity.
Ability of electronic payment.
User gets the shopping cart facility.
Users gets an alert a commodities have been updated
2.2 End result of the project
At the end of the project, the customer can do business online, and focus on customer care.
Increase in the profit of the business so that business can continue doing business 24 hours a day.
Customer’s payment can be made through the bank.
The ability of the consumer to have a good knowledge of the mobile phone.
Page | 4 2.3 Under which conditions the project will be executed In this website only the registered users are allowed to buy commodities.
User must register in the web site entering his e-mail and password as to get a verified membership.
2.4 Acceptance criteria
User can’t buy computer or parts without login.
User can pay by credit card.
User can get shopping cart service.
An acknowledgement sent to the user after submitting the form.
User can search any computer parts by typing name and brand of product.
User can buy any time of the day.
User can get discount.
Page | 5 3. Functional Description
Here we identify the functional requirements of our online bridal frock and accessories ordering website. So this is illustrated through the following diagrams. So this section outlines the use cases for each of the active user separately.
Page | 6 01. Use case: Search Items
Use case number 01
Use case name Search Items
Description 01. Enter name or brand of the mobile phone on the
Pre-Condition User shall be entered the name or brand of the computer
on the search box
Post condition User can see search result in a new page.
Alternatives Page cannot be find.
Page | 7 02. Use case: create an account.
Use case number 02
Use case name Create an account
Actor/s Customer
Description 01. Enter the valid e-mail Address.
02. Enter new pass word. 03. Enter new password again. 04. Press Create button. Pre-Condition User should be entered the new e-mail and password on the on the log in form and create new account.
Post condition User can be logged as new user then user can get computer parts
Alternatives
Page | 8 03. Use case: Order Product
Use case number 04
Use case name Order
Actor/s Customer
Description 01. Enter order details
02. Place order
Pre-Condition Customer need to be log as a customer and enter order
details and Place order.
Post condition Customer can be Order computer parts.
Alternatives Cancelling the place order.
Page | 9 04. Use case: Manage Product
Use case number 05
Use case name Manage product details
Actor/s Admin
Description 01. Log as admin
02. Update or insert products
Pre-Condition Admin need to log as admin
Post condition Customer can be view update computer details on the
web page. Alternatives Customer view before update items.
Page | 10 05. Use case: Makes payments
08 Use case number Use case name Making payment with credit card
Actor/s User
Description 01. Add to cart
02. Enter the account number 03. Press confirm button.
Pre-Condition User shall be entered the account number on given box
Post condition Customer can be Making payment then customer can get product.
Alternatives Do not do place order and payments.
Page | 11 06. Use case: Change admin details
08 Use case number Use case name Making payment with credit card
Actor/s Admin
Description 01. Log as admin
02. Change details 03. Press conform button
Pre-Condition Admin need to log as admin
Post condition Admin can see updated details
Alternatives Admin can work without change admin details
Page | 12 4. Non-Functional Description
Security
User should be registered in the web site entering his e-mail and password as to get a verified membership. Secure access to consumer’s confidential data. Passwords should never be viewable at the point of entry or at any other time.
Reliability
Never should be displayed wrong information of the computers on the web site. This web site should be displayed only computers or parts for sale.
Performance This web Site should be displayed in any display size.
Database query processing time depend on the internet speed.
Time of the loading web site is depend on the internet speed.
Maintainability Requirement
The admin should be able to insert products and remove products at any time from the database.
The admin should be able to changed details of the computer parts at any time of the day.
Usability Requirement All of the users not have computer based knowledge so that this web site should be displayed always user friendly environment to user. All the user should be able to login or create a new account through this website. Always should be displayed correct details about the products.
