Amadis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 56 Next »

To start, here is a definition of a framework:

“In general, a framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful. In computer systems, a framework is often a layered structure indicating what kind of programs can or should be built and how they would interrelate. Some computer system frameworks also include actual programs, specify programming interfaces, or offer programming tools for using the frameworks. A framework may be for a set of functions within a system and how they interrelate; the layers of an operating system; the layers of an application subsystem; how communication should be standardized at some level of a network; and so forth. A framework is generally more comprehensive than a protocol and more prescriptive than a structure”

Agnos is a software framework that can be reused to build any acceptance system. It requires good software skills, basic EMV/payment expertises, and a good knowledge of the API to start (reading documentation is not enough. We recommend to follow a course). In average, between 8 and 12 weeks are required to port the system onto a new platform to be ready to start a qualification

The advantages of using that framework are:

  • The system has already been certified in the past on different platforms

  • The system is already deployed on the field in major markets

  • The system is versatile and may be adapted to any Level3 contexts

  • The system’s version that is purchased is maintained against the very last specs and frequent test plans

However, note that:

  • The system is complex and usually requires a 3-day training session

  • The system needs to be qualified before being submitted to a TA

  • The system doesn’t implement any specific processor/acquirer security scheme (out of L2 scope)

This section provides a high level description of the framework:

Integration Environment

According to the license agreement, a corresponding set of artifacts is delivered. Software components have been prepared to fit to your platform and operating system:

  • Use binary components for your deployment model implementation

  • Use binary and development components for your implementation

The most popular platforms and operating systems of the industry are supported by Agnos (WinCE/Windows/Linux/Android/FreeRTOS), and proprietary environments have already been targeted.

Note that all the components referred above can be packaged to support your development (Eclipse IDE along with Eclipse projects) on flexible platforms like PC (Windows). Thanks to the level of abstraction that Agnos provides, it is recommended to develop on such platforms to accelerate development and test phases: Agnos Virtual Terminal is a reference implementation available on Windows that can be used along with a specific Agnos integration project targeting an embedded platform. Also, systematic use of the GPI abstraction layer is a must to achieve high level of portability.

Note: AVT on Linux is also available. Contact us for details.

Integration Steps

Here are the major steps to cross in order to port the framework in preparation to qualification tests.

Step 1: Train

The Wiki is the main source of information. There are few others documents available related to training modules (Training Modules).

In order to improve our documentations and our support, please use Wiki as references to send us requests. To help us, send questions by Jira and include some of the following artifacts (depending on the context):

  • Object (mandatory): [Company name][Project name][Software component] Topic

  • Reference of the unclear / incomplete section of a document

  • Software components versions (mandatory)

  • Test Case (or Card) reference

  • EMV Logs, Configuration files, Transaction Related Data, …

Use our portal to contact us ofr any questions: Customer Support Portal

Step 2: Play with the AVT

The AVT is used as a reference terminal to validate the behaviors of a system under test and Amadis implementation on a PC-based system. It may also be used for training purpose.

See Agnos Virtual Terminal page.

Step 3: Study the Logical Model

Step 4: Study the Physical Model

Step 5: Start Porting

See Agnos Framework Porting and/or Agnos Kernel CL Porting pages.

  • No labels