logo

American City Corporation- Doc

   

Added on  2019-09-26

12 Pages1946 Words383 Views
Running head: American City CorporationAmerican City CorporationCS352-1603A-01Jivan WashingtonJuly 18, 2016

American City CorporationTable Of ContentsAmerican City Corporation..........................................................................................................................3The Database Models, Lanaguages and Architecture..................................................................................4Database System Development Life Cycle...................................................................................................6Database Management Systems.................................................................................................................9Advanced SQL............................................................................................................................................10Web and Data Warehousing and Mining in the Business World..............................................................11References................................................................................................................................................................122

American City CorporationThe American City Corporation In 1968 the Rouse Company had formed a Subsidiary Company called American CityCorporation. The company was formed so that it could give advice to older cities to help formaplans based on the Columbia experience. In 1972 50 organizations used this model approachthat American City Corporation established and in 1970 Hartford Insurance followed and latersigned a 3 million dollar contract with American City Corporation.3

American City CorporationDatabase Models, Languages, and ArchitecturePlanning is a critical step in creating a database, and as much as jumping right into creating tables and schemas may be tempting, taking a little bit more time to put everything into perspective can always save us a lot of grief. In this article, we will look into certain elements of a database management system, namely: the 3-level ANSI-SPARC architecture, data independence, data and database administration personnel, and how planning can help us make the right choices concerning them, right from the very beginning. My company, the American City Corporation, is considering consolidating it databases to allow for central storage, access, and development, and therefore, understanding the above listed components of a DBMS is imperative.The acronym ANSI-SPARC stands for the American National Standards Institute(ANSI), while SPARC stands for Standards Planning and Requirements Committee, and is a design standard for database management systems (Özsu & Valduriez, 2011). This abstract standard was developed in 1975 and consists of a three-level architecture: the external level, the conceptual level, and the internal level. Basically, the external level describes part of the database that is useful to the users. Sometimes, it is normally referred to as the users’ view. All irrelevant data or all unauthorized data are usually excluded from this view. This provision implies that users have access to the same personalized data, and changes to a single user do not affect other users (Özsu & Valduriez, 2011).The second level, conceptual level, describes the intricate properties of the data stored, how they are inter-related, and the relevant integrity constraints. It is also good to know that onlythe data or database, administrators work at this level and that this level is always independent ofboth software and hardware operational (Özsu & Valduriez, 2011). Lastly, the internal level illustrates how data is actually physically represented in the computer system. It shows how data is physically stored in both the computer and on the hardware. Together, the three levels ensure a substantial data independence as will be discussed in the ensuing sections.It is will be important for the American City Corporation to ensure immunity of its user applications from any unprecedented changes in definition and the organization of data in its database (Date & Hopewell, 1971). This requirement can be taken care of in the initial stages of 4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Data Model Quality
|4
|655
|32