Development processes representation and management

• US 20040143811A1
• Filed: 09/02/2003
• Published: 07/22/2004
• Est. Priority Date: 08/30/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Schaefers, Andreas, Santilli, Michael, Zahn, Juergen, Lucks-Baus, Anette, Kaelicke, Elke, Mansmann, Roman, Tesche, Bernd, Pollinger, Dieter, Fried, Gerhard, Kehr, Harald, Leber, Fritz, Wenig, Reinhard, Bannert, Michael, Fisher, Harald, Mueller, Thomas, Bellis, Gary, Liesner, Marc, Filbry, Nadine, Salwitz, Kenneth, Stuckert, Harald, Patel, Nimish, Pezza, Michael, Giesche, Gertrud, Gregory, Donna, Houck, Randolph, Ambruoso, Nelson, Rajczi, Theresa, Crowe, Glenn, Roberts, Richard III, Bhatt, Chirantan Vinayak, MacDonald, Andrea, Jaeckle, Volkmar, Wagener, Dirk, Farrell, Christopher, Roesinger, Andrea, Mattox, Phillip
• Granted Patent: US 7,810,067 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Systems and techniques to manage and represent development processes. In general, in one implementation, the technique includes a method for managing a software development process. The method includes providing a cookbook describing tasks in a framework of the development process and managing performance of the development process with the cookbook. A first task description identifies an activity in the development process, an input for performance of the activity, an output consequential of performance of the activity, and instructions for performance of the activity. Managing performance of the development process with the cookbook includes assigning activities in the development process to different participants in accordance with the activities identified in the task descriptions, exchanging information between participants in accordance with the inputs and outputs identified in the task descriptions, and instructing the participants in accordance with the instructions identified in the task descriptions.

Claims

1. A method for managing a software development process, comprising:

providing a cookbook describing tasks in a framework of the development process, a first task description in the cookbook identifying

an activity in the development process,

an input for performance of the activity,

an output consequential of performance of the activity, and

instructions for performance of the activity; and

managing performance of the development process with the cookbook, including

assigning activities in the development process to different participants in accordance with the activities identified in the task descriptions,

exchanging information between participants in accordance with the inputs and outputs identified in the task descriptions, and

instructing the participants in accordance with the instructions identified in the task descriptions.

2. The method of claim 1, wherein providing the cookbook describing tasks in the framework of the development process comprises providing a regular arrangement of task descriptions in one or more matrices.

3. The method of claim 1, wherein providing the cookbook comprises:

providing a first collection of task descriptions in a first track of the development process, the first collection directed to development of a result; and

providing a second collection of task descriptions in a second track of the development process, the second collection directed to project management of the development of the result.

4. The method of claim 1, wherein providing the cookbook comprises providing the cookbook describing tasks in a collection of frameworks, the frameworks including

an evaluation phase wherein a request for a proposed development is received and evaluated,

a development and test phase wherein a development result is developed and tested,

a delivery and acceptance phase wherein the development result is delivered to and accepted by the party who requested development, and

a maintenance phase wherein the development result is maintained.

5. A method comprising:

receiving a superset of task descriptions describing potential tasks in development processes;

selecting a relevant set of task descriptions from the superset, the relevant set fit to a particular development process; and

arranging the relevant set in a framework for performing the particular development process.

6. The method of claim 5, wherein receiving the superset of task descriptions comprises receiving the superset of task descriptions organized by phases in the development process, the phases including

an evaluation phase wherein a request for a proposed development is received and evaluated,

a development and test phase wherein a development result is developed and tested,

a delivery and acceptance phase wherein the development result is delivered to and accepted by the party who requested development, and

a maintenance phase wherein the development result is maintained.

7. The method of claim 5, wherein receiving the superset of task descriptions comprises receiving the superset of task descriptions organized by tracks in the development process, a first track directed to development of a result, a second track directed to project management of the development of the result.

8. A system comprising:

a superset of task descriptions describing potential tasks in development processes, a first task description in the superset identifying

a first activity in the development process;

a first input for performance of the first activity;

a first output consequential of performance of the first activity; and

instructions for performing the first activity.

9. The system of claim 8, wherein the instructions include:

information regarding location of the first input when the first input is part of an output of a second activity in a development process; and

information regarding generation of the first input in an absence of the second activity from the development process.

10. The system of claim 8, wherein the superset is organized by phases in the development process, the phases including:

an evaluation phase wherein a request for a proposed development is received and evaluated;

a development and test phase wherein a development result is developed and tested;

a delivery and acceptance phase wherein the development result is delivered to and accepted by the party who requested development; and

a maintenance phase wherein the development result is maintained.

11. The system of claim 8, further comprising a framework for assembly of a relevant set of task descriptions from the superset, the relevant set of task descriptions fit to the development process.

12. The system of claim 11, wherein the framework comprises a matrix for regular arrangement of task descriptions in rows and columns.

13. The system of claim 8, further comprising a selection mechanism to select a relevant set of task descriptions from the superset, the relevant set of task descriptions fit to the development process.

14. The system of claim 8, wherein the superset of task descriptions includes at least forty-two task descriptions selected from a collection of tasks including

a lead generation task;

a lead qualification task;

an evaluation task;

a negotiation task;

a specification creation task;

a specification review task;

an intermediate design task;

a prototype creation task;

a design review task;

a test strategy definition task;

a test strategy review task;

a specification stage sign-off task;

a test and development guide update task;

a monitor development execution task;

a create scenario design/component architecture task;

a review scenario design/component architecture task;

a create scenario documentation task;

a component design task;

a review component design task;

a monitor development execution task;

a kickoff implementation task;

a test catalogue creation task;

an implementation task;

a test catalogue review task;

a test readiness confirmation task;

a development testing task;

a supplemental testing task;

a result freeze task;

a module integration testing task;

a technical specification creation task;

a technical specification review task;

a test systems and tester preparation task;

a user documentation task;

a component assembly task;

a master guide checklist update task;

a test readiness confirmation task;

a development result to test transfer task;

an execution monitoring task;

an acceptance test kick-off task;

an error correction task;

an acceptance testing task;

a result documentation review task;

an emergency correction task;

a test report creation task;

a handover task;

a delivery and acceptance phase initiation task;

an execution monitoring task;

a handover receipt task;

a development result distribution task;

a development result distribution validation task;

a sign-off task;

a warranty obligation fulfillment task;

a sales/marketing material creation task;

a scenario validation task;

a maintenance handover task;

a maintenance sign-off task;

a transition to maintenance task;

a phase close-out task;

a development performance reporting task;

a development process analysis task;

a participant debriefing task;

a document check-in task;

a close-out checklist completion task;

a close-out checklist review task;

a handover (development and testing to production and assembly) task;

a prototype assembly task;

a prototype validation in reference environment task;

a prototype validation in different environment(s) task;

an installation guide creation task;

an assembly/validation status reporting task;

a project management task;

a development result production task;

a prototype validation reporting task;

a handover (production and assembly to customers and maintenance) task;

a maintenance scheme establishment task;

a monitoring and dispatch task;

a problem analysis task;

a maintenance activity performance task;

a maintenance activity testing task;

a maintenance information propagation task;

a maintenance instruction generation task;

a maintenance event termination task;

a maintenance reporting task;

a development request evaluation task; and

a correction propagation task.

15. The system of claim 14, wherein the superset of task descriptions includes at least sixty tasks selected from the collection.

16. The system of claim 15, wherein superset of task descriptions includes at least seventy tasks selected from the collection.

17. The system of claim 14, wherein the descriptions of the lead generation task, the lead qualification task, the evaluation task, and the negotiation task comprise at least fourteen task descriptions selected from a second collection of tasks including:

a lead targeting and gathering task;

a lead qualification task;

a project/service request handover task;

a project/service request approval task;

an information gathering task;

an opportunity development task;

an opportunity assessment task;

a staffing/project prioritization preclarification task;

a project/service request approval task;

an evaluation offer presentation task;

an evaluation offer negotiation task;

a project charter and business case project team establishment task;

a customer business model and business process(es) analysis task;

a product strategy definition task;

a solution proposal creation task;

an ARC sheet creation task;

a solution proposal review task;

a business case creation task;

a risk analysis task;

a business case review task;

a business case approval and sign-off task;

a service/project proposal creation task;

a service/project proposal negotiation task;

a handover to development task;

a license and service agreement check task;

a framework agreement negotiation task;

a statement of work negotiation task; and

a contract execution and filing task.

18. The system of claim 17, wherein the lead generation task description, the lead qualification task description, the evaluation task description, and the negotiation task description include at least twenty tasks selected from the second collection.

19. The system of claim 18, wherein the lead generation task description, the lead qualification task description, the evaluation task description, and the negotiation task description include at least twenty five tasks selected from the second collection.

20. A method comprising:

providing one or more matrices describing tasks that define a phased, project development methodology to be used in a development process, wherein a first of the tasks receives output information from a second of the tasks when the second of the tasks is retained in the development process, and the first task provides description regarding obtaining the output information when the second task is disregarded in the development process.

21. The method of claim 20, wherein the one or more matrices describe tasks by identifying:

an activity in the development process;

an input corresponding to performance of a second activity in the development process;

an output consequential of performance of the activity; and

a link to a corresponding template for performance of the activity.

22. The method of claim 21, further comprising:

selecting one or more of the tasks in the one or more matrices;

generating a phased, software product development methodology using a set of the templates corresponding to the selected tasks; and

managing a software development process using the generated software product development methodology.