Textbook Notes (290,000)
CA (170,000)
UTM (8,000)
CCT (200)
Chapter 7

CCT225H5 Chapter Notes - Chapter 7: Mobile Computing, Breakcore, Net Present Value


Department
Communication, Culture and Technology
Course Code
CCT225H5
Professor
Max Evans
Chapter
7

This preview shows pages 1-2. to view the full 7 pages of the document.
INTRODUCTION
New applications build on past solutions organically using established building blocks
All software is developed from reusable units of code
High level, holistic organizational approach to how an organization views and acts on all its
software needs
Service-oriented architecture (SOA or SoA)a software architecture perspective that focuses on the
development, use, and reuse of small self-contained blocks of code (called services) to meet many or
even all the application software needs of an organization
Lean, agile: takes advantage of every resource in the most efficient and effective way
React quickly in a proactive way to perceived changes in the market, competition, and customer
demographics, wants and desires
Transform its processes, structure, and HR initiatives to match a changing and dynamic workforce
Organization with a SOA philosophy
Customers
Provide multichannel service delivery options and customizable products and services
Plug-and-play: into any communications channel with your organization such as fax, the web, face to
face, phone call etc.
Experience should be the same regardless of communication channel
Mass customization
Plugging in their desires and wants
Personalize products and services
End-Users
End-users of IT: employees within the organization
Achieved through a fully integrated enterprise resource planning (ERP) system that meets every
application software and information need of each and every employee
ERP should support transparent interoperability across multiple vendors and within ERP modules
provided by the same vendor
Able to access computing and information resources regardless of where they are (mobile
computing)
Regardless of IT in hand, employees should enjoy access to a full range of application software
services and information
Take advantage of multichannel service delivery
Software Development
Rapid application development (RAD)
Extreme programming (XP)
Agile methodology
Orgs can choose among numerous software development methodologies that focus on the production
and reuse of blocks of code to speed the process of software development
Information Needs
Most vitally important organizational resource -- information
Ppl throughout your org need access to info , BI, and knowledge that supports their decision making
efforts
Info be in a standard format no matter where it exists
SOA approach to info requires that:
Chapter 7: Enterprise Infrastructure, Metrics, and Business
Continuity Planning
Tuesday, April 05, 2011
3:33 PM
CCT225 Page 1

Only pages 1-2 are available for preview. Some parts have been intentionally blurred.

Info be in a standard format no matter where it exists
Strict and rigorous integrity control mechanisms are in place to ensure the completeness,
accuracy, and validity of the info
No duplicate info exists in disparate silos anywhere in your organization
Any kind fo info from any source (even external) can be quickly and easily coupled with other info
SOA approach to info requires that:
Hardware Requirements
Org should be free to choose diff technologies and diff technology platforms and integrate them
seamlessly (plug and play)
Powerful storage area networks should have the capacity to store all your info needs
You should not have to care where within these networks info is stored; your access to info should be
simple and easy
Telecommunications platform should be safe and secure, and at the same time, enable you to access a
network, either wired or wireless, using the same steps or procedures
HARDWARE AND SOFTWARE INFRASTRUCTURE
Diff players of structure, which provide support or services
Infrastructurethe structure beneath a structure
Enterprise Resource Planning (ERP) Revisited
ERP market is at the top of the IT spending list
Vendors are continuously updating their products and adding new technology based features
Long term vision
Commitment to service and support
Specialty features
Experience
Financial strength for R&D
Major vendor qualities for product selection and implementation:
The Evolution of ERP systems
ERP systems replace islands of info and processes, with a single, packaged software solution that
integrates all the traditional enterprise management functions such as financials, HR, and manufacturing
and logistics
Focus: internal production, planning, calculating time requirements components, procurement,
and materials planning
Developed to provide the right materials at the right time
No focus on service orientation
For the first time, management was able to answer the question "when?"
Early stage of ERP (1970s) system: materials requirement planning (MRP)
Evolved
Closed the loop with the accounting and financial management systems
Crossed boundaries of production functionality and started serving as decision support systems
(DSS) and executive information systems (EIS-digital dashboards in the modern day)
Company could have an integrated business system that provided visibility for the requirements of
material and capacity
Good info good decisions: integrated IT systems provide competitive advantage
Late 1980s to early 1990s: time to market: increasingly short
Early 1980s: manufacturing resources planning or MRPII
Encompasses all the resource planning for the enterprise including product design, warehousing,
material planning, capacity planning, and communication systems
Help companies become leaner and more agile to technology by integrating the basic transaction
programs for all depts, allowing quick access to timely info
Beg 1990s: enterprise resource planning (ERP)
SCM
Evolved into ERPII
CCT225 Page 2
You're Reading a Preview

Unlock to view full version