INTRODUCTION

1.1   Project Introduction

As we enter in the era of information technology of 21st century, there is a general feeling that human being needs to change their way of thinking and method of functioning to meet the challenges of the changing environment, this project is aimed at developing Sale Supply37 Application for business to digitize and also improve our business activates.

 In the current manual system the Customers get their Sales (buy something) from the Company/Dealer by visiting the Company/Dealer directly or with the help of a phone call. This system is not good for Customers and for the Company/Dealer because it have a lot of flaws and shortcomings. When the Customer visit the Company/Dealer directly then he or she has to wait for a lot of time. And most of the times they can't get their Buy (Sale Product) on that day they have to come on the next day. The current system is also not good for Companies/dealers because the Company/Dealer doesn't know in advance that he or she has to examine how many Customers. So the Companies is always in hurry and not giving proper time and attention to the Customers so the Customers become unsatisfied form the Companies behavior and they can't visit the Company/Dealer again. So there is a need for such a system that satisfy both the Customers and Companies.

The proposed system save the customer Sales/SaleOrders record And also examine those customer which visit the company directly. So within in a few second through phone Call Customer will get his Buy some Products from Company/Dealer and the Customers have to visit the Company/Dealer on the selected date and time.

1.2.  Need of Project

We have developed this project because the current system is manual.

• Time Consuming.
• No Storage Media for Customers History.
• No Storage Media for Suppliers History.
• No Expenses Record.
• Not a Respected Method.
• No Specific Reports.
• No Suppliers Satisfaction.
• No Customers Satisfaction.

1. Advantages of Proposed System

This system can be used any types of Business. If the Customers want to give Order no need to visit the Company/Dealer, for getting Product’s they can get there Product Demand, within a few second through phone Call. There is no waiting time. The Customer’s inform through Email and then Customer’s visit the Company/Dealer on Selected Date and Time. Through this Application we examine also those customer’s which visit the company directly.

• Sales/Sale’s Order
• Stock Records
• Security
• Flexibility
• Customer’s History
• Supplier’s History.
• Both Customer’s and Supplier’s Payment History.
• Expenses Record.
• Invoice.
• Receipt.
• Daily basis Reports.
• Custom Reports. 

1.  Disadvantages of Manual System

There are many shortcomings in the present system. This computerized system will fulfill all the requirements of the Customer’s, Supplier’s and Company. The following are the basic disadvantages of the manual system.

• More time consuming.
• Huge waiting time.
• No human respect.
• No Customer’s and Supplier’s satisfaction.
• In-efficient.
• No Media Storage.
• No Security.

1.5 Four Principle of Requirements Engineering

• Feasibility study.
• Requirement Analysis
• Requirement definition.
• Requirement specification

1.6 Feasibility Study ^[1]

The feasibility study comprises visits to designed client. Inutility it started with information gathering about existing system. It is observed that the current system ruined manually the core work to transfer manual system to automated computerized system. Focus is made on collection of required different aspects of new system (to be developed) were discussed first of all a question arrive was   handed over to the client manage which was composed of   discussion held start of feasibility study initial and target were set together and understanding upon delivery was finalized one discussion was over with client. There are three kinds of feasibility studies.

1. Operational feasibility
2. Technical feasibility
3. Financial feasibility.

1.6.1 Operational Feasibility

The software is very user-friendly the User’s, can easily operate the software without any difficulty.

1.6.2 Technical Feasibility

DBMS	SQL Server
Operating system	Microsoft Windows 8
Design and coding tools	C Sharp(C#)
Documentation tools	MSOffice 2010,MSOffice2007
Designing tools	Adobe Photoshop, Coral Draw, Icon Maker, Iconion

Table 1.1 Technologies needed For the System

This is a Desktop base application. The following technology needed for the system to be developed and is available to everyone have a Business.

1.6.3 Financial Feasibility

The cost of converting the manual system into a computerized is one of important factor. The proposed system is financially very visible and feasible. There are no costs like searching and hiring personal. The technologies that we are going to use are in common use and are always made available to work with. So there is no purchase costs involved no huge cast involved in training. Also no extra hardware or additional staff is required.

1.7 Requirement Analysis

 It is a communication between customer and software development team. To get better understanding of the requirement, a prototype was made and then we with different group of Company/Dealer and meet with different Customer’s for requirement gathering, which resulted more benefits and functionalities which was imposable without requirement specification.

1.8 Requirement Definition

In this stage we define User of the system and their role in operating this software. I.e. the User can manage the whole system but if user access the software illegal then the software is automatically block and then the software running want the Pincode.

1.9 Requirement Specification

Out of various alternatives structured language is used to write down functional requirement. Structure language which is a restricted form of natural language use template to specify requirements.

A feasibility study is a short focus study that aims to answer of a number of questions.

1. Does the system contribute to overall object of the system?
2. Can the system be implemented using current technology and with given cost and schedule constraints?
3. Can the system  integrated  with  other  system  which  are already  in place?
4. You should talk with information source to discover the answer to the question?
5. What is the problem with current processes and how a new system would help alleviate these problems?
6. What direct contribution will the system make to the business objective and requirements?
7. Can information be transform to and from other organizational system?
8. Does the System require technology that has not previously been used in organization?
9.  What  must  be  supported  by the  System  and  what  need  not  to be supported?
   
   
   A successful completion and adoption of the automated system will definitely make the work easier around its field by maintaining all records about Business i.e. Customer’s, Supplier’s history, Expenses etc. The existing manual system will be replaced by automated. As it is mentioned earlier that a manual system is more difficult, insecure and time consuming. All the information are kept and derived manually. This system will be able to meet all the requirements of easy to use, easy to maintain, secure etc. Records and information will be kept and upgraded safely and data will be processed faster in purposed automated system.

1.10 Advantages of Requirements Specification

1. Avoid the fraud.
2. Technical problem.
3. Operational problem.
4. Storage for data.
5. Provide setting
6. Account for users.

1.11 Software Process Model ^[2]

A software process model is a structure on the development of a software product. Several models exist to streamline the development process. Each one has its own advantages and it’s up to the development team to adopt the most appropriate one for the project sometime a combination of the models may be more suitable. So a software process model is an abstraction of actual process, which is being described. Process model may include activities, which are parts of the software process; software product and the role of people involved in the software engineering software development process include the following activities

As discussed earlier that there are several software development models some major type of these models are.

• Water fall model
• Iterative and incremental development
• Agile development
• Spiral development model etc

1.12 Model used in this project

In our project we used Evolutionary development model because the requirements is not fulfill we meet with different Companies/Dealer/Shopkeeper’s and Customer’s and collect information from them, then start analysis after analysis we start our project design when the project design is complete then come back and meet with the group of Companies and different types of Customers and show the design when they were satisfied from our design then we start the implementation when the implementation is complete then again come to them and show our project implementation when they are satisfy then we cover his project. We use evolutionary development model because in first the requirements is not fill full. Evolutionary prototyping model is a software development life cycle model in which software prototype created for demonstration and requirements elaboration. Evolutionary prototyping model includes the four main phases.

• Definition the basic requirements
• creating the working prototype
• Verification of the working prototype

Evolutionary prototyping model allows create working software prototypes fast and may be applicable to projects where.

• System requirements early are not known in advance
• creating fundamentally new software
• Developers are not confident in software architecture and algorithms
  
  
  There are two types of evolutionary development model.

1. Exploratory
2. Throw away prototyping

1.12.1 Exploratory Development

In this model the objective of the process is to work with the customer to explore their requirements and deliver a final system. The development starts with the parts of system that are understood. The system evolves by adding new features proposed by the customer.

1.12.1.1 Steps in the exploratory model

1. A starting point is determined for the work. All the information available is gathered
2. Together in an attempt to get an idea of what the new system will be expected to do, and how it can be done.
3. A rudimentary first-generation system is put together, based on the information gathered and the ideas formulated in the first step.
4. The first-generation system is tested to see how it performs, what it can and cannot do, and what might be done to improve it.
5. A second-generation system is developed from the first one, based on the improvements proposed in the previous step.
6. The second-generation system is tested, as was the first. Its performance is evaluated, and possible improvements determined.
7. The process is repeated as many times as necessary to obtain user satisfaction, or until it is decided that the project is unworkable.
8. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.
   This model resembles the prototyping model, but it begins at a more nebulous starting point, and proceeds in a less formal fashion. This scheme is not particularly cost-effective and sometimes results in less-than-optimal systems, so it should be used only when no viable alternative seems to exist. The exploratory model is a systems development method (SDM) occasionally used to design and develop a computer system or product and basically consists of planning and trying different designs until one of them seems to be the right one to develop. This model works best in situations where few, or none, of the system or product requirements are known in detail ahead of time.

1.12.2 Throw away Prototyping

In this model where the objective of the evolutionary development process is to understand the customer’s requirements and hence develop a better requirements definition for the system. The prototype concentrates on the experimenting with the customer requirements that are poorly understood. An evolutionary approach to software development is often more effective than the waterfall approach introducing systems. That meets the intermediate need of customers. The advantage of a software process that is based on evolutionary approach is specification can be developed incrementally. However from an engineering and management perspective the evolutionary approach has two problems.

• The process is not visible managers need regular deliverable to measure progress.
• If systems are developed quickly it is not cost-effective to produce document that reflect every version of the system.
• Systems are often poorly structured continual change tends to corrupt the software structure incorporating software changes becomes increasingly difficult and costly.

1.13 Tools Used

The tool(H/W & S/W) used in the development of “Sale Supply37 Application(SS37App)”

Hardware and Software Used

Following hardware and software will be use in our proposed project.

Software’s Used

Following Softwares and Languages will be use in Project:

• SQL Server 2014.
• Visual Studio 2013(Select Language C#).
• Adobe PhotoShop CS6.
• Coral Draw X5
• Icon Maker
• Iconion
• MS Windows OS 10

 Hardware Used:

• Minimum version of dotNetFrameWork 3.5 will be required.
• CPU 1.8 GH.
• RAM 1 GB
• HDD 160 GB.