Scribd
Upload
964 views5 pages

Template RICEF.

This document provides specifications for a new software project. It includes sections for document control, requirements, functional specifications, program details, data processing rules, expected outputs, and estimates. The document specifies the development type, status, priority, and assigned resources. It describes the business purpose and process, functional needs, assumptions, dependencies, and impacts on other systems. Program details like type, inputs, mappings, calculations, outputs, and error handling are also specified. Estimates for consultant and ABAP time are provided.

Uploaded by

Eduardo Alonso Martinez Medina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
964 views5 pages

Template RICEF.

This document provides specifications for a new software project. It includes sections for document control, requirements, functional specifications, program details, data processing rules, expected outputs, and estimates. The document specifies the development type, status, priority, and assigned resources. It describes the business purpose and process, functional needs, assumptions, dependencies, and impacts on other systems. Program details like type, inputs, mappings, calculations, outputs, and error handling are also specified. Estimates for consultant and ABAP time are provided.

Uploaded by

Eduardo Alonso Martinez Medina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

Software Specification

1. Document Control Section

Initial Document Set-up


Development Type: Forms / Reports / Interface / Enhancement / Workflow /Conversion
Document ID:
Short Description:
Functional Area:

Overall Document Status:


Development Reference:
Raised By:
User Responsible:
Assigned To Consultant:
Priority: 1- High / 2- Medium / 3 Low
Status: D Draft; F Final; R Removed (Obsoleted)

Approvals
This document requires the following sign-offs.

Name Title Date Signature

Change History
Version Revision Date Description & Reason for Change Author

Client Confidential Page 1 of 5 5-Sep-2017


Software Specification <Title>
Software Specification

REQUIREMENTS

2. Business Purpose & Process

Business Justification:
Process:

3. Functional Requirements

Description:
Frequency of Use: Ad hoc / Hourly / Daily / Weekly / Bi-weekly / Monthly
Expected Data Volume: N/A

3.1 Forms / Reports / Interface File Layout(s)


N/A

4. Assumptions/Prerequisites/Dependencies/Impacts to other Areas

4.1 Assumptions

4.2 Prerequisites

4.3 Dependencies

4.4 Impacts to other Areas

FUNCTIONAL SPECIFICATIONS

Client Confidential Page 2 of 5 5-Sep-2017


Software Specification <Title>
Software Specification

5. Program Type

Execution Type: Batch / Online / Background / User-Exit / Dynamic-Event


Navigational Criteria /
Required Execution Steps
(if applicable):
Transaction Code:
SAP Programs:

5.1 Interface Details (if applicable)

Type of Interface:
Category:
Frequency of Run:
External System Name:
File Name:
File Type:

6. Program Inputs

6.1 Mapping information


Layout Field SAP Field Name Length Field Description Retrieval or Update Rules/
Name Comments
<Short description. Reference to
section 7, step x for details>

6.2 Screen Layout(s)

6.3 User-exit Criteria (if applicable):

Client Confidential Page 3 of 5 5-Sep-2017


Software Specification <Title>
Software Specification

7. Data Processing Rules, Formulas and/or Calculations


<Include diagram if it provides better clarity>

8. Expected Output

8.1 Output Report and/or Screen layout(s)

8.2 High Level Unit Testing Plan or Criteria:

8.3 Error Handling Requirements (if applicable)

Error/warning/info messages at various processing stages:

Error Handling Processing options:


All or nothing if there is an error, roll back any processed data and stop processing
Only good data if there is an error, skip the erroneous record and continue processing
Stop processing run until there is an error, then stop, but dont roll anything back.
Other:

Error Processing:
Specify what action to take upon encountering each kind of error print a report, save records to a file,
recovery requirements, send an email as notification, etc.

Possible error Processing / Recovery requirements


1.
2.
3.
4.

Client Confidential Page 4 of 5 5-Sep-2017


Software Specification <Title>
Software Specification

8.4 If no output is expected, enter description of successful completion of


program:

9. Authorization Requirements

10. Estimates

Consultant man-days :

ABAP man-days :

Client Confidential Page 5 of 5 5-Sep-2017


Software Specification <Title>

You might also like