|
|
Brochures
Automated Subpoena Processing Brochure
Case Studies
Pharmaceutical companies need to define, document and publish a business process for the reporting and tracking of side-effects that might occur due to the drug usage. These side-effects referred to as Adverse Events must be recorded and categorized. Once categorized, these events need to be reported back to the FDA and other regulatory agencies like the EMEA and local country agencies. These regulatory agencies define the timeframe (based on the severity of the report) in which the events need to be reported to them (from the time of diagnosis to the filing with the agency). Delays in reporting these adverse events can lead to the company being fined heavily or even having to pull the drug from the market. Learn more about our Adverse Event Reporting solution.
In the recent past FICC used to process all input data twice a day by running the match process of all the data files received from its customers (e.g. Fannie Mae, etc.). This process had high latency between data submission and receiving trade confirmations, which exposed the end users to operational risk. To reduce the risk exposure to its customers and in an effort to provide quicker trade confirmation FICC implemented RTTM (Real-Time Trade Matching). Learn more about our RTTM solution.
SOA Implementation for Discount Brokerage
A major discount brokerage engaged Ishi consultants to design an integration infrastructure to support an enterprise process within extremely tight time constraints. The business requirements were to implement modifications to the brokerage account opening process. All account opening processes had to conform to the stipulations of the USA PATRIOT Act by the federally mandated deadline. Learn more about our SOA implementation.
Whitepapers
The purpose of this whitepaper is to provide a brief introduction to SOA and why organizations need to think about implementing SOA based solutions. It then discusses how SOA can help solve some of the key integration challenges that most companies face. This paper is meant for organizations that are facing application integration challenges and have a need to share business logic and reuse existing applications, and for technical readers who want to provide SOA based solutions to organizations that have such a need.
Unified Authentication & Validation
Unified Authentication (UA) can protect Internet users from identity theft better than with a scheme that uses regular username and password. A strong authentication mechanism such as UA involves something that the legitimate user already has; this is also called two-factor authentication, the user is required to have confidential information as well as in possession of a physical token. However, how can one prove having such an object on the Internet? Since only information can be transmitted on the Internet, the object can vouch for itself by transmitting information only it possesses. However if the transmitted information is the same each time then it is no better than a regular password. A scheme must be created in which the information transmitted must be different each time; however the authenticator must recognize legitimate transmitted data from illegitimate one.
The primary deliverable of any software application is the code. This code wires all the application logic that, as we all know has to deliver to an extent that it can be considered reliable enough to automate a business process. The reliability of any system primarily depends on its ability to perform in all possible conditions that the system is designed to work. It is this idea that encourages makers or builders of the system to test it in all possible conditions so as to ensure no or less surprises for the system to handle. This whitepaper highlights the importance of ‘testing the tests’ and profiles some of the Code Coverage products available today.
A Source Code Management (SCM) repository is perhaps one of the most important data stores a software development organization maintains. One would expect that since developers work with source code every single day, they would understand source control and related concepts extremely well. Our experience, surprisingly, is that developers struggle with source control. This article attempts to explain the basics of SCM and also takes a trip to the console to demonstrate practical usage of two common source code management tools — Rational Clearcase and CVS.
Struts 1.1 vs. 1.2 - Comparison
There have been a considerable amount changes in the Struts framework between versions 1.1 and 1.2 which are significant.
This whitepaper discusses the following:
- Point out the most significant changes between the two versions
- Look at changes involved in migrating applications from Struts 1.1 to 1.2
In case you’re unfamiliar with what an annotation is, examining Javadoc is a good place to begin. As most Java developers are aware, Javadoc provides a framework to generate documentation for code by tagging sections of code with certain predefined tags. Each tag is preceded by an @ symbol. This article traces the history of annotations and provides an insight into upcoming implementations of annotations.