Scribd
Upload
44 views

SCD Lab 01

This document outlines requirements for developing a warehouse management system. It includes questions to ask stakeholders about inventory, order fulfillment, and reporting needs. Key areas of focus identified are order fulfillment, transportation management, inventory management, and analyzing reports. The document recommends defining a budget, gathering input from key stakeholders, clarifying the need for change, seeking recommendations from others, and leveraging existing experience and expertise within the team.

Uploaded by

Saqib Altaf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views

SCD Lab 01

This document outlines requirements for developing a warehouse management system. It includes questions to ask stakeholders about inventory, order fulfillment, and reporting needs. Key areas of focus identified are order fulfillment, transportation management, inventory management, and analyzing reports. The document recommends defining a budget, gathering input from key stakeholders, clarifying the need for change, seeking recommendations from others, and leveraging existing experience and expertise within the team.

Uploaded by

Saqib Altaf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

SCD Lab 01

Name Saqib Altaf

Reg# 3249

Requirement elicitation for Warehouse Management System


In the below the features of requirement are covered questionnaire, brainstorming, warehouse
requirements etc.

1. How long would it take you to verify inventory levels or overall order accuracy?
2. What do you need to create, pack, and ship orders accurately? Do you have any of this
already?
3. How tracking reference dealt in system?
4. Who works in your warehouse and what job they have?
5. What information does your warehouse leadership need to make a strategic change?
6. Will orders be sent to your warehouses automatically, or will this be a manual process for
the sales team to do?
7. How it will generate reports?

Brain storming:
To improve the ranking on top we need.

 Order fulfilment
 Transportation management
 Inventory management
 Analyze reports
Outline a budget
Different functionality, which we’ll review in a moment, comes with different costs. Work with
leadership to know how much you can spend on the system based on today’s cash-on-hand as
well as the savings or other ROI you expect a WMS to generate.

Key stakeholder input

What do key user groups want from a new WMS? You won't know unless you ask them, and
selecting a system that doesn't meet their needs will result in lost productivity and poor user
uptake. Survey everyone who will be impacted by the change for the most accurate requirements
list possible.

Clarify the need for your change:


Warehouse needs a management tool, but can you articulate why? Can you explain savings you
expect and the benefits your company will see? Is there a customer you can better serve and gain
a positive ROI?

Recommendations from others


SCD Lab 01
Ask your contacts and contemporaries which platforms they like or use. If you have a successful
competitor, look to see which system they use you can search the internet for case studies to see
if your rival is mentioned.

Experience in team

Look for any expertise or experience that you already have on staff to see what works and what
doesn’t. Hire the domain specialist in team and give them job according to domain

Q 02:
Change of shift

In Scenario A This can be one of the reasons for the crashing of the software due to inexperienced
personnel the shift after 12:00 PM wasn’t capable enough to run the software adequately that’s why
the system crashed or didn’t specify time format accurately.

Hardware problem:

In Scenario A Another reason for the software failure can be hardware problem the software would
have been tried to shift to another hardware for which it wasn’t intended to run on that’s why it
crashed.

Time Delay:

In scenario B there is two month delay as mentioned and also there is delay in delivery.

High Cost:

Cost is high as there are conflicts in the system.

Developers Failure:

The system was very huge and complex. So there was not expert of risk management that cause
software crisis.

You might also like