STOCK MAINTANENCE SYSTEM

PROJECT ANALYSIS AND DESIGN:

Table of content:

1.Executive summary. 2.Project scope, objectives, deliverables. 3.Cost and budjet management. 4.Schedule management. 5.Risk management plan. 6.Project control and reporting plan.

EXECUTIVE SUMMARY: The project entitled PRODUCT STOCK MANAGEMENT is to maintain the stock in the warehouse. Stock Maintenance gives an idea about how products are maintained in the particular concern. The products that are to be purchased, the products that are to be sold are maintained here. This project also gives idea about the faults in the purchased product and the products that are to be replaced also been given. Further some additional details of the current stock that is available in the store is also given. Stock maintenance in this project is done in an authorized way. The password and user id has been set here. As a whole the marketing process can be improved if the stock is maintained properly. The stock has to be maintained properly since the whole marketing process can be improved. Stock maintenance in this project gives the idea about how products are maintained in a particular concern. The stock details which includes the amount of stock available, the stock is to be purchased, the date or the time it is being bought or delivered, the amount that is already available are maintained in this project. The stock maintenance in this project is understood by goin through the modules that is being involved. The whole economic status is being improved properly if stock is maintained. Storing of information about the stock values and updating the stock values for each organization which is using this system, keeps track of all the information about the stock exchange that are made by the customers, having registration feature of adding up new customers to the organization are provided in this system. PROJECT SCOPE: The Stock Maintenance System is developed after the component of the entire necessary UML Component diagram, which offers higher reliability and efficiency in handling. The developed System plays a vital role irrespective of the field of work because it has own

importance as it provides complete solution in protecting and managing the stock details of Industry. OBJECTIVE: The main objective behind developing the system is to handle the most important System which has its root in almost all the companies and firms, with ease and accuracy. This System requires utmost care because there should not be any errors in processing as well as managing the Stock details of the industry of a Concern. All these constraints are considered the system is developed to cater to the needs of the industry.The developing process of this System has to take care of certain important stages with the strong view that it deals with the most important instance of the world, the currency. Hence lots of efforts are taken to ensure that the administrator i.e., the employer enjoys all the benefits of this System. It must flexible in such a way that it allows future enhancement (or) modification i.e., these enhancement and all other aspects are handled and it is tailored in such a way that it meets the need of the administrator.

MODULAR DESCRIPTION:

STOCK REPORT: Stock Report will contain all the detail about the stocks purchased quality of stocks and cost details of the stocks.

UPDATE REPORT: Update Report will contain detail about the recent modification of the stock database. Updating the performed whenever a new stock is purchased (or) when a stock is delivered.

DELIVERY REPORT: Delivery report will contain detail about the Stocks delivered to the Customer. It also contains detail about the profit and lose encountered during the self of stocks.

PHONE ORDER: Phone Order will contain detail about the stocks ordered through Phone. This will be under the control of telephone operator.

WALK IN SALE: Walk in Sale will contain details about the stocks ordered in person; this will be under the control of sales clerk. COST AND BUDGET MANAGEMENT: A budget is a comprehensive, formal plan that estimates the probable expenditures and income for an organization over a specific period. Budgeting describes the overall process of preparing and using a budget. Since budgets are such valuable tools for planning and control of finances, budgeting affects nearly every type of organizationfrom governments and large corporations to small businessesas well as families and individuals. A small business generally engages in budgeting to determine the most efficient and effective strategies for

making money and expanding its asset base. Budgeting can help a company use its limited financial and human resources in a manner which best exploits existing business opportunities. Intelligent budgeting incorporates good business judgment in the review and analysis of past trends and data pertinent to the business. This information assists a company in decisions relating to the type of business organization needed, the amount of money to be invested, the type and number of employees to hire, and the marketing strategies required. In budgeting, a company usually devises both long-term and short-term plans to help implement its strategies and to conduct ongoing evaluations of its performance. Although budgeting can be timeconsuming and costly for small businesses, it can also provide a variety of benefits, including an increased awareness of costs, a coordination of efforts toward company goals, improved communication, and a framework for performance evaluation.

SOFTWARE REQUIREMENT SPECIFICATION: An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time. The SRS document itself states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it. It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be.

A well-designed, well-written SRS accomplishes four major goals:

It provides feedback to the customer. An SRS is the customer's assurance that the development organization understands the issues or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language, in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.

It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies ideas, and helps break down the problem into its component parts in an orderly fashion.

It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.

It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.

SRS are typically developed during the first stages of "Requirements Development," which is the initial product development phase in which information is gathered about what requirements are needed--and not. This information-gathering stage can include onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of the customer or client's current business environment. The actual specification, then, is written after the requirements have been gathered and analyzed. The National Bureau of Standards, IEEE (Standard No: 830-1984), and the U.S Department of Defense have all proposed candidate formats for software requirements specifications. The general structure is implemented with the related software application SOFTWARE TOOLS: MS-VISUAL BASIC:

Visual Basic 6.0 is fastest and easiest way to create single user and client/server applications for Microsoft Windows. Visual Basic 6.0 provides complete set of tools to simplify rapid application development both for the experienced professional and new windows programmers.The Visual part refers to the method used to create Graphical User Interface.The Basic part refers to the BASIC language used by more programmers than any other language in the history of computing. It is an ideal programming language for developing sophisticated professional applications for Microsoft. ORACLE 9i: Oracle 9i makes most necessary conversion to the code automatically when we convert our data base. However the conversion process makes some changes to code that need to aware of, and there are some additional changes that must made in order to run the application successfully in oracle.

SYSTEM REQUIREMENT : Hardware Requirements: Processor CPU Speed Strorage Capacity RAM Capacity: : : : Intel Pentium III or later. 1.0 GHZ 20 GB

512 MB

Software Requirements: Front End Back End Operating System : : : VISUAL BASIC 6.0 Oracle 9i Windows Family

Application Software

Rational Rose

The frontend of this project is Visual Basic 6.0 and Backend is MSAccess. This project is readily available, to buy this project send your postal address by SMS we will send you this project by postal VPP you can pay to the postman and collect the CD. If you are looking for different backend please email the details. We will give this project in different backend with additional cost along with video how to change the backend, and how to use the project. If you wish to write the whole project yourself, the option is open we can help you to design and write the project. We will make a video how to write the whole project and we will send to you, by watching that video you can able to write the project yourself. For more details please contact us. RISK MANAGEMENT PLAN: The main difference between an amateur and a professional trader is that the latter always tries to understand and control portfolio risks. Before entering into any trade, good traders first think about how much risk to take and how much risk exposure comes with a particular trade selection. Only then do they allow themselves to think about how much profit they stand to make. Prudent investors always cut down their position and exposure if they determine that a portfolio carries too much risk. They calculate this all-important estimation by employing Risk Management, that set of methods and procedures taken to estimate, quantify, and control risk for the purpose of achieving optimal investment results.

Potential risk treatments Once risks have been identified and assessed, all techniques to manage the risk fall into one or more of these four major categories:

Avoidance (eliminate, withdraw from or not become involved)

Reduction (optimize - mitigate) Sharing (transfer - outsource or insure) Retention (accept and budget)

Ideal use of these strategies may not be possible. Some of them may involve trade-offs that are not acceptable to the organization or person making the risk management decisions. Another source, from the US Department of Defense (see link), Defense Acquisition University, calls these categories ACAT, for Avoid, Control, Accept, or Transfer. This use of the ACAT acronym is reminiscent of another ACAT (for Acquisition Category) used in US Defense industry procurements, in which Risk Management figures prominently in decision making and planning. Risk avoidance: This includes not performing an activity that could carry risk. An example would be not buying a property or business in order to not take on the legal liability that comes with it. Another would be not flying in order not to take the risk that the airplane were to be hijacked. Avoidance may seem the answer to all risks, but avoiding risks also means losing out on the potential gain that accepting (retaining) the risk may have allowed. Not entering a business to avoid the risk of loss also avoids the possibility of earning profits.

Risk reduction Risk reduction or "optimization" involves reducing the severity of the loss or the likelihood of the loss from occurring. For example, sprinklers are designed to put out a fire to reduce the risk of loss by fire. This method may cause a greater loss by water damage and therefore may not be suitable. Halon fire suppression systems may mitigate that risk, but the cost may be prohibitive as a strategy. Acknowledging that risks can be positive or negative, optimizing risks means finding a balance between negative risk and the benefit of the operation or activity; and between risk reduction and effort applied. By an offshore drilling contractor effectively applying HSE Management in its organization, it can optimize risk to achieve levels of residual risk that are tolerable. Modern software development methodologies reduce risk by developing and delivering software incrementally. Early methodologies suffered from the fact that they only delivered

software in the final phase of development; any problems encountered in earlier phases meant costly rework and often jeopardized the whole project. By developing in iterations, software projects can limit effort wasted to a single iteration. Outsourcing could be an example of risk reduction if the outsourcer can demonstrate higher capability at managing or reducing risks. For example, a company may outsource only its software development, the manufacturing of hard goods, or customer support needs to another company, while handling the business management itself. This way, the company can concentrate more on business development without having to worry as much about the manufacturing process, managing the development team, or finding a physical location for a call center.

PROJECT CONTROL AND REPORTING PLAN:

Description Monitoring is about assessing what work has been completed for a Programme or Project including costs, risks and issues. In addition the SRO and Board will routinely monitor if the business case continues to be viable in terms of alignment with strategic objectives. This usually takes the form of the production of documentation and reports at key stages. Reporting provides the Programme/Project Board with a summary of the status of the programme/project at intervals defined by them. Controls usually relate to stages in projects and are established to control the delivery of the projects products (outputs). In project management controls take two forms - event driven and time driven. Event driven means that the control occurs because a specific event has taken place. Examples of event driven controls include End-Stage Reports, completion of a Project Initiation Document (PID) and creation of an exception plan. Time driven controls are regular progress feedbacks. Examples of time driven controls include checkpoint and highlight reporting. This does not replace the need for the Board to maintain an overall view of progress.

Purpose Monitoring is used to oversee progress of products, outputs, and outcomes. Reporting advises the correct people at the correct time of positive and negative events, allowing for progression or remedial action as appropriate. Controls then assist with both monitoring and reporting by provision of required review points such as End Stage Assessments. The diagram snapshot below displays some of the monitoring, reporting and control elements that are associated with project management in particular the area of Initiating a Project CONCLUSION: Thus the project gives the detailed explanation about how stock is maintained in an organization.it also gives idea about how stocks are to be purchased and how to be maintained in a company.