Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
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 ne
Typology: Thesis
1 / 16
This page cannot be seen from the preview
Don't miss anything!
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.
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 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.
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.
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.
Easy maintenance and administration. Ensure high level of security. This system will help in tracking records so that past records can be verified through them and one can make decisions based on the past records. This system will complete the work in a very less time resulting in less time consumption and high level of efficiency.
Key Terms Definition RMG Ready Made Garments Inventory Inventory means a list compiled for some formal purpose Production Controller Who guide and supervise production work. QC Quality Control IIS Internet Information System SRS Software Requirement Specification DFD Data Flow Diagram PQ Production Controller
www.agilemodeling.com/artifacts/ crc Model.html_._ http://en.wikipedia.org/wiki/Unified_Modeling_Language http://en.wikipedia.org/wiki/Requirements_analysis http://rfptemplates.technologyevaluation.com/rfp/for/inventory-management-garments.html http://www.slideshare.net/ahmedhasan/ieee-830-1998-software-requirements-specifications http://gulnazahmad.hubpages.com/hub/A-Step-by-Step-of-Garment-Manufacturing
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.
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
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.
The given diagram is a scenario of current system. In the present system, when the administrator sealed the production order then the people related to the production, specially PQ ,administratorās make the total production planning, and according to the plan the make a check sheet. According to the production planning total production work is divided in to partial productions. These partial productions are the part of total production. Combining this entire partial production element total production take place. But the fact is that in each stage of this partial production face production loses because of manual updating system. They cannot follow the check sheet properly. So they cannot deliver their shipment with in due date. So our client wants a system which can provide automated updating system, accurate calculation of produced goods, provide proper stock information, send notification if the shipment wonāt take place on due date, keep track of partial production, and all Financial transactions related to production.
Inventory Management System must be designed to meet the dictates of the marketplace and support the company's strategic plan. Along with the inventory system Garment industries need some more special attributes. The Softwareās for Garment are specially made for managing the various steps in order processing of garments manufacturing process. This software is modular in design and is web enabled for remote access as well as intranet usage without the need to install in every machine. Inventory Management System has some features which are badly needed for a complete Inventory system of Garment industries. So the features are, Web based interface User based Login - password based authentication for data protection. Dynamic Modular structure ā Each and every section related to a production has separate menus. Manage master details of buyer, supplier and vendor. Job Work tracking. Raw material tracking. Shipment tracking. Product category and product stock information with value. Reports include purchase, issues, stocks & categories. Customized package Notification System in case of any process delay. Check sheet automation. These features are primary requirement of our client for this inventory management system. This feature list will change in terms of client demand
There are two groups of users in our system. They are the production controller and the system maintenance administrators. They have different authorities in our system which is shown as follows; ļ Production Controller: They are the Controller of the production in each and every section related to total production. They can insert the detail product information which is completed. Besides, they are able to view order sheet and sample sheet to keep their production accurate. But their authentication domain is limited between their field, which can be exemplified as the production controller who is in charge of cutting, will not have the access to the information about payroll or customers.
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.
