Write a minimum 3-page document that compares and contrasts system technical arc

Question

Write a minimum 3-page document that compares and contrasts system technical architecture with IT enterprise architecture. Answer the following questions:

1) What, in your own words, is System Technical Architecture? How does it relate to what has been taught in this course?

2) What, in your own words, is IT Enterprise Architecture?

3) Describe the most important goals of system technical architecture?

4) Describe the most important goals of IT Enterprise Architecture?

5) What skills are critical for a successful system technical architect vs. a successful IT Enterprise Architect?

6) What types of companies might benefit from having IT Enterprise Architects on their staff. Does every company with IT products need Enterprise Architects? Why or why not?

Explanation / Answer

1. System Technical Architecture:

A system architecture is an applied model that characterizes the structure, conduct, and more perspectives of a system.An engineering portrayal is a formal depiction and portrayal of a framework, composed in a way that backings thinking about the structures and practices of the framework.

A system architecture design can involve framework parts that will cooperate to actualize the general framework. There have been endeavors to formalize dialects to portray framework engineering, all things considered these are called design depiction dialects (ADLs).

2. IT Enterprise Architecture Design:

IT Enterprise Architecture Design can be viewed as a plan for the ideal and target-conformant position of assets in the IT condition for a definitive support of the business work. As depicted in American National Standards Institute/Institute of Electrical and Electronics Engineers (, an engineering is "the major association of a framework, epitomized in its parts, their connections to each other and nature, and the standards administering its outline and advancement." A similitude can be drawn by thinking about a corporate/IT diagram for the arranging of a city or a huge improvement. In particular, then, the diagram gives the large scale perspective of how components (streets, parcels, utilities-read: stages, systems, applications, applications' coherent segments) fit, especially in connection with each other. In this book we make utilization of terms, for example, "undertaking design, the present outline" (or "endeavor engineering," or "venture engineering portrayal"), and "undertaking design diagram for the objective state" (or "target state undertaking design" or "target state endeavor design depiction".)

3. Goals of Software Architecture:

1.Reduce Total Cost of Ownership

As anyone might expect, cost decrease is a business objective every now and again said in the ATAM assessments. Now and again, cost decrease was specified as a general objective. In different cases, cost decrease was identi-fied in a particular bit of the life cycle. We named our class Reduce add up to cost of possession and subdivided it into the accompanying gatherings: lessen cost of improvement, decrease cost of arrangement and operations, diminish cost of upkeep, and diminish cost of retirement/moving to another framework. The sorts of business objectives that form these gatherings are as per the following:

•        reduce cost of advancement

•        oversee adaptability

•        disseminated advancement

•        convenientce

•        open frameworks/norms

•        testability

•        product offerings

•        integrability

•        interoperability

•        reduce cost of organization and operations

•        reduce cost of upkeep

•        reduce cost of retirement/moving to another framework

•        resigning frameworks

•        smooth move to take after on frameworks

•        supplant legacy frameworks

Take note of that huge numbers of these business objectives are quality properties [Bass 03]. Every quality property are po-tentially business objectives, however not all business objectives are quality traits.

2.Improve Capability/Quality of System

Another much of the time said gathering of business objectives alludes to the change of a framework capabil-ity or quality contrasted with earlier forms of a similar framework or stood out from the system(s) being supplanted. Here and there the business objectives just determined prerequisites on the present framework without reference to earlier frameworks. We assembled those business objectives into this classification. The fundamental gatherings of objectives in this class are as per the following:

•        performance

•        reliability/accessibility

•        product lines

•        ease of utilization

•        security

•        safety

•        scalability/extendibility

•        functionality

•        system imperatives

•        internationalization

3. Improve Market Position

Some business objectives that rose up out of the business ATAM assessments need to do with market position or timing. The gatherings of objectives fundamental this classification are as per the following:

•        expand or hold piece of the overall industry

•        maintain or enhance notoriety

•        enter new markets

•        reduce time to showcase

4 .Support Improved Business Processes

Another critical class of business objectives is worried with enhancing the inside business forms and the structure of the association. Here, the hidden gatherings of objectives are as per the following:

•        support circulated improvement

•        maintain employments of workforce on legacy frameworks

5. Improve Confidence in and Perception of the System

The last class incorporates objectives expected to upgrade the notoriety of the creating association. There was one gathering of objectives in this class: keep up/extend notoriety.

4. Goals of IT Enterprise Architecture:

The objective of big business design is to make a brought together IT condition (institutionalized equipment and programming frameworks) over the firm or the majority of the company's specialty units, with tight advantageous connections to the business side of the association (which commonly is 90% of the firm as observed before, at any rate by method for spending plan) and its methodology. All the more particularly, the objectives are to advance arrangement, institutionalization, reuse of existing IT resources, and the sharing of regular techniques for venture administration and programming improvement over the association. The final product, hypothetically, is that the undertaking engineering will make IT less expensive, more vital, and more responsive.

The motivation behind big business engineering is to make a guide of IT resources and business forms and an arrangement of administration rule that drive a progressing examination about business technique and how it can be communicated through IT. There are a wide range of proposed structures to build up a venture engineering, as talked about later on. Be that as it may, most structures contain four fundamental areas, as takes after:

Related Questions

Navigate

• Browse (All)
• Browse W
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.