Академический Документы
Профессиональный Документы
Культура Документы
A) Iterative
B) Incremental
Ans –
3) The elapsed repair or restart time when a system failure occurs. Given
that the system must be continuously available, this is used to measure
AVAIL.
· Fault detection: Faults are detected before the software is put into
operation. The software validation process uses static and dynamic
methods to discover any faults, which remain in a system after
implementation.
Exception Handling
When an error of some kind or an unexpected event occurs during
the execution of a program, this is called an exception. Exceptions may
be caused by hardware or software errors. When an exception has not
been anticipated, control is transferred to system exceptions handling
mechanism. If an exception has been anticipated, code must be included
in the program to detect and handle that exception.
Defensive programming
Failure prevention
Damage assessment
Fault recovery
(1) When coded is corrupted The use of coding techniques which add
redundancy to the data allows errors to be corrected as well as detected.
Design by Contract
A) Data-flow models
The model shows how the order for the goods moves from process to
process. It also shows the data stores that are involved in this process.
B) Semantic Models
C) Object Models
Ans –
· Be a temporary system
· Be designed rapidly
· Provide a tangible or visual expression of a proposed system.
· The usage and test planning process refines the usage models, defines
the test plans, and statistically generates the test cases. In principle, the
usage model allows an unlimited number of test cases, but only a finite
sample is derived from the usage model on the basis of the usage
probability distribution.
Ans –
The higher the CMM maturity level is, the more disciplined, stable, and
well-defined the development process is expected to be and the
environment is assumed to make more use of “automated tools and the
experience gained from many past successes” (Zhiying 2003). The
staged character of the model lets organizations progress up the
maturity ladder by setting process targets for the organization. Each
advance reflects a further degree of stabilization of an organization’s
development process, with each level “institutionaliz[ing] a different
aspect” of the process (Oshana & Linger 1999).
Each CMM level has associated key process areas (KPA) that
correspond to activities that must be formalized to attain that level. For
example, the KPAs at level 2 include configuration management, quality
assurance, project planning and tracking, and effective management of
subcontracted software. The KPAs at level 3 include intergroup
communication, training, process definition, product engineering, and
integrated software management. Quantitative process management
and development quality define the required KPAs at level 4. Level 5
institutionalizes process and technology change management and
optimizes defect prevention.
· Using the feature set to estimate the budget and schedule while
“leveraging as much past knowledge as possible” (project planning)
· Ensuring schedules and plans are visible to all the stakeholders (project
tracking)
· Ensuring that the team follows its own plan and standards and “corrects
discrepancies when they occur” (quality assurance)