Portfolio 1.1. Main problems for the organisation. The

Added on - 23 Sep 2019

  • 11

    pages

  • 2789

    words

  • 57

    views

  • 0

    downloads

Showing pages 4 of 11
Portfolio 1.1Main problems for the organisationThe main problem of Johnson and Johnson is the complex business environment, Adecentralised company with a group of 150 company and the managers are answerable for theresults of their companies and customer facing difficulties while dealing with multipleinvoices and the contract with the operating companies, because the legacy technologyunable to support the business going forward. There is no standards and decentralised IT.Solutions we propose to solve these problemsFor the Johnson and Johnson case study I am going to propose Zachman Framework to solvethese problems. Zachman Framework organises the existing functions, existing elements andprocesses.Zachman FrameworkZachman Framework is a two dimensional scheme for expressive depictions of anEnterprise.Most of the methodology is organised in the development phase but Zachmanframework organised the organisation of view taken by the various playerTheZachmanframework provide the responses of “What”, “How”, “Who” and “Where”across dimensions – Business Requirements, Conceptual Model, Logical or Physical Modeland Actual Implementation.In theJohnson and Johnson case study Zachmanframework associate the business, process,people and technology. Each cell has to be documented in detail and information is gatheredby questionnaires (subjective and objective).Followings are the Zachman Framework which is used forJohnson and Johnson case study tosolve these problems:Data (What)TechnicalArchitecture(How)People(Who)Infrastructure(Where)BusinessRequirementsInformationRequirementsDataprocessingneeds ofbusinessBusinessUserBusinessapplicationConceptualModelConceptualOverviewDatainformationand AnalysisUserCommunityModellingtools anddocumentationLogical orPhysical ModelPhysicaloverviewApplicationarchitectureand reportingenvironmentDataModeller andDBASystemarchitectureand geologicallocation ofsystemImplementationPhysicalInfrastructureETLProcessingDevelopmentandHostingrequirements
andReportingInfrastructuremaintenanceTeamPortfolio 1.2Followings are the process which is proposed for EA:Enterprise Architecture Compliance ProcessEnterprise Architecture Governance ProcessProject Engagement ProcessEnterprise Architecture Management ProcessCompare the frameworks for EA- Zachman, TOGAF, FEA, and GartnerComparison table with some criteria:1.Does very good job in this area2.Does an inadequate job in this area3.Does poor job in this area4.Does acceptable job in this areaCriteriaRatingZachmanTOGAFFEAGartnerCompleteness ofTaxonomy1223Processcompleteness3124Practiceguidance3221Business Focus3231Informationavailability2123Time to value3431Relationship between EA and SOA:The simple relationship between EA and SOA is like a contractorand electrician or plumberwho helps to design a structure and maybe physically build it. The Enterprise Architectprovides the basic design from the standpoint, functionality and resource allocation, while the
SOA bring the exact services and ensure the operation. Generally SOA is used to build abetter IT organization, and EA provide the process and approach.Portfolio 1.3Milk dairyQuikfix ElectronicsPortfolio 1.4
Week-3:1. Followings are the value that enterprise architecture program delivers:Guidance: It identifies the core competencies and the priorities of business. It provides theway how to create and manage the technology portfolios. How we can rationalize the existingsystem and how to deduct cost and redundancy.Control: Enterprise Architecture addresses all affected areas and reduces the risk2. Followings are the risk associated with implementing an EA program:1.Lack of understandingThe adoption rate of EA is very low, because the stakeholders do not participate in theEA program.2.User acceptance level low3.Solution Cost is high4. Security vulnerabilities and exposures3. The management translate the vision and strategy into strategic goalsthe plans will supportthese goals is significant business practice that need to take intellect from the business andICT specialists. Interpreting these goals into variations to the business processes, everydayprocesses and ICT schemes are where Enterprise Architecture provides real value.4.Enterprise architecture (EA) is an exercise of analysing, designing, planning andimplementing enterprise analysis to effectively perform on business tactics. It helpsbusinesses organization IT projects and policies to achieve chosen business results.5.EA develop business and IT association by producing a mutual appreciative of businessstrategy between IT and business departments, it articulate how the technology can drive thebusiness strategy. It optimises the technology and ensure for best business results and in stepwith new technology.6.When we work on a project we are confident that our project will definitely success, butthere is always a possibility of failure. When the things might go wrong is called the risk, andin project management team identifies it early in the beginning of the project. So the projectmanagement team can do some possible things.Followings are the two method of manage risk:Mitigate the Risk: Here we bound the effect of risk, so that when it occur the difficulties islesser and easy to solve.Exploit the Risk: here we look for the way to mark the risk occurs so we can train the peoplefor future use.7. The EA closing the space between IT departments and business units, EnterpriseArchitecture begins the relations between strategy and structures, processes, databases, and