Answer:
Following are the solution to this question:
Explanation:
In essence, both issues (relevant) were addressed, that form the design of the system, and all of the information collected and during initial analysis along with all subsequent stages will, in turn, affect the design of the system. Being aware, that perhaps the data is obtained to establish the entities, attributes, or relations. In particular, partnerships, clearly outline, or cardinal-ties are shaped by company policies derived from the creator's information. Example problems and the probable effects on the layout may be:
It will create the file concurrently for all depts, or would like to build and execute the database simultaneously with one dept?
How would the work be to design affect the development process? In other terms, determine the range of the system as well
as its limits about the bottom-up, centralized, or decentralized.
Do you want, and would you like an integrated framework to develop a single module? (Inventory, production, shipping, billing, etc.)
Would you like a product code, output change, and form of controlling the bolts and bolts and dept? Impact: design of the logical and physical server.
Perhaps you'd like to monitor the sources of every lot a raw resources for the nuts and bolts manufacturing? Impact: design of the logical and physical server. Model E-R.
Perhaps you'd like to monitor consumers receiving shipments of bolts and nuts? Impact: design of the logical and physical database. ER model.
Its documents will you demand, or to whom can these documents be transmitted? What specific reporting requirements?
Reactions to such concerns relate to the design, execution, testing, or subsequent functioning of the logical and physical system.
