Requirements-sigataf_requisitos.htm

Requirements

Functional Requirements

•	Being able to import data from the legacy ERP in TXT format;

•	Supplying a pre-validation of the layout structure upon importing;

•	Being able to generate output for verification in the TXT, XML, XLS, PDF formats and so on;

•	Validating data integrity upon importing;

•	Being able to trace important data, such as date, time, user and file;

•	Allowing maintenance of the data imported from the ERP, (Complements, Attachments, etc.);

•	The product must be responsible for the management of fiscal data;

•	Control of changes by LOGs;

•	Having tools for checking the data imported from the ERP, for more safety to the user;

•	Allowing the maintenance of ICMS/ICMS-ST Calculation;

•	Allowing the maintenance of IPI Calculation;

•	Allowing the maintenance of PIS/COFINS Calculation;

•	Making simple arithmetic calculations available in the direct maintenance of data in TAF. Example. Base X Rate = Tax Value;

•	Displaying warnings about the consequences of manually adjusting the data in TAF, showing the impact for manual intervention in other fronts;

•	Issuing Forms for paying the taxes, as determined by law (Agreement 06/99);

•	Allowing in-house installation;

•	Having a safety control per user, company, and establishment to determine and limit read, save and maintenance access to the data;

•	Allowing commercialization and release of accessory obligations individually;

•	Allowing the control of commercialization licenses;

•	Meeting Federal, State and City laws;

•	Complying to specific legislation of the various industries (e.g.: food, fuel, etc);

•	Complying to legislation of the entire TOTVS product portfolio (ERP, RH, Agribusiness, Health care, etc);

•	Complying to international market legislation.

Non-Functional Requirements

•	Data importing from the legacy ERP in TXT format must use the MILE component being developed by the Framework team;

•	The MILE component used for importing the pre-formatted file must provide a pre-validation of the layout structure at the moment of importing;

•	Using ByYou technology, ADVPL language;

•	Using a single relational database independent from the ERP;

•	Presenting its own interface;

•	Every product must be developed using MCV (Model, View and Controller) component;

•	Maintenance auditing is to be carried out by the AUDIT-TRAIL component, feature being developed by the Framework team;

•	TAF development is to be centralized in the CDSP;

•	The project must be detailed and well documented so that the teams of different development centers can provide maintenance and implementation of new legislation in the TAF;

•	During specifications, there must be review/alignment meetings so as to guarantee the scope originally agreed upon;

•	Any change in the scope originally agreed upon must be aligned with the development centers. Scope changes are to be controlled;

•	At the end of the project the training is to be planned for the teams from the various development centers so that they can act on the product;

•	Design evaluation, adherence and legal interpretation (CDSP, CDJOI, CDBH);

•	Consulting of TAF legislation is to be done by CDJOI.