|
Common Component Architecture
The Common Component Architecture (CCA) was a standard for Component-based software engineering used in high-performance scientific computing. Features of the Common Component Architecture that distinguish it from commercial component standards Component Object Model, CORBA, Enterprise JavaBeans include support for Fortran programmers, multi-dimensional data arrays, exotic hardware and operating systems, and a variety of network data transports not typically suited for wide area networks. The Common Component Architecture Forum Established in 1997, the Common Component Architecture Forum is a group of researchers defining the interface standards of CCA, as well as ensuring a smooth adoption of CCA tools and technologies. Adoption of CCA appears to have been ceased, with Component Based Architecture, CBA more widely used. The latest forum news released in November 2006. External links The Common Component Architecture Forum References Software architecture Component-based s ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Component-based Software Engineering
Component-based software engineering (CBSE), also called component-based development (CBD), is a style of software engineering that aims to construct a software system from software component, components that are loosely-Coupling (computer programming), coupled and Reusability, reusable. This emphasizes the separation of concerns among components. To find the right level of component granularity, software architects have to continuously iterate their component designs with developers. Architects need to take into account user requirements, responsibilities and architectural characteristics. Considerations For large-scale systems developed by large teams, a disciplined culture and process is required to achieve the benefits of CBSE. Third-party software component, Third-party components are often utilized in large systems. The system can be designed visually with the Unified Modeling Language (UML). Each software component, component is shown as a rectangle, and an interface is ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Component Object Model
Component Object Model (COM) is a binary-interface technology for software components from Microsoft that enables using objects in a language-neutral way between different programming languages, programming contexts, processes and machines. COM is the basis for other Microsoft domain-specific component technologies including OLE, OLE Automation, ActiveX, COM+, and DCOM as well as implementations such as DirectX, Windows shell, UMDF, Windows Runtime, and Browser Helper Object. COM enables object use with only knowing its interface; not its internal implementation. The component implementer defines interfaces that are separate from the implementation. Support for multiple programming contexts is handled by relying on the object for aspects that would be challenging to implement as a facility. Supporting multiple uses of an object is handled by requiring each object to destroy itself via reference-counting. Access to an object's interfaces (similar to Type conver ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
CORBA
The Common Object Request Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) designed to facilitate the communication of systems that are deployed on diverse platforms. CORBA enables collaboration between systems on different operating systems, programming languages, and computing hardware. CORBA uses an object-oriented model although the systems that use the CORBA do not have to be object-oriented. CORBA is an example of the distributed object paradigm. While briefly popular in the mid to late 1990s, CORBA's complexity, inconsistency, and high licensing costs have relegated it to being a niche technology. Overview CORBA enables communication between software written in different languages and running on different computers. Implementation details from specific operating systems, programming languages, and hardware platforms are all removed from the responsibility of developers who use CORBA. CORBA normalizes the method-call semantics betwee ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Enterprise JavaBeans
Jakarta Enterprise Beans (EJB; formerly Enterprise JavaBeans) is one of several Java APIs for modular construction of enterprise software. EJB is a server-side software component that encapsulates business logic of an application. An EJB web container provides a runtime environment for web related software components, including computer security, Java servlet lifecycle management, transaction processing, and other web services. The EJB specification is a subset of the Jakarta EE specification. Specification The EJB specification was originally developed in 1997 by IBM and later adopted by Sun Microsystems (EJB 1.0 and 1.1) in 1999 and enhanced under the Java Community Process aJSR 19(EJB 2.0)JSR 153(EJB 2.1)JSR 220(EJB 3.0)JSR 318(EJB 3.1) anJSR 345(EJB 3.2). The EJB specification provides a standard way to implement the server-side (also called " back-end") 'business' software typically found in enterprise applications (as opposed to 'front-end' user interface software ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Component Based Architecture
Component may refer to: In engineering, science, and technology Generic systems *System components, an entity with discrete structure, such as an assembly or software module, within a system considered at a particular level of analysis * Lumped element model, a model of spatially distributed systems Electrical *Component video, a type of analog video information that is transmitted or stored as two or more separate signals *Electronic component, a constituent of an electronic circuit *Symmetrical components, in electrical engineering, analysis of unbalanced three-phase power systems Mathematics *Color model, a way of describing how colors can be represented, typically as multiple values or color components * Component (group theory), a quasi-simple subnormal sub-group *Connected component (graph theory), a maximal connected subgraph *Connected component (topology), a maximal connected subspace of a topological space *Vector component, result of the decomposition of a vector into ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Architecture
Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations. The ''architecture'' of a software system is a metaphor, analogous to the architecture of a building. It functions as the blueprints for the system and the development project, which project management can later use to extrapolate the tasks necessary to be executed by the teams and people involved. Software architecture is about making fundamental structural choices that are costly to change once implemented. Software architecture choices include specific structural options from possibilities in Software design, the design of the software. There are two fundamental laws in software architecture: # Everything is a trade-off # "Why is more important than how" "Architectural Kata" is a teamwork which can be used to produce an ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
