Which best describes your current position?,How many years of experience in IT do you Have?,Number of IT people in your organization,Which continent do you currently work in?,Which sector is your organization primarily in?,What is your organization's approach to data naming conventions?,How well do you rate the quality of the data within your organization?,How long would it take for your organization to successfully rename an important column (e.g. FirstName) in one of the primary tables (e.g. Customer) within your main production database?,Does your IT department provide a service level agreement (SLA) pertaining to database performance?,Does your IT department provide an SLA pertaining to database availability?,"What strategy, if any, does your organization have for addressing the existing problems with your production data sources?",,Are you doing database testing?,When are you testing your database(s) (check all that apply)?,,,,,,"What types of database testing, if any, are you doing (choose all that apply)?",,,,,,,,,,When do you do data modeling on application development projects?,What types of structural modeling do you do on application development projects (check all that apply)?,,,,,,,When do you do data modeling on data warehouse/data mart projects?,What types of structural modeling do you do on data warehouse/data mart projects (check all that apply)?,,,,,,,What is your approach to a common glossary of business terms?,What is the approach to enterprise data modeling within your organization?,,,,
Response,Response,Response,Response,Response,Response,Response,Response,Response,Response,Response,Open-Ended Response ,Response,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),I don't know,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,Other (please specify),Open-Ended Response,Response,We don't do any structural modeling,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,I don't know,Response,We don't do any data modeling,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,I don't know,Response,We don't do enterprise data modeling at all,We just have a single logical model,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,I don't know
Developer,None,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,101 to 500,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within three months,"No, we've chosen not to do this",Yes,"We have problems, and try not to make the situation any worse",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 20 years,11 to 50,North America,Public (Government),We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,,,,,Data modeling is usually done in an evolutionary manner throughout the project,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,I don't know,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,501 to 1000,North America,Private,We don't have any data naming conventions,We have serious data quality problems,We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,11 to 50,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,"No, we don't have adequate resources","We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,"We've failed several times in the past,  but will likely attempt this again",,We just have a single logical model,,,
Developer,5 to 10 years,11 to 50,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,I don't know,I don't know,"We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
IT Management,5 to 10 years,1000+,North America,Public (Government),We don't have any data naming conventions,We have serious data quality problems,We could do it within a week,I don't know,Yes,"We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,,,,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,501 to 1000,North America,Public (Government),They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),none,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,10 to 20 years,11 to 50,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,,,We just have physical data models describing existing production data sources,,
Developer,2 to 5 years,1000+,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within three months,Yes,Yes,"We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,51 to 100,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,11 to 50,North America,Private,I don't know,We have serious data quality problems,It would likely take us longer than three months,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,Other (please specify),all of the above,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
IT Management,5 to 10 years,11 to 50,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",This is too risky for us to even attempt,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,Yes,,,,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Data Professional,5 to 10 years,1 to 10 ,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,We've never tried to create one because we haven't considered it,,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,Other (please specify),We fix each data issue on its own merits. there is no over all strategy in place.,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,101 to 500,North America,Public (Government),They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,"We've tried to create one several times, and have pretty much failed each time",,,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,10 to 20 years,101 to 500,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,We have one and developers find it useful,,,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,10 to 20 years,101 to 500,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,,We validate column constraints ,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,We have one and developers find it useful,,We just have a single logical model,,,
Project Manager,None,1000+,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,I don't know,I don't know,"We have problems, but no strategy to fix them",,I don't know,,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,10 to 20 years,11 to 50,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,I don't know,Yes,"We have problems, and try not to make the situation any worse",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Developer,2 to 5 years,1000+,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,11 to 50,North America,Public (Government),They're documented but not followed consistently,We have serious data quality problems,We could do it within a month,"No, we haven't even thought of doing this",I don't know,"We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,51 to 100,North America,Public (Government),We don't have any data naming conventions,"It's pretty good, but with a few problems",This is too risky for us to even attempt,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,10 to 20 years,1 to 10 ,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",This is too risky for us to even attempt,I don't know,I don't know,"We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,,,,,XML modeling of data structures,,"We have one, but developers rarely use it",,We just have a single logical model,,,
Data Professional,10 to 20 years,1 to 10 ,North America,Public (Government),They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this",We don't have data quality problems,,"No, we don't have adequate resources",,,We test the database at the end of each iteration as part of incremental system testing,,,,,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,I don't know,,,,,I don't know
Data Professional,5 to 10 years,101 to 500,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a week,"No, we've chosen not to do this",Yes,"We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,20+ years,11 to 50,North America,Private,They're documented and willingly followed by developers,It's perfect,We could do it within a month,Yes,"No, we've chosen not to do this",We don't have data quality problems,,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),None,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
IT Management,5 to 10 years,1 to 10 ,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
IT Management,20+ years,1 to 10 ,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",It would likely take us longer than three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Project Manager,Less than 2 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,11 to 50,North America,Public (Government),They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",This is too risky for us to even attempt,I don't know,I don't know,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,I don't know,We don't do any data modeling,,,,,,I don't know,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,We just have physical data models describing existing production data sources,
Developer,10 to 20 years,51 to 100,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,101 to 500,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,Yes,Yes,"We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,We just have a single logical model,,
Developer,10 to 20 years,11 to 50,North America,Public (Government),They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this",Yes,Other (please specify),data quality problems exist due to inherent quality of the source documents. Our processes help to improve the data quality and usability of these poor source documents.,"No, we don't have adequate resources",,,,,,I don't know,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,,,,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,UML class diagramming of the object schema,,,I don't know,,,Detailed logical data modeling,,UML class diagramming of the object schema,XML modeling of data structures,,We've never tried to create one due to lack of resources,,,,We have both a logical model and some physical models  
Developer,10 to 20 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,51 to 100,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a week,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,I don't know,We don't do enterprise data modeling at all,,,
Developer,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a month,I don't know,I don't know,We don't have data quality problems,,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,,,We validate the view definitions implemented within the database ,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,UML class diagramming of the object schema,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,"We have one, but developers rarely use it",,We just have a single logical model,,
Business Stakeholder,20+ years,501 to 1000,Africa,Public (Government),We don't have any data naming conventions,We have serious data quality problems,This is too risky for us to even attempt,"No, we've chosen not to do this",I don't know,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,"No, we never even thought of doing it",,,,,,I don't know,We validate data values as they go into the database,,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,"We've tried to create one several times, and have pretty much failed each time",,,,We have both a logical model and some physical models  
Project Manager,Less than 2 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,
Developer,20+ years,101 to 500,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  
Developer,5 to 10 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a week,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,
Developer,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,20+ years,11 to 50,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've failed several times in the past,  but will likely attempt this again",,,,We have both a logical model and some physical models  
Data Professional,20+ years,51 to 100,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  
Business Stakeholder,20+ years,101 to 500,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Project Manager,10 to 20 years,11 to 50,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,,,,,I don't know
Developer,5 to 10 years,101 to 500,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a month,I don't know,I don't know,"We have problems, but no strategy to fix them",,Yes,,,,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,11 to 50,North America,Public (Government),We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,We've never tried to create one because we haven't considered it,,,,,I don't know
Operations/Support Staff,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",This is too risky for us to even attempt,I don't know,I don't know,We don't have data quality problems,,I don't know,,,,,,I don't know,,,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,20+ years,11 to 50,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,None,1 to 10 ,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,20+ years,501 to 1000,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,We have one and developers find it useful,,We just have a single logical model,,,
Project Manager,20+ years,101 to 500,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a month,I don't know,I don't know,We don't have data quality problems,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"Data modeling is usually done up front, early in the project",We don't do any data modeling,,,,,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Data Professional,20+ years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",This is too risky for us to even attempt,"No, we've chosen not to do this",Yes,"We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,,,,We validate data values as they come out of a database,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,11 to 50,North America,Public (Government),They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,"No, we haven't even thought of doing this",Yes,"We have problems, but no strategy to fix them",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've tried to create one several times, and have pretty much failed each time",,,,We have both a logical model and some physical models  ,
IT Management,20+ years,1000+,North America,Public (Government),They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,"No, we've chosen not to do this",Yes,"We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,1 to 10 ,North America,Public (Government),We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,"We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,I don't know,,,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,20+ years,51 to 100,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",This is too risky for us to even attempt,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,I don't know,,,,,,I don't know,We validate data values as they go into the database,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
IT Management,20+ years,51 to 100,Asia,Public (Government),We don't have any data naming conventions,We have serious data quality problems,This is too risky for us to even attempt,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",Other (please specify),"Stovepipe problem and some legal, process issues prevent us to establish the consistent, standardized data management approach.",Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,UML class diagramming of the object schema,,,"We've tried to create one several times, and have pretty much failed each time",We don't do enterprise data modeling at all,,,,
Data Professional,2 to 5 years,101 to 500,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,We don't have data quality problems,,I don't know,,,,,,I don't know,We validate data values as they go into the database,,,,,,,,,,We don't do any data modeling at all ,,,Detailed logical data modeling,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,I don't know,,,We just have physical data models describing existing production data sources,,
Project Manager,10 to 20 years,11 to 50,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we've chosen not to do this",Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've tried to create one several times, and have pretty much failed each time",,,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,10 to 20 years,101 to 500,North America,Public (Government),We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and try not to make the situation any worse",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,"We've failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,20+ years,101 to 500,North America,Private,They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,Less than 2 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,"We test continuously throughout data warehouse development, following a TDD approach",,,,,,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,,,Detailed logical data modeling,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
IT Management,20+ years,11 to 50,North America,Public (Government),They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,XML modeling of data structures,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Data Professional,20+ years,1000+,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",This is too risky for us to even attempt,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",Other (please specify),"Being a DBA, I am only involved in   data base / table / view  / segment names.    Data quality is the developer's problem",Yes,,,,,,I don't know,,,,,We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,Other (please specify),"Specific testing is done by the Developers, once we set the database and related entities (including utilities) up.",We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Data Professional,10 to 20 years,501 to 1000,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,I don't know,I don't know,Other (please specify),"If 'fix whatever is causing the most political pain' is a strategy, then we have a strategy.",Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've failed several times in the past,  but will likely attempt this again",,,,We have both a logical model and some physical models  ,
Developer,5 to 10 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,51 to 100,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and try not to make the situation any worse",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Data Professional,10 to 20 years,1000+,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,We test the database at the end of each iteration as part of incremental system testing,,,,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,XML modeling of data structures,,I don't know,,,,,I don't know
Developer,20+ years,1000+,North America,Public (Government),They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
IT Management,5 to 10 years,11 to 50,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,20+ years,11 to 50,Europe,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a month,I don't know,Yes,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,I don't know,We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,11 to 50,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within three months,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",,,,,We validate data values as they go into the database,,,,,,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,We have one and developers find it useful,,We just have a single logical model,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
IT Management,5 to 10 years,11 to 50,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",,,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Tester,5 to 10 years,1 to 10 ,North America,Private,I don't know,"It's pretty good, but with a few problems",This is too risky for us to even attempt,I don't know,Yes,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,UML class diagramming of the object schema,,,I don't know,,,,,I don't know
Developer,5 to 10 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,1000+,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,I don't know,I don't know,Other (please specify),I don't know,I don't know,,,,,,I don't know,,,,,,,,,Other (please specify),I don't know.. I don't work in IT and don't program against coporate databases.,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,5 to 10 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",It would likely take us longer than three months,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,,,,I don't know
Project Manager,20+ years,11 to 50,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,,,,,,,Other (please specify),Validation is only done when a problem is found in production,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
,,,,,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a month,I don't know,I don't know,"We have problems, but no strategy to fix them",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Operations/Support Staff,20+ years,1000+,North America,Public (Government),They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,We don't have data quality problems,,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
IT Management,20+ years,11 to 50,North America,Private,They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,We validate column constraints ,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within a month,"No, we've chosen not to do this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,We validate referential integrity (RI) constraints implemented within the database,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,"We've tried to create one several times, and have pretty much failed each time",We don't do enterprise data modeling at all,,,,
Developer,20+ years,1 to 10 ,North America,Public (Government),They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this",We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,11 to 50,North America,Public (Government),They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,20+ years,1000+,North America,Private,We don't have any data naming conventions,We have serious data quality problems,We could do it in a single day,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,I don't know,We don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've tried to create one several times, and have pretty much failed each time",We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,501 to 1000,North America,Public (Government),We don't have any data naming conventions,"It's pretty good, but with a few problems",This is too risky for us to even attempt,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",We don't have data quality problems,,Yes,,,,,,I don't know,We validate data values as they go into the database,,,,,We validate referential integrity (RI) constraints implemented within the database,,,,,Data modeling is usually done in an evolutionary manner throughout the project,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,501 to 1000,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,5 to 10 years,101 to 500,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,We validate column constraints ,,,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,5 to 10 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,101 to 500,North America,Private,They're documented and enforced by our data group,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,UML class diagramming of the object schema,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,UML class diagramming of the object schema,XML modeling of data structures,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
IT Management,20+ years,1 to 10 ,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and try not to make the situation any worse",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,We've never tried to create one because we haven't considered it,,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,101 to 500,North America,Public (Government),I don't know,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,I don't know,,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,,,,I don't know
Project Manager,20+ years,501 to 1000,North America,Public (Government),They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it in a single day,Yes,Yes,We don't have data quality problems,,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,I don't know,,,,We have both a logical model and some physical models  ,
Data Professional,20+ years,1000+,North America,Public (Government),We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a week,I don't know,I don't know,"We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
Developer,5 to 10 years,11 to 50,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, and try not to make the situation any worse",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Other,20+ years,1 to 10 ,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,None,1 to 10 ,South America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",We could do it within three months,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,"No, we don't have adequate resources",,,,,,I don't know,We validate data values as they go into the database,We validate data values as they come out of a database,,,We validate the view definitions implemented within the database ,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"Data modeling is usually done up front, early in the project",We don't do any data modeling,,,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, but no strategy to fix them",,I don't know,,,,,,I don't know,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,,We validate column constraints ,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,,,,I don't know
Developer,10 to 20 years,101 to 500,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
Project Manager,10 to 20 years,51 to 100,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a month,Yes,Yes,Other (please specify),"The data quality issues are due to poor user input.  As we find issues sometimes a business analyst will update the data directly in the database.  In all cases, we find a way to prevent it from happening in the future either through user training or an update of our application through our normal change management process.",Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Developer,20+ years,101 to 500,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",It would likely take us longer than three months,I don't know,I don't know,"We have problems, but no strategy to fix them",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",We don't do any structural modeling,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"We have one, but developers rarely use it",,We just have a single logical model,,,
Quality Assurance,5 to 10 years,51 to 100,North America,Public (Government),They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,Yes,Yes,"We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,Yes,,"We test continuously throughout data warehouse development, following a TDD approach",,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,We have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
Data Professional,20+ years,51 to 100,North America,Public (Government),They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,Less than 2 years,1 to 10 ,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this","No, we've chosen not to do this",We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,We validate data values as they go into the database,,,,,,,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,"We've failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
IT Management,20+ years,101 to 500,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,We've never tried to create one because we haven't considered it,,,,We have both a logical model and some physical models  ,
Developer,20+ years,1000+,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,I don't know,I don't know,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,I don't know,,,,,UML class diagramming of the object schema,,,We have one and developers find it useful,,,,,I don't know
Developer,10 to 20 years,101 to 500,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,I don't know,I don't know,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,51 to 100,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and try not to make the situation any worse",,Yes,,"We test continuously throughout data warehouse development, following a TDD approach",,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",We don't do any structural modeling,,,,,,,"Data modeling is usually done up front, early in the project",We don't do any data modeling,,,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Data Professional,20+ years,501 to 1000,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",This is too risky for us to even attempt,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,Physical data modeling of the database schema,,,,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",We don't have data quality problems,,Yes,,,,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,11 to 50,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within three months,I don't know,I don't know,Other (please specify),We have problems and clean them up manually as encountered.,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,,,,,,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,,,We just have physical data models describing existing production data sources,,
Project Manager,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within three months,"No, we haven't even thought of doing this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,Yes,,,,We test the database at the end of the development lifecycle as part of final system testing,,,,,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,XML modeling of data structures,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Operations/Support Staff,5 to 10 years,11 to 50,North America,Public (Government),They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,"We've tried to create one several times, and have pretty much failed each time",,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Operations/Support Staff,10 to 20 years,101 to 500,North America,Private,They're documented but not followed consistently,"It's pretty good, but with a few problems",It would likely take us longer than three months,I don't know,I don't know,"We have problems, but no strategy to fix them",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We have one, but developers rarely use it",,,,,I don't know
Developer,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 years,101 to 500,North America,Private,They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it in a single day,Yes,Yes,Other (please specify),We have problems.  Larger known problems are addressed.  Other items which are viewed as upcoming potential problems are planned for appropriately before they become major.,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,501 to 1000,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,1 to 10 ,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it in a single day,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and try not to make the situation any worse",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
IT Management,20+ years,501 to 1000,North America,Private,They're documented and enforced by our data group,We have serious data quality problems,We could do it within a week,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, but no strategy to fix them",,"No, we don't have adequate resources",,,,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,"We've failed several times in the past,  but will likely attempt this again",,,,We have both a logical model and some physical models  ,
Business Stakeholder,20+ years,11 to 50,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,XML modeling of data structures,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Developer,10 to 20 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,501 to 1000,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,I don't know,I don't know,"We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,,,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,"Most of our data sources are very good, but some are a complete mess",We could do it within a week,I don't know,I don't know,"We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,We don't do any structural modeling,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,We've never tried to create one due to lack of resources,,,,,I don't know
Developer,10 to 20 years,501 to 1000,North America,Private,They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,We test the database at the end of the development lifecycle as part of final system testing,,,We validate data values as they go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,We just have physical data models describing existing production data sources,,
Data Professional,20+ years,51 to 100,North America,Public (Government),They're documented and enforced by our data group,"It's pretty good, but with a few problems",We could do it in a single day,Yes,Yes,We don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach","We test continuously throughout data warehouse development, following a TDD approach",We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,We validate data values as part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,We validate data values as they go into the database,We validate data values as they come out of a database,We validate our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,,XML modeling of data structures,,We have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
IT Management,10 to 20 years,101 to 500,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within three months,"No, we've chosen not to do this",Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,UML class diagramming of the object schema,,,I don't know,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,I don't know,,,We just have physical data models describing existing production data sources,,
IT Management,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,"Most of our data sources are very good, but some are a complete mess",We could do it within a month,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,We test the database at the end of each iteration as part of incremental system testing,We test the database at the end of the development lifecycle as part of final system testing,,,,We validate data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,,,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Developer,10 to 20 years,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,10 to 20 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,1 to 10 ,North America,Public (Government),We don't have any data naming conventions,We have serious data quality problems,This is too risky for us to even attempt,I don't know,I don't know,"We have problems, but no strategy to fix them",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,101 to 500,North America,Private,We don't have any data naming conventions,"It's pretty good, but with a few problems",We could do it within three months,I don't know,I don't know,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,I don't know,,,,,,I don't know,,We validate data values as they come out of a database,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,,,,I don't know
Developer,10 to 20 years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,501 to 1000,North America,Private,They're documented and willingly followed by developers,"Most of our data sources are very good, but some are a complete mess",It would likely take us longer than three months,Yes,Yes,"We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),None of that sounds vaguely familiar.,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,Physical data modeling of the database schema,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,51 to 100,North America,Private,They're documented and willingly followed by developers,"It's pretty good, but with a few problems",We could do it within a week,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,I don't know,,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Operations/Support Staff,20+ years,1000+,North America,Private,They're documented and enforced by our data group,It's perfect,We could do it in a single day,"No, we've chosen not to do this",Yes,We don't have data quality problems,,Yes,,,We test the database at the end of each iteration as part of incremental system testing,,,,We validate data values as they go into the database,We validate data values as they come out of a database,,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schem