Design Patterns-Origin and History: A General Repeatable Solution to a Commonly Occurring Problem in Software Design

Software design is an activity subjected to constraints Software Design specifies nature and composition of software product Software Design satisfies client needs and desires All of the mentioned Nicklaus Wirth described the first software engineering method as stepwise refinement Stepwise refinement follows its existence from 1971 It is a top down approach All of the mentioned Structural design introduced notations and heuristics Structural design emphasis on procedural decomposition The advantage is data flow representation It follows Structure chart The specification model following data flow diagram Procedures represented as bubbles Specification model is structure chart showing procedure calling hierarchy and flow of data in and out of procedures Emphasizing procedural decomposition More detailed and flexible processes Regular Notations Wide support by CASE(Computer Aided Software Engineering) Wide support by CASE, More detailed and flexible processes Transition of problem models to solution models Handling of larger and more complex products Designing Object oriented systems More procedural approach Choosing specific classes, operations Checking model’s completeness Following design task heuristics All of the mentioned Object oriented design is a far better approach compared to structural design Object oriented design always dominates structural design Object oriented design are given more preference than structural design Object oriented uses more specific notations It follows regular procedural decomposition in favor of class and object decomposition Programs are thought of collection of objects Central model represents class diagrams that show the classes comprising a program and their relationships to one another Object-oriented methods incorporates Structural methods Software Product Design Software Engineering Design Software Product & Engineering Design None of the mentioned Analysis occurs at start of product design with a product idea Analysis occurs at the end of engineering design with the SRS Product design resolution produces the design document Engineering design resolution produces the SRS Understand the problem Generate candidate solutions Iterate if no solution is adequate None of the mentioned Analyze the Problem Evaluate candidate solutions Finalize the Design None of the mentioned To frequently reanalyze the problem To generate and improve solutions only once for better output All of the mentioned None of the mentioned It begins with SRS It ends with Product Design Problem Analysis is done and end product is project mission statement None of the mentioned