Our Strengths - Case Studies
Service offerings: |
|
| Case reference: | The challenge was to build a very large scale e-mail engine that can scale up to millions of users with an average mailbox cost of less than 1USD per year. One of the quality attributes of the system was the average cost of the mailbox. Therefore, the design and architecture had to transform this into a set of architectural attributes and establish at the design stage itself that the design will meet the specified criteria. |
| Case reference: |
The challenge was to build a large scale data aggregation platform that consolidated real estate listings from across the United States. The system had to handle more than 2 million listings on a daily basis. |
| Case reference: |
The banking platform was primarily aimed to be configured by different banks, integrate with any existing applications and systems, and was designed to be highly flexible. The business processes and workflows were designed to be configured without any programming work. The entire platform was designed using a set of design frameworks - business and domain frameworks, technology platform frameworks and aspects for NFRs. We used six-sigma related 'experiments' for each major design component to establish the design constraints well before the implementation. When the platform was released to the end customers, all they needed to test for is the integration with their systems, which was accomplished within a few weeks. |
Service offerings: |
|
| Case reference: | We designed a solution for application systems management that significantly reduced the complexity of the domain and is usable independent of specific application environments. The solution provided the "how-to" information required to manage application systems to a team whose skillsets were primarily from the infrastructure management space and who had little application knowledge. |
| Case reference: | By reducing the complexity from having to model each type of object in an enterprise separately to instead modeling a handful of semantic types and semantic relationships that could then be combined to model any enterprise - the development effort required was dramatically reduced. From a developer's perspective, the modeling approach largely moved the problem from a code problem to a data problem thereby simplifying the development. |
| Case reference: |
The platform was designed as a set of small design frameworks - each framework addressing one core design requirement - like configurability, workflow process modeling, communication between components, logging, schedulers, fault-tolerance, revenue management, customer management and so on. All components would integrate with these frameworks, the entire design philosophy was reduced to a set of small computing problems. The architecture was communicated using a product roadmapping methodology - which uses inputs from various stakeholders, brings all of that together to create long term roadmap. The architecture and Design used the same problem solving techniques and methods. This approach enabled us to evolve a common set of terms of reference for all stake holders. |
Service offerings: |
|
| Case reference: |
Each area had further dimensions for instance we had the dimensions of user applications, middleware applications, databases and back-end applications as areas within the applications section of core technology. Each area had a progression path over the series of releases as well as interdependencies with other areas. Related areas of development were picked and formed into a series of platform and product releases. The roadmap was developed with a 3 to 5 year outlook. |
Service offerings: |
|
| Case reference: | |
Service offerings: |
|
| Case reference: |
In both cases, the structuring of the project, the order in which components were designed and built, the test planning and quality processes were driven from an architecture perspective. Both solutions were modeled and built using a distributed workflow system that we designed. In addition to developing the design, building the data and object models, the interfaces and APIs, we also introduced several quality engineering techniques into the development of these projects. For instance, we had well defined performance and scalability models for the system, we designed APIs to enable automated testing and designed tools to aid in the generation of large quantities of test data. We used iterative development in the creation of certain aspects of the system such as the XML processing engine where we needed to improve the performance of the existing .Net APIs by ten fold. Once the core components were in place, we used a more traditional waterfall model in the configuration of these components for the needs of the customer. |
ReLATED INFO

Our Services

Our Expertise

Consulting Services

Consulting Products

Workshops & Training
Client Case Studies
What our Clients Say..
"Your efforts during your consulting engagement with us at Veloz over 2004-2005 have led to the creation of a potentially powerful platform and technology and most importantly intellectual property of great value." "As an organization, we greatly benefited from Mr. Pappu’s problem-solving capabilities, as well as his deep understanding and experience of computing science, programming and object technologies." "…certainly the work delivered was a masterpiece.." "We look forward to your continuing association with us, your mentoring and guidance as we continue our journey over the next few years towards building the Veloz Enterprise Performance Mgt. product line." |
