CUSTOMER_CODE
SMUDE
DIVISION_CODE
SMUDE
EVENT_CODE
JAN2016
ASSESSMENT_CODE BC0054_JAN2016
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
4581
QUESTION_TEXT
What is SCM? Explain the goals of SCM?
SCHEME OF
EVALUATION
Software configuration management is a methodology to control and
manage a software development project. (1 mark)
Goals of SCM:
•Configuration identification-what code are we working with?
•Configuration control-controlling the release of a product and its
changes.
•Status accounting-recording and reporting the status of components.
•Review – ensuring completeness and consistency among
components.
•Build management – managing the process and tools used for builds.
•Process management – ensuring adherence to the organization’s
development process
•Environment management – managing the software and hardware
that host our system.
•Teamwork – facilitate team interactions related to the process
•Defect tracking – making sure every defect has traceability back to
the source.
(9 points – 9 marks)
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
117419
QUESTION_TEXT
Explain the steps performed in Change Control.
SCHEME OF
EVALUATION
1.
A change request is submitted and evaluated to assess technical merit,
potential side effects, overall impact on other configuration objects and
system functions, and the projected cost of the change.
2.
The results of the evaluation are presented as a change report, which is
used by a change control authority (CCA) – a person or group who makes
a final decision on the status and priority of the change.
3.
An engineering change order (ECO) is generated for each approved
change. The ECO describes the change to be made, the constraints that
must be respected, and the criteria/or review and audit. The object to be
changed is “die out” of the project database, the change is made, and
appropriate SQA activities are applied. The object is then “checked in” to
the database and appropriate version control mechanisms are used to
create the next version of the software.
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
117421
QUESTION_TEXT
Give examples for Prevention Costs, Appraisal Costs, Internal &
External Failure Costs.
Prevention Costs:
Quality planning
Formal technical reviews
Test equipment
Training
Appraisal Costs:
In-process and inter-process inspection
Equipment calibration and maintenance
SCHEME OF
EVALUATION
Testing
Internal Failure Costs:
Rework
Repair
Failure mode analysis
External Failure Costs:
Complaint resolution
Product return and replacement
Help line support
Warranty work
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
117422
QUESTION_TEXT
Briefly discuss the major elements in a Closure Analysis Report.
SCHEME OF
EVALUATION
1.
General and Process-Related Information: The closure report first gives
general information about the project, the overall productivity achieved
and quality delivered, the process used and process deviations, the
estimated and actual start and end dates, the tools used, and so on.
2.
Risk Management: The risk management section gives the risks initially
anticipated for the project along with the risk mitigation steps planned.
3.
Size: Many projects use the bottom-up method for estimation. In this
method, the size of the software is estimated in terms of the number of
simple, medium, or complex modules.
4.
Causal Analysis: When the project is finished, the performance of the
overall process on this project is known. If the performance is outside
the range given in the capability baseline, there is a good chance that the
variability has an assignable cause.
5.
Effort: The closure analysis report also contains the total estimated
effort and actual effort in person-hours. The total estimated effort is
obtained from the management plan.
6.
Defects: The defects section of the closure analysis report contains a
summary of the defects found during the project. The defects can be
analyzed with respect to severity, stage detected, stage injected, and so
on.
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
117423
QUESTION_TEXT
Explain the types of organizational structures.
(Each carries 2 marks)
SCHEME OF EVALUATION
1.
Hierarchical organizational structure
2.
Flat organizational structure
3.
Matrix organizational structure
4.
Networked organizational structure
5.
T-form organization
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
117425
QUESTION_TEXT
What is a Life Cycle Model? Explain waterfall Life Cycle model.
Life Cycle models describe the interrelationships between software
development phases. – 1mrk
Waterfall model: this is the least flexible and most obsolete of the life
cycle models. Well suited to projects that have low risk in the areas of
user interface and performance requirements, but high risk in budget and
schedule predictability and control. This is the base model for all the
other models. This model involves the following phases.
SCHEME OF
EVALUATION
•
Analysis
•
Design
•
Implementation
•
Testing
•
Maintenance
To follow the waterfall model, one proceeds from one phase to the next
in a purely sequential manner.
When one completes “requirements specification” they set in store the
requirements of the software. When the requirements are fully
completed, one proceeds to design. When the design is fully completed,
an implementation of that design is made by the coders. After the
implementation and integration phases are complete, the software
product is tested and debugged; any faults introduces is removed here.
Then the software product is installed, and later maintained to introduce
new functionality and remove bugs.
Thus the waterfall model maintains that one should move to a new phase
only when the preceding phase is completed and perfected and there is
no jumping back and forth.
(Explanation: 9 marks)