The e-Framework in Agile Development Projects

Please contribute, edit and add comments to this document.

• Use to proposed architecture

• rough collection of Service Genres

• SUM with Service Genres

• show to the customer???

• could use to come up with the stake (base SUM) to drive through the architecture

• Use to collect user stories

• SUM Usage Scenarios

• Functionality contains business processes

• make user stories testable (possibly convert to use cases) - not sure how this fits into the SUM

• Develop services with eF WS Profile? or Guidelines? in mind

• Construct Service Expression to specify the interface

• Note: Agile might be the reverse of the FRED/CORDRA usage, which is to document a well developed specification first as Service Expression, then code to the Service Expression.