Men are from Mars and Woman are from Venus, Why Men Don’t Listen and Women Can’t Read Maps
2012
2012 is not a disaster. That's one thing critics, for the most part, agree on -- to various degrees. Roger Ebert in the Chicago Sun-Times even goes so far as to call it "the mother of all disaster movies" -- largely because the movie doesn't merely show a few recognizable landmarks being destroyed -- but the entire Earth. "You think you've seen end-of-the-world movies?" he remarks. "This one ends the world, stomps on it, grinds it up and spits it out." His conclusion: "The movie gives you your money's worth. Is it a masterpiece? No. Is it one of the year's best? No. Does Emmerich hammer it together with his elbows from parts obtained from the Used Disaster Movie Store? Yes. But is it about as good as a movie in this genre can be? Yes." Many reviewers note that it's a useless enterprise to try to critique the screenplay -- which is based on the premise that ancient Mayans forecast the end of the world on December 21, 2012 -- the final day of their calendar. (They apparently did not forecast the end of their own civilization, which occurred hundreds of years earlier.) That hasn't stopped others from zeroing in on the plot. Like Manohla Dargis in the New York Times, who comments, "Despite the frenetic action scenes, the movie sags, done in by multiple story lines that undercut one another," she writes. Claudia Puig in USA Today sums up: "The movie is an undeniable visual spectacle, but just as unequivocally a cheesy, ridiculous story." Lou Lumenick in the New York Post won't even grant that it's cheesy, calling it instead "pure Velveeta," -- but, ah, the spectacle. "About the only thing that's missing from 2012 (except sanity)," he writes, "is 3-D, IMAX and Sensurround. For those, I would gladly pay $20 a ticket." Noting that the movie reportedly cost $260 million to make, Elizabeth Weitzman writes in the New York Daily News: "All that money can buy some jaw-dropping special effects, but not, it seems, a script worth a dime." Still, Tom Maurstad in the Dallas Morning News thinks it was probably a good idea to present a threadbare story. "If the viewer were ever invited to think or feel about what's happening on-screen, the movie's wow-whoa-ain't-it-cool momentum would collapse in a heap of horrific preposterousness," he writes. And Mick Lasalle in the San Francisco Chronicle gives it a rave review, although admitting, "It's hard to do justice to his ridiculous, wonderful movie." Lasalle makes the point: "People talk about 'formula' almost always as a pejorative, but formulas get to be formulas because they work, and there's something to be said for a formula picture done almost to perfection." On the other hand, Joe Morgenstern in the Wall Street Journal hasn't a kind word to say about either the story or the effects, tagging the movie, "destructo drek." »
Database Design and Modeling Fundamentals
Database design and the creation of an entity relationship diagram (also known as an "ERD" or data model) is an important yet sometimes overlooked part of the application development lifecycle. An accurate and up-to-date data model can serve as an important reference tool for DBAs, developers, and other members of a JAD (joint application development) team. The process of creating a data model helps the team uncover additional questions to ask of end users. Effective database design also allows the team to develop applications that perform well from the beginning. By building quality into the project, the team reduces the overall time it takes to complete the project, which in turn reduces project development costs. The central theme behind database design is to "measure twice, cut once".
Effective database designers will keep in mind the principles of normalization while they design a database. Normalization is a database design approach that seeks the following four objectives:
Effective database designers will keep in mind the principles of normalization while they design a database. Normalization is a database design approach that seeks the following four objectives:
- minimization of data redundancy,
- minimization of data restructuring,
- minimization of I/O by reduction of transaction sizes, and
- enforcement of referential integrity.
- An entity is a logical collection of things that are relevant to your database. The physical counterpart of an entity is a database table. Name your entities in singular form and in ALL CAPS. For example, an entity that contains data about your company's employees would be named EMPLOYEE.
- An attribute is a descriptive or quantitative characteristic of an entity. The physical counterpart of an attribute is a database column (or field). Name your attributes in singular form with either Initial Capital Letters or in all lower case. For example, some attribute names for your EMPLOYEE entity might be: EmployeeId (or employee_id) and BirthDate (or birthdate).
- A primary key is an attribute (or combination of attributes) that uniquely identify each instance of an entity. A primary key cannot be null and the value assigned to a primary key should not change over time. A primary key also needs to be efficient. For example, a primary key that is associated with an INTEGER datatype will be more efficient than one that is associated with a CHAR datatype. Primary keys should also be non-intelligent; that is, their values should be assigned arbitrarily without any hidden meaning. Sometimes none of the attributes of an entity are sufficient to meet the criteria of an effective primary key. In this case the database designer is best served by creating an "artificial" primary key.
- A relationship is a logical link between two entities. A relationship represents a business rule and can be expressed as a verb phrase. Most relationships between entities are of the "one-to-many" type in which one instance of the parent entity relates to many instances of the child entity. For example, the relationship between EMPLOYEE and STORE_LOCATION would be represented as: one STORE_LOCATION (parent entity) employs many EMPLOYEEs (child entity).
- The second type of relationship is the "many-to-many" relationship. In a "many-to-many" relationship, many instances of one entity relate to many instances of the other entity. "Many-to-many" relationships need to be resolved in order to avoid data redundancy. "Many-to-many" relationships may be resolved by creating an intermediate entity known as a cross-reference (or XREF) entity. The XREF entity is made up of the primary keys from both of the two original entities. Both of the two original entities become parent entities of the XREF entity. Thus, the "many-to-many" relationship becomes resolved as two "one-to-many" relationships. For example, the "many-to-many" relationship of (many) EMPLOYEEs are assigned (many) TASKs can be resolved by creating a new entity named EMPLOYEE_TASK. This resolves the "many-to-many" relationship by creating two separate "one-to-many" relationships. The two "one-to-many" relationships are EMPLOYEE (parent entity) is assigned EMPLOYEE_TASK (child entity) and TASK (parent entity) is assigned to EMPLOYEE_TASK (child entity).
- A "foreign key" exists when the primary key of a parent entity exists in a child entity. A foreign key requires that values must be present in the parent entity before like values may be inserted in the child entity. The concept of maintaining foreign keys is known as "referential integrity".
- Relationships between two entities may be classified as being either "identifying" or "non-identifying". Identifying relationships exist when the primary key of the parent entity is included in the primary key of the child entity. On the other hand, a non-identifying relationship exists when the primary key of the parent entity is included in the child entity but not as part of the child entity's primary key. In addition, non-identifying relationships may be further classified as being either "mandatory" or "non-mandatory". A mandatory non-identifying relationship exists when the value in the child table cannot be null. On the other hand, a non-mandatory non-identifying relationship exists when the value in the child table can be null.
- Cardinality helps us further understand the nature of the relationship between the child entity and the parent entity. The cardinality of a relationship may be determined by asking the following question: "How many instances of the child entity relate to each instance of the parent entity?". There are four types of cardinality: (1.) One to zero or more (common cardinality), (2.) One to one or more (P cardinality), (3.) One to zero or one (Z cardinality), and (4.) One to exactly N (N cardinality).
all about IT
Information technology (IT), as defined by the Information Technology Association of America (ITAA), is "the study, design, development, implementation, support or management of computer-based information systems, particularly software applications and computer hardware." IT deals with the use of electronic computers and computer software to convert, store, protect, process, transmit, and securely retrieve information.
Today, the term information has ballooned to encompass many aspects of computing and technology, and the term has become very recognizable. IT professionals perform a variety of duties that range from installing applications to designing complex computer networks and information databases. A few of the duties that IT professionals perform may include data management, networking, engineering computer hardware, database and software design, as well as the management and administration of entire systems.
When computer and communications technologies are combined, the result is information technology, or "infotech". Information technology is a general term that describes any technology that helps to produce, manipulate, store, communicate, and/or disseminate information. Presumably, when speaking of Information Technology (IT) as a whole, it is noted that the use of computers and information are associated.
In recent days ABET and the ACM have collaborated to form accreditation and curriculum standards for degrees in Information Technology as a distinct field of study separate from both Computer Science and Information Systems. SIGITE is the ACM working group for defining these standards.
Today, the term information has ballooned to encompass many aspects of computing and technology, and the term has become very recognizable. IT professionals perform a variety of duties that range from installing applications to designing complex computer networks and information databases. A few of the duties that IT professionals perform may include data management, networking, engineering computer hardware, database and software design, as well as the management and administration of entire systems.
When computer and communications technologies are combined, the result is information technology, or "infotech". Information technology is a general term that describes any technology that helps to produce, manipulate, store, communicate, and/or disseminate information. Presumably, when speaking of Information Technology (IT) as a whole, it is noted that the use of computers and information are associated.
In recent days ABET and the ACM have collaborated to form accreditation and curriculum standards for degrees in Information Technology as a distinct field of study separate from both Computer Science and Information Systems. SIGITE is the ACM working group for defining these standards.
Subscribe to:
Posts (Atom)