Here is the synopsis of our sample research paper on Systems versus Enterprise Architecture. Have the paper e-mailed to you 24/7/365.
Essay / Research Paper Abstract
A 6 page research paper that, first of all, offers a 2 page summary that differentiates systems architecture from enterprise architecture. Then, the writer summarizes the content of 2 web sites and 1 journal article. The final page offer findings and conclusions. Bibliography lists 10 sources.
Page Count:
6 pages (~225 words per page)
File: D0_khsavea.rtf
Buy This Term Paper »
Unformatted sample text from the term paper:
architecture if that it is similar to building codes that "ensure the building is soundly constructed" (Thomas and Cullen, 2001). Frameworks encompass "models and standards" that are used to develop
"IT architecture descriptions," and this "architecture description is the blueprint" for the system (Thomas and Cullen, 2001). According to Carnegie Mellon Universitys Software Engineering Institute, "system architecture" (SA) is defined
as the "mapping of functionality onto hardware and software components, a mapping of the software architecture onto the hardware architecture, and the human interaction with these components" (Shapira, 2006).
According to Wu (2008), traditional systems architecture refers to application development that is formulated to "address a specific set of requirements" that collectively build "toward a static architecture blueprint," while
enterprise architecture is "subject to continuous change," which is analogous to the way in which an amoeba changes in order to capture food. Aden (2008) is somewhat more explicit
in his use of analogy in differentiating between SA and EA. First of all, he states that EA is based on "the idea that one should plan technology purchases and
development ahead of time and...that business people, not technology people, should determine what is needed," in terms of systems requirements (Aden, 2008). Turning to the analogy of building a
home, Aden compares the processes involved with EA to way that homeowners offer input to a contractor on what features that they desire, i.e., the amount of closet or cabinet
space. In other words, EA derives "from the understanding that technology exists to fulfill business needs" (Aden, 2008). EA relates to the "broad decisions" that organizations made in regards to
their IT support system and how it serves to achieve organizational goals (Malhotra, 1996). Furthermore evolutionary refinements to the SA/EA approaches to architecture appear to have taken place, as
...