Product Engineering Services

» New Product Development

OIS's new product development service covers the entire spectrum of activities involved in taking a product from vision to ship - from defining the product vision to releasing a finished product and every step in between. We get deeply involved from the start by understanding our client's business, their target customers, their competitors, and other business drivers and constraints. We use this understanding to design and build a product that can exceed their market and user expectations. We understand that new products and new businesses go through a lot of flux in the initial stages. We have evolved processes and built a mindset in the company that is capable of handling such uncertainty. Our goal is to achieve predictable quality and ship on a predictable date. We provide complete transparency over the development process through regular updates, rigorous tracking, frequent binary drops, and a strong feedback process. We have strict Intellectual Property Protection Rights (IPPR) policies that provide controls at all levels - contractual, policy, and cultural.

» Product Modernization

OIS helps companies modernize their products in ways that harness new technologies, enhance functionality, improve user experience, and increase user benefits.

User environments have changed: This has resulted in new user demands. As an example, users now expect their software - from email, to line of business applications - to follow them on their mobile devices. New business processes: Enterprises in many industries, have adopted new business processes to comply with new regulations. While software companies that serve them have been incorporating changes into existing products, such changes have tended to be unwieldy workarounds, leaving users less than happy. Better Usability Better usability drives better adoption, whether the software is on the Web or on the desktop. If you can imagine a better user experience for your customers, chances are you can create it using technologies that exist today. Many of today's software applications have dated architectures - while they strive to keep up with user needs, their existing architectures are unable to support radical functionality.

» Maintenance & Support

software maintenance is the modification of a software product after delivery to correct faults, to improve performance or other attributes, or to adapt the product to a modified environment.”(ISO/IEC 14764). This international standard describes the 6 software maintenance processes as:

1. The implementation process contains software preparation and transition activities, such as the conception and creation of the maintenance plan, the preparation for handling problems identified during development, and the follow-up on product configuration management.

2. The problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group. The maintenance programmer must analyze each request, confirm it (by reproducing the situation) and check its validity, investigate it and propose a solution, document the request and the solution proposal, and, finally, obtain all the required authorizations to apply the modifications.

3. The process considering the implementation of the modification itself.

4. The process acceptance of the modification, by checking it with the individual who submitted the request in order to make sure the solution provided a solution.

5. The migration process (platform migration, for example) is exceptional, and is not part of daily maintenance tasks. If the software must be ported to another platform without any change in functionality, this process will be used and a maintenance project team is likely to be assigned to this task.

6. Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software.

There are a number of processes, activities and practices that are unique to maintainers, for example:

• Transition: a controlled and coordinated sequence of activities during which a system is transferred progressively from the developer to the maintainer;

• Service Level Agreements (SLAs) and specialized (domain-specific) maintenance contracts negotiated by maintainers;

• Modification Request and Problem Report Help Desk: a problem-handling process used by maintainers to prioritize, documents and route the requests they receive;

• Modification Request acceptance/rejection: modification request work over a certain size/effort/complexity may be rejected by maintainers and rerouted to a developer.