16it429(se).docx

SE (IT307)

[ID No.]-16IT429

Practical-2 Aim: Develop the Software Requirements Specifications (SRS) document for a specific system. Inventory Management System 2.1 Introduction: 2.1.1 Purpose of the system: Inventory management software. Inventory management software is a software system for tracking inventory levels, orders, sales and deliveries. It can also be used in the manufacturing industry to create a work order, bill of materials and other production-related documents. 2.1.2 Scope of the system: The “Inventory Management System” software is being developed as an accurate and efficient system for the user . In this system the record of the each request details are preserved along with their transaction related to them. The system is also made secured as all the updation and transaction can be done by the authorized person .

2.2 General description of the system: 2.2.1 Overall description: [Describe the general functionality of system information, user characteristics, user objective, general constraints placed on design team. Describe the features of the user community with software system and the application domain.]

2.2.2 Feasibility study: 1. Technical Feasibility: The system is self-explanatory and does not need any extra sophisticated training. As the system has been built by concentrating on the Graphical User Interface Concepts, the application can also be handled very easily with a novice User. The overall time that is required to train the users upon the system is less than half an hour. The System has been added with features of menu-driven and button interaction methods, which makes the user

6th Semester

[Page No.]

SE (IT307)

[ID No.]-16IT429

the master as he starts working through the environment. The net time the customer should concentrate is on the installation time. 2. Operational Feasibility: It determine which machine's characteristics best fit the over-all needs of the client, and how the proposed system's operational capabilities compare with the present

3. Implementation Feasibility: Implementing our project is very feasible as it is very user friendly, what it requires from us is to just connect few PC’s in LAN and then it is possible for customers to give feedback parallel. 4. Economic Feasibility: The system should provide cost effective interface by considering less power consumption approach. 5. Resource Feasibility: It is also an essential part of a feasibility study. It includes questions regarding time required to complete the project, type and amount of resources required and dependent factors. 6. Market Feasibility: A market feasibility study typically involves testing geographic locations fpr real estate development,project and usually involves parcels of real estate land. Developer often conduct market studies to determine the best location with in jurisdiction, and to test alternative land uses for given parcels.

2.3 Functional Requirements: 2.3.1 Module description: 1. Secure registration and profile management facilities for Customers 2. Browsing through the website to see the packages that are there in each category of packages like family, religious, honeymoon packages. 3. Adequate searching mechanisms for easy and quick access to particular packages, schemes and services. 4. Regular updates to registered customers of the TMS about new arrivals. 5. Uploading ‘Most visited’ packages in each category of packages. 6. Strategic data and graphs for Administrators and agents about the tours that are popular in each category and age group. 7. Maintaining database of regular customers of different needs. 8. Travel agents are responsible for internal affairs like processing payments, getting customer's feedback, updating status and answering client's queries online. 9. Feedback mechanism, so that customers can give feedback for the tour which they have visited. Also facility rating of individual place by relevant customers. Also feedback can be given on the services provided by the agency. 10. Adequate payment mechanism and gateway for all popular credit cards, cheques and other relevant payment options, as available from time to time. 6th Semester

[Page No.]

SE (IT307)

[ID No.]-16IT429

2.3.2 Functions of various user of the system: There are mainly 2 user of the product: organization, main operator& customer 1. Organization: The travel agency is the main user of the system .it will decide the various product expire date & price of various items. 2. Main operator: The organization hire various agents at various locations to manage the records of customers in each city.  Functions of agent:  Database management of product, stock details & customers.  Advertising  Communicate with customers  Management of payment  Take feedback from customers  Solve queries 3. Customers:  Login  Give personal details  Choose tour package  Payments  Ask queries  Feedback

2.4 Non- Functional Requirements: 2.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 their orders & edit it. 2.4.2 Reliability: o Application should be highly reliable o It should generate all the updated information in correct order. 2.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 registrationinformation 2.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. 2.4.5 Portability:

6th Semester

[Page No.]

SE (IT307)

[ID No.]-16IT429

o The application should be portable on any windows based system incorporating any hardware interface. 2.4.6 Reusability: o The same system will be used in each new agency.

2.5 Interface Requirements: 2.5.1 GUI 2.5.2 Hardware Interface   

Processor RAM Hard Disk

:::-

Pentium III Processor 256 MB 20 GB

2.5.3 Software Interface  

Visual Studio .Net 2003 Microsoft SQL Server 2000

2.6 Data Dictionary: 2.6.1 Table Name: login_table Description: To store the admin, customer, customer Login Details Primary Key: User Name Sr. No. 1

Name

Datatype

Constraint

Description

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

6th Semester

[Page No.]