Exquisite Linen Limited: System Requirements And Information Gathering Techniques

Background Information

The EEL store management system project is a user application. The objective of this system is to develop and design a customer relationship management system software which manages both the relationship between EEL and all the client retail store and the information regarding the stock of the organization will be represented. The system will be able to maintain a business relationship with both countries in the United States and China. It is an internet-based user interface that has the component manager to manage the inventory and maintain the (Qu and et al. 2017). The EEL system is a real-time warehouse database that handling more extensive stocks of an organization. This can be used to store the records of individual stored details, product details, keep track of the inventory, and manage the distribution of stock over several stores. However, thee system merely saves thee restocking and sales data and notified the manager about the low stock.  The aim is to reduce the tracking strain instead to handle the information about all the store’s maintenances (Chen and et al. 2016). The aim of this proposed system is to ensure the reliable availability of several representatives of several clients.  In general, the system directed towards large to small stores, also it allows services for both online and offline purchasing. The manager of the company who is responsible for maintaining sufficient product for retail as well as a manufacturing business (Souri and et al. 2019). The system is monitoring the overall In and Out transaction of every sale which a sales representative of a specific store within a particular sales region.  

To implement and manage the relationship between different customers that governs store records with the help of EEL.

To cover more than one sales area and generate a bill for performing a transaction on the last day of every month for salespersons.

To capture the information about all the retail stores, their customers, date of the visit of the customer, number of orders and the salesperson who visited in the retail store.

To manage party plans as well as, and the sales representative allocate for each customer and store the details of the party, customer and the representative of the party plan and enhance the performance of the system and also controls other issues included in the EEL organization.

To hence reduce manual effort and save valuable time of the manager, representatives, and customers

Current business processes and system limitations

Managing and maintain information for the EEL store includes gathering requirements and distributing requirements and assimilating those requirements in the development of project management processes and activities. The information-gathering process is repetitive processes that are used to gather all the necessary requirements and organize information related to different types of resources.

The information-gathering process can be categorized into four different methods are as follows:

Delphi technique: While managing a software project the presence of this technique facilitates various questionnaires to implore various ideas. The responses of the individual stakeholders, experts and participants are summarized.

Brainstorming: The list of all activities carried out through the entire system development processes are listed by using this method (Foster and Godbole, 2016). A mass interviewing method and open conversation help to generated several ideas about the better implementation of the EEL management system.

Interviewing: This method is done by placing an interview between participants, stakeholders, and experts which helps to identify the various risk factors associated with the implementation and deployment of the system.

Root cause analysis: This method is used to identify the underlying issues and problems while developing the system so that the problems can be overcome during the time of implementation.  

All the above-defined methodologies can be used by the development team of the EEL organization to meet the system requirements. Since the software/system development processes are associated with the various risks and if those are not addressed during the time of project management then it creates several issues such as time schedule, resources, quality of the project as well. The above-defined information gathering processes help EEL organization recovers the negative effects of various risks through the life cycle of EEL system development.

CRM is an application that consists of a set of applications that are designed to support various perspectives of business. Managing the business process include customer data, manages the interaction between customers, access different business information, tracking automated sales record, manages marketing, contracts, provide support for their customers, manages organizational employees, manages resources and many more have been the major advantages of CRM (Laurila 2017). CRM commonly uses the application to manage EEL business-customer relationship in a systematic way to manage employees, business customers such as retail stores, customers whether the online or offline customer and all the sates related to all the customers.

Functional requirement

The functional requirements that are related to the proposed system refer explicitly functionalities that are working as an inventory and online shipping. This leads towards the success of the given system including the primary objectives to enhance that of the performance of the existing system (Navimipour and Soltani 2016). The functional requirements of the newly proposed information system are: –

• Managing and controlling inventory and stock related to the business include both decorators as well as home items such as aromatherapy and candles.
• Maintain and managing customer relationships between the company and retail companies as well as managing offline and online customer demands.
• Monitoring upon all the retails stores of the company and look up the existing stock as well as the stock purchased by the retail store of the company.
• Maintain separate database to store the related information of the product those are recently entering into stock and the product those are purchased from the stock (Atieh and et al.2016).
• Maintaining the specific database contains the information related to the particular product types that are unavailable in stock and restocking the demands.
• The system is holding the information about the specific product which is not currently present in the EEL manufacturer to retain the goodwill of their customers (Gagnon, Lampron and Buyl 2016).
• Systematically managing party plan in various geographical sales area and the information related to package delivery and the information related to delivery partners.

Stakeholder Requirements

This newly designed Information System consists of various non-functional requirements that are necessary for understanding and controlling the record details in the management system (Toyoda and et al. 2017). The functional requirements are specifically mentioned below.

• The proposed system must consist of a responsive nature associated with all allowed provisions which monitoring several related information.
• The user interface of the system will be responsive with response time would be within 4 seconds.
• This particular system must ensure working related to Microsoft Accessibility.  
• The employees of the organization should be capable of working with all the resources available in the system.
• This system must contain the ability to store information about customers, salespeople who visited on the EEL information management website and the total amount of order placed by the retail stores (Fountas and et al. 016).

a) Event Table 

An event table lists all the events in a row and column that consists of the pieces of information about each event described in the column.

Trigger: Represents an event fired by the system.

Source: Represent an external actor or agent that sends data to the system.

Activity/Use case: The system performs behavior while an event occurs.

System response/Output: An output generated by the system and goes to the system 2017 (Wild).

Destination: Represents an external actor or agent that collects data from the online system.

Figure. 1: Use case diagram for EEL information management system

Image source: (Created by author)

A fully developed Use Case Description for the ‘Create Customer’:

a) Domain Model Class Diagram 

In system development, a domain modeming can be defined as the conceptual representation of the domains, which incorporates both the information and the behavior. It describes the abstractions of the given system that is required to be represented in software.

The following figure. 2: shows that the graphical representation of the individual component of the newly proposed system.

Manager: Permits the system users to access the system to look up the management services provided by the system (Camilleri 2016).

Customer: Allows the user of the system to access the system to search, order items serve by EEL.

Stock: Stock is used to storing all the products and raw materials that have been stored and will be ordered by the client/Customer.

Inventory: Inventory basically maintains records of all the items and the quantity of each product. It consists of the following attribute InventoryID, ProductID, Quantity.

Item: Item is the actual product produced by the EEL Company. It consists of the following attributes such as ItemNo, BarCode, ItemDesc.

Orders: A customer while places an order. It consists of the following item OrderNo, BarCode, OrderDate, DeliverDate.

Shipments: The product is successfully ordered by the EEL organization.
 

Figure. 2: Domain Model Class Diagram for EEL information management system

Image source: (Created by author)

Figure. 3: Class Diagram for the ‘Customer’ and ‘Order’ classes for EEL information management system Image source: (Created by author)

Conclusion 

The following information system is a desktop-based web application suitable for EEL organization. The information system provides an automated version of inventory management and shipping management for their customers which provides will benefit both the retail stores and customers. Also, the entire system makes the processes online in which the relationship all the retails stores can search to find a particular product, a product can be added to the account for party plan and manage order for the individual sales area. The organizational staff is coactively working with their own geographic sales area, and the system includes a way of managing customer relationships over various retail stores. This system also provides a report on the last day of every month. The system matches all the requirements of the EEL organization and will ensure the benefit of the organization.

• It can be recommended from the above study that the functionality of the EEL system can be extended in the near future by adding some features which make the system more user friendly.
• It is recommended that the exact customer requirements must be understood in the first place before the incorporation of EEL system.
• The installation of intrusion detection system is also highly recommended in order to address the data security risks coming from the social engineers.

References 

Atieh, A.M., Kaylani, H., Al-abdallat, Y., Qaderi, A., Ghoul, L., Jaradat, L. and Hdairis, I., 2016. Performance improvement of inventory management system processes by an automated warehouse management system. Procedia Cirp, 41, pp.568-572.

Camilleri, E., 2016. Project success: critical factors and behaviours. Routledge.

Chen, X., Hu, P., Shum, S. and Zhang, Y., 2016. Dynamic stochastic inventory management with reference price effects. Operations Research, 64(6), pp.1529-1536.

Disney, S.M., Maltz, A., Wang, X. and Warburton, R.D., 2016. Inventory management for stochastic lead times with order crossovers. European Journal of Operational Research, 248(2), pp.473-486.

Foster, E.C. and Godbole, S., 2016. Review of Information-Gathering Techniques. In Database Systems (pp. 523-538). Apress, Berkeley, CA.

Fountas, S., Carli, G., Sørensen, C.G., Tsiropoulos, Z., Cavalaris, C., Vatsanidou, A., Liakos, B., Canavari, M., Wiebensohn, J. and Tisserye, B., 2015. Farm management information systems: Current situation and future perspectives. Computers and Electronics in Agriculture, 115, pp.40-50.

Gagnon, M.P., Lampron, A. and Buyl, R., 2016, January. Implementation and adoption of an electronic information system for vaccine inventory management. In 2016 49th Hawaii International Conference on System Sciences (HICSS) (pp. 3172-3178). IEEE.

Hebner, R.E., Uriarte, F.M., Kwasinski, A., Gattozzi, A.L., Estes, H.B., Anwar, A., Cairoli, P., Dougal, R.A., Xianyong, F.E.N.G., Hung-Ming, C.H.O.U. and Thomas, L.J., 2016. Technical cross-fertilization between terrestrial microgrids and ship power systems. Journal of Modern Power Systems and Clean Energy, 4(2), pp.161-179.

Johnson, H. and Andersson, K., 2016. Barriers to energy efficiency in shipping. WMU Journal of maritime Affairs, 15(1), pp.79-96.

Laurila, J., 2017. Developing Computerized Maintenance Management System.

Marchewka, J.T., 2016. Information technology project management: Providing measurable organizational value. John Wiley & Sons.

Navimipour, N.J. and Soltani, Z., 2016. The impact of cost, technology acceptance and employees’ satisfaction on the effectiveness of the electronic customer relationship management systems. Computers in Human Behavior, 55, pp.1052-1066.

Qu, T., Thürer, M., Wang, J., Wang, Z., Fu, H., Li, C. and Huang, G.Q., 2017. System dynamics analysis for an Internet-of-Things-enabled production logistics system. International journal of production research, 55(9), pp.2622-2649.

Souri, A., Rahmani, A.M., Navimipour, N.J. and Rezaei, R., 2019. Formal modeling and verification of a service composition approach in the social customer relationship management system. Information Technology & People.

Toyoda, K., Mathiopoulos, P.T., Sasase, I. and Ohtsuki, T., 2017. A novel blockchain-based product ownership management system (POMS) for anti-counterfeits in the post supply chain. IEEE Access, 5, pp.17465-17477.

Wild, T., 2017. Best practice in inventory management. Routledge.

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order