Technology & Engineering

Component Selection

Component selection is the process of choosing the right parts to build a system or device. It involves considering factors such as performance, cost, availability, and compatibility with other components. Proper component selection is crucial for ensuring the functionality and reliability of the final product.

Written by Perlego with AI-assistance

5 Key excerpts on "Component Selection"

  • Book cover image for: Software Engineering
    eBook - PDF

    Software Engineering

    Principles and Practice

    • Hans van Vliet(Author)
    • 2014(Publication Date)
    • Wiley
      (Publisher)
    The component technology determines, for example, possible component interactions, certain solutions built into the technology (such as transactions or security mechanisms), and assumptions of system resources (such as scheduling policies). For this reason, it is most likely that a component model and a component technology that implements that model must be chosen at design time. For a component to be reusable, it must be designed in a more general way than a component tailored for a unique situation. Components intended to be reused require adaptability. This increases the size and complexity of the components. At the same time, they must be concrete and simple enough to serve particular requirements in an efficient way. This requires more design and development effort. Developing a reusable component may require three to four times more resources than developing a component which serves a specific purpose (Mili et al., 2002). Implementation. Implementation of components is, to a large extent, determined by the component technology selected. The component technology provides support in programming languages and automation of component compositions. It may include many services and provide many solutions that are important for the application domain. Good examples of such support are transactions management, database management, security, and interoperability support for distributed systems provided by component technologies such as .NET, J2EE, or COM+. Integration. Components are built to be easily integrated into systems. For this reason, integration considerations must be continuously in focus. Usually, component technology provides good support for components integration and integration is being performed on a daily basis. Test. Test activities are of particular importance for two reasons. First, the component should be very carefully tested since its usage and environment context is not obvious.
  • Book cover image for: Systems Engineering
    eBook - PDF

    Systems Engineering

    Analysis, Modeling and Simulation of Systems

    • Emmanuel Hygounenc(Author)
    • 2024(Publication Date)
    • Wiley-ISTE
      (Publisher)
    192 Systems Engineering possibilities or the state of the art in the field (available solutions, existing technologies), the market solutions, as well as the company’s innovation strategy. Figure 10.1. Three crossed visions of the physical architecture Figure 10.2. Physical design, a synthesis process Physical Design 193 10.2. Identification of physical components As input to this activity, we have the leaf sub-functions of functional design, the system missions of operational analysis and non-functional requirements such as design requirements. Figure 10.3. Identifying the system components We also have as input the company’s know-how with the available technologies, the state of the art as well as the innovation strategy (see Figure 10.3). At the end of this activity, we will have a list of components with possible choices to arbitrate and prioritize. A component of a system is a concrete element of this system which can be: – material, such as a physical component; – computer science, such as software or its “hardware”; – human, such as an operator or an organization. A component can be elementary or the result of the integration of other components. The identification of the system components is based on: – the sub-functions to be allocated from the functional architecture; – the missions of the system; – non-functional system requirements that influence the choice of components. 194 Systems Engineering On the other hand, the identification of components is also based on: – the company’s know-how and market solutions; – risk-taking in business innovation. These last two points have an influence on decision-making regarding the choice of constituents. Indeed, the first one calls for the project’s arbitration between “Make” or “Buy”. The second depends on the technical and competitive context of the company. Indeed, depending on its policy, the company will have to choose between disruptive innovation and incremental innovation.
  • Book cover image for: Practical Reliability Of Electronic Equipment And Products
    • Eugene R. Hnatek(Author)
    • 2002(Publication Date)
    • CRC Press
      (Publisher)
    2. System Engineering evaluates and ensures that the part works in the product as intended. 3. Manufacturing Engineering ensures that the parts can be reliably and repeatedly attached to the PCB and conducts appropriate evaluation tests of new PCB materials and manufacturing techniques, packaging technology (BGA, CSP, etc.), and attachment methods (flip chip, lead free solder, etc.). 4. Component Engineering guides Develop Engineering in the selection and use of technologies, specific IC functions, and suppliers beginning at the conceptual design phase and continuing through to a fixed de-sign; evaluates supplier-provided test data: conducts specific analyses of critical components; generates functional technology road maps; and conducts technology audits as required. 5. Reliability Engineering ensures that the product long-term reliability goals, in accordance with customer requirements, are established; that the supplier uses the proper design and derating guidelines; and that the design models are accurate and in place. Each commodity team representative is responsible for building relationships with her/his counterparts at the selected component suppliers. 4.4 THE ROLE OF THE COMPONENT ENGINEER The component engineer (CE) (see also Chapter 3) is a resource for product development and strategic planning. The focus of the CE is on matching the company's product direction with the direction of the supplier base. The most effective development support that can be provided by the CE is to implement fast and effective means of evaluating new products and technologies before they are needed, provide product road maps, participate in design reviews, and provide component application assistance. The CE has traditionally been a trailer in the product development cycle by qualifying components that are already designed into new products.
  • Book cover image for: Informatics for Materials Science and Engineering
    eBook - ePub

    Informatics for Materials Science and Engineering

    Data-driven Discovery for Accelerated Experimentation and Application

    Chapter 10

    Materials Selection for Engineering Design

    Michael Ashby* , Elizabeth Cope and David Cebon,    
    * Emeritus Professor, Cambridge University Engineering Department, Cambridge, UK
    ,
    Granta Design Limited, Cambridge, UK
    ,
    Cambridge University Engineering Department, Cambridge, UK

    1 Introduction

    Material properties limit product performance. For optimized, innovative engineering design, we need systematic procedures and informatics to select them. This is about more than just ranking materials according to a particular material property, but about assessing the entire profile of properties that will maximize performance – performance, here, meaning technical excellence at acceptable cost and minimum environmental intrusion.
    Figure 10.1 A systematic material selection strategy.

    2 Systematic Selection

    2.1 Translation

    Any engineering component has one or more functions : To support a load, to contain a pressure, to transmit heat, and so forth. This must be achieved subject to constraints : That certain dimensions are fixed; that the component must carry the design loads without failure or excessive deflection; the need to insulate against or to conduct heat or electricity; to function in a certain range of temperature or in a given environment; and many more.
    In designing the component, the designer has one or more objectives : To make it as cheap as possible, perhaps, or as light, or as environmentally benign, or some combination of these. Certain parameters can be adjusted in order to optimize the objective – the designer is free to vary dimensions that are not constrained by design requirements and, most importantly, free to choose the material for the component and the process to shape it. We refer to these as free variables
  • Book cover image for: e-Business
    eBook - PDF

    e-Business

    Organizational and Technical Foundations

    • Michael P. Papazoglou, Pieter Ribbers(Authors)
    • 2014(Publication Date)
    • Wiley
      (Publisher)
    Component technology is an evolution of object-oriented technology that can serve to integrate business functions on the basis of a homogeneous software infrastructure. Rather than creating or buying monolithic in-house end-to-end solutions, components are assembled from smaller modules built either in-house or purchased by a third party. Knitting those pieces together within the confines of a common architecture allows business systems to interoperate while isolating each piece from implementation changes in other pieces. A component is an independent, encapsulated part of a system. Each component is simple enough to be designed well, and built to implement a well-defined set of responsibilities as regards its clients but, just as importantly, has well-defined limits to its functionality. Components are autonomous units of software that may provide a useful service or a set of services to a client, and have meaning in isolation to other components with which they interoperate. Because components are autonomous units of functionality, they provide natural demarcation of development work. A component developer is responsible for making sure that the component fulfills its contract with client programs. Universal interfaces on components mean they can be ‘plugged’ into other components, development and test tools effortlessly. This removes several issues of other types of software development, e.g. structured or object oriented. To summarize the above discussion, a component can be defined as a coherent package of software implementation that exhibits the following characteristics: • It is an encapsulation of business logic (or technical functionality) that performs a set of related functions and that presents a well-defined published interface for the functions (or services) it provides and expects from others.
Index pages curate the most relevant extracts from our library of academic textbooks. They’ve been created using an in-house natural language model (NLM), each adding context and meaning to key research topics.