| No. | Item | Definition |
|---|---|---|
| 1. | alignment | shared understanding and direction |
| 2. | analysis | careful examination of details |
| 3. | API | software interface for programs |
| 4. | application | software for a specific task |
| 5. | architecture | overall system design structure |
| 6. | assessment | evaluation of current state |
| 7. | audit | formal review of records |
| 8. | automation | use of machines or scripts |
| 9. | availability | readiness for use |
| 10. | backup | copy kept for recovery |
| 11. | bandwidth | data transfer capacity |
| 12. | breach | security failure exposing data |
| 13. | budget | planned amount of money |
| 14. | business continuity | keeping operations running |
| 15. | capacity | maximum amount supported |
| 16. | client | person or company receiving services |
| 17. | cloud | internet-based computing resources |
| 18. | collaboration | working together effectively |
| 19. | communication | sharing information clearly |
| 20. | compliance | meeting rules and standards |
| 21. | configuration | system settings arrangement |
| 22. | contract | formal legal agreement |
| 23. | database | organized collection of data |
| 24. | debugging | finding and fixing errors |
| 25. | deliverable | work product to be provided |
| 26. | deployment | releasing software into use |
| 27. | design | planning form and function |
| 28. | disaster recovery | restoring after major disruption |
| 29. | discovery | finding needs and facts |
| 30. | documentation | written information and instructions |
| 31. | encryption | coding data for protection |
| 32. | escalation | raising an issue higher |
| 33. | estimate | approximate cost or time |
| 34. | firewall | network traffic filtering barrier |
| 35. | framework | structured set of tools |
| 36. | governance | oversight and decision framework |
| 37. | handover | transfer of responsibility |
| 38. | hardware | physical computer equipment |
| 39. | identity | who a user is |
| 40. | implementation | putting a plan into use |
| 41. | infrastructure | basic underlying technology framework |
| 42. | integration | combining systems to work together |
| 43. | interface | point where systems connect |
| 44. | issue | current problem needing attention |
| 45. | KPI | key performance indicator |
| 46. | latency | delay before data transfer |
| 47. | licensing | legal permission to use |
| 48. | logging | recording system events |
| 49. | maintenance | ongoing care and fixes |
| 50. | metric | measured value |
| 51. | migration | moving systems or data |
| 52. | milestone | significant project checkpoint |
| 53. | monitoring | watching system behavior continuously |
| 54. | network | connected computers and devices |
| 55. | operations | day-to-day running activities |
| 56. | optimization | making something work better |
| 57. | ownership | responsibility for something |
| 58. | patch | small software fix |
| 59. | performance | how well something operates |
| 60. | platform | base environment for software |
| 61. | policy | official rule or guideline |
| 62. | process | series of actions |
| 63. | project | planned piece of work |
| 64. | proposal | formal suggested plan |
| 65. | protocol | rules for communication |
| 66. | recommendation | suggested course of action |
| 67. | recovery | restoring after failure or loss |
| 68. | redundancy | extra components for backup |
| 69. | release | version made available |
| 70. | reliability | consistency of correct operation |
| 71. | requirement | needed feature or condition |
| 72. | resilience | ability to recover quickly |
| 73. | risk | possible problem or loss |
| 74. | roadmap | planned sequence of milestones |
| 75. | ROI | return on investment |
| 76. | scalability | ability to handle growth |
| 77. | scope | defined boundaries of work |
| 78. | security | protection against threats or access |
| 79. | server | computer providing services to others |
| 80. | service | function provided to users |
| 81. | software | programs used by a computer |
| 82. | stakeholder | person affected by the project |
| 83. | standard | agreed level or rule |
| 84. | strategy | long-term plan of action |
| 85. | system | connected set of components |
| 86. | team | group working together |
| 87. | testing | checking for correct behavior |
| 88. | threat | possible source of harm |
| 89. | throughput | amount processed in time |
| 90. | timeline | schedule of key dates |
| 91. | training | teaching users or staff |
| 92. | troubleshooting | diagnosing and solving problems |
| 93. | update | newer version or change |
| 94. | upgrade | move to a better version |
| 95. | value | worth or usefulness |
| 96. | vendor | company selling products or services |
| 97. | version | particular software release |
| 98. | virtualization | creating virtual computing resources |
| 99. | vulnerability | weakness that can be exploited |
| 100. | workflow | sequence of work steps |