Describing Business Requirements

Objective

After completing this lesson, you will be able to explain business requirements and how they relate to the configuration of Concur Request.

Introduction

In this unit, you will learn about business requirements and how they translate into configuring Concur Request.

Starting with this unit, and continuing through the remaining units in this learning journey, you are a project manager for Contoso Visuals, Inc. (CVI) and have been tasked with implementing Concur Request within the organization. You will be provided with a set of business requirements that will be used in the remaining courses as the foundation of the configuration examples.

After completing this unit, you will be able to:

  • Explain business requirements and how they relate to the configuration of Concur Request.
  • Identify CVI's key business requirements.

Overview of Business Requirements

Business requirements are the goals and guidelines you will use when working with Concur Request. They represent how a business is put together and how it operates on a day-to-day basis, including organizational structures, processes, and other software systems.

In this unit, as the project manager for CVI, you will be tasked with working with internal stakeholders to gather the information needed to configure Concur Request to best meet the requirements.

What Business Requirements are Needed to Configure Concur Request?

The requirements needed to configure Concur Request are very similar to those needed for Concur Expense or Concur Invoice. You'll want to start with the company's requirements around financial data and go from there. Other items you'll want to focus on are approval processes, the types of travel and expenses to include, and business rules that must be enforced during the request process.

How Should I Gather Business Requirements?

The best way to gather requirements is to ask the experts within the organization. The first step of the process is to identify those experts. You can do this by finding out who manages the current methodology and working with them. Those people should know the current process and could be the resources managing the new processes within Concur Request.

Once those people have been identified, you can start asking them about their needs. You can document your findings in any format you wish, such as a spreadsheet or text document. SAP Concur recommends breaking that document up into sections to group similar requirements together. Sections can include financial system requirements, approval processes, audit rules, expense types, travel segments, and so on. You can do whatever you like, as long as you and the stakeholders can interpret the document.

Now that you know a bit about how to gather and document requirements, let's go gather some!

Log in to track your progress & complete quizzes