»-----Original Message-----
»From: Roberto Marani [mailto:tan602@...]
»Sent: Thursday, April 25, 2002 00:47
»To: AsegCalidadSoftware@...
»Subject: Re: [ACS] Roles
»
»
»Si
»te recomiendo desde ya darte una vuelta por el sitio
»oficial, el SEI (Software Engineering Institue, depto
»del Carnegie Mellon University), que son los padres
»del CMM.
»La direccion es: http://www.sei.cmu.edu
»
»No se a que te referis con "roles", pero el CMM
»certifica niveles de madurez de los procesos de
»desarrollo de software.  Te paso un texto que te puede
»ayudar sobre el nivel 2:
»
»Level 2 - The Repeatable Level
»At the Repeatable Level, policies for managing a
»software project and
»procedures to implement those policies are
»established. Planning and
»managing new projects is based on experience with
»similar projects. Process
»capability is enhanced by establishing basic process
»management discipline
»on a project by project basis. An effective process
»can be characterized as
»one which is practiced, documented, enforced, trained,
»measured, and able to improve. Projects in Level 2
»organizations have installed basic software management
»controls. Realistic project commitments are based on the
»results observed on previous projects and on the requirements
»of the current project. The software managers for a project
»track software costs, schedules, and functionality; problems
»in meeting commitments are identified when they arise.
»Software requirements and the work products developed to
»satisfy them are baselined, and their integrity is controlled.
»Software project standards are defined, and the organization
»ensures they are faithfully followed. The software project
»works with its subcontractors, if any, to establish a
»customer-supplier relationship. Processes may differ between
»projects in a Level 2 organization. The organizational
»requirement for achieving Level 2 is that there are policies
»that guide the projects in establishing the appropriate
»management processes. The software process capability of Level
»2 organizations can be summarized as disciplined because
»planning and tracking of the software project is stable and
»earlier successes can be repeated. The project's process is
»under the effective control of a project management system,
»following realistic plans based on the performance of previous
»projects.
»
»Saludos
»Roberto Marani
»
»--- Idael Bandera <idael@...> wrote:
»> Señores, y señoras,
»> ¿Me pudieran decir cuáles o cómo llegar a los roles
»> de CMM?....Por lo menos
»> a los que pertenecen al nivel 2.
»> 
»> Idael
»>
»
»
»__________________________________________________
»Do You Yahoo!?
»Yahoo! Games - play chess, backgammon, pool and more
»http://games.yahoo.com/
»
»------------------------------
»
»AsegCalidadSoftware:
»Aseguramiento de la Calidad del Software
»------------------------------
»Direcciones de la lista:
»Publicar un mensaje: AsegCalidadSoftware@eGroups.com
»Suscribirse........: AsegCalidadSoftware-Subscribe@eGroups.com
»Desuscribirse......: AsegCalidadSoftware-Unsubscribe@eGroups.com
»Administrador......: AsegCalidadSoftware-Owner@eGroups.com
»Página de la lista.: http://es.eGroups.com/group/AsegCalidadSoftware
»------------------------------
»http://www.navegana.com/dinero/chanzes.html
»
»Tu uso de Yahoo!
»Grupos está sujeto a las http://ar.docs.yahoo.com/info/utos.html
»
»