Online Inventory Management System Software Requirement Specification, Thesis of Software Engineering

Download Online Inventory Management System Software Requirement Specification and more Thesis Software Engineering in PDF only on Docsity! Graduate Studies By 2015-ag-7990 Adviser Sir Ali Imran A Technical Report Submitted in Partial Fulfillment of Requirements for the Degree of Bachelors of Science In COMPUTER SCIENCE DEPARTMENT OF COMPUTER SCIENCE FACULTY OF SCIENCES UNIVERSITY OF AGRICULTURE FAISALABAD, PAKISTAN 2018 Declaration I hereby declare that the project report entitled “Graduate studies” are product my own development under the guidance of Sir Ali Imran and no part has been copied from any published source (except the references, standard mathematic genetic models/equations/formulate/protocol etc.).I further declare that the work reported in this project has not been submitted by any other either in part or in full, for the award of any other degree or diploma in this university. The university may take action if the information provided is found inaccurate at any stage. Name: Ahmad Mujtaba Reg No. 2015-ag-7990 Contents COMPUTER SCIENCE................................................................................................................................................... DEPARTMENT OF COMPUTER SCIENCE................................................................................................................. LIST OF FIGURE..........................................................................................................................................................V FIGURE 1- CURRENT SYSTEM.................................................................................................................................V 6......................................................................................................................................................................................V FIGURE 2- USE CASE DIAGRAM.............................................................................................................................V 17...................................................................................................................................................................................V FIGURE 3- ACTIVITY DIAGRAM.............................................................................................................................V 18...................................................................................................................................................................................V FIGURE 4- SWIM LANE DIAGRAM.........................................................................................................................V 19...................................................................................................................................................................................V FIGURE 5- DATA FLOW DIAGRAM (LEVEL 0).....................................................................................................V 20...................................................................................................................................................................................V FIGURE 6- DATA FLOW DIAGRAM (LEVEL 1).....................................................................................................V 21...................................................................................................................................................................................V FIGURE 7- CLASS DIAGRAM...................................................................................................................................V 22....................................................................................................................................................................................V FIGURE 8- CRC DIAGRAM........................................................................................................................................V 23....................................................................................................................................................................................V FIGURE 9- STATE REPRESENTATION DIAGRAM................................................................................................V 24...................................................................................................................................................................................V FIGURE 10- SEQUENCE DIAGRAM.........................................................................................................................V 25....................................................................................................................................................................................V FIGURE 11- COLLABORATION DIAGRAM............................................................................................................V 26....................................................................................................................................................................................V 1. INTRODUCTION......................................................................................................................................................6 IN SOFTWARE INDUSTRY REQUIREMENT ENGINEERING IS ONE OF THE MOST IMPORTANT PARTS OF SOFTWARE ENGINEERING PROCESS, WHICH ONE GIVES US THE PROPER SCENARIOS WHAT THE CUSTOMERS WANT, ANALYZING THEIR NEEDS AND CHECKING THE FEASIBILITY WHAT THEY NEED, NEGOTIATING A REASONABLE SOLUTION ETC. IN SOFTWARE INDUSTRIES, A SOFTWARE PROJECT BEGINS WHEN A BUSINESS NEED IS IDENTIFIED. SO THE FIRST STEP IS WE NEED TO UNDERSTAND THE CUSTOMER NEEDS. FIGURE OUT A ROUGH FEASIBILITY ANALYSIS, NOT ONLY THE CUSTOMER’S NEED BUT ALSO WITH THE PEOPLE WHO ARE APPARENTLY INVOLVED WITH THE INTRODUCING SYSTEM. IN THIS PHASE AFTER INTERACTING WITH OUR CLIENT “SLEEK FASHION LTD.”, WE GET SOME REQUIREMENTS FOR AN INVENTORY MANAGEMENT SOLUTION. THIS PAPER WILL BE MORE EASEFUL AFTER COMMUNICATING WITH OUR CLIENT WITH THEIR MORE SPECIFIC REQUIREMENTS. AT THE SAME TIME, IN THIS PAPER WE WILL FOCUS ON INVENTORY MANAGEMENT MODULE. AGAIN THIS PAPER IS A PARTIAL SUBMISSION; MORE DETAIL WILL BE INCLUDED AS PER COMMUNICATING WITH THE ENTIRE STAKEHOLDER’S........................................................................................6 1.1 PURPOSE....................................................................................................................................................................6 1.2 SCOPE........................................................................................................................................................................6 1.3 GLOSSARY.................................................................................................................................................................7 KEY TERMS.....................................................................................................................................................................7 DEFINITION......................................................................................................................................................................7 RMG................................................................................................................................................................................7 READY MADE GARMENTS...............................................................................................................................................7 INVENTORY......................................................................................................................................................................7 INVENTORY MEANS A LIST COMPILED FOR SOME FORMAL PURPOSE...............................................................................7 PRODUCTION CONTROLLER.............................................................................................................................................7 WHO GUIDE AND SUPERVISE PRODUCTION WORK...........................................................................................................7 QC...................................................................................................................................................................................7 QUALITY CONTROL.........................................................................................................................................................7 IIS....................................................................................................................................................................................7 INTERNET INFORMATION SYSTEM...................................................................................................................................7 SRS..................................................................................................................................................................................7 SOFTWARE REQUIREMENT SPECIFICATION.....................................................................................................................7 DFD.................................................................................................................................................................................7 DATA FLOW DIAGRAM....................................................................................................................................................7 PQ....................................................................................................................................................................................7 PRODUCTION CONTROLLER.............................................................................................................................................7 1.4 REFERENCES.............................................................................................................................................................7 3. GENERAL DESCRIPTION.....................................................................................................................................10 3.1 PRODUCT PERSPECTIVE...........................................................................................................................................10 3.3 PRODUCT FUNCTIONS..............................................................................................................................................13 3.4 POTENTIAL USER OF THE OF THE SYSTEM..............................................................................................................13 3.5 USER CHARACTERISTICS.........................................................................................................................................14 3.6 ASSUMPTIONS AND DEPENDENCIES.........................................................................................................................14 List of Figure Figure 1- Current System 6 Figure 2- Use Case Diagram 17 Figure 3- Activity Diagram 18 Figure 4- Swim Lane Diagram 19 Figure 5- Data Flow Diagram (Level 0) 20 Figure 6- Data Flow Diagram (Level 1) 21 Figure 7- Class Diagram 22 Figure 8- CRC Diagram 23 Figure 9- State Representation Diagram 24 Figure 10- Sequence Diagram 25 Figure 11- Collaboration Diagram 26 1. Introduction In software industry requirement engineering is one of the most important parts of software engineering process, which one gives us the proper scenarios what the customers want, analyzing their needs and checking the feasibility what they need, negotiating a reasonable solution etc. In software industries, a software project begins when a business need is identified. So the first step is we need to understand the customer needs. Figure out a rough feasibility analysis, not only the customer’s need but also with the people who are apparently involved with the introducing system. In this phase after interacting with our client “Sleek Fashion Ltd.”, we get some requirements for an inventory management solution. This paper will be more easeful after communicating with our client with their more specific requirements. At the same time, in this paper we will focus on Inventory management module. Again this paper is a partial submission; more detail will be included as per communicating with the entire stakeholder’s. 1.1 Purpose The purpose of this document is to present a detailed description of the Online Inventory Management System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. In this document we will try introduce our stakeholders along with their respective viewpoints, describe the existing problem, combining those various view points, balancing those to reach an ultimate “theoretical” solution of the identified problems, generating graphical reviews through unified modeling language (UML) to formulate the problems and the proposed solution, the project scope and the project schedule. Next we present the solution including system analysis, the deviation between final and initial design, the function of our Inventory management system and testing plan. Finally we evaluate our work on different aspects, present areas of improvement and conclusion. 1.2 Scope The outcome of the project would be automated inventory management service .The software will have all common features and functionalities along with some other special facilities. To provide user efficient working environment. User friendly interface for the target stakeholders. Proper monitoring facility for the authority. 8. Who are the people you want to directly to interact with the system and what should be their domain? 9. What event starts the use case? 10. How does the use case end? 11. Are there any optional situations for the use case? 12. How the processes will work, if the system will become automated? 2.2 Stakeholders view point Different Stakeholders achieve different benefits form a software system. Consequently each of them has a different point of view. So we have to recognize the requirements from multiple view point. For this Inventory management system point of view of stakeholders is:  Executives and upper management beholds the people who are concerned with company management and company’s financial states. They always deal with the profitability and increasing production unit. So their view about the system is how to utilize the system to gain highest profit.  Production controller is the people who supervise a part of a production unit. They will interact with our system to input the data of their subordinate workers. Their view point would be to input that information without any kind of difficulties and maintain the private accounts of each worker  The production supervisors are the people who act as the subordinates of the production controllers, and they must have the real interactions with the root operation. This is not necessary that every supervisor will have distinguished areas to work with; there can be more than one supervisor to supervise a single activity, when it’s a larger one. The supervisors are responsible to check the given input and the outcomes they managed to produce. As these information are required for the operation of our system, production supervisors are identified as one vital stakeholder.  One of the indirect stakeholders of our proposed system is the root level workers of RMG sector, who use to do the primary level jobs of cutting, printing, and combing all the parts together, or any other jobs for example. As because of our limitation of resources, all the workers won’t use our system frequently. But, for occasional possibilities, some of them will use his system, and their illiteracy must be considered by the system developers. 2.3 Collaboration As information from multiple viewpoints is collected, emerging requirements may be inconsistent or may conflict with one another. So considering the scope of feasibility, we have collaborated the following list of requirements from multiple viewpoints. The extracted ideas gathered from the inventory department are:  Online status of item quantity in terms of on-hand, on-hand available, reserved, ordered, to order, rejected, defective and rework able quantities.  Complete excise functionality and generation of excise registers.  Quality Control based on QC parameters.  Physical verification of stock.  Purchasing and subcontracting.  Accounting – inventory synchronization.  Update delay notification.  Keep Track of partial Production.  All Financial transactions related to production. . The next steps of this analysis are analyzing credibility and go/ no- go decision making. For these, this team needs more data to be analyzed and communicating with the client. We hope that we will be able to submit the full Functioning paper within a short time. 3. General Description 3.1 Product Perspective In this modern world of commercialization, garments business has been established as one of the flourishing in Bangladesh. It has been one of the most flourishing export sectors for our country, as we have told in background. Now, our project is concerned with this sector. This is a huge field to cover, as hundreds of manageable aspects can be found to maintain the highest productivity of textile manufacturing. We choose the inventory management as our preferred field to work. To instantiate, this can be specified as a b2b system, from producers to abroad or home dealers through some intermediate business nodes. The important deals that our RMG sector are mostly from abroad interests, as stated above. And our goal would be facilitate this whole process, from collecting raw materials to the finished product shipment. Unlike the old days, RMG sector of Bangladesh has been implementing a variety of management software, in order to enhance the productivity, and to satisfy the customers’ needs. As these deals are very sensitive to handle, and there are a lot of variables that must be maintained, the need of online interaction between the buyer and the seller, or even seller to seller, is a must, and can play a dramatic influence on these deals. As the whole process has multiple steps to the way to finished goods, a single delay in a single step can cause delay in the shipment schedule, suppose our delay in cutting can demolish the required time structure, which can also cause financial damage and bad business reputation. The existing systems have been using not for so long, and the maturity level of software industry in our country is still very low. So, the systems which are being used in recent days in the garments industry do have a lot of bugs, functional dependencies and design constraints. Besides, there is still a lacking of a complete solution for managing garments which is yet to be made. And we have to say, after studying, we find that majority of the garment industry doesn’t use any automated management system, where a large amount of problems in manual management can be solved in automated system. The thing is missing all through and which we have been planning to introduce in these kind of usual management system, is online interface to control the system. Internet has been a pivotal determiner in every aspects life. We are proposing to introduce internet controlling module of this system, so that the authority of our client can monitor and manipulate the system, as well as the database through the internet. At the same time, there are technologies being used to manage payroll, appointments, inventory, and in many other purposes. But as our major concerns will be inventory oriented, we will focus the most on that.  Administrator: They are authorized staffs to control the system. They are assigned with different level of authority to control different parts of the system like inventory and administrators. In addition, administrators are responsible to maintain database. 3.5 User Characteristics The users of the software are classified into two categories – Registered user and unregistered user. Both users will be able to visit the homepage of the website but only the registered user is allowed to give input in the system. To work through the system one user should go through some fixed steps- First of all the user should be registered. The separate production module will be presented to the user as a catalog for viewing. The user can browse through the categories to choose the module they desire. The user can input partially complete production quantity of the total production. Finally the product will be delivered within a fixed and trusted time period to the next production module. And the process will continue until the shipment is completed 3.6 Assumptions and Dependencies After completing our study about inventory and inventory management system, we thought that, our Inventory management software will be ideal one in terms of garments industries of our country. According to our view that inventory system will Contain module like Information of different products category Available stock Price of different items transaction details One can also extract any reports relating to purchase and Sale. The inventory management application will have all the categories, Subcategories, items, Stock details and reports. The administrator of this inventory system will have right to create product, add items delete items etc. The application will provide all information of the products. The category will be tagged with subcategory. Again the subcategories are tagged with different items in the respective category and rate of the item. Each item will have a specific bar code. The rates will be tagged to the bar code. Using these functions the user can: Add items to inventory Edit items in inventory Add an action for an item The application will also help to generate reports to get latest update on Master Entry Purchase order entry Receive entry Delivery entry Report This inventory system also has some dependencies like  If data’s are inserted it cannot be deleted except administrator  User can insert a data but can’t delete  If data’s are not inserted, user cannot view report.