Service Oriented Design I Introduction

1
Service Oriented Design I Introduction

• 605.702 Service Oriented ArchitectureJohns-Hopkin
  s University
• Montgomery County Center, Spring 2009
• Lecture 10 April 8, 2009
• Instructor T. Pole

2
Agenda

• One (Last) Schedule Change
• No class next week, no class on 4/15/09
• Two classes following week on 4/20/09 and 4/22/09
• Regular class week after next on 4/29/09
• Final Exam and Projects due 5/6/09
• Required Reading for This Week
• Chapter 13 Service Oriented Design Part I
  Introduction
• Chapter 14 Service Oriented Design Part II SOA
  Composition Guidelines
• Class Project
• Assigning to Teams
• SEAM Project
• Deliverables set 2 2-01, 2-03, 2-03
• ITInc Program Tracking (IPT) Example Project
• ITInc Requirements Statement
• ITInc Customer Meeting
• Requirements Analysis
• Review Mid Term Exam
• Review Exercise 4b

3
CH 13 Service Oriented Design I Introduction

• Chapter 14
• Compose SOA
• Chapter 15
• Design entity-centric business services
• Design application services
• Design task-centric business services
• Other topics
• Application defined user types XSD
• WSDL Service interfaces

4
Ch 14 Service Oriented Design II SOA Composition
Guidelines

• Choose Service Layers
• Position Core Standards
• XML and SOA
• WSDL and SOA
• SOAP and SOA
• UDDI and SOA
• Choose SOA Extensions
• WS- extensions

5
Class Project Assigning Teams

• Take 10 minutes to discuss among yourselves how
  you might form teams
• At least two, no more then four members per team
• Yellow Team
• Blue Team
• Green Team
• Each Team will submit one set of software
• The team will build the software together
• Each member of each team will submit one report
• The team will design the SOA together
• Each member of the team will write their own
  report

6
XYZ Software SEAM Related Business Processes

• Engineers search SEAM for assets to reuse
• Engineers access assets via SEAM
• Engineer submits new assets to SEAM
• Project registers with SEAM
• This enables them to access SEAM for reuse
  existing assets, and submit new assets
• This is required to gather reuse metrics per
  project
• SEAM admins update asset
• Which notifies registered asset users

7
Scenario 1 Engineers Searches for Assets

• Service must have operation(s) that identifies
  what metadata fields are available to define a
  query with, and what values are valid for each
  field
• Service must have operation(s) that accepts a
  query and creates a list of matching assets

8
Scenario 2 Engineers Access Assets

• Service must have operation(s) that accept the
  identification of specific assets, and returns
  them to requestor

9
Scenario 3 Engineer Submits new Assets

• Service must have operation(s) that permit
  requestor to supply asset and related metadata
  for submission to SEAMS

10
Scenario 4 Project Registers with SEAMSys

• Service must have operation(s) that allow user to
  inform repository that there is a new valid value
  for the metadata field which records project that
  asset originated from.

11
Scenario 5 System Admin Updates Asset

• Service must have operation(s) that permit end
  user to change the content of an asset, and
  change the values for an assets metadata fields.

12
Class Project Deliverables Set 2

• Deliverable 2-01
• Final Architecture
• Deliverable 2-02
• Final Services and Operations List
• Deliverable 2-03
• Map Each Process to SOA Diagram
• You will create five of these

13
Deliverables Check List
14
ITInc ITP Example Project

• ITInc Requirements
• ITInc Customer Meeting
• Requirements Analysis
• Business Process Modelling
• ITInc Deliverables Set 1
• ITInc Deliverables Set 2
• White Board Exercise

15
Review Mid Term Exam

• Correct answers to questions
• Scoring guidelines

16
Exercise 4a Review

• What 4a must do
• What youve learned from 4a that you must apply
  to the class project