Loading ...
Sorry, an error occurred while loading the content.

Re: Hardin offers SOA Resources

Expand Messages
  • JP
    ... This is a spec for a software architect or engineer. When will people learn if you want to hire an architect the specification needs to meet the challenge,
    Message 1 of 4 , Jul 1 6:48 AM
    • 0 Attachment
      I'm quite concerned about the job description for SOA Enterprise Architect:

      > *Job Description: SOA Enterprise Architect:*
      > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
      > This job description from G.1440 will give you a good idea of the
      > technical skills required for a wide-ranging SOA implementation. Some
      > examples:
      >
      > * Familiarity with high-level languages such as BPEL and
      > specifications such as WS-CDL and WS-Coordination.
      > * Understanding of the Enterprise Service Bus approach, including
      > IBM ESB.
      > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
      > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
      > InterTest, JES Tools, Control--M Products Tools.>>
      >

      This is a spec for a software architect or engineer. When will people learn if you want to hire an architect the specification needs to meet the challenge, such as:

      * Ability to quickly identify patterns across existing systems
      * Diverse set of experiences in IT to pull upon to help in problem identification and resolution
      * Ability to define governance frameworks for projects and be able to gain cooperation from team members to follow
      * Past experiences designing and operating systems that meet the following criteria [put criteria of systems you want this person to help design around in your particular opportunity]
      * Ability to communicate fluently with engineering regarding topics related to security, integration, systems, etc.

      These are just some examples, but I believe the point is made.

      JP

      --- In service-orientated-architecture@yahoogroups.com, Gervas Douglas <gervas.douglas@...> wrote:
      >
      > <<More than three-quarters of businesses that have implemented or are
      > working on service-oriented architecture said they are happy with the
      > results in a recent Forrester Research survey. However, only 31 percent
      > of the same group said they had realized all the benefits they expected
      > from SOA.
      >
      > Apparently some folks are easy to please.
      >
      > Or, as our Loraine Lawson notes in her *great ongoing coverage of SOA
      > and integration issues
      > <http://www.itbusinessedge.com/cm/blogs/lawson/soa-wheres-the-respect/?cs=47514>*,
      > it may well be that shops have simply lost sight of the strategic
      > virtues of SOA across the enterprise and now look at it more as a
      > single-use project that they can be "happy" with, at least on a tactical
      > level.
      >
      > Of course, that's not what SOA is supposed to be about. It's an
      > architecture that promises re-use of services across virtually any
      > business process, either inside or outside your enterprise.
      >
      > Here in the IT Downloads library, we have numerous resources to help you
      > evaluate the SOA fit for your organization and to guide you in both the
      > tactical and strategic implementation of SOA in your shop. All of these
      > resources are available for free download to IT Business Edge members.
      >
      > *'SOA Governance' Excerpt*
      > <http://www.itbusinessedge.com/itdownloads/soa-governance-excerpt/89937>: This
      > 30-page book excerpt from our partners at InformIT focuses on the
      > often-overlooked differences between governance, methodology and
      > management, with little pearls of wisdom such as:
      >
      > * Governance does not dictate when or how to make a decision. It
      > determines who should make the decision and establishes limits for
      > that person or group.
      > * Management makes decisions according to governance rules.
      > * Neither management nor methodology can replace governance, nor
      > compensate for poor governance.
      >
      > These issues are fundamental to SOA reaching its full potential, since
      > as an architecture it spans development teams and business units. It has
      > to be based on a strong culture of governance, or it will fragment and
      > become nothing more than a methodology.
      >
      > The book chapter also includes numerous chart and diagrams, like this
      > scale chart that rates the Autonomy and Control of various governance
      > cultures.
      >
      > <http://img.itbe.com/reports/images/ed/hardin20110624-01.png>
      >
      > *The SOA Source Book Excerpt:
      > <http://www.itbusinessedge.com/itdownloads/soa-source-book-excerpt/88772>*
      > This IT Download from our partners at The Open Group lays out the basic
      > principles of SOA in terms that both IT and business execs can readily
      > grasp.
      >
      > This 7-page document lays out 14 key benefits of SOA and the
      > infrastructure needed to support them. You can see a portion of a quick
      > overview table below.
      >
      > <http://img.itbe.com/reports/images/ed/hardin20110624-02.png>
      >
      > Topics covered include:
      >
      > * Developing software "facades" via asset wrapping that help
      > recognize all IT components as providing a service.
      > * Implementing a services directory as opposed to hard-wiring
      > service calls.
      > * Encrypting service messages to ensure enterprise data security.
      >
      > *Job Description: SOA Enterprise Architect:*
      > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
      > This job description from G.1440 will give you a good idea of the
      > technical skills required for a wide-ranging SOA implementation. Some
      > examples:
      >
      > * Familiarity with high-level languages such as BPEL and
      > specifications such as WS-CDL and WS-Coordination.
      > * Understanding of the Enterprise Service Bus approach, including
      > IBM ESB.
      > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
      > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
      > InterTest, JES Tools, Control--M Products Tools.>>
      >
      > *You can find this at:
      > http://www.itbusinessedge.com/cm/blogs/itdownloads/be-really-happy-with-your-soa-efforts-thanks-to-these-resources/?cs=47548&utm_source=itbe&utm_medium=email&utm_campaign=EEB&nr=EEB
      >
      > Gervas*
      >
    • Michael Poulin
      I agree with JP. The extract from the  *Job Description: SOA Enterprise Architect:* shows that the writer has very little, if any, understanding about both -
      Message 2 of 4 , Jul 9 2:32 PM
      • 0 Attachment
        I agree with JP.

        The extract from the  *Job Description: SOA Enterprise Architect:* shows that the writer has very little, if any, understanding about both - service orientation and architecture. The job description is for Integration specialist, not for SOA Architect. 

        - Michael


        From: JP <jpmorgenthal@...>
        To: service-orientated-architecture@yahoogroups.com
        Sent: Friday, July 1, 2011 2:48 PM
        Subject: [service-orientated-architecture] Re: Hardin offers SOA Resources

         
        I'm quite concerned about the job description for SOA Enterprise Architect:

        > *Job Description: SOA Enterprise Architect:*
        > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
        > This job description from G.1440 will give you a good idea of the
        > technical skills required for a wide-ranging SOA implementation. Some
        > examples:
        >
        > * Familiarity with high-level languages such as BPEL and
        > specifications such as WS-CDL and WS-Coordination.
        > * Understanding of the Enterprise Service Bus approach, including
        > IBM ESB.
        > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
        > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
        > InterTest, JES Tools, Control--M Products Tools.>>
        >

        This is a spec for a software architect or engineer. When will people learn if you want to hire an architect the specification needs to meet the challenge, such as:

        * Ability to quickly identify patterns across existing systems
        * Diverse set of experiences in IT to pull upon to help in problem identification and resolution
        * Ability to define governance frameworks for projects and be able to gain cooperation from team members to follow
        * Past experiences designing and operating systems that meet the following criteria [put criteria of systems you want this person to help design around in your particular opportunity]
        * Ability to communicate fluently with engineering regarding topics related to security, integration, systems, etc.

        These are just some examples, but I believe the point is made.

        JP

        --- In service-orientated-architecture@yahoogroups.com, Gervas Douglas <gervas.douglas@...> wrote:
        >
        > <<More than three-quarters of businesses that have implemented or are
        > working on service-oriented architecture said they are happy with the
        > results in a recent Forrester Research survey. However, only 31 percent
        > of the same group said they had realized all the benefits they expected
        > from SOA.
        >
        > Apparently some folks are easy to please.
        >
        > Or, as our Loraine Lawson notes in her *great ongoing coverage of SOA
        > and integration issues
        > <http://www.itbusinessedge.com/cm/blogs/lawson/soa-wheres-the-respect/?cs=47514>*,
        > it may well be that shops have simply lost sight of the strategic
        > virtues of SOA across the enterprise and now look at it more as a
        > single-use project that they can be "happy" with, at least on a tactical
        > level.
        >
        > Of course, that's not what SOA is supposed to be about. It's an
        > architecture that promises re-use of services across virtually any
        > business process, either inside or outside your enterprise.
        >
        > Here in the IT Downloads library, we have numerous resources to help you
        > evaluate the SOA fit for your organization and to guide you in both the
        > tactical and strategic implementation of SOA in your shop. All of these
        > resources are available for free download to IT Business Edge members.
        >
        > *'SOA Governance' Excerpt*
        > <http://www.itbusinessedge.com/itdownloads/soa-governance-excerpt/89937>: This
        > 30-page book excerpt from our partners at InformIT focuses on the
        > often-overlooked differences between governance, methodology and
        > management, with little pearls of wisdom such as:
        >
        > * Governance does not dictate when or how to make a decision. It
        > determines who should make the decision and establishes limits for
        > that person or group.
        > * Management makes decisions according to governance rules.
        > * Neither management nor methodology can replace governance, nor
        > compensate for poor governance.
        >
        > These issues are fundamental to SOA reaching its full potential, since
        > as an architecture it spans development teams and business units. It has
        > to be based on a strong culture of governance, or it will fragment and
        > become nothing more than a methodology.
        >
        > The book chapter also includes numerous chart and diagrams, like this
        > scale chart that rates the Autonomy and Control of various governance
        > cultures.
        >
        > <http://img.itbe.com/reports/images/ed/hardin20110624-01.png>
        >
        > *The SOA Source Book Excerpt:
        > <http://www.itbusinessedge.com/itdownloads/soa-source-book-excerpt/88772>*
        > This IT Download from our partners at The Open Group lays out the basic
        > principles of SOA in terms that both IT and business execs can readily
        > grasp.
        >
        > This 7-page document lays out 14 key benefits of SOA and the
        > infrastructure needed to support them. You can see a portion of a quick
        > overview table below.
        >
        > <http://img.itbe.com/reports/images/ed/hardin20110624-02.png>
        >
        > Topics covered include:
        >
        > * Developing software "facades" via asset wrapping that help
        > recognize all IT components as providing a service.
        > * Implementing a services directory as opposed to hard-wiring
        > service calls.
        > * Encrypting service messages to ensure enterprise data security.
        >
        > *Job Description: SOA Enterprise Architect:*
        > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
        > This job description from G.1440 will give you a good idea of the
        > technical skills required for a wide-ranging SOA implementation. Some
        > examples:
        >
        > * Familiarity with high-level languages such as BPEL and
        > specifications such as WS-CDL and WS-Coordination.
        > * Understanding of the Enterprise Service Bus approach, including
        > IBM ESB.
        > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
        > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
        > InterTest, JES Tools, Control--M Products Tools.>>
        >
        > *You can find this at:
        > http://www.itbusinessedge.com/cm/blogs/itdownloads/be-really-happy-with-your-soa-efforts-thanks-to-these-resources/?cs=47548&utm_source=itbe&utm_medium=email&utm_campaign=EEB&nr=EEB
        >
        > Gervas*
        >



      • Ashraf Galal
        General Schwarzkopf once observed Leadership is a potent combination of strategy and character. But if you must be without one, be without the strategy. IT
        Message 3 of 4 , Jul 10 10:24 AM
        • 0 Attachment
          General Schwarzkopf once observed " Leadership is a potent combination of strategy and character. But if you must be without one, be without the strategy."

          IT Executives work to align IT and IT-enabled business processes with stated business strategy.
          But business-IT strategic alignment can be an elusive goal.
          Strategies rarely offers clear direction for development of stable IT infrastructure and business process capabilities.
          To best support a company's strategy, it is recommended by Jeanne Ross and her collegues, that the company defines an operating model.

          "An Operating model is the necessary level of business process integration and standardization for delivering goods and services to customers.
          Integration and standardization are key dimensions of an operating model.
          Standardization of business processes and related systems means defining exactly how a prcoess will be executed regardless of who is performing the process or where it is completed.
          the result of standardization, a reduction in variability; can be dramatic increase in throughput and efficiency.
          Standardization has cost to pay for.
          Integration links efforts of organizational units through shared data.
          This sharing of data can be between processesto enable end-to-end transaction processing or across processes to allow the company to present a single face to customers.
          the benefits of integration include increase efficiency, cooperation, transparency, and agility.
          Integration has cost to pay for too. "


          From business perspective, not from an IT, business and integration must be considered as two separate decisions.
          The integration is part of the business before considering it part of IT.
          If we follow SOA principles and constraints, then we can call it SOA architect.
          If we follow other architecture, then we can call it Integration architect. 

          All the best

          Ashraf Galal



          to best support a company's 
          On 09/07/2011 5:32 PM, Michael Poulin wrote:  
          I agree with JP.

          The extract from the  *Job Description: SOA Enterprise Architect:* shows that the writer has very little, if any, understanding about both - service orientation and architecture. The job description is for Integration specialist, not for SOA Architect. 

          - Michael


          From: JP <jpmorgenthal@...>
          To: service-orientated-architecture@yahoogroups.com
          Sent: Friday, July 1, 2011 2:48 PM
          Subject: [service-orientated-architecture] Re: Hardin offers SOA Resources

           
          I'm quite concerned about the job description for SOA Enterprise Architect:

          > *Job Description: SOA Enterprise Architect:*
          > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
          > This job description from G.1440 will give you a good idea of the
          > technical skills required for a wide-ranging SOA implementation. Some
          > examples:
          >
          > * Familiarity with high-level languages such as BPEL and
          > specifications such as WS-CDL and WS-Coordination.
          > * Understanding of the Enterprise Service Bus approach, including
          > IBM ESB.
          > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
          > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
          > InterTest, JES Tools, Control--M Products Tools.>>
          >

          This is a spec for a software architect or engineer. When will people learn if you want to hire an architect the specification needs to meet the challenge, such as:

          * Ability to quickly identify patterns across existing systems
          * Diverse set of experiences in IT to pull upon to help in problem identification and resolution
          * Ability to define governance frameworks for projects and be able to gain cooperation from team members to follow
          * Past experiences designing and operating systems that meet the following criteria [put criteria of systems you want this person to help design around in your particular opportunity]
          * Ability to communicate fluently with engineering regarding topics related to security, integration, systems, etc.

          These are just some examples, but I believe the point is made.

          JP

          --- In service-orientated-architecture@yahoogroups.com, Gervas Douglas <gervas.douglas@...> wrote:
          >
          > <<More than three-quarters of businesses that have implemented or are
          > working on service-oriented architecture said they are happy with the
          > results in a recent Forrester Research survey. However, only 31 percent
          > of the same group said they had realized all the benefits they expected
          > from SOA.
          >
          > Apparently some folks are easy to please.
          >
          > Or, as our Loraine Lawson notes in her *great ongoing coverage of SOA
          > and integration issues
          > <http://www.itbusinessedge.com/cm/blogs/lawson/soa-wheres-the-respect/?cs=47514>*,
          > it may well be that shops have simply lost sight of the strategic
          > virtues of SOA across the enterprise and now look at it more as a
          > single-use project that they can be "happy" with, at least on a tactical
          > level.
          >
          > Of course, that's not what SOA is supposed to be about. It's an
          > architecture that promises re-use of services across virtually any
          > business process, either inside or outside your enterprise.
          >
          > Here in the IT Downloads library, we have numerous resources to help you
          > evaluate the SOA fit for your organization and to guide you in both the
          > tactical and strategic implementation of SOA in your shop. All of these
          > resources are available for free download to IT Business Edge members.
          >
          > *'SOA Governance' Excerpt*
          > <http://www.itbusinessedge.com/itdownloads/soa-governance-excerpt/89937>: This
          > 30-page book excerpt from our partners at InformIT focuses on the
          > often-overlooked differences between governance, methodology and
          > management, with little pearls of wisdom such as:
          >
          > * Governance does not dictate when or how to make a decision. It
          > determines who should make the decision and establishes limits for
          > that person or group.
          > * Management makes decisions according to governance rules.
          > * Neither management nor methodology can replace governance, nor
          > compensate for poor governance.
          >
          > These issues are fundamental to SOA reaching its full potential, since
          > as an architecture it spans development teams and business units. It has
          > to be based on a strong culture of governance, or it will fragment and
          > become nothing more than a methodology.
          >
          > The book chapter also includes numerous chart and diagrams, like this
          > scale chart that rates the Autonomy and Control of various governance
          > cultures.
          >
          > <http://img.itbe.com/reports/images/ed/hardin20110624-01.png>
          >
          > *The SOA Source Book Excerpt:
          > <http://www.itbusinessedge.com/itdownloads/soa-source-book-excerpt/88772>*
          > This IT Download from our partners at The Open Group lays out the basic
          > principles of SOA in terms that both IT and business execs can readily
          > grasp.
          >
          > This 7-page document lays out 14 key benefits of SOA and the
          > infrastructure needed to support them. You can see a portion of a quick
          > overview table below.
          >
          > <http://img.itbe.com/reports/images/ed/hardin20110624-02.png>
          >
          > Topics covered include:
          >
          > * Developing software "facades" via asset wrapping that help
          > recognize all IT components as providing a service.
          > * Implementing a services directory as opposed to hard-wiring
          > service calls.
          > * Encrypting service messages to ensure enterprise data security.
          >
          > *Job Description: SOA Enterprise Architect:*
          > <http://www.itbusinessedge.com/itdownloads/job-description-soa-enterprise-architect/88771>
          > This job description from G.1440 will give you a good idea of the
          > technical skills required for a wide-ranging SOA implementation. Some
          > examples:
          >
          > * Familiarity with high-level languages such as BPEL and
          > specifications such as WS-CDL and WS-Coordination.
          > * Understanding of the Enterprise Service Bus approach, including
          > IBM ESB.
          > * Experience with JCL, TSO, ISPF, ENDEVOR, IDMS, EXPEDITOR,
          > ABEND-AID for CICS, DB2, File--AID, MVS Tools, SQL, VSAM,
          > InterTest, JES Tools, Control--M Products Tools.>>
          >
          > *You can find this at:
          > http://www.itbusinessedge.com/cm/blogs/itdownloads/be-really-happy-with-your-soa-efforts-thanks-to-these-resources/?cs=47548&utm_source=itbe&utm_medium=email&utm_campaign=EEB&nr=EEB
          >
          > Gervas*
          >




        Your message has been successfully submitted and would be delivered to recipients shortly.