The National Academies Press

Currently Skimming:

Pages 47-63

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 47... ... 47 Design and Implementation for Sustainable DOT EIPs This section highlights how DOT EIP services could be decomposed and implemented following the principles of microservices architecture. This section does so by providing the reader with a list of requirements for sustainable DOT EIPs; technology recommendations for building, hosting, and managing microservices; examples of microservices implementations depicted as a series of system engineering diagrams for each of the DOT EIP services described in Table 2-1; and recommendations for migrating services from a monolithic EIP system to a microservices architecture. Read the entire page →
From page 48... ... 48 Guidance for Development and Management of Sustainable Enterprise Information Portals Functional Requirements F1. The DOT EIP shall contain a service discovery and registrar service F2. Read the entire page →
From page 49... ... Design and Implementation for Sustainable DOT EIPs 49 Table 5-1. (Continued) Read the entire page →
From page 50... ... 50 Guidance for Development and Management of Sustainable Enterprise Information Portals 5.3 Technology Recommendations for Sustainable DOT EIPs Table 5-2 shows a list of recommended technologies for developing sustainable DOT EIPs following a microservices architecture approach. These technologies were selected based on a survey of industry practitioners and a scoring and ranking of each of the suggested technologies based on its reliability, security, interoperability, usability, scalability, modifiability, reusability, integrability, affordability, and appropriateness for DOT organizations. Read the entire page →
From page 51... ... Design and Implementation for Sustainable DOT EIPs 51 EIP Component Recommended Approach Se rv ic e API Gateway Adopt a cloud API framework. Searching Adopt a cloud enterprise search service. Read the entire page →
From page 52... ... 52 Guidance for Development and Management of Sustainable Enterprise Information Portals Se cu ri ty a nd Id en ti ty Identity and Access Management The recommended approach for providing identity and access management service capabilities in a sustainable DOT EIP API is the adoption of a cloud access and identity management solution. Security Audit There is no single approach to providing a security audit to a sustainable DOT EIP. Read the entire page →
From page 53... ... Design and Implementation for Sustainable DOT EIPs 53 Table 5-5 presents the set of interfaces while Table 5-6 and Table 5-7 present business and data services, respectively. 5.4.2.1 Block Definition Diagrams Block definition diagrams are created to communicate structural information about a system. Read the entire page →
From page 54... ... 54 Guidance for Development and Management of Sustainable Enterprise Information Portals User Actions Action Descriptions illustrated in the Use Case Diagram Set up alert Alerts are set up either by DOT operations or maintenance users to be sent when there is important or relevant information of which other users should be made aware. Receive alert Alerts containing new important or particularly relevant DOT system information are received by DOT operations or maintenance users. Read the entire page →
From page 55... ... Design and Implementation for Sustainable DOT EIPs 55 interact with the DOT EIP. Public web user interfaces Deﬁnes the web interfaces that will be used by the public to interact with the DOT EIP. Read the entire page →
From page 56... ... 56 Guidance for Development and Management of Sustainable Enterprise Information Portals Internal DOT EIP Business Services Descriptions Access management Provide secure access to all the other DOT EIP components and manage users' privileges. Analysis management Provide advanced analysis of DOT data such as traﬀic sensor data or driver's behavior data to all the other DOT EIP components. Read the entire page →
From page 57... ... Design and Implementation for Sustainable DOT EIPs 57 Data Services Descriptions Analytical database services Internal DOT EIP services that will be used to provide advanced data analysis capabilities to other DOT EIP components. An example could be a set of services performing text analysis on DOT documents or training prediction models using historical data. Read the entire page →
From page 58... ... 58 Guidance for Development and Management of Sustainable Enterprise Information Portals showing the main data exchanges between the service components involved in the high-level use cases and omitted some of the components that were less relevant to the use cases, such as logging and service discovery. The components that were not included in the data flow but are still involved in the process are represented at the top of the diagrams as unconnected hexagons. Read the entire page →
From page 59... ... Figure 5-3. Asset management and engineering services component and data flow diagram. Read the entire page →
From page 60... ... 60 Guidance for Development and Management of Sustainable Enterprise Information Portals Figure 5-4 shows an activity diagram representing the possible flow of actions that could be taken during the asset management and engineering services scenario. In creating the activity diagram, the team focused on representing the high-level workflow that would need to be followed to perform the tasks occurring during each of the implementation examples. Read the entire page →
From page 61... ... Design and Implementation for Sustainable DOT EIPs 61 diagrams to the single scenario of "DOT maintenance employee archives older asset data" for illustration. Other use case scenarios for asset management and engineering services would require their respective sequence diagram. Read the entire page →
From page 62... ... 62 Guidance for Development and Management of Sustainable Enterprise Information Portals to as the "Big Bang" rewrite. It is often the only option when migrating an application to another monolithic platform; it can be extremely risky, and it will likely lead to failures that will postpone the modernization plan. Read the entire page →
From page 63... ... Design and Implementation for Sustainable DOT EIPs 63 In Figure 5-6, Module Z is the candidate module to extract. Its components are used by Module X, and Module Z uses Module Y Read the entire page →

From page 47...

... 47 Design and Implementation for Sustainable DOT EIPs This section highlights how DOT EIP services could be decomposed and implemented following the principles of microservices architecture. This section does so by providing the reader with a list of requirements for sustainable DOT EIPs; technology recommendations for building, hosting, and managing microservices; examples of microservices implementations depicted as a series of system engineering diagrams for each of the DOT EIP services described in Table 2-1; and recommendations for migrating services from a monolithic EIP system to a microservices architecture.