A PROJECT DESIGN ON STOCK MAINTENANCE SYSTEM (No of pages: 97)
INTRODUCTION TO PROJECT
AIM AND OBJECTIVES
TOOLS AND TECHNOLOGY
SYSTEM ANALYSIS & DESIGN
SOFTWARE DEVELOPMENT LIFE CYCLE
SYSTEM DESIGN AND DATA FLOW DIAGRAM
PAGE LAYOUT AND CODING
TESTING AND IMPLEMENTATION
The main purpose of the stock maintenance system is to manage the entire details of the stock system in an automated way. The stocks which are purchased from the various dealers and suppliers are stored in the store keeper and their entries are recorded into the database. The software system provides facilities for adding new item, removing an item, updating the stock, calculating the turn over, sales amount, total number of stocks. It also involves purchasing of stocks by the customers.
OBJECTIVES OF THE PROJECT:
- To implement the STOCK MAINTENANCE SYSTEM to manage the entire details of the stock system in an automated way.
- To provides friendly relationship with shopkeeper and customers
- To generate complete statistical data on particular stock
- To review the system of inventory model and reorder level of raw material.
- To find out the economic order quantity for cutting tools and consumables.
Problem statement and literature review:
A problem statement is a concise description of the issues that need to be addressed by a problem solving team and should be presented to them (or created by them) before they try to solve the problem. When bringing together a team to achieve a particular purpose provide them with a problem statement.
- Keeping of records of sales and purchase on papers was time consuming and was difficult to store it for long time
- Any enquiry regarding a customer’s bill is very slow as the process is done manually and it involves a lot of paper work.
- Sometimes a small error in doing entries for the entries of bill and bill particulars that cause to major problems in managing the data.
- The calculator (an additional instrument) was required to sum of the amount of items and to calculate the balance amount on paid of amount by customer. It limits the earlier way.
- It needs a lot of care to handle the huge number of files and it needs a lot of storage space.
- It takes a lot of time to generate reports that to have a question of 100% accuracy in one time.
- There is no security of the data as any one can view files
Rosenblatt (1977) says: “The cost of maintaining inventory is included in the final price paid by the customer. Good in inventory represent a cost to their owner; the manufacturer has the expense of materials and labour. The wholesaler also has funds tied up.” Therefore, the basic goal of the manufacturers is to maintain a level of inventory that will provide optimum stock at lowest cost. Morris (1995) stressed that inventory management in its broadest perspective is to keep the most economical amount of one kind of asset in order to facilitate an increase in the total value of all assets of the organization human and material resources.
Ogbo (2011) posits that the major objective of inventory management and control is to inform managers how much of a good to re-order, when to reorder the good, how frequently orders should be placed and what the appropriate safety stock is, for minimizing stock-outs. Thus, the overall goal on inventory is to have what is needed, and to minimize the number of times one is out of stock.
Ghosh & Kumar (2003) defined inventory as a stock of goods that is maintained by a business in anticipation of some future demand. This definition was also supported by Brag (2005) who stressed that inventory management has an impact on all business functions, particularly operations, marketing, accounting, and finance. He established that there are three motives for holding inventories, which are transaction, precautionary and speculative motives. The transaction motive occurs when there is a need to hold stock to meet production and sales requirements.
Methodology and references:
METHODOLOGY TO BE USED:
PROJECT DEVELOPMENT APPROACH
This strategy is often referred to as Software Process Model or Software Engineering Paradigm. A software process model for software engineering is chosen based on the nature of project and application, the methods and tools to be used and the controls and deliverables that are required.
Among them, we will choose a very popular one, The Classical System Development Life Cycle Model or the Waterfall Model. This approach is classically thought of as a set of six interrelated activities that make up the entire system development life cycle.
Water Fall Model:
This is also called Classic Life Cycle Model or Linear Sequential Model or Software Development Life Cycle Model (SDLC). This model has the following activities:
- System Information Engineering and Modeling
- Software Requirement Analysis
- System Analysis and Design
- Code Generation
MODULES TO BE USED :
- STOCK MODULE
- SALES MODULE
- DELIVERY MODULE
- REPLACING THE FAULTS MODULE
SOURCES OF DATA:
1 PRIMARY DATA &
2 SECONDARY DATA.
1 PRIMARY DATA:
The primary data would be collected through personnel interviews with experienced development team and other technical head. The required information will be collected in the following technique:
- On the basis of observations
- By discussions with concerned technical team.
- By personnel interviews with head of organization.
- SECONDARY DATA:
Secondly data will be acquired through various sources such as other relevant website.
The required information will be collected in the following techniques:
- Organizational Manuals
- Documents & Statements
The following can serve to be the sources of information:
- The store’s administrative staff.
- The management of bills.
- The old bills or the history of bills.
HARDWARE AND SOFTWARE REQUIREMENT to be used:
PLATFORM (OS) WIN-2000 /XP / 7
BACKEND SQL Server 2005 or 2008
APPLICATION SYSTEM STOCK MANAGEMENT SYSTEM
MICROPROCESSOR à 500 MHz
RAM à 128 MB, 64 KB Cache
Min. Storage Requirement à 1 GB
Server à 1 (For maintaining database)
There are different design technique will be included:
- Input Design
- Output Design
- Screen Design
- File Design
- Database Design
- Architecture design