Lucky Strike
Software
The following
formal criteria that must be met before a software release can be allowed.
Attach to this form empirical documentation for each item.
1. [X] At least 90%
of planned code is complete.
2. [X] The slope of
the code growth curve for the week prior to release must be less than 25%.
3. [X] At least 90%
of binary miniature milestones are complete.
4. [X] There are no
severity 1 open defects.
5. [ ] The number of
defects reported must be at least 80% of predicted.
6. [X] 75% of all
severity 2 reported defects must have been fixed.
7. [ ] In the week prior to release, the ratio of
defects reported to defects fixed must be less than 25%.
8. [ ] A test coverage tool shows that system
test coverage is at least 80%. (Stage 3)
9. [X] The Release
Sign-Off form has been signed by all parties.
Explanation of
any items not checked.
5. The number of defects reported must
be at least 80% of predicted.
Our modules were relatively trivial and
not defect prone. Therefore we did not find the required
number of defects
planned. We found 17.6% of defects
planned.
7. In the week prior to release, the ratio of defects reported to defects fixed must be less than 25%
Our team was resolving defects at
the same rate at which they were being reported, It would be impossible for us
to meet this criteria, The ratio would always be one.
8.
A test coverage tool shows that system test coverage is at least 80%.
This was not
required for Stage 3 per the instructor’s request due to the minimal amount
of time towards
the end of the quarter.
1.
At least 90% of planned code is complete.
From our progress indicators the amount of code planned for
completion for Stage 3 was 915. 936 lines of code were completed during stage
3, 102% of the what was planned. The total lines of code at the end of Stage 3
to date was 6904. The actual amount of code completed to date is 6925. This is
100.3% of what was planned.
2.
The slope of the code growth curve for the week prior to release must be less
than 25%.
Our progress indicators show that there were 160 lines of
code delivered in week 9, the week prior to release. The total of lines of code
submitted for stage 3 was 936. Therefore the slope code growth is 17.09% (160 /
936).
3.
At least 90% of binary miniature milestones are complete
All requirements (from the Staged Delivery Plan) and planned
code (Integration Plan) for Stage 3 have been completed except for the features
that our group was allowed to disregard by the instructor. These features
include: robot color, tutorial, organize levels, and import an ‘xsb’ file.
4.
There are no severity one defects
According to Teamatic, all reported defects as of the end of
week 5, have been closed or resolved.
5. The number of defects reported must be at
least 80% of predicted
Requirement not met. Refer to #5 Explanation above.
6.
75% of all severity 2 reported defects must have been fixed.
All defects in Teamatic have been
closed or resolved, therefore all severity 2 defects have been fixed.
7.
In the week prior to release, the ratio of defects reported to defects fixed
must be less than 25%
Requirement not met. Refer to #7 Explanation above.
8.
A test coverage tool shows that system test coverage is at least 80%
Not required for stage 3.
9.
The Releas Sign-Off form has been signed off by all parties
All stakeholders have signed off on
the release. (See attached “Release Sign-Off Form”)