This HTML5 document contains 71 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dcthttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n8https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbphttp://dbpedia.org/property/
dbchttp://dbpedia.org/resource/Category:
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Continuous_design
dbo:wikiPageWikiLink
dbr:Evolutionary_database_design
Subject Item
dbr:Database_refactoring
dbo:wikiPageWikiLink
dbr:Evolutionary_database_design
Subject Item
dbr:Evolutionary_Database_Design
dbo:wikiPageWikiLink
dbr:Evolutionary_database_design
dbo:wikiPageRedirects
dbr:Evolutionary_database_design
Subject Item
dbr:Evolutionary_database_design
rdfs:label
Evolutionary database design
rdfs:comment
Evolutionary database design involves incremental improvements to the database schema so that it can be continuously updated with changes, reflecting the customer's requirements. People across the globe work on the same piece of software at the same time hence, there is a need for techniques that allow a smooth evolution of database as the design develops. Such methods utilize automated refactoring and continuous integration so that it supports agile methodologies for software development. These development techniques are applied on systems that are in pre-production stage as well on systems that have already been released. These techniques not only cover relevant changes in the database schema according to customer's changing needs, but also migration of modified data into the database an
dct:subject
dbc:Database_theory
dbo:wikiPageID
51531494
dbo:wikiPageRevisionID
1046592910
dbo:wikiPageWikiLink
dbr:Database_management_system dbr:Data_definition_language dbr:Configuration_management dbr:Flyway_(software) dbr:Data_quality dbr:Production_(computer_science) dbr:Red_Gate_Deployment_Manager dbr:Sandbox_(software_development) dbr:Test-driven_development dbr:Acceptance_testing dbr:Attribute_(computing) dbr:Database dbr:Data_validation_and_reconciliation dbr:Test-first_development dbr:Continuous_design dbr:Incrementalism dbr:Database_trigger dbr:Waterfall_model dbr:Table_(database) dbr:Reference_database dbr:Data_model dbr:Regression_testing dbr:Data_modeling dbr:Software_development_process dbr:Database_schema dbr:Test_case dbr:Autopatch dbr:Database_refactoring dbc:Database_theory dbr:Pre-production dbr:Data_migration dbr:Business_analyst dbr:Data_structure dbr:Requirements_engineering dbr:Ruby_on_Rails dbr:Optimization_(computer_science) dbr:Liquibase dbr:Database_design dbr:Stored_procedure dbr:Iterative_and_incremental_development dbr:Refactoring dbr:Continuous_integration dbr:Rollback_(data_management) dbr:Source_code dbr:Agile_software_development dbr:Referential_integrity dbr:View_(database) dbr:Entity–attribute–value_model dbr:Entity–relationship_model dbr:Semantics_(computer_science) dbr:Database_administrator dbr:Relational_database_management_system dbr:Software_requirements_specification
owl:sameAs
n8:2eApP wikidata:Q28455639
dbp:wikiPageUsesTemplate
dbt:Reflist dbt:Main_article
dbo:abstract
Evolutionary database design involves incremental improvements to the database schema so that it can be continuously updated with changes, reflecting the customer's requirements. People across the globe work on the same piece of software at the same time hence, there is a need for techniques that allow a smooth evolution of database as the design develops. Such methods utilize automated refactoring and continuous integration so that it supports agile methodologies for software development. These development techniques are applied on systems that are in pre-production stage as well on systems that have already been released. These techniques not only cover relevant changes in the database schema according to customer's changing needs, but also migration of modified data into the database and also customizing the database access code accordingly without changing the data semantics.
prov:wasDerivedFrom
wikipedia-en:Evolutionary_database_design?oldid=1046592910&ns=0
dbo:wikiPageLength
13724
foaf:isPrimaryTopicOf
wikipedia-en:Evolutionary_database_design
Subject Item
wikipedia-en:Evolutionary_database_design
foaf:primaryTopic
dbr:Evolutionary_database_design