Designers Must Do the Modeling {2}

by Asim K

In his article Designers Must Do the Modeling, which was published in IEEE Software , Volume 15 Issue 2, Brian Lawrence enunciates on the fact that designers for database, or any other project, must do the modeling. Lawrence defines the stepping stone as figuring out the customer’s problem rather than figuring out requirements for the project. In his logical breakdown, Lawrence cites ERD models as only an output of the requirements process which will dictate database  design later on in the process. He pursues this opinion with another, saying that producing the ERD diagram (or whichever type of diagram you may be working with) has the benefit of allowing ourselves to understand the customer’s problem better so we can design better solutions. Because the designers have to produce the requirements model, Lawrence embraces the not-so-popular opinion that the designers themselves are the owners of the model.  Citing a quote by Dwight Eisenhower, the author embraces the planning process over the actual plan. To further reinforce this statement, Lawrence says that managers must help persuade designers to understand that they must model requirements – no matter if the designers see it as their duty or not. Similar to the statement of “Learning by Doing”, Brian Lawrence embraces a brilliant model in saying that it is during the planning phase that we learn the most, not in the implementation of the plan. Personally, I agree with this worldview because I have experienced the  same euphoria myself. When I was younger, around 11 or 12, years old I would sit down to learn HTML as a hobby (yes, HTML was my hobby). Although my websites churned out to look like absolute trash and functioned on a pretty depressing level, in the process of research, working with clients, figuring out bells and whistles, I was able to generate a more holistic understanding  of what I was learning and still retain that knowledge today. On these terms, I agree that the designers – the individuals who actually work with the client to figure out their problems and solve them – are the people who should create the requirements needed for their projects; in our case: a databaase. Lawrence, B. (1998). Designers must do the modeling. Software, IEEE, 15(2). Retrieved from

No More Data Modeling? {4}

by Renee L
With more advanced and faster database technologies, some people say that there is no need for data modeling. In addition, organizations with agile development environments do not use data modeling. In fact, data modeling is not even mentioned at all. However, data modeling expert and consultant, Len Silverston, argues that it is more important to use data modeling now than ever. The purpose of data modeling is to understand the data requirements, build a foundation for the design, and allow data to be integrated. Therefore, if organizations do not have a data model, how are they going to understand the data and foundation of the database/business? Silverston also recommends that modeling techniques should be applied to agile development environments because things are happening so quickly. Thus, modeling would be perfect for agile development because it focuses on delivering solutions quickly. A data model can help produce things more quickly and prevent from making a mess because people will understand how everything fits together and the specific data requirements and design of the database. read more...

The Art of SQL Injection {3}

by Ermie C
In this peer reviewed article, it explains the many ways  on how SQL databases can be infiltrated with certain techniques.  There are techniques such as changing the attributes of the entities in the database.  They explain how sql injections can be implemented in any web application and any application that is connected with a database.  It’s really impressive that they have shown a technique on how to detect SQL injections.  This all deals with creating backups for the original database queries and attributes.  The the solution to seeing this is that they have created a SQL algorithm that compares the dynamic(present) database and compares it to the static database(past).  Then when it compares, it will essentially, detect the differences in queries and attributes.  However, just like every double edged sword, SQL injections are possible for any web application with a database, these techniques to detect and prevent SQL injections can be also be implemented. read more...

A Model for Models: Data Modeling Basics {Comments Off on A Model for Models: Data Modeling Basics}

by Brian T
Data modeling is a vital aspect of database creation and management. The ER diagrams lay the logical framework for an entire system, upon which so many people and other systems will be relying. Fundamentals, as with every other academia subject, are a complete necessity. Luckily, articles such as this one exist which aid in understanding. It outlines the basics of modeling which we have also touched on in class. It covers a variety of styles, patterns, and classifications of ER diagrams which may be used in the modeling process. read more...

Advancement in Data Modeling {1}

by Joey L
This article focuses on why technical architects and data modelers should adapt and evolve their current modeling practices to an agile data-modeling scheme.  Modelers most likely would believe that when building a data model, they should design and implement every single aspect of the model before building software that uses its resources from the data.  In agile data modeling, however, vastly changes how data models are implemented.  Agile modeling takes on an increment development activities on modeling.  Models are first simply designed efficient enough to allow incremental development in the future.  Only the basic framework of the design is developed to support the current development of the project.  Details of the model that are not immediately needed is often omitted by an agile modeler.  By following this scheme for modeling development, only the intended purpose of the model is produced. read more...

Importance of Data Modeling {1}

by Peter C

According to Data Modeling isn’t Dead article, it said that data modeling is very important. In the early 1980s, data modeling was very important because it was used for most project development. In order to create a business, data modeling was necessary because it was used as an outline. Just to start the company, it will need entities, relationship, and primary key. The best way to start a data modeling will be to create an entity relationship diagram. That will let the people see how the company is supposed to be run.  This is the most important model because it will show a complete picture of the operation. However, this is very time consuming which is why not every enterprise will use it. Not a lot of company would want to spend a ton of money on using this model which gives data modeling a bad name. read more...