系统架构师英文题目

建议用谷歌翻译多听几遍

(一)

Software architecture reconstruction is an interpretive, interactive, and iterative process including many activities. ( Information extraction ) involves analyzing a system’s existing design and implementation artifacts to construct a model of it. The result is used in the following activities to construct a view of the system. The database construction activity converts the ( elements and relations ) contained in the view into a standard format for storage in a database. The ( view fusion ) activity involves defining and manipulating the information stored in database to reconcile, augment, and establish connections between the elements. Reconstruction consists of two primary activities: ( visualization and interaction )and ( pattern definition and recognition ). The former provides a mechanism for the user to manipulate architectural elements, and the latter provides facilities for architecture reconstruction.

软件架构重建是一个解释性的、交互式的、迭代的过程,包括许多活动。 (信息提取)涉及分析系统的现有设计和实现工件以构建其模型。结果用于以下活动以构建系统视图。数据库构建活动将视图中包含的(元素和关系)转换为标准格式以存储在数据库中。 (视图融合)活动涉及定义和操作数据库中存储的信息,以协调、扩充和建立元素之间的连接。重构包括两个主要活动:(可视化和交互)和(模式定义和识别)。前者为用户提供了操纵架构元素的机制,后者为架构重建提供了便利。

(二)

An application architecture specifies the technologies to be used to implement one or more information systems. It serves as an outline for detailed design, construction, and implementation. Given the models and details, include ( logical DFDs and ERD ), we can distribute data and processes to create a general design of application architecture. The design will normally be constrained by architecture standards, project objectives, and ( the feasibility of techniques used ). The first physical DFD to be drawn is the ( network architecture DFD ). The next step is to distribute data stores to different processors. Data( partitioning and replication )are two types of distributed data which most RDBMSs support. There are many distribution options used in data distribution. In the case of ( storing specific tables on different servers ), we should record each table as a data store on the physical DFD and connect each to the appropriate server.

应用程序体系结构指定用于实现一个或多个信息系统的技术。它作为详细设计、构建和实施的大纲。给定模型和细节,包括(逻辑DFD和ERD),我们可以分发数据和流程来创建应用程序架构的总体设计。设计通常会受到架构标准、项目目标和(所用技术的可行性)的约束。第一个要画的物理DFD是(网络架构DFD)。下一步是将数据存储分配给不同的处理器。数据(分区和复制)是大多数 RDBMS 支持的两种分布式数据。数据分发中使用了许多分发选项。对于(将特定表存储在不同服务器上)的情况,我们应该将每个表记录为物理 DFD 上的数据存储,并将每个表连接到适当的服务器。

(三)

A system’s architecture is a representation of a system in which there is a mapping of ( functionality ) onto hardware and software components, a mapping of the ( software architecture ) onto the hardware architecture, and a concern for the human interaction with these components. That is, system architecture is concerned with a total system, including hardware, software, and humans. Software architectural structures can be divided into three major categories, depending on the broad nature of the elements they show. 1)( Module structures ) embody decisions as a set of code or data units that have to be constructed or procured. 2)( Component-and-connector structures ) embody decisions as to how the system is to be structured as set of elements that have runtime behavior and interactions. 3)( Allocation structures )embody decisions as to how the system will relate to nonsoflware structures in its environment (such as CPUs, file systems, networks, development teams, etc.).

系统架构是系统的表示,其中存在(功能)到硬件和软件组件的映射、(软件架构)到硬件架构的映射,以及对人类与这些组件的交互的关注。也就是说,系统架构涉及整个系统,包括硬件、软件和人。软件架构结构可以分为三大类,具体取决于它们所显示元素的广泛性质。 1)(模块结构)将决策体现为一组必须构建或获取的代码或数据单元。 2)(组件和连接器结构)体现了如何将系统构建为具有运行时行为和交互的元素集的决策。 3)(分配结构)体现了系统如何与其环境中的非软件结构(例如CPU、文件系统、网络、开发团队等)相关的决策。

(四)

Many of the activities performed during the preliminary investigation are still being conducted in ( analysis phase), but in much greater depth than before. During this phase, the analyst must become fully aware of the ( root problem) and must develop enough knowledge about the (business environment ) and the existing systems to enable an effective solution to be proposed and implemented. Besides the ( logical models) for process and data of current system, the deliverable from this phase also includes the ( formal requirements definition) for the proposed system.

初步调查期间进行的许多活动仍在(分析阶段)进行,但比以前深入得多。在此阶段,分析师必须充分意识到(根本问题),并且必须对(业务环境)和现有系统有足够的了解,以便能够提出和实施有效的解决方案。除了当前系统的流程和数据的(逻辑模型)之外,此阶段的可交付成果还包括拟议系统的(正式需求定义)。

(五)

During the systems analysis phase, you must decide how data will be organized, stored, and managed. A (data structure) is a framework for organizing, storing, and managing data. Each file or table contains data about people, places, things, or events. One of the potential problems existing in a file processing environment is (data redundancy) , which means that data common to two or more information systems is stored in several places. In a DBMS, the linked tables form a unified data structure that greatly improves data quality and access. A(n) (entity-relationship diagram) is a model that shows the logical relationships and interaction among system entities. It provides an overall view of the system and a blueprint for creating the physical data structures. (Normalization) is the process of creating table designs by assigning specific fields or attributes to each table in the database. A table design specifies the fields and identifies the primary key in a particular table or file. The three normal forms constitute a progression in which (third normal form) represents the best design. Most business-related databases must be designed in that form.

在系统分析阶段,您必须决定如何组织、存储和管理数据。 A(数据结构)是组织、存储和管理数据的框架。每个文件或表都包含有关人物、地点、事物或事件的数据。文件处理环境中存在的潜在问题之一是(数据冗余),这意味着两个或多个信息系统共有的数据存储在多个地方。在 DBMS 中,链接表形成统一的数据结构,极大地提高了数据质量和访问。 A(n)(实体关系图)是展示系统实体之间逻辑关系和交互的模型。它提供了系统的总体视图和创建物理数据结构的蓝图。 (规范化)是通过为数据库中的每个表分配特定字段或属性来创建表设计的过程。表设计指定特定表或文件中的字段并标识主键。三种范式构成一个级数,其中(第三范式)代表最佳设计。大多数与业务相关的数据库必须以这种形式设计。

(六)

Complex software systems are typically composed of subsystems and/or (modules), some of which may themselves be complete software systems. These components must seamlessly integrate into the larger system. Architectural design addresses this challenge by determining what the components are and how they integrate and communicate with each other. The following are some considerations (factors) that influence system architecture decisions: performance, availability, security, and (maintainablity). These requirements typically do not synchronize with each other, so (trade-offs) will be necessary. Two issues of paramount importance in architectural design are resource sharing and system control. There are four approaches to resource sharing: the Repository Model, the Client-Server Model, the Abstract Machine Model, and the (Component Model); and two approaches that you should be familiar with - (centeralized control) and event-based control

复杂的软件系统通常由子系统和/或(模块)组成,其中一些本身可能是完整的软件系统。这些组件必须无缝集成到更大的系统中。架构设计通过确定组件是什么以及它们如何相互集成和通信来解决这一挑战。以下是影响系统架构决策的一些考虑因素(因素):性能、可用​​性、安全性和(可维护性)。这些要求通常不会相互同步,因此(权衡)是必要的。架构设计中最重要的两个问题是资源共享和系统控制。资源共享有四种方法:存储库模型、客户端-服务器模型、抽象机模型和(组件模型);以及您应该熟悉的两种方法 - (集中控制)和基于事件的控制

(七)

System analysis is traditionally done top-down using structured analysis based on( functional decomposition). Object-oriented analysis focuses on creation of models. The three types of theanalysis model are( class model,interaction model and state model). There are two substages of object-oriented analysis.( Domain analysis )focuses on real-world things whose semantics the application captures. The object constructedin the requirement analysis shows the( static structure)of the real-world system and organizes it intoworkable pieces.( Application analysis)addresses the computer aspects of the application that are visible tousers. The objects are those which can be expected to vary from time to time quite rapidly.

系统分析传统上是使用基于(功能分解)的结构化分析自顶向下完成的。面向对象的分析侧重于模型的创建。分析模型的三种类型是(类模型、交互模型和状态模型)。面向对象分析有两个子阶段。(领域分析)专注于应用程序捕获其语义的现实世界事物。需求分析中构造的对象显示了现实世界系统的(静态结构)并将其组织成可工作的部分。(应用程序分析)解决了用户可见的应用程序的计算机方面。这些对象是那些预计会不时快速变化的对象。

(八)

The prevailing distributed computing model of the current era is called client/server computing. A (Client/Server system) is a solution in which the presentation,presentation logic,application logic,data manipulation and data layers are distributed between client PCs and one or more servers. A (Thin client) is a personal computer that does not have to be very powerful in terms of processor speed and memory because it only presents the interface to the user. A (Fat client) is a personal computer,notebook computer,or workstation that is typically more powerful in terms of processor speed,memory,and storage capacity. A (Database serverer) hosts one or more shared database but also executes all database commands and services for information systems. A (n)(Web server) hosts Internet or intranet Web sites,it communicates with clients by returning to them documents and data.

当前时代流行的分布式计算模型称为客户端/服务器计算。 A(客户端/服务器系统)是一种将表示、表示逻辑、应用逻辑、数据操作和数据层分布在客户端PC和一台或多台服务器之间的解决方案。 A(瘦客户端)是一台个人计算机,在处理器速度和内存方面不必非常强大,因为它只向用户呈现界面。 A(胖客户端)是个人计算机、笔记本电脑或工作站,通常在处理器速度、内存和存储容量方面更强大。数据库服务器(Database serverer)托管一个或多个共享数据库,但也执行信息系统的所有数据库命令和服务。 (n)(Web 服务器)托管 Internet 或 Intranet 网站,它通过向客户端返回文档和数据来与客户端进行通信。

(九)

The objective of ( architecture design ) is to determine what parts of the application software will be assigned to what hardware. The major software components of the system being developed have to be identified and then allocated to the various hardware components on which the system will operate. All software systems can be divided into four basic functions. The first is ( data storage ) . Most information systems require data to be stored and retrieved, whether a small file,such as a memo produced by a word processor, or a large database, such as one that stores an organization’s accounting records.The second function is the ( data access logic ) , the processing required to access data, which often means database queries in Structured Query Language. The third function is the ( application logic ) , which is the logic documented in the DFDs, use cases,and functional requirements.The fourth function is the presentation logic, the display of information to the user and the acceptance of the user’s commands.The three primary hardware components of a system are ( clients,servers,and network ) .

(架构设计)的目标是确定应用软件的哪些部分将分配给哪些硬件。必须确定正在开发的系统的主要软件组件,然后将其分配给系统将在其上运行的各种硬件组件。所有的软件系统都可以分为四个基本功能。首先是(数据存储)。大多数信息系统都需要存储和检索数据,无论是小文件(例如文字处理器生成的备忘录)还是大型数据库(例如存储组织的会计记录的数据库)。第二个功能是(数据访问逻辑) ),访问数据所需的处理,这通常意味着结构化查询语言中的数据库查询。第三个功能是(应用逻辑),即DFD、用例和功能需求中记录的逻辑。第四个功能是表示逻辑,向用户显示信息并接受用户的命令。系统的三个主要硬件组件是(客户端、服务器和网络)。

(十)

The architecture design specifies the overall architecture and the placement of software and hardware that will be used. Architecture design is a very complex process that is often left to experienced architecture designers and consultants. The first step is to refine the ( nonfunctional requirements ) into more detailed requirements that are then employed to help select the architecture to be used and the software components to be placed on each device. In a ( client-server architecture ) , one also has to decide whether to use a two-tier, three-tier, or n-tier architecture. Then the requirements and the architecture design are used to develop the hardware and software specification. There are four primary types of nonfunctional requirements that can be important in designing the architecture. ( Operational requirements ) specify the operating environment(s) in which the system must perform and how those may change over time. ( Performance requirements ) focus on the nonfunctional requirements issues such as response time, capacity, and reliability. ( Security requirements ) are the abilities to protect the information system from disruption and data loss, whether caused by an intentional act. Cultural and political requirements are specific to the countries in which the system will be used.

架构设计指定了总体架构以及将使用的软件和硬件的布局。架构设计是一个非常复杂的过程,通常留给经验丰富的架构设计师和顾问。第一步是将(非功能性需求)细化为更详细的需求,然后使用这些需求来帮助选择要使用的架构以及要放置在每个设备上的软件组件。在(客户端-服务器架构)中,还必须决定是使用两层、三层还是n层架构。然后使用需求和架构设计来开发硬件和软件规范。有四种主要类型的非功能性需求对于设计架构非常重要。 (操作要求)指定系统必须执行的操作环境以及这些环境如何随时间变化。 (性能需求)关注响应时间、容量、可靠性等非功能性需求问题。 (安全要求)是指保护信息系统免受破坏和数据丢失的能力,无论是否是故意行为造成的。文化和政治要求因系统使用国家而异。

  • 2
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
SQLAlchemy 是一个 SQL 工具包和对象关系映射(ORM)库,用于 Python 编程语言。它提供了一个高级的 SQL 工具和对象关系映射工具,允许开发者以 Python 类和对象的形式操作数据库,而无需编写大量的 SQL 语句。SQLAlchemy 建立在 DBAPI 之上,支持多种数据库后端,如 SQLite, MySQL, PostgreSQL 等。 SQLAlchemy 的核心功能: 对象关系映射(ORM): SQLAlchemy 允许开发者使用 Python 类来表示数据库表,使用类的实例表示表中的行。 开发者可以定义类之间的关系(如一对多、多对多),SQLAlchemy 会自动处理这些关系在数据库中的映射。 通过 ORM,开发者可以像操作 Python 对象一样操作数据库,这大大简化了数据库操作的复杂性。 表达式语言: SQLAlchemy 提供了一个丰富的 SQL 表达式语言,允许开发者以 Python 表达式的方式编写复杂的 SQL 查询。 表达式语言提供了对 SQL 语句的灵活控制,同时保持了代码的可读性和可维护性。 数据库引擎和连接池: SQLAlchemy 支持多种数据库后端,并且为每种后端提供了对应的数据库引擎。 它还提供了连接池管理功能,以优化数据库连接的创建、使用和释放。 会话管理: SQLAlchemy 使用会话(Session)来管理对象的持久化状态。 会话提供了一个工作单元(unit of work)和身份映射(identity map)的概念,使得对象的状态管理和查询更加高效。 事件系统: SQLAlchemy 提供了一个事件系统,允许开发者在 ORM 的各个生命周期阶段插入自定义的钩子函数。 这使得开发者可以在对象加载、修改、删除等操作时执行额外的逻辑。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

算法小生Đ

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值