Enterprise Architect is a CASE software (Computer Aided Software Engineering) that has excellent support for software system development. EA is different from ordinary UML drawing tools (such as VISIO), it will support the whole process of system development. In the requirements analysis phase, system analysis and design phase, system development and deployment, there is strong support, plus forward and reverse engineering of 10 programming languages, project management, document generation, data modeling, etc. Allows each role in system development to obtain the best development efficiency.
The component model describes the software components that will be used to build the system. These can be built from the class model and written for the new system from scratch, or they can be introduced from other projects and third-party vendors. Components are high-level collections of smaller pieces of software and provide a "black box" building block method for software construction.
Component symbol
The components may be similar to ActiveX controls-user interface controls or business rules servers. The components are drawn as shown in the figure below:
Component diagram
The component diagram shows the relationship between software components, their dependencies, communication, location and other conditions.
interface
Components may also expose interfaces. These are visible entry points or services that the component is advertising and can be used by other software components and classes. Generally, components are composed of many internal classes and class packages. It can even be assembled from a set of smaller components.
Components and nodes
The deployment diagram illustrates the physical deployment of the system in a production (or test) environment. It shows where the component will be located, on what server, machine or hardware. It may indicate network links, LAN bandwidth, etc.
Claim
Components may come with requirements to indicate their contractual obligations-that is, what services they will provide in the model. Need help document the functional behavior of software elements.
Restrictions
Components may come with constraints that dictate the environment in which the component operates. Preconditions specify conditions that must be met before the component can perform certain functions. Post-conditions indicate what will be after the component completes some work, and invariants specify the conditions that must remain true for the life of the component.
Situation
A scene is a text/process description of the operation of an object over time, describing how the component works. Multiple scenarios may be created to describe the basic path (perfect operation) as well as exceptions, errors, and other situations.
Traceability
You can indicate traceability by implementing links. A component can implement another model element (for example, a use case), or a component can be implemented by another element (for example, a package of classes). By providing implementation links with components, you can map the dependencies between model elements and the traceability from initial requirements to final implementation. one example
The following example shows how to link components to provide a conceptual/logical view of system construction. This example is related to the server and security elements of an online bookstore. It includes elements such as Web server, firewall, ASP page and so on.
Server component
This figure illustrates the layout of the main server-side components that need to be built for an online bookstore. These components are a mix of custom items and purchased items and will be assembled to provide the required functionality.
Security component
The security component diagram shows how security software such as certificate authorities, browsers, web servers, and other model elements work together to ensure the security regulations in the proposed system.
