Projects:MatchStatement Unmatch Multiple Records/FunctionalSpecs

Contents 1 Unmatch Transaction Engine Refactor - Functional Specifications 1.1 Overview 1.1.1 Purpose 1.1.2 Scope 1.2 Design Considerations 1.2.1 Assumptions 1.2.2 Constraints 1.3 Functional Requirements 1.3.1 Business process definition 1.3.2 Functional requirements descriptions 1.4 Technical Requirements 1.5 Non-Functional Requirements 1.6 Discussion Items

Unmatch Transaction Engine Refactor - Functional Specifications

Overview

This project intends to deliver a new and extensible unmatch engine for core's Openbravo ERP.

Purpose

Current unmatch engine only covers the single transaction unmatch method. This project will deliver a new unmatch engine that will facilitate to unmatch different transaction in the same time.

Scope

This project will deliver a new API to manage unmatch multiple transactions. All core functionality based on old unmatch will be updated to support the new one.

Design Considerations

Assumptions

• It must be possible to develop new unmatch algorithms using modules.

Constraints

• Instances currently using unmatch must be properly updated to the new engine.

Functional Requirements

Business process definition

1. Match Statement screen.
   1. Unmatch Multiple Records in the same time.
   2. Unmatch Multiple Records does not change previous unmatch single record.

Functional requirements descriptions

In this section are described all the functional requirements to fulfill this development.

The aim of the new engine is to unmatch Multiple Records. Each record will have its Imported Bank Statement without any match.

Technical Requirements

• All code shall be written as java classes using DAL.

Non-Functional Requirements

Discussion Items

Open and comment discussion items on project's Open discussion forum