Consider the user requirements document as a tool for helping the reader understand the functionality required of a new system. Another way to think of this is if you were asking an employee to research a new electronic system and you provided the user requirements document as a tool for him/her to use as a guide for selecting a new Supply Chain Management system. How would they choose one system over another? You need the document to have enough detail to provide the employee with that guidance. You should review the Developing User Requirements online lesson in week 8s material to understand the correct format for capturing the requirements.

The provided search results do not seem to directly answer the question of "User Requirements Deliverable and Discussion", but here's an overview of what a user requirements document typically includes and how it is used:

Explanation:

A user requirements document, also known as a user requirements specification (URS), is a formal document that outlines the functionalities and features that a software system, product or service must have to meet the needs of the end-users. It is typically created during the early phases of software development, after the business analysis team has gathered and analyzed user requirements.

The document should include a clear and concise statement of the problem that the system is addressing, as well as a list of functional and non-functional requirements. Functional requirements specify what the system should do, while non-functional requirements specify how the system should behave, such as performance, security, and scalability.

Some common components of a user requirements document include:

Introduction: a brief overview of the problem and the expected outcomes.

Business Requirements: a detailed description of the end-users and their needs that the system is intended to address.

Functional Requirements: a detailed description of the functionalities and features that the system should have to address the business requirements.

Non-functional Requirements: a detailed description of the performance, security, and other non-functional requirements of the system.

Constraints: any constraints, limitations, or dependencies on the system design or implementation.

Assumptions: any assumptions made in the design or implementation of the system.