Software development

• US 8,051,404 B2
• Filed: 10/26/2001
• Issued: 11/01/2011
• Est. Priority Date: 10/26/2000
• Status: Expired due to Fees

• Current Assignee: Micro Focus Incorporated (Open Text Corporation)
• Original Assignee: Micro Focus Incorporated (Open Text Corporation)
• Inventors: Hogan, Michael, Conaty, Garrett, McGovern, Fergal, Chapman, Martin, Head, Philip
• Primary Examiner(s): DAO, THUY CHAN
• Application Number:
  US10/415,466
• Publication Number:
  US 20050125769A1
• Time in Patent Office: 3,658 Days
• Field of Search: None
• US Class Current: 717/109
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

A method of developing software capable of performing a task, the task comprising at least one task step required to perform the task. The task step has a resultant effect. The method comprises recording a use case comprising one or more scenarios, that comprise one of more further steps; recording the scenario or one of the scenarios as a main success scenarios such that the resultant effect of the main success scenario is the same as the resultant effect of the task step. Use cases which have been stripped of context-specific information may be re-used. Such information may be included in a reference to the re-used use case.

Claims

1. A method executed by a computer for developing software capable of performing a task, the task comprising a task step required to perform the task, the task step having a resultant effect and determining one or more changes in business entities, wherein the method comprises:

recording a use case comprising one or more scenarios, the or each scenario comprising one or more further steps, wherein the use case is a representation of the task step associated with determining the one or more changes in the business entities;

recording a refinement relationship between the task step and the use case, the refinement relationship having an associated justification stating how the task step is realized by the use case;

recording the scenario or one of the scenarios as a main success scenario such that a resultant effect of the main success scenario is the same as the resultant effect of the task step;

determining that the resultant effect of the task step is the same as the resultant effect of the main success scenario by using one or more justifications; and

qualifying the use case by removing context-specific information, wherein context-specific information includes one or more attributes of the use case that are associated with an environment in which the use case is used.

2. The method as claimed in claim 1 wherein the use case is a reusable use case and the method further comprises recording a reference to the reusable use case stored elsewhere.

3. The method as claimed in claim 2 wherein the reusable use case is stored without context-specific information.

4. The method as claimed in claim 1 wherein the use case comprises, in addition to the main success scenario, one or more alternative scenarios.

5. The method as claimed in claim 1 wherein the use case has a required post-condition.

6. The method as claimed in claim 1 wherein the use case has a required post-condition, the use case being applied only to the main success scenario.

7. The method as claimed in claim 1 wherein the use case comprises a pre-condition.

8. A method executed by a computer for developing software capable of performing a task, the task comprising a task step required to perform the task, the task step having a resultant effect and determining one or more changes in business entities, wherein the method comprises:

recording a reference to a use case comprising one or more further steps such that the further step or one of the further steps have a resultant effect which is the same as the resultant effect of the task step, wherein the use case is a representation of the task step associated with determining the one or more changes in the business entities;

recording a refinement relationship between the task step and the use case, the refinement relationship having an associated justification stating how the task step is realized by the use case;

determining that the resultant effect of the task step is the same as the resultant effect of the further step or one of the further steps by using one or more justifications; and

qualifying the use case by removing context-specific information, wherein context-specific information includes one or more attributes of the use case that are associated with an environment in which the use case is used;

wherein the use case is stored elsewhere with no context-specific information, thereby allowing re-use of the use case.

9. The method as claimed in claim 8 wherein the further steps collectively define a main success scenario.

10. The method as claimed in claim 8 comprising recording a justification demonstrating how the resultant effect is realised by the one or more further steps.

11. The method as claimed in claim 8 further comprising determining the extent of the software development on the basis of the refinement relationship.

12. The method as claimed in claim 11 wherein:

the software development is a project;

the project has a project life-cycle; and

the refinement relationship states what stage of the project life-cycle the project is at.

13. A non-transitory computer readable medium having program instructions for a software tool executed by a computer for developing software capable of performing a task, the task comprising a task step required to perform the task, the task step having a resultant effect and determining one or more changes in business entities, wherein the tool comprises:

logic for recording a reference to a use case comprising one or more further steps such that the one or more further steps have a resultant effect which is the same as the resultant effect of the task step, wherein the use case is a representation of the task step associated with determining the one or more changes in the business entities;

logic for recording a refinement relationship between the task step and the use case, the refinement relationship having an associated justification stating how the task step is realized by the use case;

logic for determining that the resultant effect of the task step is the same as the resultant effect of the one or more further steps by using one or more justifications;

logic for qualifying the use case by removing context-specific information, wherein context-specific information includes one or more attributes of the use case that are associated with an environment in which the use case is used; and

logic for storing the use case elsewhere with no context-specific information, thereby allowing re-use of said use case.