Final answer:
In database design, an attribute in the conceptual phase becomes a column in the logical phase. Constraints act as rules for the database, while criteria are used to compare and evaluate aspects of the database's design.
Step-by-step explanation:
In the context of database design, an attribute in the conceptual design becomes a column or field in the logical design. During the conceptual design phase, the focus is on understanding what data needs to be stored and how different pieces of data are related; it involves creating a high-level data model that often uses entity-relationship diagrams. The transition to logical design involves converting this high-level model into a more detailed model that can be implemented in a database management system, defining the structure of each table and the columns within those tables.
A constraint in the logical design of a database is like a rule that must be followed by data in the database; for example, a constraint might require that the values in a particular column must be unique or not null. A criterion, on the other hand, is used to evaluate and compare different aspects of design such as performance, usability, or scalability. For instance, in database design, criteria could include how quickly queries can be executed or how much data the database can effectively manage.