Spelling suggestions: "subject:"IT frameworks"" "subject:"IT gframeworks""
1 |
Best practices for implementing multiple concurrent IT frameworks (CMMI, ITIL, Six-Sigma, CobiT and PMBOK)Harryparshad, Nirvasha 20 August 2012 (has links)
This research report aims to provide an insight into the implementation of multiple concurrent IT frameworks, and how to best implement each of the chosen frameworks resulting in a hybrid of best practices for implementing multiple concurrent IT frameworks
|
2 |
Best practices for implementing multiple concurrent IT frameworks (CMMI, ITIL, Six-Sigma, CobiT and PMBOK)Harryparshad, Nirvasha 20 August 2012 (has links)
This research report aims to provide an insight into the implementation of multiple concurrent IT frameworks, and how to best implement each of the chosen frameworks resulting in a hybrid of best practices for implementing multiple concurrent IT frameworks
|
3 |
Unification Of It Process Models Into A Simple Framework Supplemented By Turkish Web Based ApplicationAygun, Betul 01 September 2010 (has links) (PDF)
Information technology usage has become compulsory for all organizations whether government or private organizations to achieve visibility, compete rivals and execute their missions better. To get desired result from usage of information technology, IT of organization has to be managed well. Up till now, various frameworks are developed to manage it well. Best examples for this kind of frameworks are COBIT and ITIL, containing all processes which can be handled in IT management and becoming widespread through the world. COBIT and ITIL are complementary frameworks rather
than competitors. Due to this reason, organizations must implement both of them instead of choosing one of them. In addition to these, ISO/IEC 27001:2005 which focuses on information security management process is a quite famous IT standard in terms of security.
This thesis provides organizations to meet requirements of these frameworks/standards which are process based frameworks and standards complementary to each other, with a unique implementation by taking unification of processes in a more simple and understandable way. Consequently, it provides reduction in the duplicate work and prevents inconsistencies that may occur. In addition, including CMMI level two requirements motivate the organization to implement higher maturity level of CMMI. Moreover, this study provides organizations to implement ISO 27001 management structure which establish a foundation for extension to technical structure of it. Besides these, this study provides an alignment of frameworks model and COBIT and ITIL which helps organization to trace ITIL and COBIT simultaneously. Lastly by providing a web based application, there exists foundation for knowledge bank of IT processes in Turkish and profile pages for each organization to manage, trace and reach their own IT processes in a digital environment.
|
4 |
Kravställning på Incidenthanteringssystem / Requirements definition for an Incident Management SystemAhlqvist, Petter, Vagiström, Johan January 2015 (has links)
Användandet av IT relaterade tjänster har ökat kraftigt de senaste åren och visar inga tecken på att avstanna. Men i takt med att användningen ökar så ökar även riskerna, för vad händer egentligen när de IT-tjänster som så många företag och privatpersoner förlitar sig på plötsligt fallerar eller på annat sätt blir oåtkomliga? För att skydda sig mot sådana scenarier så blir det allt vanligare bland företag som driver IT-tjänster att använda sig incidenthantering, vars syfte är att genom fördefinierade processer återställa IT-tjänster till fungerande läge när en incident väl inträffar. För att implementera en incidenthanteringsprocess är det vanligt att verksamheter använder någon form av ramverk eller metod för att underlätta och effektivisera arbetet, i skrivande stund heter de mest använda ramverken ITIL och COBIT. Det är mycket vanligt att en incidenthanteringsprocess i en verksamhet bygger på någon form av system eller applikation vars syfte är att underlätta och effektivisera hanteringen av incidenter, ett sådant system benämns ofta som incidenthanteringssystemet. Trots att ramverk som ITIL och COBIT är använda i stor utsträckning världen över så uppstår det ett problem i att de båda saknar fokus på incidenthanteringssystemet och vad ett sådant system skall klara av. För när ramverken inte tar upp en sådan central del av incidenthanteringsprocessen så innebär det att den implementerande verksamheten själva måste lägga tid och resurser på att reda ut hur ett sådant system skall fungera. Denna studie adresserar problemet med att de vanligast använda ramverken för incidenthantering inte behandlar det, för processen, så centrala incidenthanteringssystemet genom att undersöka och besvara följande forskningsfrågor. Vilka implicita och explicita krav bör ett incidenthanteringssystem uppfylla? Vilka krav på incidenthanteringssystemet går att utläsa från de mest använda ramverken för incidenthantering? Hur matchar de framtagna kraven de krav som ställts av en verksamhet ur näringslivet? Denna studie riktar sig framförallt till de verksamheter eller individer som anser sig ha nytta av en sammanställning av de krav som ett incidenthanteringssystem bör uppfylla och kan fungera som ett stöd vid implementering eller inköp av ett nytt incidenthanteringssystem. Genom att identifiera kraven som ställs på ett incidenthanteringssystem utifrån de mest använda ramverken för incidenthantering så bidrar studien med resurser för implementationen av nämnt system drastiskt minskar. Samt genom att presentera ett konkret exempel, fallstudien, och jämföra det med kraven från ramverken bidrar studien med en referenspunkt för verksamheter att utgå ifrån när de implementerar eller köper ett nytt incidenthanteringssystem. / The use of IT-related services has increased massively over the past years and it shows no signs to stop. But alongside the usage increasing the risks also increases, because what will happen when the IT-services that so many rely upon suddenly cease to function, or in other ways become inaccessible? To protect against such scenarios it is increasingly more common for IT-service businesses to use incident management, whose purpose is to recover IT-services to their functional state, using predefined processes, should an event occur. It is common for IT-service businesses when implementing an incident management process to use some kind of framework or method to facilitate and streamline its work process, and as of writing this paper, the most used frameworks are ITIL and COBIT. It is very common for an IT-service business that in the incident management process develop a system or application whose purpose is to facilitate and streamline the incident management, and these are commonly referred to as Incident Management Systems. Even though ITIL and COBIT being widely used worldwide, there are some weaknesses in them, regarding Incident Management Systems, since both of the frameworks lack focus and depth of what an Incident Management System should manage. Such lack of focus and depth of a vital and central part of the Incident Management process, may prove expensive to IT-service businesses since the business needs to investigate what the system needs to manage, and how to manage it. This paper address the problem with ITIL and COBIT lack of focus and depth regarding the central part of the incident management process, the Incident Management System by investigating and reciprocate the following questions. Which implied and explicit requirements should an Incident Management System meet? Which Incident Management System requirements can be found from the most used frameworks regarding Incident Management? How well does the identified requirements match those requirements made by a real world company? The target audience for this paper is mainly IT-service business or individuals that considers themselves in need of a compilation of requirements that an Incident Management System should meet and can be used as a supporting tool when implementing or purchasing a new Incident Management System. By identifying requirements that an Incident Management Systems should meet from the most used framework regarding Incident Management, this paper will contribute with means for the implementation of the Incident Management System, reducing the costs for the investigation of demands of such a system. It will also present interested parties with a concrete example, the single case study, to compare with the requirements from the frameworks, contributing with a benchmark for IT-service business to start from when implementing or purchasing an Incident Management System.
|
Page generated in 0.0432 seconds