[an error occurred while processing this directive]
You are here:  Home > Events > Enterprise Architecture Practitioners Conference San Diego
  Jason Uppal - Chief Architect, QRS, Canada    

photoJason Uppal, P.Eng. is a chief architect of QRS (Canada) and is a Certified Master IT Architect by The Open Group. He holds an undergraduate degree in Mechanical Engineering, graduate degree in Economics and a post graduate diploma in Computer Science.

Currently, Jason is the lead architect for ITO Software Solution, a community based software solution that provide business processes automation to industrialize – enterprise architecture, portfolio management, program and project management and IT service management (key ITIL functions) practices. For more information on ITO solution: visit ITO community web site www.itoProcesses.com.

For further discussion on this topics, Jason can be reached at jason.uppal@quickresponse.ca



Making the Business Case for Enterprise Architecture

In most large organizations the role of Enterprise Architect (EA) is now generally understood. However, the exact RESPONSIBILITIES of the EA are subject of much debate. This debate, in part, stems from the fact that many CIO’s and IT leadership have not accepted the fact that Business Architecture is a necessary component of Enterprise Architecture practice. Without the inclusion of Business Architecture, Enterprise Architecture Practice will never be able to construct a tangible business case and as such will continue to be a backroom activity within IT Organization.

In this session, I will outline the RESPONSIBILITY (RACI Model) of the Enterprise Architect and describe a pragmatic business case that can be supported both by the CIO and the CFO.

What will you learn?

  • RESPONSIBILITY of an Enterprise Architect
  • Dimensions of a Business Case
  • Business Case Drivers
  • a Sample Business Case


In software development circles Rational Unified Process (RUP) is a reasonably well understood framework and methodology. Frequently RUP practitioners, a breeding ground for future Enterprise Architects, fail to make a distinction between the scope of TOGAF ADM and the scope of RUP. As a result, they create a considerable amount of churn, duplication and "religious debate" within the ranks of IT professionals, only to deliver sub optimal solutions to the enterprise.

In this session, I will outline an example problem statement – IT Asset Management, and apply TOGAF ADM to define Enterprise Architecture and RUP to define Software Solution. Attendees will receive a working sample of TOGAF ADM artifacts that will outline an architecture vision and architecture roadmap for a typical IT Asset Management Solution and identify the touch-point between TOGAF ADM and RUP.

Pre-requisite: some working knowledge of TOGAF ADM and RUP is required.

return to program


   |   Legal Notices & Terms of Use   |   Privacy Statement   |   Top of Page   Return to Top of Page