Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enterprise architecture artefacts

Portfolio of artefacts I've created over the years

  • Login to see the comments

Enterprise architecture artefacts

  1. 1. Enterprise architecture artefacts Brian Loomis
  2. 2. Princeton Digital Advisors uses architectural techniques to ensure the problem gets solved, whether it’s a long-term legacy system migration, or a new cloud-based as-a- service offering. These are non-code examples from recent projects, showing how we carry the architectural intent from the business case through to implementation. Assessments and program portfolio techniques Techniques which understand the customer better (business architecture) Techniques to drive risk down in non- functional ASRs Techniques which provide guidance to the implementation team (solution architecture)
  3. 3. Tools we use Project phase Plan (Imagine) Build (Become) Run (Achieve) Sustain (Maximize) Techniques & tools Business model • • Lean Startup Canvas • • (brainstorming) Competitive analysis/SWOT & capability • • (PCF) Customer Journey Map • • • Personas & Empathy Maps • • • • Storyboards • Business Process Modelling / Service Design • • • & • • • Impact Map • Mockups (web/mobile) • • • • System modelling (UML) • or Cameo System Diagramming (general) • (Visio stencils) • • • • Cloud diagramming • • Database diagramming • Interface definition • • • contract • CI/CD & DevOps • • • • • • • & us/solutions/devops • • Test/QA • • monitoring • Auto-deploy and environment management • Microsoft Operations Framework • versions/tn-archive/cc506049(v=technet.10) • Heatmap • • • • • Visualization Map • • Roadmaps • templates/technology-roadmap • • • • • roadmap-templates-smartsheet • ap=roadmap&utm_content=roadmapLP • Enterprise architecture • • Accountability • Architect, Bus Architect/Analyst • Product manager • Architect • Product/project manager • Architect • Service manager • Architect, Ent Arch • Product manager
  4. 4. Portfolio & enterprise planning Identification of value, coordinating related projects, high-level guidance to development teams
  5. 5. Program & project roadmaps
  6. 6. Capability & heat map assessments
  7. 7. Business model canvas
  8. 8. Helping people live better lives Transform internally (employee) New product & subscription revenue via IoT Social & mobile tools (competitive draw) for easier onboarding, ordering; predictable benefits Crowd-sourced R&D; sentiment analysis Reliable, easy-to-use global solutions; best practice sharing Global “reach” with cloud; integrated solutions for China Increase customer loyalty Create new revenue streams Drive brand of Contoso Enable One Contoso Retain and grow entry-level ABOs Cross-team collaboration Sentiment-driven 4P’s & customer service improvements Best practice coaching; improved analytics for building mega- businesses; leader development Lower operations costs with COTS, consolidate suppliers OpportunitiesGoals Solution Space*Objective Total experience (customer) Renew franchisee partnership Double number of Platinum's Increase ABO productivity Increase Contoso Sales / Revenue Focus on growth markets Externalized applications; easier business/down-line management Benefits dependency network Reduce operational costs Measured-by KPIs Employee satisfaction Campaign effectiveness measures Employee sat / 360 feedback Employee engagement CAPEX to sales ratio CAC, retained customer order size Gross profit, operating margin Net promoter score, online share of voice Time to hire, employee churn, training ROI Working capital ratio, net promoter score Operating expense ratio, reduced COGS Revenue per employee, net revenue Revenue growth rate (target markets) * People, process & technology
  9. 9. Operating model assessment
  10. 10. Joint venture IT assessment
  11. 11. Architectural guidance • Views in the architectural design phase (ISO 42010) • Patterns (environment, language selection, models in code) • Informal or viewpoint guidance after sprints have begun • Formal ATAM/PBAAM reviews or architectural review of project under way • External or partner-led reviews
  12. 12. Project requirements And high level design
  13. 13. Customer journey mapping and service blueprinting
  14. 14. Service blueprinting
  15. 15. The Instructor Experience LMS “Universe” D2L Qualtrics Integrations Tophat, Remind, Respondus, Piazza, SmartSparrowBio, Pearson, PackBack, MATLAB, LiveText VIA, Cengage, Crowd mark, Digication, Ech360, IClicker Online Zoom Office 365 Teams Instructional design WKAR Studio Univ. classroom software Windows 10 Adobe Presenter Office 365 - PowerPoint Google Classroom Central support BeSocratic (CEM) LON-CAPA (Mult.) CATME Virtual desktop (VDI) Assessment Scoring Office (Digital Desk) ProctorU (via D2L) Proctorio (via D2L) NortonInquizitive Proctored exams in room? Proctored exams on web? Recording Kaltura MediaSite Camera available (Web Zoom storage? Cisco? Unit-supported Bisk Amesite WileyPlus WebWork (MTH) ExamSoft? Accessibility Closed captioning on request ASL reader? Classroom hardware Tech cart (Crestron control screen, HDMI & VGA laptop connections, microphone(s), classroom PC, BluRay player, Campus Cable TV tuner, document camera) WiFi, iClickr, specialty (REAL room, confidence monitor, catch box) College systems eValue University lab software Unit lab software LDX (CoB) University systems SIS Student success (EAB) Academic profile Student ePortfolio Google Calendar, Drive Staff print Ziteboard, Jamboard ZipGrade, Prezi UNIT SUPPORTED SELF SUPPORTED CENTRALLY SUPPORTED Bookstore Student print Internet or TechStore downloads (e.g., ChemDraw) Support Centers WRAC Math RC UURAF Neighborhoods?
  16. 16. High level design diagrams and information flows
  17. 17. Comparing architectures or significant requirements (ASRs)
  18. 18. Prototypes and mockups for user experience
  19. 19. Project Implementation
  20. 20. Architectural guidance • Design patterns (API gateways, full-stack) • Code best practices (MVC or microservices) • Views as a result of architectural spikes or experiments • Guidance on containerization and DevOps pipelines • Specific views on architecturally significant requirements
  21. 21. Deployment on-premises
  22. 22. Performance & protocol views
  23. 23. Deployment in public cloud (GCP)
  24. 24. Deployment in public cloud (AWS, Azure)
  25. 25. Database design
  26. 26. Testing strategy and environments
  27. 27. Organizational change management
  28. 28. Brian W. Loomis Chief Digital Officer and Founder, Princeton Digital Advisors Brian has over 20 years of management and technology consulting experience with deep experience in translating the business objectives from the boardroom into world-class digital products and services. He has served as a CTO, as an enterprise architect, and as a product designer in several start- ups, and has created business-driven technology strategies, customer experience validation, and developed over a dozen innovative digital products and services. Brian has consulted with teams in organizations across high-tech, healthcare, manufacturing, consumer goods and public sector. Brian is a regular international speaker and a prolific writer within architecture and agile communities and holds multiple architecture distinctions and technical certifications. He is an alum from Microsoft, having been on two technical teams supporting .NET and Azure as they first launched, and has broadened out to be a trusted advisor for journeys to multiple cloud platforms. Brian received his Bachelor’s in Electrical Engineering from Princeton University as well as advanced degrees in business and computer science and served as an officer in the United States Air Force. Home base for him and his family is in East Lansing, Michigan.