1. Team 7, ISS, NUS
Balaji Balasubramanian
Li Gang
Ruibo Zhang
Saranya Ranganathan
Sonia Sodhi
Vivek Raja Mani 1

2. Introduction
Child-Wear Vision & Mission
Overall Assumptions & Actors
Organization Structure
Scope & Goal of this Program
Architecture Vision & Principles
SWOT Analysis & Strategy Map
2

3. Performance Driven Governance Based Enterprise Architecture

4. Introduction
4

5. 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.

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

7. Human Actors
Customer
Supplier
Sales Staff
Order Processing Administrator
Manufacturing Team Member
Enterprise Architects
Senior Management Team Members
System Actors
Sales Record System
IT Team Members
Inventory System
Manufacturing Planning System
Account and Financial Information System
Human Resource System
Customer Billing System
Sales and Billing System
Manufacturing and Inventory System
7

8. 8

9. 9

10. 10

12. CEO
Enterprise Architecture Steering Committee
CIO
Establishes standards and offer
guidance aimed at sustaining
Chief Enterprise
Architect (Business the business objectives long
& Performance term. Also, accountable for
Architect) Performance of EA
Provide technology solutions
Information Solution & Technical
Architect Architect based on defined business
requirements. They are also
concerned with things at a
logical level as well as the
physical level
Responsible for establishing data quality
standards, data taxonomies and offering
input to how information is exchanged 12
internally and externally.

13. Enable 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

14. Define baseline architecture & propose target architecture for
Performance
Business
Information
Application
Technology
Define Architecture Governance & Management for
Implementation and Change
Facilitate a single view of the organization
14

15. Vision
Prepare a shared enterprise vision that describes “picture of desired future”
that is to be achieved
Improvise overall business service levels and productivity
Anytime, Anywhere, Always - Information Available ,Accessible, Useable
Principles
Deliver the most good to the broadest range of IT users
Implement Enterprise-wide EA. EA compliance for every program and project
The 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-making
Reduce integration and interoperability complexity and increase agility for
enterprise change
Reuse common solutions. Practice Modular Solutions 15

16. Business Architecture
Mission
Values
Vision
Strategy
Strategy Map
Balanced Scorecard
Targets & Initiatives
16

17. Strengths Weaknesses
Strong understanding of the current business Lack of protection for IT systems (such as viruses
processes with the suppliers of Child –Wear in email attachments causing hard disk
corruption)
Departments take responsibilities on their own
business processes and IT systems decisions No capitalization / usage of the the online
market exchanges and trade hubs, with
Strong understanding on overall suppliers selling fabrics at lower price
interrelationship between departments
(including business process workflows) Lack of integration of IT systems. The Sales /
Inventory and Manufacturing planning systems
Open for sharing of data (such as inventory are not well integrated with each other,
information) resulting in slow / delayed process of
communication and completion of orders
The manufacturing planning system available in-
house is stable and has not had any large down Missing standardization of business process
time (downtime <0.1%) 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

18. Opportunities Threats
To integrate the Child-Wear procurement Current IT system used by Child-Wear is a
system with Fabric.Net.sg using the ebXML standalone system and not integrated with
standard. suppliers / buyers available online
Lower procurement cost and compete with
competitors The AS400 system used for Manufacturing
To be able to receive quotations/orders via Planning system also runs other corporate
internet applications like Account and Financial system /
To provide tools / mechanisms to the sales team Human resource system, which may impact the
to be able to enter orders while being in the business critical application MPS
field
To 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 usage
To be able to develop / host and maintain a
secure high volume e-Business website

19. Long term Increase Cheaper and Quick
Reduction in
objectives Customer Base Suppliers
Operating Cost
Achieve internal business Take full advantage Use eBusiness
Internal process efficiency of Internet Mechanism
Invest in IT Systems revamping and consolidation
Organization Align Organization towards IT revamp
alignment
Learning the Benefits achieved from IT enablement
19

20. The 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 quot;anytime / anywherequot; 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

21. Marketing & Sales
Marketing Strategy & Increase Sales &
Sales Portfolio Sales Statistics
Plan Customer Base
Business Management Procurement & Manufacturing
Operations Product Lifecycle Sourcing
Management Management Strategy Inventory
Management
Time to Market Resource Efficient
Management Management Manufacturing
Customers Suppliers & Partners
Customer
Customer Sourcing Supplier
Satisfaction &
Problem Management Service Strategy Payment
Sourcing Supplier
Customer Order Customer Billing
Strategy Payment

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
23

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.
24

25. 25

26. Target State: Customer Order Fulfillment – Process Request for Quotation (RFQ) – Response
Process RFQ Resp. for Online RFQ Resp. for RFQ thru Sales Team Resp. to Cust. Proc. Sys.
Customer
Customer
Receive Receive
response to RFQ response to RFQ
Team Procurement
SalesTeam Procurement
Customer
Customer
System
System
Receive
response to RFQ
Receive
Response to RFQ
response to RFQ
Sales and Billing System (SBS) Storefront
Salesand Billing System (SBS) Storefront
System
Receive
System
Response to RFQ
Web
Web
response to RFQ
Receive
response on
product
availability
information
Calculate Price Response to RFQ
Sales
26

27. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
1. Revamp and Important to understand Define the processes IA
consolidate the difficulty to consolidate needed to understand the
Sales Record data from existing systems existing data; define data
System and principles, conceptual
Customer Billing model, logical model and
System into new Continuity of business metadata
centralized operations by users using
Sales and Billing new revamped system Define usability AA
System (SBS) requirements of
Important to understand applications
the improved performance
in capturing transaction Define the need of user BA,
training Governance
Define the design to cut
down the number of steps BA, AA
to capture transactions and
necessity to handle
exception cases
27

28. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
2. Revamp and Important to understand Define the processes IA
consolidate the difficulty to consolidate needed to understand the
Manufacturing data from existing systems existing data; define data
Planning System principles, conceptual
and Inventory model, logical model and
System into new metadata
centralized
Manufacturing Important to understand Define usability AA
and Inventory ease of use of application to requirements of
System (MIS) users applications
Continuity of business Define the need of user BA,
operations by users using training Governance
new revamped system
Important to understand Define the design to cut BA, AA
the improved performance down the number of steps
in capturing transaction to capture transactions and
necessity to handle
exception cases
28

29. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
3. Integration of Important to understand the Analyze the existing TA
SBS with MIS need of new technology technology for possible
through Web involve or reuse of existing reuse and requirement for
Services technology new technology for
bridging the gap
Important to understand the
need for security control Define policy for security TA
control
Important to understand
interfaces needed for
message passing Define the functionalities AA, IA
to be published and
messages to be passed
29

30. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
4. Allowing Important to understand the Define globalization design AA
customers to need of application to cross principle when developing
submit order different time zone and the applications
online through locale
new Web Cross platform testing shall
storefront and Important to understand be conducted AA
personalization that customers may use
of contents different browsers to access
the application
Ensure the conformance of
Important to understand security policy by TA
possible loss of implementing security
confidentiality, integrity of control
the data passing through
communication channel
30

31. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
5. Provision of Important to understand Define the necessary data IA, AA
Web Services to messages that need to flow for request and response
customers’ between communication passing, and define the
procurement standard format of the
systems message
Important to define the
number of services to be Define the necessary AA
published functionalities to be
published and plan for
future expansion for
inclusion of new
functionalities
Important to understand the
implication of security Define the security control TA
issues, confidentiality, mechanism to be
integrity and availability of implemented and imposed
both the customers’ on both the customers’
procurement systems and procurement systems and
Child-Wear system Child-Wear System
31

32. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
6. Collaboration Important to understand Understand the necessary IA, AA
with suppliers’ messages that need to flow data for request and
order systems between communication response passing, and the
through the their standard format of the
provided Web message
Services Important to understand the
number of services to be Understand the list of AA
consumed functionalities to be
consumed and plan for
future expansion for
consuming of new
functionalities
Important to understand the
implication of security Understand and implement TA
issues, confidentiality, the security control
integrity and availability of mechanism for
both the suppliers’ order communication between
systems and Child-Wear the suppliers’ order
system systems and Child-Wear
System
32

33. No. Identified Gaps Importance of Addressing Approach of Addressing Stage to Take
the Action
7. Cutting down the Important to understand Define clear organization Governance
need of how the new operation structure and the
coordination model requires responsibilities of each
between Sales restructuring of existing group
Team with Order organization
Processing
Administrator
and
Manufacturing
Team
8. Automatic billing Important to understand Define application and AA, TA
to customer how the automatic billings technology architectures
will cut down delay of billing for transmitting invoice to
cycles and technology used customers
across different type of
customers
33

34. Information Architecture

35. 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 levels
Easy 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.

36. Invoice
Id INTEGER
CustomerID INTEGER
ProductID INTEGER
Quantity INTEGER Inventory
Payment Details CHAR(500)
1
Id INTEGER
1
Item_ID INTEGER
QuantityInStock INTEGER
Quotation
1
Products
Id INTEGER
1 1..*
CustomerID INTEGER
Productid INTEGER Id INTEGER
Quantity INTEGER Description CHAR(50) PurchaseRequest
EstimatedValue INTEGER
1
Quantity INTEGER
EstimatedDate DATETIME
Status INTEGER
Id INTEGER
1 1 SupplierID INTEGER
ItemID INTEGER
Quantity INTEGER
1
1 1
0…*
0…*
Stakeholders
Authentication Items
Id INTEGER 1 1
CompanyName CHAR(10) Id INTEGER Id INTEGER
ContactPerson CHAR(10) Username CHAR(10) Description INTEGER
Address CHAR(10) password CHAR(10)
Type INTEGER Usertype CHAR(10)
SecondaryID INTEGER
1
Users 1
Sections
Id INTEGER 1 1 ID INTEGER
FirstName CHAR(10)
Name CHAR(10)
LastName CHAR(10)
Description CHAR(10)
Address CHAR(10)
ContactPersonUserID INTEGER
Department CHAR(10)

37. Entity Name Source Destination Frequency Format
Quotation Customer SBS Whenever the customer posts Web service request
a quotation
Invoice SBS Customer When the sales team keys in SOAP message/ MQ
Usage of WS-Security for web
the quotation Message
PurchaseRequest MIS Suppliers
services andManufacturing team SOAPwill MQ
When the
keys in the request forCertificates
X.509 raw message/
Message
largely cover the security aspect of
materials to the suppliers
Inventory SBS MIS
the system besidesneeds to
When the Sales team
check the current status of
SOAP message/ MQ
Message
encryption/decryption of the
stocks in the inventory
Authentication Users of the Child wear website Whenever any user of the queue service request
messages in message Web
system system needs to be
authenticated to enter the
system.
Sections SBS Section head When the contact person of SOAP message/ MQ
every section of the child Message
wear company needs to be
Identified
Products SBS MIS When the sales team needs to SOAP message/ MQ
check the details of the Message
existing stock details
Items Manufacturing MIS When the manufacturing team SOAP message/ MQ
team needs to check the details of Message
the existing inventory details.

38. 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

39. Quotation Stake Invoice Inventory Products Sections Purchase
S/N Process Holder 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 R U C
materials
3.2 Update the products list U

40. Process PurchaseReq
Quotation Stakeholder Invoice Inventory Products Items Sections uest
Customer I
Supplier I
Invoice I
Products I
Items I
Inventory I
New Data Architecture CR CR CR
I = Included CR-Create

41. Data 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
42

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.
43

46. Target Application Architecture
Current Application Architecture
Applications Sales & Billing Web Storefront Manufacturing and High Performance
System (SBS) (Part of SBS) Inventory System Child-wear
(MIS) 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

47. Service Oriented Architecture
Capability Maturity Model
Applying design Patterns and Framework

48. Technology Architecture
48

49. Qualities
Derived from
TOGAF TRM Infrastructure Applications Business Applications
Application Programming Interface
Transaction Processing
Software Engineering
Location & Directory
Data Management
System & Network
Data Interchange
User Interface
Management
Qualities
Qualities
Security
Operating System Services
Network Services
Communications Infrastructure Interface
Communication Infrastructure
Qualities
49

50. Separation of Concerns
Following the “Modularity” and “Abstraction” approach for the developing the
technical features.
Anticipation of Change
Changes is the “known unknowns” during the software engineering process, which
requires to be handled properly to be minimized the negative impact on Child-Wear.
Generality
The application designed and implemented should be free from unnatural restrictions
and limitations.
Consistency
Applications, projects, products and processes should keep consistent through the
whole organization to increase the reliability and decrease the complexity.
Follow Proper SE Methodology
Proper SE methodology can help Child-Wear to deliver the application successfully.
Systems and Network
All 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.

51. Security
The 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 Continuity
Transactions must roll back when the transaction fails and ensure business
continuity. Also, monitor performance of the system and network
continuously.

52. Feasibility 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.

53. RUP 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 Server
Browser: IE 4.0 +, Mozilla Firefox 1.0 HTML: 4.0 + Web 2.0
Script Support: JavaScript 1.1
Use 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 Security
Oracle 10g for Database
JDBC
Hibernate
XML for Webservices
Java Naming and Directory Interface (JNDI)
Lightweight Directory Access Protocol (LDAP)
SSL,PKI, Single Sign On

54. Software Engineering
Run-time Environment
Programming Language
Data Management
Data dictionary / Repository
Security
Identification and Authentication
Security Management
Non-Repudiation

55. Re-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. Target Technology Architecture
PKI Routers
SSL
Firewall Apache Firewall
Oracle 10g
Internet DMZ
JBoss
5.0
TZ
56

57. Technical Principles
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.
57

58. Best Practices
1 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
58

59. Technical Principles
1
2
3
Technology and Product Standards
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
59

60. Technical Service (6) – User Interface
1.User Interface
Technical Principles
1 Ease of Use
The User Interface must be user friendly.
2 Good Look and Feel
The User Interface must be implemented with good look and feel.
3 Consistency
The User Interface Design must be consistent through all the applications within Child-Wear.
Technology and Product Standards
1 Adobe Photoshop
2 Macromedia Dreamweaver
3 Macromedia Flash
4 Java Server Pages
60

61. Technical Service (6) – User Interface
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 61
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
62

63. Initiative Priority * Category
New 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
HIGH BA/IA/AA/TA
Web Store for retail and corporate customers for Ordering.
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, MEDIUM TA
Workstation's etc)
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
63

64. Governance
64

65. Child-Wear
Enterprise Architecture
Architecture
Governance &
Management Team
Sales & Business Analysis Manufacturing Finance Team Information
Marketing & Management & Technology
Team Team Procurement Team
65

66. 66

67. Business 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

68. Audience
EA Steering Committee, Enterprise Architects, ‘C’ Level executives, Line of Business owners, IT
team
Contents
Enterprise Architecture statements and implementation guidelines
The 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 communication
The 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 communication
The 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.

69. Measure magnitude and the impact of every proposed
change
Group & prioritize them as simple, incremental or re-
architecting
Approve them at Architecture Board level with consent
from Business.
The following steps are taken care before change is done:
1. Impact Analysis and evaluation
2. Resource allocation and management for architecture tasks
3. Risk evaluation

70. 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.

71. BA Process (Current)

72. Current State: Customer Order Fulfillment – Process Order
Process RFQ Process Order
Customer
Customer
Receive Receive product Receive invoice
Place order
response for RFQ
Customer Manufacturin Processing Sales Record Sales Team
System (SRS) Sales Team
Key in order Send order
Receive order
information request
Sales Record
Administrator System (SRS)
Store order
information
Administrator
Processing
Order
Order
Receive order
Bill Customer
request
Customer Manufacturin
Team
gTeam
Receive order Update Send product to
request inventory system customer
System
BillingSystem g
Bill Customer
Billing
72

73. Current State: Customer Order Fulfillment – Process Order
Process RFQ Process Order
Customer
Customer
Receive Receive product Receive invoice
Place order
response for RFQ
Customer Manufacturin Processing Sales Record Sales Team
System (SRS) Sales Team
Within 3 days of Y Key in order Send order
Receive order
RFQ response? information request
Refer to Receive RFQ N
Sales Record
Administrator System (SRS)
Store order
Print order
information
Administrator
Processing
Order
Order
Receive order
Bill Customer
request
Customer Manufacturin
Team
gTeam
Receive order Update Send product to
request inventory system customer
System
BillingSystem g
Bill Customer
Billing
73

74. Current State: Inventory Procurement
Process RFQ
Manufacturin
Manufacturin
Y
Receive enquiry Enquire ability to Receive response Calculate Response how
Estimate raw Check raw
g Team
g Team
on how quickly Raw materials supply raw on ability to supply product quickly product
materials materials
product can be available? materials raw materials manufacturing can be
needed availability
manufactured N information information timeline manufactured
Inventory
Inventory
System
Display raw
System
materials
availability
information
Supplier
Receive enquiry Response ability
Supplier
on ability to supply to supply raw
raw materials materials
information information
Manufacturin
Manufacturin
g Planning
g Planning
System
System
Display product
manufacturing
timeline
74

75. Application Architecture
Stake holders concerns and how the target architecture
addresses them

76. Interoperability between Sales Record System
(SRS) and Customer Billing System
Shared functions/ Services
Software Development for Sales and Billing
System (SBS)

77. Application Interoperability View
Captures the interoperability/ inter-dependency between
the applications
Application Consuming Data
Application SBS MIS
Producing SBS Quotation (Web Service -
Data XML)
Order (Web Service - XML)
MIS Manufacturing
Timescales (Web
Service - XML)
Common Application Services View
captures the services that are used across all or most of
the applications

78. Technology Architecture
Inventory

79. Technology Architecture Inventory (1)
TRM Domain: Software Engineering
S/ Technical Application
Category Business Process Supported Business Owner Current Target
N Supported
Programming Sales Record
1 Manage quotation and order Sales team C++ Java
Language System (SRS)
Run-Time Sales Record Application Server:
2 Manage quotation and order Sales team -
Environment System (SRS) JBoss 5.0
Order processing
Run-Time Manage the stock of the Application Server:
3 Inventory System administrators and the -
Environment products and the raw materials JBoss 5.0
manufacturing team
Run-Time Customer Billing Order processing Application Server:
4 Bill orders for customers -
Environment System administrators JBoss 5.0
Capture the details of raw
Run-Time Manufacturing Application Server:
5 materials and calculate the Manufacturing team -
Environment Planning System JBoss 5.0
delivery time
Run-Time Child-Wear Application Server:
6 Display marketing literature Marketing and Sales team -
Environment Website JBoss 5.0
Run-Time Sales Record Host Server: IBM
7 Manage quotation and order Sales team PC
Environment System (SRS) System x3850 M2
Order processing
Run-Time Manage the stock of the Host Server: IBM
8 Inventory System administrators and the PC
Environment products and the raw materials System x3850 M2
manufacturing team 79

80. Technology Architecture Inventory (1)
TRM Domain: Software Engineering
S/ Technical Application Business Process
Business Owner Current Target
N Category Supported Supported
Run-Time Customer Billing Order processing Host Server: IBM
9 Bill orders for customers PC
Environment System administrators System x3850 M2
Run-Time Child-Wear Display marketing Marketing and Sales Host Server: IBM
10 PC
Environment Website literature team System x3850 M2
Run-Time Sales Record Manage quotation and Brower: IE 4.0 +
11 Sales team -
Environment System (SRS) order Mozilla Firefox 1.0
Manage the stock of the Order processing
Run-Time Brower: IE 4.0 +
12 Inventory System products and the raw administrators and the -
Environment Mozilla Firefox 1.0
materials manufacturing team
Run-Time Customer Billing Order processing Brower: IE 4.0 +
13 Bill orders for customers -
Environment System administrators Mozilla Firefox 1.0
Capture the details of raw
Run-Time Manufacturing Brower: IE 4.0 +
14 materials and calculate the Manufacturing team -
Environment Planning System Mozilla Firefox 1.0
delivery time
Run-Time Child-Wear Display marketing Marketing and Sales Brower: IE 4.0 +
15 -
Environment Website literature team Mozilla Firefox 1.0
Run-Time Sales Record Manage quotation and JavaScript 1.1
16 Sales team -
Environment System (SRS) order
80

81. Technology Architecture Inventory (1)
TRM Domain: Software Engineering
S/ Technical Application Business Process Curr
Business Owner Target
N Category Supported Supported ent
Manage the stock of the JavaScript 1.1
Run-Time Order processing administrators
17 Inventory System products and the raw -
Environment and the manufacturing team
materials
Run-Time Customer Billing JavaScript 1.1
18 Bill orders for customers Order processing administrators -
Environment System
Capture the details of raw
Run-Time Manufacturing
19 materials and calculate the Manufacturing team - JavaScript 1.1
Environment Planning System
delivery time
Run-Time Display marketing
20 Child-Wear Website Marketing and Sales team - JavaScript 1.1
Environment literature
Run-Time Sales Record Manage quotation and
21 Sales team - HTML: 4.0
Environment System (SRS) order
Manage the stock of the
Run-Time Order processing administrators
22 Inventory System products and the raw - HTML: 4.0
Environment and the manufacturing team
materials
Run-Time Customer Billing
23 Bill orders for customers Order processing administrators - HTML: 4.0
Environment System
Capture the details of raw
Run-Time Manufacturing
24 materials and calculate the Manufacturing team - HTML: 4.0
Environment Planning System
delivery time
25
Run-Time
Child-Wear Website
Display marketing
Marketing and Sales team 81- HTML: 4.0
Environment literature

82. Technology Architecture Inventory (2)
TRM Domain: Data Management
S/ Technical Application Business Process
Business Owner Current Target
N Category Supported Supported
Data
Sales Record Manage quotation and
26 Dictionary / Sales team - Oracle 10g
System (SRS) order
Repository
Data Manage the stock of the Order processing
27 Dictionary / Inventory System products and the raw administrators and the - Oracle 10g
Repository materials manufacturing team
Data
Customer Billing Order processing
28 Dictionary / Bill orders for customers - Oracle 10g
System administrators
Repository
Data Capture the details of raw
Manufacturing
29 Dictionary / materials and calculate the Manufacturing team - Oracle 10g
Planning System
Repository delivery time
Data
Child-Wear Display marketing Marketing and Sales
30 Dictionary / - Oracle 10g
Website literature team
Repository
82

83. Technology Architecture Inventory (3)
TRM Domain: Security
S/ Technical Application Business Process
Business Owner Current Target
N Category Supported Supported
Identification
Sales Record Manage quotation and
31 and Sales team - Single Sign On
System (SRS) order
Authentication
Identification Manage the stock of the Order processing
32 and Inventory System products and the raw administrators and the - Single Sign On
Authentication materials manufacturing team
Identification
Customer Billing Order processing
33 and Bill orders for customers - Single Sign On
System administrators
Authentication
Identification Capture the details of raw
Manufacturing
34 and materials and calculate the Manufacturing team - Single Sign On
Planning System
Authentication delivery time
Identification
Child-Wear Display marketing Marketing and Sales
35 and - Single Sign On
Website literature team
Authentication
83

84. Technology Architecture Inventory (3)
TRM Domain: Security
Technical Application Curre
S/N Business Process Supported Business Owner Target
Category Supported nt
Security Sales Record System Symantec
36 Manage quotation and order Sales team -
Management (SRS) AntiVirus
Manage the stock of the Order processing
Security Symantec
37 Inventory System products and the raw administrators and the -
Management AntiVirus
materials manufacturing team
Security Customer Billing Order processing Symantec
38 Bill orders for customers -
Management System administrators AntiVirus
Capture the details of raw
Security Manufacturing Symantec
39 materials and calculate the Manufacturing team -
Management Planning System AntiVirus
delivery time
Security Symantec
40 Child-Wear Website Display marketing literature Marketing and Sales team -
Management AntiVirus
84

85. Technology Architecture Inventory (3)
TRM Domain: Security
S/ Technical Application Business Process
Business Owner Current Target
N Category Supported Supported
Non- Sales Record Manage quotation and
41 Sales team - SSL, PKI
Repudiation System (SRS) order
Manage the stock of the Order processing
Non-
42 Inventory System products and the raw administrators and the - SSL, PKI
Repudiation
materials manufacturing team
Non- Customer Billing Order processing
43 Bill orders for customers - SSL, PKI
Repudiation System administrators
Capture the details of raw
Non- Manufacturing
44 materials and calculate Manufacturing team - SSL, PKI
Repudiation Planning System
the delivery time
Non- Child-Wear Display marketing Marketing and Sales
45 - SSL, PKI
Repudiation Website literature team
85

86. Technology Architecture Inventory (3)
TRM Domain: Security
S/ Technical Application Business Process
Business Owner Current Target
N Category Supported Supported
Non- Sales Record Manage quotation and
41 Sales team - SSL, PKI
Repudiation System (SRS) order
Manage the stock of the Order processing
Non-
42 Inventory System products and the raw administrators and the - SSL, PKI
Repudiation
materials manufacturing team
Non- Customer Billing Order processing
43 Bill orders for customers - SSL, PKI
Repudiation System administrators
Capture the details of raw
Non- Manufacturing
44 materials and calculate Manufacturing team - SSL, PKI
Repudiation Planning System
the delivery time
Non- Child-Wear Display marketing Marketing and Sales
45 - SSL, PKI
Repudiation Website literature team
86

87. TA Gap and Recommendation

88. Gaps and Recommendations (1)
ID Description Recommendation
1 Sales Record System (SRS) currently is written in C++. The Re-write the application and integrate with Customer Billing
target programming is Java System with Java.
2 The current application server for Sales Record System (SRS) is Migrating the application to JBoss 5.0 if currently it is not
unknown. The target application server is JBoss 5.0. running on it.
3 The current application server for Inventory System is unknown. Migrating the application to JBoss 5.0 if currently it is not
The target application server is JBoss 5.0. running on it.
4 The current application server for Customer Billing System is Migrating the application to JBoss 5.0 if currently it is not
unknown. The target application server is JBoss 5.0. running on it.
5 The current application server for Manufacturing Planning Migrating the application to JBoss 5.0 if currently it is not
System is unknown. The target application server is JBoss 5.0. running on it.
6 The current application server for Child-Wear Website is Migrating the application to JBoss 5.0 if currently it is not
unknown. The target application server is JBoss 5.0. running on it.
7 Sales Record System (SRS) is currently running on a PC. The Migrating the application to host server IBM System x3850
target host server is IBM System x3850 M2 M2
8 Inventory System is currently running on a PC. The target host Migrating the application to host server IBM System x3850
server is IBM System x3850 M2 M2
9 Customer Billing System is currently running on a PC. The target Migrating the application to host server IBM System x3850
host server is IBM System x3850 M2 M2
88

89. Gaps and Recommendations (2)
ID Description Recommendation
10 Child-Wear Website is currently running on a PC. The target host Migrating the application to host server IBM System x3850
server is IBM System x3850 M2 M2
11 Currently whether Sales Record System (SRS) supports Brower: If it doesn‟t, enhance the application to support Brower: IE
IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +. 4.0 +. Mozilla Firefox 1.0
12 Currently whether Inventory System supports Brower: IE 4.0 + is If it doesn‟t, enhance the application to support Brower: IE
not sure. The target is to support Brower: IE 4.0 +. 4.0 +. Mozilla Firefox 1.0
13 Currently whether Customer Billing System supports Brower: IE If it doesn‟t, enhance the application to support Brower: IE
4.0 + is not sure. The target is to support Brower: IE 4.0 +. 4.0 +. Mozilla Firefox 1.0
14 Currently whether Manufacturing Planning System supports If it doesn‟t, enhance the application to support Brower: IE
Brower: IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +. Mozilla Firefox 1.0
4.0 +.
15 Currently whether Child-Wear Website supports Brower: IE 4.0 + If it doesn‟t, enhance the application to support Brower: IE
is not sure. The target is to support Brower: IE 4.0 +. 4.0 +. Mozilla Firefox 1.0
16 Currently whether Sales Record System (SRS) supports Brower: If it doesn‟t, enhance the application to support JavaScript 1.1
IE 4.0 + is not sure. The target is to support Brower: IE 4.0 +.
17 Currently whether Inventory System supports JavaScript 1.1is not If it doesn‟t, enhance the application to support JavaScript 1.1
sure. The target is to support JavaScript 1.1
18 Currently whether Customer Billing System supports JavaScript If it doesn‟t, enhance the application to support JavaScript 1.1
1.1is not sure. The target is to support JavaScript 1.1
89

90. Gaps and Recommendations (3)
ID Description Recommendation
19 Currently whether Manufacturing Planning System supports If it doesn‟t, enhance the application to
JavaScript 1.1 is not sure. The target is to support JavaScript 1.1 support JavaScript 1.1
20 If it doesn‟t, enhance the application to
Currently whether Child-Wear Website supports JavaScript 1.1 is
support JavaScript 1.1
not sure. The target is to support JavaScript 1.1
21 Currently whether Sales Record System (SRS) supports HTML 4.0 If it doesn‟t, enhance the application to
is not sure. The target is to support HTML 4.0 support HTML 4.0
22 Currently whether Inventory System supports HTML 4.0 is not sure. If it doesn‟t, enhance the application to
The target is to support HTML 4.0 support HTML 4.0
23 Currently whether Customer Billing System supports Brower: IE If it doesn‟t, enhance the application to
4.0 + is not sure. The target is to support HTML 4.0 support HTML 4.0
24 Currently whether Manufacturing Planning System supports HTML If it doesn‟t, enhance the application to
4.0 is not sure. The target is to support HTML 4.0 support HTML 4.0
25 Currently whether Child-Wear Website supports HTML 4.0 is not If it doesn‟t, enhance the application to
sure. The target is to support HTML 4.0 support HTML 4.0
26 Currently whether Sales Record System (SRS) is running on Oracle If it is not, migrate the DBMS to Oracle 10g.
10g is not sure. The target DBMS is Oracle 10g.
27 Currently whether Inventory System is running on Oracle 10g is If it is not, migrate the DBMS to Oracle 10g.
not sure. The target DBMS is Oracle 10g.
90

91. Gaps and Recommendations (4)
ID Description Recommendation
28 Currently whether Customer Billing System is running on Oracle 10g is If it is not, migrate the DBMS to Oracle 10g.
not sure. The target DBMS is Oracle 10g.
29 Currently whether Manufacturing Planning System is running on Oracle If it is not, migrate the DBMS to Oracle 10g.
10g is not sure. The target DBMS is Oracle 10g.
30 Currently whether Child-Wear Website is running on Oracle 10g is not sure. If it is not, migrate the DBMS to Oracle 10g.
The target DBMS is Oracle 10g.
31 Current Sales Record System (SRS) doesn‟t support Single Sign On. The Build Single Sign On for the application.
target TA requires Single Sign On to be built.
32 Current Inventory System doesn‟t support Single Sign On. The target TA Build Single Sign On for the application.
requires Single Sign On to be built.
33 Current Customer Billing System doesn‟t support Single Sign On. The Build Single Sign On for the application.
target TA requires Single Sign On to be built.
34 Current Manufacturing Planning System doesn‟t support Single Sign On. Build Single Sign On for the application.
The target TA requires Single Sign On to be built.
35 Current Child-Wear Website doesn‟t support Single Sign On. The target TA Build Single Sign On for the application.
requires Single Sign On to be built.
36 Currently whether Sales Record System (SRS) is protected by Symantec Build Symantec AntiVirus protection if the
AntiVirus is unknown. The target requires Symantec AntiVirus protection. application is not being protected now.
91

92. Gaps and Recommendations (5)
ID Description Recommendation
37 Currently whether Inventory System is protected by Symantec AntiVirus is unknown. Build Symantec AntiVirus protection if the
The target requires Symantec AntiVirus protection. application is not being protected now.
38 Currently whether Customer Billing System is protected by Symantec AntiVirus is Build Symantec AntiVirus protection if the
unknown. The target requires Symantec AntiVirus protection. application is not being protected now.
39 Currently whether Manufacturing Planning System is protected by Symantec AntiVirus Build Symantec AntiVirus protection if the
is unknown. The target requires Symantec AntiVirus protection. application is not being protected now.
40 Currently whether Child-Wear Website is protected by Symantec AntiVirus is unknown. Build Symantec AntiVirus protection if the
The target requires Symantec AntiVirus protection. application is not being protected now.
41 Currently whether Non-Repudiation mechanism has been set up for Sales Record Setup Non-Repudiation mechanism if it
System (SRS) is unknown. The target is to set up Non-Repudiation mechanism for the hasn‟t been setup for the application.
application.
42 Currently whether Non-Repudiation mechanism has been set up for Inventory System Setup Non-Repudiation mechanism if it
is unknown. The target is to set up Non-Repudiation mechanism for the application. hasn‟t been setup for the application.
43 Currently whether Non-Repudiation mechanism has been set up for Customer Billing Setup Non-Repudiation mechanism if it
System is unknown. The target is to set up Non-Repudiation mechanism for the hasn‟t been setup for the application.
application.
44 Currently whether Non-Repudiation mechanism has been set up for Manufacturing Setup Non-Repudiation mechanism if it
Planning System is unknown. The target is to set up Non-Repudiation mechanism for hasn‟t been setup for the application.
the application.
45 Currently whether Non-Repudiation mechanism has been set up for Child-Wear Setup Non-Repudiation mechanism if it
Website is unknown. The target is to set up Non-Repudiation mechanism for the hasn‟t been setup for the application.
application.
92