Service-Oriented Analysis
COURSE DESCRIPTION:
Service-Orientation holds the promise of delivering on the hope of every business: a software foundation that is immediately adaptable to changes in business model and business needs. Adopting a service-oriented architecture enables the technical infrastructure, but that is really the easier part. The greater challenge is identifying those business services to be supported with that infrastructure. This course is devoted to practical techniques for identifying and describing the right business services to be implemented within a service-oriented architecture.
This course focuses on how an organization moving to Service Orientation can identify effective business Services. Exercises in each section of the course demonstrate techniques to identify candidate services, then organize them to achieve real business goals. The various types of services are discussed, and emphasis is placed on identifying the responsibility profile of each service - a proven technique to eliminate duplication of functionality. Further exercises demonstrate how to define the interactions and operations of each service to assure it meets its prescribed business goals.
TOPICS COVERED:
At the end of this course, students will be able to:
- Explain the concepts of Service-Orientation, and the goals of SO-Analysis
- Follow a practical process for identifying business services
- Gather requirements to construct candidate services
- Organize candidate services to produce a service granularity hierarchy
- Characterize & document services effectively for use, and reuse
- Understand how to integrate these service into the larger business framework
AUDIENCE:
This course is designed for business analysts, systems analysts, requirements analysts, technical managers, and software developers who wish to learn techniques for successful business analysis in software development.
DURATION:
2 days (private, on-site presentation only)
PRICE:
Please call (866) 426-6871 for pricing details
PREREQUISITES:
None. Experience in software project management, business or systems analysis, or requirements gathering is desirable, but not mandatory.