Please enable JavaScript.
Coggle requires JavaScript to display documents.
Introduction (Enterprise Application (Characteristics (Acess data…
Introduction
Enterprise Application
Includes
Payroll,patient records, shipping tracking, cost analysis, credit scoring, insurance, supply chain, accounting, customer service, and foreign exchange trading
Doesn't worry about interacting with hardware directly
Mainly focuses on integrating with persistent/long-term data
DOESN'T include
elevator controllers, operating systems, compilers, and games
Characteristics
Persistent data
Needs to be around for multiple runs of the program
Needs to persist for several years
In some sense the data will remain consistent as the program,operating system, and compilers around it change
Meanwhile everything should still be working the way is designed
Lots of data
The data we are using can be gigabytes worth meaning that managing it is a major part of the system
Acess data concurrently
Many people are using it at the same time
Many issues can be caused if hundreds of people are attempting to use the app
Even if only a few people are using it, errors can be created if the same data is attempted to be accessed at the same exact time
Lots of user interfaces
The data must be presented in multiple ways
Must be maintained throughout multiple different screens
Integrate with other enterprise applications
Conceptual dissonance
The meaning of a "customer" varies within a businness itself
Sometimes there's unique cases when it comes to business so we must still handle these "one-off" cases
Architecture
A series of layers that work together to represent the whole
The decisions that goes into selecting an architecture is what is invaluable to making a solid robust app
Kinds of Enterprise Application
THere are plenty of different types of Enterprise Applications, each with their own difficulties that don't apply to the next
There is no one mold that satisfies everything