Question

Case Study: Auto-Parts Warehouse Management System

Jack Greig and Daniel Cox have several years of experience of running an auto-parts business as a supplier in a major city of Australia. The current warehouse management system is not able to handle highly dynamic procedures that can help them move and store inventory at peak efficiency and lowest cost. Jack and Daniel have decided to develop a new Auto-Parts Warehouse Management System where its functionality can be applied throughout all core warehouse processes, transforming the warehouse into a competitive advantage.

You are the business system analyst assigned to develop this system. In your meeting with Jack and Daniel, they provided significant details regarding the basic operations of the system. They expect the system will perform the various functions such as receiving all types of orders, inventory control, order processing, pick up and process orders, order load management, outbound documentation, system alerts, packing orders, and crystal reports. Please note, you must consider the number of wireless communication devices that configure with the proposed system and enables the warehouse management to run the distribution using real-time operations. These extensive system functions will improve warehouse operations by minimising costs and increasing productivity.

Task

Further background

Refer to the Project Vision Document submitted in Assessment Item 1 regarding Auto-Parts Warehouse Management System. In this assignment, you are required to prepare a report that describes the detailed architecture and design of the proposed system.

answers the questions:

1. Identify and briefly describe the functional and non-functional requirements for the proposed system. (2 pages, times new roman, size 12)

Answer 1

Functional Requirements:-

The main purpose of functional requirements is to define all the activities or operations that take place in the warehose management system. of auto parts. These are derived through interactions with the users of the system.  The general Functional Requirements arrived at the end of the interaction with the Users are listed below.

1. The System holds all the details of the all the employees who are working in the organization.

2. It allows admin to manage all types of users, hold their details, authenticate these users at the time of login and accordingly provide different options to communicate with the system.

3. It holds the details of all the warehouses which are part of our company.

4. It holds the details of all Product Stocks held in the ware-house of the company.

5. The system allows the warehouse manager to log into the system and enter their inwards entries related to their warehouse.

6. It also allows them to view the list of inward entries.

7. The system allows the warehouse manager to log into the system and enter their outward entries and their purpose related to their warehouse .

8. It also allows them to view the list of Outward entries.

9. Whenever an inwards entry is entered then accordingly the stock number will be automatically updated.

10. Whenever an outward entry is entered then accordingly the stock number will be automatically updated.

11. The system allows the warehouse  manager to log into the system and enter stock return entries and the reason for return.

12. Whenever a return entry is entered then accordingly the stock number will be automatically updated if the reason is order cancelled otherwise It need not update the stock.

13. It allows the authorized manager to process the order.

14. It allows the admin to view the list of users and take the print

15. It allows admin to generate warehouse details report.

16. It allows admin to generate inwards details report.

17. It allows admin to generate outwards details report.

18. It allows admin to generate returns details report.

19. It allows admin to generate stock statement report.

20. It allows any user to logout when he wants to come out from the system.

NonFunctional Requirements:-

1. Analysis, Design & Data requirements :-

  The Analysis & Design phases of the system yield Use Case diagrams, textual analysis, Sequence Diagrams, Class diagrams & Data Dictionary. Data dictionary consists of process statements showing how data is flowing from starting point to end point.

2. Constraint:-

  These are the requirements that are not directly related to the functionality of the system. These should be considered as mandatory when the system is developed.

1. The system should be available over the intranet so that the Users like the warehouse managers & clerks can use the system from their respective locations which could be anywhere in the organization.

2. The system should be easy to understand and organized in a structured way. The users should also receive feedback about any errors that occur.

3 .Data integrity should be maintained if an error occurs or the whole system comes down

4. An inward entry should be entered in the database whenever stock comes into the warehouse. That is the number of items should be updated automatically.

5. An outward entry should be entered in the database whenever stock goes out into the warehouse. That is the number of items should be updated automatically.

6. A return entry should be entered in the database whenever stock returned into the godown. That is the number of items should be updated automatically.

3. Guidelines

Some guidelines should be follow to enhance the usability of the system.

1. The system should display a user friendly menu for users to choose from.

2.The system should display warehouse ID and item to be selected from the popup list in the forms .

3.Services of the system should be available 24 hours a day.

4.The system should be designed in such a way that it is easy to enhance it with more functionality. It should be scalable & easily maintainable.