Understand what you do so you can do it better
Presenter – Tim Rayburn (Sogeti)
- What is SOA? (Service Oriented _________)
- Approach
- Architecture
- Application
- Analysis
- Agreement
- Going to an SOA should NOT be changing how you do what you do
- SOA is philosophy, not product
- Aligning business with IT is the goal
- It is EVOLUTION, not Revolution
- Mapping Your Business
- Business should have an idea as to what their process is, preferably a process map
- Draw out what you want done including the weird scenarios
- Define what your organization does, and what your organization does only to get a certain job done (i.e. email is not what your business does, it’s something your business does to get your job done)
- SOA leads to Agility, rapid response to change
- Where to Start? Choose wisely!
- Choose the right people to work with (not perfectionist, good enough is good enough)
- Types of Services
- Composite Services
- Packaged Application Services
- Custom Application Services
- Infrastructure Services
- Not a singular task, but a sequence of tasks that get something done
- Users don’t care about what happens on the back end, as long as the front end stays the same.
- Given the right input, we can make a service work, regardless of back end technology
- Infrastructure Services are NOT the goal, they are the tools to get the job done
- How to Think about Services
- Services are a black box, you get to care about inputs and outputs, but not about how it does the work
- Services are not always answered by computational algorithms
- Services aren’t always computers/machines, services can include human powered tasks, but must apply the same rules of input/output only
- Services can be departments where work is queued for a human
- Obviously these should be asynchronous