Right from the start, key project stakeholders typically have a vision of what the final solution will look like. Unfortunately, their visions often vary from person to person, conflict with each other, and were formed before analysis was done to determine what the business truly needs and what existing and/or new technology options are available. To resolve this conflict, a conceptual business solution should be developed, after sufficient analysis, to tell the story of how a proposed solution is likely to look. Reaching agreement on the conceptual business solution provides significant benefits to the project by:

• Showing how business and technology will come together to deliver the project’s intentions.
• Setting a baseline for all subsequent design decisions and detailing.
• Allowing the solution concept to be evaluated including cost benefit analysis and build vs. buy decisions.

• Bridging specific business needs and technical directions specified by the architects.
• Using business requirements to determine technology solutions.
• Using technology to optimize the business.
• Transforming business and technical requirements into a defensible concept.

Course Outcomes:
Students of this course will return to work with:

1. An understanding of how an optimal solution concept is developed from business requirements, organizational and technology directions, and marketplace opportunities.
   
2. An understanding of, and appreciation for, the difference between
   
   
   1. Business requirements and a business solution design.
      
   2. Design concepts and design decisions.
      
   3. Business design components and technical design components.
   
   
3. A framework for transforming business models/requirements into a conceptual design.
   
4. How to utilize component diagrams and deployment diagrams to illustrate and specify business solutions.

Course Outline:

From Analysis to Design What is a Conceptual Solution Design? Why is it Important? Analysis vs. Design vs. Realization 5 Threads of Business Requirements	Solution Design What is a “concept”? Design Disciplines: Architectural Design Engineering Design Detail Design Degrees of Specificity
Sub-disciplines of Architectural Design Conceptual Design Business Design Technical Design	Conceptual Design Considerations Inputs/Outputs Does Business Drive Technology or Does Technology Drive Business?
Two Main Approaches to Architecture Design Holistic Brute Force Pros, Cons and Fit	Communicating the Concept Deployment Diagrams Component Diagrams Other Instruments
Enterprise Options and System Solutions What to do when the choice of technology is yours. What to do when the application is the solution.	Balancing Designs Installed vs. New Opportunities Organizational Directions vs. Unique Project Needs Enterprise vs. Individual Needs Establishing Priorities
Next Steps Exercises From Concept to Reality Preparing Yourself Preparing Your Organization

Who Should Attend:
Systems Analysts, Business Analysts, Solution Architects, Project Managers, Technical Leads.

Course Duration:
Two Days

Class Availability: Request It Now!