1. Implementation of information system

2. Implementation in system’s lifecycle It can be done after the system is designed, It is one of the most difficult stages, The system changes its owner, The mistakes are revealed..

3. Difficulties in implementation.. Depend on: If the system is implemented in new organization or existing before? It is easier to implement the system in a new organization. Is the system customized or unique? It is easier to implement the typical (customized) system.

4. Implementation procedure Total implementation Pilot implementation Trial implementation Concurrent implementation

5. Total implementation New system (resignation of an old system), The easiest and the cheapest, Dangerous because: there is no way back (if the system is not tested)

6. Partial implementation Less risk, More expensive (comparing to total implementiation), Should be structuralised (regions and/or functions), Pilot implentation is difficult when subsystems cannot be distincted.

7. Concurrent implementation An old system is being used when the new is being implemented, Generates conflicts, Expensive.

8. Implementation process Preparation Testing exploitation

9. Preparation sOrganization: Risk definition, assessment and minimization, Users training, Databases building, Documentation changing, Structure changing

10. Preparation System: System instalation, Appointing supervising team (copyrights), Users training

11. Users manual Introduction System description (parametres), Databases description, Algorithms description, Rules description, Exploitation characteristics

12. Preparation Infrastructure (hardware): Hardware instalation, Computer nets instalation.

13. Testing Testing, checking, examining the system

14. Implementation Preliminary exploitation (trials), Problems elimination

15. Exploitation System exploitation

16. Implementation management Managers are responsible for : Resources allocation, Methods, processes, procedures definition, Tasks sequencing and scheduling, Jobs assignement, Assessment methods definition

17. Users participation Supervisers (least active), Conceptualizer, Member of implementation team (most active),

18. Conflicts Limited resources sharing, Different aims and tasks, Job sequencing, Different approach to work quality, Different approach to management, Differences concerning age, education, background, Problems with work organization.m

19. Implementation efficiency Defrosting Changes implementation, Frosting..

20. Defrosting Need for changes, Potential problems..

21. Changes implementation Switching the systems, New system instalation

22. Frosting New balance should be found

23. Risk in implementation Problems with users, Problems with implementation.

24. Risk analysis Discordances in implementation, Corrective action planning, Solutions finding.

25. Information in IT systems

26. Databases Models bases Procedures bases Knowledge bases

27. Databases A group of sets used in customers service process, A database system is to developed to gather, store, process and visualize information, A database system users include final users, coders, deesigners, systems analytics, databases administrators, data administrators

28. Users reuirements Fast work, Possibilities of development and reorganization, Accesibility, Efficiency, Safety, Data consistency and independency, Accuracy.

29. Models Simple data, Complex data, Records, Sets.

30. Models General models, Logical models, Physical models.

31. General models Holistic approach to data, Requirements data should meet, Stable, Important for users..

32. Logical models Hierarchical (traditional), Net (traditional), Relative, Object.

33. Data warehouse Subject oriented, Integrated, With data which arenot changed, With data from a long time period, Providing information, and not operation, Analytical, supporting decision-makers.