TL;DR: A power analysis technique is developed that has been applied to two commercial microprocessors and can be employed to evaluate the power cost of embedded software and can help in verifying if a design meets its specified power constraints.
Abstract: Embedded computer systems are characterized by the presence of a dedicated processor and the software that runs on it Power constraints are increasingly becoming the critical component of the design specification of these systems At present, however, power analysis tools can only be applied at the lower levels of the design-the circuit or gate level It is either impractical or impossible to use the lower level tools to estimate the power cost of the software component of the system This paper describes the first systematic attempt to model this power cost A power analysis technique is developed that has been applied to two commercial microprocessors-Intel 486DX2 and Fujitsu SPARClite 934 This technique can be employed to evaluate the power cost of embedded software This can help in verifying if a design meets its specified power constraints Further, it can also be used to search the design space in software power optimization Examples with power reduction of up to 40%, obtained by rewriting code using the information provided by the instruction level power model, illustrate the potential of this idea >
TL;DR: In this article, it has been recognized that the two-phase version of the interrupted time-series design can be frequently modeled using a four-parameter design matrix, however, there are differences across writers in the details of the recommended design matrices to be used in the estimation of the four parameters of the model.
Abstract: It has been recognized that the two-phase version of the interrupted time-series design can be frequently modeled using a four-parameter design matrix. There are differences across writers, however, in the details of the recommended design matrices to be used in the estimation of the four parameters of the model. Various writers imply that different methods of specifying the four-parameter design matrix all lead to the same conclusions; they do not. The tests and estimates for level change are dramatically different under the various seemingly equivalent design specifications. Examples of egregious errors of interpretation are presented and recommendations regarding the correct specification of the design matrix are made. The recommendations hold whether the model is estimated using ordinary least squares (for the case of approximately independent errors) or some more complex time-series approach (for the case of autocorrelated errors).
TL;DR: The authors describe the MIT microelectromechanical computer-aided design system (MEMCAD), in which selected commercial software packages are linked with specialized database and numerical programs to allow designers to quickly perform both mechanical and electrical analyses of structures.
Abstract: The authors describe the MIT microelectromechanical computer-aided design system (MEMCAD), in which selected commercial software packages are linked with specialized database and numerical programs to allow designers to quickly perform both mechanical and electrical analyses of structures either described directly, or derived from the design specification (mask data plus process flow). The system architecture, the various modules, and their present status are described, and present system performance is demonstrated with several examples. >
TL;DR: This chapter gives both an overview of the key concepts found in a range existing languages and tools and a specific proposal for modeling the abstract behavior of a design.
Abstract: This chapter describes high-level design techniques for developing hardware or software and combinations of the two. The chapter gives both an overview of the key concepts found in a range existing languages and tools and a specific proposal for modeling the abstract behavior of a design. The aim of such high-level design techniques is to reduce the design time or effort by shifting as many decisions and analysises as possible from low-level to high-level models.
TL;DR: In this paper, the authors describe a way of thinking about engineering design in the context of a project and a project context, and present a set of guidelines for embedding design.
Abstract: 0.- 0.1 Terminology.- 0.2 Examples.- 1 The Context.- 1 Ways of Thinking about Engineering Design.- 1.1 Disasters and Failures.- 1.2 Engineering Excellence.- 1.3 New Innovations.- 1.4 Improving Engineering Design.- 1.5 Systematic Approaches to Engineering Design.- 1.6 Systematic Design in Practice.- 1.7 Tips for Management.- 2 The Project Context.- 2.1 Engineering Projects.- 2.2 Engineering Design in the Project Context.- 2.3 The Effect of Influences.- 2.4 Influences at the Macroeconomic Level.- 2.5 Influences at the Microeconomic Level.- 2.6 Influences at the Corporate Level.- 2.7 Design Context Checklist and Work Sheet.- 2.8 Tips for Management.- 2 Task,Team and Tools.- 3 Profiling the Project.- 3.1 Influences at the Project Level.- 3.2 Engineering Design in the Project Context.- 3.3 Design Task.- 3.4 Design Team.- 3.5 Design Tools and Techniques.- 3.6 Design Team Output.- 3.7 Project Profile Checklist and Work Sheet.- 3.8 Tips for Management.- 4 Managing the Design Team.- 4.1 Influences at the Personal Level.- 4.2 Knowledge, Skills, and Attitude.- 4.3 Motivation.- 4.4 Relationships.- 4.5 Personal Output.- 4.6 Personnel Profile Checklist and Work Sheet.- 4.7 Tips for Management.- 3 The Project.- 5 Project Proposal: Getting the Job.- 5.1 Proposals and Briefs.- 5.2 Preparing a Proposal.- 5.3 Negotiations.- 5.4 Debriefing.- 5.5 Project Proposal Checklist and Work Sheet.- 5.6 Tips for Management.- 6 Design Specification: Clarification of the Task.- 6.1 Problem Statement and Design Specification.- 6.2 Defining the Problem.- 6.3 Project Planning.- 6.4 Demands and Wishes.- 6.5 Design Specification.- 6.6 Design Specification Checklist and Work Sheet.- 6.7 Tips for Management.- 7 Feasible Concept: Conceptual Design.- 7.1 Divergent and Convergent Thinking.- 7.2 Generating Ideas.- 7.3 Selecting and Evaluating Concepts.- 7.4 Estimating Costs.- 7.5 Presenting the Final Concept.- 7.6 Conceptual Design Checklist and Work Sheet.- 7.7 Tips for Management.- 8 Developed Concept: Embodiment Design.- 8.1 Abstract Concept to Developed Design.- 8.2 Overall Guidelines for Embodiment Design.- 8.3 Specific Guidelines for Embodiment Design.- 8.4 General Guidelines for Embodiment Design.- 8.5 Embodiment Design Checklist and Work Sheet.- 8.6 Tips for Management.- 9 Final Design: Detail Design for Manufacture.- 9.1 The Importance of Detail Design.- 9.2 The Design Manager and Detail Design.- 9.3 Quality Assurance.- 9.4 Interaction of Shape, Materials, and Manufacture.- 9.5 Manufacturing Drawings and Information.- 9.6 Standard Components.- 9.7 Assembly.- 9.8 Testing and Commissioning.- 9.9 Detail Design Checklist and Work Sheet.- 9.10 Tips for Management.- 10 Users and Customers: Design Feedback.- 10.1 Expectations.- 10.2 Use and Abuse.- 10.3 Maintenance.- 10.4 Litigation.- 10.5 Design Quality Assessment Work Sheet.- 10.6 Tips for Management.- 11 Standards and Codes.- 11.1 General Issues.- 11.2 Basic Definitions.- 11.3 Safety Standards.- 11.4 Some Reference Articles on Safety Standards.- 11.5 Some Reference Articles on International Standards.- 11.6 ISO0 International Standards for Quality Management.- 11.7 National Standards for Engineering Design Management.- 11.8 Tips for Management.- 11.9 Contact Information and URLs for Standards and Codes.- 12 Engineering Design Process: Review and Analysis.- 12.1 Summary.- 12.2 Forensic Analysis of Engineering Design Issues.- 12.3 Analysis of the Engineering Design Process.- 241.- 243.- 247.