Test
IS2.13
Crea una cuenta gratis para terminar este test
Guarda tu progreso y consulta tu resultado final.
¿Ya tienes cuenta? Inicia sesión
Preguntas del test (20)
1The purpose of configuration change control is?
- ATo maintain the integrity of the product in all of its states
- BBeing able to track
- CBe constituents or compounds
- DHave complete control of the system
- EMake change in their development
- FManage of different processes or sets of tools
2The following types of items are the minimum that shall be subject to change control:
- AConstituent CIs as they participate in larger components
- BEach configuration baseline as a separately identified configuration item
- CSpecification of the environment and tool chains used in producing the baseline
- DThe lines of code must be identified and used in the development
- EEstablish forms in the change request
- FDesignate items subject to change control
3A change request form shall be established with at least the following standard fields:
- ADescription of proposed change and rationale/purpose
- BState of the change
- CAffected baseline
- DOutcome of analysis of impact on the project
- EResolution
- FApprovals
4For controlling constituent configuration items, the following attributes shall be available in the CMDB for each change request:
- AOriginator
- BImpact analysis
- CRationale and approval
- DNotification
- EReversibility
- FSet of Changes
5What Is Software Quality?
- AQuality must be defined and measured if improvement is to be achieved
- BIt is a multidimensional concept
- CComposed of levels of abstraction
- DPopular use language
- EIs responsible for capturing what one thinks
- FSeries of steps leading to an end
6The narrowest sense of product quality is commonly recognized as?
- ALack of "bugs" in the product
- BBottleneck
- CMistakes in production
- DMistakes in the product
- EThe lacks of "errors" in production
- FAccumulated tasks
7To increase overall customer satisfaction as well as satisfaction with various quality attributes, the quality attributes must be taken into account?
- AThe planning and design of the software
- BThe analysis and the result
- CThe development
- Donly planning
- EThe result and development
- FThe software design and result
8The exponential model is another special case of the Weibull family, with the shape parameter m equal to:
- A1
- B2
- C0
- D3
- E-1
- F-2
9What does CDF and PDF mean?
- ACumulative distribution function and Probability density function
- BUpdated development function and Project development function
- CCumulative distribution factor and practice distribution function
- DCumulative design function and project design function
- Ecumulative distribution function and designated probability factor
10How many models of software reliability modeling have been proposed?
- AMore than one hundred models have been proposed in professional journals and in software conferences
- BMore than a thousand models were created based on the other models
- CMore than a thousand models have been proposed in professional journals and software conferences
- DMore than five hundred models have been proposed in professional journals and software conferences
- ENo more than fifty models have been proposed in professional journals and software conferences
- FNo more models have been proposed in professional journals and software conferences
11Software reliability growth models can be classified into two major classes
- Adepending on the variable
- Bdepending of the model
- Cdepending on the analysis
- Ddepending on the design
- Edepending on the development
- Fdepending on the result
12They are reliability growth models:
- AJelinski-Moranda Model
- BLittlewood Models
- CGoel-Okumoto Imperfect Debugging Model
- DGoel-Okumoto Nonhomogeneous Poisson Process Model
- EMusa-Okumoto Logarithmic Poisson Execution Time Model
- FThe Delayed S and Inflection S Models
13The basic assumptions of the fault count model are as follows (Goel, 1985):
- ATesting intervals are independent of each other
- BTesting during intervals is reasonably homogeneous
- CNumbers of defects detected during non overlapping intervals are independent of each other
- DAll faults contribute equally to cause a failure
- EFix time is negligible
- FFix is perfect for each failure; there are no new faults introduced during correction
14Los criterios para la evaluación del modelo son los siguientes:
- AValidez predictiva
- BCapacidad
- CCalidad de los supuestos
- DAplicabilidad
- ESencillez
- FEscalabilidad
15The metrics in the analysis include:
- AFan-in
- BFan-out
- CMcCabe's cyclomatic complexity index (CPX)
- DNumber of INCLUDES in the module
- EPrevious defect history
- FDefect level in the current system
16Los sistemas de gestión de versiones ofrecen a menudo varias características:
- AIdentificación de versión y entrega
- BGestión de almacenamiento
- CRegistro del historial de cambios
- DDesarrollo independiente
- ESoporte de proyecto
- FSoporte técnico
17Al comparar las firmas en los archivos de código fuente y objeto, es posible decidir si el componente del código fuente se usó para generar el componente de código objeto.Hay dos tipos de firmas que pueden usarse:
- AModificación de marca de tiempo
- BSumas de verificación de código fuente
- CValidación del codigo utilizado
- DModificación del codigo objeto
- ESumas realizadas en el codigo objeto
- FModificación del codigo fuente
18Cuáles son los principales procesos de administración de la configuración?
- AAdministración del cambio
- BGestión de versiones
- CConstrucción del sistema
- DGestión de entregas de software
- EPlanificación del diseño
- FAdministración del análisis realizado
19Qué es la construcción de un sistema?
- AProceso de ensamblar componentes de sistema en un programa ejecutable
- BPasos que deben seguirse para realizar el sistema
- CCrear los elementos necesarios para su construcción
- DHacer una estandarización
- EProceso que nos da como resultado un sistema
- FPasos que se realizan en un momento determinado
20Las entregas de sistema contienen:
- ACódigo ejecutable
- BArchivos de datos
- CArchivos de configuración
- DDocumentación
- EDiseño de la interfaz
- FAnálisis realizado
Información
- Descripción
- Test sobre IS2.13, creado por Leandro Ramos Valdéz el 11/07/2018.
- Autor
- Leandro Ramos Valdéz
- Idioma
- English
- Visitas
- 2
- Valoración
- Aún sin valoraciones Valora este test