Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>EDIT</strong>: As the question has changed in emphasis, I've edited my answer as follows.</p> <p><strong>Architecture</strong> and <strong>architect</strong> are heavily-overloaded terms. To start, you need to specify whether you're talking about a software company (where software is the product/service) or a line-of-business company (where software supports the product/service). </p> <p>There is also the top-down view of architecture (what matters from the organisation viewpoint) versus the bottom-up view (what matters from the project requirements viewpoint).</p> <p>In a large line-of-business company, architecture from the top-down (organisation) viewpoint is normally partitioned something like this:</p> <ul> <li><a href="http://en.wikipedia.org/wiki/Business_architecture" rel="nofollow noreferrer">Domain</a> architecture, sometimes called business architecture. For example, understanding commodities trading processes and the associated IT systems.</li> <li><a href="http://en.wikipedia.org/wiki/Data_architecture" rel="nofollow noreferrer">Data</a> architecture. For example, understanding descriptions of data in storage and data in motion; descriptions of data stores, data groups and data items; and mappings of those data artifacts to data qualities, applications, and locations.</li> <li><a href="http://en.wikipedia.org/wiki/Technical_architecture" rel="nofollow noreferrer">Technical</a> architecture. For example, understanding the structure and behaviour of the technology infrastructure of an enterprise, solution or system.</li> </ul> <p>My architecture areas from the bottom-up (requirements) viewpoint look something like this:</p> <ul> <li>Correct use of middleware - loose coupling, fault tolerance, target-specific transforms, killing point-to-point, etc. </li> <li>Identifying and engineering-out as many reconciliations as possible. </li> <li>Identifying and engineering-out as much dual-keying as possible. </li> <li>Identifying and engineering-out as many manual processes as possible. </li> <li>Identifying and engineering-out any end-user computing solutions - e.g. Access databases, Excel spreadsheets. </li> <li>Identifying and engineering-out any end-user editing of "the answer" - taking information after all work is completed, and then editing it. </li> <li>Investigating complete data lifecycle: who owns it, who enriches it, who distributes it, single version of the truth, removing reconciliations. </li> <li>Identifying performance and scalability metrics, testing risky areas against multiple data profiles. </li> <li>Identifying real-time versus batch processes and interfaces, and eliminating batch dependencies wherever feasible. </li> <li>Consolidation to single platform where possible, and single versus multiple instances. </li> <li>Ability to handle new vanilla business quickly, and new complex business within reasonable timescales. </li> <li>Identification of a clear support model, especially across regions where necessary. </li> <li>State maintenance and recovery - how well every-day processing and interface failures can be recovered. </li> <li>BCP/DR requirements and capabilities, general fault tolerance, WAN dependencies. </li> <li>Where can project risk be reduced? </li> <li>Security, end-user and developer access, ring of steel around production. </li> <li>What MI reporting facilities are in place? </li> <li>Emphasising simplicity as much as possible, system de-commissioning. </li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWhat architectural perspectives do you consider as part of your overall software design?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRoadWarrior
    1. USRoadWarrior
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI couldn't agree with you more about the overloading of the term. I think far too often it leads to unclear or misalignment. As for structure, this is really line of business. If you look at an EA framework like zachman, it captures all 3 of the architectures you've outlined.
      singulars
      1. PO
      1. USAjaxx
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload