Method for application development

• US 20090271760A1
• Filed: 04/24/2008
• Published: 10/29/2009
• Est. Priority Date: 04/24/2008
• Status: Abandoned Application

• Current Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Original Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Inventors: Ellinger, Robert Stephen
• Application Number:
  US12/081,982
• Publication Number:
  US 20090271760A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/20 Software design

Abstract

A process and method for application development that conforms with Rapid Application Development (RAD) requirements and Software Engineering Institute (SEI) Software Capability Maturity Model Integrated (CMMI) Level 3 requirements. An application development process that conforms with Rapid Application Development (RAD) requirements and Software Engineering Institute (SEI) Software Capability Maturity Model Integrated (CMMI) Level 3 requirements includes one or more formally-named development cycles, one or more formally-named design cycles, in which each development cycle includes one or more formally-named design cycles, and one or more formally-named construction cycles, in which each design cycle includes one or more formally-named construction cycles.

Claims

1. An application development process comprising:

one or more formally-named development cycles;

one or more formally-named design cycles, wherein each development cycle includes one or more formally-named design cycles;

one or more formally-named construction cycles, wherein each design cycle includes one or more formally-named construction cycles; and

,

wherein the application development process conforms with Rapid Application Development (RAD) requirements and Software Engineering Institute (SEI) Software Capability Maturity Model Integrated (CMMI) Level 3 requirements.

2. The application development process of claim 1, further comprising:

a SEI SW CMM Level 3 conformant risk management process.

3. The application development process of claim 1, further comprising:

a SEI SW CMM Level 3 conformant issue management process.

4. The application development process of claim 1, further comprising:

a SEI SW CMM Level 3 conformant software quality assurance (SQA) process.

5. The application development process of claim 1, further comprising:

a SEI SW CMM Level 3 conformant documentation process.

6. The application development process of claim 1, further comprising:

a use case based estimating process that utilizes one or more use-cases.

8. The application development process of claim 1, wherein the one or more development cycles identify certain customer requirements for an application and include holding a planning game, wherein each planning game includes determining to meet the certain customer requirements during a development cycle and assigning work to meet the certain customer requirements.

9. The application development process of claim 8, wherein the one or more design cycles include holding a design cycle planning meeting, wherein the design cycle planning meeting includes designing components of the application to meet the certain customer requirements.

11. An application developed using the application development process of claim 1.

12. The application of claim 1, wherein the application is a web application

7. The application development process of claim further comprising:

a use case based earned value process that bases earned value on the number of use-cases that are completed.

10. The application development process of claim 10 further comprising acceptance test development based on use-cases, wherein acceptance tests are used to test whether the coded components of the application meet the certain customer requirements.

13. An application development method comprising steps of:

executing a development cycle, wherein executing the development cycle identifies certain customer requirements for an application, the executing a development cycle further including;

implementing a planning game, wherein implementing the planning game includes determining to meet the certain customer requirements during the development cycle and assigning work to meet the certain customer requirements; and

executing one or more design cycles, wherein executing each of the one or more design cycles includes;

implementing a design cycle planning meeting, wherein implementing the design cycle planning meeting includes designing components of the application to meet the certain customer requirements; and

executing one or more construction cycles to code and test the components of the application designed in the design cycle; and

wherein the application development method conforms with Rapid Application Development (RAD) requirements and Software Engineering Institute (SEI) Software Capability Maturity Model Integrated (CMMI) Level 3 requirements.

14. The method of claim 13, wherein the executing each of the one or more construction cycles further includes:

implementing a standup meeting; and

constructing the designed components.

15. The method of claim 14, wherein the constructing step includes:

coding the designed components;

verifying the code from the coding step; and

unit testing the verified code.

16. The method of claim 15, wherein the verifying step includes egoless programming.

17. The method of claim 14, wherein the standup meeting is approximately thirty minutes.

18. The method of claim 13, wherein the customer requirements include use-cases.

19. The method of claim 18, wherein the customer requirements further include constraints.

20. The method of claim 18, wherein the determining to meet the certain customer requirements includes prioritizing use-cases.

21. The method of claim 20, wherein the customer performs the prioritizing use-cases step.

22. The method of claim 18, wherein the determining to meet the certain customer requirements includes assigning use-cases.

23. The method of claim 22, wherein a development team member performs the assigning use-cases step.

24. The method of claim 18 further comprising a step of developing acceptance tests based on the use-cases, wherein the acceptance tests are used to test whether the coded components of the application meet the certain customer requirements.

25. The method of claim 24 further comprising a step of acceptance testing of the coded components of the application using the acceptance tests.

26. The method of claim 25, wherein the executed development cycle is a first development cycle, the method further comprising executing a second development cycle if the coded components of the application fail the acceptance testing.

27. The method of claim 13, wherein the designing components step includes designing a class based on one or more of the certain customer requirements.

28. The method of claim 27, wherein the designing classes step uses class, responsibility, collaborator (CRC) cards.

29. The method of claim 28, wherein the designing classes step further includes:

identifying candidate classes on the CRC cards;

adding responsibilities;

consolidating classes based on the responsibilities; and

re-factoring classes based on the responsibilities.

30. The method of claim 29, wherein the designing classes step further includes:

adding collaborating classes;

consolidating classes based on the collaborating classes; and

re-factoring classes based on collaborating classes.

31. The method of claim 30, wherein the designing classes step further includes:

testing classes to ensure that they perform all the functions needed by the one or more of the certain customer requirements.

32. The method of claim 13 wherein the development cycle has a duration of four weeks.

33. The method of claim 13 wherein the executing the development cycle includes executing four design cycles.

34. The method of claim 13 wherein each design cycle has a duration of one week.

35. The method of claim 13 wherein executing one or more design cycles includes executing five construction cycles.

36. The method of claim 13 wherein each construction cycle has a duration of one day.

37. The method of claim 13 further comprising executing a startup phase.

38. An application developed according to the method of claim 13.