Computer-aided project notebook

• US 6,161,113 A
• Filed: 01/20/1998
• Issued: 12/12/2000
• Est. Priority Date: 01/21/1997
• Status: Expired due to Term

• Current Assignee: Texas Instruments, Inc.
• Original Assignee: Texas Instruments, Inc.
• Inventors: Mora, Pamela S., Barlow, Bruce E., Beede, Bruce R., Kennett, Jackie R., Limerick, Sydney R.
• Primary Examiner(s): Alam, Hosain T.
• Assistant Examiner(s): Kindred, Alford W.
• Application Number:
  US09/009,166
• Time in Patent Office: 1,057 Days
• Field of Search: 707/505, 707/506-508, 707/513, 707/500, 707/515, 707/526, 345/335, 345/329, 345/330, 345/331, 345/332, 345/217, 345/204-205, 345/218-220, 345/231, 345/201, 709/217, 709/200, 709/203, 709/204-205, 709/218-220, 709/231, 709/201
• US Class Current: 715/234
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method of providing a computer-aided project notebook for use on a computer system programmed with collaboration software (11). A database (11b) stores forms for documents comprising the notebook. The forms are categorized into views, such as a methodology view that sorts documents by status (FIG. 3). Methodology documents have status fields, into which a user may enter status data. After status data is entered, the document will appear in the correct view (FIG. 5). Other features of the notebook are document interconnectivity, shared fields, trace maps, and document access especially designed for project development.

Claims

1. A method of providing a computer-aided project notebook for software development, for use with collaboration software, comprising the steps of:

creating a management document database and a technical document database, said management document database and technical document database storing pre-composed forms for documents to be completed by one or more users, said databases comply with software development methodology and provide a sequential outline for the software project documentation, each of said forms having a view field that identifies a view for that form and a selection criteria field that identifies selection criteria for the view associated with that form;

wherein at least one said view is a software development methodology view having document status selection criteria, and wherein one or more of said forms has a status field operable to receive document status data from said user; and

providing programming for said collaboration software, said programming operable to automatically update said status field in response to said document status data.

2. The method of claim 1, further comprising the step of providing user-composed forms to be retrieved from said database in response to a selection by said user from compose menu.

3. The method of claim 2, wherein user-composed forms and said pre-composed forms have a many-to-one relationship.

4. The method of claim 2, wherein each said user-composed form has said view field and selection criteria field.

5. The method of claim 1, wherein at least one of said forms has a section accessible only if an associated formula is satisfied said formula operable to determine whether said user has a certain project role.

6. The method of claim 1, further comprising the step of providing programming for a display that prompts a user to enter a request for signatures for a document and that generates a signature request document in response to said request for approval.

7. The method of claim 1, further comprising the step of providing programming operable to create a new version of an existing document.

8. The method of claim 1, further comprising the step of providing programming for automatically accessing a first of said forms from a second of said forms.

9. The method of claim 8 wherein said second of said forms contains project member data.

10. The method of claim 8 wherein said first of said forms is a form to be approved and said second of said forms is a request for approval form.

11. The method of claim 10 wherein one of said forms is a change request form having a change request view and further comprising the step of providing programming for converting said change request form to a requirements form having a requirements view.

12. The method of claim 1, wherein at least one of said forms is a preliminary requirements form and another of said forms is a detailed requirement form, and wherein one of said views is a trace map view, and further comprising the step of providing programming that displays a requirements trace map in response to said user having selected said trace map view.

13. The method of claim 1, wherein said management database methodology documents include statement of work, authorization to proceed documents at various stages of the project, an approach document, a software project plan, software quality assurance plan, a software configuration management plan, test report, periodic review and prototype planning.

14. The method of claim 1, wherein said technical database methodology document includes a test plan, a training analysis document, a requirement review, a preliminary design review, a software design document, an installation and support plan, a training design document, user documentation, a critical design review, system test procedures, test readiness review, production readiness review, post-installation review and prototype results.

15. The method of claim 1, wherein said status selection criteria includes in-work and pending approval.