Set a Strategy
Define a Service
Plan a Project
Design a Solution
Methods
In-Person Elicitation, Interviews, and Workshops
Business Process Diagrams and Models
Systems Diagrams
Use Cases
User Stories
Data Models
Requirements Lists and Specifications
Product Roadmaps
UI Wireframes and Prototypes
Business Model Canvases
Strategy on a Page
Business Process Mapping
Capability Mapping
Conceptual Data Modeling
Brick Diagram
Business Model Canvases
Sequence Diagrams (or Interaction Diagrams)
MESA
Pace Layers
Roadmaps
Stakeholder Engagement
Systems Diagrams
User Experience Mapping
Capstone: Project Documents
Capstone: UX Design Guides
Reference Architecture - Reference Architecture documents themselves are not so important as the process of UW stakeholders coming together to construct those documents and, in so doing, converge on common solutions. The documents represent the product of building a common approach across stakeholders as much as they serve as a guide for implementations.
EXAMPLES
Architecture Value Scorecard v2
Container-Based Applications Reference Architecture
Delete Means Delete
EA Guiding Principles
Minimize site-to-site VPNs
Private IP Addresses for Office Systems
Security and Privacy Policies
UX Design Guides
Workday Guardrails
EA Program Charge - helps stakeholders maximize the architectural value of their services, solutions, data, processes, or organizations
- Scope the right problem space, and assess the processes, people, and constraints in the space
- Analyze the problem and provide structure for evaluating what's working and what should be changed
- Develop alternatives and create a roadmap for one or more solutions
- Define the major components of a solution so it can be designed in detail
Steps to Establish Reference Architecture
- Identify the need for a new RA
- Prioritize potential RAs and decide which ones to develop next
- Ensure that the architectural decisions in each RA are consistent with enterprise strategy
- Provide or delegate input on the content of an RA, Commit resources to participate in the RA drafting process, Lend authority to the decisions the RA contains, Champion the RA to ensure implementation decisions are consistent with it
- Arbitrate implementation questions or new issues as they arise
- Oversee implementation decisions consistent with the RAs
Change is Interdisciplinary- We believe that the most successful change initiatives make use of best practices from multiple change disciplines, which enable different aspects of a change. The EA team encourages the use of relevant best practices from all these disciplines. As part of a team, an architect should be able to help the team plan how each discipline can contribute.
Agile development
Business analysis
Design thinking
DevOps practices
IT Service management
Organizational change management
Process improvement
Project and program management
Conceptual, Logical, Physical
Service Model Canvases
Architectural Value
Align services closely to UW needs and design them to enable business outcomes;
Balance trade-offs in solutions, such as functionality, reuse, full lifecycle costs, and risk;
Manage data to enable future opportunities and decision-making;
Streamline business processes and set them up for ongoing improvement; and
Develop organizations and individuals that are prepared for the future.
EA Scope
Consult with groups to include broad, long-term context in their decisions and strategies
Develop and manage reference architectures on behalf of the UW
Bring analytical methods that help groups identify tradeoffs, maximize value, and reach decisions
Convene stakeholders across UW organizations to build common understanding and collaboration
Inspire and educate people to think and act architecturally in their own work through outreach, training, and communities of practice
Proactively analyze strategic issues and bring recommendations to key decision-makers
Escalate key architectural decisions to senior management
Support key functions such as strategy and portfolio management
Context
The UW operates a complex set of services, solutions, data, and processes to enable its multifaceted mission in a rapidly changing environment. This complexity creates opportunities and risks that need to be identified and evaluated.
In UW-IT and across the UW, groups seek to make better decisions that balance trade-offs while increasing architectural value — including effectiveness, efficiency, adaptability, and sustainability.
Enterprise Architecture principles, methods, and consultation help groups do this on behalf of the entire University.
As a < insert type of user >, I want < insert goal > so that < insert reason >.
Example: As a student employee, I want to log my hours so that I will get paid for my work.
Student enrolls in courses for a quarter
Student reviews the schedule of available courses
Student researches a specific course in the catalog
Student researches available courses
Student completes a registration request
Details can include the process triggers, inputs, steps, roles (who does what), sub-processes, outputs, and outcomes.
Vertical Swimlane, Flow Chart, UML Activity Diagram
A Business Model Canvas lays out key topics that represent how an organization, program, or service works, so that stakeholders can clarify their intent.