Clients using KD products: Banks Telecommunication operators Internet Intermediaries Manufacturing Retail

Steps in implementation of IS 1. 2. 3. 4. 5. 6. Request for proposal Detailed documentation of the functional requirements of the customers. Design of the system at the architectural, database, and business logic levels. Detailing of development timeline and resource requirements. Actual development. System Integration

Implementation issues:

People: People are the most important element in most computer-based information systems. They make the difference between success and failure for an organisation. Information systems personnel include all the people who manage, run, program and maintain the system including the CIO, who manages the IS department. Users are the people who work with information systems to get results. Users include financial executives, marketing representatives, manufacturing operators and many others.

The existing employees in the organisation would be needed to be trained for the development purposes. KDs competencies and corporate culture would need to accommodate a good numbers of talented software engineers from the Top Engineering institutions whose primary function would be product development. Language and cultural barriers can get in the way of effective communication and create complications in the workplace. Attitudinal barriers, biases and stereotyping by co-workers, supervisors and managers can hinder the ability of a business to prosper. Requirement specification is one of the most critical issues in designing an IS. Most of the issues in people are due to poor requirement understanding.

The issue in requirement specification could be due to various factors: The client (end user) may not be clear with his needs. The requirement specification conveyed by client could be misinterpreted and misunderstood by the engineer (interpreter). The engineer (interpreter) could in-turn convey a wrong specification to the development team leading to a development of the application which does not meet the client requirement.

The prototype developed and approved by the client may not be addressing all the requirements of the clients (end user).

A change in the requirement specification document by the client during the development process is a crucial issue affecting the overall implementation.

Now when the product/application has been developed by the developers we require the testers who will be involved in verifying if we have built the right product. Finally, during the user Acceptance testing the User/Client might ask for some changes which could leads to the same process again.