Child Wear Ea Blueprint V0.7

Child-Wear Pte Ltd

Enterprise Architecture Blueprint

Team 7, ISS, NUS

1

Balaji BalasubramanianLi GangRuibo ZhangSaranya RanganathanSonia SodhiVivek Raja Mani

Agenda

IntroductionChild-Wear Vision & MissionOverall Assumptions & ActorsOrganization StructureScope & Goal of this ProgramArchitecture Vision & Principles

SWOT Analysis & Strategy Map

2

Child-Wear EA Blueprint

Performance Driven Governance Based Enterprise Architecture

4

Introduction

Child-Wear Vision & Mission

Vision

• To be the number one clothing brand in the child wear manufacturing business.

Mission

• Exceed our customer needs and expectations of price, service, and selection in children dresses

• Procure and manufacture quality children dresses at lower cost.

Overall Assumption

Child-Wear is starting EA from ground level.No EA resources at Child-Wear till now

6

ActorsHuman Actors

CustomerSupplierSales StaffOrder Processing AdministratorManufacturing Team MemberEnterprise ArchitectsSenior Management Team MembersIT Team Members

7

System ActorsSales Record SystemInventory SystemManufacturing Planning SystemAccount and Financial Information SystemHuman Resource SystemCustomer Billing System Sales and Billing System Manufacturing and Inventory System

Background (Current Sales Order Process)

8

Current Inventory Process

9

Current Manufacturing Process

10

RFQ Acceptance and Billing Process

Organizational Structure

12

CEO

CIO

Chief Enterprise Architect (Business & Performance Architect)

Information Architect Solution & Technical Architect

Responsible for establishing data quality standards, data taxonomies and offering input to how information is exchanged internally and externally.

Establishes standards and offerguidance aimed at sustainingthe business objectives longterm. Also, accountable for Performance of EA

Provide technology solutionsbased on defined business requirements. They are alsoconcerned with things at a logical level as well as the physical level

Enterprise Architecture Steering Committee

Overall Goal of EA ProgramEnable effective and efficient communication with the users/ management/ customers/ suppliers.

To leverage the existing business processes

Reduce overall cost – Production & Overhead

Use the power of internet to widen existing customer base.

To improve service levels to the customers

Improvise Supply Chain Management Process

Minimise processes and system redundancies

13

Scope of EA ProgramDefine baseline architecture & propose target architecture for

PerformanceBusiness InformationApplicationTechnology

Define Architecture Governance & Management for Implementation and Change

Facilitate a single view of the organization

14

Architecture Vision & PrincipleVision

Prepare a shared enterprise vision that describes “picture of desired future” that is to be achievedImprovise overall business service levels and productivityAnytime, Anywhere, Always - Information Available ,Accessible, Useable

PrinciplesDeliver the most good to the broadest range of IT usersImplement Enterprise-wide EA. EA compliance for every program and projectThe planning and management of Enterprise Architecture must be unified and have a planned evolution that is governed across the enterprise.Information Is an Enterprise Asset. Focus on Boundaryless Information Flow.Facilitate the sharing of information to accelerate and improve overall decision-makingReduce integration and interoperability complexity and increase agility for enterprise changeReuse common solutions. Practice Modular Solutions 15

16

Business Architecture

Targets & InitiativesBalanced Scorecard

Strategy MapStrategy

VisionValuesMission

Strengths WeaknessesStrong understanding of the current business processes with the suppliers of Child –Wear

Departments take responsibilities on their own business processes and IT systems decisions

Strong understanding on overall interrelationship between departments (including business process workflows)

Open for sharing of data (such as inventory information)

The manufacturing planning system available in-house is stable and has not had any large down time (downtime <0.1%)

Lack of protection for IT systems (such as viruses in email attachments causing hard disk corruption)

No capitalization / usage of the the online market exchanges and trade hubs, with suppliers selling fabrics at lower price

Lack of integration of IT systems. The Sales / Inventory and Manufacturing planning systems are not well integrated with each other, resulting in slow / delayed process of communication and completion of orders

Missing standardization of business process resulting in redundant processes.

Usage of old technology in the current system

Resistance from employees in supporting new initiative to improve business processes and IT systems

SWOT (as-is)

Opportunities ThreatsTo integrate the Child-Wear procurement system with Fabric.Net.sg using the ebXML standard.Lower procurement cost and compete with competitorsTo be able to receive quotations/orders via internetTo provide tools / mechanisms to the sales team to be able to enter orders while being in the fieldTo help Sales team access the inventory management system, there by reducing the dependency on the operators causing delay in time to respond.The child-wear website currently used only for marketing literature and has not been utilized / explored for more interactive usageTo be able to develop / host and maintain a secure high volume e-Business website

Current IT system used by Child-Wear is a standalone system and not integrated with suppliers / buyers available online

The AS400 system used for Manufacturing Planning system also runs other corporate applications like Account and Financial system / Human resource system, which may impact the business critical application MPS

SWOT (as-is)

Strategy Map for Child-Wear

19

Reduction in Operating Cost

Achieve internal business process efficiency

Take full advantage of Internet

Increase Customer Base

Use eBusiness Mechanism

Cheaper and Quick Suppliers

Invest in IT Systems revamping and consolidation

Align Organization towards IT revamp

Learning the Benefits achieved from IT enablement

Organization alignment

Long term objectives

Internal

Business PrincipleThe entire organization own and implements business processes and the IT systems that supports them.Business strategy, supported by well-defined business objectives and justified business value, shall drive the IT investments of Child-Wear.Business process re-engineering should be easily possible through appropriate use of technology.Business processes shall be automated where technology allow, to reduce processing time and cost and increase per process throughput.Child-Wear provides secure "anytime / anywhere" business services to its customer community.Child-Wear operations are maintained in spite of any system disruption.Information management processes must comply with all relevant laws, policies and regulations.Enable Interoperability with suppliers.Provide effective and efficient customer services.

20

Business Reference Model

Marketing & Sales

Procurement & Manufacturing

Customers Suppliers & Partners

Business Management

Marketing Strategy & Plan

Sales Portfolio

Operations Management

Time to Market Management

Product Lifecycle

ManagementResource

Management

Customer Satisfaction &

Problem Management

Customer Service

Customer Billing

Customer Order

Sales Statistics

Sourcing Strategy Inventory

Management

Sourcing Strategy

Efficient Manufacturing

Supplier Payment

Increase Sales & Customer

Base

Sourcing Strategy

Supplier Payment

Performance Referenece Model

23

Low Standardization & Low Integration model Lack of centralized / common applications Lack of common / standardized business processes People dependent for sharing of information between

departments

Operating Model (Current State)

24

High Standardization & Integration model Decisions on IT systems to be made centrally through

proper processes Sharing of common applications and data throughout

enterprise level “Best Practices” processes to be implemented

centrally and propagated to every department Higher service levels achieved due to alignment of

business processes.

Operating Model (Target State)

25

Core Business Process Analysis (Target)

26

Resp. to Cust. Proc. Sys.

Target State: Customer Order Fulfillment – Process Request for Quotation (RFQ) – Response

Process RFQ Resp. for Online RFQ Resp. for RFQ thru Sales Team

Cus

tom

er

Proc

urem

ent

Syst

em

Cus

tom

er

Proc

urem

ent

Syst

emSa

les a

nd B

illing

Sys

tem

(SBS

)Sa

les a

nd B

illing

Sys

tem

(SBS

)W

eb

Stor

efro

nt

Syst

em

Web

St

oref

ront

Sy

stem

Sale

s Tea

mSa

les T

eam

Cus

tom

erC

usto

mer

Receive response on

product availability information

Response to RFQ

Receive response to RFQ

Calculate Price

Response to RFQ



Response to RFQ



Core Business Process Analysis (Target)

27

No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take the Action

1. Revamp and consolidate Sales Record System and Customer Billing System into new centralized Sales and Billing System (SBS)

Important to understand the difficulty to consolidate data from existing systems

Continuity of business operations by users using new revamped system

Important to understand the improved performance in capturing transaction

Define the processes needed to understand the existing data; define data principles, conceptual model, logical model and metadata

Define usability requirements of applications

Define the need of user training

Define the design to cut down the number of steps to capture transactions and necessity to handle exception cases

IA

AA

BA,Governance

BA, AA

Gap Analysis

28


2. Revamp and consolidate Manufacturing Planning System and Inventory System into new centralized Manufacturing and Inventory System (MIS)

Important to understand the difficulty to consolidate data from existing systems

Important to understand ease of use of application to users

Continuity of business operations by users using new revamped system

Important to understand the improved performance in capturing transaction

Define the processes needed to understand the existing data; define data principles, conceptual model, logical model and metadata

Define usability requirements of applications

Define the need of user training

Define the design to cut down the number of steps to capture transactions and necessity to handle exception cases

IA

AA

BA,Governance

BA, AA

Gap Analysis

29


3. Integration of SBS with MIS through Web Services

Important to understand the need of new technology involve or reuse of existing technology

Important to understand the need for security control

Important to understand interfaces needed for message passing

Analyze the existing technology for possible reuse and requirement for new technology for bridging the gap

Define policy for security control

Define the functionalities to be published and messages to be passed

TA

TA

AA, IA

Gap Analysis

30


4. Allowing customers to submit order online through new Web storefront and personalization of contents

Important to understand the need of application to cross different time zone and locale

Important to understand that customers may use different browsers to access the application

Important to understand possible loss of confidentiality, integrity of the data passing through communication channel

Define globalization design principle when developing the applications

Cross platform testing shall be conducted

Ensure the conformance of security policy by implementing security control

AA

AA

TA

Gap Analysis

31


5. Provision of Web Services to customers’ procurement systems

Important to understand messages that need to flow between communication

Important to define the number of services to be published

Important to understand the implication of security issues, confidentiality, integrity and availability of both the customers’ procurement systems and Child-Wear system

Define the necessary data for request and response passing, and define the standard format of the message

Define the necessary functionalities to be published and plan for future expansion for inclusion of new functionalities

Define the security control mechanism to be implemented and imposed on both the customers’ procurement systems and Child-Wear System

IA, AA

AA

TA

Gap Analysis

32


6. Collaboration with suppliers’ order systems through the their provided Web Services

Important to understand messages that need to flow between communication

Important to understand the number of services to be consumed

Important to understand the implication of security issues, confidentiality, integrity and availability of both the suppliers’ order systems and Child-Wear system

Understand the necessary data for request and response passing, and the standard format of the message

Understand the list of functionalities to be consumed and plan for future expansion for consuming of new functionalities

Understand and implement the security control mechanism for communication between the suppliers’ order systems and Child-Wear System

IA, AA

AA

TA

Gap Analysis

33


7. Cutting down the need of coordination between Sales Team with Order Processing Administrator and Manufacturing Team

Important to understand how the new operation model requires restructuring of existing organization

Define clear organization structure and the responsibilities of each group

Governance

8. Automatic billing to customer

Important to understand how the automatic billings will cut down delay of billing cycles and technology used across different type of customers

Define application and technology architectures for transmitting invoice to customers

AA, TA

Gap Analysis

Information Architecture

Data Principles

Data Creation:All enterprise data should be captured once at the point of its creation.

Data Identifiers:Every object in the enterprise will contain a globally unique identifier. That identifier will be in the form of the Universally Unique Identifier (UUID).

Standard Data Elements:The use of standard data elements of universal fields will be used across the Enterprise for new development and system enhancements.

Spatial Information is a valued investment and asset:Spatial information can accelerate and improve decision-making, increase accountability, and improve services. Information must be shared to maximize effective decision-making.

Information Access based on access levelsEasy and timely access to data and information based on the access levels for various authorized personnel needs to be the rule rather than the exception. This needs to be accomplished without compromising security, confidentiality, and privacy.

Data Model -Conceptual Model

Quotation

Id INTEGER CustomerID INTEGER Productid INTEGER Quantity INTEGER EstimatedValue INTEGER EstimatedDate DATETIME Status INTEGER

Items

Id INTEGER Description INTEGER

Inventory

Id INTEGER Item_ID INTEGER QuantityInStock INTEGER

Products

Id INTEGER Description CHAR(50) Quantity INTEGER

Invoice

Id INTEGER CustomerID INTEGER ProductID INTEGER Quantity INTEGER Payment Details CHAR(500)

PurchaseRequest

Id INTEGER SupplierID INTEGER ItemID INTEGER Quantity INTEGER

Stakeholders

Id INTEGER CompanyName CHAR(10) ContactPerson CHAR(10) Address CHAR(10) Type INTEGER

Authentication

Id INTEGER Username CHAR(10) password CHAR(10) Usertype CHAR(10) SecondaryID INTEGER

Users

Id INTEGER FirstName CHAR(10) LastName CHAR(10) Address CHAR(10) Department CHAR(10)

Sections

ID INTEGER Name CHAR(10) Description CHAR(10) ContactPersonUserID INTEGER

1

0…*

1

1

1

1

1

11

1

1

1

1

1..*

1

0…*

1

1

1

Data Dissemination & Interoperability ViewEntity Name Source Destination Frequency Format

Quotation Customer SBS Whenever the customer postsa quotation

Web service request

Invoice SBS Customer When the sales team keys inthe quotation

SOAP message/ MQ Message

PurchaseRequest MIS Suppliers When the Manufacturing teamkeys in the request for raw materials to the suppliers


Inventory SBS MIS When the Sales team needs to check the current status of stocks in the inventory


Authentication Users of thesystem

Child wear website Whenever any user of the system needs to be authenticated to enter the system.

Web service request

Sections SBS Section head When the contact person of every section of the child wear company needs to be Identified


Products SBS MIS When the sales team needs to check the details of the existing stock details


Items Manufacturing team

MIS When the manufacturing team needs to check the details of the existing inventory details.


Usage of WS-Security for web services and X.509 Certificates will largely cover the security aspect of the system besides encryption/decryption of the messages in message queue

Data Lifecycle View

Entity Name Create Read Update Delete

Quotation SBS SBS SBS

Invoice SBS SBS SBS

PurchaseRequest MIS MIS MIS

Inventory MIS MIS,SBS MIS

Sections MIS,SBS SBS,MIS

Products MIS,SBS SBS,MIS MIS

Items MIS MIS MIS

Stakeholder SBS,MIS SBS,MIS SBS,MIS

Business/Information Matrix

S/N ProcessQuotation Stake

HolderInvoice Inventory Products Sections Purchase

Request

1 REQUEST

1.1 Request through Sales Team C R R

1.2 Request online C R R

1.3 Process Request for quote R R R

2.1 Check products availability R

2.2 Check raw materials availability R R

2.3 Quote for the request product U R R

2.4 Create invoice U R C

3 Processing the Order

3.1 Create purchase request for raw materials

R U C

3.2 Update the products list U

Data Gaps & Recommendations

Process

Quotation Stakeholder Invoice Inventory Products Items SectionsPurchaseReq

uest

Customer I

Supplier I

Invoice I

Products I

Items I

Inventory I

New Data Architecture CR CR CR

I = Included CR-Create

Best PracticesData architecture should be aligned to the business. Any change in the business should be easily accommodated.

Data Standards are to be followed to ensure interoperability with suppliers/customers.

Data access layer should be created to maintain all the CRUD activities.

Ensure authorized person is allowed access to the data.

All transaction with the data has to be logged as audit trail.

Regular backup of data is to be done.

Avoid storage of duplicated data across different storage sources.

Entity names and attributes should use and be referenced consistently across the company, both in systems and documents.

Sensitive information should be encrypted in transit and in the storage.

Data entity owner’s concern should be addressed and the consent should be got before any modifications.

42

Application Architecture

Application Architecture Principles

43

All Applications should align with the business vision and requirements.

Cost effectiveness and Operational Effectiveness - Reduction of TCO (Total Cost of Ownership)

Reduced integration complexity by adhering to industry standards

Ease of use to enable the users to work without any dependencies.

Component-based model and reuse – all functions, modules, tools and services will be designed such that they support reusability.

Changes to Application are to be made only based on Business Need

Software and Hardware conform to defined standards to promote interoperability of data, applications and technology.

Current Application Architecture

Target Application Architecture

Target Application Architecture

Current Application Architecture

Applications Sales & Billing System (SBS)

Web Storefront (Part of SBS)

Manufacturing and Inventory System (MIS)

High Performance Child-wear Website

Sales Record System (SRS)Inventory System

Customer Billing System

Manufacturing Planning System

Child-wear Website

-Need to be developed

Included, but need to be modified

Gap Analysis

Best Practices

Service Oriented ArchitectureCapability Maturity ModelApplying design Patterns and Framework

48

Technology Architecture

49

Infrastructure Applications Business Applications

Operating System Services

Communication Infrastructure

Qualities

Qualities

Qualitie

sQualit

ies

Application Programming Interface

Softw

are

Engin

eerin

g

Communications Infrastructure Interface

Network Services

Locatio

n &

Dire

cto

ry

Use

r Inte

rface

Data

Inte

rchange

Data

Managem

ent

Transa

ctio

n Pro

cessin

g

Security

System

& N

etw

ork

Managem

ent

Derived from TOGAF TRM

Technical Reference Model

Technical PrinciplesSeparation of ConcernsFollowing the “Modularity” and “Abstraction” approach for the developing the technical features.Anticipation of ChangeChanges is the “known unknowns” during the software engineering process, which requires to be handled properly to be minimized the negative impact on Child-Wear. GeneralityThe application designed and implemented should be free from unnatural restrictions and limitations.ConsistencyApplications, projects, products and processes should keep consistent through the whole organization to increase the reliability and decrease the complexity.Follow Proper SE MethodologyProper SE methodology can help Child-Wear to deliver the application successfully.Systems and NetworkAll the system and network management application within Child-Wear should be consolidated and integrated for effective and efficient usage. Should ensure business continuity.Usability & Look-Feel The look and feel must be easy to use and consistent among all applications.

SecurityThe computing system's assets can be read only by authorized parties and each of the transaction must be traceable. All the resources / services available within Child-Wear must be registered and maintained with Location and Directory service.Business ContinuityTransactions must roll back when the transaction fails and ensure business continuity. Also, monitor performance of the system and network continuously.

Technical Principles

Best PracticesFeasibility Study must be conducted before carrying out any project

Both functional and non-functional requirements must be captured and documented.

Activities to be performed for a project shall be properly planed.

The project progress must be monitored.

Corrective actions must be taken if any variance from the plan are detected

Deliverables (products / services) must be reviewed, approved and authorized before the issue.

CASE tool should be utilized to help in development and management.

Technology and Product StandardsRUP shall be used as the formal methodology for Child-Wear.UML shall be used as the standard notation.Java shall be the programming language.Use JBoss 5.0 as the Application ServerBrowser: IE 4.0 +, Mozilla Firefox 1.0 HTML: 4.0 + Web 2.0Script Support: JavaScript 1.1Use IBM System x3850 M2 as the host server.MS Project and Visio shall be used to facilitate the Software Engineering processes.Symantec Network Security and Symantec AntiVirus for SecurityOracle 10g for DatabaseJDBC HibernateXML for WebservicesJava Naming and Directory Interface (JNDI)Lightweight Directory Access Protocol (LDAP)SSL,PKI, Single Sign On

Gap Analysis

Software EngineeringRun-time EnvironmentProgramming Language

Data ManagementData dictionary / Repository

SecurityIdentification and AuthenticationSecurity ManagementNon-Repudiation

Key Recommendations for TA GapsRe-write the application and integrate with Customer Billing System with Java.

Migrating the application to JBoss 5.0 if currently it is not running on it.

Migrating the application to host server IBM System x3850 M2

Enhance applications to support Broswer: IE 4.0 +, Mozilla Firefox 1.0, JavaScript 1.1

Migrate the DBMS to Oracle 10g

Build Single Sign On for all applications

Add Symantec AntiVirus protection

Setup Non-Repudiation mechanism

56

Firewall

Internet

Firewall

DMZ

TZ

PKISSL

ApacheOracle 10g

JBoss 5.0

Routers

Target Technology Architecture

57


1

2

3

4

Technology and Product Standards

1

Best Practices

1 Monitor performance of the system and network continuously.

2 Trends Analysis should be performed on periodical basis.

3 Thresholds should be well analyzed and set.

4 Quality goals should be set in advance.

5 Services must be monitored and reported properly.

6 CPU, Memory and hard drive usage should be monitored.

7 System and network management shall always be linked and aligned with Child-Wear’s business strategies and goals.

System & Network Management

58

Best Practices1 Establish a sound security policy as the “foundation” for design.

2 Identify potential trade-offs between reducing risk and increased costs and decrease in other aspects of operational effectiveness.

3 Implement layered security

4 Implement tailored system security measures to meet organizational security goals.

5 Minimize the system elements to be trusted.

6 Confidential Information should be encrypted when transmitting through the internet.

7 Implement security through a combination of measures distributed physically and logically.

8 Isolate public access systems from mission critical resources (e.g., data, processes, etc.).

9 Use boundary mechanisms to separate computing systems and network infrastructures.

10 Where possible, base security on open standards for portability and interoperability.

11 Use common language in developing security requirements.

12 Ensure that developers are trained in how to develop secure software

Technical Service (3) - Security

59


1

2

3


1

Best Practices

1 Always follows the locking mechanism and principles for transaction processing.

2 Transactions must be roll back when the transaction fails

3 Ensure the Atomicity, Consistency, Isolation and Durability for all the transactions performed

Technical Service (4) – Transaction Processing

Technical Service (6) – User Interface

60

1. User InterfaceTechnical Principles

1 Ease of UseThe User Interface must be user friendly.

2 Good Look and FeelThe User Interface must be implemented with good look and feel.

3 ConsistencyThe User Interface Design must be consistent through all the applications within Child-Wear.


1 Adobe Photoshop

2 Macromedia Dreamweaver

3 Macromedia Flash

4 Java Server Pages

Technical Service (6) – User Interface

61

Best Practices

1 Provide instant access to search tools, areas of specialized interest, login and exit points. User should be able to jump from one section to a specific area anywhere within the site. Provide Quicklink access to most widely used tools and functions.

2 The aesthetics or chosen creative concept shouldn’t overshadow functionality; it should enhance the online brand and experience.

3 Functionality and the aesthetics should be consistently enabled across multiple online channels, platforms, and browser variations. This assures that a learned pattern of recognition is rewarded and that processes are leveraged for enhanced functionality, access, and optimal information architecture.

4 Avoid mixing icon and hypertext driven navigation as it may confuse users and detract from functionality. Utility driven tools and help functions should be consistently placed throughout site. Color, navigation functions, and interactivity should display and perform the same way.

5 Customization lets users change their experience and preferences to better meet their needs. Personalization is what the site presents to the user based on profiling or previous user behavior and interests. Customization allows users to navigate faster without sifting through unwanted material. Personalization can pre-populate form fields freeing users from repetitive tasks. Avoid asking users for personal information too soon; as it is one of the major reasons for site abandonment.

6 Simplify the number of steps needed to perform tasks. Avoid drop-down menus that rely on the users’ memory. Optimize graphics, and minimize the use of unnecessary graphics to improve download time.

7 Information should be organized in intuitive and related groupings. Primary functions are to be prominently displayed and not buried.

8 Provide access for all types of users as defined by status of relationship or special needs: customers, prospects, mobile workers, disabled persons, etc.

9 Visual cues should be utilized, clearly indicating where the user is in the process or information architecture. Help utilities such as step wizards enable users to better accomplish goals. Navigational aids such as different graphically displayed ‘select’ and ‘roll-over’ states also help to indicate where the user is located. Color-coding can also indicate to the user where they are in specific sections.

10 Simple, brief and intuitive labels and naming conventions. Short copy blocks and limited scrolling. Complex pages should be broken down into smaller sections.

62

Opportunities & Solutions

63

Opportunities and Solutions PortfolioInitiative Priority * CategoryNew Centralized Sales and Billing System(SBS) HIGH BA,AA New Centralized Manufacturing and Inventory System (MIS) HIGH BA,AA

Integrated System Authentication and Authorization for all systems HIGH IA,AA,TA

Oracle Servers to ensure 24x7 Data Availability HIGH TA

Web Store for retail and corporate customers for Ordering.

HIGH BA/IA/AA/TA

Web Services for integrating with Customers from SBS MEDIUM BA, AA

Web Services for integrating with Suppliers from MIS MEDIUM BA, AA IT Infrastructure to enhance business needs(PDA's for sales team, Laptop's, Workstation's etc)

MEDIUM TA

Implement Enterprise Service Bus (ESB) to integrate all IT Systems HIGH BA/IA/AA/TA

* Priority based on Business Impact, Risk and Strategic business requirement

64

Governance

65

Governance Mode - Centralized

Child-Wear

Enterprise Architecture

Sales & Marketing

Team

Business Analysis & Management

Team

Manufacturing&

Procurement

Finance Team Information Technology

Team

Architecture Governance &

Management Team

66

Governance Mode - Centralized

Governance Policies & PracticesBusiness is accountable for all IT initiatives and business approval required for all IT implementations.

Architecture standards will be centralized and followed throughout the organization.

Review of compliance with the actual standards will be undertaken by Architecture Governance Management Board once per quarter.

Enterprise Architects will stay part of any IT initiative and provide holistic guidance on the overall IT implementation.

Architecture will be reviewed every 6 months and will be always made related to Organization Goals and Strategies.

Any issues in following Architecture Guidelines will be reported to the Architecture Governance Board for Exception allowance. The Governance Board will review the issue based on the urgency of Business.

67

AudienceEA Steering Committee, Enterprise Architects, ‘C’ Level executives, Line of Business owners, IT team

ContentsEnterprise Architecture statements and implementation guidelinesThe value, benefits, and importance of Enterprise Architecture.The contribution of Enterprise Architecture Committee and Program to the pursuit of business objectives.Program objectives, milestones, and deliverables in the current and future architectural releases

Mode of communicationThe basic EA scope and value materials, as well as some high-level business-oriented status information, will be available (and prominently displayed) on the EA website. These materials should be suitable for use/delivery by EA Committee members as well as other staff. Any update to this document will be notified through e-mails. This would ensure the awareness among the EA team of the update to the scope.

Frequency of communicationThe communication will be on a monthly basis. The decision for monthly communication is to closely monitor the developments/setbacks that are happening due to the newly implemented policies/proposals and impose corrective measures.

Skeletal Communication Plan

Measure magnitude and the impact of every proposed changeGroup & prioritize them as simple, incremental or re-architectingApprove them at Architecture Board level with consent from Business.

The following steps are taken care before change is done:1. Impact Analysis and evaluation2. Resource allocation and management for architecture tasks3. Risk evaluation

Change Management Process

Enterprise Architecture is the capability that must be core to the business and inherently be part of their Child Wear’s crown jewels

The EA team must always function in-house. They can be supported for some activities (the more tactical ones), by strategic vendor partner or consultants.

For development of IT and IT Systems and applications, Child wear can use a strategic partnership form of outsourcing.

A strategic partnership deal might encompass mainframe operations, WAN and LAN management, telephony, web hosting, and help desk services.

EA Guideance to Outsourcing

Back Up Slides

BA Process (Current)

72

Process Order

Current State: Customer Order Fulfillment – Process Order

Process RFQ

Cus

tom

er

Billin

g Sy

stem

Cus

tom

er

Billin

g Sy

stem

Man

ufac

turin

g Te

am

Man

ufac

turin

g Te

amO

rder

Pr

oces

sing

Adm

inist

rato

r

Ord

er

Proc

essin

g A

dmin

istra

tor

Sale

s Rec

ord

Syst

em (S

RS)

Sale

s Rec

ord

Syst

em (S

RS)

Sale

s Tea

mSa

les T

eam

Cus

tom

erC

usto

mer

Receive response for RFQ

Place order

Receive order

Store order information

Key in order information

Send order request

Receive order request


Bill Customer

Bill Customer

Receive invoice

Update inventory system

Send product to customer

Receive product

Core Business Process Analysis (Current)

73

Process Order

Current State: Customer Order Fulfillment – Process Order

Process RFQ

Cus

tom

er

Billin

g Sy

stem

Cus

tom

er

Billin

g Sy

stem

Man

ufac

turin

g Te

am

Man

ufac

turin

g Te

amO

rder

Pr

oces

sing

Adm

inist

rato

r

Ord

er

Proc

essin

g A

dmin

istra

tor

Sale

s Rec

ord

Syst

em (S

RS)

Sale

s Rec

ord

Syst

em (S

RS)

Sale

s Tea

mSa

les T

eam

Cus

tom

erC

usto

mer

Receive response for RFQ

Place order

Within 3 days of RFQ response?

Receive order

Store order information

Key in order information

Send order request

Print order



Bill Customer

Bill Customer

Receive invoice

Y

Update inventory system

Send product to customer

Receive product

NRefer to Receive RFQ


74

Process RFQ

Current State: Inventory Procurement

Ma

nufa

ctu

rin

g P

lannin

g

Syst

em

Ma

nufa

ctu

rin

g P

lannin

g

Syst

em

Sup

plie

rSu

pp

lier

Inve

nto

ry

Syst

em

Inve

nto

ry

Syst

em

Ma

nufa

ctu

rin

g T

ea

m

Ma

nufa

ctu

rin

g T

ea

m

Receive enquiry on how quickly product can be manufactured

Estimate raw materials needed

Check raw materials

availability

Raw materials available?

Display raw materials

availability information

Receive enquiry on ability to supply

raw materials information

N

Enquire ability to supply raw materials

information

Response ability to supply raw

materials information

Receive response on ability to supply

raw materials information

Calculate product

manufacturing timeline

Display product manufacturing

timeline

Response how quickly product

can be manufactured

Y


Backup Slides

Application ArchitectureStake holders concerns and how the target architecture addresses them

Stake Holder Concerns

Interoperability between Sales Record System (SRS) and Customer Billing SystemShared functions/ ServicesSoftware Development for Sales and Billing System (SBS)

Addressing the Concerns

Application Interoperability ViewCaptures the interoperability/ inter-dependency between the applications

Common Application Services Viewcaptures the services that are used across all or most of the applications

Application Consuming Data

Application Producing Data

SBS MIS

SBS Quotation (Web Service - XML)Order (Web Service - XML)

MIS Manufacturing Timescales (Web Service - XML)

Technology Architecture Inventory

Technology Architecture Inventory (1)

79

TRM Domain: Software Engineering

S/N

Technical Category

Application Supported

Business Process Supported Business Owner Current Target

1Programming Language

Sales Record System (SRS)

Manage quotation and order Sales team C++ Java

2Run-Time Environment


Manage quotation and order Sales team -Application Server: JBoss 5.0


Inventory SystemManage the stock of the products and the raw materials

Order processing administrators and the manufacturing team

-Application Server: JBoss 5.0



Bill orders for customersOrder processing administrators

-Application Server: JBoss 5.0



Capture the details of raw materials and calculate the delivery time

Manufacturing team -Application Server: JBoss 5.0


Child-Wear Website

Display marketing literature Marketing and Sales team -Application Server: JBoss 5.0



Manage quotation and order Sales team PCHost Server: IBM System x3850 M2




PCHost Server: IBM System x3850 M2


80


S/N

Technical Category


Business Process Supported

Business Owner Current Target






Child-Wear Website

Display marketing literature

Marketing and Sales team




Manage quotation and order

Sales team -Brower: IE 4.0 + Mozilla Firefox 1.0




-Brower: IE 4.0 + Mozilla Firefox 1.0








Manufacturing team -Brower: IE 4.0 + Mozilla Firefox 1.0


Child-Wear Website







Sales team -JavaScript 1.1


81


S/N

Technical Category



Business OwnerCurrent

Target




-JavaScript 1.1



Bill orders for customers Order processing administrators -JavaScript 1.1




Manufacturing team - JavaScript 1.1


Child-Wear Website Display marketing literature Marketing and Sales team - JavaScript 1.1



Manage quotation and order Sales team - HTML: 4.0




- HTML: 4.0



Bill orders for customers Order processing administrators - HTML: 4.0




Manufacturing team - HTML: 4.0


Child-Wear Website Display marketing literature Marketing and Sales team - HTML: 4.0

82


TRM Domain: Data Management

S/N

Technical Category




26Data Dictionary / Repository



Sales team - Oracle 10g




- Oracle 10g




- Oracle 10g




Manufacturing team - Oracle 10g


Child-Wear Website



- Oracle 10g

83


TRM Domain: Security

S/N

Technical Category




31Identification and Authentication



Sales team - Single Sign On




- Single Sign On




- Single Sign On




Manufacturing team - Single Sign On


Child-Wear Website



- Single Sign On

84



S/NTechnical Category


Business Process Supported Business OwnerCurre

ntTarget

36Security Management


Manage quotation and order Sales team -Symantec AntiVirus




-Symantec AntiVirus




-Symantec AntiVirus




Manufacturing team -Symantec AntiVirus


Child-Wear Website Display marketing literature Marketing and Sales team -Symantec AntiVirus

85


S/N

Technical Category




41Non-Repudiation



Sales team - SSL, PKI

42Non-Repudiation



- SSL, PKI

43Non-Repudiation



- SSL, PKI

44Non-Repudiation



Manufacturing team - SSL, PKI

45Non-Repudiation

Child-Wear Website



- SSL, PKI


86


S/N

Technical Category




41Non-Repudiation



Sales team - SSL, PKI

42Non-Repudiation



- SSL, PKI

43Non-Repudiation



- SSL, PKI

44Non-Repudiation



Manufacturing team - SSL, PKI

45Non-Repudiation

Child-Wear Website



- SSL, PKI


TA Gap and Recommendation

Gaps and Recommendations (1)

88

ID Description Recommendation

1 Sales Record System (SRS) currently is written in C++. The target programming is Java

Re-write the application and integrate with Customer Billing System with Java.

2 The current application server for Sales Record System (SRS) is unknown. The target application server is JBoss 5.0.


3 The current application server for Inventory System is unknown. The target application server is JBoss 5.0.


4 The current application server for Customer Billing System is unknown. The target application server is JBoss 5.0.


5 The current application server for Manufacturing Planning System is unknown. The target application server is JBoss 5.0.


6 The current application server for Child-Wear Website is unknown. The target application server is JBoss 5.0.


7 Sales Record System (SRS) is currently running on a PC. The target host server is IBM System x3850 M2


8 Inventory System is currently running on a PC. The target host server is IBM System x3850 M2


9 Customer Billing System is currently running on a PC. The target host server is IBM System x3850 M2



89


10 Child-Wear Website is currently running on a PC. The target host server is IBM System x3850 M2


11 Currently whether Sales Record System (SRS) supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.

If it doesn’t, enhance the application to support Brower: IE 4.0 +. Mozilla Firefox 1.0

12 Currently whether Inventory System supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.


13 Currently whether Customer Billing System supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.


14 Currently whether Manufacturing Planning System supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.


15 Currently whether Child-Wear Website supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.


16 Currently whether Sales Record System (SRS) supports Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.

If it doesn’t, enhance the application to support JavaScript 1.1

17 Currently whether Inventory System supports JavaScript 1.1is not sure. The target is to support JavaScript 1.1


18 Currently whether Customer Billing System supports JavaScript 1.1is not sure. The target is to support JavaScript 1.1



90


19 Currently whether Manufacturing Planning System supports JavaScript 1.1 is not sure. The target is to support JavaScript 1.1


20Currently whether Child-Wear Website supports JavaScript 1.1 is not sure. The target is to support JavaScript 1.1


21 Currently whether Sales Record System (SRS) supports HTML 4.0 is not sure. The target is to support HTML 4.0

If it doesn’t, enhance the application to support HTML 4.0

22 Currently whether Inventory System supports HTML 4.0 is not sure. The target is to support HTML 4.0


23 Currently whether Customer Billing System supports Brower: IE 4.0 + is not sure. The target is to support HTML 4.0


24 Currently whether Manufacturing Planning System supports HTML 4.0 is not sure. The target is to support HTML 4.0


25 Currently whether Child-Wear Website supports HTML 4.0 is not sure. The target is to support HTML 4.0


26 Currently whether Sales Record System (SRS) is running on Oracle 10g is not sure. The target DBMS is Oracle 10g.

If it is not, migrate the DBMS to Oracle 10g.

27 Currently whether Inventory System is running on Oracle 10g is not sure. The target DBMS is Oracle 10g.



91


28 Currently whether Customer Billing System is running on Oracle 10g is not sure. The target DBMS is Oracle 10g.


29 Currently whether Manufacturing Planning System is running on Oracle 10g is not sure. The target DBMS is Oracle 10g.


30 Currently whether Child-Wear Website is running on Oracle 10g is not sure. The target DBMS is Oracle 10g.


31 Current Sales Record System (SRS) doesn’t support Single Sign On. The target TA requires Single Sign On to be built.

Build Single Sign On for the application.

32 Current Inventory System doesn’t support Single Sign On. The target TA requires Single Sign On to be built.


33 Current Customer Billing System doesn’t support Single Sign On. The target TA requires Single Sign On to be built.


34 Current Manufacturing Planning System doesn’t support Single Sign On. The target TA requires Single Sign On to be built.


35 Current Child-Wear Website doesn’t support Single Sign On. The target TA requires Single Sign On to be built.


36 Currently whether Sales Record System (SRS) is protected by Symantec AntiVirus is unknown. The target requires Symantec AntiVirus protection.

Build Symantec AntiVirus protection if the application is not being protected now.


92


37 Currently whether Inventory System is protected by Symantec AntiVirus is unknown. The target requires Symantec AntiVirus protection.


38 Currently whether Customer Billing System is protected by Symantec AntiVirus is unknown. The target requires Symantec AntiVirus protection.


39 Currently whether Manufacturing Planning System is protected by Symantec AntiVirus is unknown. The target requires Symantec AntiVirus protection.


40 Currently whether Child-Wear Website is protected by Symantec AntiVirus is unknown. The target requires Symantec AntiVirus protection.


41 Currently whether Non-Repudiation mechanism has been set up for Sales Record System (SRS) is unknown. The target is to set up Non-Repudiation mechanism for the application.

Setup Non-Repudiation mechanism if it hasn’t been setup for the application.

42 Currently whether Non-Repudiation mechanism has been set up for Inventory System is unknown. The target is to set up Non-Repudiation mechanism for the application.


43 Currently whether Non-Repudiation mechanism has been set up for Customer Billing System is unknown. The target is to set up Non-Repudiation mechanism for the application.


44 Currently whether Non-Repudiation mechanism has been set up for Manufacturing Planning System is unknown. The target is to set up Non-Repudiation mechanism for the application.


45 Currently whether Non-Repudiation mechanism has been set up for Child-Wear Website is unknown. The target is to set up Non-Repudiation mechanism for the application.


Child Wear Ea Blueprint V0.7

Business

target architecture

baseline architecture

enterprise asset

information available

sharing of information

shared enterprise vision

suppliers of child wear

overall suppliers