Design

What to Expect in Data Warehousing {2}

by Penny P
Data warehouses play a critical role in corporation/institutions. They allow users to quickly retrieve data to be used for data mining or for data analysis tools. The results that they get from these tools are then used to support business decisions that would be made. The authors of the article designed a case study that would help beginners understand the basics of data warehousing. Using the enrollment data from Universities, the main objective was to prepare the data for a mining system that would be used for predicting student enrollment. read more...

Look Before You Leap {1}

by Han C
Being able to use available knowledge to help build an effective and efficient product for your customer is crucial in the business world. Coming up with the right solution the first time can make the difference in money and time. That is why this article stresses the importance of forward engineering. Although the article itself it still rather old. The information is relevant to what we have done in our second assignment and maybe even our third and final assignment. The article discusses the benefits of implementing forward engineering practices in business systems analysis, for example, “Logical modeling gets it right and physical modeling makes it optimal for the chosen database platform and technology.” Furthermore, the author does not believe in merely relying on reverse engineering to provide the necessary business in’s and out’s and recommends forward engineering whenever possible. read more...

Building a Best-Fit Data Warehouse: Why Understanding Physical Database Structure Matters {Comments Off on Building a Best-Fit Data Warehouse: Why Understanding Physical Database Structure Matters}

by Hassib K
The article went on at length discussing the various uses of data warehouses and how they should be designed physically so that they can complete all necessary tasks quickly and efficiently.  There are 3 types of business intelligence that it went over and those included, operational BI, analytics, and management BI.  It mentioned that there are other scenarios as well, but it did not go into those.  O’Brien states that the data warehouse will perform at its peak when the logical data models, BI workload, and optimal physical database design are matched up; so there is a RIGHT way to physically design the database for each situation.  He discussed the difference between SMP, Clusters, MPP, and Grids.  BI workloads can be viewed at from a perspective of how much demand they place on the physical architecture.  The characteristics to look at include:  data volume, number of users, types of queries, frequency and timing of access, and latency requirements.  Some business intelligence activities will place more demand than others.  Operational BI for example requires time-sensitive real-time information usually and this will place a heavy demand on the physical architecture if many users are requesting the same information at the same time.  Management BI usually requires the “push-button” access to various reports and information and Historical Analytics usually requires incredibly large amounts of data that can possibly contain information from a client over the past 10 or 20 years. read more...

Before You Start, Make Sure You Have an Effective Design {1}

by Jongwoo Y
The article that I chose talks about how important it is to design an effective structure for a database before actually putting it into practice. This means that a person planning to setup a database must actually layout an effective design that can handle everything a business needs or it will be destined for failure. By either creating the blueprints of the database on paper or through a database design program, a business may be able to avoid future problems that can costs thousands or even millions of dollars (Starr, 2009). If they skip to choose this step, businesses may find themselves in a less than ideal situation and be forced to sacrifice valuable resources that could be used on something more profitable . A great way to avoid this type of situation is by using peer review (Starr, 2009). read more...

The Subtle Rise of HTML5 {Comments Off on The Subtle Rise of HTML5}

by Cole O’C
Over the last two years, HTML5 has been supported and adopted by a lot of big name companies such as Microsoft, Apple, Google, Amazon, and LinkedIn. While HTML5 is technically only the latest version of a technical standard, it has come to represent a set of features and capabilities that both enhance user experience and simplify development processes. This simplification is most plainly seen when companies are developing an application for both iOS and Android; HTML5 allows them to develop one application that can be run on any web browser. The powerful tools of HTML5 make it hard to differentiate between the cloud and the web, as well as desktop and client functionality. The technology is incredibly flexible and quite affordable to incorporate. However, the new standard does have its downsides. Applications developed with HTML5 are sometimes limited compared to their iOS and Android counterparts, as certain features are harder to access. Another issue facing HTML5 is application distribution, which has become an almost non-issue for iOS via the App Store and Android via the Marketplace. Google Chrome’s app store, which seeks to become a primary HTML5 distributor, is fairly new and does not have quite the presence of its non-HTML5 counterparts. Although it may take some time, HTML5 has the potential to overcome its weaknesses and become a platform-spanning giant. read more...

Common Databasing mistakes {2}

by Daniel M
The article that i read was about the common mistakes that are made when people are designing and building databases. The article talks about how people need not rush into the planning aspect of the database in order to just get it done. The next big mistake that people make is in the naming of objects. The article talks about how important consistency is when you are naming objects and how important it is that you make the name something that anyone can recognize and understand why you named it that. Defining is another common mistake when people are building databases. the article says that you need to define all of your table, columns, and relationships so that you can figure out what you did later on. the last important thing that is too often overlooked is to make sure you do ample amount of testing of your database before you say it is done. The article talks about how when time starts to get short on a project the first thing that people tend to not do is to test the database well enough before they release it. read more...

SQL Injection, easier than it sounds. {Comments Off on SQL Injection, easier than it sounds.}

by Caezar M
Sumamry:

The recent slew of attacks on businesses using SQL injection from hacking groups might make it seem like top notch stuff but its suprisingly easier than it sounds. the key in SQL injection is finding web applications that are vulnerable to the injection of malicious code into the database. so after the site is used legitimately the user is usually redirected at the command of the rogue commands the hacker implemented in the system. a recent attack was one called LizaMoon that affected over 1 million web sites. and its not the administrators fault, they have little control over this. it is solely the fault of the web based application that was not properly secured. web based applications should have buffers and filters that check the input for malicious code but not all applications do. so when it reached the system level the code can do its intended purpose. read more...

Reference Data {Comments Off on Reference Data}

by Alexander V
Summary:

The article talks about the advances of database design and modeling and how it is a necessary skill. Then it goes on to question whether different data models have different rates of accuracy and whether the data model can have all the design information for a database. The author states that there are limits on what models can do and failure to understand the limits can lead to data management problems. He says data modeling in general is focused on the logical level, which is a good thing. The problem that the author brings to light is when there is the divide between the logical and physical database design and the data entered into the database acted to “specify a layer of design.” This type of data is called referential data and is commonly referred to as “code tables, lookup tables or domain values.” Referential data typically contains a “code” which is the  primary key and a description. Reference data has many important properties that other types of data do not have. One property would be that a “code” value usually has a definition.  The author defines reference data as “any kind of data that is used solely to categorize other data found in a database or solely for relating data in a database to information beyond the boundaries of the enterprise.” One way that referential data specifies database design is by “effectively replacing attributes in entities.” He says one of the biggest problems with referential data design is failure to assign definitions to data values. This leads to the problem of the divide between logical and physical models. Data models and databases are full of reference data tables and business users are usually left to deal with data values which are not found in the data model and are needed to understand the database. The author concludes that there needs to be better tools and techniques to deal with this problem. read more...

Database Designer 1.0 {Comments Off on Database Designer 1.0}

by Peter C
Summary:

According to Howard article, he stated that Oracle is lowering the cost of Database Designer 1.0 by scaling it. It will make it easier for the users to use because it will reduce it complexity. The database designer is good for a stand-alone environment because it does a good job on generating a database. The Database has a wizard that can convert it into a diagram. They can copy the old database and format to a new database. It will make the user to be able to use it easier for their company. The product has the ability to generate SQL and is also compatible with high-end databases. In addition to the Reverse Engineer Wizard, it contains a Data Diagrammer and the Generation Wizard. This will give the user an overview of the project and can show them how it is process. read more...

The Gatherer, Hunter Approach {2}

by James C
Summary:

Many successful companies today are finding that not all good ideas come from their own R&D department, but rather blogs, RSS feeds, forums and search engines. The key though to their success is not only keeping up with the knowledge of new ideas and improvements but also to connect them with the right personal to implement them. Other companies that have followed in suit with these “giants” of innovation have failed to recognize the latter of this approach. These successful companies have recognized and even specialized the of two positions that have given the most contribution, idea scouts, personal responsible for seeking and determining the importance of new ideas, and idea connectors, personal responsible for finding the meaningful association between the new ideas and company products and services. This article states in detail the processes that successful companies go through to gain or maintain the leading edge in technology. read more...