Discovering and fixing software bugs is a difficult maintenance task, and a considerable amount of effort is devoted by software developers on this issue. In the world of software one cannot get rid of the bugs, fixes, patches etc. each of them have a severity and priority associated to it. There is not yet any formal relation between these components as both of these either depends on the developer and tester or on customer and project manger to be decided on. On one hand, the priority of a component depends on the cost and the efforts associated with it. While on the other, the severity depends on the efforts required to accomplish a particular task. This research paper proposes a formula that can draw a relationship among severity and priority.
[1]
Alistair Cockburn,et al.
Writing Effective Use Cases
,
2000
.
[2]
Joseph M. Mellichamp,et al.
Software Development Cost Estimation Using Function Points
,
1994,
IEEE Trans. Software Eng..
[3]
Charles R. Symons,et al.
Function Point Analysis: Difficulties and Improvements
,
1988,
IEEE Trans. Software Eng..
[4]
Mordechai Ben-Menachem,et al.
Writing effective use cases
,
2001,
SOEN.
[5]
D. Ross Jeffery,et al.
Function Points in the Estimation and Evaluation of the Software Process
,
1990,
IEEE Trans. Software Eng..