Skip to content

You are not logged in. Register orLog In

start:

Entry Checklist Software Specification Process

Owner:
Joerg Sievers

Last Change:
Friday, February 10, 2006

Status:
Standard

Goal of this document:
 Help to check if all necessary pre-requisites for starting the specification process are fulfilled avoiding wasting resources and failures in the specification process.

Intended readership:
 Specification authors, specification reviewers (Development , Quality Assurance , User Experience, Documentation)

Send Feedback to:
dev@specs.openoffice.org

Can you answere each of the following questions [Q] with 'Yes'? If not why not? The consequence could be that your valuable work won't be integrated into OpenOffice.org.

Q1 [Requirement]:

Does a requirement, request for enhancement (RFE), or issue exist?

Q2 [Concept]:

Is a product concept available, which is understandable to the intended readership?

Q3 [Project-Resources]:

Do you have a project team?

An OpenOffice.org feature is always being devoleped by an Implementation Team (i-Team). An i-Team consists at least of two distinct persons:

  • A developer (required)
  • A quality assurance member (required)
  • An user experience member (optinonal, in case the feature affects the user interface)

Q4 [Implementation Team Agreement]:

Do all project members agree on Q1 - Q3?

Document History

Revision

Change

Initials

Date

1

Ownership changed to JSI; Goal statement changed

JSI

Sep 22, 2005

2

Result from the inspection review into the document;
C5 removed; Visioning now matches to CMS and new format

JSI

Sep 23, 2005

3

Header changed, Status changed for approving document.

JSI

Oct 10, 2005

4

C1 sentence corrected with better wording.

JSI

Oct 12, 2005

5

Rules revised for OpenOffice.org usage

CJ

Dec 16, 2005
6
 Converted to HTML CJ Dec 22, 2005
7
 Reviewed by CJ/TRA CJ/TRA Dec 28, 2005
8
 Revised by TRA, JSI, CJ; based on OO.o feedback CJ Jan 27, 2006