Patent application serial number 830667 is assigned to
The following quote was obtained by the news editors from the background information supplied by the inventors: "There are many kinds of computer software, each with its own challenges and complexities. The invention described in this document is primarily for use in an area of software known as
"A common way to describe an architecture is to decompose it into layers, and as such most discussions on enterprise architecture begin with an illustration in terms of layers. Furthermore, it is generally accepted that well-formed enterprise architectures consist of three principal layers: User Interface, Domain, and Data Source. The Domain layer (middle layer) is the focus of software development and contains object-oriented software known as business objects. Software developers design business objects with full consideration of the target platform, which includes, but is not limited to limitations in memory, CPU, networks, and databases. The collection of documents that describe the business objects in light of these limitations is known as the design model. It is well known that the design model isn't easily accessed by the User Interface, and likewise, it isn't easily persisted to a Data Source, especially in the case of relational databases. These difficult access points are known as representational gaps.
"The three fundamental approaches for implementing design models that determine the extent of representational gaps are: top-down, bottom-up, and meet-in-the-middle. These approaches center around the flexibility of the relational database. The most common approach is bottom-up or meet-in-the middle because most enterprises have databases in production and databases can't be easily changed. The top-down approach is not often seen in production and is most suitable for embedded systems or application prototypes. The domain modeling approach chosen affects the representational gaps because of the bias in the direction of the approach. The top-down approach favors the conceptual model and results in complex database mappings from the design model to the database. The bottom-up approach favors the database and results in complex mappings between the user interface and the design model. The meet-in-the-middle approach tries to split the difference.
Most Popular Stories
- 15 Myths That Could Ruin Your Hispanic Ad Campaign
- AIG to Create 230 Jobs in Charlotte
- General Motors Names Mary Barra as First Female CEO
- Russia Says Nyet to Canada North Pole Claim
- Bipartisan Negotiators Reach Modest Budget Agreement
- Justin Bieber Visits Typhoon Victims, Plays Concert
- Bitcoin Clones Lurch Onto Financial Scene
- Senate Dems Move Forward With Obama Nominees
- MasterCard to Split Shares, Raise Dividend
- New Obama Aide to Focus on Climate Change