Professional Documents
Culture Documents
Contenido
1. Criterios para definir el dominio del
conocimiento
2. El dominio de la informacin
3. Arquitectura de Software para Dominios
Especficos DSSA
4. Controles y mtricas de acuerdo al dominio
5. Modelos de Madurez
6. Enfoque de acuerdo al dominio
El dominio de la informacin.
Visin etnometodolgica
La toma de requerimientos es una actividad
social
Porque involucra comunicacin entre personas
(discusiones, observacin de la realidad, etc)
Porque involucra negociacin para lograr
consensos
Porque afecta y cambia los sistemas de actividad
humana
El dominio de una aplicacin es, generalmente,
un mundo social
Mundo Social
El dominio de la informacin
El software se construye para procesar datos;
para transformar datos de una forma a otra; es
decir, para aceptar una entrada, manipularla de
alguna forma y producir una salida
Metodologas
Las principales metodologas estructuradas para
el desarrollo de sistemas de software incluyen la
especificacin de los requerimientos y, a partir
de estos la elaboracin de un diseo.
Principios fundamentales
Representar y comprender el dominio de la
informacin, as como el dominio funcional de un
problema.
Subdividir el problema de forma tal que se
descubran los detalles de una manera progresiva
(o jerrquica). La particin se aplica para reducir
la complejidad.
Representar al sistema lgica y fsicamente.
DSSA
Para la formalizacin de la reutilizacin es
esencial el anlisis de dominios.
Dominio
Es una esfera de actividad o inters, tambin
denominado campo
Un dominio especfico es un rea de
aplicacin, un campo para el cual los sistemas
de software fueron creados.
Anlisis de dominios
Es el proceso mediante el cual la informacin
utilizada en el desarrollo de sistemas es
identificada, capturada y organizada con el
propsito de hacerla reutilizable en la creacin
de nuevos sistemas de software para tal
dominio.
Representacin matemtica
Conjuntos
Modelos de Madurez
CMMI
Is the successor of the Capability Maturity Model
(CMM)
Developed in 1991 to overcome CMM's pitfall of
having many incompatible maturity models.
The idea was to create an overall framework for
the integration of different maturity models.
CMMI stages
0 Non-existent when
The organisation does not recognise the need for
IT security. Responsibilities and accountabilities
are not assigned for ensuring security. Measures
supporting the management of IT security are not
implemented. There is no IT security reporting
and no response process for IT security breaches.
CMMI stages
Maturity Level 1 Initial
Processes are only basically defined or not defined
at all. This leads to a strong dependence on single
persons within a project. A remedy is to define
and document basic processes and keep records
of important information.
CMMI stages
Maturity Level 2 Managed
In order to establish a basis, the fundamentals of
project management need to be defined at level
2. These applied project management principles
lead to controllable and manageable projects
which can be completed in time and in budget.
CMMI stages
Maturity Level 3 Defined
At level 3 the focus shifts from single projects to
the whole organization. Standardized processes
are defined globally within the organization which
leads to a stronger exchange of data and
experience across different projects. It also implies
some kind of cultural change since employees
have to change their minds from focusing solely
on their project goals to focusing on the
organizations overall goals.
CMMI stages
Maturity Level 4 - Quantitatively Managed
After consistent processes have been introduced
across the organization, measurement and
benchmarking systems can be introduced in order
to be able to better control projects.
Wide, adequate predictions of processes as well
as other assumptions based on recognized
variances at a particular process can be made.
CMMI stages
Maturity Level 5 Optimizing
At level five the focus is to continuously improve
the prevailing processes. This is mostly done by
analyzing variations based on the quantitative
measure introduced at level four. Due to changes
of circumstances a continuous adaptation to new
requirements is indispensable in order to remain
competitive.
CMMI stages
COBIT
COBIT defines IT activities in a generic process
model within four domains. These domains are
Plan and Organise, Acquire and Implement,
Deliver and Support, and Monitor and Evaluate.
The domains map to ITs traditional
responsibility areas ofplan, build, run and
monitor.
COBIT
COBIT
Plan and Organise (PO)
Provides direction to solution delivery (AI) and service delivery (DS)
Acquire and Implement (AI)
Provides the solutions and passes them to be turned into services
Deliver and Support (DS)
Receives the solutions and makes them usable for end users
Monitor and Evaluate (ME)
Monitors all processes to ensure that the direction provided is
followed
COBIT framework
IT resources are managed by IT processes to
achieve IT goals that respond to the business
requirements. This is the basic principle of the
COBIT framework
COBIT framework
Bibliografa
Kendall & Kendall , Anlisis Y Diseo De Sistemas 3 Ed., Prentice Hall, Mxico,1997.
Pressman, Roger S. "Ingeniera del Software: Un enfoque prctico", 5a edicin. Editorial McGraw
Hill, Espaa, 2002.
Yourdon, Edward, Anlisis estructurado moderno, Ed. Prentice Hall/Pearson, 1993.
Carma MacClure. Reuse lngineering: extending infonnation engineering to enable software reuse.
Extended lntelligence, lne. 1994
Rubn Prieto-Diaz. Domain Analysis: an introduction. The Contel Technology Center, 1985.
Rubn Prieto-Diaz. Domain Analysis for reusability. IEEE Computer Society Press, Los Alamitos,
CA, 1990.
COBIT 4.1