US5903897A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Software documentation release control system
Assignee: Alcatel USA Sourcing Inc
•
Filing: 1996-12-18
•
Granted: 1999-05-11
•
Expires: 2016-12-18
Abstract
Abstract A system and method (510) for software documentation process control includes the steps of receiving and storing check-in data related to documentation (540, 542, 544, 546, 550, 552) checked into a version control system (12). Subsequently, the documentation are associated with a specific version and release of a software product, and tags the documentation with a unique label indicative of the specific version and release of the software product. The documentation is stored in a project file directory (566) associated with the specific version and release of the software product.
Inventors
- 👤 David F. Carrier, III
- 👤 R. John K. Gillespie
- 👤 Janet Kwai Fun Lui
- 👤 Donald L. Weeks, Jr.
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-04 01:48
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/70; G06F8/71; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99943; Y10S707/99951; Y10S707/99952; Y10S707/99954
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
99 words
A software documentation process control system, comprising: a version control system operable to process at least one document and associated source module related to a predetermined version and release of a software product; and a document collector coupled to the version control system and adapted for associating the at least one document and associated source module with the predetermined version and release of the software product; a load builder operable to generate the predetermined version and release of the software product from selected documents and associated source modules identified with the predetermined version and release of the software product.
Claim 2
Dependent Claim
99 words
A software documentation process control system, comprising: a version control system operable to process at least one document and associated source module related to a predetermined version and release of a software product; and a document collector coupled to the version control system and adapted for associating the at least one document and associated source module with the predetermined version and release of the software product; a load builder operable to generate the predetermined version and release of the software product from selected documents and associated source modules identified with the predetermined version and release of the software product.
Claim 3
Dependent Claim
18 words
The system, as set forth in claim 1, wherein the at least one document comprises engineering specification documentation.
Claim 4
Dependent Claim
19 words
The system, as set forth in claim 1, wherein the at least one document comprises test cases and reports.
Claim 5
Dependent Claim
18 words
The system, as set forth in claim 1, wherein the at least one document comprises a standards checklist.
Claim 6
Dependent Claim
17 words
The system, as set forth in claim 1, wherein the at least one document comprises customer documentation.
Claim 7
Dependent Claim
17 words
The system, as set forth in claim 1, wherein the at least one document comprises project memoranda.
Claim 8
Dependent Claim
20 words
The system, as set forth in claim 1, wherein the at least one document comprises documents associated with load building.
Claim 9
Dependent Claim
26 words
The system, as set forth in claim 1, further comprising a project file document directory for storing the at least one document according to document classification.
Claim 10
Dependent Claim
31 words
The system, as set forth in claim 1, further comprising a project file document directory having a plurality of subdirectories for storing the at least one document according to document classification.
Claim 11
Dependent Claim
73 words
An automated method for document process control, comprising the steps of: receiving at least one document and associated source module; assigning a unique label indicative of a part number of a software product to the at least one document and the associated source module; and storing the at least one document in a predetermined project file document directory; building the software product from selected documents and associated source modules having the unique label.
Claim 12
Dependent Claim
73 words
An automated method for document process control, comprising the steps of: receiving at least one document and associated source module; assigning a unique label indicative of a part number of a software product to the at least one document and the associated source module; and storing the at least one document in a predetermined project file document directory; building the software product from selected documents and associated source modules having the unique label.
Claim 13
Dependent Claim
46 words
The automated method, as set forth in claim 10, further comprising the steps of: determining the type of the at least one document; and storing the at least one document into a subdirectory of the project file document directory in response to the determined document type.
Claim 14
Dependent Claim
34 words
The automated method, as set forth in claim 10, further comprising the step of: checking in the at least one document into a version control system; and generating check-in data associated with the document.
Claim 15
Dependent Claim
36 words
The automated method, as set forth in claim 10, further comprising the step of providing an interactive user interface for displaying information, prompting data entry by users, and receiving information associated with each of the steps.
Claim 16
Dependent Claim
29 words
The automated method, as set forth in claim 10, wherein the assigning step comprises the step of assigning a feature specification documentation number to the at least one document.
Claim 17
Dependent Claim
127 words
An automated method for software file release with documentation process control, comprising the steps of: receiving and storing check-in data related to source modules checked into a version control system; receiving and storing check-in data related to documentation checked into the version control system; associating the documentation with the source modules and a specific version and release of a software product; storing the documentation in a project file document directory associated with the specific version and release of the software product; and tagging the documentation with a unique label indicative of the specific version and release of the software product; building the specific version and release of the software product from documentation and associated source modules identified with the specific version and release of the software product.
Claim 18
Dependent Claim
127 words
An automated method for software file release with documentation process control, comprising the steps of: receiving and storing check-in data related to source modules checked into a version control system; receiving and storing check-in data related to documentation checked into the version control system; associating the documentation with the source modules and a specific version and release of a software product; storing the documentation in a project file document directory associated with the specific version and release of the software product; and tagging the documentation with a unique label indicative of the specific version and release of the software product; building the specific version and release of the software product from documentation and associated source modules identified with the specific version and release of the software product.
Claim 19
Dependent Claim
40 words
The automated method, as set forth in claim 15, further comprising the steps of: determining the type of the documentation; and storing the documentation into a subdirectory of a project file document directory in response to the determined document type.
Claim 20
Dependent Claim
36 words
The automated method, as set forth in claim 15, further comprising the step of providing an interactive user interface for displaying information, prompting data entry by users, and receiving information associated with each of the steps.
Claim 21
Dependent Claim
29 words
The automated method, as set forth in claim 15, wherein the tagging step comprises the step of assigning a feature specification documentation number to the at least one document.
References Cited (Backward Citations)
US4558413A
Cited
US4696003A
Cited
US4751635A
Cited
US4809170A
Cited
US4951192A
Cited
EP0323707A2
Cited
US4864569A
Cited
US4912637A
Cited
US5155847A
Cited
US5038316A
Cited
US5278979A
Cited
US5339435A
Cited
US5452206A
Cited
US5291598A
Cited
US5671415A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-05-10 | 2002-11-09 | 2003-05-11 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-05-10 | 2006-11-09 | 2007-05-11 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-05-10 | 2010-11-09 | 2011-05-11 | $7700.00 | Window Closed / Lapsed |