Integrated Use of Rational Unified Process, Unified Modeling Language, Zachman Framework, The Open Group Architecture Framework (TOGAF)
» Register here
Deadline: September 21, 2009, 11:59PM EDT
Date: Saturday, September 26, 2009
Time: 9:30 AM; Duration – 3 hours
Attend onsite: 245 Church St. (Ryerson University), Toronto
Attend online: Web conferencing option available
Conference Attendees: Free (requires registration ID number)
IEEE and/or PMI members: $55 (Canadian)
All others: $75 (Canadian)
Who should attend
Vitalie Temnenco is an enterprise / solutions architect and methodology consultant with a versatile background and extensive projects portfolio. He currently provides architectural mentoring on several implementation projects (the latest being Taxpayer Portal for Ontario) and helps project managers and teams embrace RUP and the Enterprise Architecture concepts. His experience includes architecting and building solutions for clients in a variety of business domains, such as banking, finance, insurance, retail, and telecommunications. In this role, he teaches clients to effectively use UML and RUP for business and systems analysis as well as in construction of new systems. In his spare time, he writes about rare, non-standard, and innovative applications of methodologies, frameworks, and technologies.
PDU's Earned: Attendees will receive 3 PDU's!
This tutorial is brought to you with a gracious support of the HiTech Institute Project Management Institute Registered Education Provider (R.E.P.)
Looking for answers, project managers (PMs) typically bounce from architects to developers, from developers to testers, and so on. Often empowered by Project Management Professional (PMP) knowledge and certification, PMs find themselves increasingly dependant on domain-specific expertise. They often find that the IBM® Rational® Unified Process®, or RUP®, is the framework chosen by their implementation teams, so they must adjust and rethink what they know according to RUP disciplines.
In the modern, IT-driven enterprise Project Management as a discipline found itself increasingly entangled with the enterprise and system architecture and process subjects. During this session the speaker will explore common misconceptions about RUP as a project management tool, discuss how the Project Management Body of Knowledge (PMBOK) standard intersects with RUP methodology, and explain ways to reduce or eliminate the ambiguity often misperceived to exist when relating these two complementary process frameworks. Finally, it will posit and explores the potential value of an enterprise PM role.
By virtue of the author’s experience as an Enterprise Architect, this session will provide a glimpse into the architectural perspective on project management. Project Managers will benefit by learning practical insights into RUP and IT architecture. IT architects will benefit by better understanding project managers' expectations.
Over the past decade, the advantages of using the Unified Modeling Language (UML) for modeling software applications have become clear. During this same timeframe, the Rational Unified Process, or RUP, has proved itself as a software development process, and the Zachman Framework1 has proved itself as a framework for organizing and communicating architectural artefacts. Amid the swarm of overlapping methodologies, these stand apart as three pillars of modern information systems architecture. As leaders in their respective disciplines, UML, RUP, and the Zachman Framework can be used together in any organization to deliver better overall architectural value.
Both RUP and Zachman are model-driven and require a notation to function. Since RUP dictates UML as a notation, it probably makes sense to standardize on UML for enterprise architecture as well. Despite the fact that both RUP and Zachman rely on models, they have virtually no functional overlap. Since both RUP and Zachman can depend on UML, the latter is the preferred methodology of the three to introduce first. Applying RUP to Zachman or vice versa makes for a better overall learning experience. Using Zachman to classify available artefacts, or even just referencing the Zachman structure and principles, makes RUP tailoring easier as it provokes thinking about roles, artefacts, workflows, and activities essential to a development organization. Project planning efforts also benefit from applying Zachman, as it can quickly lead you to artefacts that can be used during requirements gathering or analysis/design. Even when there are no artefacts linked to Zachman available, the Zachman structure itself is still very helpful because it provides various useful perspectives on the business problems a project addresses.
During this session we will consider some combined usages of these technologies by examining their meta-characteristics and discussing practical ways of applying them in combination within the organization.
When provided with a problem statement or pointed to a specific user need, a project team equipped with the IBM Rational Unified Process® (RUP®) approaches a solution by creating a Business Case, a Vision statement, and a Software Requirements Specification among other artefacts. These work products and the activities that produce them are well understood within both the technical and business communities. However, the ways in which we conceptualize, prioritize, and select which business problems and user needs to implement in software remains a highly variable process throughout our industry.
In terms of their scope, there is a certain amount of overlap between enterprise, solution, and business architectural frameworks as they are commonly understood. So, how do they relate?
During this session we explore the maturing and increasingly important role of enterprise architecture (EA) frameworks for today's software development organizations. The presenter will begin by contrasting the discipline of enterprise architecture with the solution architecture and business architecture disciplines, while relating them to RUP. Then he will discuss how The Open Group Architecture Framework (TOGAF) advantageously expands the boundaries for enterprise architecture set by RUP to include enterprise business and IT planning, implementation governance, and other activities. Finally, he will tackle ways to apply TOGAF in combination with a few other EA frameworks.
The attendees are expected to have some system design and development experience. There are no specific EA prerequisites; however the tutorial assumes basic exposure to EA.