Application architecture pack
Ratings for the Application architecture pack
Build the application portfolio, map interfaces and integrations, and design target states and rationalization
Who it is for. Application, solution and enterprise architects who own the application landscape: its catalog, its interfaces, its target state and the decisions to buy, build, modernize or retire.
219 blocks, 80 prompts, 6 prompt sets, 52 variables, in 16 topics. Version 2.
Made for Pro. Every download starts with 14 days of Pro, so you can add this pack today and use all of it; on the Free plan you can add it and read it, with your library read-only until you move to Pro or remove it. How packs work on Free and Pro
How to add a pack
- Download the pack. It is a single file that ends in .promptmason.json.
- In PromptMason, open Settings → Backup & data → Block packs and choose Add a pack from a file….
- Pick the file you downloaded.
The pack is added next to what you have, in a folder named for the pack with one subfolder for each topic. See Add a block pack for the details.
What is inside
Topics
- Application architecture scope, principles and viewpoints
- Application inventory and portfolio catalog
- Baseline application architecture views
- Target application architecture and building blocks
- Application gap analysis and roadmap inputs
- Application portfolio rationalization
- Application landscape health and technical debt
- Integration architecture
- Build, buy or SaaS assessment
- Solution architecture for a new system
- Solution design review against the application architecture
- Legacy modernization strategy
- SaaS sprawl and license overlap
- Application decommissioning
- Application due diligence in M&A
- Application roadmaps and lifecycle planning
Application architecture scope, principles and viewpoints
- Role blocks
- Application architect
- Context blocks
- Company and application landscape, Architecture practice and vocabulary, Architecture work in hand, Documents provided
- Task blocks
- Scope the application architecture work, Stakeholder concerns and viewpoints, Draft application architecture principles, Review draft principles for conflicts and testability, Define the catalog attributes, Input request to application owners, Brief a business sponsor on application architecture
- Format blocks
- Scoping note, Principle catalog
- Constraints blocks
- Work only from the material given, Stay at the application level, Call applications by their catalog names
- Prompts
- Scope the work and its views; Application principles for the board; Review the draft principles; Catalog attributes and input request; Brief the sponsor
- Prompt sets (what is a prompt set?)
- Run Phase C, Application Architecture. From the scope and views to the application requirements and the sponsor summary: baseline, target, gaps and work packages, in order.
- Scope the work and its views
- Baseline narrative and validation workshop
- Logical application components
- Target architecture narrative
- Gap analysis
- Work packages and cross-domain needs
- Application requirements for the next phases
- Phase C summary for the sponsor
Application inventory and portfolio catalog
- Role blocks
- Portfolio catalog owner
- Context blocks
- Catalog attributes and categories in use, Survey responses received
- Task blocks
- What counts as an application, Application owner survey, Consolidate survey responses into catalog entries, Clean up the application inventory, Write a catalog entry, Catalog data quality review, Quarterly catalog refresh note
- Format blocks
- Catalog entry layout, Inventory table
- Constraints blocks
- One entry per application
- Prompts
- Definitions guide and owner survey; Consolidate survey responses; Clean up the inventory; Write a catalog entry; Catalog quality review and refresh note
Baseline application architecture views
- Role blocks
- Baseline architect
- Context blocks
- Application inventory in scope, Interface list in scope, Business architecture inputs, View conventions
- Task blocks
- Interface catalog, Application and organization matrix, Application and function matrix, Role and application matrix, Application use-case diagram specification, Process and application realization diagram specification, Application interaction matrix, Application communication diagram specification, Application and user location diagram specification, Baseline application architecture narrative, Baseline validation workshop
- Format blocks
- Matrix table, Catalog table, Diagram specification
- Constraints blocks
- Interfaces are named by the data they carry, Describe the baseline as it is
- Prompts
- Interface catalog; Organization matrix and user locations; Function matrix and process realization; Interaction matrix and communication diagram; Role matrix and use cases; Baseline narrative and validation workshop
Target application architecture and building blocks
- Role blocks
- Target state architect
- Context blocks
- Target state drivers, Building block vocabulary
- Task blocks
- Define the logical application components, Map logical components to physical components, Target application portfolio catalog, Target application communication diagram specification, Architecture building block specification, Target state options, Target application architecture narrative
- Format blocks
- Building block sheet, Options comparison
- Constraints blocks
- Logical before physical, Products are candidates until chosen
- Prompts
- Logical application components; Target catalog and communication diagram; Physical components from the inventory; Building block specification; Target state options; Target architecture narrative
Application gap analysis and roadmap inputs
- Role blocks
- Transition planner
- Context blocks
- Baseline and target in hand
- Task blocks
- Application gap analysis matrix, Gap descriptions and resolution candidates, Impact on the other architecture domains, Transition architectures, Application migration diagram specification, Work packages for Opportunities and Solutions, Application architecture requirements for later phases, Phase C application architecture summary
- Format blocks
- Gap matrix with gap list, Work package cards, Timeline table
- Constraints blocks
- A gap names both ends, Every transition state stands on its own
- Prompts
- Gap analysis; Transition architectures and migration diagram; Work packages and cross-domain needs; Application requirements for the next phases; Phase C summary for the sponsor
Application portfolio rationalization
- Role blocks
- Portfolio rationalization lead
- Context blocks
- Assessment criteria and portfolio categories, Rationalization goals
- Task blocks
- Score applications on business fit and technical fit, Assign portfolio categories, Find functional overlaps, Options for one overlap group, Rationalization business case, Talk to an owner about elimination, Rationalization wave plan, Rationalization progress report
- Format blocks
- Scoring table, Business case one-pager, Leadership report
- Constraints blocks
- A saving counts when a cost stops, Score from evidence you can show
- Prompts
- Score and categorize the portfolio; Overlaps and consolidation options; Rationalization business case and wave plan; Talk to an owner about elimination; Rationalization progress report
- Prompt sets (what is a prompt set?)
- Rationalize the application portfolio. From fit scores to the business case, the wave plan and the talk with an owner whose application goes, in order.
- Score and categorize the portfolio
- Overlaps and consolidation options
- Rationalization business case and wave plan
- Talk to an owner about elimination
Application landscape health and technical debt
- Role blocks
- Landscape health assessor
- Context blocks
- Assessment notes in hand
- Task blocks
- Application health assessment, Technical debt register, Landscape health heat map narrative, End-of-support and version currency review, Critical application risk register, Technical debt reduction proposal, Annual landscape health report
- Format blocks
- Health scorecard, Debt register table
- Constraints blocks
- Describe debt by its consequence
- Prompts
- Health check and debt register for one application; Heat map and annual health report; Support and risk review; Technical debt reduction proposal
Integration architecture
- Role blocks
- Integration architect
- Context blocks
- Integration platform and standards
- Task blocks
- Choose the integration pattern, Interface specification, Business event catalog, API catalog, Integration landscape review, Integration platform capability assessment, Integration design review, Data exchange agreement
- Format blocks
- Interface specification sheet, Decision record
- Constraints blocks
- No integration through shared databases, Name the system of record at every interface
- Prompts
- Pattern choice and interface specification; Event and API catalogs; Integration landscape review and platform needs; Integration design review; Data exchange agreement
Build, buy or SaaS assessment
- Role blocks
- Sourcing options assessor
- Context blocks
- Sourcing policy, Vendor responses received
- Task blocks
- Frame the need, Long list and shortlist of options, Evaluation criteria and weights, Questions for demos and reference calls, Score the responses, Cost comparison over the horizon, Risks of each option, Sourcing recommendation paper
- Format blocks
- Recommendation paper, Cost comparison table
- Constraints blocks
- Build only what differentiates, Every cost line states its basis
- Prompts
- Frame the need and shortlist the options; Criteria, weights and demo questions; Score the vendor responses; Cost and risk comparison; Recommendation paper
- Prompt sets (what is a prompt set?)
- Decide build, buy or SaaS. From the framed need to a sourcing recommendation the decision maker can sign, in order.
- Frame the need and shortlist the options
- Criteria, weights and demo questions
- Score the vendor responses
- Cost and risk comparison
- Recommendation paper
Solution architecture for a new system
- Role blocks
- Solution architect
- Context blocks
- Project in hand
- Task blocks
- Solution architecture document draft, Solution context diagram specification, Solution component model, Software engineering diagram specification, Software distribution diagram specification, Enterprise manageability diagram specification, Architecture decision record, Non-functional requirements at the solution level, Alignment with the target application architecture, Risks and assumptions log, Board submission summary
- Format blocks
- Solution architecture document layout, Requirements table
- Constraints blocks
- Decisions record the rejected options, Name every dependency with its owner
- Prompts
- Solution architecture document draft; Context and component model; Architecture decision record; Software engineering view; Distribution and manageability views; Non-functional requirements and risks; Alignment statement and board submission
- Prompt sets (what is a prompt set?)
- Architect a new system. From the context and component model to the solution architecture document and its board submission, in order.
- Context and component model
- Software engineering view
- Distribution and manageability views
- Non-functional requirements and risks
- Solution architecture document draft
- Alignment statement and board submission
Solution design review against the application architecture
- Role blocks
- Design reviewer
- Context blocks
- Design under review, Review standards
- Task blocks
- Compliance review of a solution design, Reuse check, Review findings report, Waiver request, Prepare the review conversation, Application design review checklist
- Format blocks
- Review findings report layout, Checklist layout
- Constraints blocks
- Every finding cites its rule, Review the design, not the people
- Prompts
- Review a solution design; Reuse check against the portfolio; Waiver request; Prepare the review conversation; Application design review checklist
Legacy modernization strategy
- Role blocks
- Modernization strategist
- Context blocks
- Modernization drivers, Legacy application in hand
- Task blocks
- Assess a legacy application for modernization, Modernization options for one application, Incremental modernization plan, Modernization roadmap for the portfolio, Modernization business case, Risk and knowledge-loss assessment, Reassure the business owner
- Constraints blocks
- One option per application, with its trigger, Service continues at every step
- Prompts
- Assess a legacy application and pick its path; Incremental modernization plan; Modernization roadmap for the portfolio; Modernization business case and risks; Reassure the business owner
- Prompt sets (what is a prompt set?)
- Modernize a legacy application. From the assessment and chosen path to the plan, the business case and the talk with the business owner, in order.
- Assess a legacy application and pick its path
- Incremental modernization plan
- Modernization business case and risks
- Reassure the business owner
SaaS sprawl and license overlap
- Role blocks
- SaaS portfolio steward
- Context blocks
- SaaS discovery sources, Discovery data in hand
- Task blocks
- Build the SaaS inventory from discovery data, SaaS overlap analysis, Consolidation recommendation for a SaaS group, License right-sizing, Renewal review, Talk to a team about an unsanctioned tool, SaaS intake standard
- Format blocks
- Overlap table
- Constraints blocks
- Count active users, not seats
- Prompts
- SaaS inventory from discovery data; Overlaps and consolidation; Right-size licenses before renewal; Talk to a team about an unsanctioned tool; SaaS intake standard
Application decommissioning
- Role blocks
- Decommissioning lead
- Context blocks
- Retirement decision
- Task blocks
- Decommission readiness assessment, Decommission plan, Data disposition note, Decommission notices, Decommission checklist and sign-off
- Format blocks
- Action plan table
- Constraints blocks
- Nothing is switched off while an interface points at it
- Prompts
- Decommission readiness; Decommission plan and data disposition; Notices to users and system owners; Decommission checklist and sign-off
- Prompt sets (what is a prompt set?)
- Decommission an application. From the readiness verdict to the signed checklist that allows switch-off, in order.
- Decommission readiness
- Decommission plan and data disposition
- Notices to users and system owners
- Decommission checklist and sign-off
Application due diligence in M&A
- Role blocks
- Due diligence architect
- Context blocks
- Deal context, Data room material
- Task blocks
- Due diligence request list, Assess the target's application landscape, Integration options by capability, Day one and first hundred days plan, Red flags for the deal team, Transition service scope
- Format blocks
- Due diligence findings report
- Constraints blocks
- Code names only
- Prompts
- Due diligence request list; Assess the target's landscape; Integration options and day one plan; Red flags and transition services for the deal team
Application roadmaps and lifecycle planning
- Role blocks
- Application roadmap owner
- Context blocks
- Vendor roadmap in hand
- Task blocks
- Roadmap for one application, Vendor roadmap review, Upgrade decision paper, Portfolio roadmap, Lifecycle status review
- Constraints blocks
- Every date has a source
- Prompts
- Roadmap for one application; Vendor roadmap and upgrade decision; Portfolio roadmap; Lifecycle status review