Configuration Management (Ali Mollabagher.Com)

Islamic Azad University
Science & Research Campus

IT Management
Structured System Analysis & Design Method

Configuration Management

Instructor
Dr.Motadel

Presented by:
Hamed Godazgar
Ali Mollabagher
Eshrat Shafaat
nd
2 Semester of 2008-2009 1

In God We Trust

Copyright © 2008-2009 Ali-
2
Mollabagher.com | All rights reserved

3

Content

• Why Configuration Management ?
• What Is Configuration Management ?
• History
• Configuration Items
• Planning
• Configuration Management Control
• Benefits
• Costs & Risks
• Conclusion
• References
4

Why Presenting Configuration Management ?

The Information Technology Infrastructure Library (ITIL) is a set of
concepts and policies for managing information technology (IT)
infrastructure, development and operations & Configuration Management
is one of these standards.

5

Why we use Configuration Management ?

It is used to track the system after change as it require, change
occur due to following reasons.

To make system cross-platform

Accommodating new functionality

Tailored for particular user requirements

6

What Is Configuration Management ?

Define Manage Control Audit

Changes made to the original system

Establish system Maintain system
integrity integrity

7

History

1960s 1970s 1990s

Started

The American Government - Military Standards

Emerging many other standards and publications

8

Configuration Items

Program code
Standards, and procedures
listings
Maintenance
requests Testing, operatio
n, and execution
Design plans
specifications
Manuals
(user, operation, command, and system)

System
specifications Problem and error reports

Set of resources to support configuration management
an aggregation of hardware, software, or documentation which is designed for
configuration control
9

Planning

1.Establish a configuration management plan

2.Responsible developers and maintainers must be
identified

Planning
3.Budget must be defined

4.Must be ensure that the appropriate tools and
documentation are available.

5.Configuration items are collected.

10

Configuration Control

1.Establishing a baseline

2.Version control
Configuration
control
3.Freezing the system

4.Benchmarks

5. Regression testing

6.Establishing a new baseline
11

Initial line as a reference point for all other measurements.

outcome or milestone of system development

The version of the system on which the final system test is performed might
serve as the initial baseline.

12

13

In subsequent releases,

 the major number is increased when there are significant jumps in

functionality,

 the minor number is incremented when only minor features or significant

fixes have been added, and

 the revision number is incremented when minor bugs are fixed.

14

15

Designating development stage

0 For alpha status
1 For beta status
2 For release candidate
3 For public release

1.2.0.1 Instead of 1.2-a
1.2.1.2 Instead of 1.2-b2 (beta with some bug fixes)
1.2.2.3 Instead of 1.2-rc
1.2.3.0 Instead of 1.2-r (commercial distribution)
1.2.3.5 Instead of 1.2-r5 (commercial distribution with many bug fixes)
16

Windows 95 4.0
Windows 98 4.10
Windows Me 4.90
Windows 2000 NT 5.0
Windows XP NT 5.1
Windows 2003 NT 5.2
Windows Vista NT 6.0
Windows 7 NT 6.1

17

18

Involves archiving the entire system, including :

The executable programs
Data files
Source code,
Related documentation.

The archive can be used to reestablish the pre-change version.

19

At the time the system is frozen,
benchmark measurements
(execution time, response time, and the like)
should be taken for the system.

20

To measure how the change affected response time and
other standard performance metrics.

Benchmark measurements taken on the baseline is the key
to regression testing.

21

After approval is granted, the production system is frozen, the
new version of the test system becomes the production
system, and a new baseline is established.

22

Configuration auditing and reporting

 The purpose of configuration auditing is to ensure that the approved
changes have been implemented.

The purpose of configuration reporting is to ensure that the changes
are broadcast

23

Benefits of Configuration Management

Improves Decreases

Product protection Rework

Product visibility Confusion

Product control Project Risk

Team
communication

Customer
Confidence 24

Costs of Configuration Management

Costs are outweighed by benefits, because Configuration Management allows handling of a
large volume of changes, thus keeping quality. Configuration Management control reduces
risks of viruses, wrong software, fraud, theft, and so on.

Staff costs for developing and running procedures

Hardware and software configuration identification

Hardware and software for the CMDB & DSL

Customization of Configuration Management tool

Integration with other Service Management tools

Training and education
25

Risks of Configuration Management

CIs with too much or too little detail

Interfaces to other systems in which CI information is stored

Keep the information in the CMDB accurate

Roles and responsibilities

Lack of configuration control

Overambitious schedules and unrealistic expectations

No commitment from management
26

27

Conclusion

• Configuration Management is a component of ITIL Standard
for implementing IT in enterprises

• Changes are inevitable in the system so keeping track of
changes is an essential task .

• The duty of configuration management is to define, manage
changes by planning and controlling them from analyzing to
the end of system existence.

28

References
1.The information system consultant’s handbook : system Analysis and Design
/ chapter 80/configuration management

1.http://www.atlasfarhang.com/History.aspx

2.IBM.Press.Implementing.ITIL.Configuration.Management

3.^ APMG (2008). quot;ITIL® Service Management Practices: V3 Qualifications Schemequot;

(HTML). http://www.itil-officialsite.com/nmsruntime/saveasdialog.asp?lID=572&sID=86

. Retrieved on 2009-02-24.
1.^ Office of Government Commerce (2006). “
Best Practice portfolio: new contracts awarded for publishing and accreditation servicesquot;

(HTML). http://www.ogc.gov.uk/About_OGC_news_4906.asp

1.^ Office of Government Commerce (2008). quot;Best Management Practice: ITIL® V3 and ISO/IEC 20000quot;

(HTML). http://www.best-management-practice.com/gempdf/ITIL_and_ISO_20000_March08.pdf

29

References
1.^ The IT Skeptic (2008). quot;Three reasons why ISO20000 certification is not ITIL V3 certificationquot;

(HTML). http://www.itskeptic.org/node/581

Retrieved on 2009-02-24.
1.^ IBM Global Services (2004). quot;IBM and the IT Infrastructure Libraryquot;

(PDF). http://www.ibm.com/services/us/igs/pdf/wp-g510-3008-03f-supports-provides-itil-
capabilities-solutions.pdf

1.^ IBM Global Services (2003). quot;IBM's commitment to ITIL (archived)quot;
(HTML). http://web.archive.org/web/20070304184624/http://www-
935.ibm.com/services/us/index.wss/detail/its/a1000593?cntxt=a1000429

Retrieved on 2007-03-04.
1.^ Van Schaik, E. A. (1985). A Management System for the Information Business. Englewood
Cliffs, NJ, Prentice-Hall, Inc. ISBN 0-13-549965-8
2.^ Van Schaik, E. A. (2006 2nd Ed.). A Management system for the Information Business. Red
Swan Publishing. ISBN 1933703032
3.^ Nolan, Richard, 1974, 1982. Managing the Data Resource Function. St. Paul, Minnesota, West
Publishing. ISBN 0829900039 (1982 ed.) Copyright © 2008-2009 Ali-
30
4.^ Office of Government Commerce. ITIL Refresh | All rights reserved
Mollabagher.com Statement

References
. Retrieved February 13, 2006.
1.^ Office of Government Commerce (UK)CCTA and OGC

. Retrieved May 5, 2005.
1.^ Office of Government Commerce (2000). Service Support. The Stationery Office. ISBN 0-11-
330015-8.
2.^ Office of Government Commerce (2001). Service Delivery. IT Infrastructure Library. The
Stationery Office. ISBN 0-11-330017-4.
3.^ Office of Government Commerce (2002). Planning To Implement Service Management. The
Stationery Office. ISBN 0-11-330877-9.
4.^ Cazemier, Jacques A.; Overbeek, Paul L.; Peters, Louk M. (2000). Security Management. The
Stationery Office. ISBN 0-11-330014-X.
5.^ Office of Government Commerce (2002). ICT Infrastructure Management. The Stationery
Office. ISBN 0-11-330865-5.
6.^ Office of Government Commerce (2005). The Business Perspective. The Stationery Office.
ISBN 0-11-330894-9.
7.^ Office of Government Commerce (2002). Application Management. The Stationery Office.
ISBN 0-11-330866-3.
8.^ Office of Government Commerce (2005). ITIL Small Scale Implementation. The Stationery
Office. ISBN 0-11-330980-5.
9.^ van Bon, J.(Editor) (2002). The guide to IT service management. Addison Wesley. ISBN 0-201-
73792-2.
10.^ Meyer, Dean, 2005. quot;Beneath theCopyright © 2008-2009 Ali-
Buzz: ITILquot;
31

References

CIO Magazine, March 31, 2005
1.^ van Herwaarden, H. and F. Grift (2002). quot;IPW(tm) and the IPW Stadia Model(tm) (IPWSM)quot;.
The guide to IT service management. J. Van Bon. London, Addison-Wesley: 97-115.

• http://techrepublic.com.com/2001-6240-0.html

32

Configuration Management (Ali Mollabagher.Com)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Configuration Management (Ali Mollabagher.Com)

Ähnlich wie Configuration Management (Ali Mollabagher.Com) (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Configuration Management (Ali Mollabagher.Com)

Hinweis der Redaktion