Issue 4683: Section 9.2 /Example                                                                                                                                                                                    (spem-ftf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde@orange-ftgroup.com)
Nature: Uncategorized Issue
Severity: 
Summary: Inputs and Outputs for processes are undefined (in contrast with inputs
and output for
  activities which are defined in 8.2)
Resolution: Accept.
Revised Text: Modify the text for 8.2 Example.
"Composition of ProcessComponents is done by a process of unification.  For example, consider both of these:
·	a ProcessComponent P1 containing WorkDefinitions that take a set of high-level use cases and non-functional requirements as input and deliver an architecture as output.
·	a ProcessComponent P2 containing WorkDefinitions that take an architecture and a set of detailed use cases as input, and deliver an executable, unit-tested body of code as output.
To combine these two components, <remainder of text unchanged>"

Actions taken:
November 7, 2001: received issue
October 23, 2002: closed issue
Discussion: 

End of Annotations:=====
From: BELAUNDE Mariano FTRD/DTL/LAN
       <mariano.belaunde@rd.francetelecom.com>
To: spem-ftf@omg.org
Subject: Issues to the SPEM document
Date: Wed, 7 Nov 2001 12:43:16 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: Nnl!!iMLe9;"'!!~>;!!

Hi all,

You will find below a list of issues regarding the current version of
the SPEM specification.

Regards,
Mariano Belaunde
France Telecom R&D
------------------------------------------------------


 Section 9.2 /Example
  Inputs and Outputs for processes are undefined (in contrast with
  inputs
and output for
  activities which are defined in 8.2)