Please enable JavaScript.
Coggle requires JavaScript to display documents.
UWASH EA - Coggle Diagram
-
Methods
In-Person Elicitation, Interviews, and Workshops
-
-
-
User Stories
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.
Data Models
Conceptual, Logical, Physical
-
-
-
Business Model Canvases
A Business Model Canvas lays out key topics that represent how an organization, program, or service works, so that stakeholders can clarify their intent.
-
-
-
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.
-
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
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
Architectural Value
-
Balance trade-offs in solutions, such as functionality, reuse, full lifecycle costs, and risk;
-
-
-
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.
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.
-
-
-
-
-
-
-
-
EA Scope
Consult with groups to include broad, long-term context in their decisions and strategies
-
Bring analytical methods that help groups identify tradeoffs, maximize value, and reach decisions
-
Inspire and educate people to think and act architecturally in their own work through outreach, training, and communities of practice
-
-
-