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 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,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 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,,,,,,,,,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 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 just have a single logical model,,We have both a logical model and some physical models  ,
Developer,20+ 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 within a month,"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 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 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,,,XML modeling of data structures,,"We have one, but developers rarely use it",,,,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,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),"Each silo has its own data stores (amorpheous, no data dictionary or repository; all application driven.  Data is and has always been an afterthought.  We await for doomsday to make a change.","No, we don't have adequate resources",,,,,,I don't know,We validate data values as they go into the database,,,,,,,,,,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,,,,,,,I don't know,"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,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",We could do it within a month,"No, we haven't even thought of doing 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 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",We don't do any structural modeling,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,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 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",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,Other (please specify),,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,2 to 5 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,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 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,,,,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 have both a logical model and some physical models  ,
Developer,20+ years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,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 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 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,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,,,,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,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 a month,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 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,,,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, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,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",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",,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 our object-to-relational (O/R) mappings,,,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,,,,,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,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,51 to 100,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'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 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 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",,,Detailed logical data modeling,Physical data modeling of the database 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,,
Data Professional,5 to 10 years,101 to 500,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'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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,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",This is too risky for us to even attempt,Yes,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,,"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,,,,,,I don't know,,High-level domain modeling,,Physical data modeling of the database schema,,,,We've never tried to create one due to lack of resources,,,,,I don't know
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",,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 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,,,,I don't know,,,,,,,I don't know,I don't know,,,We just have physical data models describing existing production data sources,,
IT Management,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,"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 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 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",,,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",,,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 just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Project Manager,10 to 20 years,1 to 10 ,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",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 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",,,,Physical data modeling of the database schema,,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,,,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  ,
Project Manager,5 to 10 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,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 within a month,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,,,,,,,,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 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,5 to 10 years,1 to 10 ,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, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,,I don't know,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,,,,,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,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'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 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,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,,,,I don't know,,,,,,,I don't know,I don't know,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",This is too risky for us to even attempt,"No, we've chosen not to do this","No, we've chosen not to do this",Other (please specify),"Really, it depends upon the client",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 column constraints ,We validate default column values,Other (please specify),"Again, it depends upon the client how much we are able to do",Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data 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'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 enforced by our data group,"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 have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,,I don't know,,,,,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",,,,Physical data modeling of the database schema,UML class diagramming of the object schema,,,We don't do any data modeling at all ,,,,,,,I don't know,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 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'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 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 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,,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Tester,Less than 2 years,1000+,North America,Private,I don't know,"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 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 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,,,,,,,,,I don't know,,,,,UML class diagramming of the object schema,,,I don't know,,,,,UML class diagramming of the object schema,,,I don't know,,,,,I don't know
Developer,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 in a single day,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 data values as they come out of a database,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,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,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,"No, we haven't even thought of doing this",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 the view definitions implemented within the database ,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,I don't know,,,,,,,I don't know,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,Private,They're documented but not followed consistently,We have serious data quality problems,We could do it within a month,"No, we've chosen not to do this",Yes,"We have problems, but no strategy to fix them",,Yes,,,,,,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,,,,,,,I don't know,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,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",Other (please specify),Problems are addressed with periodic scheduled updates of applications and data source providers.,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,,,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,,XML modeling of data structures,,We have one and developers find it useful,,,,,I don't know
Developer,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,Yes,Yes,"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 the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,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 have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
Developer,2 to 5 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 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 intend to rewrite all applications and data sources and release them simultaneously",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,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,5 to 10 years,1 to 10 ,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, 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,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout 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 just have physical data models describing existing production data sources,,
Project Manager,10 to 20 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,11 to 50,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've chosen not to do this","No, we've chosen not to do this","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 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 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'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,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 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 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 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,,,,,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
Project Manager,10 to 20 years,101 to 500,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 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 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 ,,,,"Data modeling is usually done up front, early in 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 up front, early in the project",,,Detailed logical data modeling,,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Business Stakeholder,20+ years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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'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 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,,,Detailed logical data modeling,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,I don't know,,,We just have physical data models describing existing production data sources,,
Other,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",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,,"No, we never even thought of doing it",,,,,,I don't know,We validate data values as they go into the database,,,,,,,,,,I don't know,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,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 week,I don't know,I don't know,"We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,Other (please specify),I don't know,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,I don't know,,,,,I don't know
Developer,5 to 10 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 years,11 to 50,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'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 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 column constraints ,,,,"Data modeling is usually done up front, early in 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,,,,
Operations/Support Staff,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,"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 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 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,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,XML modeling of data structures,,"We have one, but developers rarely use it",,,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,11 to 50,North America,Public (Government),I don't know,"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, 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 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,,,"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,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 week,"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 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,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,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,1 to 10 ,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 haven't even thought of doing this",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 data values as they go into the 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",We don't do any data modeling,,,,,,,We have one and developers find it useful,,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,"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",,,,,,I don't know,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 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",,"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,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,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,2 to 5 years,11 to 50,North America,Public (Government),I don't know,"It's pretty good, but with a few problems",We could do it within a week,I don't know,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 column constraints ,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
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 a month,"No, we haven't even thought of doing 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 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",,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'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,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 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 up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,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  ,
Project Manager,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",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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),NA,"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,,,XML modeling of data structures,,We've never tried to create one because we haven't considered it,,We just have a single logical model,,,
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,"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 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 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,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,We have one and developers find it useful,,We just have a single logical model,,,
Data Professional,10 to 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 within a month,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 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, .)",,,,,,,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,,,,Physical data modeling of the database schema,,,,"We have one, but developers rarely use 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,1 to 10 ,North America,Public (Government),They're documented but not followed consistently,We have serious data quality problems,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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 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 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 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,,,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 just have physical data models describing existing production data sources,,
Business Stakeholder,20+ years,11 to 50,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've chosen not to do this",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,,,,,,,,,,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",,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,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",Yes,"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 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 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,,,,"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,We have both a logical model and some physical models  ,
Data Professional,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",,,,,,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 referential integrity (RI) constraints implemented within the database,,,,,"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, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Developer,2 to 5 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 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 our object-to-relational (O/R) mappings,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,I don't know,,,,,I don't know
Operations/Support Staff,2 to 5 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 years,1 to 10 ,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 within a month,"No, we haven't even thought of doing 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 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 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,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain 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,501 to 1000,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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",This is too risky for us to even attempt,"No, we haven't even thought of doing this",Yes,"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 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 don't do any data modeling at all ,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,We don't do enterprise data modeling at all,,,,
Developer,20+ years,51 to 100,North America,Private,I don't know,It's perfect,We could do it in a single day,I don't know,I don't know,We don't have data quality problems,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,None,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 week,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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in 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,,,,,I don't know
Developer,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",We could do it within a month,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 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 ,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, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
IT Management,20+ years,101 to 500,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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",It would likely take us longer than three months,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,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
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 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 each iteration as part of incremental system testing,,,,,,,,,,,,Other (please specify),I'm currently concerned with metadata of many systems rather than this database specific level.,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Data Professional,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",This is too risky for us to even attempt,"No, we haven't even thought of doing this",Yes,"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 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 due to lack of resources,We don't do enterprise data modeling at all,,,,
IT Management,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 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",,"No, we don't have adequate resources",,,,,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 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,,,,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,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,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 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,,,,,,,I don't know,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,I don't know,,,,We have both a logical model and some physical models  ,
Business Stakeholder,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,"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 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,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,UML class diagramming of the object schema,,,We have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
Developer,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 within a week,I don't know,I don't know,Other (please specify),"We have problems, and they will likely remain in legacy systems, but we have plans to avoid them in the future.",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 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",,,Detailed logical data modeling,,,XML modeling of data structures,,I don't know,,,,,,,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,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,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 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",,,Detailed logical data modeling,Physical data modeling of the database schema,,,,I don't know,,,,,,,I don't know,I don't know,,We just have a single logical model,We just have physical data models describing existing production data sources,,
Developer,5 to 10 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,101 to 500,North America,Public (Government),They're documented but not followed consistently,"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 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 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,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  ,
Project Manager,2 to 5 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,1000+,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 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 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 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 don't do enterprise data modeling at all,,,,
Developer,20+ years,11 to 50,North America,Private,We don't have any data naming conventions,We have serious data quality 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 try not to make the situation any worse",,"No, we don't have adequate resources",,,,,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 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 due to lack of resources,We don't do enterprise data modeling at all,,,,
Data Professional,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",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,,,,,,,,,Other (please specify),Unknown,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,We don't do any data modeling,,,,,,,We've never tried to create one because we haven't considered it,,,,,I don't know
IT Management,10 to 20 years,1 to 10 ,North America,Private,We don't have any data naming conventions,It's perfect,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 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 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,,,,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,,
Other,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 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,,
Developer,5 to 10 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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, 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 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 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,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,,
Developer,5 to 10 years,1 to 10 ,North America,Private,They're documented but not followed consistently,We have serious data quality problems,We could do it within a month,Yes,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 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 default column values,,,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,,,,
Project Manager,5 to 10 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 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 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,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,"We have one, but developers rarely use it",,We just have a single logical model,,,
Developer,10 to 20 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,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,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 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'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 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 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,,,,,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,,,,
Developer,5 to 10 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'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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,None,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,101 to 500,North America,Public (Government),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 month,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,We validate data values as they go into the database,,,,,,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,I don't know,,,,,,,I don't know,I don't know,,,,We have both a logical model and some physical models  ,
IT Management,10 to 20 years,51 to 100,North America,Private,I don't know,"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",,I don't know,,,,,,I don't know,,,,,,,,,,,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 failed several times in the past,  but will likely attempt this again",,,,,I don't know
Data Professional,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,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 they go into the 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,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 have both a logical model and some physical models  ,
Developer,20+ years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,Less than 2 years,1 to 10 ,North America,Private,I don't know,"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, but no strategy to fix them",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Operations/Support Staff,20+ years,1 to 10 ,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,"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 the development lifecycle as part of final system testing,,,,,,,We validate the view definitions implemented within the database ,,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,I don't know,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
Project Manager,None,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'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 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,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,,,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,Less than 2 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",This is too risky for us to even attempt,"No, we haven't even thought of doing this",Yes,Other (please specify),"We cannot modify our ERP schema, but often find and correct problems with production data during Data Warehousing development, and subsequently take measures to prevent recurrence",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 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 in an evolutionary manner throughout the project,,,,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,20+ years,1000+,Europe,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,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,,,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,I don't know,We don't do enterprise data modeling at all,,,,
Developer,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 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",,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 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,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,,,Physical data modeling of the database schema,,,,I don't know,,,We just have physical data models describing existing production data sources,,
Developer,20+ 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",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 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 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 have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 years,1000+,North America,Private,They're documented and enforced by our data group,"It's pretty good, but with a few problems",It would likely take us longer than three months,I don't know,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,,,,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 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,Physical data modeling of the database schema,,XML modeling of data structures,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,I don't know,,,,,I don't know
Tester,5 to 10 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 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 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,,,,,,,I don't know,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Other,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 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",,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 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,,,,"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,We have both a logical model and some physical models  ,
Data Professional,5 to 10 years,51 to 100,North America,Private,They're documented but not followed consistently,It's perfect,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",,Yes,,,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,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,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,1 to 10 ,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",,"No, we never even thought of doing it",,,,,,I don't know,We validate data values as they go into the database,,,,,,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,,,,
Developer,10 to 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",,I don't know,,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,We just have a single logical model,,,
Project Manager,5 to 10 years,501 to 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 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 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 ,We validate default column values,,,,,,,,,,,,,,,,,,,,,,,,
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,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,,,,,,,,,Other (please specify),Do not know,"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,,,I don't know,,,,,I don't know
Developer,10 to 20 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,None,51 to 100,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,Yes,Yes,"We have problems, but no strategy to fix them",,Yes,,,,,,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,,,,,,,,,"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,,,,,I don't know
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",Other (please specify),NA,"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 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 default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,,,,,I don't know
Developer,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 a week,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),We're not really testing.,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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,51 to 100,North America,Private,We don't have any data naming conventions,We have serious data quality 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 try not to make the situation any worse",,"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),We occasionally visualy inspect the data and make a judgement call on its quality,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,"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,1000+,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 three months,Yes,Yes,"We have problems, and have a database refactoring strategy in place to evolve the data sources over time",,,,,,,,,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,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 physical data models describing existing production data sources,,
Developer,10 to 20 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 a week,Yes,Yes,"We have problems, but no strategy to fix them",,"No, we don't have adequate resources","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,,,,,,,,,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,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,5 to 10 years,501 to 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 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 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,,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,We've never tried to create one because we haven't considered it,,,,We have both a logical model and some physical models  ,
Developer,5 to 10 years,11 to 50,North America,Private,They're documented but not followed consistently,It's perfect,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 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,,,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Project Manager,5 to 10 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, but no strategy to fix them",,"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 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 default column values,,,,,,,,,,,,,,,,,,,,,,,,
Tester,5 to 10 years,101 to 500,North America,Public (Government),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,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,,,,,,,,,,,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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,101 to 500,North America,Private,We don't have any data naming conventions,It's perfect,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 don't have data quality problems,,"No, we never even thought of doing it","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,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,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,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,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,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Data Professional,10 to 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 month,Yes,Yes,"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 the development lifecycle as part of final system testing,,,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,We don't do any data modeling at all ,,,,,,,I don't know,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 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",Other (please specify),"As our primary data sources are ported to our primary data sets, data problems are resolved and documented.",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 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 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,501 to 1000,North America,Private,I don't know,"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,Yes,"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 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",,,,,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 just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,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",This is too risky for us to even attempt,"No, we haven't even thought of doing this",Yes,"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 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 view definitions implemented within the 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,,,,,,I don't know,,We don't do any data modeling,,,,,,I don't know,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,,,
Developer,20+ 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 within a week,"No, we haven't even thought of doing this","No, we've chosen not to do this",Other (please specify),Our data is cleaned/verified on entry and then maintained through the user interface,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 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",,,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,,,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Other,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 in a single day,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 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 come out of a database,,,,,We validate column constraints ,,,,I don't know,,High-level domain 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,,,,,I don't know,We don't do enterprise data modeling at all,,,,
IT Management,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,"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,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,,,,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,10 to 20 years,501 to 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 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 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,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,2 to 5 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,I don't know,I don't know,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 column constraints ,,,,"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,,,,,I don't know,,,,,I don't know
Data Professional,20+ 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 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",,I don't know,,,,,,I don't know,,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",We don't do any structural modeling,,,,,,,"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,,,,
Tester,20+ years,101 to 500,North America,Private,I don't know,"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",,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
Data Professional,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 in a single day,"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 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,,,,,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
Developer,5 to 10 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 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 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 column constraints ,,,,"Data modeling is usually done up front, early in 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 up front, early in the project",,,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 just have physical data models describing existing production data sources,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 in a single day,"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 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 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,,,,,,,I don't know,"We have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Developer,5 to 10 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,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,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout 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,I don't know,,,,,I don't know
Other,10 to 20 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 a week,"No, we haven't even thought of doing this",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 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",,,,,,,I don't know,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,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 month,"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 continuously throughout data warehouse development, following a TDD approach",,,,,,,,"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",,,,,UML class diagramming of the object schema,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
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 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 go into the database,We validate data values as they come out of a database,,,,,We validate column constraints ,We validate default column values,,,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 due to lack of resources,,,,,I don't know
Developer,10 to 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,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",,,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,,,,,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Project Manager,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 three months,"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 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,,,"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 and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,20+ years,1 to 10 ,North America,Public (Government),They're documented but not followed consistently,We have serious data quality problems,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, and try not to make the situation any worse",,"No, we don't have adequate resources",,"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,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,,,,,I don't know
Data Professional,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 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 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 ,,,,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
Business Stakeholder,5 to 10 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 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,Yes,Yes,Other (please specify),"We have problems and are addressing them with multiple strategies, including refactoring, data source correction, and knowledge management training.",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,,,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,,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,None,501 to 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 within three months,I don't know,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,,,,,,,I don't know,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 don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,101 to 500,North America,Private,We don't have any data naming conventions,We have serious data quality 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",,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,20+ 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 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 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,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,,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,101 to 500,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,I don't know,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, .)",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,,XML modeling of data structures,,"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 have both a logical model and some physical models  ,
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 month,I don't know,Yes,"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 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,,,,XML modeling of data structures,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,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 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 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 ,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,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 within a month,Yes,Yes,"We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources",,,,,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 in an evolutionary manner throughout 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 due to lack of resources,We don't do enterprise data modeling at all,,,
Developer,10 to 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 within a month,"No, we've chosen not to do this",Yes,Other (please specify),A mix of refactoring strategy and application workarounds or interfaces.,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 ,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,,,,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  
Business Stakeholder,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,"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 each iteration as part of incremental system testing,,,,,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 have one, but developers rarely use it",,We just have a single logical model,,
IT Management,20+ years,101 to 500,North America,Private,They're documented but not followed consistently,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, 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 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 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,,,
Developer,10 to 20 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,"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",,,,,,I don't know,,,,,,,,,,,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 a month,Yes,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 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 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",,High-level domain modeling,,,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  
Developer,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 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",,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 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,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,UML class diagramming of the object schema,,,I don't know,,,,We have both a logical model and some physical models  
Operations/Support Staff,5 to 10 years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,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, 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 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 ,We validate default column values,,,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,,,,,,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,"No, we've chosen not to do this",Yes,We don't have data quality problems,,Yes,,"We test continuously throughout data warehouse development, following a TDD approach",,,,,,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,High-level domain 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,UML class diagramming of the object schema,,,"We have one, but developers rarely use it",,We just have a single logical model,,
Other,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 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",,"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 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,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, but developers rarely use it",,,We just have physical data models describing existing production data sources,
Developer,10 to 20 years,501 to 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 within a month,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 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 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 because we haven't considered it,We don't do enterprise data modeling at all,,,
Project Manager,20+ years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,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 week,Yes,Yes,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 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 ,,,,,,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,,,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 just have a single logical model,,
Project Manager,10 to 20 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 a week,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 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,UML class diagramming of the object schema,XML modeling of data structures,,We have one and developers find it useful,,We just have a single logical model,,
Business Stakeholder,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",This is too risky for us to even attempt,"No, we've chosen not to do this","No, we've chosen not to do this",Other (please specify),The problems are slight and manually repaired when needed,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),n/a,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 due to lack of resources,We don't do enterprise data modeling at all,,,
Developer,20+ years,1000+,North America,Private,I don't know,"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 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 column constraints ,We validate default column values,,,Data modeling is usually done in an evolutionary manner throughout 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,,,,,,,I don't know,I don't know,,We just have a single logical model,,,
Developer,20+ years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,1000+,North America,Private,I don't know,"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 have a database refactoring strategy in place to evolve the data sources over time",,Yes,,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,XML modeling of data structures,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Other,10 to 20 years,1000+,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 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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,1 to 10 ,North America,Public (Government),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",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,We validate column constraints ,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Operations/Support Staff,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,I don't know,"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 referential integrity (RI) constraints implemented within the database,We validate column constraints ,We validate default column values,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
Developer,None,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,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 the development lifecycle as part of final system testing,,,,,,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Other,20+ years,1 to 10 ,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",This is too risky for us to even attempt,"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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,5 to 10 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,"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 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 column constraints ,We validate default column values,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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 month,"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 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 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,,I don't know,,,,,,,I don't know,I don't know,,We just have a single logical model,,,
Developer,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 three months,"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 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 up front, early in the project",We don't do any structural modeling,,,,,,,Data modeling is usually done in an evolutionary manner throughout 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,5 to 10 years,1 to 10 ,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",,"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 default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,I don't know,,High-level domain 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,1 to 10 ,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, 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,,,,,,,,,,,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,We don't do enterprise data modeling at all,,,,
Other,10 to 20 years,11 to 50,North America,Public (Government),I don't know,"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 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 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,,,,,,,,,"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 because we haven't considered it,,,,,I don't know
Developer,5 to 10 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 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 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 the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,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 because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,20+ years,1 to 10 ,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 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 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 our object-to-relational (O/R) mappings,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,20+ years,51 to 100,North America,Private,I don't know,"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 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 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,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Business Stakeholder,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 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 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 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 up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,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,,,,XML modeling of data structures,,"We have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Developer,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 within a month,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 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
Project Manager,10 to 20 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Quality Assurance,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 in a single day,Yes,Yes,"We have problems, but no strategy to fix them",,I don't know,,,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,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,We validate column constraints ,,,,"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 have one, but developers rarely use it",,,,,I don't know
Other,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,I don't know,"No, we've chosen not to do this","We have problems, and try not to make the situation any worse",,Yes,,,,,,I don't know,,,,,,,,,,,I don't know,,,,,,,I don't know,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,I don't know,We don't do enterprise data modeling at all,,,,
Project Manager,20+ years,51 to 100,Australia,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 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 data warehouse development, following a TDD approach",,,,,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,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,UML class diagramming of the object 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,2 to 5 years,1 to 10 ,North America,Public (Government),I don't know,"It's pretty good, but with a few problems",We could do it within a month,I don't know,I don't know,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 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 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,,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,Detailed logical data modeling,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical 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,2 to 5 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,"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 the development lifecycle as part of final system testing,,,,,,,,,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,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,"We have one, but developers rarely use it",,,,,I don't know
Data Professional,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",This is too risky for us to even attempt,I don't know,Yes,"We have problems, but no strategy to fix them",,I don't know,,,,,,I don't know,,,,,,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",,,,,,,I don't know,"Data modeling is usually done up front, early in the project",We don't do any data modeling,,,,,,,"We've failed several times in the past,  but will likely attempt this again",,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 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 a month,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 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,,,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,,,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've failed several times in the past,  but will likely attempt this again",,,,We have both a logical model and some physical models  ,
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",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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,,,"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,,,,
IT Management,10 to 20 years,11 to 50,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 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 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,,,"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 never tried to create one because we haven't considered it,,,,We have both a logical model and some physical models  ,
IT Management,20+ 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 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 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 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,,,,,"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  ,
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 within a month,"No, we haven't even thought of doing this",Yes,"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 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 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,,,,,,I don't know,,,,,,,I don't know,"We've failed several times in the past,  but will likely attempt this again",,,We just have physical data models describing existing production data sources,,
Other,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,Yes,Yes,Other (please specify),We allow customers to login and 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 test the database at the end of the development lifecycle as part of final system testing,,,,,,,,,,,Other (please specify),None of these apply. We do test availability.,"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 and developers find it useful,,We just have a single logical model,,,
Operations/Support Staff,20+ years,1000+,North America,Private,They're documented and willingly followed by developers,It's perfect,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 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,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 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  ,
Developer,2 to 5 years,51 to 100,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,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,,,,,,,,,,"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",,High-level domain modeling,Detailed logical data modeling,,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,20+ years,1000+,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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,,,We don't do any data modeling at all ,,,,,UML class diagramming of the object schema,,,We don't do any data modeling at all ,,,,,,,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,,,,
Other,Less than 2 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,20+ years,1000+,North America,Private,They're documented but not followed consistently,We have serious data quality problems,We could do it within a month,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 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 column constraints ,We validate default column values,Other (please specify),"We do all the above, but pretty casually: run the apps and see what breaks","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  ,
IT Management,10 to 20 years,1000+,North America,Private,They're documented and willingly followed by developers,It's perfect,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 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",,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 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",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 don't have adequate resources",,,,,,I don't know,,,,,,,We validate column constraints ,,,,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,,,,We have both a logical model and some physical models  ,
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,I don't know,I don't know,"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",,,,,,,,,,,,,,Other (please specify),"Daimler-chrysler developed the web based application to replace a client/middleware/server arch. and waited until the very end to try and find out what tables data was getting written to. Aaaaaand asked us the developers, who are not members of the original group who engineerd the old system, we are both 6-8mths on the job,  the system was 5 years old. so much for reverese engineering.",We don't do any data modeling at all ,,,,,UML class diagramming of the object schema,,,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,,
IT Management,5 to 10 years,11 to 50,North America,Private,We don't have any data naming conventions,We have serious data quality problems,It would likely take us longer than three months,"No, we've chosen not to do this","No, we've chosen not to do this",Other (please specify),"We have problems, and we intend to determine a database refactoring strategy to evolve the data sources over time","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 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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Data Professional,10 to 20 years,501 to 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 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",,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 the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,Detailed logical 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,,,,
Developer,2 to 5 years,1 to 10 ,North America,Public (Government),I don't know,"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",,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
Data Professional,20+ years,51 to 100,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,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 column constraints ,We validate default column values,,,We don't do any data modeling at all ,,,,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,,XML modeling of data structures,,"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,,
IT Management,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 within a week,"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,,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,We don't do any data modeling at all ,,High-level domain modeling,Detailed logical data modeling,,UML class diagramming of the object schema,XML modeling of data structures,,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,,,,
Operations/Support Staff,5 to 10 years,101 to 500,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 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 within a week,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 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 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,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,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,20+ years,11 to 50,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 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",,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 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,,,,"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 have both a logical model and some physical models  ,
Developer,10 to 20 years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,5 to 10 years,1 to 10 ,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",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 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,,,,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, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,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","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,,,,,,,,,,,"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",,,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,,,,
Project Manager,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 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 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 up front, early in the project",,,Detailed logical data modeling,,UML class diagramming of the object schema,,,We don't do any data modeling at all ,,,Detailed logical data modeling,,UML class diagramming of the object 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,20+ years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 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 month,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 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 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,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,UML class diagramming of the object schema,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,,We just have physical data models describing existing production data sources,,
Developer,20+ 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've chosen not to do this","No, we've chosen not to do this",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 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,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,,XML modeling of data structures,,We have one and developers find it useful,,We just have a single logical model,,,
IT Management,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",We could do it within a week,"No, we've chosen not to do this",Yes,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 view definitions implemented within the database ,,We validate column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,,,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 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 three months,Yes,Yes,"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 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 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,,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,,,"We have one, but developers rarely use it",,We just have a single logical model,,,
IT Management,5 to 10 years,1 to 10 ,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 within a month,"No, we haven't even thought of doing this","No, we haven't even thought of doing this",Other (please specify),we are currently restructuring backup/recovery to address recently discovered data integrity and availablity 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 column constraints ,We validate default column values,,,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,We don't do any data modeling,,,,,,,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,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",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, 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 the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,,,,"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,,,"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 due to lack of resources,,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 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 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 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 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,XML modeling of data structures,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,20+ years,1 to 10 ,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,"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 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 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 just have a single logical model,We just have physical data models describing existing production data sources,,
Business Stakeholder,20+ years,1 to 10 ,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,Yes,Yes,We don't have data quality problems,,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 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,,,,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 just have a single logical model,,We have both a logical model and some physical models  ,
Developer,Less than 2 years,51 to 100,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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 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 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 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 due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,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 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",,"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 part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,,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,,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,,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,,,,
Developer,10 to 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 three months,"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 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 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,,,I don't know,,High-level domain 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,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 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",,I don't know,,,,,,I don't know,,,,"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,,,,,,I don't know,,,,,,,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,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 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 default column values,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,"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  ,
Developer,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 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 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 column constraints ,We validate default column values,,,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 due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,2 to 5 years,1 to 10 ,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 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 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 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,,,,,I don't know,,,,,,,I don't know,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,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 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 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,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,,,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Data Professional,20+ years,11 to 50,North America,Public (Government),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 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 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,,,,,,,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,10 to 20 years,51 to 100,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ 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'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 never even thought of doing it",,,,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",,High-level domain modeling,,,,XML modeling of data structures,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Developer,5 to 10 years,101 to 500,North America,Private,They're documented but not followed consistently,We have serious data quality problems,It would likely take us longer than three months,Yes,"No, we've chosen not to do this","We have problems, but no strategy to fix them",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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",We could do it within a week,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 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 don't do any data modeling at all ,We don't do any structural modeling,,,,,,,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 because we haven't considered it,We don't do enterprise data modeling at all,,,,
Data Professional,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",It would likely take us longer than 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",,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 the view definitions implemented within the database ,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,We don't do any data modeling at all ,We don't do any data modeling,,,,,,,I don't know,,,,We have both a logical model and some physical models  ,
Developer,20+ years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 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",This is too risky for us to even attempt,I don't know,"No, we haven't even thought of doing this","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,We don't do enterprise data modeling at all,,,,
IT Management,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,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 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 up front, early in 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 have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Project Manager,20+ years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,None,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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",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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,Less than 2 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 don't have data quality problems,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,1 to 10 ,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,"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,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,20+ years,1000+,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 week,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 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  ,
Developer,5 to 10 years,1 to 10 ,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Operations/Support Staff,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 week,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 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,,,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,We have one and developers find it useful,,,,,I don't know
Developer,10 to 20 years,11 to 50,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 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",,I don't know,"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 default column values,,,"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, but developers rarely use it",,,,,I don't know
Developer,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",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 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,,,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,,,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,,,,,I don't know
Developer,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, 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,,,,,,,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 don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,11 to 50,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 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",,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 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,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,,,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Quality Assurance,2 to 5 years,11 to 50,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",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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,501 to 1000,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 20 years,1000+,North America,Public (Government),I don't know,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",,I don't know,,,,,,I don't know,,,,,,,,,Other (please specify),Don't know,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,,,,
Project Manager,10 to 20 years,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 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 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",,I don't know,,,,,,I don't know,,,,,,,,,,,"Data modeling is usually done up front, early in the project",,High-level domain 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,,,,
Developer,10 to 20 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 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 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 column constraints ,,,,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 don't do enterprise data modeling at all,,,,
Developer,10 to 20 years,101 to 500,North America,Public (Government),We don't have any data naming conventions,We have serious data quality problems,We could do it within a month,"No, we haven't even thought of doing 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 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 ,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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,10 to 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 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 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 column constraints ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,Detailed logical data modeling,,,,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Developer,2 to 5 years,11 to 50,North America,Public (Government),I don't know,"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 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,,,We validate the view definitions implemented within the database ,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,5 to 10 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,1 to 10 ,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","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 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 they go into the database,We validate data values as they come out of a database,,,,,We validate column constraints ,We validate default column values,,,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,2 to 5 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 week,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 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 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",,,,,UML class diagramming of the object schema,,,I don't know,,,,,I don't know
IT Management,20+ years,101 to 500,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,"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 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 tried to create one several times, and have pretty much failed each time",,We just have a single logical model,,,
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",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",,"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 the view definitions 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 have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,20+ years,1 to 10 ,North America,Private,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),We will be rebuilding the entire database into something up-to-date and manageable,"No, we don't have adequate resources",,,,,,I don't know,,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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,2 to 5 years,11 to 50,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,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 view definitions implemented within the database ,,,We validate default column values,,,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 have one, but developers rarely use it",,We just have a single logical model,,,
Developer,10 to 20 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 a month,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 our object-to-relational (O/R) mappings,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,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,,,,XML modeling of data structures,,"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,1 to 10 ,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",It would likely take us longer than three months,I don't know,"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,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,20+ 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,"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",,"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 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,,,,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 because we haven't considered it,,,We just have physical data models describing existing production data sources,,
Developer,10 to 20 years,51 to 100,North America,Public (Government),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'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 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 come out of a database,We validate our object-to-relational (O/R) mappings,,,,,,,,We don't do any data modeling at all ,We don't do any structural 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,,,UML class diagramming of the object schema,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Developer,5 to 10 years,51 to 100,North America,Private,They're documented but not followed consistently,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, 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 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,,,,I don't know,,,,,,,I don't know,"We've failed several times in the past,  but will likely attempt this again",,,,We have both a logical model and some physical models  ,
Quality Assurance,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 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",,I don't know,,,,,,I don't know,,,,,,,,,Other (please specify),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,20+ years,1 to 10 ,North America,Private,They're documented but not followed consistently,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",Other (please specify),We treat this as an issue for ETL or integration components.  It requires constant evolution.,"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,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,,,,,"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 and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),none,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,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, and try not to make the situation any worse",,"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,,,,,,,,,,"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 because we haven't considered it,,,We just have physical data models describing existing production data sources,,
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",We could do it in a single day,Yes,Yes,"We have problems, and try not to make the situation any worse",,"No, we don't have adequate resources","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 column constraints ,,,,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,,,Detailed logical data modeling,,,,,"We've failed several times in the past,  but will likely attempt this again",,,,,I don't know
Developer,2 to 5 years,1000+,North America,Public (Government),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 in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,"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 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",,,,,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 don't do enterprise data modeling at all,,,,
Other,10 to 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 in a single day,I don't know,I don't know,Other (please specify),we have problems and 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,,,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Data Professional,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",It would likely take us longer than three months,"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 the development lifecycle as part of final system testing,,,,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",,,,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,,We just have physical data models describing existing production data sources,,
IT Management,20+ 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 month,Yes,Yes,"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 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 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 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 have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Developer,20+ years,51 to 100,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Quality Assurance,10 to 20 years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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 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",,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 referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Project Manager,5 to 10 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 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 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,,Physical data modeling of the database schema,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,I don't know,,,,,I don't know
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,Yes,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 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 ,We validate default column values,,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,I don't know,,,,,I don't know
Developer,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,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 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 ,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,,,,,,Data modeling is usually done in an evolutionary manner throughout 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,,,
IT Management,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've chosen not to do this","No, we've chosen not to do this","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 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 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,5 to 10 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,"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 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 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,,,,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  ,
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",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,,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,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,,,,,I don't know
Project Manager,20+ years,101 to 500,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 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, .)",,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,Physical data modeling of the database schema,,,,We don't do any data modeling at all ,,,,,,,I don't know,"We've failed several times in the past,  but will likely attempt this again",,,We just have physical data models describing existing production data sources,,
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 in a single day,Yes,"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,,,,,,,,,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,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,,,,
Operations/Support Staff,10 to 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 within a month,"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 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 the view definitions implemented within the database ,,,,,,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 up front, early in the project",,High-level domain modeling,Detailed logical data modeling,,,,,We've never tried to create one because we haven't considered it,,We just have a single logical model,,,
Business Stakeholder,20+ years,1 to 10 ,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 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 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 ,,,,We don't do any data modeling at all ,We don't do any structural modeling,,,,,,,I don't know,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,,,,
IT Management,10 to 20 years,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,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 in an evolutionary manner throughout the project,,,Detailed logical data modeling,,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,"We've failed several times in the past,  but will likely attempt this again",,,We just have physical data models describing existing production data sources,,
Project Manager,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've chosen not to do this","No, we've chosen not to do this","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 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 ,,,,"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 tried to create one several times, and have pretty much failed each time",,We just have a single logical model,,,
Developer,10 to 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 in a single day,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,,,,,,,,,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 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,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,,,,,,,,,,,"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,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,,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,,
Data Professional,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 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 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 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 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,,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  ,
Quality Assurance,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,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 within a month,"No, we've chosen not to do this",Yes,Other (please specify),"We have few problems, but address them as soon as they are identified.",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 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 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 due to lack of resources,,,,We have both a logical model and some physical models  ,
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,"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 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 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",,,Detailed logical data modeling,,,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Business Stakeholder,20+ 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 don't have data quality problems,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,51 to 100,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,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 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 in an evolutionary manner throughout the project,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,"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,51 to 100,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've chosen not to do this",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 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 column constraints ,,,,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,,,"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,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
IT Management,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",This is too risky for us to even attempt,"No, we haven't even thought of doing 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 go into the database,We validate data values as they come out of a database,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 years,11 to 50,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 don't have data quality problems,,Yes,,"We test continuously throughout data warehouse development, following a 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,,,,,,,We have one and developers find it useful,We don't do enterprise data modeling at all,,,,
Developer,5 to 10 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,"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 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 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,,,,
Quality Assurance,10 to 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 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 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 ,,,,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,"Data modeling is usually done up front, early in the project",,,,,,,I don't know,We've never tried to create one due to lack of resources,,,,,I don't know
Developer,20+ years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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",This is too risky for us to even attempt,"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 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 default column values,,,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,"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 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,,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain 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,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",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 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 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,,,,"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 because we haven't considered it,,We just have a single logical model,,,
Project Manager,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 month,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 come out of a database,,,,,,,,,I don't know,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
Business Stakeholder,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 in a single day,"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,,"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 go into the database,We validate data values as they come out of a 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 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 don't do enterprise data modeling at all,,,,
Developer,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 don't have data quality problems,,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,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,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 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 within a month,"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 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 ,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
Developer,5 to 10 years,1000+,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 within a month,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,,,,,,,,,Other (please specify),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 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",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 data values as they go into the database,,,,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",,,,,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,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,20+ years,1 to 10 ,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 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 up front, early in 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,20+ years,1000+,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,"No, we haven't even thought of doing this","No, we haven't even thought of doing this","We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,"No, we never even thought of doing it",,,,,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 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,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 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 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 default column values,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,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 week,"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",,"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 go into the database,,,,,We validate referential integrity (RI) constraints implemented within the database,,,,,"Data modeling is usually done up front, early in 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 don't do enterprise data modeling at all,,,,
IT Management,2 to 5 years,1 to 10 ,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'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 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,,,,,,,,,"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,,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  ,
Other,10 to 20 years,1 to 10 ,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 column constraints ,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 years,501 to 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",This is too risky for us to even attempt,I don't know,I don't know,"We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),No structured testing,I don't know,We don't do any structural modeling,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",We don't do any 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,,,,I don't know
Project Manager,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 within a week,Yes,Yes,Other (please specify),"We have a few problems, and we implemented extreme programming concepts (Agile concepts) to include refactoring the DB, Table Driven Rules engine applications to quickly handle aberant data.  This allows for minor application changes without code effort.  We also use continuous integration to formally apply (long term need) the temporary rules from the Rules engine based on priority.",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 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, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,2 to 5 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 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",,"No, we don't have adequate resources",,,,,,I don't know,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,,,,,,I don't know,,,,,I don't know
IT Management,20+ years,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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,"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,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,20+ years,1000+,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,10 to 20 years,1000+,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,Yes,Yes,"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 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 up front, early in the project",,,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,,,,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
Developer,20+ years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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 in a single day,"No, we've chosen not to do this","No, we've chosen not to do this","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 referential integrity (RI) constraints implemented within the database,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
Project Manager,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 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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,20+ 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,"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 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 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,,,XML modeling of data structures,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,We've never tried to create one because we haven't considered it,,We just have a single logical model,,,
IT Management,10 to 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",We could do it within a month,Yes,Yes,"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 don't do any data modeling at all ,We don't do any structural modeling,,,,,,,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Project Manager,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 week,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",,,,,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 don't do any data modeling at all ,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,We just have a single logical model,,,
Developer,5 to 10 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,I don't know,I don't know,"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 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,,,,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,5 to 10 years,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,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 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",,,,Physical data modeling of the database schema,,,,"Data modeling is usually done up front, early in the project",,,,,UML class diagramming of the object schema,,,I don't know,,,,We have both a logical model and some physical models  ,
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",It would likely take us longer than three months,I don't know,I don't know,We don't have data quality problems,,"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 up front, early in the project",,,,,UML class diagramming of the object schema,XML modeling of data structures,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Developer,10 to 20 years,51 to 100,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",Other (please specify),Head in the sand approach,"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 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 due to lack of resources,We don't do enterprise data modeling at all,,,,
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 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 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 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,UML class diagramming of the object schema,,,I don't know,,High-level domain 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  ,
Developer,None,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,101 to 500,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,"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 continuously throughout application development, following a test-driven development (TDD) approach",,,,,,,,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 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 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  ,
Data Professional,10 to 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,"No, we haven't even thought of doing 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 part of the process of extracting data into reporting databases (e.g. data marts and/or data warehouses),,,,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,,,,,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,,,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 due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,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 month,I don't know,"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 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,,,,,,,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,2 to 5 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 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 our object-to-relational (O/R) mappings,,,,,,,,"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,,,,,"We have one, but developers rarely use it",We don't do enterprise data modeling at all,We just have a single logical model,,,
Operations/Support Staff,20+ years,11 to 50,North America,Private,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","We have problems, but no strategy to fix them",,"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 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 due to lack of resources,We don't do enterprise data modeling at all,,,
Developer,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 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",,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 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,We don't do any structural modeling,,,,,,,I don't know,,,,,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 just have a single logical model,,
Developer,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Stakeholder,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 don't have data quality problems,,Yes,"We test continuously throughout application development, following a test-driven development (TDD) approach",,,,,,,,,,,We validate referential integrity (RI) constraints implemented within the database,,,,,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 ,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,,,
Project Manager,20+ years,51 to 100,North America,Public (Government),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",Yes,"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 go into the database,,,"We validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,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,,,,,,,I don't know,We don't do enterprise data modeling at all,,,
Project Manager,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 don't have data quality problems,,"No, we don't have adequate resources",,,,,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 our object-to-relational (O/R) mappings,,,,,,,,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,2 to 5 years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,10 to 20 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",We could do it within a week,I don't know,I don't know,We don't have data quality problems,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,10 to 20 years,11 to 50,North America,Private,We don't have any data naming conventions,We have serious data quality 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",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,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,5 to 10 years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,5 to 10 years,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 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, .)",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",,,,Physical data modeling of the database schema,UML class diagramming of the object schema,,,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,
Developer,20+ years,101 to 500,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 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,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,5 to 10 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,"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 data values as they come out of a database,We validate our object-to-relational (O/R) mappings,,,We validate referential integrity (RI) constraints implemented within the database,We validate column constraints ,,,,I don't know,,,,,UML class diagramming of the object schema,,I don't know,"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 have both a logical model and some physical models  
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 a month,Yes,Yes,Other (please specify),Revising those that have problems; some consolidation into new systems,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,Other (please specify),Enterprise level validation for feeds into other systems,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,XML modeling of data structures,,We have one and developers find it useful,,,,We have both a logical model and some physical models  
Developer,20+ years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Operations/Support Staff,20+ 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,"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",,"No, we never even thought of doing it",,,,,,I don't know,,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,,,
Data Professional,5 to 10 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 within a week,"No, we haven't even thought of doing 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 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",,,,,UML class diagramming of the object schema,,,"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,,,
Operations/Support Staff,10 to 20 years,11 to 50,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 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,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 just have physical data models describing existing production data sources,We have both a logical model and some physical models  ,
Project Manager,10 to 20 years,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,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 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 the development lifecycle as part of final system testing,,,,,,,,,,,,,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,,,,
Quality Assurance,10 to 20 years,11 to 50,North America,Private,I don't know,"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,"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,,,,,,,,,Other (please specify),N/A,"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,,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
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",We could do it within a month,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 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 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,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 have both a logical model and some physical models  ,
Other,None,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,5 to 10 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 a week,I don't know,"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 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,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,,,,I don't know,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Project Manager,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 in a single day,"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 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,We don't do any structural modeling,,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,"We have one, but developers rarely use it",,,We just have physical data models describing existing production data sources,,
Developer,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",This is too risky for us to even attempt,I don't know,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 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 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,,,,,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Data Professional,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 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,"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 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'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,51 to 100,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,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 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 ,We validate default column values,,,We don't do any data modeling at all ,,,,,UML class diagramming of the object schema,XML modeling of data structures,,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,,,,
Developer,5 to 10 years,11 to 50,North America,Private,We don't have any data naming conventions,We have serious data quality 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 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 come out of a database,,,,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,We don't do any data modeling at all ,,High-level domain 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,"Most of our data sources are very good, but some are a complete mess",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,"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 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 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,,,,,,,I don't know,We've never tried to create one due to lack of resources,,,,,I don't know
IT Management,10 to 20 years,1000+,North America,Private,They're documented but not followed consistently,We have serious data quality problems,We could do it within a month,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 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),"Failover testing, backup & recovery testing",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 failed several times in the past,  but will likely attempt this again",We don't do enterprise data modeling at all,,,,
Developer,None,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,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",This is too risky for us to even attempt,"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 validate the functionality implemented within the database (e.g. stored procedures, stored functions, .)",We validate the view definitions implemented within the database ,,,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,,,,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,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","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",,"No, we never even thought of doing it","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 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,,,,,"Data modeling is usually done up front, early in the project",We don't do any data modeling,,,,,,,I don't know,,We just have a single logical model,,,
Developer,20+ 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,"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 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, .)",,,,,,,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 have one and developers find it useful,,We just have a single logical model,,,
Tester,10 to 20 years,51 to 100,North America,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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'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 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 up front, early in the project",,,,Physical data modeling of the database schema,,,,"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 physical data models describing existing production data sources,,
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 in a single day,I don't know,I don't know,"We have problems, but no strategy to fix them",,"No, we never even thought of doing it",,,,,,I don't know,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",,High-level domain 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,,UML class diagramming of the object schema,,,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,11 to 50,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","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,,,,,,,,,,,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 because we haven't considered it,We don't do enterprise data modeling at all,,,,
Developer,20+ years,1 to 10 ,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'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 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,,,,,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,We've never tried to create one due to lack of resources,,We just have a single logical model,,,
Project Manager,10 to 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 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 never even thought of doing it",,,,,,I don't know,,,,,,,,We validate default column values,,,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,,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Operations/Support Staff,10 to 20 years,1000+,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,"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 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,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain 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,51 to 100,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",Other (please specify),We don't have a strategy.,"No, we never even thought of doing it",,,,,,I don't know,,,,"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",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,,,,,I don't know
IT Management,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 within a month,"No, we haven't even thought of doing 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 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 column constraints ,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 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 within a week,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 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 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,,,,I don't know,,,,,,,I don't know,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Project Manager,20+ years,1000+,Europe,Public (Government),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Quality Assurance,10 to 20 years,101 to 500,North America,Private,I don't know,We have serious data quality 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",,"No, we don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),Embbed db; verified at design,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
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 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",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,5 to 10 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 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",,,,,,I don't know,,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",,High-level domain modeling,,,,,,I don't know,,,,,I don't know
Project Manager,10 to 20 years,101 to 500,North America,Private,They're documented but not followed consistently,We have serious data quality problems,This is too risky for us to even attempt,"No, we haven't even thought of doing 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 don't have adequate resources",,,,,,I don't know,,,,,,,,,Other (please specify),"Basically, manual reconcilliation of wrong wrong fields",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 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,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,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 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,,,,,,Other (please specify),It depends. We tend to only validate the things that interest us at a particular time.,Data modeling is usually done in an evolutionary manner throughout the project,,,Detailed logical data modeling,,,,,I don't know,,,Detailed logical data modeling,,,,,We've never tried to create one because we haven't considered it,,,,,I don't know
Developer,5 to 10 years,1 to 10 ,North America,Private,I don't know,"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",Other (please specify),Upgrade the database,I don't know,,,,,,I don't know,,,,,,,,,,,I don't know,,High-level domain modeling,,,UML class diagramming of the object schema,,,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
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 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 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 the functionality implemented within the database (e.g. stored procedures, stored functions, .)",,,,We validate default column values,,,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 due to lack of resources,We don't do enterprise data modeling at all,,,,
IT Management,10 to 20 years,101 to 500,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,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 within three months,Yes,Yes,"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 data warehouse development, following a 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,,,,,,,,"Data modeling is usually done up front, early in the project",,,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 just have a single logical model,We just have physical data models describing existing production data sources,,
Developer,20+ years,51 to 100,North America,Public (Government),I don't know,"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,,,,,,,,,Other (please specify),I don't know.,"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,10 to 20 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 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 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,,,,,,XML modeling of data structures,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,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  ,
Quality Assurance,5 to 10 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 a week,I don't know,I don't know,"We have problems, and try not to make the situation any worse",,"No, we never even thought of doing it",,,,,,I don't know,,,,,,,,,,,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,,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Business Stakeholder,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 three months,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,,,,,,,,,,,Other (please specify),I don't know the details of this testing.,"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,,High-level domain modeling,,,UML class diagramming of the object schema,,,We've never tried to create one due to lack of resources,,,We just have physical data models describing existing production data sources,,
Project Manager,10 to 20 years,501 to 1000,North America,Private,They're documented and enforced by our data group,We have serious data quality problems,This is too risky for us to even attempt,I don't know,Yes,Other (please specify),"We have problems, and have a team setup to fix them as we find 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),,,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 have one and developers find it useful,,,We just have physical data models describing existing production data sources,,
Developer,20+ years,101 to 500,North America,Private,We don't have any data naming conventions,We have serious data quality problems,We could do it within a month,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",,,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, .)",,,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 ,,High-level domain modeling,,,,,,We've never tried to create one because we haven't considered it,We don't do enterprise data modeling at all,,,,
Data Professional,20+ 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",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, 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 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 due to lack of resources,,,,,I don't know
Developer,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,"No, we've chosen not to do this",Yes,"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 go into the database,,,,,,,,,,We don't do any data modeling at all ,,High-level domain modeling,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,High-level domain modeling,,,,,,We've never tried to create one due to lack of resources,We don't do enterprise data modeling at all,,,,
Project Manager,2 to 5 years,11 to 50,North America,Private,They're documented but not followed consistently,We have serious data quality problems,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 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
Data Professional,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,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 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, .)",,,,,,,"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 up front, early in the project",,High-level domain modeling,,,UML class diagramming of the object schema,,,"We have one, but developers rarely use it",,,,,I don't know
Developer,5 to 10 years,1 to 10 ,North America,Public (Government),I don't know,We have serious data quality problems,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,,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 due to lack of resources,We don't do enterprise data modeling at all,,,,
Developer,20+ years,11 to 50,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,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,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 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,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,,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 don't do enterprise data modeling at all,,,,
Other,None,1 to 10 ,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 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 within a week,"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 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, .)",We validate the view definitions implemented within the database ,We validate referential integrity (RI) constraints implemented within the database,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,UML class diagramming of the object schema,,,"We have one, but developers rarely use it",,,,We have both a logical model and some physical models  ,
IT Management,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 within a week,Yes,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 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 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,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,XML modeling of data structures,,We've never tried to create one due to lack of resources,,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  ,
Operations/Support Staff,20+ years,11 to 50,Asia,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 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 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,,,"Data modeling is usually done up front, early in the project",We don't do any structural 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,,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,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 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 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 ,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,Physical data modeling of the database 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  ,
Project Manager,5 to 10 years,1000+,Asia,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 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 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,,,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 just have physical data models describing existing production data sources,,
Operations/Support Staff,20+ years,1000+,North America,Private,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,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",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, and try not to make the situation any worse",,"No, we never even thought of doing it",,,,,,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 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,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,,,,We've never tried to create one because we haven't considered it,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",We could do it within three months,"No, we've chosen not to do this","No, we haven't even thought of doing this","We have problems, and intend to rewrite all applications and data sources and release them simultaneously",,"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 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,,UML class diagramming of the object schema,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database schema,UML class diagramming of the object 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,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,"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",,,,,,I don't know,,,,"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 ,,,,I don't know,,,,,,,I don't know,I don't know,,,,,,,I don't know,I don't know,,,,,I don't know
Operations/Support Staff,20+ years,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 within a week,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",,"No, we never even thought of doing it",,,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 come out of a database,,,We validate the view definitions implemented within the database ,,,,,,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,Data modeling is usually done in an evolutionary manner throughout the project,,,,,,,I don't know,"We have one, but developers rarely use it",,,,,I don't know
Developer,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 month,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 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 ,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,UML class diagramming of the object schema,,,I don't know,,,,,,,I don't know,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,5 to 10 years,51 to 100,North America,Private,They're documented and willingly followed by developers,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, 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 column constraints ,,,,"Data modeling is usually done up front, early in the project",,High-level domain modeling,,Physical data modeling of the database 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,,XML modeling of data structures,,"We have one, but developers rarely use it",,We just have a single logical model,,,
Project Manager,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 within a month,"No, we've chosen not to do this",Yes,Other (please specify),Implement master data management throught the enterprise.,Yes,,"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,,,,,,,,"Data modeling is usually done up front, early in the project",,,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,,,,We've never tried to create one due to lack of resources,,,,We have both a logical model and some physical models  ,
Business Stakeholder,5 to 10 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 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,,,,,,,,,Other (please specify),None,We don't do any data modeling at all ,,,,,,,I don't know,We don't do any data modeling at all ,,,,,,,I don't know,I don't know,,,,,I don't know
Business Stakeholder,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,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 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,,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,,XML modeling of data structures,,We have one and developers find it useful,,,,We have both a logical model and some physical models  ,
IT Management,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 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 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 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,,,,,,,,,,,,,,,,,,,,,,,,
Tester,5 to 10 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 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 dat