L9 - April 5, 2006copyright Thomas Pole , all rights reserved 1 Lecture 9: Reuse Driven Processes and Text Ch. 7: Programming with Models

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 2 Agenda Lecture: Reuse Driven Processes Lab: Basic Web Services Text: Chapter 8: “Programming with Models” Class Project –Review: Project Assignment #1 –Project’s Process –Project Assignment #2: Domain Definition and Discerning Family Members Q&A

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 3 Lecture: Reuse Driven Processes A reuse driven SDLC process performs all of the standard SDLC tasks, goals, work products, and….. –Supports the discovery of reusable software assets, as early in the life cycle as possible. –Supports the discovery, capture or harvesting, and management of reusable assets.

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 4 Traditional SDLC User/Customer Req. Analyst Problem Statement Req. Statement Design Architect Implementor Design Validated Product Tester

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 5 Reuse Driven SDLC User/Customer Req. Analyst Problem Statement Req. Statement Design Architect Implementor Design Validated Product Tester Asset Management System Traceability DSL Req. Assets Req. Specs Design Assets Design Specs Imp. Assets Req. Specs. Test Assets Dev. Team New Assets

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 6 Reuse Driven SDLC - Process Req. Analyst works with Customer, uses DSL to match user’s needs to available reusable assets. Uses both reusable req. statement assets, as well as newly defines reqs. To produce req. statement. Architect starts with req. statement, uses req’s tagged as reusable to locate reusable design assets, searches for other assets while completing Design. Implementor uses design including design features tagged as reusable to locate reusable imp. Assets, use design features to look for other reusable imp. assets, produce complete implementation. Tester uses REQUIREMENTS tagged as reusable to locate reusable test assets. Whole team identifies new assets that are reusable, as well as new requirements that could result in reusable assets.

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 7 Reuse Driven SDLC Needs DSL Specific Language (multiple dialects) –DSL in Requirements mode Understandable to both req. analyst and customer/user. Transform problem model to requirements model –DSL in Design mode Transform requirements model to design model Crosse the divide between problem space and solution space –DSL in Implementation Mode Transform design into implementation Must represent variations in engineering concepts as well as application concepts (algorithms, structures, protocols, etc.)

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 8 Lab: Basic Web Services The Need: A Packaging Mechanism, and the Solution: SOAP/Web Services –Must support variability. Unfortunately, SOAP only supports tailoring and parameterization, but some IDE’s add inheritance and/or generics –Must support DIAE delivery SOAP supports excellent DIAE’s loose coupling goals.

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 9 SOAP Simple Object Access Protocol Capture a programmatic interface using an XML variant, called SOAP. –Uses a subset of XML –Also adds to XML to represent behavior –Definition is still evolving, adding: Transaction processing Security

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 10 Break 15 minutes Next: –Ch 6: Models and Patterns –Class Project –Exercise #2 review –Questions?

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 11 CH 7: Programming with Models Pages 231 – 264 Pages 265 – 277 will be combined with Chapter 8 next week. Automating Factoring and Modeling Aspects are outside the context of this class. We will cover Pattern Engines, but not use oone in the project.

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 12 Class Project Produce a reuse driven software development infrastructure: –Schedule (approximate) Domain Definition – week #1 Process definition – week #2 Generic Design - week #3 Reusable Assets - week #4 Final Exam & Team Work Session - week #5 Project Presentations - week #6

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 13 Class Project: Domain Definition From your inputs:

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 14 Class Project: Assignment #2 Process Definition: What will our process be for: –Comparing new system requirements to existing assets. –Tracing requirement specs to design assets to implementation assets. –Capturing from a recently completed system development effort new reusable assets, and opportunities for new reusable assets. Short paragraph description of each by 9:00 PM next Monday the 10 th of April.

L9 - April 5, 2006copyright Thomas Pole , all rights reserved 15 Questions? For next week: –Read the text through chapter 8, “Language Anatomy” for next week. – me your …… then 9:00 PM Monday April 10, 2006.