According to the above we try to mention BADLY has different kind Of System such as library system, registrar system, and stock management system and so on. But we are going to develop the system on non renewable part of stock and inventory The current system has its own strength and management system. Weakness, with current system those customers that have not access internet can be used by manually. This is strength that we are identifying from the current system. The current system has more weakness when compared to its strength.
Some of the weaknesses are The customer waits long time to get service The customer spend a lot of time because of the queue A lot of paper work has to be done in a storing process which wastes a lot of time, paper and source. The product in the warehouse is not arranged properly and this will make life harder to search for the right product in specific time. 1. 1 Document Purpose This project purpose is to improve the previous system, which is manual stock and inventory system. Our system is new, computerized, and easy to use.
We started this project with only one purpose that is making fast and good working system within IBID store. 1. 2 Scope of the project The scope of the project is confined within study, analysis, design and implementation part of inventory management system in Braider University. This includes: Study of the existing inventory management system at Braider University. Investigation of the drawbacks of the existing manual stock system. Analyze the functional and non-functional requirements of the system.
Implement the new system using java or C++ methodologies When we mean these, our system is concerned with not overall functionality of the stock management system in general but it concerned only to non renewable part Of the stock management system in Braider University. 1. 3 Intended Audience and Document Overview . Store keeper Material registration Material distribution Check receipts Search existing materials file’s Check items available in store 2. Developer Store keepers this person is assigned to control all activities in BID store.
They have their own work division in there, such as inserting, checking, deleting and updating items info 2. Overall Description 2. 1 Product Perspective In previous stock system there is no computerized work system, Therefore, we preparing a new and self contained computerized system to facilitate the inventory system of BID as modernized system. Fig 2. 1 overview of the system . 2 product Functionality By the current inventory system store kipper can control all items in store by manually.
In this system he/she register new items, check expiry items, check finished items, & prepare reports weekly, monthly & yearly. But all those responsibilities are given for store keeper & the system is difficult b/ c it is manual system, and so many problems can happens rather than use of system, such as time losing, less security and others. Our system can play big roll to simplify all those problems. It has following main functions consuming time minimize difficulties load of work evolves computerized recordable system to prepare timing reports 2. Users and Characteristics In SMS (stock management system) the user will be only the store keeper, and in most case store keepers are performable with how can data receive, store, and check expiration. As we get an info from our requirement our user has knowledge about how can use computer system, and he is also interact with other software systems. And he also can communicate by English language within his Computer. But We have to Only describe how he/ she can use our system within few days, maybe for 2 or 3 days. 2.
Operating Environment client and the server GUI: Microsoft windows Bunt Fig 2. 2 system environment 2. 5 Design and Implementation Constraints We faced some problems during requirement gathering. Example: We didn’t get the store keeper many times and this limits our work time; Our version after finishing the product may need training for the user; this intern consumes money. The software we will develop and the existing hardware may not relate, this and the like problems are limits our work. 2. 6 User Documentation As we mention above our user is performable with item arrangement in tore.
It means the keeper doesn’t need any description about how he/she can store items. Butte have to give deep description about the system, because this is new system. This description will take at least 2 or 3 weeks. Additionally we have to prepare using manual which is simple to read and understand the system. 2. 7 Assumptions and Dependencies Although we are planning to complete our project in a given dead line, we may encounter unexpected problem or risk that can be either artificial or natural disaster. Of them Sometimes failure of system Power problem and virus attack
To handle this problem we have some method to resist not completely but partially by using different secondary storage devices, attaching to email and by taking note as day to day diary. Therefore whatever situation happen or occurred that hinder during the progression of our project we try our best to do what expected from us and reform it. 3. Specific Requirements 3. 1 External Interface Requirements User Interfaces The first face of our system is will be login form. It helps the user to keep secret store’s data. As you see on picture the page will ask the store keeper to enter correct user name & password.
Surname is access name Of the employee & password means secret code of the employee to access the system. Both user name & password are must be available only for employees in store. Fig 3. 1 interface 1 The second page is putted to available options to access registration new items, select and deletes items from store. This page makes a connection b/n pages to do those options. Hardware Interfaces Our user can interact with the system within any personal computer. This (the new) system is hardware dependence; it means the user can’t perform it without installing on a personal computer.
The system needs some inputs & it accepts within peripheral devices, and prepares an output at the mode of display with computer screen. It accepts information of items, such as name of item, manufactured date, expiry date, quantity and other necessary to registration of items. Software Interfaces Our system can perform with some other software. For example, database management system, visual basic system etc. The system interface designed by Visual basic system; the user needs to insert, delete, check info of an item from stored info on database system, in this process there happens haring info.
Communications Interfaces Setting up the server into server mode requires that there will be open ports for accepting connections from the university. The connection between the client and the server uses Connection oriented communication, via TCP/ IP-?Transfer Control Protocol/lenient Protocol, implements reliable delivery of messages. Connection-oriented communication makes programming easier because the protocol includes mechanisms for detecting and handling errors and an acknowledgment mechanism between client and service.
