BR030 - Change The Global Receipient IRC-Notifications To Local

BR.
030 Business Requirements Definition & Mapping form
BR.030 BUSINESS REQUIREMENTS

DEFINITION & MAPPING FORM
Wadgessen – Change the Global receipient “IRC-Notifications” to

Local
For the Author: NO sections in this document must be deleted unless otherwise explicitly stated in this
template. If not applicable then write N/A. You may add new sections if needed.
NO documents must be inserted into this document – use the References section and
give links. Do not delete this red text when you use this template !!
Document Name BR030_iRec- Termination Alert to Applicant

Owner Enterprise Architect (EA)
Approved by
Approved Date
Author SA - Maks Reghunathan
See version history in SharePoint
Last Updated Do not delete: Template version used : Doc.
Version: 1.0
<System name - release level - functional
Document Ref.
area - functional level>
Page 1 of 15
BR.030 Business Requirements Mapping form - Change the Global receipient “IRC-Notifications” to Local
Document Control
Document Review & Inspection
Document version control: SharePoint is used for this.
Review- and Inspection records for this solution document:
DD-MMM-YYYY R=Review Initials of Number of Decision*

& version I=Inspection reviewers/ comments/
(Inspections & Reviews only)
BC=Buddy inspectors input
check
Decision*: Approved / Conditionally approved provided that required input is updated/ Rejected (re-inspection needed)
Status: Draft, Proposal, Approved.
Related documents
Note! If this document co-relates to other documents then mention them here including
the approved version number and correct link to the SharePoint location.
E.g. a Technical Design document (MD.070) corresponds to a specific version of a

Functional Design document (MD.050). A Requirements Specification (e.g. BR030)
corresponds to specific versions of a Feature from the Feature List and one or more
MD050s. Etc.
If Helios Documentation Center (HDC) is used as storage the unique document ID shall
be indicated.
Document Name Version SharePoint path or Unique Doc. ID from

HDC’s Unique Doc.ID list (see Ref. 2)
Page 2 of 15 Doc. Version: 0.1

Contents
Document Control.......................................................................................................2
Document Review & Inspection............................................................................2
Feature list...................................................................................................................5
Requirements Essay.....................................................................................................6
Background...........................................................................................................6
Detailed requirement statements:........................................................................6
Current versus Proposed (optional).............................................................................7

Business Practices.................................................................................................7
Business Policies....................................................................................................7
Business Procedures.............................................................................................7
Business Requirements Mapping Solution (Std. Systems)...........................................8

Solution Summary.................................................................................................8
Solution Detail.......................................................................................................8
Solution Components (Std. Systems)....................................................................9
Error Handling...........................................................................................................11
Other non-functional requirements (optional)..........................................................12
Implementation Notes for this Deliverable...............................................................13
Open Issues.........................................................................................................13
Closed Issues.......................................................................................................13
References..........................................................................................................13
Glossary.....................................................................................................................14

Introduction
This document is used to describe and define the business requirement(s) for a business
process and mapping it to an overall solution using business language.
The BR.030 is the document containing the extraction and formulation of detailed
business requirements (formulated as features), and translation of those into a solution
overview.
The purpose of the BR.030 is to document the solution overview that meets business
requirements into a form, where functional design can start.
For any requirements delivered as part of the Helios solution, all requirements must refer
to a Feature in the Helios Feature List (see Ref. 2).
As a rule of thumb: One Feature à One BR030.

Feature list
Feature Description
Unique Feature ID
& version* For Helios: Copy from Helios Feature List.
Feature Title & Link
(For Helios: Use the Helios
Feature List(*Ref 2) ID on (For Helios: Use the Helios Feature
SharePoint) List)
For non- Helios a User Story might be
used (format: As a [role] I need to
[action] in order to fulfil [goal])
Change the Global receipient IRC- Irecruitment Alerts are marked to

408
Notifications to Local mailing group IRC-Notification which
should be changed to Local mailing
group specific to Wadgassen
Table 1
Note! If Feature Title and Description differ from the same stated in the Helios Feature List, then
HFL takes precedence at any time.
*) Note! Version number of each feature is available in the HDC Feature list. Version number is
important to document in this BR030 in order to know exactly how the feature was described in
HDC at the time the BR030 was approved. The feature may be updated without *this* document
also being updated which results in inconsistency.

Requirements Essay
Background
The Current Solution provides Irec (Recruitment Related) Alerts sending the notifications to
a global group called “Notification IRC” group . Business needs to send all these notifications to local “Site
specific” Group of recipients. As these notification are local and may not be relevant to Global Group.
Detailed requirement statements:
Unique Classification Business

Requirement
Description (business objective) Value
[ID] (Must-Have/Should-
Testable, unambiguous
(mandatory) Have/Could Have/Won’t
Have) 1(low)-100 (high)
408 Background: -
The Recruitment Solution provides various

notifications . Many (four) of these notifications are Must-Have 100
sent to a common recipient “Global group” which
results in local notification sent to global recipients
across sites.
Requirement:
Irecruitment Notification should be sent to Local

recipients specific to Wadgassen
Table 2. The unique requirement IDs will as a rule of thumb be unique within this BR030 only

Current versus Proposed (optional)

Current
The Curernt Recruitment Alerts Sends Notification to IRC-Notifiation mail group that is global mail
group.
Proposed
Create local mailing groups and send mail to site specific groups, so that the information is not sent
across the sites.Create separate mail box for each site and dynamically select mail to site specific mail
box.
Business Practices
Business Policies
Business Procedures

Business Requirements Mapping Solution (Std. Systems)

Map here high-level future business process models to the standard Applications/Systems. Future
business processes are modelled in detail.
A gap analysis between the future process vision and the Application functionality is performed and gap
resolution options are identified.
Solution Summary
Solution Detail
For each Requirement and sub-requirement(s) describe an overall solution in a non-technical language
that the user can easily understand.
Req. Solution (testable)

ID
408 Irecruitment Alerts are marked to mailing group IRC-Notification which should be changed to Local
mailing group specific to Wadgassen. This maling group shall be generated dynamically based on
the site and the solution will be global across all the sites. The details of the design will be
described in MD050 document.
Alerts to be modified:
1.FLS Inform Manager of Vacancy Posting
2.FLS Applicant Offer
3.FLS Reconsidered Applications
4.FLS Withdraw Application Status
Application Enhancement:

Change the “To” value from global to local recipients.
Solution Components (Std. Systems)
Follow these guidelines in using the sections:
1) Workaround: NA
2) Application Enhancement: NA
3) Re-engineering Opportunity:
4) Solution/Design Document Reference: NA
Workaround
NA
Application Enhancement
NA
Reengineering Opportunity
The Dynamic list of the recipient can be changed at any point of time as business demands.
Solution/Design Document Reference

NA
Mechanism
NA
Interfaces
NA
Solution Technique
NA

Error Handling

Other non-functional requirements (optional)

Describe here at overall level requirements that are not functional. For example:
requirements to performance, security, etc.

Implementation Notes for this Deliverable
Open Issues
ID Issue Criticality* Resolution (suggested) Responsibility Target Date Impact Date

(critical, Major,
Minor)
*) Criticality is explained in the Show Room’s wiki. Click here.
Closed Issues
Note! When an Issue is closed the Resolution *must* be filled in
ID Issue Resolution (actually approved) Responsibility Target Date Impact Date
References
Reference and Title Link and/or description of the referenced

documentation
Ref. 1: Documentation This document must follow the rules stated in this
Management Policy policy for Global IT. Click here to open.
Ref. 2: Helios Feature List The official Helios Feature List is maintained by the
Enterprise Architecture Office and can be found here.

Glossary
Term Description
BRS (Business Business Requirement Scenario.

Requirement A formal statement of the detailed business requirements for a business
Scenario) process, the source of these requirements, how these requirements will be
satisfied (either by the application, manual process steps, workarounds or
other application solutions), and what prototyping steps must be taken to
prove the designs.
Source: Oracle’s AIM Method Handbook.
Business Requirement A formal statement that describes application features necessary to

support a business process step.
Business Requirement An activity that describes the business requirements for a business process
in business language, optionally compares the current solution for a
Mapping
business requirement to a proposed solution and specifies details for the
type and nature of the solution in a descriptive format.
The deliverable can also be used as a record of key decisions, or as a

placeholder in anticipation of additional detailed design documentation.
Business Process The complete response that a business makes to an event.
A business process entails the execution of a sequence of one or more

process steps. It has a clearly defined deliverable or outcome. A Business
Process is defined by the business event that triggers the process, the
inputs and outputs, all the operational steps required to produce the
output, the sequential relationship between the process steps, the business
decisions that are part of the event response, and the flow of material
and/or information between process steps.
HDC Helios Documentation Center. Also a repository for non-Helios projects’

solution documentation.

HFL Helios Feature List. See also Ref. 2
Information Model A model of the information needed to support a business or other activity.
Requirements are typically defined as lists of detailed items as well as

summarized data from business transactions, such as orders and
purchases, and master records, such as customers and vendors. How
frequently this information must be made available is also part of the
requirement.
Information requirements (the what and when) are turned into functional
specifications (the how) of an information system by systems analysts
(generically speaking).
The information is defined as a collection of data elements that are

obtained by running query and report programs against a particular
database or group of databases. The data and information that is stored in
the databases in the first place is also derived from the information
requirements.
Mapping A technique for establishing application fit to business requirements,

identifying gaps and proposing initial solutions. Also a technique to define
the relationship between objects.
MoSCoW List Must have, Should have, Could have, Won’t have — a way of
classifying requirements or facilities for inclusion in an information system.
(classification of
requirements)
This mechanism is often used in timeboxed development where the scope

may need to be redefined according to the rate of progress.
The Must have is vital and hence must be developed or included.
The Should have is important, but not vital
The Could have is nice to have, but not really important
The Won’t have is not developed or included
Inspired by: Oracle’s AIM Method Handbook.
Requirement Definition 1 (non-Oracle applications):

A requirement is a need that a particular design, product or

process must be able to perform. A statement that identifies a
See also User Story necessary attribute, capability, characteristic, or quality of a System for it
to have value and utility to a customer, organisation, internal user, or
other stakeholder. Source: Wikipedia, the free encyclopedia.
Note! A requirement is not only a functional requirement. Other examples

of requirements are performance requirements, usability requirements,
etc.
Definition 2 (Oracle application):
A requirement is a specific, detailed business need which is to be

compared with application functionality to determine if the need can be
met with the standard Oracle software. Source: Oracle’s AIM Method
Handbook.
Requirements A formal statement of detailed business requirements for a process, the

source of the requirements, how these requirements will be satisfied
Scenario
(either the application, manual procedure, workarounds, or other
application solutions) and what prototyping steps must be taken to prove
the design.
User Story A light weight and lean alternative to describing more detailed
requirements.
See also Requirement Format: As a [role] I want to be able to [action] in order to [goal]
Example:
As an Oracle Administrator I must be able to create new Oracle users in

order for them to update their OTL time sheets.

BR030 - Change The Global Receipient IRC-Notifications To Local

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BR030 - Change The Global Receipient IRC-Notifications To Local

Hochgeladen von

Copyright:

Verfügbare Formate

BR.

030 Business Requirements Definition & Mapping form

BR.030 BUSINESS REQUIREMENTS

Wadgessen – Change the Global receipient “IRC-Notifications” to

Document Name BR030_iRec- Termination Alert to Applicant

Document Review & Inspection

Document version control: SharePoint is used for this.

Review- and Inspection records for this solution document:

DD-MMM-YYYY R=Review Initials of Number of Decision*

E.g. a Technical Design document (MD.070) corresponds to a specific version of a

Document Name Version SharePoint path or Unique Doc. ID from

Page 2 of 15 Doc. Version: 0.1

Detailed requirement statements:........................................................................6

Current versus Proposed (optional).............................................................................7

Business Requirements Mapping Solution (Std. Systems)...........................................8

Solution Components (Std. Systems)....................................................................9

Page 3 of 15 Doc. Version: 0.1

As a rule of thumb: One Feature à One BR030.

Page 4 of 15 Doc. Version: 0.1

Change the Global receipient IRC- Irecruitment Alerts are marked to

Page 5 of 15 Doc. Version: 0.1

Detailed requirement statements:

Unique Classification Business

The Recruitment Solution provides various

Irecruitment Notification should be sent to Local

Page 6 of 15 Doc. Version: 0.1

Current versus Proposed (optional)

Page 7 of 15 Doc. Version: 0.1

Business Requirements Mapping Solution (Std. Systems)

Req. Solution (testable)

1.FLS Inform Manager of Vacancy Posting

2.FLS Applicant Offer

3.FLS Reconsidered Applications

4.FLS Withdraw Application Status

Page 8 of 15 Doc. Version: 0.1

Change the “To” value from global to local recipients.

Solution Components (Std. Systems)

Follow these guidelines in using the sections:

4) Solution/Design Document Reference: NA

Solution/Design Document Reference

Page 9 of 15 Doc. Version: 0.1

Page 10 of 15 Doc. Version: 0.1

Other non-functional requirements (optional)

Page 11 of 15 Doc. Version: 0.1

Implementation Notes for this Deliverable

ID Issue Criticality* Resolution (suggested) Responsibility Target Date Impact Date

*) Criticality is explained in the Show Room’s wiki. Click here.

Note! When an Issue is closed the Resolution *must* be filled in

ID Issue Resolution (actually approved) Responsibility Target Date Impact Date

Reference and Title Link and/or description of the referenced

Page 12 of 15 Doc. Version: 0.1

BRS (Business Business Requirement Scenario.

Source: Oracle’s AIM Method Handbook.

Business Requirement A formal statement that describes application features necessary to

Source: Oracle’s AIM Method Handbook.

The deliverable can also be used as a record of key decisions, or as a

Source: Oracle’s AIM Method Handbook.

Business Process The complete response that a business makes to an event.

A business process entails the execution of a sequence of one or more

Source: Oracle’s AIM Method Handbook.

HDC Helios Documentation Center. Also a repository for non-Helios projects’

Page 13 of 15 Doc. Version: 0.1

Note! When an Issue is closed the Resolution must be filled in