The document outlines high-level tasks for establishing an SCI EA practice, including onboarding it with the PMO, establishing EA principles and standards, creating a business/products architecture roadmap, capturing the current application and infrastructure architecture states, identifying target architecture states, and establishing guidelines and processes around areas like technology selection, reviews, documentation, and governance. It aims to develop an incremental EA model and asset repository to optimize architectures across retail and enterprise systems.

1. SCI EA Practice Establishment - High-level tasks list
 Treat establishing of the SCI EA practice as an internal project and
onboard it withthe PMO
 Identify EA involvedbusiness andtechnical SMEs, their rolesand
responsibilities
 Establishand Agree on EA Principles andStandards
o Capture regulations andcorporate standards
 Create a list of concerns tofocus
o Business Architecture
 Capture current products andcapabilities
 Identify plannedproducts and capabilities updates/additions
 Create business/productsarchitecture roadmap
 Identify all SLAs available today
 Establishinternal SLAs for eachcritical process
 Extract common requirements for reusablesolutions
 Establishcommon business terminology vocabulary
o ApplicationandInformation Architecture
 Capture current applicationarchitecture state
 Identify target applicationarchitecturestate basedon
business/products architecture roadmap.
 Identify gaps and create anapplicationarchitecture roadmap
 Identify milestones, if necessary
 Adhere common business terminology vocabulary and
establishcommontechnology terminology vocabulary based
on it
 Establishsolutions architecture guidelines
 Support reusability:ServiceOrientation
 Horizontal and vertical Scalability
 Loose coupling (if applicable)
 Support for evolving technologies(if applicable and
makes sense)
 Identify list of standardtechnologies supportedby SCI
systems
o OS Stack
 Windows 7,8,10

2.  Linux (proxy servers)
o Application Stack
 .NET 4.5
 MVC.NET
 Spring.NET
 Etc.
 Mobile ApplicationStack
 iOS 7,8,9
 Androidx.x
o Middleware
 Biztalk 2010, 2013
 Biztalk ESB Tollkit
 Mule ESB
 Apache Kafka
o Database Stack
 MS SQL Server 2008 R2, 2014
o Establishnewtechnology reviewandonboarding
process
 Establish applications outdate technology sunset plan
and incorporate it withthe ApplicationArchitecture
Roadmap
o Identify list of systems that use not up to date
technologies
 Identify all systems usedinthe SCI including Finance,
Customer Care, HR etc.
o Buildan artefact (TBD) representing all internal
SCI systems connectionsbetweenthemselves
and with SCI Core products. This will include
existing integrations andLogical connections as
well
 Establishguidelinesandtechnical implementation
guide for the consistent UI throughout SCI
products/systems , including HTML/CSS guides
o Infrastructure Architecture

3.  Establishstandardserver resources consumptionmetrics
 Builda Server ResourcesUtilizationReport basedonthose
metrics
 Establishreviewprocessof Server ResourcesUtilization
Reports toensure effective infrastructurearchitecture
 Establishsystems monitoring and alerts (inprogress)
 Identify additional requirements, metrics andKPIs for
Productionsystems support improvement
 Establishinfrastructure outdate technology sunset planand
incorporate it withthe Infrastructure/Technology
Architecture Roadmap
 Identify list of servers that use not up todate software
o Ensure optimal organizationstructure
 Ensure staff cross-training andknowledge exchange between
teams
 Schedule knowledge exchange sessions
 EA Governance
o Avoidindependently evolving architectures for Retailand
Enterprise Developmentproducts
o Establishand maintainlist of all interfaces betweenall internal
systems andensure proper documentation
o EstablishArchitecture ReviewBoard(ARB) toimplementprinciples
and standards by constraining a newdevelopment. –The decision
on how ARB Review will tobe placedinto the SDLC needtomade
prior to starting the work on new ADD format
definition/standardization
 Establishsolutionarchitecture review procedures
 What artefacts/deliverables needtobe present
 What criterias will be examined/measured
 EstablishEA metrics andKPIs (on a later stage)
 Identify if update toexisting EA diagrams is required
and update themif needed.
 Incorporate an EA practice intocurrent project management
methodology in close collaborationwiththe PMO

4. o Integrate Architecture Practices intothe various SDLCs –Addition
by Ryan.
 Choose and tailor SCI EA Framework – Agendafor next meetings
o Define deliverables and artefacts for eachstepinthe TOGAF ADM
o Customize deliverables templates
 Optimize Architectural DescriptionDocument structure
o Customize Zachmanframework
 Choose a tool to model and populate EA Asset Repository - Agendafor
next meetings
o Sparx EA
 Plan communicationmethods betweenEA teammembers
o Meetings schedule
 Develop change impact/risk assessment methodology - Agendafor next
meetings
o Risk vs. Cost vs. Benefit analysis
o Recommenda change to the plan/roadmap basedon the step
above
 EstablishIncremental EA model development method - Agreed