GROUP 2

CMMI
ISO
UMI
 CAPABILITY
MATURITY MODEL
INTEGRATION
(CMMI)
 CMMI

The Capability Maturity Model Integration (CMMI) is a model that helps

organizations to:
Effectuate process improvement
Develop behaviors that decrease risks in service, product, and software
development

The model enables organizations to measure, build, and improve

capabilities—to improve overall performance.
 CMMI GOALS
To improve software-development
processes
To evaluate capability of a
software

CMMI helps "integrate traditionally

separate organizational functions, set
process improvement goals and
priorities, provide guidance for quality
processes, and provide a point of
reference for appraising current
processes." - Software Engineering
Institute (SEI, 2008)
 BACKGROUND AND
HISTORY OF CMMI
In early 1960's, many companies saw a potential in
software development and started developing
software without any proper techniques or standards
This resulted in "Software Crisis" - US military had
several software projects extended or canceled in
1980's
CMMI was developed by Carnegie Mellon University
CMMI TIMELINE
The CMMI was developed from 1987 until
1997.

In 2002, version 1.1 was released

Version 1.2 followed in August 2006

Version 1.3 in November 2010

V1.3 was replaced by V2.0 in March 2018

 CMMI
EVALUATION
Appraisals
 APPRAISALS

Organizations that want to better understand how their practices compare

to CMMI best practices and want to implement CMMI practices often start
with an appraisal.

The appraisal report is a document, which among other things, lists the
strengths and weaknesses of the organization which wants to reach a
desired process capability level or a maturity level. It is a guideline to plan
improvement efforts, and a document to track the developments and
achievements.
 APPRAISALS
The official appraisal method used by the CMMI Institute is known as the Standard
CMMI Appraisal Method for Process Improvement (SCAMPI). There are three
classes of appraisal methods:
SCAMPI Class A is the most formal and rigorous type of appraisal.
Organizations that conduct this type of appraisal usually have already
implemented a number of changes and need to benchmark their progress
formally.
SCAMPI Class B appraisals are primarily used by organizations that have
implemented some changes and want to gauge their progress towards
targeted CMMI levels.
SCAMPI Class C appraisals are less expensive, quicker, and more flexible than
either Class A or Class B appraisals.
CMMI STRUCTURE
Maturity Levels
Capability Levels
 22
Process Areas
 MATURITY LEVELS
(STAGED REPRESENTATION)

The CMMI model breaks down

organizational maturity into five levels. For
businesses that embrace CMMI, the goal
is to raise the organization up to Level 5.
Maturity Level 1 – Initial
Maturity Level 2 – Managed
Maturity Level 3 – Defined
Maturity Level 4 – Quantitatively
Managed
Maturity Level 5 – Optimizing
 CAPABILITY LEVELS
(CONTINUOUS REPRESENTATION)

The continuous representation of a CMMI model

consists of the same process areas as the staged
representation. However, no process area is assigned
to a particular maturity level.

Capability Level 0 – Incomplete

Capability Level 1 – Performed
Capability Level 2 – Managed
Capability Level 3 – Defined
 ISO
(INTERNATIONAL
ORGANIZATION FOR
STANDARDIZATION)
 WHAT IS ISO?

ISO (INTERNATIONAL ORGANIZATION FOR STANDARDIZATION) IS A

WORLDWIDE FEDERATION OF NATIONAL STANDARDS BODIES.

ISO IS A NON-GOVERNMENTAL ORGANIZATION THAT COMPRISES

STANDARDS BODIES FROM MORE THAN 160 COUNTRIES, WITH ONE
STANDARDS BODY REPRESENTING EACH MEMBER COUNTRY. FOR
EXAMPLE, THE AMERICAN NATIONAL STANDARDS INSTITUTE
REPRESENTS THE UNITED STATES.
 HOW ARE ISO STANDARDS DEVELOPED?

The International Organization for Standardization has a six-stage process for

developing standards.

Proposal stage. The first step in developing a new standard starts when industry
associations or consumer groups make a request. The relevant ISO committee
determines whether a new standard is indeed required.

Preparatory stage. A working group is set up to prepare a working draft of the new
standard. The working group is composed of subject matter experts and industry
stakeholders; when the draft is deemed satisfactory, the working group's parent
committee decides which stage occurs next.
Committee stage. This is an optional stage during which members of the parent committee review
and comment on the draft standard. When the committee reaches consensus on the technical
content of the draft, it can move to the next stage.

Enquiry stage. The draft standard at this stage is called a Draft International Standard (DIS). It is
distributed to ISO members for comments and, ultimately, a vote. If the DIS is approved at this
stage without any technical changes, ISO publishes it as a standard. If not, it moves to the
approval stage.

Approval stage. The draft standard is submitted as a Final Draft International Standard (FDIS) to
ISO members. They vote to approve the new standard.

Publication stage. If ISO members approve the new standard, the FDIS is published as an official
international standard.
WHAT IS ISO CERTIFICATION?
According to the ISO, the phrase "ISO certification"
should never be used to indicate that a product or
system has been certified by a certification body as
conforming to an ISO standard. Instead, ISO suggests
referring to certified products or systems using the
full identification of the ISO standard.
WHAT ARE POPULAR ISO STANDARDS?

ISO/IEC 27000. These security standards define a six-step

process for developing and implementing information
security policies and processes.
ISO/IEC 12207. This ISO standard creates a consistent
lifecycle management process for all software.
ISO 9000. This family of standards defines how organizations
can establish and maintain effective quality assurance
systems for manufacturing and service industries.
BUSINESS UNIFIED
MODELING
LANGUAGE (UML)
 WHAT IS UML?
THE UNIFIED MODELING LANGUAGE (UML)
WAS CREATED TO FORGE A COMMON,
SEMANTICALLY AND SYNTACTICALLY
RICH VISUAL MODELING LANGUAGE FOR
THE ARCHITECTURE, DESIGN, AND
IMPLEMENTATION OF COMPLEX
SOFTWARE SYSTEMS BOTH
STRUCTURALLY AND BEHAVIORALLY. UML
HAS APPLICATIONS BEYOND SOFTWARE
DEVELOPMENT, SUCH AS PROCESS FLOW
IN MANUFACTURING.
 THE ORIGIN OF UML

The Three Amigos’ of software engineering as they were known, had evolved other
methodologies. They teamed up to provide clarity for programmers by creating new
standards. The collaboration between Rumbaugh, Booch and Jacobson made all three
methods stronger and improved the final product.

The efforts of these thinkers resulted in the release of the UML 0.9 and 0.91 documents in
1996. It soon became clear that several organizations, including Microsoft, Oracle, and IBM
saw UML as critical to their own business development. They, along with many other
individuals and companies, established resources that could develop a full-fledged
modeling language. The Three Amigos published The Unified Modeling Language User Guide
in 1999, and an update which includes information about UML 2.0 in the 2005 Second
Edition.
THE ORIGIN OF UML

 THE PURPOSE OF UML ACCORDING TO OMG

THE OMG DEFINES THE PURPOSE OF THE UML:

Providing system architects, software engineers, and software developers

with tools for analysis, design, and implementation of software-based
systems as well as for modeling business and similar processes.

Advancing the state of the industry by enabling object visual modeling

tool interoperability. However, to enable meaningful exchange of model
information between tools, agreement on semantics and notation is
required.

 UML AND DATA MODELING

THE UML IS POPULAR AMONG PROGRAMMERS, BUT

ISN’T GENERALLY USED BY DATABASE DEVELOPERS.
ONE REASON IS SIMPLY THAT THE UML CREATORS DID
NOT FOCUS ON DATABASES. DESPITE THIS, THE UML IS
EFFECTIVE FOR HIGH-LEVEL CONCEPTUAL DATA
MODELING, AND IT CAN BE USED IN DIFFERENT TYPES
OF UML DIAGRAMS.
 MODELING CONCEPTS SPECIFIED BY UML

SYS T EM DEV E L OPME N T FO CUS ES O N THREE O VER AL L D I FFER EN T SYSTEM

MODELS:

F UNCTI ONAL

OBJ ECT

DYNAMI C
 OBJECT-ORIENTED CONCEPTS IN UML

THE OBJECTS IN UML ARE REAL WORLD ENTITIES THAT

EXIST AROUND US. IN SOFTWARE DEVELOPMENT, OBJECTS
CAN BE USED TO DESCRIBE, OR MODEL, THE SYSTEM
BEING CREATED IN TERMS THAT ARE RELEVANT TO THE
DOMAIN. OBJECTS ALSO ALLOW THE DECOMPOSITION OF
COMPLEX SYSTEMS INTO UNDERSTANDABLE COMPONENTS
THAT ALLOW ONE PIECE TO BE BUILT AT A TIME.
 OBJECT-ORIENTED CONCEPTS IN UML

HERE ARE SOME FUNDAMENTAL CONCEPTS OF AN OBJECT-ORIENTED

WORLD:
OBJECTS REPRESENT AN ENTITY AND THE BASIC BUILDING BLOCK.
CLASS BLUE PRINT OF AN OBJECT.
ABSTRACTION BEHAVIOR OF A REAL WORLD ENTITY.
ENCAPSULATION MECHANISM OF BINDING THE DATA TOGETHER AND
HIDING THEM FROM OUTSIDE WORLD.
INHERITANCE MECHANISM OF MAKING NEW CLASSES FROM EXISTING
ONE.
POLYMORPHISM IT DEFINES THE MECHANISM TO EXISTS IN DIFFERENT
FORMS.
 UML TERMS GLOSSARY

ABS TRACT S Y N T AX CO MP L IA N CE
COMMON WAR EH O U S E ME TA MO D E L ( CWM)
CONCRETE S Y N T AX CO MP L IA N CE
COR E
LEVEL 0 ( L0)
META OBJE CT F ACI L I T Y ( MO F )
METAMODEL
METAMODEL CO N S T R UCTS ( L M)
 UML TERMS GLOSSARY

MODEL DRIVEN ARCHITECTURE (MDA)

OBJECT CONSTRAINT LANGUAGE (OCL)
OBJECT MANAGEMENT GROUP (OMG)N
UML 1
UNIFIED MODELING LANGUAGE (UML)
XMI
NOTATION FOR LINK
 TYPES OF UML DIAGRAMS
STRUCTURAL UML DIAGRAMS

CLASS DIAGRAM THE MOST COMMONLY USED UML DIAGRAM, AND THE PRINCIPAL FOUNDATION OF ANY OBJECT-ORIENTED
SOLUTION. CLASSES WITHIN A SYSTEM, ATTRIBUTES AND OPERATIONS AND THE RELATIONSHIP BETWEEN EACH CLASS. CLASSES
ARE GROUPED TOGETHER TO CREATE CLASS DIAGRAMS WHEN DIAGRAMMING LARGE SYSTEMS.
 TYPES OF UML DIAGRAMS

STRUCTURAL UML DIAGRAMS

COMPONENT DIAGRAM DISPLAYS THE STRUCTURAL RELATIONSHIP OF SOFTWARE SYSTEM ELEMENTS,
MOST OFTEN EMPLOYED WHEN WORKING WITH COMPLEX SYSTEMS WITH MULTIPLE COMPONENTS.
COMPONENTS COMMUNICATE USING INTERFACES.
 TYPES OF UML DIAGRAMS

STRUCTURAL UML DIAGRAMS

COMPOSITE STRUCTURE DIAGRAM COMPOSITE STRUCTURE DIAGRAMS ARE USED TO SHOW
THE INTERNAL STRUCTURE OF A CLASS.
 STRUCTURAL UML DIAGRAMS

DEPLOYMENT DIAGRAM ILLUSTRATES

SYSTEM HARDWARE AND ITS SOFTWARE.
USEFUL WHEN A SOFTWARE SOLUTION IS
DEPLOYED ACROSS MULTIPLE MACHINES
WITH UNIQUE CONFIGURATIONS.
 STRUCTURAL UML DIAGRAMS

OBJECT DIAGRAM SHOWS THE RELATIONSHIP BETWEEN OBJECTS USING REAL WORLD
EXAMPLES AND ILLUSTRATES HOW A SYSTEM WILL LOOK AT ANY GIVEN TIME. BECAUSE DATA
IS AVAILABLE WITHIN OBJECTS, THEY CAN BE USED TO CLARIFY RELATIONSHIPS BETWEEN
OBJECTS.
 STRUCTURAL UML DIAGRAMS

PACKAGE DI AGRAM THERE ARE TWO SPE CI AL TYPE S OF DEP ENDENCI ES DEFI NED BET WEEN P AC KAG ES:
PACKAGE I MPORT AND PACKAGE MERGE. P ACKAGES CAN REP RESENT THE DI F F ER ENT LEVELS OF A SYSTEM TO
REVEAL THE ARCHI TE CTURE . PACKAGE DEP ENDENCI ES CAN BE MAR KED TO SHOW THE C OMMUNI C ATI ON
MECHANI SM BETWE E N L E VE L S.
 BEHAVIORAL UML DIAGRAMS
ACTIVITY DIAGRAMS GRAPHICALLY REPRESENTED BUSINESS OR OPERATIONAL WORKFLOWS TO
SHOW THE ACTIVITY OF ANY PART OR COMPONENT IN THE SYSTEM. ACTIVITY DIAGRAMS ARE
USED AS AN ALTERNATIVE TO STATE MACHINE DIAGRAMS.
 BEHAVIORAL UML DIAGRAMS
COMMUNI CATI ON DI AGRAM SI MI LAR TO SEQUE NCE DI AGRAMS, BUT THE FOCUS I S ON MESSAG ES P ASSED
BETWEEN OBJ ECTS. THE SAME I NFORMATI ON CAN BE REP RESENTED USI NG A SEQUENC E DI AG R AM AND
DI FFERENT OBJ E CTS.
 BEHAVIORAL UML DIAGRAMS
INTERACTION OVERVIEW DIAGRAM THERE ARE SEVEN TYPES OF INTERACTION DIAGRAMS,
AND THIS DIAGRAM SHOWS THE SEQUENCE IN WHICH THEY ACT.
 BEHAVIORAL UML DIAGRAMS
SEQUENCE DIAGRAM SHOWS HOW OBJECTS INTERACT WITH EACH OTHER AND THE ORDER OF
OCCURRENCE. THEY REPRESENT INTERACTIONS FOR A PARTICULAR SCENARIO.
 BEHAVIORAL UML DIAGRAMS
STATE DIAGRAM SIMILAR TO ACTIVITY DIAGRAMS, THEY DESCRIBE THE BEHAVIOR OF
OBJECTS THAT BEHAVE IN VARYING WAYS IN THEIR CURRENT STATE.
 BEHAVIORAL UML DIAGRAMS
TIMING DIAGRAM LIKE SEQUENCE DIAGRAMS, THE BEHAVIOR OF OBJECTS IN A GIVEN TIME
FRAME ARE REPRESENTED. IF THERE IS A SINGLE OBJECT, THE DIAGRAM IS SIMPLE. WITH MORE
THAN ONE OBJECT, INTERACTIONS OF OBJECTS ARE SHOWN DURING THAT PARTICULAR TIME
FRAME.
 BEHAVIORAL UML DIAGRAMS
USE CASE DI AGRAM REPRESENTS A PARTI CUL AR F UNCTI ONALI TY OF A SYSTEM, CREATED TO I LLUSTR ATE HOW
FUNCTI ONALI TI ES RE L ATE AND T HEI R I NTERNAL/EXTERNAL CONT R OLLER S ( AC TOR S) .
 GROUP 2

KEVI N RYAN S . B AN D O J O

ALF RED ALVAR EZ

THANK YOU F O R L I S T E N IN G

NI CK EMERAL D CAT ADA