Revision of 12017 design from Wed, 2008-05-14 02:16

Design for 12017


Design for item

What user need will be met by this feature?

 

Try to include information about what the user wants to accomplish, rather than technical details of how it will be accomplished.

What is the technical design for the change?

Describe enough that developers can understand what changes will be made. If the design is extensive, it may be best to store it in another wiki page.

What sections of the toolkit will be impacted by the change?

This may include program names or sections that users interact with. This information should help in developing functional test cases (as opposed to existing regression test cases).

See also

Link to any external design information, such as a specification document from OASIS or an RFE submitted at SourceForge

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I