ug

1. OCSP
Online College Stationary Portal

2. Scenario (Case)
• The OCSP system provides user friendly interface and also provides powerful and
efficient database management system. The aim of proposed system is to
develop a system of improved facilities. The existing system work is done
manually thus hampering its accuracy and effectiveness. The proposed system
can overcome the limitations of the existing system.
• The system provides proper security and reduces the manual work. The existing
system has several disadvantages and many more difficulties to work. The
proposed system tries to eliminate or reduce these difficulties up to some extent.
• The proposed system will help the user to reduce the workload and mental
conflict. Through this system it is possible to print various reports for the
organization.
• The aim of the proposed system is to develop a system of improved facilities.
• Admin can generate requirements of product.
• Admin can allocate product to H.O.D. and H.O.D. can allocate product to the staff.

3. Software Requirements Specification
• Hardware Specification
• Processor : Intel Dual based System
• Processor Speed : 1GHz to 2GHz
• RAM : 512MBto 1GB
• Hard Disk : Requires space of min.10GB
• Keyboard : 104 keys
• Software Specification
• IDE & Language : Visual Studio 2019 –ASP.NET
• Framework Using C#
• Database : SQL Server
• Operating System : Windows 7/8/8.1/10

4. Revision History
Name Date Reason For Changes Version
Add Multiple Type of
User
Customer want this application
get used by different users
1

5. 1 Introduction
• This document aims at defining the overall s/w requirement for
Online College Stationary Portal
• The final product will be having functionalities mentioned in this
document & assumptions for any additional functionality should not
be made by any of the parties involved in developing /testing
/implementing/ using this product.
• In case it is required to have some additional features, a formal
change request will need to be raised and subsequently a new release
of this document and/or product will be produced.

6. 1.1 Purpose (Objective of the system)
• Create distinct users based on their roles and permissions.
• Authenticate users at their login.
• The system provides assurance of proper accuracy and effectiveness thereby improving
the related services.
• This system provides better management by providing desired flexibility, fast response,
ability to support changes and ability to maintain quality services.
• This system will have stronger controls like passwords and various levels of user access
options will be added.
• We are going to develop the proposed system with an objective to eliminate the running
cost by overcoming the continuous stationery expenses, manual storage need, and extra
staff in the information resources department of the organization.
• We have tried to develop this system keeping in mind the user of the system. So there is
not much need for a trained professional to use this system.

7. 1.1 Purpose:Conti..
• We have made a very user friendly interface so that it can be easy to
access.
• Provide database security to store the data related to the proposed
project.
• Provide the information about available stationary products.
• Facility to allocate the available stationary products to users from
respective departments of a college.
• Facility to order new stationery products that are unavailable or finished.
• Providing interface to view stock details of the available stationary
products in the stock.
• Mechanism to reset the password in case the user forgets it.
• Facility to generate reports for all the modules of the proposed project.

8. 1.2 Document Conventions
This document will use IEEE format. The format for headings is as
follows:
Major headings are in bold 14pt font, and concurrent headings in
bold 12 pt font. Sections are in the format of x.y, where x and y are real,
positive integers. 1.3
1.3 The intended audience
The intended audience for this document are the development team,
testing team & the stake holders of Fashion Mart

9. 1.4 Product Scope
• Functional Requirements
• Secure registration and profile management facilities for users
• Maintain database of regular customers of different needs
• Provide the information about available stationary products.
• Facility to allocate the available stationary products to users from respective
departments of a college.
• Facility to order new stationery products that are unavailable or finished.
• Providing interface to view stock details of the available stationary products in the stocks.
• Non-Functional Requirements
• Secure access of confidential! data (customer details)
• 24 X7 availability
• Better component design to get better performance at peak time

10. • 1.5 Definition, Acronyms & abbreviations
OFM- Online Fashion Mart
HTTPS: Secure Hypertext Transfer Protocol
TCP/IP: Transmission control Protocol/Internet Protocol
• 1.6 References IEEE recommended Practice for SRS
– IEEE Standards

11. 2. Overall description
2.1 Product perspective
It’s a new self contained product
The existing system was a manual system.
The proposed system is aimed towards the vendors to reach out to the
maximum cross section of customer and common people who can be
potential customer.
This product aims at bridging the gap between the Users,Product and
the requirements.
OCSP will be a user-friendly, ‘quick to learn’ and reliable software for
the above purpose

12. 2.2 Product Functions
• Module wise requirements: -
• Manage User Type: - This module is for the requirement from user that
creates type of user like Staff/Administrator.
• Manage User: - This module is for the requirement from user that creates
and manage user’s details.
• MANAGE DEPARTMENT DETAILS: - This module is for the requirement from
user that creates and manage department details.
• MANAGE STREAM DETAILS: - This module is for the requirement from user
that creates and manage stream details.
• MANAGE WHOLESALER DETAILS: - This module is for the requirement from
user that creates and manage wholesaler details.

13. • MANAGE PRODUCT DETAILS: - This module is for the requirement from user that
creates and manage product details.
• STOCK IN MAINTENANCE: - This module is for the requirement from user that
creates and manage stock details.
• ALLOCATE PRODUCT: - This module is for the requirement from user that creates
and manage product allocation details.
• MANAGE PRODUCT Requirement DETAILS: - This module is for the requirement
from user that creates and manage product requirement details.
• Order Details: - This module is for the requirement from user that creates and
manage product order details.
• Order Bill details: - This module is for the requirement from user that creates and
manage order bill details.
• Reports: - In this module user requires all the reports.

14. 2.3 User Classes and Characteristics
• Administrator
Database Management: Control the database and keep track of all records of users
View all details: View the details and control the whole site.
Generate reports
• HOD
Manage Product ,product requirement and allocation details.
• Faculty
Manage product requirement and allocation details

15. • 2.4 Operating Environment
• Software requirements
– Windows 7 or above operating system
– IIS Server
– MSSQL Server
• Hardware Requirements
– Core i5 processor
– 4GB RAM
– 20GB of hard disk space in terminal machines
– 1TB hard disk space in Server Machine

16. 2.5 Design and Implementation Constraints
• Only administrator can access the whole system.
• Each user should have individual ID and password.
• Database is password protected.
• No multilingual support provided.

17. 2.6 User Documentation:
• There will be no user manuals, or tutorials provided as it is made as
simple as web beginners can also use it easily with best web GUI
functionality.
• Help menu will be provided instead.
2.7 Assumptions and Dependencies:
• Each user must have a valid user id and password
• Users must log in to the system to access any record.

18. 3. External Interface Requirements
3.1 User Interfaces
• List all the Input and output screens
• Manage User Type
• Manage User
• MANAGE DEPARTMENT DETAILS
• MANAGE STREAM DETAILS
• MANAGE WHOLESALER DETAILS
• MANAGE PRODUCT DETAILS
• STOCK IN MAINTENANCE
• ALLOCATE PRODUCT
• MANAGE PRODUCT Requirement DETAILS
• Order Details
• Order Bill details
• Reports
3.2 Hardware Interfaces:
• PCs, Laser Printer, Wi-Fi Router
• The system will use the standard hardware and data communication resources.
• This includes, but not limited to, general network connection at the server/hosting site, network
server and network management tools.

19. 3.3 Software Interfaces
• OS: Windows 7/8, Linux
• Web Browser: The system is a web based application; clients need a
modern web browser such as Mozilla Firebox, Internet Explorer, Opera,
and Chrome. The computer must have an Internet connection in order
to be able to access the system.

20. 3.4 Communication Interfaces:
• This system use communication resources which includes but not
limited to, HTTPS protocol for communication with the web browser
and web server and TCP/IP network protocol with HTTPS protocol.
• This application will communicate with the database that holds all
the ordering information. Users can contact with server side through
HTTPS protocol by means of a function that is called HTTPS Service.
This function allows the application to use the data retrieved by server
to fulfill the request fired by the user

21. 4. System Features
Overall Use case Diagram

22. 2) Admin based
Use case
Diagram

23. 3) HOD based Use
case Diagram

24. 4) Staff based
Use case
Diagram

25. 5. Other Non-functional Requirements
5.1 Usability:
• The system provides a help and support menu in all interfaces for the
user to interact with the system. The user can use the system by
reading help and support.
5.2 Security:
• The system provides username and password to prevent the system
from unauthorized access. The password must be of eight characters.

26. 5.3 Performance:
• The system response time for every instruction conducted by the user must
not exceed more than a minimum of 10 seconds. The system should have
high performance rate when executing user’s input and should be able to
provide response within a short time span usually 50 second for highly
complicated task and 20 to 25 seconds for less complicated task.
5.4 Availability:
• The system should always be available for access at 24 hours, 7 days a
week. Also in the occurrence of any major system malfunctioning, the
system should be available in 1 to 2 working days, so that business process is
not severely affected.

27. 5.5 Error handling:
• Error should be considerably minimized and an appropriate error
message that guides the user to recover from an error should be
provided. Validation of user’s input is highly essential. Also the
standard time taken to recover from an error should be 15 to 20
seconds.
5.6 Ease of use:
• Considered the level of knowledge possessed by the users of this
system, a simple but quality user interface should be developed to
make it easy to understand and required less training.
5.7 Business Rules:
Rule Types Descriptions
Structural rules A user must own at least one user account.
Behavioural rules An individual order must be have bill details
Definitional rules The total price is defined as all product in order.

28. 6. Other Requirements
6.1 Database Requirement: Tables (Entities) List out the Tables- Master
and Transaction
•Table Name: tbl_user
•Table Name: tbl_usertype
•Table Name: tbl_stream
•Table Name: tbl_depatment
•Table Name: tbl_wholesaler
•Table Name: tbl_product
•Table Name: tbl_allocation
•Table Name: tbl_requirement
•Table Name: tbl_stockMaintenance
•Table Name: tbl_order
•Table Name: tbl_orderProduct
•Table Name: tbl_bill
•Table Name: tbl_billProduct