STD_DBs Date Status Draft for discussion ISO concept database

Document Sample
STD_DBs Date Status Draft for discussion ISO concept database Powered By Docstoc
					STD_DBs N56
Date: 2008-04-05 Status: Draft for discussion

ISO concept database - Common features
The ISO concept database will contain a wide variety of objects from different subject fields of ISO's technical work, which comprise both items under development as well as standardized or "released" items. The subject fields are represented in document STD_DBs N55 by the following five committee clusters: - Cluster A: Terminology - Cluster B: Graphical symbols - Cluster C: Product properties - Cluster D: Codes and coding systems - Cluster E: Other fields There are commonalities inside each cluster as well as across different clusters. However, there are also specific features both inside and between the clusters. In the following section a number of key features of the concept database are listed for review and discussion which are assumed to be common across the clusters. Document STD_DBs N57 contains a questionnaire to determine specific features for each cluster as perceived by the committee representatives in the Standards as database-group. 1. Management of the development process

The ISO development process is traditionally organized in a projects, which are managed in a decentralized manner by committee secretaries, their assistants, working group convenors and project leaders. Individuals in these roles are referred to below collectively as project managers. The technical or subject contributions to the work come from the representatives inside the various groups, i.e. members of working group, project teams, task forces and, at a later stage, by the representatives of the ISO member bodies. In addition to the decentralized management of projects, there is a centralized monitoring organized by the ISO Central Secretariat, based on a set of time frames, which then trigger notifications and alerts to the project mangers in case projects exceed certain deadlines. Individuals in these roles are referred to below collectively as project monitors. Principal approach: 1. The secretary of the committee is responsible as the project manager. However, the secretary can delegate the responsibility to other individuals (assistants or others) who perform then the role of project managers. 2. The individual(s) in the role of project manager(s) can change over the course of a project. E.g. a project leader can be assigned as project manager at the beginning of the project. Later on the secretary or an assistant to the secretary can take over as project manager. The responsibility of the project leader would then no longer comprise the function of process management, but may still be the key technical contact point for the project. 2. Role-based accessibility to the content in the concept database

Access to the database content must first distinguish between items under development ("not yet standardized") and items which have been released ("standardized"). A second criterion is that a distinction must be made between the role of the users accessing the database.

rwe/C:\Standards as databases\00_Meeting_2008_04_14_15\STD_DBs_N56_CDB_Common features.doc

Page 2 For more details see the definition of the four access layers in STD_DBs N53. A distinction is to be made between the following key roles (the list of roles is non-exhaustive) Key roles (unregistered) member of the public Principal permissions Access to content available for public access (access to public information layer 1, for terminology access to layer 1 and 2) without the need to register Read access to the whole database Read access to the whole database Read access to the whole database + Write access to the particular project + Permission to manage the process (i.e. change the stage codes for the project or work packages inside the project) Read access to the whole database + Write access to the particular project Read access to the whole database Read access to the whole database + Download access to a particular sub-area Read access to the whole database + Access to the balloting application and items subject to ballot Read access to the whole database + Write access to the particular project(s)

(registered) secretary/chair of any committee or working group (registered) member of any committee or working group (incl. liaisons) (registered) project leader (project manager)

(registered) participant in a particular project (registered) member of an ISO member organization (registered) customer or subscriber (registered) balloter (in a Validation Team or as a member body balloter) (registered) ISO/CS staff (Technical Programme Manager and Technical Editor) 3.

Drafting, commenting and balloting features

There shall be features for the drafting by the project team members as well as possibilities for commenting by other project team members on proposals made. Reviews by Maintenance Teams shall be supported by commenting features. Balloting shall be done at any stage required (see the development and maintenance procedure in STD_DBs N57) by - the Validation Team (for the Normal Database Procedure) - Committee balloters (for the Extended Database Procedure) - DIS/FDIS balloters (for the Extended Database Procedure) 4. Features for version control

Replaced or withdrawn items shall be kept in the database with the respective status identifier as well as a reference to the replacing item(s). 5. Search

The following search criteria shall be supported (and combination between them): - "Standardized" / "Under development" - Types of objects (Terminology, graphical symbols, product properties etc.)

rwe/C:\Standards as databases\00_Meeting_2008_04_14_15\STD_DBs_N56_CDB_Common features.doc

Page 3 - ICS - Committee reference - Standards reference number - Stage codes or range of stage codes - Dates or date ranges when current stage was reached - Designation (including with abbreviations) - Full text throughout the content of the record - By change request - By work package 6. Email notifications

Users in all roles (see the list of key users under 2.) shall have the possibility to subscribe to email notifications for the whole are certain sub-sections of the CDB requesting information about changes to the database content. Depending on the roles of the users, the layers of access are different, which results in different notifications being sent (e.g. an unregistered member of the public has no access to re-usable graphic files for symbols. In case a new graphic file is added, no notification would be sent, whereas a customer or committee member would be notified). The notifications need to be specified for each role. It shall also be possible to opt out from receiving notifications. 7. Up- and download of database content

It shall be possible to upload content which is developed outside the ISO/CDB (e.g. extracted from Word-files, provided from external databases) into the CDB. It shall also be possible to extract content from the ISO/CDB by registered customers to be used in customer applications are to other databases in which segments of the content of the ISO/CDB will be made available (possibly together with other content). 8. Reporting and monitoring features

There shall be reporting and monitoring features to control the status of work by - work packages - stages - time frames - committees 9. Other features

To be discussed.

rwe/C:\Standards as databases\00_Meeting_2008_04_14_15\STD_DBs_N56_CDB_Common features.doc


				
DOCUMENT INFO
Shared By:
Stats:
views:15
posted:2/11/2009
language:English
pages:3