Chapter 7 Notes

3 Pages
Unlock Document

University of Toronto Scarborough
Financial Accounting
Tim Richardson

Chapter 7 NotesIntroductiona serviceoriented architecture SOA or SoA is a software architecture perspective that focuses on the development use and reuse of small selfcontained blocks of code called services to meet many or even all the application software needs of a firmthus new applications build on past solutions organically using established building blocksif SoA is adopted firm says that instead of bringing in brand new systems all software developed from reusable units of codeSoA is a highlevel holistic organizational approach as to how an organization views and acts on all its software needswith a serviceoriented architecture philosophy the organization wouldobe a lean agile organization that takes advantage of every resource in the most efficient and effective wayoreact quickly in proactive way to perceived changes in market competition customer demographics wants and desiresorespond quickly to and adapt to new advances in technologyotransform its processes structure and HR initiatives to match a changing and dynamic workforceInformation Needsan SoA approach to information require thatoinformation be in a standard format no matter where it existsostrict and rigorous integrity control mechanisms are in place to ensure the completeness accuracy and validity of the infoono duplicate information exists in disparate silos anywhere in your organizationoany kind of information from any source even external can be quickly and easily coupled with other informationHardware and Software Infrastructurein a corporation the IT infrastructure includes the hardware software such as ES software and information that 1 ensure the components work together and 2 enable people business processes and customers to interact and perform their tasksEnterprise Resource Planning ERP Revisitedtwo of the primary goals of an ERP system within a serviceoriented architecture are1provide interoperability within an ERP vendor and for modules among different ERP vendors2hide the underlying IT infrastructure of information and hardware from endusers and customersAdvantagesDisadvantagesCentralize databaseReliable information accessTime consumingAvoid data and operations redundancyExpensiveDelivery and cycle time reductionLack of conformity of modulesCost reductionVendor dependenceEasy adaptabilityToo many features too much complexityImproved scalabilityQuestionable scalability and global reachGlobal reachNot enough extended ERP capabilityEbusiness
More Less

Related notes for MGAC70H3

Log In


Don't have an account?

Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.