Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

End-To-End Project Management Tool

IP.com Disclosure Number: IPCOM000016153D
Original Publication Date: 2002-Aug-05
Included in the Prior Art Database: 2003-Jun-21
Document File: 5 page(s) / 65K

Publishing Venue

IBM

Abstract

Disclosed is a design for an end-to-end project management tool initially intended for Lotus Notes* but adaptable to any framework. For software development companies who use Lotus Notes* as their base software for email, calendar, document archiving, etc, it is common that several databases are required to manage the various processes and documents which are associated with software projects. For example, databases typically involved include: Issues Feedback DB Strategy DB Planning DB Project Management DB Release Management DB Design Change Document DB Test DB Build Status DB Information Development DB Customer support DB Reference Document DB

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 5

End-To-End Project Management Tool

Disclosed is a design for an end-to-end project management tool initially intended for Lotus Notes* but adaptable to any framework.

For software development companies who use Lotus Notes* as their base software for email, calendar, document archiving, etc, it is common that several databases are required to manage the various processes and documents which are associated with software projects. For example, databases typically involved include:

Issues / Feedback DB Strategy DB Planning DB Project Management DB Release Management DB Design Change Document DB Test DB
Build Status DB Information Development DB Customer support DB Reference Document DB

Problems which occur besides the issue of managing several databases include:

Finding the various database Switching between databases when dealing with more than one process Cross referencing information from one DB to another Coherency from one DB to another

This invention involves the use of a Notes database to create a centralized end-to-end project management tool. By combining all the above process databases into one coherent project database which allows users to cross reference documents internally to the database and allows documents to evolve through reuse. For example, a feedback document can evolve to a requirement, which can then evolve to a Line Item, which will spawn Design Changes, which then spawn Test Plans, etc.

The following is a listing of suggested various FORMS, which could be used within a Notes project database, which:

Requirement / Line Item PCR (Plan Change Request) DCR (Design Change Request) Doc DCR (Document DCR) Testcase
Test Plan
Test Report
Test Tracker Scenario Testcase Scenario Status Report CPS Plan (Continued Programming Support) Build Plan

1

Page 2 of 5

Parts List SBR (Service Build Request) Dependency
Assumption
Risk
Release
Department
Component Sub Component ID Deliverable SRCR (Shared Resource Change Request) Project Plan Entry
Lesson Learned
Feedback
Vacation Plan
Vacation Day
Away Day
Event
News Article
Customer
Objective
Strategic Thru...