IEEE P1016 Working Group: 18 November 2001 Meeting Agenda

November 18, 2001

9-11 AM EST Review Project Plan and Programmatic (Basil)

Project Plan and PAR have been submitted to SESC. Review plan and discuss work to be done in terms of options and ideas (All). Come to some preliminary closure on a detailed WBS, Scope, Success Criteria, Expectations.

11-1 PM EST Review Base Documents (Video is connected) [not to include Z, VDL, UML, IDEF stds] only IEEE stuff!

Begin review of base documents and determine directions for their use [and treatment for Annexes], harmonization with 830 & 12207.0 life cycle (Dr J) other positions welcomed.

Lunch 1-3 PM EST

3-5 PM EST Review Base Documents (Video is connected)

Review of base documents and determine directions for their use [and treatment for Annexes], harmonization with 1016.1 and SWEBOOK (Basil); 1471 (Rich); 1012 (Judy) other positions welcomed.

For reference: here's the outline proposed in the project plan.

1. Scope
2. References
3. Definitions
4. Considerations for producing an SDD
4.1 Software life cycle
4.2 SDD within the life cycle
4.3 Purpose of an SDD
5. Design description information content (normative)
5.1 Introduction
5.2 Design entities
5.3 Design entity attributes
6. Design description organization (normative)
6.1 Introduction
6.2 Design views
6.3 Design viewpoints
Annex A (Informative) Use of IEEE 1302.1 Functional Modeling Language in an SDD
Annex B (Informative) Use of IEEE 1302.2 Conceptual Modeling Language in an SDD
Annex C (Informative) Use of the Unified Modeling Language in an SDD
Annex D (Informative) Use of ISO Z in an SDD
Annex E (Informative) Use of the ISO Vienna Definition Language in an SDD

*The "mock up" DRAFT version 0.0 with this outline and material from 1016-1998 is available from Rich.

For example prepare to discuss your ideas and things like:

  • mandate standards in SDD, only notations/languages with formally defined semantics,
  • completeness criteria for SDD set [design representation as a whole] to include: minimal set of 'well' defined views, tractability to requirements and tests incl. evaluations for non-functional requirements, required self description of contextual expectations for design 'components' and explicit design requirements for product measurements and evaluation oriented elements in the design for self-tests, probes etc.

5-7 PM EST Thrust of Revision (Video is connected)

Argue main thrust of changes to 1016, we all bring the (pieces for) 1 or 2 pages [Word .doc files] for the 0.1 draft [0.0 is the base P1016 from current 1016]* to the meeting, and laptops.

Editing of the 0.1 partial draft into 0.2 complete [very preliminary] draft.

7-9 PM (Video is connected)

Review of a 0.2 draft and action items, assignment of draft 0.2 elements to produce draft 0.3 and 0.4 [monthly] and 0.5 [the first out for external review, out in March 2002]; WBS elements to individuals and also other work. [Basil to lead this part].