| |
Application Development Projects |
I-Series Password Change Project |
Within many options in the product, a password is required for both authorization and auditing purposes. When a user enters the password, that password is used to identify the user and then authorize the user for the action he is taking. To accomplish the task of identifying and authorizing, the password was stored in clear text in a database table when the product was originally designed.
Recently, to enhance the security, it was decided not to store passwords in text format. Instead, the encrypted I-Series password would be used to authenticate the user. The following major changes were required to implement this feature:
1) .Add a username field to every screen that currently requires a password.
2) The username field is defaulted with the last user who successfully authenticated.
The changes affected three classifications of programs:
1) Secured Screens
2) Secured Menu Options
3) Override Windows
The second phase of this project involved expansion of password field to 30 characters.We found out the display files and programs, which used password field and changed them to accommodate new 30 character long password. |
|
Currency Conversion Project
|
This project deals with the accuracy in ordering outside of base currency. Base currency is the currency used in all menus in the system. E.g. USD. When currency of vendor/item is not at base, the cost of the item relating to purchasing changes as the currency exchange rate changes.As the item is actually based on the alternate currency, this creates an inaccurate cost in Purchasing, as it is based on the last cost of the item, and is converted.
The scope of the project is to store the last cost of an item in the currency of the item, as opposed to base currency.
We analyzed the requirement and found out the physical files and programs which required changes. We changed all programs to calculate the last cost in its currency. The QA team tested all item entry, purchasing, and accounts payable menu options to confirm that the last cost is getting stored in item currency and it is actually considering the exchange rate in all calculations. |
|
EU- Notilus Interface (TE) |
The goal of this project was to give the customers the ability to continue to process travel and other expenses made into expense management tool via a feed to their existing software (RENTALMAN).
One of the customer’s processes travel and other sales related expenses through an expense management tool called Notilus. Currently, the information is auto-fed into Mistral for reimbursement. The customer wanted to continue using a similar process with RENTALMAN. This project involved creating a weekly feed from Notilus to RENTALMAN to enable payment checks to be printed and paid.
We analyzed the existing accounts payable program which writes invoices and based on the same technique we wrote a new program which accepts an excel and enters invoices in batch.
|
|
XRT Interface Project |
France is currently using EFT payments for AP invoices within the Mistral Equipment Rental system. One of the customers wanted to develop an interface format so that payments of AP invoices can continue through XRT. The current EFT was replaced with XRT process.
In this project, we created a feed to XRT for A/P payments. We produced a remittance advice document that can be emailed, faxed, or printed. A unique batch number was assigned for each file transfer which could be used for retrieval.
|
|
Quality Assurance Projects |
Version 11 Regression Testing and fix |
Keeping in mind the business in Europe, the company decided to add features required by European customers. These features involved major changes in the Accounts Payable and General Ledger modules as per the European accounting system. These were more of functional changes than technical. Majority of the development work was done by the onshore team. Once the development was done, an online training of this functionality was given to both Development and QA teams.
We did the regression testing for this version and resolved any issues we came across.
In the second phase we did the regression testing of the application on one of the customer’s machine.
|
|
Testing Printer Files |
The company provides its product as a service also. Initially, there was a single set of objects used by all the customers. Now to accommodate customer specific changes, company decided to make separate libraries for all of them. As a part of this, all the major invoices were also moved to individual libraries. We (off-shore) were supposed to test these changes. Our job was to execute the major transactions and test whether the invoices were getting printed properly and appropriate objects were being used. As a part of our test, we compared the spooled outputs for any differences.
|
|
AS/400 Support Projects |
At present, we are fixing the issues reported by the company’s in-house QA team as well as by its customers. This involves reproduction of the issue, identifying the cause, coding a solution, and then testing the fix in appropriate environments. Once the fixes are tested, they are moved to the production environment by the onshore team.
We are successfully fixing priority 2 and priority 3 issues by maintaining the SLA of the customers.
|
| |
