MIS(3IT05) 20IT479

Practical-1
Aim: Develop the Software Requirements Specifications (SRS)
document for a specific system.

Textile Management System

1.1 Introduction:
1.1.1 Purpose of the system:
Textile management systemise the process whereby consumers directly buy goods,
services etc from a seller interactively in real-time without an intermediary service over the
Internet.

1.1.2 Scope of the system:

➢ We plan to develop an application that reduces the manual work of staff

workers. Make an application that can be used from any machine in the
LAN.
➢ Make an application that give access to different department according
to their departments to their rights.
➢ Application saves the data in the database in universal XML format.
➢ Reduce errors caused by manual processing of data.
➢ Reduces the chance of stealing the information.

1.2 General description of the system:

1.2.1 Overall description:

The proposed system is developed to create a simple, user friendly and

to use software that avoids the tedious task done by the existing system. The
proposed system is accessible only to authenticated user of the system wherein
all users of the system contain their valid user id and password.

The main requirement of this project is to make the task of inserting the
employee related details, product related details and maintain them very simple
and time saving. After inserting the details it must be retrieved whenever
necessary by search criteria which will give the actual information needed by
the valid user.

1
5th Semester
MIS(3IT05) 20IT479

Order Receiving Purchase of Raw

System Material Supplier
Concern

1.2.2 Feasibility study:

Preliminary investigation examines project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All systems are feasible if they are given unlimited resources and infinite time. There
are aspects in the feasibility study portion of the preliminary investigation:

1. Technical Feasibility:
o The proposed system uses MySQL for the database, HTML, JS and CSS for the
front-end, PHP for back-end
o The proposed equipment have the technical capacity to hold the data required to use
the new system using MySQL Database.
o It will provide adequate response to inquiries, regardless of the number or location
of users.
o System can be upgraded after development.

2. Operational Feasibility:
Operational feasibility aspects of the project are to be taken as an important part of the project
implementation.
o There is sufficient support for the management from the users.
o The System will work properly after proper development and deployment.
o This system is targeted to be in accordance with the above-mentioned issues.
Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can
undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.

3. Economic Feasibility:
As the necessary hardware and software are available in the market at low cost, the initial
investment is the only cost incurred and does not need any further enhancements. Hence it
is economically feasible.

2
5th Semester
MIS(3IT05) 20IT479

1.3 Functional Requirements:

1.3.1 Module description:

1. LOG IN
• Enter User ID and Password To Login.

2. MDI Form
• This form acts as container for all other forms.

3. Customer Details Form

• This form allows user to view Customer details.

4. Customer Order Form

• This form allows user to enter Customer Order details.

5. Customer Bill Form

• This form allows user to enter Customer Bill details.

1.3.2 Functions of various user of the system:

1 . Customer :
• Login
• Give Personal Details
• Enter Order Details
• Payment
• Place the Order
• Create Customer Report
2 . Supplier :
• Login
• Give Personal Details
• Select Raw Material
• Make Order
• Show Available Stock
• Payment
• Create Supplier Report

1.4 Non- Functional Requirements:

1.4.1 Security:
o It should be providing password to log on to the system.
o He/she should be able to see the record of package & edit it.

3
5th Semester
MIS(3IT05) 20IT479

1.4.2 Reliability:
o Application should be highly reliable
o It should generate all the updated information in correct order.

1.4.3 Availability:
o Any information about customer should be quickly available from any computer to
the authorized user. The previously visited customer’s data must also be maintained
and should be made available to the system authorized by simply entering his
registration-Id.

1.4.4 Maintainability:
o The application should be maintainable in such a manner that if any new
requirement occurs then it should be easily incorporated in an individual module.

1.4.5 Portability:
o The application should be portable on any window based system incorporating any
hardware interface.

1.4.6 Reusability:
o The same system will be used in each new agency.

1.5 Interface Requirements:

• 1.5.1 GUI
▪ The home page will contain a good interface for both customers and
suppliers. It will also include serval option like customer login and supplier
login by which both parties can perform different operations.

▪ Customer will have a profile page which can only be accessed by customers
login id and password. The customer is able to update their profiles and can
make changes. Also customer is able to see their previous Orders and
payment details. They can also ask any query.

▪ Payment gateway will be fully secure and user is able to choice any payment
method of their choice like UPI, Net Banking, Card etc.

4
5th Semester
MIS(3IT05) 20IT479

1.5.2 Hardware Interface

Intel Pentium P4
256 MB of memory
15” screen
1.0 GB of disk space
Windows XP
1.5.3 Software Interface
• Operating System Windows Operating System
• Front End C#.NET
• Back End MS SQL server 2000

1.6 Data Dictionary:

1.6.1 Table Name: login_table
Description: To store the admin, customer, Supplier Login Details
Primary Key : user_name
Sr.
Name Datatype Constraint Description
No.
1 user_name Varchar(10) Primary key To store the user name
2 user_type Varchar(10) Not null To store user type
3 password nvarchar(10) Not null To store the password

1.6.2 Table Name: customer_details

Description: This table stores the details of all the Customers.

Fields Data Type Description

customer_id Int It stores the ID of the customer
customer_name varchar(100) It stores the name of the customer
contact_no varchar(50) It stores the contact no of customer
email varchar(50) It stores the email of user customer
address varchar(MAX) It stores the address of customer
lock Int It stores the value either 0 or 1

5
5th Semester
MIS(3IT05) 20IT479

1.6.3 Table Name : supplier_details

Description: This table stores supplier details.

Fields Data Type Description

supplier_id Int It stores the supplier ID
supplier_name varchar(100) It stores the supplier name
contact_no varchar(50) It stores the contact no
Email varchar(50) It stores the email id of the supplier
Address varchar(MAX) It stores the address of the supplier
Lock Int It stores the value either 0 or 1

6
5th Semester