Design and Implementation of Laundry Management System
Chapter One
AIM AND OBJECTIVES OF STUDY
This study is aimed at developing a laundry management system for [case study].
The objectives of the system include:
- Implementing a computerized system which can perform a better managing process for laundry
- Implementing a system that increases time performance
- Implementing a system that has automated backup and recovery
CHAPTER TWO
LITERATURE REVIEW
INTRODUCTION
A Literature review is a description of the literature relevant to a particular field or topic. A literature review gives an overview of the field of analysis, what has already been said on the topic, which the key writers are, what the prevailing theories and hypotheses are, what questions are being asked, and what methodologies and methods are appropriate and useful.
CONTEXT AWARE LAUNDRY MANAGEMENT SYSTEM
A Context-aware system adapts and adjusts itself without needing an explicit user intervention in response to changes in its context. The concept of decomposition guided many researchers in their development of the context-aware architectural models. The main goal of using decomposition is to construct a layered architecture, augmented with encapsulation techniques so that context acquisition is separated from its use.
Functionally separating layers from each other allows developers to hide lower layer details from higher layers. An important consequence of using layered architectural approaches is that they easily lend themselves to sharing and re-use of software and hardware components.
Business logic functions, user interface, and data acquisition can easily be separated from each other in a layered approach. One of the conceptual models for context-aware applications proposed by Alisto et al, 2002 modularizes the system using five layers: physical, data, semantic, inference, and application. Despite this complexity, however, for those familiar with Model-View- Controller (MVC) architectural pattern, it is relatively easy to map these five layers to the layered abstraction of MVC. Rehman et al. (2016) has proposed architecture based on the MVC pattern with a special emphasis on userapplication interaction. Another equally important topic in context aware systems is suggesting a representation and storage for context data, in order to simplify the processing and transfer of it as much as possible by the applications. Therefore, successful development and maintenance of context-aware applications depends on selecting a flexible and easy-to-use context model.
Several resources provide valuable information, and a clear vision of the context modelling approaches. Among these, ontology based models possess attributes such as simplicity, flexibility, and extensibility which make the model expressive and generic. Jung et al. (2012) proposed an ontology-based context model that specifies concepts, and relations between them in terms of context.
Additionally, Hong et al study lists several other applications in the areas of information and decision support systems, mobile systems and web services. Truong et al. studied contextaware web service and Miraoui et al. (2008) surveyed pervasive context-aware architectures. Merezeanu et al. (2016) proposed platforms which separate context data retrieval and storage from the business logic. The PCAD platform presents architecture for context aware application development, enabling context aware applications to be built rapidly using services provided by the platform. The platform manages the common work such as context acquisition and storage, therefore enabling the application to focus on the domain specific logic. Merezeanu et al. integrated Wireless Sensor Networks, IoT and Cloud Computing technologies in a framework built as a layered architecture to provide context-aware sensing, computing and communication capabilities to industrial applications.
For example Lu et al. (2010) proposed a service oriented software system architecture using washable RFID tags. Their study concentrated on tracking items between the factory and laundry shop but did not consider the processes taking place in the factory. Tajima et al. (2011) proposed a context aware hanging system for laundry items using hangers which automatically detect the status of clothes, and inform users via multiple media.
LAUNDRY OPERATIONS
In this section, the operations of a laundry from a business processes perspective in order to reveal the fundamental business functions and services are described.
The core laundry business processes typically contains four major activities (Steen, 2014):
- Collection and Transportation
- Administration/Back Office operations
- Scheduling, and
- Cleaning,
The workflow starts with an order from a customer, followed by collection and transportation of unwashed laundry.
Next is the cleaning process, which includes automated operations performed by different machines. Upon completion of the cleaning process, items are first sent to packaging then to customer service, which is responsible for on time delivery and calculation of the bill. Finally, the cleaned laundry is returned back to the customer. At every step of the operation, a cost control process ensures the costs are minimized.
Collection and Transportation: Collection and Transportation process includes dirty laundry collection, transportation to factory, and the return to the customer to an agreed schedule. Since certain items need to be treated according to their condition, attention must be paid during collection. For instance, it is important that linens and bedding used in surgical operations are collected and treated separately from other laundry at every stage.
Administrative: Effective management of administrative activities is vital to maintain a healthy and sustainable financial position.
CHAPTER THREE
RESEARCH METHODOLOGY
INTRODUCTION
Research is an investigation in order to discover new factors through planning and systematic collection analysis and interpretation of data, whereas particular task, therefore, research methodology is a detailed description of what the researcher planned and procedure adopted in gathering new facts relevant to the project work.
It is therefore an established fact that without data, there can be no analysis. This is the crux of social science research. Data can be defined simply as basic facts an figure mostly numeric in nature, resulting from business economic and social activities of man.
This section describes the analysis of existing and proposed system, the system design and the method of data collection.
ANALYSIS OF THE EXISTING SYSTEM
Laundry firm currently uses a manual system for the management and maintenance of critical information. The current system requires numerous paper forms, with data stores spread throughout the Laundry firm management infrastructure. Often information (on forms) is incomplete, or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. This has lead to inconsistencies in various data due to large volume of contrasting customer details leading to mix-up of clothes in the laundry firm which thus leads to delay in collecting the clothes back.
OVERVIEW OF THE PROPOSED SYSTEM
The Laundry Management System is designed for any Laundry firm to replace their existing manual, paper based system. The new system is in form of an e-registration system to control the following; customer information, products, services, users, carts and receipt. These services are to be provided in an efficient, cost effective manner, with the goal of reducing the delay and resources currently required for such tasks as clothes details are bounded to a particular customer with a given id. Since the existing system makes use of tedious administrative tasks, lots paper work and time, in which full information cannot be gotten from busy customers.
CHAPTER FOUR
SYSTEM TESTING AND IMPLEMENTATION
INTRODUCTION
System testing and implementation is the last step in software development. It involves a process of putting into action, a formulated plan. Before implementation, plans must have been completed and objectives must be clear.
CHAPTER FIVE:
SUMMARY, CONCLUSION AND RECOMMENDATIONS
SUMMARY
I present the design and implementation of a laundry management system (LMS) used in vstics laundry. They are usually faced with difficulties in keeping detailed records of customers clothing; this little problem as seen to most laundry firms is highly discouraging as customers are filled with disappointments, arising from issues such as customer clothes mix-ups and untimely retrieval of clothes. The aim of this application is to determine the number of clothes collected, in relation to their owners, as this also helps the users fix a date for the collection of their clothes. Also customer’s information is secured, as a specific id is allocated per registration to avoid contrasting information.
CONCLUSION
The package was designed in such a way that future modifications can be done easily. The following conclusion can be deduced from the development of the project.
- Automation of the entire system improves the efficiency.
- It provides a friendly graphical user interface which proves to be better when compared to the existing system.
- It provides a friendly graphical user interface which proves to be better when compared to the existing system.
- It gives appropriate access to the authorized users depending on their permissions.
- It effectively overcomes the delay in communications.
- Updating of information becomes so easier.
- System security, data security and reliability are the striking features.
- The System has adequate scope for modification in future if it is necessary.
RECOMMENDATIONS
In the world nothing is free from error. So it is very common that the automated laundry systems may contain error. The system is fully dependent on human intelligence. In future the following features will be integrated with:
- Searching based on search analyzer
- Mailing facility
- Chatting facility
REFERENCES
- Alisto et al (2002). Structuring context aware applications: Five-layer model. Retrieved from https://www.researchgate.com/structuringcontextaware on July 29, 2018
- Jung et al. (2012). Context Modelling Using Semantic Web Technologies. Retrieved from https://www. https://www.researchgate.com/semanticwebtechnology on July 29, 2018
- Lu et al. (2010). A Flexible Architecture for RFID Based Laundry Management Systems. Retrieved from https://www.researchgate.com/rfidbasedlaunry on July 29, 2018
- Miraoui et al. (2008). Architectural Survey of Context-Aware Systems in Pervasive Computing Environment. Retrieved from https://www.researchgate.com/pervasivecomputing on July 28, 2018
- Merezeanu et al. (2016). Context-aware Control Platform for Sensor Network Integration in IoT and Cloud. Retrieved from https://www.researchgate.com/contextawareplatform on July 28, 2018
