Software Architecture Recovery based on Dynamic Analysis
- 格式:pdf
- 大小:180.36 KB
- 文档页数:8
22类高频场景词汇一、家庭场景(Family Scene)1. father [ˈfɑːðə(r)] n. 父亲。
2. mother [ˈmʌðə(r)] n. 母亲。
3. son [sʌn] n. 儿子。
4. daughter [ˈdɔːtə(r)] n. 女儿。
5. brother [ˈbrʌðə(r)] n. 兄弟。
6. sister [ˈsɪstə(r)] n. 姐妹。
7. grandfather [ˈɡrænfɑːðə(r)] n. 祖父;外祖父。
8. grandmother [ˈɡrænmʌðə(r)] n. 祖母;外祖母。
9. home [həʊm] n. 家;adv. 在家。
10. family [ˈfæməli] n. 家庭。
二、学校场景(School Scene)1. teacher [ˈtiːtʃə(r)] n. 教师。
2. student [ˈstjuːdnt] n. 学生。
3. classroom [ˈklɑːsruːm] n. 教室。
4. desk [desk] n. 书桌。
5. chair [tʃeə(r)] n. 椅子。
6. book [bʊk] n. 书。
7. pen [pen] n. 钢笔。
8. pencil [ˈpensl] n. 铅笔。
9. blackboard [ˈblækbɔːd] n. 黑板。
10. schoolbag [ˈskuːlbæɡ] n. 书包。
三、购物场景(Shopping Scene)1. shop [ʃɒp] n. 商店;v. 购物。
2. supermarket [ˈsuːpəmɑːkɪt] n. 超级市场。
3. grocery [ˈɡrəʊsəri] n. 食品杂货店。
4. product [ˈprɒdʌkt] n. 产品。
5. price [praɪs] n. 价格。
1前言。
2Mathematics(数学)。
3DataStructures&Algorithms(数据结构、算法)。
4Compiler(编译原理)。
5OperatingSystem(操作系统)。
6Database(数据库)。
7C(C语言)。
8C++(C++语言)。
9Object-Oriented(面向对象)。
10SoftwareEngineering(软件工程)。
11UNIXProgramming(UNIX编程)。
12UNIXAdministration(UNIX系统管理)。
13Networks(网络)。
14WindowsProgramming(Windows编程)。
15Other(*)。
Mathematics(数学)。
书名(英文):DiscreteMathematicsandItsApplications(FifthEdition)。
书名(中文):离散数学及其应用(第五版)。
原作者:KennethH.Rosen。
书名(英文):ConcreteMathematics:AFoundationforComputerScience(SecondEdition)。
书名(中文):具体数学:计算机科学基础(第2版)。
原作者:RonaldL.Graham/DonaldE.Knuth/OrenPatashnik。
DataStructures&Algorithms(数据结构、算法)。
书名(英文):DataStructuresandAlgorithmAnalysisinC,SecondEdition。
书名(中文):数据结构与算法分析--C语言描述(第二版)。
原作者:MarkAllenWeiss。
书名(英文):DataStructures&ProgramDesignInC(SecondEdition)。
书名(中文):数据结构与程序设计C语言描述(第二版)。
原作者:RobertKruse/C.L.Tondo/BruceLeung。
计算机专业术语中英⽂对照计算机专业术语对照Aabstraction layer,抽象层access,获取,存取acoustic coupler,声⾳耦合器Active Directory,活动⽬录Acyclic Dependencies Principle,⾮循环依赖原则(ADP)acyclic digraph,有向⽆环图Adaptive Code,⾃适应代码Add Parameter,添加参数ADSL,Asymmetrical Dingital Subscriber Loop,⾮对称数字⽤户环线affinity,绑定affinity group,地缘组agent,代理agent-based interface,代理⼈界⾯Agile,敏捷⽅法论agile practice,敏捷实践agile peocess,敏捷流程agility,敏捷性AI,Artificial Intelligence,⼈⼯智能air waves,⽆线电波algorithm,算法analog,模拟的animation,动画annotation,注解,注释answering machine,电话应答机antenna,天线anti-pattern,反模式APM,异步编程模型(Asynchronous Programming Model)Apocalyptic defect,灾难缺陷application,应⽤,应⽤程序,应⽤软件application life cycle,应⽤程序⽣命周期application pool,应⽤程序池Application Programming Interface,应⽤程序编程接⼝(API)architecture,体系机构,结构architecture decay,架构腐坏Architecture Style,架构风格ARPA,Advanced Research Projects Agency,(美国国防部)⾼级研究计划署ARPAnet,ARPA⽹Arrange-Act-Assert,准备-执⾏-断⾔(AAA)artifact,构建物4ASF,Apache Software Foundation 的简写Aspect-Oriented Programming,⾯向切⾯编程(AOP)aspect ratio,屏幕⾼宽⽐assembly,程序集Asynchronous Programming Model,异步编程模型(APM)ATM,asynchronous transfer mode,异步传输模式atomic opreation,原⼦操作atomic transaction,原⼦事务atomicity,原⼦性attribute,特性augmented reality,增强实现authentication,⾝份验证authorization,授权automated unit testing,⾃动化单元测试automation,⾃动化autonomous,独⽴性availability,可⽤性availability set,可⽤性集AZs,可⽤性区域(Availability Zones,亚马逊 AWS 中数据中⼼的叫法)4BBackend as a Service,后端即服务(BaaS)backpane,底板backward compatibility,向后兼容性bandwidth,带宽bar code,条形码Base Class Library,基类库(BCL)baseline,准线baud,波特BCL,基类库(Base Class Library)bear,熊behavior,⾏为behavior preserving program transformations,⾏为保留式程序转换1 Behavioral error,⾏为错误BFF,为前端服务的后端(Backends For Frontends)4Big Ball of Mud,⼤泥球(BBM)big data,⼤数据Big Design Up Front,⼤优先设计(BDUF)binary,⼆进制的binochlar,双⽬并⽤的bit,⽐特Bit-field,位域bitnik,⽐特族blob,BLOBblock,阻断block blob,块 BLOBBlockchain as a Service,区块链即服务(BaaS)bottleneck,瓶颈bounded context,边界上下⽂、界限上下⽂4box,装箱bps,bits per second,⽐特/秒breakpoint,断点broadcast,(⽆线电或电视)⼴播Broken Hierarchy,⽀离破碎的层次结构2Broken Modularization,拆散的模块化2brownfield project,⾏进中项⽬Browser Object Model,浏览器对象模型(BOM)browser-server,浏览器-服务器bug,缺陷built-in,内置的,内建的;嵌⼊的;内置bulkhead,舱壁4business intelligence,商业智能business layer,业务层business logic layer,业务逻辑层busy (status),忙(状态);繁忙(状态)byte,字节Ccable,电缆Cache/Caching,缓存call stack,调⽤堆栈callout box,标注框camelCase,camel ⼤⼩写canary releasing,⾦丝雀发布4carbon copy,复写本,副本;抄送(CC)carriage return,回车Cascading Style Sheets,层叠样式表(CSS)catastrophic failover,灾难性故障转移4CD,持续交付(Continuous Delivery)4CDC,消费者驱动的契约(Customer-Driven Contract)4CDN,内容分发⽹络(Content Delivery Network)cell,单元cellular telephone,移动电话Central Processing Unit,中央处理器(CPU)certificate,(数字)证书Certificate Authority,证书认证机构Change Bidirectional Association to Unidirectional,将双向关联改为单向关联1Change Point,修改点:需要往代码中引⼊修改的点Change Reference to Value,将引⽤对象改为值对象1Change Unidirectional Association to Bidirectional,将单向关联改为双向关联1Change Value to Reference,将值对象改为引⽤对象1channel,信道,频道character,字符Characterization test,特征测试:描述软件某部分的当前⾏为的测试,当你修改代码时能够⽤来保持⾏为check in,签⼊check out,签出chip,芯⽚choreography,协同CI,持续集成(Continuous Integration)4cipher,密码claim,声明class definition,类定义CLI,公共语⾔基础结构(Common Language Infrastructure)client-server,客户端-服务器clone,克隆,复制cloud computing,云计算cloud service,云服务CLR,公共语⾔运⾏时(Common Language Runtime)CLS,公共语⾔规范(Common Language Specification)cluster,集群clustered index,聚集索引CMS,内容管理系统(Content Management System)co-occurring smells,同时出现的坏味2coaxial cable,同轴电缆COBIT,信息和相关技术的控制⽬标,Control Objectives for Information and Related Technology4 CoC,更改开销(Cost of Change)code smell,代码味道Collapse Hierarchy,折叠继承关系1comcurrency,并发command,命令command prompt,命令⾏提⽰Command/Query Responsibility Segregation,命令/查询职责分离(CQRS)Command/Query Separation,命令/查询分离(CQS)commingled bits,混合的⽐特communication,通信community,社区committed,已提交(的)Common Intermediate Language,公共中间语⾔Common Language Infrastructure,公共语⾔基础结构(CLI)Common Language Runtime,公共语⾔运⾏时(CLR)Common Language Specification,公共语⾔规范(CLS)Common Type System,公共类型系统(CTS)common name,通⽤名称compatibility,兼容性Competing Consumer pattern,消费者竞争模式4Component Object Model,组件对象模型(COM)composite formatting,复合格式化Composite Pattern,复合模式concurrency conflicts,并发冲突concurrency mode,并发模式conditional compilation,条件编译conditional compilation statement,条件编译语句configuration,配置,设置connection string,连接字符串Consolidate Conditional Expression,合并条件表达式1Consolidate Duplicate Conditional Fragments,合并重复的条件⽚段1consistenct,⼀致性constructor,构造函数container,容器Container As A Service,容器即服务(CaaS)4content,内容context,上下⽂contextual keyword,上下⽂关键字continuous integration,持续集成contribute,贡献Contributor License Agreement,贡献者许可协议convention,约定covariance,协变contravariance,逆变convert,转换Convert Procedural Design to Objects,将过程化设计转化为对象设计1cookie,Cookiecore,内核;.NET Core 的简写(能且仅能与 .NET Framework 的简写nfx同时出现,作如nfx/core,单独使⽤时应为全称.NET Core)corruption,损毁Cosmetic issue,外观上问题Cost of Change,更改开销(CoC)COTS,现成的商业软件(Commercial Off-The Shelf)4counterpoint,对位4Coupling count,耦合数:当⼀个⽅法被调⽤时传给它以及从它传出来的值的数⽬。
系统架构设计师大纲(System architect program)System Architect exam outlineI. examination instructions:1. test objectivesQualified personnel should be able to according to the system requirements specification, combined with the actual situation of the development of technology and application, considering the constraint conditions, correct and reasonable design of software architecture, system architecture to ensure the good properties of the project; to look askance in system architecture description, analysis, design and evaluation; to write corresponding design documents in accordance with the relevant standards; able to work with the system analyst, project manager of mutual collaboration and cooperation; senior engineer with the actual work ability and professional level.2. examination requirements(1) master the basic knowledge of computer hardware, software and network;(2) familiar with the information system development process;(3) understand the standard of information system development and the standard of common information technology;(4) familiar with the mainstream middleware and applicationserver platforms;(5) master the basic techniques of software system modeling and system architecture design;(6) familiar with information security technology, security strategy and safety management knowledge;(7) to understand the basic knowledge of information technology and related laws and regulations;(8) understand the industry characteristics of users, and design appropriate system design according to the characteristics of the industry;(9) master the basic mathematical knowledge of application(10) proficiency in reading and correctly understanding English literature in related fields;3. test subjects design settings(1) comprehensive knowledge of information systems, examination time is 150 minutes, written examination, multiple-choice questions;(2) system architecture design case analysis, examination time is 90 minutes, written test, question and answer question;(3) system architecture design papers, examination time is 120 minutes, written test, thesis questions.Two, examination scopeExamination subjects 1: comprehensive knowledge of information systems1. basic knowledge of computer software and network1.1 operating systemThe type and structure of the L operating systemFundamentals of L operating systemsL network operating system and network managementL embedded operating system and real time operating system1.2 database systemThe type, structure and performance evaluation of L database management systemL commonly used relational database management systemL database schemaL database normalizationL distributed database system, parallel database systemL data warehouse and data mining technologyL Database EngineeringL backup recovery1.3 embedded systemsFeatures of L embedded systemHardware composition and design of L embedded systemL embedded system application software and development platformL embedded system networkL embedded system database1.4 data communication and computer networkBasic knowledge of L data communicationL open system interconnection reference modelL common protocol standardsL network interconnection and common network equipmentThe classification and application of L computer network1.5 multimediaTypes, characteristics and data formats of L multimediaCompression coding of L multimedia data1.6 system configuration and performance evaluationL multilayer structure, distributed systemL system configuration methods (double, double, hot backup, fault tolerance, clustering)L performance calculations (response time, throughput, TAT)L performance design (system tuning, Amdahl solutions, response characteristics, load balancing)L performance metrics (SPEC-Int, SPEC-Fp, TPC, Gibsonmix, response times)L performance evaluation2. basic knowledge of information technology2.1 overall planning of information systems engineeringL overall planning objectives and scopeMethodology of L master planningComposition of L information systemsImplementation of L information system2.2, government informatization and e-governmentThe concept, content and technical form of L E-government L strategy and course of Chinese government informatizationThe process model and technical model of L e-government construction2.3 enterprise informatization and e-commerceL enterprise informatization concept, purpose, planning and methodThe main modules and main algorithms of L ERPL enterprise business process reengineering (BPR) Application of L, CRM and PDM in EnterpriseL knowledge managementL enterprise application integrationL idea of whole supply chain managementL Business IntelligenceTypes and standards of L E-commerceTwo4 Information Resource Management2.5 international and domestic standards, laws and regulations concerning informatization3. basic knowledge of system development3.1 development managementThe scope, time, and cost of the L projectL document management, configuration managementQuality and risk of L software developmentOperation and evaluation of L software3.2 demand managementL requirements changeL requirements trackingL demand change risk management3.3 software development methodL software development life cycleL software development model (waterfall model, evolution model, incremental model, spiral model, prototype, component assembly model, RUP, agile method)L components and software reuseL reverse engineeringL formal method3.4 software development environment and toolsL integrated development environmentL development tools (modeling tools, analysis and design tools, programming tools, testing tools, project management tools, etc.)3.5 design methodsL analysis and design diagrams (DFD, ERD, UML, flow charts, NS diagrams, PAD)L structured analysis and designL module designL object oriented analysis and designL I/O design, man-machine interface designL design patterns3.6 component based developmentThe concept and classification of L componentsL Middleware TechnologyL typical application architecture (J2EE,.NET)3.7 application system constructionL application system design and development (use of analysis and design methods, external design, internal design, programming design, testing)The use of L packages (development tools, operations management tools, business processing tools, ERP, groupware, OA tools)3.8 test and reviewL test review methodL validation and validation (V&V)L test automationL test design and management methods4. basic knowledge of software architectureThe concept of L software architectureThe style of L software architectureL domain specific software architectureL architecture based software development methodologyL software architecture evaluationL software product lineL design patterns5. safety and reliability technology4.1 information security and privacyL encryption and decryptionL authentication (digital signature, key, password)L access controlL security and security management (anti leakage, digital watermarking)L Security Protocols (SSL, PGP, IPSec)Backup and recovery of L systemL prevents viruses4.2 system reliabilityL reliability design (fault tolerance technique, error avoidance technique)L reliability index and evaluation4.3 safety regulations and rules for protecting private informationL information system security regulations and systemsL computer antivirus systemL protects private information rules6. standardization and intellectual property rightsL standardization awareness, standardization of development, standard life cycleL international standards, American standards, national standards, trade standards, local standards and enterprise standardsL code standards, file format standards, security standards,software development standards and documentation standardsL standardization bodiesL intellectual property7. application dataL probability and statistics applicationsL graph theory applicationsL combination analysisSelection and application of L algorithm (numerical algorithm and non numerical algorithm)L methods of operations (network planning technology, linear programming, forecasting, decision making, inventory management, simulation)L mathematical modeling8. professional EnglishL has the level of English reading required by senior engineersL master English terminology in this fieldExamination subjects 2: system architecture design case analysis1. system planningProposal and feasibility analysis of L system projectL system formulation, evaluation and improvementAnalysis and comparison of new and old l systemsL effective use of existing software, hardware, and data resources2. software architecture designL software architecture designL XML TechnologyL architecture based software development processL software quality attributesL architecture model (style)L domain specific software architectureL architecture based software development methodologyL architecture evaluationL software product lineL system evolution3. design patternsThe concept of l design patternsThe composition of the l design patternL schema and software architectureL design pattern classificationImplementation of l design pattern4. system designL process designL man-machine interface designL file design, storage designL database designDesign of l network application systemIntegration and design of L system running environment L middleware and application serverL performance design and performance evaluationL system conversion plan5. software system modelingL system requirementsThe role and significance of L modelingL defines problems (goals, functions, performance, etc.) and resolution models (static structure models, dynamic behavior models, and physical models)L structured system modeling and data flow diagramsL object oriented system modelingL unified modeling language (UML)L database modeling and E-R diagramL reverse engineering6. distributed system designDesign of L distributed communication protocolL object based distributed system designDesign of Web based distributed system for LL distributed system design based on messaging and collaborationInteroperability design of L heterogeneous distributed systems7. embedded system designL real time systems and embedded system featuresL real time task scheduling and multitask designL interrupt handling and exception handlingDesign and development of L embedded system8. reliability analysis and design of the systemFault model and reliability model of L systemReliability analysis and reliability calculation of L systemL measures to improve system reliabilityFault countermeasures and backup and recovery of L system9. security and privacy design of the systemAccess control techniques for L systemsL data integrityL data and file encryptionSecurity of L communicationSecurity design of L systemExamination subjects 3: system architecture design papersAccording to the given system architecture design, a number of topics, select one of the topics, in accordance with the requirements of the thesis.1. system modelingL definition, problem, and resolution modelL structured system modelingL object oriented system modelingL database modeling2. software architecture designL software architecture designL domain specific software architectureL architecture based software development methodologyL software evolution3. system designL process designHuman computer interface design of L systemL file design, storage designL database designDesign of l network application systemIntegration and design of L system running environment L system performance designL middleware and application server4. distributed system designDesign of L distributed communication protocolL object based distributed system designDesign of Web based distributed system for LL distributed system design based on messaging and collaborationInteroperability design of L heterogeneous distributed systems5. reliability analysis and design of the systemFault model and reliability model of L systemL measures to improve system reliabilityFault countermeasures and backup and recovery of L system6. security and privacy design of the systemAccess control techniques for L systemsL data integrityL data and file encryptionSecurity of L communicationSecurity design of L systemExamples of questionsExamination subjects 1: comprehensive knowledge of information systems(a) multiple-choice questions1. in the TCP/IP protocol hierarchy, SNMP is (2) request / response protocol over (1) protocol. The public managementinformation service / public management information protocol CMIS/CMIP based on ISO/OSI/RM is a complete network management protocol family, and the network management application process uses the OSI reference model (3).(1) A.TCP, B.UDP, C.HTTP, D.IP(2) A. asynchronous B. synchronization, C., master-slave D., connection oriented(3) A. network layer, B. transport layer, C. presentation layer,D. application layerTwoThe software product line is mainly composed of (4) and the product collection two parts.(4) A. component library, B. core resource, C. architecture,D. Development Organization(two) questions and answersRead the following narrative about software architecture, answer questions 1 and 2.A group company to develop a network of financial procedures, so that employees can work on the Internet for financial processing and reimbursement. When designing the architecture of the financial process, the project team was divided:(1) Zhang engineer believes that client / server (C/S) architecture should be adopted. The Finance Department of each branch should install a software client which is connected to the head of the Finance Department of the head office through the client. If employees are out of town on business, they need to reimburse their accounts, and they also need to install this client.(2) Li engineer believes that the browser / server (BS) structure should be adopted, and the branch offices and staff directly through the Windows operating system own IE browser, you can connect to the head office of the finance department.After the intense discussion of the project team, the hybrid structure of C/S and B/S was selected.[problem 1]Please discuss briefly the differences between the C/S structure and the B/S structure and their respective advantages and disadvantages in a word less than 200 words.[problem 2]How do you design the C/S and B/S hybrid structures with words less than 200 words, so what are the benefits of the design?(three) thesis questionsOn the grasp of user's needs in system designFor systems engineers, it is the most difficult to properly understand the content of the work and design effective systems when a work is systematized.In order to correctly reflect the user's requirements to the specifications of the system, the conventional approach is to submit the specifications and output statements to the user for comments. In some cases, a prototype of the system is also available. Ask the user for a trial.Please focus on the topic of "grasp user needs in system design", and then discuss the following three problems in turn.1. describe the development project you are involved in, and the work you do.2. describe where you've done your work, and what means of communicating with users in order to reflect user requirements into the system specifications?3. give a brief account of what you think is effective and no effect on the means you employ.。
2022-2023年软件水平考试《高级系统架构设计师》预测试题(答案解析)全文为Word可编辑,若为PDF皆为盗版,请谨慎购买!第壹卷一.综合考点题库(共50题)1.应用系统构建中可以采用多种不同的技术,()可以将软件某种形式的描述转换为更高级的抽象表现形式,而利用这些获取的信息,(请作答此空 )能够对现有系统进行修改或重构,从而产生系统的一个新版本。
A.逆向工程((Reverse Engineering)B.系统改进 (System Improvement)C.设计恢复 (Design Recovery )D.再工程 (Re-engineering)正确答案:D 本题解析:所谓软件的逆向工程就是分析已有的程序,寻求比源代码更高级的抽象表现形式。
一般认为,凡是在软件生命周期内将软件某种形式的描述转换成更为抽象形式的活动都可称为逆向工程。
与之相关的概念是:重构(restructuring),指在同一抽象级别上转换系统描述形式;设计恢复(design recovery),指借助工具从已有程序中抽象出有关数据设计、总体结构设计和过程设计的信息(不一定是原设计);再工程(re-engineering),也称修复和改造工程,它是在逆向工程所获信息的基础上修改或重构已有的系统,产生系统的一个新版本。
2.企业数字化转型的五个发展阶段依次是()A.初始级发展阶段、单元级发展阶段、流程级发展阶段、网络级发展险段、生态级发展阶段B.初始级发展阶段、单元级发展阶段、系统级发展阶段、网络级发展阶段、生态级发展阶段C.初始级发展阶段、单元级发展阶段、流程级发展阶段、网络服发展输段、优化级发展阶段D.初始级发展阶段、流程级发展阶段、系统级发展险段、网络级发展阶段、生态级发展阶段正确答案:A本题解析:企业数字化转型的五个发展阶段依次是:初始级发展阶段、单元级发展阶段、流程级发展阶段、网络级发展险段、生态级发展阶段。
3.The objective of (请作答此空) 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 (72). 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 (73), the processing required to access data, which often means database queries in Structured Query Language. The third function is the (74), 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 (75).A.architecture designB.modular designC.physical designD.distribution design正确答案:A本题解析:架构设计的目标是确定应用软件的哪些部分将被分配到何种硬件。
IBM DB2 UDB产品介绍IBM DB2 UDB产品介绍前言数据库管理系统,尤其是关系型数据库,与IBM数据库有着不可分割的关系。
三十多年来从理论研究到具体的系统实现,IBM数据库研究人员对数据库管理系统的发展作出了极大的贡献。
70年代之前,数据库中的数据结构以层次型(如IBM IMS数据库)及网络型为主。
在这些数据库中记录与记录之间往往存在着指针(pointers)以方便应用程序搜寻有关联的数据。
1970年IBM数据库研究中心的E.F.Codd博士在其论文[Codd70]中提出了关系型的数据库模式。
在这创新的理论中记录与记录的关系建立在它们共享的数值上而非基于隐藏的指针。
数据库的查询因而可以用非过程化(nonprocedural)的语句表达。
Codd同时证明了用一阶谓词逻辑微积分(first-order predicate calculus)等数学理论作为非过程化语句基础的可能性,并进一步地发展了关系微积分(relational calulus[Codd71a])与关系代数(relational algebra[Codd71b]),奠定了关系型数据库日后发展的理论基础。
为此E.F.Codd博士在1981年得到了计算机科学界的最高荣誉奖ACM图灵奖(ACM Turing Award)。
1973年位于美国加州圣荷西市的IBM数据库研究中心开始了一个大的关系型数据库系统研究项目System R[Astrahan 76],探讨并验证在多用户与大量数据下关系型数据库的实际可行性。
System R对关系型数据库的商业化起着关键性的催化作用。
在D.Chamberlin博士的领导下System R的一个研究小组发明了一套比关系微积分与关系代数更适合最终用户使用的非程序化查询语言SQL[Chamberlin74,76,80]。
SQL的设计宗旨是面向最终用户,达到简单,易学,易用。
并且,SQL把早期数据管理系统中各种独立的功能如查询,数据修改,数据定义和控制等整合到一个单一的语言环境内。
计算机专业英语词汇计算机专业英语主要涉及到计算机原理、操作系统、数据结构、算法、软件工程、网络技术、数据库技术、人工智能等方面的知识。
下面是一些常用的计算机专业英语词汇:一、计算机原理1. computer architecture 计算机体系结构2. central processing unit (CPU) 中央处理器3. random access memory (RAM) 随机存取存储器4. read-only memory (ROM) 只读存储器5. input/output (I/O) input/output 输入输出6. software 软件7. hardware 硬件8. operating system (OS) 操作系统9. binary code 二进制码10. processor 处理器二、操作系统1. file system 文件系统2. kernel 内核3. process 进程4. thread 线程5. memory management 内存管理6. virtual memory 虚拟内存7. disk management 磁盘管理8. device drivers 设备驱动程序9. system calls 系统调用10. interrupt 中断三、数据结构和算法1. algorithm 算法2. data structure 数据结构3. array 数组4. stack 栈5. queue 队列6. linked list 链表7. binary tree 二叉树8. search algorithm 查找算法9. sorting algorithm 排序算法10. recursion 递归四、软件工程1. software engineering 软件工程2. project management 项目管理3. software design 软件设计4. software testing 软件测试5. software documentation 软件文档6. object-oriented programming (OOP) 面向对象编程7. agile development 敏捷开发8. code review 代码审查9. software maintenance 软件维护10. software quality assurance 软件质量保障五、网络技术1. computer network 计算机网络2. local area network (LAN) 局域网3. wide area network (WAN) 广域网4. internet 互联网5. World Wide Web (WWW) 万维网6. transmission control protocol/Internet protocol (TCP/IP) 传输控制协议/网际协议7. router 路由器8. switch 交换机9. firewall 防火墙10. wireless network 无线网络六、数据库技术1. database 数据库2. relational database 关系数据库3. SQL (Structured Query Language) 结构化查询语言4. database management system (DBMS) 数据库管理系统5. data mining 数据挖掘6. data warehousing 数据仓库7. backup and recovery 备份和恢复8. transaction processing system (TPS) 事务处理系统9. normalization 数据库规范化10. indexing 索引七、人工智能1. artificial intelligence (AI) 人工智能2. machine learning 机器学习3. deep learning 深度学习4. neural network 神经网络5. natural language processing (NLP) 自然语言处理6. expert systems 专家系统7. decision support systems (DSS) 决策支持系统8. robotics 机器人技术9. computer vision 计算机视觉10. cognitive computing 认知计算以上是一些常用的计算机专业英语词汇,掌握这些词汇可以帮助学生更好地理解计算机领域的技术和知识,也有助于提高英语应用能力。
发表于: 2009-11-29 14:26发表主题: ITIL术语中英文对照表,论坛里有看到,但是没有过验证,在这里贴ITIL术语中英文对照表 Absorbed overhead 可分摊间接费用 Absorption costing 吸收成本法,完全成本法Acceptance 验收 Acceptance environment 验收环境 Acceptance test 验收测试 Access control 访问控制 Accounting会计核算 Accuracy 准确度 Action lists 行动列表 Activity Based Costing (ABC) 作业成本法(ABC) Adaptive maintenance 适应性维护 Additive maintenance 补充性维护 Adjustability 可调整性 Agreed Service Time (AST)约定服务时段 Alert 告警 Alert phase 告警阶段 Allocated cost 可直接分配成本 Application 应用,应用系统Application maintenance 应用维护 Application management 应用管理 Application sizing 应用选型 Application software 应用软件 Apportioned cost 待分摊间接成本 Architecture 架构 Archive 存档 Asset 资产 Asset management 资产管理Assurance 保证 Attributes 属性 Audit 审计 Auditability 可审计性 Authentication 验证 Authenticity 真实性Authorisation 授权 Automatic Call Distribution (ACD) 自动呼叫转发(系统)(ACD) Availability 可用性Availability management 可用性管理 Availability Management Database (AMDB) 可用性管理数据库(AMDB)Backup 备份 Balanced Scorecard (BSC) 平衡计分卡 Baseline 基线 Baseline security 安全基线 Batch processing rate批处理速度 Benchmark 标杆 Biometrics 生物测定学 BS7799 BS7799 Budgeting 预算编制 BugBUG(也可形象地译为“臭虫”) Build 构建 Building environment 构建环境 Business 业务,商业 Business capacity management 业务能力管理 Business Continuity Management (BCM) 业务持续性管理(BCM) Business function业务功能,业务职能部门 Business Impact Analysis (BIA) 业务影响分析(BIA) Business process 业务流程 Business recovery objective 业务恢复目标 Business recovery plan framework 业务恢复计划框架 Business recovery plans业务恢复计划 Business recovery team 业务恢复小组 Business Relationship Management (BRM)业务关系管理(BRM) Business request 业务请求 Business Unit (BU) 业务单元(BU) Bypass 临时措施 Call 呼叫Call center 呼叫中心 Capacity Database (CDB) 能力数据库(CBD) Capacity management 能力管理 Capacity plan能力计划 Capacity planning 能力规划 Capital investment appraisal 资本投资评估 Capitalization 资本化 Category类别,分类 Central point of contact 联络中心 Certificate 证书 Certification Authority (CA) 认证机构(CA) Certify 认证 Change 变更 Change Advisory Board (CAB) 变更顾问委员会(CAB) Change Advisory Board /Emergency Committee (CAB/EC) 变更顾问委员会/应急委员会(CAB/EC) Change authority 变更授权 Change builder变更构建者 Change control 变更控制 Change document 变更文档 Change history 变更历史 Change log 变更日志Change management 变更管理 Change manager 变更经理 Change model 变更模式 Change processing 变更处理Change Record 变更记录 Change request 变更请求 Chargeable unit 计费单元 Charging 计费 CI level 配置项级别Clarity 易理解性 Classification 分类,分级 Clean desk 桌面清理,桌面整理 Client 客户 Cold stand-by 冷支持Command, control and communications 命令、控制和协调 Communication facility 通信设备,通信设施 Compatibility 兼容性 Completeness 完整性 Complexity 复杂性 Component Failure Impact Analysis (CFIA)组件故障影响分析(CFIA) Compromise 泄漏 Computer 计算机 Computer Aided Systems Engineering (CASE)计算机辅助系统工程(CASE) Computer center 计算机中心 Computer operations 计算机操作 Computer platform计算机平台 Computer system 计算机系统 Computer Telephony Integration (CTI) 计算机电话集成(系统)(CTI)Confidentiality 保密性 Confidentiality, Integrity and Availability (CIA) 保密性、完整性和可用性(CIA)Configuration 配置 Configuration baseline 配置基线 Configuration control 配置控制 Configuration documentation配置文档 Configuration identification 配置标识 Configuration Item (CI) 配置项(CI) Configuration management配置管理Configuration Management Database (CMDB) 配置管理数据库(CMDB) Configuration management plan 配置管理计划 Configuration manager 配置经理 Configuration structure 配置结构 Configure 配置 Connectivity 连通性Contingency manager 应急经理 Contingency plan 应急计划 Contingency planning 应急规划 Contingency planning and control 应急规划及控制 Continuity 持续性 Continuity manager 持续性经理 Continuous availability 持续可用性Continuous operation 持续运作 Contract 合同 Control 控制 Controllability 可控性 CookieCookie(也可形象地译为“甜饼”,译者注) Correctability 可纠正性 Corrective controls 纠正性控制 Corrective maintenance 纠正性维护 Corrective measures 纠正措施 Cost 成本,费用 Cost effectiveness 成本效益 Cost management 成本管理 Cost unit 成本单元 Costing 成本核算 Countermeasure 防范措施 Cracker 骇客 CRAMM CRAMM(英国中央计算机与电信局行风险分析和管理的方法。
软件测试英语单词Acceptance testing : 验收测试Acceptance Testing:可接受性测试Accessibility test : 软体适用性测试actual outcome:实际结果Ad hoc testing : 随机测试Algorithm analysis : 算法分析algorithm:算法Alpha testing : α测试analysis:分析anomaly:异常application software:应用软件Application under test (AUT) : 所测试的应用程序Architecture : 构架Artifact : 工件ASQ:自动化软件质量(Automated Software Quality)Assertion checking : 断言检查Association : 关联Audit : 审计audit trail:审计跟踪Automated Testing:自动化测试Backus-Naur Form:BNF范式baseline:基线Basic Block:基本块basis test set:基本测试集Behaviour : 行为Bench test : 基准测试benchmark:标杆/指标/基准Best practise : 最佳实践Beta testing : β测试Black Box Testing:黑盒测试Blocking bug : 阻碍性错误Bottom-up testing : 自底向上测试boundary value coverage:边界值覆盖boundary value testing:边界值测试Boundary values : 边界值Boundry Value Analysis:边界值分析branch condition combination coverage:分支条件组合覆盖branch condition combination testing:分支条件组合测试branch condition coverage:分支条件覆盖branch condition testing:分支条件测试branch condition:分支条件Branch coverage : 分支覆盖branch outcome:分支结果branch point:分支点branch testing:分支测试branch:分支Breadth Testing:广度测试Brute force testing: 强力测试Buddy test : 合伙测试Buffer : 缓冲Bug : 错误Bug bash : 错误大扫除bug fix : 错误修正Bug report : 错误报告Bug tracking system: 错误跟踪系统bug:缺陷Build : 工作版本(内部小版本)Build Verfication tests(BVTs): 版本验证测试Build-in : 内置Capability Maturity Model (CMM): 能力成熟度模型Capability Maturity Model Integration (CMMI): 能力成熟度模型整合capture/playback tool:捕获/回放工具Capture/Replay Tool:捕获/回放工具CASE:计算机辅助软件工程(computer aided software engineering)CAST:计算机辅助测试cause-effect graph:因果图certification :证明change control:变更控制Change Management :变更管理Change Request :变更请求Character Set : 字符集Check In :检入Check Out :检出Closeout : 收尾code audit :代码审计Code coverage : 代码覆盖Code Inspection:代码检视Code page : 代码页Code rule : 编码规范Code sytle : 编码风格Code Walkthrough:代码走读code-based testing:基于代码的测试coding standards:编程规范Common sense : 常识Compatibility Testing:兼容性测试complete path testing :完全路径测试completeness:完整性complexity :复杂性Component testing : 组件测试Component:组件computation data use:计算数据使用computer system security:计算机系统安全性Concurrency user : 并发用户Condition coverage : 条件覆盖condition coverage:条件覆盖condition outcome:条件结果condition:条件configuration control:配置控制Configuration item : 配置项configuration management:配置管理Configuration testing : 配置测试conformance criterion:一致性标准Conformance Testing:一致性测试consistency :一致性consistency checker:一致性检查器Control flow graph : 控制流程图control flow graph:控制流图control flow:控制流conversion testing:转换测试Core team : 核心小组corrective maintenance:故障检修correctness :正确性coverage :覆盖率coverage item:覆盖项crash:崩溃criticality analysis:关键性分析criticality:关键性CRM(change request management): 变更需求管理Customer-focused mindset : 客户为中心的理念体系Cyclomatic complexity : 圈复杂度data corruption:数据污染data definition C-use pair:数据定义C-use使用对data definition P-use coverage:数据定义P-use覆盖data definition P-use pair:数据定义P-use使用对data definition:数据定义data definition-use coverage:数据定义使用覆盖data definition-use pair :数据定义使用对data definition-use testing:数据定义使用测试data dictionary:数据字典Data Flow Analysis : 数据流分析data flow analysis:数据流分析data flow coverage:数据流覆盖data flow diagram:数据流图data flow testing:数据流测试data integrity:数据完整性data use:数据使用data validation:数据确认dead code:死代码Debug : 调试Debugging:调试Decision condition:判定条件Decision coverage : 判定覆盖decision coverage:判定覆盖decision outcome:判定结果decision table:判定表decision:判定Defect : 缺陷defect density : 缺陷密度Defect Tracking :缺陷跟踪Deployment : 部署Depth Testing:深度测试design for sustainability :可延续性的设计design of experiments:实验设计design-based testing:基于设计的测试Desk checking : 桌前检查desk checking:桌面检查Determine Usage Model : 确定应用模型Determine Potential Risks : 确定潜在风险diagnostic:诊断DIF(decimation in frequency) : 按频率抽取dirty testing:肮脏测试disaster recovery:灾难恢复DIT (decimation in time): 按时间抽取documentation testing :文档测试domain testing:域测试domain:域DTP DETAIL TEST PLAN详细确认测试计划Dynamic analysis : 动态分析dynamic analysis:动态分析Dynamic Testing:动态测试embedded software:嵌入式软件emulator:仿真End-to-End testing:端到端测试Enhanced Request :增强请求entity relationship diagram:实体关系图Encryption Source Code Base:加密算法源代码库Entry criteria : 准入条件entry point :入口点Envisioning Phase : 构想阶段Equivalence class : 等价类Equivalence Class:等价类equivalence partition coverage:等价划分覆盖Equivalence partition testing : 等价划分测试equivalence partition testing:参考等价划分测试equivalence partition testing:等价划分测试Equivalence Partitioning:等价划分Error : 错误Error guessing : 错误猜测error seeding:错误播种/错误插值error:错误Event-driven : 事件驱动Exception handlers : 异常处理器exception:异常/例外executable statement:可执行语句Exhaustive Testing:穷尽测试exit point:出口点expected outcome:期望结果Exploratory testing : 探索性测试Failure : 失效Fault : 故障fault:故障feasible path:可达路径feature testing:特性测试Field testing : 现场测试FMEA:失效模型效果分析(Failure Modes and Effects Analysis)FMECA:失效模型效果关键性分析(Failure Modes and Effects Criticality Analysis) Framework : 框架FTA:故障树分析(Fault Tree Analysis)functional decomposition:功能分解Functional Specification :功能规格说明书Functional testing : 功能测试Functional Testing:功能测试G11N(Globalization) : 全球化Gap analysis : 差距分析Garbage characters : 乱码字符glass box testing:玻璃盒测试Glass-box testing : 白箱测试或白盒测试Glossary : 术语表GUI(Graphical User Interface): 图形用户界面Hard-coding : 硬编码Hotfix : 热补丁I18N(Internationalization): 国际化Identify Exploratory Tests –识别探索性测试IEEE:美国电子与电器工程师学会(Institute of Electrical and Electronic Engineers)Incident 事故Incremental testing : 渐增测试incremental testing:渐增测试infeasible path:不可达路径input domain:输入域Inspection : 审查inspection:检视installability testing:可安装性测试Installing testing : 安装测试instrumentation:插装instrumenter:插装器Integration :集成Integration testing : 集成测试interface : 接口interface analysis:接口分析interface testing:接口测试interface:接口invalid inputs:无效输入isolation testing:孤立测试Issue : 问题Iteration : 迭代Iterative development: 迭代开发job control language:工作控制语言Job:工作Key concepts : 关键概念Key Process Area : 关键过程区域Keyword driven testing : 关键字驱动测试Kick-off meeting : 动会议L10N(Localization) : 本地化Lag time : 延迟时间LCSAJ:线性代码顺序和跳转(Linear Code Sequence And Jump)LCSAJ coverage:LCSAJ覆盖LCSAJ testing:LCSAJ测试Lead time : 前置时间Load testing : 负载测试Load Testing:负载测试Localizability testing: 本地化能力测试Localization testing : 本地化测试logic analysis:逻辑分析logic-coverage testing:逻辑覆盖测试Maintainability : 可维护性maintainability testing:可维护性测试Maintenance : 维护Master project schedule :总体项目方案Measurement : 度量Memory leak : 内存泄漏Migration testing : 迁移测试Milestone : 里程碑Mock up : 模型,原型modified condition/decision coverage:修改条件/判定覆盖modified condition/decision testing :修改条件/判定测试modular decomposition:参考模块分解Module testing : 模块测试Monkey testing : 跳跃式测试Monkey Testing:跳跃式测试mouse over:鼠标在对象之上mouse leave:鼠标离开对象MTBF:平均失效间隔实际(mean time between failures)MTP MAIN TEST PLAN主确认计划MTTF:平均失效时间(mean time to failure)MTTR:平均修复时间(mean time to repair)multiple condition coverage:多条件覆盖mutation analysis:变体分析N/A(Not applicable) : 不适用的Negative Testing : 逆向测试, 反向测试, 负面测试negative testing:参考负面测试Negative Testing:逆向测试/反向测试/负面测试off by one:缓冲溢出错误non-functional requirements testing:非功能需求测试nominal load:额定负载N-switch coverage:N切换覆盖N-switch testing:N切换测试N-transitions:N转换Off-the-shelf software : 套装软件operational testing:可操作性测试output domain:输出域paper audit:书面审计Pair Programming : 成对编程partition testing:分类测试Path coverage : 路径覆盖path coverage:路径覆盖path sensitizing:路径敏感性path testing:路径测试path:路径Peer review : 同行评审Performance : 性能Performance indicator: 性能(绩效)指标Performance testing : 性能测试Pilot : 试验Pilot testing : 引导测试Portability : 可移植性portability testing:可移植性测试Positive testing : 正向测试Postcondition : 后置条件Precondition : 前提条件precondition:预置条件predicate data use:谓词数据使用predicate:谓词Priority : 优先权program instrumenter:程序插装progressive testing:递进测试Prototype : 原型Pseudo code : 伪代码pseudo-localization testing:伪本地化测试pseudo-random:伪随机QC:质量控制(quality control)Quality assurance(QA): 质量保证Quality Control(QC) : 质量控制Race Condition:竞争状态Rational Unified Process(以下简称RUP):瑞理统一工艺Recovery testing : 恢复测试recovery testing:恢复性测试Refactoring : 重构regression analysis and testing:回归分析和测试Regression testing : 回归测试Release : 发布Release note : 版本说明release:发布Reliability : 可靠性reliability assessment:可靠性评价reliability:可靠性Requirements management tool: 需求管理工具Requirements-based testing : 基于需求的测试Return of Investment(ROI): 投资回报率review:评审Risk assessment : 风险评估risk:风险Robustness : 强健性Root Cause Analysis(RCA): 根本原因分析safety critical:严格的安全性safety:(生命)安全性Sanity testing : 健全测试Sanity Testing:理智测试Schema Repository : 模式库Screen shot : 抓屏、截图SDP:软件开发计划(software development plan)Security testing : 安全性测试security testing:安全性测试security.:(信息)安全性serviceability testing:可服务性测试Severity : 严重性Shipment : 发布simple subpath:简单子路径Simulation : 模拟Simulator : 模拟器SLA(Service level agreement): 服务级别协议SLA:服务级别协议(service level agreement)Smoke testing : 冒烟测试Software development plan(SDP): 软件开发计划Software development process: 软件开发过程software development process:软件开发过程software diversity:软件多样性software element:软件元素software engineering environment:软件工程环境software engineering:软件工程Software life cycle : 软件生命周期source code:源代码source statement:源语句Specification : 规格说明书specified input:指定的输入spiral model :螺旋模型SQAP SOFTWARE QUALITY ASSURENCE PLAN 软件质量保证计划SQL:结构化查询语句(structured query language)Staged Delivery:分布交付方法state diagram:状态图state transition testing :状态转换测试state transition:状态转换state:状态Statement coverage : 语句覆盖statement testing:语句测试statement:语句Static Analysis:静态分析Static Analyzer:静态分析器Static Testing:静态测试statistical testing:统计测试Stepwise refinement : 逐步优化storage testing:存储测试Stress Testing : 压力测试structural coverage:结构化覆盖structural test case design:结构化测试用例设计structural testing:结构化测试structured basis testing:结构化的基础测试structured design:结构化设计structured programming:结构化编程structured walkthrough:结构化走读stub:桩sub-area:子域Summary:总结SVVP SOFTWARE Vevification&Validation PLAN:软件验证和确认计划symbolic evaluation:符号评价symbolic execution:参考符号执行symbolic execution:符号执行symbolic trace:符号轨迹Synchronization : 同步Syntax testing : 语法分析system analysis:系统分析System design : 系统设计system integration:系统集成System Testing : 系统测试TC TEST CASE 测试用例TCS TEST CASE SPECIFICATION 测试用例规格说明TDS TEST DESIGN SPECIFICATION 测试设计规格说明书technical requirements testing:技术需求测试Test : 测试test automation:测试自动化Test case : 测试用例test case design technique:测试用例设计技术test case suite:测试用例套test comparator:测试比较器test completion criterion:测试完成标准test coverage:测试覆盖Test design : 测试设计Test driver : 测试驱动test environment:测试环境test execution technique:测试执行技术test generator:测试生成器test harness:测试用具Test infrastructure : 测试基础建设test log:测试日志test measurement technique:测试度量技术Test Metrics :测试度量test procedure:测试规程test records:测试记录test report:测试报告Test scenario : 测试场景Test Script:测试脚本Test Specification:测试规格Test strategy : 测试策略test suite:测试套Test target : 测试目标Test ware : 测试工具Testability : 可测试性testability:可测试性Testing bed : 测试平台Testing coverage : 测试覆盖Testing environment : 测试环境Testing plan : 测试计划Testing procedure : 测试过程Thread testing : 线程测试time sharing:时间共享time-boxed : 固定时间TIR test incident report 测试事故报告ToolTip:控件提示或说明top-down testing:自顶向下测试TPS TEST PEOCESS SPECIFICATION 测试步骤规格说明Traceability : 可跟踪性traceability analysis:跟踪性分析traceability matrix:跟踪矩阵Trade-off : 平衡transaction:事务/处理transaction volume:交易量transform analysis:事务分析trojan horse:特洛伊木马truth table:真值表TST TEST SUMMARY REPORT 测试总结报告Tune System : 调试系统TW TEST WARE :测试件Usability Testing:可用性测试Usage scenario : 使用场景User acceptance Test : 用户验收测试User database :用户数据库User interface(UI) : 用户界面User profile : 用户信息User scenario : 用户场景V&V (Verification & Validation) : 验证&确认validation :确认verification :验证version :版本Virtual user : 虚拟用户volume testing:容量测试VSS(visual source safe):VTP Verification TEST PLAN验证测试计划VTR Verification TEST REPORT验证测试报告Walkthrough : 走读Waterfall model : 瀑布模型Web testing : 网站测试White box testing : 白盒测试Work breakdown structure (WBS) : 任务分解结构Zero bug bounce (ZBB) : 零错误反弹。
英语作文-揭秘集成电路设计中的时钟与数据恢复技术与应用In the realm of integrated circuit (IC) design, particularly in high-speed digital systems, the synchronization and recovery of clock and data signals play an essential role in ensuring reliable operation. Clock and data recovery (CDR) techniques are pivotal in modern electronic devices where the need for precise timing and efficient data transmission is paramount.Clock recovery involves the process of extracting an accurate clock signal from a data stream that may have been distorted or attenuated during transmission. This is crucial because many digital systems rely on a stable clock to synchronize operations and ensure data integrity. In contrast, data recovery focuses on correctly interpreting the transmitted data bits based on this recovered clock signal.### The Role of Clock and Data Recovery。
2nd International Conference on Humanities Science and Society Development (ICHSSD 2017)Design and Application of Experimental Teaching Assistant Platform forPrinciple of Computer CompositionLei Wei1, a, Qiuyun Zhao 1,b1 School of Computer, Chengdu University of Information Technology, Chengdu, Chinaa**************.cn,b***************.cn* Lei WeiKeywords: Principle of Computer Composition; Auxiliary teaching; Virtual experiment; Component. Abstract.This paper discusses problems existing in the experimental teaching of Principle of Computer Composition. In order to strengthen the teaching objective of the course and improve students’ practical ability and innovative thinking, an experimental teaching assistant platform is designed and developed based on MVC. The platform uses the SSM framework. The platform realizes functions of the resource sharing, student management, virtual experiment management, simulation program management, performance management, Q&A and system management. And through the component technology, the platform has good expansibility. The application shows that the platform plays a good role in strengthening the communication between teachers and students, promoting the achievement of teaching objectives and cultivating students’ abilities.1.IntroductionPrinciple of Computer Composition is a major compulsory course in the computer science major. It plays an important role in the course system of hardware category and cultivating students’ ability to analyze, develop, use and design computer hardware system [1]. In order to achieve the intended teaching objectives, the experimental teaching links are specially designed in the course. And through various means to guarantee the quality of the experiment, especially in recent years with the development of information technology, computer aided teaching has been widely introduced into the experimental teaching of Principle of Computer Composition [2-5]. But there are still some problems that need to be solved. Problems are mainly reflected as follows. More research focuses on the development of virtual experimental systems. There is no whole link to the experiment teaching and establishing corresponding auxiliary teaching platform, lacks research on how to apply the experimental auxiliary teaching platform. These can’t provide guidance to practical applications. It is necessary to further explore the role of software in the learning of hardware curriculum knowledge.Based on existing problems, we use the component technology in combination with the actual teaching requirements. The design and development of Principle of Computer Composition experiment teaching assistant platform based on MVC architecture. The platform supports the development of experimental teaching of computer composition in terms of curriculum information management, virtual experiment system, simulation program management and performance management. And the application method of the platform is discussed. The feasible schemes are proposed.2.Platform design2.1Platform functional designThe experimental teaching assistant platform of Principle of Computer Composition is aiming at teachers and students. Teachers mainly provide the information sharing, job correction, performance management and other functions. Students mainly provide virtual experiment, simulation program,report upload and other functions. It provides the function of interaction between teachers andFig. 1. Experiment teaching assistant platform functional structure(i) Resource sharingThe module is mainly open to teachers and students to share information. It includes teaching courseware, experimental instruction, experiment instruction, software use manual, notice of course related notice, etc. Teachers can achieve the resource directory management, resource upload and input, resource maintenance, resource access management, resource download and browsing.(ii) Student managementTeachers use the student management module to carry out the input, modification, deletion, batch data import and the function of student audit. Students use the student management module to implement the course selection. Only elective students can upload lab reports and statistics. It supports the standard Excel file data import in batch data import.(iii) Virtual experiment managementThe virtual experiment management is the biggest difference between the platform and other auxiliary teaching systems. It contains three sub-modules of the component library, virtual experiment, and implementation report management. The component library uses the component technology to provide some of the basic chips needed to complete the experiment. The virtual experiment project management mainly provides three experimental projects management which are the arithmetic logic operation unit, the static random memory reading and writing, and the simple model machine design. Students use the components in the component library to simulate the line operation by dragging and dropping the mouse to form functional components. The experiment report management realizes the upload, modification and the scoring function of experiment reports. Students must upload and modify lab reports within the time limit set by teachers. Results of the experiment report are as part of the grade management.(iv) Simulation program managementSince the course is involved in more complex principles, many principles are difficult to understand, so the platform introduces software simulation technology into the teaching of Principle of Computer Composition. It has been added the simulation program management module. Students adopt the software simulation technology to write the simulation of the hardware working mechanism. It is submitted to the platform through the program submission function. The platform automatically determines the correctness of the program and gives the results.(v) Performance managementThe student achievement mainly consists of the attendance, experiment report, simulation program, and virtual experiment. The attendance and test reports are manually entered by teachers according to the actual situation. Results of simulation programs and virtual experiments are automatically generated by the system. Teachers can set the weight of each achievement and makestatistical analysis of grades according to need, such as by item statistics. Results of the statistics are shown in tables or graphs and can export out Excel files.(vi) Q&AThe discussion module is mainly introduced to facilitate interaction between teachers and students. Students can choose to enter the topic by interest, conduct topic release, delete topics, and view topics. But students can only delete their own topics. Teachers can delete other people’s topics or top up some topics.(vii) System managementThe system management consists of three sub-functions of user management, permission management and data management. The data management implements data backup and recovery, as well as the logging management capabilities. The user management mainly realizes the management of user information, such as the user name, password, role, etc. The permission management enables all columns and functions to be specified. It has automatic and autonomic increase access function. The platform architectureThe Principle of Computer Composition experiment teaching auxiliary platform adopts the architecture shown in Fig. 2. It is divided into the data layer, the data access layer, the business logic processing layer, and the display layer, respectively corresponding to the three layers architecture of the MVC (Model View Controller). The data layer provides a variety of data to be processed by the platform. Date is stored in the form of database and file. The data access layer provides the interface to access data. Through the data access interface, the previous layer only needs to call these interfaces, the corresponding database operation can be completed for the data persistence operation; The business logic layer mainly implements the business logic processing of the platform, this layer accepts the request made by users and invokes the data access interface on request to obtain the data and returns the result data to the presentation layer. The display layer provides human-computer interaction to achieve the acceptance and results of user requests. To improve the reusability of the code, the platform provides reusable resources in the form of components, the display layer, business logic processing layer, and part of the data access layer are implemented by the component assembly,Data layer(databasesystem,file system)Fig.2. The platform architecture3.Application of platformIn order to test the experimental auxiliary teaching platform, we have applied it in the computer application students of the 2014 grade in computer science department and achieved good results. In practice, we mainly pay attention to the following aspects.(i) Materials of the lecture are all entered into the platform for students to view and download. In the experimental class, the traditional experimental box was used to record the students’ attendance and the completion of the experiment and give the results in a quantitative way. Students fill out the experiment report online, the teacher corrects the experiment report and gives the result.(ii)After class, students are required to enter the platform, combine the experiment in the internal experiment box, conduct the virtual experiment, and give the normal results according to the number and quality of the virtual experiment project.(iii) Students are required to use the software simulation technology to write the relevant working principles, and principles are submitted through the platform automatically, and the relevant results are generated.(iv) Encourage students in accordance with the platform component design specification, write their own related components, more tests and complete the project, such as the complex model design experiment, the pipeline design experiment and the vector processor.(v) To give full play to the function of platform answer discussion, the teacher participates in the discussion, actively guides the students to carry out the discussion on related issues, and strengthens the solution of the problem and the collision of new ideas.4.ConclusionIt is using the means of informatization to carry out the Principle of Computer Composition experiment auxiliary teaching. It breaks the time and space constraints that existed in previous teaching and fully inspires the students’ autonomous learning ability and creative thinking. The quality of curriculum teaching is improved effectively. At the same time, it also makes the examination of achievement more fair and reasonable. The next step is to extend the functionality of the platform, increase the subsystem of the question bank and the online test system and apply it into the theory course. The corresponding mobile app should be also developed to better play the role of auxiliary teaching.AcknowledgementThis paper is supported by Principles of Computer Organization high-quality curriculum construction project of Chengdu University of Information Technology, and the construction stage research achievements of the fifth batch of characteristic specialties of the Ministry of Education Computer Science and Technology (TS2488).References[1]Q. Y. Zhao, J. He, and L Wei, Discussion on the teaching mode of Computer Organization andArchitecture, Computer Knowledge and Technology, vol. 3, pp. 693-694, 2008.[2]J. X. Yang, The exploration and practice of computer composition principle experiment networkteaching, Laboratory Science, vol. 3, pp. 45-47, 2008[3]W. F. Zhang, J. Xiao, and H. Y. Liu, Design and implementation of virtual experiment system forcomputer composition principle, Research and Exploration in Laboratory, vol. 5, pp. 62-66, 2014.[4]H. Y. Zhang, Development of experimental simulation coursewares of principle of computerorganization, Modern Computer, vol. 6, pp. 157-160, 2010.[5]J. X. Wang, L. Y. Zhang, and Y. Sheng, Design and implementation of principles of computerorganization virtual lab based on component, Journal of System Simulation, vol. 9, pp.2469-2474, 2008.。
2022年职业考证-软考-系统架构设计师考试全真模拟全知识点汇编押题第五期(含答案)一.综合题(共15题)1.单选题进行系统监视通常有三种方式:一是通过(),如UNIX/Linux系统中的ps、last等;二是通过系统记录文件查阅系统在特定时间内的运行状态;三是集成命令、文件记录和可视化技术的监控工具,如()。
问题1选项A.系统命令B.系统调用C.系统接口D.系统功能问题2选项A.Windows 的netstatB.Linux 的iptablesC.Windows的PerfmonD.Linux 的top【答案】第1题:A第2题:C【解析】第1题:本题考查的是系统安全相关知识。
系统监视的目标是为了评估系统性能。
要监视系统性能,需要收集某个时间段内的3种不同类型的性能数据:(1)常规性能数据。
该信息可帮助识别短期趋势(如内存泄漏)。
经过一两个月的数据收集后,可以求出结果的平均值并用更紧凑的格式保存这些结果。
这种存档数据可帮助人们在业务增长时作出容量规划,并有助于在日后评估上述规划的效果。
(2)比较基准的性能数据。
该信息可帮助人们发现缓慢、历经长时间才发生的变化。
通过将系统的当前状态与历史记录数据相比较,可以排除系统问题并调整系统。
由于该信息只是定期收集的,所以不必对其进行压缩存储。
(3)服务水平报告数据。
该信息可帮助人们确保系统能满足一定的服务或性能水平,也可能会将该信息提供给并不是性能分析人员的决策者。
收集和维护该数据的频率取决于特定的业务需要。
进行系统监视通常有 3 种方式。
一是通过系统本身提供的命令,如 UNIX/Liunx 中的 w、ps、last,Windows 中的 netstat 等,第一空选择A选项。
二是通过系统记录文件查阅系统在特定时间内的运行状态;三是集成命令、文件记录和可视化技术,提供直观的界面,操作人员只需要进行一些可视化的设置,而不需要记忆繁杂的命令行参数,即可完成监视操作,如Windows的Perfmon 应用程序。
1INTRODUCTION1.1Current problemsAs the reducing of the fossil energy, the living environment is going worse, clean energy and renewable energy are taken more and more attention. In the process, wind power has been developed as the fourth power energy source after thermal power, hydropower and nuclear power, in developed countries. The daily work of wind turbines service enterprises is mainly around the service projects management. The project schedule, staff efficiency and cost control are directly related to the enterprise operation level. The enterprise exists or not is depended on what kind of information system used by service project management.1.2The current situation of the projectmanagement system developmentMicrosoft Office Project supports simple graphics and images which can suit general projects in many areas. But the use of it seriously limited in the mobile internet era. Based on the B/S structure, Oracle Primavera P6 created by Primavera System inc integrates project plan, schedule and resource, used in many large or mega construction projects. But because of versatility and limitedness of project schedule and resource management, it shows lack of functional requirements in the enterprise operation management. 1.3PurposesBase on the actual investigation of service project management mode and business process in the wind turbines service corporation, and using of ODPS platform, to design a service project management which can realize the information, automation standardization and reflect enterprise operation status constantly. And it can provide basis for decision making through the multi-information management system platform.2THE FRAMEWORK OF THE SYSTEM2.1The whole descriptionThe system designed in this paper is based on the data of projects, staff and material inventory. The system regards service projects as the core; regards services management, the support for decisions and services to staff as specific targets. The service project management system integrates human resource management, project management, warehouse management, technical documents and data management, information sharing platform as a unit. It is a highly collaborative system, business management information system and intelligent decision system. Through the rapid exchange and integration of various technologies and business data, so as to achieve projects management, projects business regulation and other business automation and standardization, to promote management tools and methods; to integrate with OA, ORACLE ERP,The Design and Application of Service Project Management System Based on ODPS PlatformWentao Zhu & Qiang YuDepartment of Management, Hebei University, Baoding, Hebei, ChinaJianli YangDepartment of Electronic and Information Engineering, Hebei University, Baoding, Hebei, China*******************,***************.cn,***********************ABSTRACT: Because of ineffective management, it appears schedule delay, materials supply not in time, cost overruns, human resource management confusion, security management and quality management activities carried out in disorder during the process of wind turbines service projects at this time. The paper designs an advanced service project management system based on ODPS platform which can be integrated with other systems in order to standardize the management of wind turbines service project management, realize the scientific process of information and automation, and enhance the competitiveness of wind turbines service enterprises.KEYWORD: ODPS Platform; Wind Turbine; Service Project Management SystemInternational Conference on Social Science, Education Management and Sports Education (SSEMSE 2015)© 2015. The authors - Published by Atlantis Press920financial and other systems.2.2Association frameworkThrough the transmission medium such as optical fiber, cable networks, wireless networks to construct a comprehensive project management system, which regards projects management as core business, project tasks as main line and connects the relevant business. It can be accessed by computers, smart phones and other devices. System associated frame schematic is shown below:Figure -1 Associated framework diagramService project management system is a self management system and closely relates with the financial system, the OA office automation system,ERP system, SCADA system, BI system and othersystems. It’s the core business management systemfor wind turbines service enterprises.2.3System designThis system adopts "5-layers&3-system" designpattern. 5 layers are IT infrastructure layer,presentation layer, application layer, applicationsupport layer and information resource layer. 3systems are information standardization system,security system and operation management system.In order to realize the construction scheduled targets,using the design idea of platform and modular;relying on unified data exchange, unified interfacestandard, and unified security uniform. As shownbelow:Standard SystemIT InfrastructurePDADisp la yT erminaT elep honeF a xMob ilePhonesystemFigure -2 Service project management system design pattern diagram9212.3.1The description of system hierarchy designIT Infrastructure Layer provides the basis environment for system operation, including three parts, network communication, host storage, and system software. The network section includes VPN, internet and so on. Host storage section includes host, storage, backup recovery and other integrated facilities. System software includes operating systems, database software.Presentation layer is responsible for interacting with the user, accepting service requests, integrating application, sharing resource retrieval, publishing information, and other functions. The content in this layer is shown in the form of a comprehensive portal, through the browser usually. Visitors can log one time into multiple systems, which is flexible business processes and integration, through computer, PDA, or cell phone. This layer can realize flexible collocation and integration of business processes.Application layer is based on framework, platform, services and tools supported by application support layer. Database access layer provides its data resources. Application layer build business applications for all kinds of users of the system, such as project management, human resource management, warehouse management, security management, quality management, device management, knowledge management, portal systems and so on.Application support layer is a development architecture built over the under layer hardware and software, with componentized software platform; in order to achieve seamless integration of systems management and business applications, to realize business applications developed customized and managed configurable. The coding of business development is reduced greatly. The flexibility and reusability of system application is increasing. Application support layer Includes workflows, rights management, resource directory services, report management, messaging services, system maintenance and other components. It can provide support for the upper application system.Information resource layer is mainly all kinds of business information processing. Information resource library, total of four databases, includes warehouse database, project management database, human resource management database, knowledge database.2.3.2Support systems descriptionTo ensure the system can be used widely and operating stable only depends on application development and network construction is not enough. It also needs common supports from three different sides: security, standardization, operation and maintenance. Support system includes threeparts. They are information technology standards system, safety guarantee system, operation management systemInformation technology standard system is referring to advanced experience of the implementation of e-government and regarding its national standard system as framework. Information technology standard system includes appropriate national and international standards, operation and maintenance debugging norms, standards of computer technology, communications and networking technologies standards. The most important thing is combination with the standard specifications of information systems in use.Safety guarantee system consists of network security platform, application security platform and system security platform. Network security platform provides security controls of access to information, trust services, basic security protections, failback and disaster recovery services, etc. Application security platform including authentication, access control, data security, system logs, mainly to provide a unified user management services, namely, provide a unified user management, role management, authorization, certification, etc. System security platform includes the operating system security, server security, anti-virus system and so on.Operation management system includes operation and maintenance management, storage backup management, operation problems management. It means operation, maintenance, support and training system, run through the whole process of the system from designing to running, providing a good operation and maintenance support functions and improving the real-time dynamic documents services.3FUNCTION REALIZATION3.1The description of ODPS development platformThe service project management system designed in this paper is entirely based on the ODPS platform.ODPS named Open Document Processing System is an operational framework with advanced concept through abstraction of business functions in numerous projects practice. It’s also a technical framework, coming from techniques accumulation, which has developed numerous products. ODPS includes workflow technology, form processors, document processors, document type systems, and other related development tools.ODPS running framework of application support platform is divided into four layers, they are: presentation layer, request service layer, business layer and resource access layer.Presentation layer framework designed in full compliance with the MVC model. The controller is used to separate model and view, to achieve the 922effect of loose coupling between layers; and to increase flexibility, reusability and maintainability. In the Web framework, we mainly use JSP, JavaBeans, Taglib, XML and Servlet technologies, etc in J2EE, combined with a variety of classic design mode, the main Web application development technology integrated into a unified framework. Developers do not have to use their own coding to achieve a full development of its MVC mode, which greatly saves time.Request service layer playing pivot roles, it is responsible for connecting the presentation layer and business layer, and is responsible for converting data between two levels, transferring data and so on. This layer includes business delegate, facade, and data transfer object modules; and is completely transparent to the system developers. In other words, developers do not need to focus on how the client's data package, but also do not care about how to access the business logic layer. They only need to master the methods of how to call business objects needed by business domain layer on request service layer.Business layer is mainly composed of process controls, filters, business proxy objects, business objects, preservation state, resource control and transaction control module. For developers, they need to develop filter and business object, can also selectively use business proxy object. For the unrelated business logic operation of resource management, transaction management and routing control, developers need only a simple configuration via the configuration file without writing a line of code. The system will take on the management of affairs and resources automatically according to the configuration files written by developers.For resource access layer, in order to separate persistent storage and business logic completely, the base running framework adopted standard model of DAO. Resource access layer also provides a variety of data access layer DAO implementations, including databases, LDAP, and other file systems. So that developers can stay focus on business logic while developing, without the need of considering the database and LDAP structure.ODPS platform is based on open standards J2EE technology route, cross-platform applications, insisting loosely coupled design principles, using a large number of middleware and AJXA technologies. While using the CA identity authentication technology, rights management, configuration services and a variety of applications security services, to protect the security of application system.3.2Function ModulesService project system overall functions design as shown below:Figure -3 Functions design diagramProject Management: Under the limited conditions, using the systems integration methods to manage all of the work involved effectively. Mainly contents 5 processes, project planning process, project control process, project execution process, project closure process.Warehouse Management: The system satisfied the needs of business warehouse management from production, support multi-party system information exchange, easy to expand value-added services, support multi-warehouse and multi-project management. It is mainly divided into 6 parts: basic data management, entering-warehouse management, out-of-warehouse management, stock management, statistical analysis, operational monitoring and analysis.Human Resource Management: the system can achieve the personnel fingerprint attendance, travel tracking, position management, file management, allowance calculation, human resource planning and deployment, work analysis and other functions.Knowledge Management: The system establishing enterprise knowledge documentation center and customer service knowledge base. It can realize knowledge planning, knowledge tracking, knowledge map, mutual help knowledge, knowledge evaluation and so on. At the same time, supports documentation sub-libraries, assign permissions, document encryption, publishing approval process, supports standard document formats and Office online editing, and other functions.Device Management: The system provides the amount of stock decision for the storage manager, through records of each wind turbine parts information, geographic information, delivery time.Through the docking of SCADA system owned by each turbine, constantly monitor all wind power turbines operation state, the key parts operation state and generating capacity, to achieve wind turbines’scientific management of daily inspection and maintenance, regular maintenance of the key parts.Security Management: All project departments can record dangerous source in the system, and share it to the whole company. We can record in the system such as project security basic information, the implementation of security measures, inspection 923and rectification, violations and penalties, regular safety training and implementation, collection and disposal of wastes, suggestions and summary information. Company level monthly reports will be automatically produced for managers’ decisions, through pooled analysis of all of this information via the system.Quality management: The system realizes functions of inspection records of important tools and measuring tools, and automatically alerts the operators the next inspection date. The system records failure information of wind turbines, such as, time, location, cause, treatment methods, the responsible person, damaged parts and other information. It can generate fault history records, and the automatic identify batches problems after pooled analysis. We can analysis and evaluate the effect of quality work monthly completed after comparison with annual quality objectives pre-set through the system.3.3 System deploymentThe overall operating environment of integrated application software mainly involves three types of servers: database server, integrated application server,file server. Specifically, as shown below:Database Server Tape LibraryDisk ArrayFile ServerApplication ServerFigure -4 System deployment diagram4 CONCLUSIONThis paper analyzes characteristics of wind power turbines service industry business; using ODPS development platform, completes the design and development work for wind power turbines the service project management system. This system has made outstanding contributions in the management decision, leading the innovation management mode, and enhancing enterprises competitiveness. After promoting the use of certain enterprises shows that the system has a strong practical able to realize flexible customization and modifications many elements of project management, which can be carried out with other management information systems convergence and effective transfer and sharing of data, the system fully functional, cover all stages of project management. Enterprises make the system can concentrate business, standardize management, improve efficiency, and at the same time reduce office costs. REFERENCES[1] Kongdecai. “Design and Implementation of ProjectManagement System Based o n Critical Chain Technology”. Enterprise Management . ShenYangLigong University. 2012.[2] Wangyong,Zhangbin. PMBOK Guide (Version 4).Publishing House of Electronics Industry.2009.[3] Liuxuejin,Yuzhiwei. ”The project management method inthe application of scient ific research project management”. Science and technology information . 2009 NO.24.[4] Qinanbang. Project management: a new perspective ofmanagement (Version 7). China Renmin University Press. 2011.[5] Sunjian.”Design and Implementation of the ProjectManagement System”. Department of Computer Science and Technology , Jilin University, 2013.924。
DDR4 System memory SAS / RAID Controller ODD Optical Disk Drives HDD Hard Disk Drives SSD Solid State Drives LAN LAN ComponentsFC Fibre Channel Controller IB Infiniband Controllers OMNI OMNI Path ControllersPSU Power supply unit, power cableUSB iRMC, eLCM, Cool-safe, TPM, Region Kits Others15Accessories121110138614579RAID Base UnitCPU2Rack Rack Architecture PRIMERGY RX4770 M44-way / 2U Rack Server3Chapter 14Folder Base Content CPU RAM<-- order code E-part (bold) -- <-- order code L-part (bold)<-- "name" of this part<--description of this part, in same cases as well description of content <--requires a free PCIe slot --> means total amount of PCIe slots reduced <--indicates how often this part can be configured in the related ServerFor further information see:Link to datasheet:http:// xxxFujitsu is providing the content of this document with very high accuracy. In case you identify a mistake, we would kindly encourage you to inform us. We kindly ask for understanding, that errors still may occur and that Fujitsu may change this document without noticeText fields with grey color offer extra information for related topics (e.g prerequesites, technical back ground, configuration rules, limitations, …Configuration diagram PRIMERGY RX4770 M4PCIe slot restrictions on high TDP CPUs used in Performance base unit:If CPUs > 165W TDP are in use PCI slot 1 & 2 cannot be equipped with PCI cards (needed for improved air flow) This configuration is also reduced if on slot 3 and 6 a PCI card with 75W is in use!Only 2 PCI slots out of 4 (4, 5, 7, 8) are available then.PCIe slot restrictions while using liquid cooled base unit:While using liquid cooled base unit PCI slot 5, 6 & 7 are occupied.RX4770 M4 Back viewConfiguration diagram PRIMERGY RX4770 M4Key:Light colored slots are use able with Light colored CPUs Dark colored slots are use able with dark colored CPUsDynamic LoM OCP PHY interface (recommended)2x 1x 1x 1xDDR4 DIMM Order (according CPUs installed)2x Processor2x …..Memory Mode installationRegion kit APAC/EMEA/India or other iRMC S5 advanced pack (recommended)min. components for RX4770 M4#Base Unit (includes 2x PSU)1x Device use ability:Slot Number# 2 2.5" SAS # 3 2.5" SAS 2.5" PCIe # 15 2.5" SAS # 9 2.5" SAS 2.5" PCIe # 10 2.5" SAS 2.5" PCIe # 11# 6 2.5" SAS 2.5" PCIe Video USBOperating PanelUSB devices / optical devices (IV)# 7 2.5" SAS 2.5" PCIe # 8# 1 2.5" SAS # 5 2.5" SAS 2.5" PCIe 2.5" PCIe SAS/PCIe - HDD/SSD slots ( V )2.5" SAS # 4 2.5" SAS 2.5" PCIe F R O N T V I E W# 0 2.5" SAS USB5.25"x 0.5" bay for DVD/Blu-rayCPU#4#3#22.5" SAS 2.5" PCIe# 12 2.5" SAS 2.5" PCIe # 13 2.5" SAS 2.5" PCIe # 14 2.5" SAS 2.5" PCIeRX4770 M4 ArchitectureIntelC624ChipsetRX4770 M4 Processor Information's and RulesTwo CPU must be configured as minimum, maximum 4 CPU´s are possible too.Memory area defined to not used CPU slots are not use able too.Only 2 CPU or 4 CPU configurations are allowed, only same version, no mix!Later upgrading to a 4 processor system is also possible, but may require adding Memory modules. RX4770 M4 Memory Information's and RulesRAS Features defined by Intel POR are required!Subject to change by Intel POR!RAS (Reliability, Availability, Serviceability)Reliability- System attributes to ensure Data integrity.- capability to prevent, detect, correct and contain faults over a given time interval.Availability- System attributes to help stay operational in the presence of faults in the system.- Capability to map out failed units, ability to operate in a degraded mode.Serviceability- System attributes to help system service, repair.- Capability to identify failed units, and facilitates repair.Elements of RAS1.Fault Avoidance2.Fault Detection3.Fault Correction/Recovery4.Failure Identification and reconfigurationSkylakeScalable Processor:Intel® Run Sure Technology FeaturesResilient System Technologiesintegrateprocessor,firmware,andsoftwarelayersthatallowthesystemtodiagnoseand/orrecoverfrompreviouslyfatalerrors •Advanced Error Detection and Correction (AEDC)•MCA 2.0 Recovery (as per eMCAgen2 architecture)•MCA Recovery-Execution Path•MCA Recovery-Non Execution Path•Local Machine Check (LMCE) based recoveryResilient Memory Technologiesensuredataintegrity&enablesystemstokeeprunningreliablyoveralongerperiodoftime,reducingthefrequencyofservicecalls •SDDC + 1, Adaptive DDDC (MR) +1•Addressed range/Partial Memory MirroringIntel®Run Sure TechnologyDesigned to Reduce the Frequency & Cost of DowntimeError Prevention- Quality Assurance- Hardened circuits- Thermal controlsError Detection / Correction- Parity / CRC- Error correctionError Isolation / Recovery- Error Containment- Redundancy Failover- Self-Healing ModesSoftware Assisted Recovery- Integrated OS / VMM/ DBMS recoveryrequiredrequired if 2nd CPUBank Iis configuredBank IIoptional, same type in Bank per CPU optional, any typerequiredrequired if 2nd CPU Bank I is configured Bank II optional, same type in Channel per CPU optional, any typerequiredrequired if 2nd CPU Bank I Spare Spare Spare Spare Spare Spare R1Spare Spare Spare Spare Spare Spare is configured (black)Data Data Data Data Data Data R2Data Data Data Data Data Data optional, same type Bank II Data Data Data Data Data Data R1Data Data Data Data Data Data in Channel per CPU (blue)DataDataDataDataDataDataR2DataDataDataDataDataDataoptional, any typeC h a n n e l DC h a n n e l EC h a n n e l LC h a n n e l M1st XEON CPU (4 - 28 Core)C h a n n e l AC h a n n e l BC h a n n e l CC h a n n e l DC h a n n e l EC h a n n e l FC h a n n e l GC h a n n e l HC h a n n e l JC h a n n e l KC h a n n e l LC h a n n e l MC h a n n e l GC h a n n e l HC h a n n e l JC h a n n e l KC h a n n e l AC h a n n e l BC h a n n e l CC h a n n e l DC h a n n e l EC h a n n e l F2nd XEON CPU (4 - 28 Core)C h a n n e l JC h a n n e l KC h a n n e l AC h a n n e l BC h a n n e l CC h a n n e l LC h a n n e l MC h a n n e l FC h a n n e l GC h a n n e l Hrequiredrequired if 2nd CPU Bank IR1is configured (black)R2R3optional, same typeR4in Channel per CPUBank II R1optional, any type(blue)R2R3R4requiredrequired if 2nd CPU Bank I is configured Bank II optional, same type in Bank per CPU optional, any typerequiredrequired if 2nd CPU Bank I is configured Bank II optional, same type in Bank per CPU optional, any typerequiredrequired if 2nd CPU Bank I is configured Bank II optional, same type in Bank per CPU optional, any typeC h a n n e l LC h a n n e l MC h a n n e l CC h a n n e l DC h a n n e l AC h a n n e l BC h a n n e l EC h a n n e l FC h a n n e l GC h a n n e l HC h a n n e l JC h a n n e l KC h a n n e l AC h a n n e l BC h a n n e l CC h a n n e l DC h a n n e l EC h a n n e l FC h a n n e l GC h a n n e l HC h a n n e l JC h a n n e l KC h a n n e l LC h a n n e l Ma n n e l Aa n n e l Ba n n e l Ca n n e l Da n n e l Ea n n e l Fa n n e l Ga n n e l Ha n n e l Ja n n e l Ka n n e l La n n e l MMirrored Channel Mode (2 DIMMs per CPU) requires identical modules on channel A & B (1st CPU) or channel G & H (2nd CPU) 50% of the capacity is used for the mirror => the available memory for applications is only half of the installed memory. If this mode is used, a multiple of 2 identical modules has to be ordered.e l Ae l Be l Ce l De l Ee l Fn e l Ge l Hn e l Jn e l Kn e l Le l MMirrored Channel Mode (3 DIMMs per CPU) requires identical modules on channel A, B & C (1st CPU) or channel G, H & J (2nd CPU) 50% of the capacity is used for the mirror => the available memory for applications is only half of the installed memory. If this mode is used, a multiple of 3 identical modules has to be ordered.requiredrequired if 2nd CPU Bank I Data Mirror Data Data Mirror Data Data Mirror Data Data Mirror Data is configured (black sockets)Bank II Data DataDataDataDataDataDataDataDataDataDataDataoptional, same type (blue sockets)in Bank per CPU optional, any typerequiredrequired if 2nd CPU Bank I D/M D/M D/M D/M D/M D/M D/M D/M D/M D/M D/M D/M is configured (black sockets)Bank II Data MirrorDataMirrorDataMirrorDataMirrorDataMirrorDataMirroroptional, same type (blue sockets)in Bank per CPU optional, any type4Socket Purley Platform; CPU, Memory and AEP Configuration ExampleDDR4 DIMMsDDR4/Apache Pass OptionalPCIe* uplink connection for Intel® QuickAssistTechnology and Intel® EthernetExample DIMM population shown; please look up Apache Pass customer collateral for specific rules on **DDR4/Apache Pass DIMM populationsMirror Channel Mode (4 DIMMS per CPU)C h a n n e l AC h a n n e l Bh a n n e l CC h a n n e l DC h a n n e l Eh a n n e l FC h a n n e l GC h a n n e l Hh a n n e l JC h a n n e l Kh a n n e l LC h a n n e l M1st XEON CPU (4 - 28 Core)2nd XEON CPU (4 - 28 Core)Mirrored Channel Mode requires identical modules on channel A, B, C, D, E, F (1st CPU) or channel G, H, J, K, L and M (2nd CPU) 50% of the capacity is used for the mirror => the available memory for applications is only half of the installed memory. If this mode is used, a multiple of 6 identical modules has to be ordered.1st XEON CPU (4 - 28 Core)2nd XEON CPU (4 - 28 Core)Mirrored Channel Mode (4 DIMMs per CPU) requires identical modules on channel A, B, D & E (1st CPU) or channel G, H, K & L (2nd CPU) 50% of the capacity is used for the mirror => the available memory for applications is only half of the installed memory. If this mode is used, a multiple of 4 identical modules has to be ordered.Mirror Channel Mode (6 DIMMS per CPU)C h a n e l AC h a n e l BC h a n e l CC h a n e l DC h a n e l EC h a n e l FC h a n e l GC h a n e l HC h a n n e l JC h a n e l KC h a n e l LC h a n e l MPRIMERGY RX2530 M1System configurator andorder information guideEdition 30th of November 2015PRIMERGY RX4770 M4System configurator and order information guide Edition31st of August 2016Chapter 6 - Optical Disk DrivesS26361-F3778-E1S26361-F3641-E6S26361-F3718-E2FS26361-F3778-L1S26361-F3641-L6S26361-F3718-L2DVD-RW supermulti ultra slim Blu-ray Triple Writer ultra slim DVD-ROMmax. 1x per systemmax. 1x per systemmax. 1x per systemGall formats, DUAL/DL, DVD-RAM only W2K, W3K and Linux 6x BD-RW, 8x DVD, 24x CD,BD DL and all CD/DVD formats 16x DVD; 48x CD-ROM Test and release for Japan only 9.5mm, black bezel 9.5mm, black bezel 9.5mm black bezelPRIMERGY RX4770 M4System configurator and order information guide Edition31st of August 2016The HDDs not released with PRAID EP5x0i (S26361-F4042-E204/E208)900GB15 000SAS 12Gb/s 512n S26361-F5531-E590S26361-F5531-L5901.2TB10 000SAS 12Gb/s 512n SEDS26361-F5581-E112S26361-F5581-L112300GB10 000SAS 12Gb/s 512n SED S26361-F5581-E130S26361-F5581-L130600GB10 000SAS 12Gb/s 1.2TB10 000SAS 12Gb/s 512e S26361-F5543-E112S26361-F5543-L1121.8TB10 000SAS 12Gb/s 512e S26361-F5543-E118S26361-F5543-L118512n SED S26361-F5581-E160S26361-F5581-L160max. 8/16x - depending on base unit & configurationCapacity RPMInterface Sector order code E-part order code L-part 1TB7 200SATA 6Gb/s 512e S26361-F3907-E100S26361-F3907-L100max. 8/16x - depending on base unit & configurationHDD SATA 2.5" 7.2K 512e (SFF) Enterprise Business Critical with hot plug/hot replace tray2TB7 200SATA 6Gb/s 512e S26361-F3907-E200S26361-F3907-L2001TB7 200SATA 6Gb/s 512n S26361-F3956-E100S26361-F3956-L1002TB7 200SATA 6Gb/s 512n S26361-F3956-E200S26361-F3956-L200max. 8/16x - depending on base unit & configurationHDD SATA 2.5" 7.2K 512n (SFF) Enterprise Business Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part 1TB7 200SAS 12Gb/s 512e S26361-F5573-E100S26361-F5573-L1002TB7 200SAS 12Gb/s 512e S26361-F5573-E200S26361-F5573-L200max. 8/16x - depending on base unit & configurationHDD SAS 2.5" 7.2K 512e (SFF) Enterprise Business Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part 1TB7 200SAS 12Gb/s 512n S26361-F5600-E100S26361-F5600-L1002TB7 200SAS 12Gb/s 512n S26361-F5600-E200S26361-F5600-L200max. 8/16x - depending on base unit & configurationHDD SAS 2.5" 7.2K 512n (SFF) Enterprise Business Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part 600GB10 000SAS 12Gb/s 512e S26361-F5543-E160S26361-F5543-L160900GB10 000SAS 12Gb/s 512e S26361-F5543-E190S26361-F5543-L190max. 8/16x - depending on base unit & configurationHDD SAS 2.5" 10K 512e (SFF) Enterprise Mission Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part 900GB10 000SAS 12Gb/s 512n S26361-F5550-E190S26361-F5550-L1901.2TB10 000SAS 12Gb/s 512n S26361-F5550-E112S26361-F5550-L112300GB10 000SAS 12Gb/s 512n S26361-F5550-E130S26361-F5550-L130600GB10 000SAS 12Gb/s 512n S26361-F5550-E160S26361-F5550-L160max. 8/16x - depending on base unit & configurationHDD SAS 2.5" 10K 512n (SFF) Enterprise Mission Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part S26361-F5531-E545S26361-F5531-L545600GB15 000SAS 12Gb/s 512n S26361-F5531-E560S26361-F5531-L560GChapter 7 - Hard Disk DrivesH2.5" (SFF) Hard drivesHDD SAS 2.5" 15K (SFF) Enterprise Mission Critical with hot plug/hot replace trayCapacity RPMInterface Sector order code E-part order code L-part 300GB15 000SAS 12Gb/s 512n S26361-F5531-E530S26361-F5531-L530450GB15 000SAS 12Gb/s 512n 512e S26361-F5543-E124S26361-F5543-L1242.4TB10 000SAS 12Gb/s 512e SEDS26361-F5582-E124S26361-F5582-L1241.8TB10 000SAS 12Gb/s 512e SED S26361-F5582-E118S26361-F5582-L1182.4TB10 000SAS 12Gb/s SAS drives and SATA drives can be mixed, but cannot be used in one logical RAID volume.SAS & SATA drives require a dedicated SAS or RAID Controller Hard Disk Sector Format Information:512n HDD: 512 byte sectors on the drive media.512e (e=emulation) HDD: 4K physical sectors on the drive media with 512 byte logical configuration.512e HDD Disk Drives: VMware 6.0 or earlier is not supported.SED (=Self Encrypting Drives) require ether a RAID controller with ®SafeStore (SED) support or an HBA and in addition a software instance, supporting SED Key Management.It is strongly recommended to order SafeStore (SED) RAID controller with SED HDD or SSD devices for SafeStore (SED) functionality.HDD Classes:Business-Critical (BC) -SATA=Nearline SATA Enterprise Drives / 7.2Krpm,SATA 6G.Business-Critical (BC) -SAS=Nearline SAS Enterprise Drives / 7.2Krpm,SAS 12G.Mission-Critical (MC)=SAS 10K and SAS 15K Enterprise Drives with max. performance and reliability.PRIMERGY RX4770 M4System configurator andorder information guideEdition 31st of August 2016S26361-F1452-E140REGION KIT Europe1x per systemS26361-F1452-E110REGION KIT JPFor Shipments to Japan regions 1x per systemmax. 1x per systemUse according to import restrictions Your Server is readyS26361-F1452-E100REGION KIT APAC/America/EMEA/India For Shipments to Asia pacific, America, EMEA or India regions 1x per systemS26361-F3552-E101TPM 1.2 Module SPITrusted Platform Module on Motherboard Use according to import restrictions max. 1x per systemS26361-F3552-E100S26361-F3552-L100TPM 2.0 Module SPITrusted Platform Module on Motherboard PWith our made4you service we fulfill any individual requirement and wish of our customers perfectly -e.g.> special hardware configurations,> staging services ex factory,> extended lifecycle management,> customer specific logos, component,> BIOS fixes and many more.For further information please contact us *******************************.com.Fujitsu PortfolioBuild on industry standards, Fujitsu offers a full portfolio of IT hardware and software products, services, solutions and cloud offering, ranging from clients to datacenter solutions and includes the broad stack of Business Solutions, as well as the full stack of Cloud offering. This allows customers to leverage fromalternative sourcing and delivery models to increase their business agility and to improve their IT operation’s reliability.You would like to add some customer specific solutions?PRIMERGY RX4770 M4System configurator and order information guide Edition31st of August 2016/fts/products/computing/peripheral/accessories/index-facts.htmlChapter 15 - AccessoriesMouse M520 Grey S26381-K467-E101S26381-K467-L101Mouse M530 Black USB Mouse:Mouse M520 Black S26381-K467-E100S26381-K467-L100n/a S26381-K468-L100Mouse M530 Greyn/aS26381-K468-L101S26391-F6048-L364ADATA USB 3.0 Flash Stick UE700 – 32GB S26391-F6048-L332ADATA USB 3.0 Flash Stick UE700 – 64GBUSB sticks (FOR PROJECTS ONLY) - no standard release USB Keyboards for Tower Servers for following countries:USB professional Keyboard KBPC PX ECO Country version FUJITSU Keyboard KB521 USB (grey)US/ int 105 keys (UK keyboard + US int. Layout)S26381-K521-E102S26381-K341-E104Czech/SlovakS26381-K521-E104S26381-K341-E110US 104 keys (US keyboard + US layout)S26381-K521-E110S26381-K341-E120Germany S26381-K521-E120S26381-K341-E122Germany / Int S26381-K521-E122S26381-K341-E140France S26381-K521-E140S26381-K341-E154Sweden / Finland S26381-K521-E154S26381-K341-E165United Kingdom S26381-K521-E165S26381-K341-E170Switzerland S26381-K521-E170S26381-K341-E180Spain S26381-K521-E180S26381-K341-E185ItalyS26381-K521-E185USB Optical Disc DriveExternal Ultra Slim Portable DVD Writer (HitachS26341-F103-L142Please find the layout of all Fujitsu keyboards here: /PRIMERGY RX4770 M4System configurator and order information guide Edition31st of August 2016Chapter 6 - ODD optical disk drivesFConfig with 1x 9.5mm bayS26361-F3778-E1S26361-F3641-E6S26361-F3718-E2S26361-F3778-L1S26361-F3641-L6S26361-F3718-L2DVD-RW supermulti ultra slim Blu-ray Triple Writer ultra slim DVD-ROMmax. 1x per systemmax. 1x per systemmax. 1x per systemGall formats, DUAL/DL, DVD-RAM only W2K, W3K and Linux 6x BD-RW, 8x DVD, 24x CD,BD DL and all CD/DVD formats 16x DVD; 48x CD-ROM Test and release for Japan only 9.5mm, black bezel 9.5mm, black bezel 9.5mm black bezel The base units with 12x 3.5" or 24x 2.5" HDD do not offer 1x 9.5mm optical drive bay!。
AcceptanceTesting--可接受性测试一般由用户/客户进行的确认是否可以接受一个产品的验证性测试;actualoutcome--实际结果被测对象在特定的条件下实际产生的结果;AdHocTesting--随机测试测试人员通过随机的尝试系统的功能,试图使系统中断;algorithm--算法一个定义好的有限规则集,用于在有限步骤内解决一个问题;2执行一个特定任务的任何操作序列; algorithmanalysis--算法分析一个软件的验证确认任务,用于保证选择的算法是正确的、合适的和稳定的,并且满足所有精确性、规模和时间方面的要求;AlphaTesting--Alpha测试由选定的用户进行的产品早期性测试;这个测试一般在可控制的环境下进行的;analysis--分析分解到一些原子部分或基本原则,以便确定整体的特性;2一个推理的过程,显示一个特定的结果是假设前提的结果;3一个问题的方法研究,并且问题被分解为一些小的相关单元作进一步详细研究; anomaly--异常在文档或软件操作中观察到的任何与期望违背的结果;applicationsoftware--应用软件满足特定需要的软件;architecture--构架一个系统或组件的组织结构;ASQ--自动化软件质量AutomatedSoftwareQuality使用软件工具来提高软件的质量;assertion--断言指定一个程序必须已经存在的状态的一个逻辑表达式,或者一组程序变量在程序执行期间的某个点上必须满足的条件;assertionchecking--断言检查用户在程序中嵌入的断言的检查;audit--审计一个或一组工作产品的独立检查以评价与规格、标准、契约或其它准则的符合程度;audittrail--审计跟踪系统审计活动的一个时间记录;AutomatedTesting--自动化测试使用自动化测试工具来进行测试,这类测试一般不需要人干预,通常在GUI、性能等测试中用得较多;Backus-NaurForm--BNF范式一种分析语言,用于形式化描述语言的语法baseline--基线一个已经被正式评审和批准的规格或产品,它作为进一步开发的一个基础,并且必须通过正式的变更流程来变更;BasicBlock--基本块一个或多个顺序的可执行语句块,不包含任何分支语句;basistestset--基本测试集根据代码逻辑引出来的一个测试用例集合,它保证能获得100%的分支覆盖;behaviour--行为对于一个系统的一个函数的输入和预置条件组合以及需要的反应;一个函数的所有规格包含一个或多个行为;benchmark--标杆/指标/基准一个标准,根据该标准可以进行度量或比较;BetaTesting--Beta测试在客户场地,由客户进行的对产品预发布版本的测试;这个测试一般是不可控的big-bangtesting--大锤测试/一次性集成测试非渐增式集成测试的一种策略,测试的时候把所有系统的组件一次性组合成系统进行测试; BlackBoxTesting--黑盒测试根据软件的规格对软件进行的测试,这类测试不考虑软件内部的运作原理,因此软件对用户来说就像一个黑盒子;bottom-uptesting--由低向上测试渐增式集成测试的一种,其策略是先测试底层的组件,然后逐步加入较高层次的组件进行测试,直到系统所有组件都加入到系统;boundaryvalue--边界值一个输入或输出值,它处在等价类的边界上;boundaryvaluecoverage--边界值覆盖通过测试用例,测试组件等价类的所有边界值;boundaryvaluetesting--边界值测试通过边界值分析方法来生成测试用例的一种测试策略;BoundryValueAnalysis--边界值分析该分析一般与等价类一起使用;经验认为软件的错误经常在输入的边界上产生,因此边界值分析就是分析软件输入边界的一种方法branch--分支在组件中,控制从任何语句到其它任何非直接后续语句的一个条件转换,或者是一个无条件转换; branchcondition--分支条件branchconditioncombinationcoverage--分支条件组合覆盖在每个判定中所有分支条件结果组合被测试用例覆盖到的百分比; branchconditioncombinationtesting--分支条件组合测试通过执行分支条件结果组合来设计测试用例的一种方法;branchconditioncoverage--分支条件覆盖每个判定中分支条件结果被测试用例覆盖到的百分比;branchconditiontesting--分支条件测试通过执行分支条件结果来设计测试用例的一种方法;branchcoverage--分支覆盖通过测试执行到的分支的百分比;branchoutcome--分支结果见判定结果decisionoutcomebranchpoint--分支点见判定decisionbranchtesting--分支测试通过执行分支结果来设计测试用例的一种方法;BreadthTesting--广度测试在测试中测试一个产品的所有功能,但是不测试更细节的特性;bug--缺陷capture/playbacktool--捕获/回放工具参考capture/replaytoolCapture/ReplayTool--捕获/回放工具一种测试工具,能够捕获在测试过程中传递给软件的输入,并且能够在以后的时间中,重复这个执行的过程;这类工具一般在GUI测试中用的较多;CASE--计算机辅助软件工程computeraidedsoftwareengineering用于支持软件开发的一个自动化系统;CAST--计算机辅助测试在测试过程中使用计算机软件工具进行辅助的测试;cause-effectgraph--因果图一个图形,用来表示输入原因与结果之间的关系,可以被用来设计测试用例certification--证明一个过程,用于确定一个系统或组件与特定的需求相一致;changecontrol--变更控制一个用于计算机系统或系统数据修改的过程,该过程是质量保证程序的一个关键子集,需要被明确的描述;codeaudit--代码审计由一个人、组或工具对源代码进行的一个独立的评审,以验证其与设计规格、程序标准的一致性;正确性和有效性也会被评价;CodeCoverage--代码覆盖率一种分析方法,用于确定在一个测试套执行后,软件的哪些部分被执行到了,哪些部分没有被执行到;CodeInspection--代码检视一个正式的同行评审手段,在该评审中,作者的同行根据检查表对程序的逻辑进行提问,并检查其与编码规范的一致性;CodeWalkthrough--代码走读一个非正式的同行评审手段,在该评审中,代码被使用一些简单的测试用例进行人工执行,程序变量的状态被手工分析,以分析程序的逻辑和假设;code-basedtesting--基于代码的测试根据从实现中引出的目标设计测试用例;codingstandards--编程规范一些编程方面需要遵循的标准,包括命名方式、排版格式等内容;CompatibilityTesting--兼容性测试测试软件是否和系统的其它与之交互的元素之间兼容,如:浏览器、操作系统、硬件等; completepathtesting--完全路径测试参考穷尽测试exhaustivetestingcompleteness--完整性实体的所有必须部分必须被包含的属性;complexity--复杂性系统或组件难于理解或验证的程度;Component--组件一个最小的软件单元,有着独立的规格ComponentTesting--组件测试参考单元测试computationdatause--计算数据使用一个不在条件中的数据使用;computersystemsecurity--计算机系统安全性计算机软件和硬件对偶然的或故意的访问、使用、修改或破坏的一种保护机制; condition--条件一个不包含布尔操作的布尔表达式,例如:Aconditioncoverage--条件覆盖通过测试执行到的条件的百分比;conditionoutcome--条件结果条件为真为假的评价;configurationcontrol--配置控制配置管理的一个方面,包括评价、协调、批准、和实现配置项的变更; configurationmanagement--配置管理一套技术和管理方面的原则用于确定和文档化一个配置项的功能和物理属性、控制对这些属性的变更、记录和报告变更处理和实现的状态、以及验证与指定需求的一致性; conformancecriterion--一致性标准判断组件在一个特定输入值上的行为是否符合规格的一种方法;ConformanceTesting--一致性测试测试一个系统的实现是否和其基于的规格相一致的测试;consistency--一致性在系统或组件的各组成部分和文档之间没有矛盾,一致的程度;consistencychecker--一致性检查器一个软件工具,用于测试设计规格中需求的一致性和完整性;controlflow--控制流程序执行中所有可能的事件顺序的一个抽象表示;controlflowgraph--控制流图通过一个组件的可能替换控制流路径的一个图形表示;conversiontesting--转换测试用于测试已有系统的数据是否能够转换到替代系统上的一种测试;correctivemaintenance--故障检修用于纠正硬件或软件中故障的维护;correctness--正确性软件遵从其规格的程度;correctness--正确性软件在其规格、设计和编码中没有故障的程度;软件、文档和其它项满足需求的程度;软件、文档和其它项满足用户明显的和隐含的需求的程度;coverage--覆盖率用于确定测试所执行到的覆盖项的百分比;coverageitem--覆盖项作为测试基础的一个入口或属性:如语句、分支、条件等;crash--崩溃计算机系统或组件突然并完全的丧失功能;criticality--关键性需求、模块、错误、故障、失效或其它项对一个系统的操作或开发影响的程度; criticalityanalysis--关键性分析需求的一种分析,它根据需求的风险情况给每个需求项分配一个关键级别; cyclomaticcomplexity--循环复杂度一个程序中独立路径的数量;datacorruption--数据污染违背数据一致性的情况;datadefinition--数据定义一个可执行语句,在该语句上一个变量被赋予了一个值;datadefinitionC-usecoverage--数据定义C-use覆盖在组件中被测试执行到的数据定义C-use使用对的百分比;datadefinitionC-usepair--数据定义C-use使用对一个数据定义和一个计算数据使用,数据使用的值是数据定义的值;datadefinitionP-usecoverage--数据定义P-use覆盖在组件中被测试执行到的数据定义P-use使用对的百分比;datadefinitionP-usepair--数据定义P-use使用对一个数据定义和一个条件数据使用,数据使用的值是数据定义的值;datadefinition-usecoverage--数据定义使用覆盖在组件中被测试执行到的数据定义使用对的百分比;datadefinition-usepair--数据定义使用对一个数据定义和一个数据使用,数据使用的值是数据定义的值;datadefinition-usetesting--数据定义使用测试以执行数据定义使用对为目标进行测试用例设计的一种技术;datadictionary--数据字典1一个软件系统中使用的所有数据项名称,以及这些项相关属性的集合;2数据流、数据元素、文件、数据基础、和相关处理的一个集合;dataflowanalysis--数据流分析一个软件验证和确认过程,用于保证输入和输出数据和它们的格式是被适当定义的,并且数据流是正确的;dataflowcoverage--数据流覆盖测试覆盖率的度量是根据变量在代码中的使用情况;dataflowdiagram--数据流图把数据源、数据接受、数据存储和数据处理作为节点描述的一个图形,数据之间的逻辑体现为节点之间的边;dataflowtesting--数据流测试根据代码中变量的使用情况进行的测试;dataintegrity--数据完整性一个数据集合完全、正确和一致的程度;datause--数据使用一个可执行的语句,在该语句中,变量的值被访问;datavalidation--数据确认用于确认数据不正确、不完整和不合理的过程;deadcode--死代码在程序操作过程中永远不可能被执行到的代码;Debugging--调试发现和去除软件失效根源的过程;decision--判定一个程序控制点,在该控制点上,控制流有两个或多个可替换路由;Decisioncondition--判定条件判定内的一个条件;decisioncoverage--判定覆盖在组件中被测试执行到的判定结果的百分比;decisionoutcome--判定结果一个判定的结果,决定控制流走哪条路径;decisiontable--判定表一个表格,用于显示条件和条件导致动作的集合;DepthTesting--深度测试执行一个产品的一个特性的所有细节,但不测试所有特性;比较广度测试; designofexperiments--实验设计一种计划实验的方法,这样适合分析的数据可以被收集;design-basedtesting--基于设计的测试根据软件的构架或详细设计引出测试用例的一种方法;deskchecking--桌面检查通过手工模拟软件执行的方式进行测试的一种方式;diagnostic--诊断检测和隔离故障或失效的过程;dirtytesting--肮脏测试参考负面测试negativetestingdisasterrecovery--灾难恢复一个灾难的恢复和重建过程或能力;documentationtesting--文档测试测试关注于文档的正确性;domain--域值被选择的一个集合;domaintesting--域测试参考等价划分测试equivalencepartitiontestingdynamicanalysis--动态分析根据执行的行为评价一个系统或组件的过程;DynamicTesting--动态测试通过执行软件的手段来测试软件;embeddedsoftware--嵌入式软件软件运行在特定硬件设备中,不能独立于硬件存在;这类系统一般要求实时性较高;emulator--仿真一个模仿另一个系统的系统或设备,它接受相同的输入并产生相同的输出;End-to-Endtesting--端到端测试在一个模拟现实使用的场景下测试一个完整的应用环境,例如和数据库交互,使用网络通信等; entityrelationshipdiagram--实体关系图描述现实世界中实体及它们关系的图形;entrypoint--入口点一个组件的第一个可执行语句;EquivalenceClass--等价类组件输入或输出域的一个部分,在该部分中,组件的行为从组件的规格上来看认为是相同的; equivalencepartitioncoverage--等价划分覆盖在组件中被测试执行到的等价类的百分比;equivalencepartitiontesting--等价划分测试根据等价类设计测试用例的一种技术;EquivalencePartitioning--等价划分组件的一个测试用例设计技术,该技术从组件的等价类中选取典型的点进行测试;error--错误IEEE的定义是:一个人为产生不正确结果的行为;errorguessing--错误猜测根据测试人员以往的经验猜测可能出现问题的地方来进行用例设计的一种技术;errorseeding--错误播种/错误插值故意插入一些已知故障fault到一个系统中去的过程,目的是为了根据错误检测和跟踪的效率并估计系统中遗留缺陷的数量;exception--异常/例外一个引起正常程序执行挂起的事件;executablestatement--可执行语句一个语句在被编译后会转换成目标代码,当程序运行是会被执行,并且可能对程序数据产生动作; ExhaustiveTesting--穷尽测试测试覆盖软件的所有输入和条件组合;exitpoint--出口点一个组件的最后一个可执行语句;expectedoutcome--期望结果参考预期结果predictedoutcome;failure--失效软件的行为与其期望的服务相背离;fault--故障在软件中一个错误的表现;feasiblepath--可达路径可以通过一组输入值和条件执行到的一条路径;featuretesting--特性测试参考功能测试FunctionalTestingFMEA--失效模型效果分析FailureModesandEffectsAnalysis可靠性分析中的一种方法,用于在基本组件级别上确认对系统性能有重大影响的失效FMECA--失效模型效果关键性分析FailureModesandEffectsCriticalityAnalysisFMEA的一个扩展,它分析了失效结果的严重性;FTA--故障树分析FaultTreeAnalysis引起一个不需要事件产生的条件和因素的确认和分析,通常是严重影响系统性能、经济性、安全性或其它需要特性;functionaldecomposition--功能分解参考模块分解modulardecompositionFunctionalSpecification--功能规格说明书一个详细描述产品特性的文档;FunctionalTesting--功能测试测试一个产品的特性和可操作行为以确定它们满足规格;glassboxtesting--玻璃盒测试参考白盒测试WhiteBoxTestingIEEE--美国电子与电器工程师学会InstituteofElectricalandElectronicEngineers incrementaltesting--渐增测试集成测试的一种,组件逐渐被增加到系统中直到整个系统被集成;infeasiblepath--不可达路径不能够通过任何可能的输入值集合执行到的路径;inputdomain--输入域所有可能输入的集合;inspection--检视对文档进行的一种评审形式;installabilitytesting--可安装性测试确定系统的安装程序是否正确的测试;instrumentation--插装在程序中插入额外的代码以获得程序在执行时行为的信息;instrumenter--插装器执行插装的工具IntegrationTesting--集成测试测试一个应用组合后的部分以确保它们的功能在组合之后正确;该测试一般在单元测试之后进行; interface--接口两个功能单元的共享边界;interfaceanalysis--接口分析分析软件与硬件、用户和其它软件之间接口的需求规格;interfacetesting--接口测试测试系统组件间接口的一种测试;invalidinputs--无效输入在程序功能输入域之外的测试数据;isolationtesting--孤立测试组件测试单元测试策略中的一种,把被测组件从其上下文组件之中孤立出来,通过设计驱动和桩进行测试的一种方法;jobcontrollanguage--工作控制语言用于确定工作顺序,描述它们对操作系统要求并控制它们执行的语言;LCSAJ--线性代码顺序和跳转LinearCodeSequenceAndJump包含三个部分:可执行语句线性顺序的起始,线性顺序的结束,在线性顺序结束处控制流跳转的目标语句;LCSAJcoverage--LCSAJ覆盖在组件中被测试执行到的LCSAJ的百分比;LCSAJtesting--LCSAJ测试根据LCSAJ设计测试用例的一种技术;LoadTesting--负载测试通过测试系统在资源超负荷情况下的表现,以发现设计上的错误或验证系统的负载能力; logicanalysis--逻辑分析1评价软件设计的关键安全方程式、算法和控制逻辑的方法;2评价程序操作的顺序并且检测可能导致灾难的错误;logic-coveragetesting--逻辑覆盖测试参考结构化测试用例设计structuraltestcasedesignmaintainability--可维护性一个软件系统或组件可以被修改的容易程度,这个修改一般是因为缺陷纠正、性能改进或特性增加引起的;maintainabilitytesting--可维护性测试测试系统是否满足可维护性目标;modifiedcondition/decisioncoverage--修改条件/判定覆盖在组件中被测试执行到的修改条件/判定的百分比; modifiedcondition/decisiontesting--修改条件/判定测试根据MC/DC设计测试用例的一种技术;MonkeyTesting--跳跃式测试随机性,跳跃式的测试一个系统,以确定一个系统是否会崩溃; MTBF--平均失效间隔实际meantimebetweenfailures两次失效之间的平均操作时间;MTTF--平均失效时间meantimetofailure第一次失效之前的平均时间MTTR--平均修复时间meantimetorepair两次修复之间的平均时间multipleconditioncoverage--多条件覆盖参考分支条件组合覆盖branchconditioncombinationcoverage mutationanalysis--变体分析一种确定测试用例套完整性的方法,该方法通过判断测试用例套能够区别程序与其变体之间的程度;NegativeTesting--逆向测试/反向测试/负面测试测试瞄准于使系统不能工作;non-functionalrequirementstesting--非功能性需求测试与功能不相关的需求测试,如:性能测试、可用性测试等;N-switchcoverage--N切换覆盖在组件中被测试执行到的N转换顺序的百分比;N-switchtesting--N切换测试根据N转换顺序设计测试用例的一种技术,经常用于状态转换测试中;N-transitions--N转换N+1转换顺序operationaltesting--可操作性测试在系统或组件操作的环境中评价它们的表现;outputdomain--输出域所有可能输出的集合;partitiontesting--分类测试参考等价划分测试equivalencepartitiontestingpath--路径一个组件从入口到出口的一条可执行语句顺序; pathcoverage--路径覆盖在组件中被测试执行到的路径的百分比;pathsensitizing--路径敏感性选择一组输入值强制组件走一个给定的路径;pathtesting--路径测试根据路径设计测试用例的一种技术,经常用于状态转换测试中; performancetesting--性能测试评价一个产品或组件与性能需求是否符合的测试; portabilitytesting--可移植性测试瞄准于证明软件可以被移植到指定的硬件或软件平台上; PositiveTesting--正向测试测试瞄准于显示系统能够正常工作;precondition--预置条件环境或状态条件,组件执行之前必须被填充一个特定的输入值;predicate--谓词一个逻辑表达式,结果为‘真’或‘假’;predicatedatause--谓词数据使用在谓词中的一个数据使用;programinstrumenter--程序插装参考插装instrumenterprogressivetesting--递进测试在先前特性回归测试之后对新特性进行测试的一种策略;pseudo-random--伪随机看似随机的,实际上是根据预先安排的顺序进行的;QA--质量保证qualityassurance1已计划的系统性活动,用于保证一个组件、模块或系统遵从已确立的需求;2采取的所有活动以保证一个开发组织交付的产品满足性能需求和已确立的标准和过程;QC--质量控制qualitycontrol用于获得质量需求的操作技术和过程,如测试活动;RaceCondition--竞争状态并行问题的根源;对一个共享资源的多个访问,至少包含了一个写操作,但是没有一个机制来协调同时发生的访问;recoverytesting--恢复性测试验证系统从失效中恢复能力的测试;regressionanalysisandtesting--回归分析和测试一个软件验证和确认任务以确定在修改后需要重复测试和分析的范围;RegressionTesting--回归测试在发生修改之后重新测试先前的测试以保证修改的正确性;release--发布一个批准版本的正式通知和分发;reliability--可靠性一个系统或组件在规定的条件下在指定的时间内执行其需要功能的能力; reliabilityassessment--可靠性评价确定一个已有系统或组件的可靠性级别的过程;requirements-basedtesting--基于需求的测试根据软件组件的需求导出测试用例的一种设计方法;review--评审在产品开发过程中,把产品提交给项目成员、用户、管理者或其它相关人员评价或批准的过程; risk--风险不期望效果的可能性和严重性的一个度量;riskassessment--风险评估对风险和风险影响的一个完整的评价;safety--生命安全性不会引起人员伤亡、产生疾病、毁坏或损失设备和财产、或者破坏环境;safetycritical--严格的安全性一个条件、事件、操作、过程或项,它的认识、控制或执行对生命安全性的系统来说是非常关键的;SanityTesting--理智测试软件主要功能成分的简单测试以保证它是否能进行基本的测试;参考冒烟测试SDP--软件开发计划softwaredevelopmentplan用于一个软件产品开发的项目计划;securitytesting--安全性测试验证系统是否符合安全性目标的一种测试;security.--信息安全性参考计算机系统安全性computersystemsecurityserviceabilitytesting--可服务性测试参考可维护性测试maintainabilitytestingsimplesubpath--简单子路径控制流的一个子路径,其中没有不必要的部分被执行;simulation--模拟使用另一个系统来表示一个物理的或抽象的系统的选定行为特性;simulation--模拟使用一个可执行模型来表示一个对象的行为;simulator--模拟器软件验证期间的一个设备、软件程序、或系统,当它给定一个控制的输入时,表现的与一个给定的系统类似;SLA--服务级别协议servicelevelagreement服务提供商与客户之间的一个协议,用于规定服务提供商应当提供什么服务;SmokeTesting--冒烟测试对软件主要功能进行快餐式测试;最早来自于硬件测试实践,以确定新的硬件在第一次使用的时候不会着火;softwaredevelopmentprocess--软件开发过程一个把用户需求转换为软件产品的开发过程;softwarediversity--软件多样性一种软件开发技术,其中,由不同的程序员或开发组开发的相同规格的不同程序,目的是为了检测错误、增加可靠性;softwareelement--软件元素软件开发或维护期间产生或获得的一个可交付的或过程内的文档;softwareengineering--软件工程一个应用于软件开发、操作和维护的系统性的、有纪律的、可量化的方法; softwareengineeringenvironment--软件工程环境执行一个软件工程工作的硬件、软件和固件;softwarelifecycle--软件生命周期开始于一个软件产品的构思,结束于该产品不再被使用的这段期间;SOP--标准操作过程standardoperatingprocedures书面的步骤,这对保证生产和处理的控制是必须的;sourcecode--源代码用一种适合于输入到汇编器、编译器或其它转换设备的计算机指令和数据定义; sourcestatement--源语句参考语句statementspecification--规格组件功能的一个描述,格式是:对指定的输入在指定的条件下的输出;specifiedinput--指定的输入一个输入,根据规格能预知其输出;spiralmodel--螺旋模型软件开发过程的一个模型,其中的组成活动,典型的包括需求分析,概要设计,详细设计,编码,集成和测试等活动被迭代的执行直到软件被完成;SQL--结构化查询语句structuredquerylanguage在一个关系数据库中查询和处理数据的一种语言;state--状态一个系统、组件或模拟可能存在其中的一个条件或模式;statediagram--状态图一个图形,描绘一个系统或组件可能假设的状态,并且显示引起或导致一个状态切换到另一个状态的事件或环境;statetransition--状态转换一个系统或组件的两个允许状态之间的切换;statetransitiontesting--状态转换测试根据状态转换来设计测试用例的一种方法;statement--语句。
Software Architecture Recovery based on Dynamic AnalysisAline Vasconcelos1,2, Cláudia Werner11COPPE/UFRJ – System Engineering and Computer Science ProgramP.O. Box 68511 – ZIP 21945-970 – Rio de Janeiro – RJ – Brazil2CEFET Campos (Centro Federal de Educação Tecnológia de Campos) Dr. Siqueira, 273 – Pq. Dom Bosco – ZIP 28030-130 - Campos dos Goytacazes- RJe-mail: [aline, werner]@cos.ufrj.brAbstractArchitecture recovery from legacy systems has been claimed to offer great contributions to software maintenance and reuse. Most of the approaches to architecture recovery is based on the static analysis of systems and lack a sound support to architectural elements identification. In this context, this paper presents an approach to architecture recovery based on dynamic analysis of systems. The system is executed for some specified use-cases and execution traces are collected. By analyzing the execution traces, interaction patterns are detected and architectural elements are defined based on these interaction patterns and their relation to use-case realizations. Moreover, in order to evaluate the proposed approach a case study is presented.1.IntroductionThis paper presents an approach to software architecture recovery from object-oriented legacy systems mainly based on the dynamic analysis of systems. Software architecture represents the description of a system global structure in terms of their elements and relationships among them, along with the principles that guide their design and evolution [1]. The proposed approach has been investigated in the context of the Odyssey project [11], which involves the development of a software development environment based on domain models named Odyssey. Our goals are to contribute to program comprehension and software maintenance and to generate artifacts that can later be used to specify a domain reference architecture.Architecture recovery involves a set of methods for the extraction of architectural information from lower level representations of a software system, such as source code [7]. The abstraction process to generate architectural elements frequently involves clustering source code entities (such as files, classes, functions etc.) into subsystems according to a set of criteria that can be application dependent or not. Architecture recovery from legacy systems is motivated by the fact that these systems do not often have an architectural documentation, and when they do, this documentation is many times out of synchronization with the implemented system. Most approaches to software architecture recovery has been exploring the static analysis of systems [2] [5] [6] [7]. When considering object-oriented software, which employs a lot of polymorphism and dynamic binding mechanisms, dynamic analysis becomes an essential technique to comprehend the system behavior, object interactions, and hence to reconstruct its architecture. In this work, the criteria used to determine how source code entities should be clustered in architectural elements are mainly based on the dynamic analysis of the system, taking into account the occurrences of interaction patterns and types (classes and interfaces) in use-case realizations.The proposed architecture recovery approach aims at the extraction of a functional decomposition of the system, clustering entities that implement similar and coherent functionality. However, it is important to state that an application can have many architecture descriptions, considering, for example, the different architectural views [3] or the diversity of implemented architectural patterns [2]. In this work, we adopt the 4+1 view model [3] to describe an architecture and, besides the functional decomposition that corresponds to the logical view of the architecture, the process and scenario views are also recovered by a dynamic reverse engineering sub-process. T o present the proposed approach, following this introduction, section 2 describes the proposed software architecture recovery process; section 3 presents a case study used to evaluate the process; and section 4 outlines some conclusions and lists our ongoing work.2.The Proposed ApproachThe proposed process to software architecture recovery is depicted in figure 1.Figure 1: The proposed software architecture recovery process.The process is iterative and incremental. The architecture is recovered in cycles, starting by the use-case modeling activity, and in each cycle a more complete description of the system architecture is obtained. The process is semi-automatic and guided by a developer who must have some knowledge about the application. This knowledge, if not existent, can be obtained from system experts, available system documentation and application execution. In the following we briefly describe the process activities.Static Reverse Engineering and Use-Case ModelingThe process starts by the static reverse engineering and use-case modeling activities. The static reverse engineering aims at the recovery of a static model of the system, which is represented through UML Class Diagrams. This activity is executed only once.The use-case modeling can start in parallel to the static reverse engineering. Its goal is to establish the focus of the architecture recovery in the current cycle of the process. To recover the whole architecture of an application in one step is a hard task [5]. In [9] the focus of the recovery process is also established by the use-case modeling. However use-cases are selected according to the change and evolution requirements of the application. In our work, the recovery must start by some key use-cases of the application, representing essential functionality, and incorporates more use-cases as the developer feels it is necessary.The use-case modeling activity involves a manual reconstruction of some system use-cases whenever an up-to-date use-case model of the application is not available. Besides use-cases definition, this activity also involves use-case scenarios description. A use-case scenario encompasses a set of steps that guide the developer during the application execution. In order to specify the use-cases and their scenarios, as stated in [4], which is also a reverse engineering method that performs the analysis of input and output events of the application, user manuals and application execution may be investigated. In application executions, menu options at the application user-interface are a good indicator of system use-cases. Moreover, test cases documentation, if available, can also be analyzed. Dynamic Reverse Engineering and Architectural Elements DefinitionDynamic reverse engineering aims at the reconstruction of a system behavioral model, represented through UML sequence diagrams, in this case. To this end, the system is executed for the specified use-case scenarios and these executions are monitored, allowing the collection of execution traces. Execution traces encompass the set of events and messages generated during system execution, with their sender and receiver instances and their types. They are the input source of information to the reconstruction of sequence diagrams and the definition of architectural elements.The criteria to architectural elements definition are based on the analysis of these execution traces. Most of the approaches to architecture recovery does not establish general criteria to architectural elements definition [5] [9]. When they do, architectural elements identification is based on the static analysis of the system [2] [6]. In this work, our assumption is that the dynamic model of the system, considering object-oriented software, reveals significant information about object interactions that is essential to support architectural elements reconstruction. We propose two criteria to architectural elements definition, namely:•Criterion 1: Clustering in subsystems source-code entities (classes and interfaces) that participate in interaction patterns that appear in a large1 set of use-cases. An interaction pattern that participates in the realization of a large set of use-cases indicates types that represent a central functionality in the architecture.•Criterion 2: Clustering of source-code entities that participate in the realization of a small set of use-cases together with these use-cases in subsystems.An interaction pattern represents an ordered sequence of messages and events that frequently occur during system execution. Moreover, the architectural elements defined must thereafter be mapped to the sequence diagrams reconstructed in order to allow a representation of a dynamic model of the system architecture, corresponding to the process and scenarios view [3]. The scenarios view relates use-cases to architectural elements.A challenge we face, however, to conduct this dynamic analysis is the volume of information obtained in the traces. One of the solutions proposed to this problem is to filter out from the traces the events and messages to/from Java API classes.EvaluationIn each cycle of the recovery process, the architecture reconstructed must be evaluated by system experts. The goal is to validate if the recovered elements really correspond to an expected architecture representation, being helpful to system comprehension.1 The number of use-cases that indicate a large set is application-dependent. As we perform several case studies applying the proposed process, a percentage value for this number can be defined.In order to reduce the frequently required manual effort to architecture recovery, a tool set to support the process has been developed in the context of the Odyssey project [11]. The following section presents a case study that was performed to evaluate the proposed process along with the description of our tool set.3.Case StudyA case study to evaluate the proposed process has been done with the support of the Odyssey environment, aiming at the reconstruction of its own architecture. Odyssey is a software development environment that covers the development for reuse, through domain engineering, and the development with reuse, through application engineering. It has two main views, namely Environment and Modeling Environment, in which the developer can create domains, applications, model domains and applications etc. Odyssey is written in Java programming language and contains around 650 classes.Along the years Odyssey became a huge environment, with drawbacks related to performance, usage complexity and evolution. Many tools, such as the pattern detection tool, are not necessary in some particular usage scenarios, and they can represent an overhead to the whole environment in these scenarios. Since Odyssey continues to evolve, in 2003 the team decided to reengineer the environment in order to reduce its complexity and to allow its customization to specific needs. However, only a few of the original developers were available and there was no up-to-date documentation of the whole environment design to be investigated. Thus the team realized the need to recover the Odyssey architecture in order to allow its comprehension and facilitate its reengineering. The following sections illustrate how the proposed process was applied to the recovery of the Odyssey architecture, taking into account a few architectural elements, i.e., the kernel of the application and some elements related to essential features of the environment.3.1.Static Reverse Engineering and Use-Case ModelingThe static reverse engineering was performed with the Ares tool, a reverse engineering tool integrated to the Odyssey environment, which is capable of extracting a UML static model from Java source-code. The use-case modeling activity started through the identification of some key use-cases, namely: Create a New Domain; Create a New Class; Create a New Use-Case; Create a New Class Diagram; and Define a New User. The identification of key use-cases is the developer responsibility, but may take into account some essential features of the application. In the case of Odyssey, since it represents a development environment, which encompasses reuse through domain engineering, the key use-cases were the ones related to domain creation and its modeling. Moreover, an important feature of the Odyssey environment is its control over authorized users. Some more use-cases were defined along the other recovery cycles.Create a New ClassMain Scenario: Create a new class through pop-up menu option. To start this scenario the user must be in theModeling Environment view of Odyssey.Steps:1.The user goes to the Structural View and presses the mouse right button.2.Odyssey shows a menu window with some options.3.The user chooses “Creates New Class”.4.Odyssey creates a new class element in its Structural View, with a graphical representation and a set ofdocumentation items to be fulfilled.Figure 2. Main scenario for Create New Class use-case.The main scenarios for each use-case were specified. Figure 2 exemplifies a scenario description to the main scenario for the use-case “Create a New Class”.3.2.Dynamic Reverse EngineeringDuring the dynamic reverse engineering, Odyssey was executed to the specified use-case scenarios and the execution traces were collected. To support the dynamic reverse engineering, we developed a trace collector tool, named Tracer, that uses aspects [10] to monitor Java program executions and collect the messages and events generated during execution. Tracer fits well the process needs, since it allows the collection of execution traces to be enabled and disabled at run-time, making it feasible to collect only the execution traces related to a specific use-case scenario or application functionality. Moreover, some filters can be applied while using Tracer, allowing the user to determine packages and/or classes to be traced. Tracer stores the trace in a XML file, facilitating the post-processing of the generated information. Based on these execution traces, sequence diagrams, associated to the use-case scenarios, were reconstructed using Odyssey.3.3.Architectural Elements DefinitionArchitectural elements definition started with the detection of interaction patterns in the reconstructed dynamic model. By comparing the sequence diagrams reconstructed to the Odyssey use-cases, it was possible to identify two interaction patterns that appear in almost all of the use-case scenarios. They are depicted in figures 3 and 4.Figure 3 illustrates the first pattern in the context of the “Create New Class” use-case. This pattern occurs anytime a new semantic element (like a class, a use-case or a user) needs to be created in Odyssey. Environment and ModelingEnvironment classes control a semantic element creation, asking SemanticFactory to fabricate the correspondent element. There are little differences in this pattern considering the different use-case scenarios, such as the ClassNode class, which is UseCaseNode in the “Create New Use-Case” use-case. It is important to state, however, that we assume that an interaction pattern can have some interleaved messages.The second interaction pattern detected is illustrated in figure 4. This pattern is in fact a continuation of the first one. By analyzing the patterns in figures 3 and 4, it was possible to realize that every model element, like classes, use-cases, diagrams etc., are modeling items (class ModelItem) and abstract models (class AbstractModel).Through the interaction patterns detected, it was possible to visualize the Odyssey kernel, the Semantic Core element, which encompasses the classes that are essential to the definition and instantiation of any semantic element and appear in the realization of almost all the use-cases, like Environment, ModelingEnvironment, AbstractModel etc. It is depicted in figure 6. Moreover, since Odyssey works with some factories, an architectural element to encapsulate them was defined. Architectural elements are depicted in figure 5. The Semantic Core depends on the Factories in order to create new semantic elements. The Class Modeling architectural element contains the classes (e.g. ClassModelRepresentation) that only appear in the realization of the use-cases related to class modeling. The same holds for the Use-Case Modeling architectural element. The classes in the Class Modeling and UseCase Modeling architectural elements are subclasses of classes in the Semantic Core.Figure 3. First interaction pattern detected in the Odyssey execution.Figure 4. Second interaction pattern detected in the Odyssey execution.In order to reconstruct the internal structure of each architectural element, a tool that queries the Odyssey internal class model was applied. The Class Manipulation tool provides some query capabilities to the Odyssey environment, allowing the user to select classes in the static model of an application based on some search criterion.The static reverse engineering of Odyssey was performed within Odyssey itself, making it possible to use the Class Manipulation tool to locate in the static model the classes that appeared in the interaction patterns detected. Since Odyssey has 650 classes, by using this tool, we could slice its static model and reduce the time to reconstruct its partial architecture. Moreover, by querying classes using their name string, allowed us to find classes with similar names. Grouping classes with a common string in their names,although not being one of our main crietria to architectural elements definition, is also helpful since designers use to follow this criterion in order to characterize architectural elements, like layers. The Class Manipulation tool also computed the high-level dependencies between the architectural elements (shown in figure 5) as their internal structures were reconstructed.Figure 5. Some Odyssey architectural elements.Figure 6. Semantic Core internal structure. 3.4. EvaluationBy evaluating the Odyssey architecture with experts we could confirm that the recovered architectural elements were reasonable. However, some static relationships between classes, as the aggregation between the classes Model and ModelItem (figure 6), were not recovered by the static reverse engineering tool and needed to be added manually to the diagram. Nevertheless, the recovered architecture was successfully used as the basis to the reengineering of the Odyssey, which lead to the generation of a new version of the environment, named OdysseyLight [12].4. Conclusions and Ongoing WorkThrough the presented case study it was possible to have an initial evaluation of the effectiveness of architecture recovery based on dynamic analysis of software. There are Odyssey Architectural Elementsalso a few approaches to architecture recovery that take into account the dynamic analysis. In [8], the authors apply the formal concept analysis technique to identify methods shared by use-cases implementation. Each concept in the generated conceptual lattice encompasses a set of use-cases and their shared methods. However, the lattice does not make clear where a source-code entity, such as a class, must be located in the architecture, since the same entity appears in more than one concept. In [9], dynamic analysis is also considered in the recovery process. However, this analysis is not automated and it is not used as the basis to architectural elements identification.In our proposal, criteria to architecture reconstruction are clearly defined based on use-case realizations. Moreover, we are currently specifying and developing tools to support the process activities to which an automated support still does not exist, such as the sequence diagram reconstruction and interaction patterns detection.References1. Garlan, D., Perry, D. Introduction to the Special Issue on Software Architecture. IEEETransactions on Software Engineering, April 1995, p. 269-274.2. Harris, D. R., Yeh, A., Reubestein, H.B., Yeh, A.S. Reverse Engineering to theArchitectural Level. In Proceedings of the 17th International Conference on Software Engineering, Scattle, Washington, April 1995, p. 186-195.3. Kruchten, P.B. The 4+1 View Model of Architecture. IEEE Software, November 1995, Vol. 12, Number 6, p. 42-50.4. Penteado, R.A.D., Germano, Masiero, F., P.C. An Overall Based on Fusion to ReverseEngineer Legacy Code. In Proceedings of the 3rd IEEE Working Conference on Reverse Engineering, Monterey, California, November, 1996, p. 179-188.5. Kazman, R., Carrière, S.J. Playing Detective: Reconstructing Software Architecturefrom Available Evidence. Technical Report CMU/SEI-97-TR-010, Carnegie Mellon University, October 1997.6. Mendonça, N. C., Kramer, J. Developing an Approach for the Recovery of DistributedSoftware Architectures. In Proceedings of the 6th IEEE International Workshop on Program Comprehension, Ischia, Italy, June 1998, p. 28-36.7. Sartipi, K., Kontogiannis, K., Mavaddat, F. Software Architecture Recovery. SoftwareEngineering Group, University of Waterloo, Waterloo, Ontario, Canada, Technical Report, 1999.8. Bojic, D., Velasevic, D. A Use-Case Driven Method of Architecture Recovery forProgram Understanding and Reuse Reengineering. In Proceedings of the 4th European Software Maintenance and Reengineering Conference, Zuriq, Swiss, February 2000, p.23-31.9. Ding, L., Medvidovic, N. Focus: a LightWeight, Incremental Approach to SoftwareArchitecture Recovery and Evolution. Working IEEE/IFIP Conference on Software Architecture, Amsterdam, Netherlands, August 2001, p. 191-200.10. AOSD Steering Committee. Aspect-Oriented Software Development. In:. Accessed in 09/02/2004.11. Odyssey Project. In: http://www.cos.ufrj.br/~odyssey. Accessed in 05/10/2004.12. Murta, L., Vasconcelos, A., et al. Run-Time Variability through Component DynamicLoading. To appear in the Proceedings of the Tools Session at the 18th Brazilian Symposium on Software Engineering, Brasilia, Brazil, October 2004.。