System and method for automated generation of software development life cycle audit documentation

Patent metadata

Field	Value
Publication number	US-10963243-B2
Application number	US-201916663869-A
Country	US
Kind code	B2
Filing date	Oct 25, 2019
Priority date	Oct 25, 2018
Publication date	Mar 30, 2021
Grant date	Mar 30, 2021

Abstract

An embodiment of the present invention may be directed to an automated generation of software development life cycle audit documentation tool that enables development teams to move from point-in-time documentation to living documentation while still satisfying software development life cycle (SDLC) audit and risk concerns. An embodiment of the present invention is directed to generating release artifacts for application teams, to avoid costly application development time being used to fill in paperwork. An embodiment of the present invention may run as a Command Line Interface, or as a part of the build pipeline for application teams. This enables development teams to spend their time focusing on delivering high quality business solutions in a rapid fashion.

First claim

What is claimed is:

1. A system for automated generation of software development life cycle audit documentation, the system comprising:
a source code repository that stores source code;
an interface that communications with one or more users via a communication network; and
a computer processor, coupled to the repository and the interactive interface, configured to perform the steps of:
retrieving one or more requirements from a business collaboration tool;
identifying one or more code changes relating to the one or more requirements from a source code repository to determine functional code that was changed for each requirement;
linking business budget and financial milestone data to the one or more requirements to document who approved an associated business investment;
accessing code review information from the source code repository to ensure each code change was reviewed and approved by a team member;
accessing a test execution and results from a test management system;
linking the test execution and results to one or more functional requirements and non-functional requirements;
accessing non-functional tests from one or more systems of records;
linking the non-functional tests to one or more release and business requirements;
applying a template that describes a format of a living documentation that automatically links to a release cycle; and
generating the living documentation based on the template.

2. The system of claim 1 , wherein test code committed to the source code repository is linked back to ensure test code coverage is provided.

3. The system of claim 1 , wherein build information is linked from a build pipeline tool that shows each daily build, associated results and unit test results for each build.

4. The system of claim 1 , wherein the test execution and results relate to QA, UAT, integration and regression.

5. The system of claim 1 , wherein the non-functional tests comprise stress tests, load tests, performance tests and security tests.

6. The system of claim 1 , wherein the living documentation is a software development software development life cycle (SDLC) documentation.

7. The system of claim 1 , wherein the computer processor is further configured to perform the step of: generating SDLC artifacts to satisfy risk and audit concerns.

8. The system of claim 1 , wherein the computer processor is further configured to perform the step of: documenting application code in the living documentation.

9. The system of claim 1 , wherein the computer processor is further configured to perform the step of: storing the living documentation is a collaboration board.

10. The system of claim 1 , wherein the computer processor is further configured to perform the step of: storing the living documentation immutably with application binaries.

11. A method for automated generation of software development life cycle audit documentation, the method comprising the steps of:
retrieving, via an input, one or more requirements from a business collaboration tool;
identifying, via a computer processor, one or more code changes relating to the one or more requirements from a source code repository to determine functional code that was changed for each requirement;
linking, via the computer processor, business budget and financial milestone data to the one or more requirements to document who approved an associated business investment;
accessing, via source code repository, code review information to ensure each code change was reviewed and approved by a team member;
accessing, via the computer processor, a test execution and results from a test management system;
linking, via the computer processor, the test execution and results to one or more functional requirements and non-functional requirements;
accessing, via the computer processor, non-functional tests from one or more systems of records;
linking, via the computer processor, the non-functional tests to one or more release and business requirements;
applying, via the computer processor, a template that describes a format of a living documentation that automatically links to a release cycle; and
generating, via the computer processor, the living documentation based on the template.

12. The method of claim 11 , wherein test code committed to the source code repository is linked back to ensure test code coverage is provided.

13. The method of claim 11 , wherein build information is linked from a build pipeline tool that shows each daily build, associated results and unit test results for each build.

14. The method of claim 11 , wherein the test execution and results relate to QA, UAT, integration and regression.

15. The method of claim 11 , wherein the non-functional tests comprise stress tests, load tests, performance tests and security tests.

16. The method of claim 11 , wherein the living documentation is a software development software development life cycle (SDLC) documentation.

17. The method of claim 11 , further comprising the step of: generating SDLC artifacts to satisfy risk and audit concerns.

18. The method of claim 11 , further comprising the step of: documenting application code in the living documentation.

19. The method of claim 11 , further comprising the step of: storing the living documentation is a collaboration board.

20. The method of claim 11 , further comprising the step of: storing the living documentation immutably with application binaries.

Assignees

• Jpmorgan Chase Bank Na

Inventors

• Alexander Shawn Wesley

Classifications

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/73 Primary

  Program documentation · CPC title

• G06F11/3684

  for test design, e.g. generating new test cases · CPC title

• G06F11/3688

  for test execution, e.g. scheduling of test suites · CPC title

• G06F8/74

  Reverse engineering; Extracting design information from source code · CPC title