|
Transforming business process requirements into robust, high-level system designs involves three distinct design activities: - Designing Conceptual Business Solutions - determining how major business and technology components will deliver on the project’s intentions.
- Designing Business Use Cases – identifying the business transactions required to deliver the specified, to-be functionality.
- Designing Technical Use Cases – transforming the business use cases into high-quality system transaction specifications.
This course emphasizes the third step in this process, designing the technical use cases. It examines what’s needed to accept and interpret a set of business use cases and apply appropriate technology to create a specification of the to-be system that:- Delivers the required business functionality.
- Is rigorous, unambiguous, and workable by the developers.
- Provides for flexible solutions with re-useable potential.
- Includes a complete set of transactions for development.
Course Outcomes:
Students of this course will return to work:
- Articulating the value of formal, robust system design to the success of the organization.
- Understanding the differences between business use cases and technical use cases.
- With a framework for transforming business use cases into technical use cases and completing the design.
Course Outline:
Foundations
- Design
- System Transactions
- Business Use Cases
- Technical Use Cases
- Quality
- Workability
|
Technical Use Cases & Components
- Use Case Diagrams
- Use Case Scenarios
- Flowcharts and Other Instruments
- SOA Implications and Identifying Services
|
Design Solution Transactions
- Understanding the Conceptual Business Solution Architecture
- What to do if there is “no conceptual architecture”
- Interpreting the Business Use Cases
|
Designing System Transactions
- Applying Technical Mechanisms to the Business Transactions
- Developing Architectural-level Technical Use Cases
|
Taking it Forward
- Process vs. Other Threads
- Detailing the Design
- Designing User-system Interactions
- Developing other Logic Design Instruments (e.g. flow charts, activity diagrams, etc.)
|
Recapping the Role of Technical Designer
- What is my job?
- Why is it valuable?
- Preparing myself
- Preparing the organization
|
Who Should Attend:
Systems Analysts, Developers, Technical Leads, Solution Architects or anyone responsible for accepting business requirements and designing technology to support workflow.
Course Duration:
Two Days
Class Availability:
Request It Now!
|
