Sunteți pe pagina 1din 11

nThe main objective of the project is to provide better inventory system.

and providing the current stock details, employee details, new items to be added, transactions as well as reports.provide a basis for recording sales and purchases. The inventory system records the quantity for each item at the end of each period. The two primary inventory systems include a periodic system and the perpetual system. The periodic system involves counting the inventory at the end of each period. Throughout the period, the balance remains unchanged. The perpetual system involves adjusting the inventory balance each time a transaction, such as an inventory purchase or a sale, occurs.The scope of an inventory system considers which needs the inventory system addresses. These include valuing the inventory, measuring the change in inventory and planning for future inventory levels. The value of the inventory at the end of each period provides a basis for financial reporting on the balance sheet. Measuring the change in inventory allows the company to determine the cost of inventory sold during the period. The inventory level and changes allow the company to plan for future inventory needs.

http://www.scribd.com/doc/22286019/project-report-on-sales-and-inventory-management-System Username:Kuldeep password:ksr

4. requirements gathering (document per Fact Finding Technique) Document Functional Requirements(List of Features and its Requirements) Data Requirements(Data Needed) 5. Prototype Agreed Features/functions to be implemented

Requirements for inventory gathering on the HMC


By meeting the requirements for using the inventory gathering process, you can enhance the quality and quantity of data that you collect in the system plans that you create on the Hardware Management Console (HMC).

To maximize the amount and type of hardware information that the inventory gathering process is able to collect from the managed system, ensure that you complete the following tasks before you create a system plan: Ensure that data in the inventory cache on the managed system is maximized and current. See Tips for maximizing data in a system plan on the HMC for more information.

Ensure that the managed system is in the standby state or that the managed system is powered on. Note: You cannot create a system plan if the managed system is in either the power-off state or the recovery state. Ensure that all the logical partitions are activated on the managed system from which you plan to base the new system plan. Ensure that the IBM Installation Toolkit for Linux is loaded if you are creating a system plan that will have information about a Linuxsystem or logical partition running in the Linux environment. This toolkit is required so that systems and logical partitions that run in theLinux operating environment can perform inventory gathering. The IBM Installation Toolkit for Linux is available at the IBM Service and productivity tools Web site (http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/installtools/home.html). Note: If you installed Linux on the logical partition as part of deploying a system plan on a system with HMC Version 7R3.3.0, or later, the Deploy System Plan Wizard installed the necessary Toolkit packages as part of the Linux installation. Ensure that you have a Resource Monitoring and Control (RMC) connection between the HMC and each logical partition. An RMC connection is required for the inventory-gathering process. The use of RMC ensures that the inventory gathering process can capture more detailed hardware information. Without RMC, for example, the inventory gathering process is not able to detect the types of disk drives installed on a managed system. An RMC connection also is required to collect data for Virtual I/O Server device mappings. Note: IBM i logical partitions use Management Central to respond to RMC requests from the HMC. It is possible for a logical partition to have more than one HMC to manage it. In this situation, if you want to use RMC to create a new system plan, you must ensure that you create the system plan from the primary HMC that manages the logical partition because secondary HMCs cannot use RMC. To ensure that the HMC can use RMC, complete the following steps: 1. In the HMC navigation area, select HMC Management. 2. In the contents area, select Change Network Settings. The Customize Network Settings window appears. 3. Click LAN Adapters, select the appropriate adapter from the list, and click Details. 4. On the Basic Settings page of the LAN Adapters Details window, ensure that Partition communication is selected. 5. On the Firewall Settings page, in the Available Applications list, select all instances of RMC, and click Allow Incoming, if necessary. 6. Click OK to close the LAN Adapter Details window. 7. Click OK to close the Customize Network Settings window. 8. Restart the HMC if you made any changes to these configuration settings. For some operating systems, you might need to perform additional steps to ensure that RMC is configured and running correctly. To learn more about configuring and using RMC, see Understanding RMC and resource managers in the Reliable Scalable Cluster Technology (RSCT) documentation (http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp? topic=/com.ibm.cluster.rsct_6100_00.admin.doc/bl503_undrmc.html).

Parent topic:

Inventory gathering process on the HMC

Send feedback | Rate this page

Last updated: Fri, Oct 30, 2009

35.1 Purpose
The requirements specification is a document that clearly and precisely defines the customers logical requirements (or needs) in such a way that it is possible to test the finished system to verify that those needs have actually been met. The point is to ensure that the customers needs are correctly defined before time, money, and resources are wasted working on the wrong solution. Typically, writing a formal requirements specification is the final step in the analysis phase of the system development life cycle.

35.2 Strengths, weaknesses, and limitations


The logical models and prototypes prepared during analysis are often less than adequate as a foundation for system design. The requirements specification builds on the logical models, providing an unambiguous, precise definition of the users needs. If work is outsourced or subcontracted, the requirements specification can be added to the contract to define the deliverables. Although a few pages might be enough to define a simple systems requirements, a complete requirements specification for a significant system can be quite lengthy, and preparing one is both time consuming and expensive. Requirements can change over time, and the requirements specification must be flexible enough to change with them. Often, this is not the case.

35.3 Inputs and related ideas


Writing a formal requirements specification is the final step in the analysis phase of the system development life cycle (Part IV). The system requirements are typically verified against the goals and objectives identified during the problem definition and information gathering process (Part II).The requirements are the basis for the subsequent design stage (Part VI) and suggest test criteria (# 74) and test data (# 75). The sample requirements in this # correspond to specification levels defined in the U.S. Department of Defense competitive procurement process (# 41).

35.4 Concepts
A requirement is something that must be present in the system. The requirements specification is a document that clearly and precisely defines the customers logical requirements (or needs) in such a way that it is possible to test the finished system to verify that those needs have actually been met. The point is to ensure that the customers needs are correctly defined before time, money, and resources are wasted working on the wrong solution. 35.4.1 Types of requirements A behavioral requirement defines something the system does, such as an input, an output, or an algorithm. Under this category, a functional requirement identifies a task that the system or component must perform, and an interface requirement identifies a link to another system component. Non-behavioral requirements define attributes of the system. For example, performance requirements specify such characteristics as speed, frequency, response time, accuracy, and precision. Other nonbehavioral requirements might define such parameters as portability, reliability, security, and

maintainability. Such constraints as physical size and weight, environmental factors, ergonomic standards, and the like are listed in design requirements or constraint requirements. Quality requirements, often stated as an acceptable error rate, the mean time between failures, or the mean time to repair, are sometimes grouped with performance requirements, but many organizations list them separately. Firms that have adopted total quality management often include additional measures of quality. Economic requirements specify such things as performance penalties, limits on development and operating costs, the implementation schedule, and resource restrictions. They are more common in Europe than in the United States. Occasionally, marketing and political requirements are added. 35.4.2 Characteristics of a good requirement A good requirement is unambiguous, testable (or verifiable), consistent with other requirements, correct (every listed requirement must actually be a requirement), understandable, modifiable (requirements can change), and traceable to both higher-level (parent) and lower-level (child) requirements. 35.4.3 Writing requirements The examples shown below illustrate the types of requirements that might be written at three key specification levels. Note that the data dictionary and (perhaps) one or more logical models are often included in the requirements specification as an appendix to provide clear definitions for the data elements, data structures, processes, and algorithms.
35.4.3.1 The high-level system/segment specifications

The high-level system/segment specifications identify the system and its major segments at a conceptual level. Typically they define key terms and identify broad, system-wide objectives and constraints down to the configuration item level. They are logical, describing what the system must do, not how the system must work. For example, imagine that the objective for an inventory system (as defined during the problem definition phase) is: .

Inventory is the goods and products held in stock by a business. Store and business owners need to know the precise number of items available in storage (in inventory) at any given time, so they could place orders and control losses .Usually inventory is held in order to have products available in case there is a delay in supply from the supplier or manufacture

A typical supply chain starts from stores requesting stock to the head office, they issues purchases orders to vendors, who then ship products to a warehouse, who distribute goods to the stores, which sell the products to the end users. Generally speaking, holding a high amount of inventory for long periods of time is not a good thing for a company, because of storage costs, spoilage costs and money management. However, possessing too little inventory isn't good either, because the business can run out of popular items and loose a percent in market share. Management of inventory forecast and strategies is necessary for every serious business and can help minimize inventory costs.

System Investigation The Crack Monkey Bookstore has been in business for about six months and wants to expand to the Internet to help move inventory. This bookstore will be dealing in collage schoolbooks only, both new and used. We will start to implement this system by following the Systems Development Life Cycle by starting with the System Investigation.Feasibility Study Presently we are a local bookstore located in Mesa that has to rely on both word of mouth and local advertisement for business. The books are stored in the back of the building on bookracks in alphabetical order. The Crack Monkey Bookstore has been approved for a 150,000-dollar loan form the government to make these and other improvements. Some of the other improvements are: enlarging the warehouse, redesigning the front of the store and changing the display area. We are hopping to both increase sales and help maintain a more accurate inventory of our books, which will increase our productivity and cash flow. Organizational Feasibility This proposed system would help the store, by increasing the sales and maintaining a more dynamic inventory. With this system in place the hopes of the owners are to be able to expand through out the valley.Economic Feasibility This system will help in the moving of books to decrease on hand inventories. It will also reduce manpower needs with a more accurate inventory system. No need of a large filing cabinet system to keep track of paper flow

Order custom essays brand-new and 100% original, tailored to your needs, price quote
With the new system we will be able to reach more customers there by increasing revenues.Technical FeasibilityThis would put the bookstore in competition with other bookstores that are already on the web, but with our bookstore being local there will be a faster delivery time. Getting the hardware or software to start this is not a problem with today's technical knowledge.Operational Feasibility Being that this is a small business and the owners run it, the acceptance of the new system by the employees should be no problem. Management will support this new system with open arms, being that this is what they want. Suppliers will like the new system for receiving new orders, and the customers will be able to shop from home to get books instead of going to the bookstore. These things found in the investigation are just a few things that are needed to decide whether to up grade their current system or not.System Analysis The organizational analysis or the information systems requirements of the company will be broken down into the needs of the various departments. Then the system will be networked together to integrate the company as a complete information system. Present System Currently there is no E-business system at the bookstore. That is one of many reasons that the Crack Monkey Bookstore is looking into E-business systems. Most of the store's information is a paper trail that requires a lot of time and effort to either find or go back and fix any errors. At the warehouse, along with all the books, is file cabinet after file cabinet, which keeps all of the records for the warehouse inventories. In the accounting/personnel office, there is two file cabinets: one for employee records and the other for accounts receivable and accounts payable. There is another filing cabinet in the store which contains customers records such as addresses, phone numbers, etc., so we are able to contact them when either the order is filled or when we find a requested book. Management is designing the new system with emphasis on ease of use so that the labor-intensive duties of everyday filing and bookkeeping are both easy and more efficient. Functional Requirements AnalysisThe new system will consist of five main sections: 1 Warehouse2 Accounting3 Internet4 Point of Sale5.ResourcesWarehouse The warehouse shall be the center of most activities. Duties range from receiving and shipping inventory to properly identifying storage locations for easy retrieval. This function includes the shipping and receiving not only of new stock, but also of customer point of sale activities. It must be fast, accurate and efficient in order to maintain a sharp business edge over competition. Inventory management has two sections: stock picking / inventory replacement and shipping / receiving. Both will require inventory software as well as a tie-in to the customer database. Hardware requirements are: Bar code scanners, permanently mounted for the shipping and receiving area and mobile RF scanners for the stock pickers and inventory replacement personnel. Additional shipping/receiving hardware includes standard PC I/O terminals, and printers for shipping labels.AccountingThe accounting software is the center of the business. It will require standard accounting software, and shall operate as an immediate update system. Point of sale data shall directly access inventory. When a sale is made dollars and taxes are calculated and logged, inventory is reduced and marked as pending. When the picker has removed the book from its holding area, the item is marked as "picked waiting for delivery." If the book is shipped, the item is marked as delivered when the shipping label is printed. If a book is purchased, dollars and tax are calculated and logged; inventory is increased and marked "pending;" and once the picker has placed the item for

storage the item is marked "stored and available for sale." Accounting will require a PC terminal and printer at a workstation.Internet Internet access shall require a homepage with links to several different pages, depending what the customer wants to do. A "buy" page would reference the buying requirements; a "sell" page would reference the selling requirements; and a "research" page would assist in finding and ordering books not available locally. An "employment opportunity" page would also be available if required. Internet functions would allow customers to check inventory and secure the books they want. They can buy or sell online new or used books, as inventory is available. Internet is directly tied to inventory and customer data files. Hardware required would be a PC terminal with modem to an Internet provider and software to interface to the existing customer database and accounting department.Point of Sale The point of sale will be located in the front of the store, and requires a permanently mounted barcode scanner, a telephone, credit card data entry terminal, and a cash register. This position shall perform all point of sale functions: buy, sell, credit, and debit. Direct access to the customer database is required, as well as communications to the warehouse for order pick up as needed Resources The Resources department is a vital part of the business. It functions to predict the buying trends of existing customers. This utilizes data mining to record and analyze data of existing customers' buying habits referenced to local programs offered at school.When a customer enters into a course of study, the use of specific books could be anticipated, and a program established to provide these books at the correct time and at a reduced rate for the life of the program. This would create a partnership with the customer for a long-term relationship. With the added benefit of being able to resell the used book at a reasonable price, the bookstore provides a cost-saving program to the financially strapped student, while at the same time making a reasonable profit for the store.System Design Point of SaleThe point of sale located at the front of the store is the heart of the business. It has two major functions: buy and sell. All customer interactions are handled from this position. A cash register and credit card machine are the workhorses of the business. Help resources are also available from this position, incorporated within a touch screen and assisted with a keyboard and scanner for input. BuyDuring a customer buy operation, the local inventory can be searched by the ISBN number, book title, author, class, customer ID number, or class number, example: CIS 319. The customer can ask for help finding a book. The customer is asked if he or she belongs to the book club, and his or her personal account number is entered. Once the data is entered, inventory is checked. If the book is on hand, the standard list price, our sell price, plus tax, and total dollars are shown.FindIf the book is not available locally, a search is done first at other local resources, and a delivery estimate is given, along with the price and discount if possible.New MemberIf the customer is not a member of the club, additional sales questioning begins. The business' objec ...

Scope

Definition
Inventory control is the process of managing inventories in such a way as to minimize inventory costs, including both holding costs and potential out of stock costs, write authors William M. Pride, Robert J. Hughes and Jack R, Kapoor in Business.

Inventories
Manufacturers recognize three general types of inventory: raw materials, work-in-process (WIP) and finished goods. At a car maker, a tire is raw material, the chassis on the production line is WIP, and the finished automobile is finished goods. While each is under ownership of the company, it is inventory. Retailers have only finished goods--called "stock" or "merchandise."

Sponsored Links

Free datasheet search


185 million datasheets, inventory and part comparisons. Check it out! www.datasheets.com

Balance
Inventory costs a company in purchasing, storage and handling. Effective inventory control minimizes those costs, by determining the minimum of time required to receive materials from suppliers, and to produce goods to order; and the minimum amount of raw materials required to begin an order.

Systems
An inventory control system is a methodology, or technology, of inventory control. It may be as simple as a handwritten manifest, as complex as a material requirements planning (MRP) system. Enterprise software providers, including SAP and Oracle, offer dedicated inventory control software systems.

Cost of Goods Sold


An effective inventory system minimizes the cost of inventory, including storage costs; handling; and loss through pilfering and obsolescence.

Read more: Define the Scope & Function of Inventory Control | eHow.com http://www.ehow.com/facts_6157507_define-scope-function-inventorycontrol.html#ixzz1pfJ2z2Pi

Examples of Functional Requirements


Functional requirements should includes functions performed by specific screens, outlines of work-flows performed by the system and other business or compliance requirements the system must meet. Interface requirements Field accepts numeric data entry Field only accepts dates before the current date Screen can print on-screen data to the printer Business Requirements Data must be entered before a request can approved Clicking the Approve Button moves the request to the Approval Workflow All personnel using the system will be trained according to internal SOP AA-101 Regulatory/Compliance Requirements The database will have a functional audit trail The system will limit access to authorized users The spreadsheet can secure data with electronic signatures Security Requirements Members of the Data Entry group can enter requests but not approve or delete requests Members of the Managers group can enter or approve a request, but not delete requests Members of the Administrators group cannot enter or approve requests, but can delete requests Depending on the system being described, different categories of requirements are appropriate. requirement gathering process, as appropriate to the system. Requirements outlined in the functional requirements are usually tested in the

System

Owners, Key End Users, Developers, Engineers and Quality Assurance should all participate in the Operational Qualification.

Additional Comments
The functional specification describes what the system must do; how the system does it is described in the Design Specification. If a

User Requirement Specification was written, all requirements outlined in the user requirement

specification should be addressed in the functional requirements.

The Functional Specification should be signed by the

System Ownerand Quality Assurance. If key end users,

developers or engineers were involved with developing the requirements, it may be appropriate to have them sign and approve the document as well. Depending on the size and complexity of the program, the functional requirements document can be combined with either the user requirements specification or the design specification

S-ar putea să vă placă și