Explain the translation of analysis model into design model.
Software design sits at the technical kernel of software engineering and is applied regardless of thesoftware process model that is used. Beginning once software requirements have been analyzed andspecified, software design is the first of three technical activities—design, code generation, and test—thatare required to build and verify the software. Each activity transforms information in a manner thatultimately results in validated computer software.Each of the elements of the analysis model provides information that is necessary to create the fourdesign models required for a complete specification of design. The flow of information during softwaredesign is illustrated in above figure.Software requirements, manifested by the data, functional, and behavioral models, feed the designtask. Using one of a number of design methods (discussed in later chapters), the design task produces adata design, an architectural design, an interface design, and a component design.The data design transforms the information domain model created during analysis into the datastructures that will be required to implement the software. The data objects and relationships defined inthe entity relationship diagram and the detailed data content depicted in the data dictionary provide thebasis for the data design activity.Part of data design may occur in conjunction with the design of software architecture. More detaileddata design occurs as each software component is designed. The architectural design defines therelationship between major structural elements of the software, the ?design patterns? that can be used toachieve the requirements that have been defined for the system, and the constraints that affect the way inwhich architectural design patterns can be appliedThe architectural design representation the framework of a computer-based system—can be derivedfrom the system specification, the analysis model, and the interaction of subsystems defined within theanalysis model. The interface design describes how the software communicates within itself, withsystems that interoperate with it, and with humans who use it. An interface implies a flow of information(e.g., data and/or control) and a specific type of behavior. Therefore, data and control flow diagramsprovide much of the information required for interface design.The component-level design transforms structural elements of the software architecture into aprocedural description of software components. Information obtained from the PSPEC, CSPEC, and STDserve as the basis for component design.