Please enable JavaScript.
Coggle requires JavaScript to display documents.
The Architecture of an Enterprise System (Week Two) (Service-Oriented…
The Architecture of an Enterprise System (Week Two)
defnition
blueprint of the actual enterprise system
types
Logical
: focuses on end-users’ requirements
Physical
: focuses on the efficiency of the system (costs, response time, etc)
Long Architecture
Works to assist in implementing the org’s vision & biz processes, focuses on end-users’ requirement
Functional view
End-user view
– performance, availability, usability, security
Business view
– targeted market, time to market, cost and benefits, projected time line, integration with legacy systems
Developer view
- maintainability, portability, reusability, testability
Physical Architecture
Highlights how the data, application logic and presentation are integrated and installed in the IT environment, focuses on the efficiency of the system (costs, response time, etc)
3-tier architecture
Benefits
Scalability
Easier architecture to add, change and remove applications
User interface and database not affected by upgrades to applications
Reliability
Easier to increase reliability by implementing multiple levels of redundancy
Scheduling and prioritization of jobs can be managed better from a central location
Security
Higher security because there is less software on the client machines
Flexibility
Business logic of an application is separate from its presentation logic
Reusability
Easier to implement reusable components
Maintainability
Support and maintenance cost are less on a single server
Limitation
Economics
– increased overall platform costs.
Complexity
– development environment more difficult to use than 2-tier applications
Web Services Architecture
Benefits
A wide range of end user access to Enterprise applications over the Web
server-centric architecture enables secure end-user access to ERP application
Easy integration of enterprise applications with existing internal systems and external trading partner systems
allow better system-to-system integration
Client-centric—Architecture has better response time because user requests are mostly processed on the client’s computer
Dawbacks
Client-centric architectures lack security
Server centric is slower.
Service-Oriented Architecture
A collection of services
Allow message interaction between any service consumer and service provider
A consumer (client) and a provider (server) sign a service-level agreement contract that specifies
benefits
Scalability, reusability, flexibility, agility
Improve business visibility
Reduce the cost of integration
limitation
Numerous complex structure for integration
Maintenance environment to support rapid integration capability
Security system needs to be sophisticated
Cloud Architecture
Cloud computing
software service provided over the Internet, securely, by a service provider on a monthly or yearly lease
Benefits
Low cost; pay for subscription, not for licenses and upgrades
Easy access
Cost saving from owing software and hardware, and maintenance
Drawbacks
Data security, vulnerability
Potential conflicts of interest
Implications for management
Enterprise architecture is an important technology for the long-term functioning of the organization
ERP architecture decisions are complex
ERP architecture must be flexible
Learn to filter out the hyped technologies that do not provide value