🌁Software Engineering: Component (Definitions)

"An application-level software unit supported by a container. Components are configurable at deployment time. The J2EE platform defines four types of components: enterprise beans, Web components, applets, and application clients." (Kim Haase et al, "The J2EE™ Tutorial", 2002)

"A single part in a subassembly, subsystem, or system. An example is a stamped metal part before it has anything assembled to it." (Clyde M Creveling, "Six Sigma for Technical Processes: An Overview for R Executives, Technical Leaders, and Engineering Managers", 2006)

"A software architecture developed by Microsoft to build component-based applications. COM is used to communicate between components on the same computer. It’s part of a strategic building-block approach for developing application programs." (Evan Levy & Jill Dyché, "Customer Data Integration", 2006)

"A single part in a subassembly, subsystem or system. An example would be a stamped metal part prior to having anything assembled to it." (Lynne Hambleton, "Treasure Chest of Six Sigma Growth Methods, Tools, and Best Practices", 2007)

"A subassembly or piece/part used in a product that allows a product to achieve the desired level of functionality. A fuel injector is a component used in an automobile engine." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"A metasubtype of class; a large-scale class that contains internal parts and provides services via a well-defined interface." (Bruce P Douglass, "Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development", 2009)

"A piece of computer software that can be used as a building block in larger systems. Components can be parts of business applications that have been made accessible through Web Service related standards and technologies, such as WSDL, SOAP, and XML. See WSDL, SOAP, and XML." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies 2nd Ed.", 2009)

"For our purposes, an aggregation of cohesive types that expose services through well-defined abstractions, while encapsulating implementation details and minimizing coupling to other components. (There is a wide-range of definitions for component in computer science and industry.)" (Dean Wampler & Alex Payne, "Programming Scala", 2009)

"(1) A minimal software item that e.g. can be tested in isolation. (2) A component is a potential, or actual, part of some larger system, or specification [TGilb]." (International Qualifications Board for Business Analysis, "Standard glossary of terms used in Software Engineering", 2011)

"1.A discrete object or entity that is a part of a larger system." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A program object similar to a control, but without a visible presence on the form at run time." (Rod Stephens, "Start Here! Fundamentals of Microsoft® .NET Programming", 2011)

"A programming entity similar to a control except it has only code and doesn't have a visible appearance on the screen. You still place it on a form at design time, however, and the program's code can interact with it." (Rod Stephens, "Stephens' Visual Basic® Programming 24-Hour Trainer", 2011)

"A discrete piece of content that is about a specific subject, has an identifiable purpose, and can stand alone. Components can be reused multiple times in multiple information products." (Charles Cooper & Ann Rockley, "Managing Enterprise Content: A Unified Content Strategy, 2nd Ed.", 2012)

"A piece of computer software that can be used as a building block in larger systems. Components can be parts of business applications that have been made accessible through web service–related standards and technologies, such as WSDL, SOAP, and XML." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"1. A minimal software item that has its own specification or that can be tested in isolation.  2. A software unit that fulfills the implementation standards of a component model (EJB, CORBA, .NET)." (Tilo Linz et al, "Software Testing Foundations, 4th Ed", 2014)

"An identifiable element within the program or project that provides a particular function or group of related functions." (Project Management Institute, "Navigating Complexity: A Practice Guide", 2014)

"A constituent part, element, or piece of a complex whole." (Project Management Institute, "Practice Standard for Scheduling" 3rd Ed., 2019)

"A minimal software item that can be tested in isolation." (SQA)

"General term referring to one part of something more complex" (ITIL)