软件测量程序中英文对照外文翻译文献
软件测试部分中英文对照
Test design : 测试设计
Test driver : 测试驱动
Testing environment : 测试环境
Artifact : 工件
Automated Testing : 自动化测试
Architecture : 构架
Assertion checking : 断言检查 (10)
Audit : 审计
Application under test (AUT) : 所测试的应用程序
Hotfix : 热补丁
G11N(Globalization) : 全球化
Gap analysis : 差距分析
Garbage characters : 乱码字符
Glossary : 术语表
Glass-box testing : 白箱测试或白盒测试
GUI(Graphical User Interface) : 图形用户界面
Decision coverage : 判定覆盖
Debug : 调试
Defect : 缺陷
defect density : 缺陷密度 (60)
Deployment : 部署
Desk checking : 桌前检查
Blocking bug : 阻碍性错误
Bottom-up testing : 自底向上测试 (20)
Branch coverage : 分支覆盖
Brute force testing : 强力测试
Bug : 错误
Bug report : 错误报告
Load testing : 负载测试
Maintenance : 维护
软件应用中英文对照外文翻译文献
软件应用中英文对照外文翻译文献(文档含英文原文和中文翻译)原文：The Design and Implementation of SingleSign-on Based on Hybrid ArchitectureAbstract—For the purpose of solving the problems of user repeated logon from various kinds of Application which based on hybrid architecture and in different domains, single sign-on architecture is proposed. On the basis of analyzing the advantages and disadvantages of existing single sign-on models, combined with the key technology like Web Service, Applet and reverse proxy, two core problems such as single sign-on architecture mix B/S and C/S structure applications and cross-domain single sign-on are resolved. Meanwhile, the security and performance of this architecture are well protected since the reverse proxy and related encryption technology are adopted. The results show that this architecture is high performance and it is widely applicable, and it will be applied to practical application soon.Index Terms—single sign-on, web service, cross domain, reverse proxy, B/S, C/SINTRODUCTIONWith the information society, people enjoy the progress in the huge interests, but at the same time also faced the test of information security. With all system users need to log in the system increased, users need to set a lot of user names and passwords, which are confused easily, so it will increase the possibility of error. But most users use the same user name and password, this makes the authentication information is illegally intercepted and destroyed the possibility of increased, and security will be reduced accordingly. For managers, the more systems need more corresponding user databases and database privileges, these will increase management complexity. Single sign-on system is proposed a solution to solve the problem. Using single sign-on, we can establish a unified identity authentication system and a unified rights management system. It not only improve system efficiency and safety, but also can use user-friendly and to reduce the burden on administrators.TABLE 1 The comparison of a variety of single sign-on toachieve modelsSSO Achieve- Action ability Manageability ModelBroker Model The large Enable centralizedtransformation of the managementold systemAgent Model Need to add a new Management moreagent for each of the difficult to controlold system,transplantation isAgent and relatively simpleTransplantation Enable centralizedBroker Model simple, managementtransformation of theold system withlimited capacityGateway Model Need to use a Easy to manage, butdedicated gateway to databases between theaccess various different gateways needapplications to be synchronized Token Model Implementation of Need to add newrelatively simple components andincrease themanagement burdenSingle sign-on refers to when the user needs to access a distributed environment which has different applications to provide the service, only sign on once in the environment,no need for the user to re-sign on the various application systems[1]. Now there are many products and solutions to implement SSO, such as Passport of Microsoft, IBM Web Sphere Portal Server although these SSO products could do well in the function of single sign-on, but most of them are complex and inflexible. Currently, the typical models to achieve SSO include broker model, agent model, agent and broker model, gateway model and token model [2]. In table 1, it analyses these models can be implemented and manageability. Based on the above comparison, agent and broker model has the advantages both centralized management and revised less original application service procedure. So I decide to adopt agent and broker model as the basis for this model. In order to integrate information and applications well and with the B/S mode in-depth application software, there has been the concept of enterprise portal, offer a best way to solve this problem. Enterprise portal provides business users access information andapplications, and complete or assist in a variety of interactive behavior of a single integrated access point. The appropriate system software portal provides a development, deployment and management of portal applications services. Enterprise information portal concerns portal, content management, data integration, single sign-on, and much other content.SYSTEM CONSTRUCTION WHICH REGISTERS BASED ON THE WEB SERVICE MIX CONSTRUCTION SINGLE SIGN-ONThe system consists of multiple trust domains. Each trust domain has much B/S architecture of the application servers; in addition to B/S architecture of the application servers also included C/S architecture application servers. All the applications are bound together through a unified portal to achieve functionality of single sign-on. You can see that this architecture is based on the agent and the broker model. A unified agent portal is playing a broker role, and various applications are playing an agent role. The B/S architecture applications are installed on the Client side of SSO Agent, and the unified portal is installed on the Server side of SSO Agent. Between them is through these two Agents to interact. In addition, in Fig 1, the external provision of authentication server is LDAP authentication interface. Token authentication Web Service server provides the interfaces of single sign-on token of the additions, deletions, editions and queries. But the permission Web Service server provides the appropriate authority information system, to achieve unified management authority for accessing unified portal application system.The system supports cross- domain access, that is, the domain D1 users can access the application domain D2, and the domain D2 users can access the application domain D1. At the same time, the system also supports the application of different structures between the single sign-on, that is, user after accessing the application A of the B/S structure access the application E of C/S structure without having to repeatedly enter user name and password, or user access the application A after the application E without re-enter login information.The whole structure of Single Sign-on is as Fig 1 shown.Figure 1: The Structure of Single Sign-onA. The login processThe whole single sign-on process is as Fig 2 shown: Below is the process specific steps description:1）User login in the client browser to access A application, SSO Client of A system intercept and redirect the URL to the landing page of Unified Portal System 2）Enter the user name and password, Unified Portal System submits to the authentication server for authentication. If the information is correct, Unified Portal System automatically generates, saves notes and the role of the user ID to a local, and calls the increate-note interface of Web Service to insert the information.3）Unified Portal System returns a list of application resources pages to the user. The user clicks any one application system (e.g. A system). The SSO Client-side of A application system read the notes information and call the query-notes interface of Web Service. If it is consistent and within the time limit, it will get the role information of the user in A application system and log in A application system. At the same time, it will call the update-note interface of Note Certification Web Service to update the log-in time of this current note. Then call the interface of user rights Web Service to get this user‟s permission information with corresponding application system.4）If user end to access A application system, exit and click on the link of B application system, system implementations will be are as the same as steps (3).5）If user complete all the required access-applications and need to do the log-off operation, it will mainly call the deletion-note interface to destroy the corresponding note information.Figure 2: The whole process of Single Sign-onB.The solution of Cross-domain problemsIn the traditional implementation of single sign-on system will be generally used cookie as storage of client-side notes, but because of restrictions on cookie itself properties make it only on the host under the same domain effective, and distributed application system always can not guarantee that all hosts under the same domain. The current system does not store the note information in the client-side but placed various application parameters of the link directly. The note-verification is through the application of the SSO Client-side call to the corresponding interface of Web Service to complete.Through the Simple Object Access Protocol (SOAP) to provide software service in the Web, use WSDL file to illuminate and register by UDDI [3]. Shown in Fig 3, after the user through the application of UDDI to find a WSDL description of the document, he can call the application which through SOAP to provide by one or more operations of Web services. The biggest characteristic of Web Service is its cross-platform, whether it is the application of B/S structure or C/S structure, whether it is the application using J2EE or .NET to implement, it can access Web Service as long as to give Web Service server's I:P and interface name.The following is this system process of achieving cross-domain access:1）User log in Unified Portal system successfully.2）User accesses A application system within the trusted domain D1, complete the access and then exit this application.3）User clicks the URL of B application system within trusted domain D2 of the resources list of Unified Portal.4）SSO Client of B application intercepts the request, gets the note behind URL, and calls the query-note interface of Web Service.5）Query interface of Web Service gets back the legal information of this note to the SSO Client.6）SSO Client redirect to B application system, the user access B application.Figure 3: Web Service StructureC. The Solution of Single Sign-on between B/S and C/S StructuresAs we know, the implementation principles of applications are quite different between B/S and C/S structures. In this system, the applications of B/S structure can be accessed through by clicking URL of the application-resources-list page of Unified Portal. Since the browser security restrictions, the page does not allow users to directly call the local exe files, so need to adopt an indirect way to call C / S architecture applications. This article uses the way of Applet to call local exe files, the implementations as below:For all C/S structures, create a common Agent. This Agent's role is an interceptor, which means it need browsers to access after the C/S structure joined up Unified Portal system. (Please note that: Since the original B/S architecture and C/S structure is not using the same authentication method. For the C/S application access to the unified portal framework to achieve single sign-on system, the need for a unified authentication management, and in order to change the amount of compression to a minimum. Implementation of this system is to create a needless user name and password authentication code for all applications which are accessed a unified portal, and land on the unified portal system certified landing page. When a user uses browser to log into the unified portal system successfully and then can access any application, including the B/S architecture and C/S structure of the application. To be ensure the security of C/S application framework, when the user clicks directly to the desktop shortcut to open applications still using the original authentication.)Applications of C/S architecture are all using the same Applet of URL. The received parameters of this common Applet include bills, application name, unified login-name and password. When a user does not do the login operation before, the first visit a C/S application will be intercepted to the login-page of Unified Portal system for sign-on. If a user logged in before, when visiting a C/S application, this Agent will call the interface of Web Service note-validation to validate the note which was transferred. If the validation issuccessful, Applet object will be downloaded to the user's local to implement. In order to transform the original applications as little as possible, the method of this article is to open the login window of the corresponding application through by Applet. Below are the codes: public void OpenExe(String appName){ Runtime rn=Runtime.getRuntime();Process p=null;p=rn.exec(“c:\.” + appName + “.exe”);}After opening the log-in window of the application, the operation steps of this Applet as follows:1）Applet needs to call the bottom API of windows to get the user-name of login window, password-input box and the handle of login button through by JNI.2）Locate the user-name-input box to send unified login name. Locate password-input box to send the password. (Password information is arbitrary and in order to distinguish it from the user clicks on a shortcut directly landing system, also need to send a code that uses a unified portal access without a password authentication system.) Locate the login button to send the click event.3）At last, Applet will minimize the IE window, the related windows of applications will be placed to the forefront.These are the implementation process of C/S architecture application single sign-on. The application codes which have not been changed at all before will join up the Unified Portal system using a loosely coupled way. Need to explain that, due to the Applet JVM security restrictions, cause Applet can not directly call the user's System32 directory of local native windows dll. Now the method is first to start to use C or C + + to write the class which got the corresponding input box and button of the login window, and generate a JNIWindowUtil.dll file (JNIWindowUtil is a user-defined dll's name). And it is to place the dll in the same directory with the Applet. When the Applet is downloaded to the client side, dll is also downloaded to the user's System32 directory of local at the same time. Applet process also needs to execute statement: System.loadLibrary("JNIWindowUtil"). After completing these above steps, it can really use JNI in Applet internal to achieve the corresponding functions.D. Authentication serverThe old system user authentication information is usually stored in a database, but this architecture used LDAP to store user information. LDAP, short for Lightweight Directory Access Protocol, is the standard directory access protocol based on a simplified form. It also defines the way data organization; it is based on TCP/IP protocol of the de facto standard directory service, and has distributed information access and data manipulation functions. LDAP uses distributed directory information tree structure. It can organize and manage various users‟ information effectively and provide safe and efficient directory access.Compared with the database, LDAP is the application for reading operation more than writing operation, and database is known to support a large number of writing operations. LDAP supports a relatively simple transaction, but the database is designed to handle a large number of various transactions. When the query in Cross-domain data is mainly read data, modify the frequency is very low. When Cross-domain access to the transaction, it does not require a large load, so in comparison with the database, LDAP is the ideal choice. It is more effective and simple. This framework is applied to a large bank, the bank's systems can belong to different regions, and use of personnel may come from different geographies. In order to achieve distributed management, the use of three-level management, respectively named the Bank headquarter, Provincial and City branches of the three levels of branches, as shown in Fig 4:Figure 4: LDAP Authentication StructureDirectory replication and directory reference is the most important technology in LDAP protocol. It can be seen from the figure, Provincial and City branches of the LDAP server branch data are copied from the floor, but not a simple copy of all information, just copy the relevant data with their own information. Because for a particular application system, its users are mostly belong to the sameregion, so that implementation can greatly simplify the management of directory services and to improve the efficiency of information retrieval When a user outside the region to use this system, because of its user information in the region can not retrieve LDAP server, you need to other regions of the LDAP server to query, and therefore requires a way to use up the reference queries,first Provincial branches of the server search, without further reference to Bank headquarter of the server up until the search to the appropriate user information.The management of the regionalCitybranch, using the LDAP directory replicationmodel of Single Master/Multi Slave. When a directory user queries the directory information, Master LDAP Server and Slave LDAP Server (Slave server can have more than one) can provide services to the directory,depending on the directory user makes a request to which the directory server. When the user requests the directory update directory information, in order to ensure the Master LDAP Server and Slave LDAP Server in the same directory information content, the need for replication of directory information, thisis achieved through the LDAP Replica server data ing directory replication, when the directory number of users increases or the need to improve system performance, only simply add Slave LDAP server to the systemand then can immediatelyeffective in improving system performance,and the whole directory service system can have a good load balancing.E.Permissions Web ServerAccess Controltechnology began in the computer age of providing shared data. Previously, the way people use computers is mainly to submit the run-code written by user or run the user profile data. Users do not have much data sharing, and do not exist to control access to data. When computer comes into user's shared data, the subject of access control is nature to put on the desktop.Currently, the widely used access control models is using or reference to the early nineties of last century the rise of role-based access control model (Role-Based Access Control -RBAC). RBAC model's success is that it is inserted the "role" concept between the subject and object, decouples effectively between subject and the corresponding object (permission), and well adapts to the subject and object associated with the instability.RBAC model includes four basic elements, namely the user (User -U), roles (Roles -R), session (Session -S) and permission (Permission -P), also in the derived model also includes constraints (Constrains -C).The basic idea is to assign access rights to roles, and then the roles are assigned to users. In one session, users can gain the access rights through roles. The relationship between the elements:a user can have multiple roles, a role can be granted to multiple users; a role can have multiple permissions, a permission can be granted multiple roles;user can have multiple conversations, but a conversationis only to bind a user; a conversationcan have multiple roles, a role can share to multiple conversations at the same time; Constraints are that act on specific constraints on these relationships. As shown in Fig 5:This system is to use this very sophisticated permission access control model.Rights management, not only protects the safety of system, but also facilitates management. Currently most using the manner of code reuse and database structure reuse, rights management module is integrated into business systems.Such a framework has the following shortcomings.1)Once the permissions system has been modified, the maintenance costs will be very high.This is the general shortcoming of using code reuse and database structure reuse. Once revised, we will have to update the code in all business system and database structure, and also to ensure that existing data can smooth the transition.Some processes may require manual intervention, which is a "painful" thing for the developers and maintenance personnel.2)Did not facilitate management of Permission data.Need to enter permission management module of various business systems to manage the corresponding rights. It is complex operation, and not intuitive.3)For different architectures, different software operating environment, we must develop and maintain different permissions system. For example, B/S and C/S architecture system must each develop their own rights management system.This paper argues that most commonfunction of the permission system can abstracted from business systems to form an independent system -"unified rights system". Business system only retains the rights inquiries,read common data system and the control rights function of this system specific fine degree (such as menus, buttons, links and so on). As shown Fig 1.How to achieve a unified rights management? This paper argues that there are two implementations, one way is to use Web services to provide rights data; the other is using Mobile Agent to provided permissions data. However, the secondone run, maintenance costs are higher, and implement is more difficultythan Web services. So this architecture using Web services to provide authority data of the various systems in a unifiedway.Business system using Web services client interface to query data and obtain system privileges to share data. The client is just a port, and specific implementation code is placed in "unified rights system". These client interfaces introduced to the business system by package. If we keep the client interfaces unchanged, modify and upgrade of the unified authority system will not affect the business ers and permissions through Web pages of "unified rights system" to unify management and to achieve the user's single sign-on. The biggest advantage of Web services is the integration of data between heterogeneous systems. This breaks the restrictions of B/S, C/S structure;there is no difference between Windows and Linux platform.SYSTEM SECURITY ANALYSIS1)The interception of user name and password. The system for authentication of the user login and send the user name and password to Applet objects are used SSL protocol. And make sure that information during transmission confidentiality and integrity.Meanwhile, due to the key which is hard to get and time limited, so it can effectively prevent that intermediary attack tothe transmission of information.2)Replay attack. Many systems will use the ways of time stamp to avoid duplication attacks. However, this approach requires thecomputer clocks of communication parties to be synchronization. But it is difficult to achieve, while also appears the following situation: the two sides‟clocks which are connecting with each other, if they are out of synchronization occasionally, the correct information may be mistaken to discard for replay information, but the incorrect replay information may be as the latest one to receive. Base on the above, this system needs a simple method F of an appointment between query interfaces of Web Service provided and SSO Client of each application system or Agent.This system‟s parameter value is a random string X. The whole process of bill validation as shownin Fig6:a)When the user accesses to application system A, the SSO Client of system A intercept and call the query interface of Web Service provided, and the input parameters are a random string X and the corresponding note.b)Web Service server receives system A‟s call, intercepts note to compare with the note‟s informationof Session queue. If the queue contains the note, it will return the value of F(X) for showing validation is successful. If not, it will r eturn …failed‟ for showing validation is failed.c)SSO Client of the application A receives the return information of Web Service server, and then compares the return value with F(X) of this system. If the two are the same, it will redirect to system A, otherwise it will not be allowed to visit.The random string is different, which each interact with Web Service server. So you can limit replay attacks very well. 3)Use reverse proxy technology. Reverse proxy technologyis a substitute, which is a reverse proxy server as to N identical application servers. When external access to this application, it just knows the reverse proxy server and can not see the back multiple application servers. This improves the security of this application system.Through the above analysis, this system can provide users with a good safety Web environment.SYSTEM PERFORMANCE ANALYZESFirst, this system in addition to use SSL encryption in the transmission of user name and password, the interactions of between other servers and between user and servers are based on HTTP protocol to transmit. SSL encryption and decryption process requiresa lot of system cost, severely reduces the performance of the machine, so we should not be use this protocolto transmit data too much. Since the data which need to encrypt is small, only a userID value (note), so the performance of using MD5 to encrypt is quite satisfactory.Second, when user accessesany application system of each domain, they will be redirected to Unified Portal system for identity authentication, or directed to Web Service server for note validation. User need to sign on the system only when he is certification first time. When the visitor volume is larger, the user switch to the new application system will easily handle an interruption, which issingle sign-failure phenomenon. This phenomenon has two reasons, one is the server load is too large, the other one is network bandwidth is not enough. Among them, the method which is resolved the server load is too large is to use server cluster. Cluster is made up of multiple servers. As a unified resource, it provides a single system service to external. In this system, except for using reverse proxy technology to improve the security of accessing the applications, the more important is capability which can help to implement cluster technology of load balancing. The whole structure of reverse proxy is shown in Fig7:Fig7, reverse proxy server R provides the correspondinginterface to implement the algorithm of load balancing except for providing cache for the behind A1, A2 and A3 application. That is, it can consider the arrival request to distribute to the server which has the best performance through by scanning the conditions of CPU, memory and I/O of A1, A2, A3 server.By LoadRunner8.1, the use of reverse proxy system before and after was related to stress testing. The test results are shown in Fig 8:It can be seen from Figure 8,at the beginning, when the number of concurrent users is not large, use the reverse proxy and out of use proxy is similar. But with the gradual increase of concurrent users, the performance difference between the twois more and more evident.To 100 concurrent users to access,the system response time of using the reverse proxy is almost twice as fast as the one out of use proxy.System Web Service server needs to store the info rmation of note, so using Web Service server cluster to pay attention to this problem: the different Servers of cluster use different JVM, so an object of JVM can not be accessed by other JVM directly. For this problem, there are two methodsto resolve:1)Put the object in Session, and then configure cluster to the copy model of Session.2) Use Memcache, put the object in Memcache, and then all Server get this object from Memcache. To be equivalent to open a public memory area, which everyone can access.Any more, business system requires get rights information data through the Web services frequently. This performance of the system put forward higher requirements. The system has been taken two measures to improve performance:1)It receives a request by using time-sharing patterns of authority data server. After that, if always be calculated in real-time data, it will not certainly respond in time as the server limited resources. This will cause the system to slow down.A "time-sharing patterns of authority data" can solve this problem.When the system data changes (such as a new operation is authorized tothe role, etc), the system automatically calculates the affected user, and then re-calculate the relevant authority data, save to the specified fieldof database.When the business system requests data, only run "to read the database designated field corresponding to the specified data" such a simple action, you can greatly speed up the system response speed.2)Designed the cache structure to rely solely on time-sharing model is not enough to。
【计算机专业文献翻译】软件测试
附录2 英文文献及其翻译原文：Software testingThe chapter is about establishment of the system defects objectives according to test programs. You will understand the followings: testing techniques that are geared to discover program faults, guidelines for interface testing, specific approaches to object-oriented testing, and the principles of CASE tool support for testing. Topics covered include Defect testing, Integration testing, Object-oriented testing and Testing workbenches.The goal of defect testing is to discover defects in programs. A successful defect test is a test which causes a program to behave in an anomalous way. Tests show the presence not the absence of defects. Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible.Tests should exercise a system's capabilities rather than its components. Testing old capabilities is more important than testing new capabilities. Testing typical situations is more important than boundary value cases.An approach to te sting where the program is considered as a ‘black-box’. The program test cases are based on the system specification. Test planning can begin early in the software process. Inputs causing anomalous behaviour. Outputs which reveal the presence of defects.Equivalence partitioning. Input data and output results often fall into different classes where all members of a class are related. Each of these classes is an equivalence partition where the program behaves in an equivalent way for each class member. Test cases should be chosen from each partition.Structural testing. Sometime it is called white-box testing. Derivation of test cases according to program structure. Knowledge of the program is used to identify additional test cases. Objective is to exercise all program statements, not all path combinations.Path testing. The objective of path testing is to ensure that the set of test cases is such that each path through the program is executed at least once. The starting point for path testing is a program flow graph that shows nodes representing program decisions and arcs representing the flow of control.Statements with conditions are therefore nodes in the flow graph. Describes the program control flow. Each branch is shown as a separate path and loops are shown by arrows looping back to the loop condition node. Used as a basis for computing the cyclomatic complexity.Cyclomatic complexity = Number of edges -Number of nodes +2The number of tests to test all control statements equals the cyclomatic complexity.Cyclomatic complexity equals number ofconditions in a program. Useful if used with care. Does not imply adequacy of testing. Although all paths are executed, all combinations of paths are not executed.Cyclomatic complexity: Test cases should be derived so that all of these paths are executed.A dynamic program analyser may be used to check that paths have been executed.Integration testing.Tests complete systems or subsystems composed of integrated components. Integration testing should be black-box testing with tests derived from the specification.Main difficulty is localising errors. Incremental integration testing reduces this problem. Tetsing approaches. Architectural validation. Top-down integration testing is better at discovering errors in the system architecture.System demonstration.Top-down integration testing allows a limited demonstration at an early stage in the development. Test observation: Problems with both approaches. Extra code may be required to observe tests. Takes place when modules or sub-systems are integrated to create larger systems. Objectives are to detect faults due to interface errors or invalid assumptions about interfaces. Particularly important for object-oriented development as objects are defined by their interfaces.A calling component calls another component and makes an error in its use of its interface e.g. parameters in the wrong order.Interface misunderstanding. A calling component embeds assumptions about the behaviour of the called component which are incorrectTiming errors: The called and the calling component operate at different speeds and out-of-date information is accessed.Interface testing guidelines: Design tests so that parameters to a called procedure are at the extreme ends of their ranges. Always test pointer parameters with null pointers. Design tests which cause the component to fail. Use stress testing in message passing systems. In shared memory systems, vary the order in which components are activated.Stress testingExercises the system beyond its maximum design load. Stressing the system often causes defects to come to light. Stressing the system test failure behaviour. Systems should not fail catastrophically. Stress testing checks for unacceptable loss of service or data. Particularly relevant to distributed systems which can exhibit severe degradation as a network becomes overloaded.The components to be tested are object classes that are instantiated as objects. Larger grain than individual functions so approaches to white-box testing have to be extended. No obvious ‘top’ to the system for top-down integration and testing. Object-oriented testing. Testing levels.Testing operations associated with objects.Testing object classes. Testing clusters of cooperating objects. Testing the complete OO systemObject class testing. Complete test coverage of a class involves. Testing all operations associated with an object. Setting and interrogating all object attributes. Exercising the object in all possible states.Inheritance makes it more difficult to design object class tests as the information to be tested is not localized. Weather station object interface. Test cases are needed for all e a state model toidentify state transiti.ons for testing.Object integration. Levels of integration are less distinct in objectoriented systems. Cluster testing is concerned with integrating and testing clusters of cooperating objects. Identify clusters using knowledge of the operation of objects and the system features that are implemented by these clusters. Testing is based on a user interactions with the system. Has the advantage that it tests system features as experienced byusers.Thread testing.Tests the systems response to events as processing threads through the system. Object interaction testing. Tests sequences of object interactions that stop when an object operation does not call on services from another objectScenario-based testing. Identify scenarios from use-cases and supplement these with interaction diagrams that show the objects involved in the scenario. Consider the scenario in the weather station system where a report is generated.Input of report request with associated acknowledge and a final output of a report. Can be tested by creating raw data and ensuring that it is summarised properly. Use the same raw data to test the WeatherData object.Testing workbenches.Testing is an expensive process phase. Testing workbenches provide a range of tools to reduce the time required and total testing costs. Most testing workbenches are open systems because testing needs are organisation-specific. Difficult to integrate with closed design and analysis workbenchesTetsing workbench adaptation. Scripts may be developed for user interface simulators and patterns for test data generators. Test outputs may have to be prepared manually for comparison. Special-purpose file comparators may be developed.Key points:Test parts of a system which are commonly used rather than those which are rarely executed. Equivalence partitions are sets of test cases where the program should behave in an equivalent way. Black-box testing is based on the system specification. Structural testing identifies test cases which cause all paths through the program to be executed.Test coverage measures ensure that all statements have been executed at least once. Interface defects arise because of specification misreading, misunderstanding, errors or invalid timing assumptions. To test object classes, test all operations, attributes and states.Integrate object-oriented systems around clusters of objects.译文：软件测试本章的目标是介绍通过测试程序发现程序中的缺陷的相关技术。
测试操作软件中英文对照
测试操作软件中英文对照目录：1 Satcon电源逆变系统操作主界面---------------------------------------------------------------------------------------------------------- 32 写入界面/ writer -------------------------------------------------------------------------------------------------------------------------- 52.1 控制/Control ---------------------------------------------------------------------------------------------------------------------------- 52.2 测试/Test ----------------------------------------------------------------------------------------------------------------------------------- 52.3 功能/Feature ----------------------------------------------------------------------------------------------------------------------------- 62.4 光伏/PV ------------------------------------------------------------------------------------------------------------------------------------- 62.5 组件/Components ------------------------------------------------------------------------------------------------------------------------ 72.6 额定值/Ratings ---------------------------------------------------------------------------------------------------------------------------- 82.7 直流电压保护/Vdc Prot ------------------------------------------------------------------------------------------------------ 82.8 直流电流保护/Idc Prot -------------------------------------------------------------------------------------------------------------- 92.9 交流电压保护/Vac Prot ------------------------------------------------------------------------------------------------------------- 102.10 交流电压保护2/Vac Prot 2 ------------------------------------------------------------------------------------------------------- 102.11 交流电流保护/Iac Prot ------------------------------------------------------------------------------------------------------------ 112.12 交流电流保护2/Iac2 Prot -------------------------------------------------------------------------------------------------------- 112.13 接地保护/Gnd Prot ---------------------------------------------------------------------------------------------------------------- 122.14 接地保护2/Gnd Prot 2 ------------------------------------------------------------------------------------------------------------ 122.15 频率保护/Frequency Prot -------------------------------------------------------------------------------------------------------- 132.16 寄存器/Regs ---------------------------------------------------------------------------------------------------------------------- 132.17 寄存器2/Regs 2 -------------------------------------------------------------------------------------------------------------------- 142.18 电压比例/V Scaling ---------------------------------------------------------------------------------------------------------------142.19 电流比例/I Scaling ----------------------------------------------------------------------------------------------------------------- 152.20 其他比例/Misc.Scaling ------------------------------------------------------------------------------------------------------------152.21 校准/Calibrate ---------------------------------------------------------------------------------------------------------------------- 162.22 温度/Thermal ------------------------------------------------------------------------------------------------------------------------ 162.23 温度2/Thermal 2 ------------------------------------------------------------------------------------------------------------------- 172.24 modbus通讯/Modbus -------------------------------------------------------------------------------------------------------------- 172.25 系列号/Serial ------------------------------------------------------------------------------------------------------------------------- 182.26 外部控制/Ext control --------------------------------------------------------------------------------------------------------------- 183 读取界面/reader ----------------------------------------------------------------------------------------------------------------------------193.1 测量/Meters ----------------------------------------------------------------------------------------------------------------------------- 203.2 相/Phases -------------------------------------------------------------------------------------------------------------------------------- 203.3 每个机器/Per Unit -------------------------------------------------------------------------------------------------------------------- 213.4 电流调节/I Regs ---------------------------------------------------------------------------------------------------------------------- 213.5 电压调节/V Regs --------------------------------------------------------------------------------------------------------------------223.6 软件/Software ------------------------------------------------------------------------------------------------------------------------- 223.7 计时器/Timers ------------------------------------------------------------------------------------------------------------------------ 233.8 温度/Thermal ------------------------------------------------------------------------------------------------------------------------- 233.9 直流输入路数1/String 1 ----------------------------------------------------------------------------------------------------------- 243.10 直流输入路数2/String 2 ---------------------------------------------------------------------------------------------------------- 24 3.11 直流输入每路千瓦时1/String kWHr 1 --------------------------------------------------------------------------------------- 25 3.12 直流输入每路千瓦时2/String kWHr 2 --------------------------------------------------------------------------------------- 25 3.13 数字信号输入/DIN ---------------------------------------------------------------------------------------------------------------25 3.14 数字信号输出/DOUT ------------------------------------------------------------------------------------------------------------263.15 模拟信号输入/AIN --------------------------------------------------------------------------------------------------------------264 点阵显示/Bit Show ---------------------------------------------------------------------------------------------------------------------- 27 4.1 状态/Status --------------------------------------------------------------------------------------------------------------------------- 27 4.2 现场可编程门阵列/FPGA --------------------------------------------------------------------------------------------------------27 4.3 输入/输出/INPUTS/OUTPUTS -------------------------------------------------------------------------------------------------- 28 4.4 故障1-3/Fault 1-3 ------------------------------------------------------------------------------------------------------------------- 29 4.5 故障4-6/Fault 4-6 ------------------------------------------------------------------------------------------------------------------- 30 4.6 故障7/Fault7 ------------------------------------------------------------------------------------------------------------------------ 30 4.7 比例/CAL ----------------------------------------------------------------------------------------------------------------------------- 31 4.8 点阵显示8/BitShow 8 -------------------------------------------------------------------------------------------------------------- 311 Satcon 电源逆变系统操作主界面简写注释：PCS : power conditioning system 电源逆变系统 PLL ：phase locked loop 锁相环路 volts : voltages 做名称是电压 做单位是伏特 amps : amperes 安培 rdy : ready 准备 pwr ：power 功率操作Satcon 电源逆变系统操作软件点阵显示写入界面读取界面其他窗口停机 重启 启动 停止 转到本地控制 转到远程控制 唤醒待机 直流输入电压 直流连接电流 没有故障 锁相环路失效 输入功率锁相环路没锁定输出电流输出视在功率输出有功功率功率因素直流输入没准备好输出电网端没准备好 没准备好CR1开路CR2开路 无功率输出门极关闭AC 断路器断开PI （Kp ，Ti ）: P=proportional 比例 对应参数为Kp ， I=intergral 积分 对应参数为Ti DSP ：Digital Signal Processor 数字信号处理器停机 重启 启动 停止连接电源逆变系统 断开电源逆变系统 电源逆变系统通讯设置用户级别服务端级别系统级别 退出软件比例积分调节（Kp ，Ti ） 设置与DSP 通讯的参数从DSP 上传设置到电脑从电脑下载设置到DSP2 写入界面/ writer 2.1 控制/Controlcmd : command 指令，控制 2.2 测试/Test功率控制模式指令单位详细步骤保存运行使能无功功率控制模式 有功功率控制 功率因素控制无功功率控制 直流电压控制最大dq 电流 出厂默认100%有功功率升降速度无功功率升降速度保存所有设置到电脑和DSP 从电脑读取设置 从DSP 读取设置 清除设置测试模式选择闭合输出门极测试_选择 外部输入掩码开环测试中电压控制 闭环测试中电压控制风扇转速测试有功电流控制cct : circuit 电路open cct test 开环测试 short cct test 闭环测试 ext ：external 外部 2.3 功能/featurebw ：bandwidth 带宽estop ：emergency stop 紧急停止 2.4 光伏电压/PV急停_重置自动重置间隔时间锁相环路带宽自动重置最大尝试次数自动重置锁死时间输出接触器断开延时 保存参数 初始化指令重新接入电网延时min ：minimum 最小值，最小 PV ：photovoltage 光电压 光伏mppt ：maximum power point tracking 最大功率点跟踪 2.5 组件/components直流输入门槛电压 超过门槛电压后直流输入延时低功率限定 低功率延时预充电电压最小值 功率最小改变值直流电压操作每步间隔时间 功率改变延时Mppt 中直流电压改变最小值 Mppt 中直流电压改变最大值风扇转速可(1)否(0)调节 逆变桥数IGBT 开关频率死区时间输出滤波电感值输出滤波电容大小有（0）无（1）变压器三角型电压反馈1/星型接0直流输入路数freq：frequency 频率cap：capacity电容容量num：number 数量2.6 额定值/ratings额定输出功率额定输出频率额定输出电压额定逆变器输出电压欧洲机型CE 1，UL 0 变压器电压抽头比例语言接地类型:1接地，0 浮地inv：inverter 逆变器这里指逆变模块IGBTIGBT:Insulated Gate Bipolar Transistor 绝缘栅双极型晶体管euro：europe 欧洲2.7 直流电压保护/Vdc Protvolt ：voltage 电压inst ：instantaneous 瞬间，即刻的 Prot ：protection 保护 2.8 直流电流保护/Idc Prot直流输入电压过压保护直流输入过压保护延时直流输入电压欠压保护门限直流输入欠压保护延时直流过压保护门限 直流过压保护延时直流欠压保护门限直流欠压保护延时直流过压瞬间保护门限直流欠压瞬间保护下限直流输入过流保护门限 直流输入过流保护延时直流输入瞬间过流保护门限2.9 交流电压保护/Vac Prot2.10 交流电压保护2/Vac Prot 2输出电压瞬间过压保护门限输出电压过压快速保护门限 输出电压过压快速保护延时输出过压慢速保护门限输出过压慢速保护延时输出欠压快速保护下限 输出欠压快速保护延时输出欠压慢速保护下限 输出欠压慢速保护延时输出电压不平衡保护门限 输出电压不平衡保护延时2.11 交流电流保护/Iac Prot2.12 交流电流保护2/Iav2 ProtUL ：Underwriters Laboratories 美国保险商实验室 说这个机器是UL 的是说这个机器要符合UL 认证标准 同理CE 的是欧盟标准输出过流保护门限 输出过流保护延时中线过流保护门限 中线过流保护延时电流不平衡保护门限电流不平衡保护延时IGBT 过流保护门限 IGBT 过流保护延时UL 型号触发保护最小输出功率UL 型号触发保护的电流不平衡百分比值IGBT 硬件过流(短路)保护门限2.13 对地保护/Gnd ProtGFDI ：2.14 对地保护2/Gnd Prot 2漏电流快速保护门限漏电流快速保护延时漏电流慢速保护门限 漏电流慢速保护延时接地直流保险保护动作电压 接地直流保险保护动作延时对地阻抗保护门限阻值 对地阻抗保护触发延时接地漏电流保护门限电流接地漏电流保护触发延时浮地阻抗测量传感器失效判定门限值Gnd：ground 地，接地Max：maximum 最大值2.15 频率保护/Frequency Prot超频保护门限超频保护延时欠频保护门限低频保护延时频率瞬间变动保护限定频率瞬间变动保护时间限定lmt：limit 限制限定tmlmt：time limit 时间限定2.16 寄存器/Regs（一般不用动）直流输入电压调节器增益直流输入电压调节器时间常量输出线电流调节器增益输出线电流调节器时间常量抗孤岛效应增益系数直流电流正反馈系数IGBT电流调节器增益IGBT电流调节器时间常量Reg：regulator 调节器应该指的是运放Cur：current 电流2.17 调节2/Regs 2（一般不用动）temp ：temperature 温度 2.18 电压比例/V Scalingfdbk ：feedback 反馈 2.19 电流比例/I Scaling功率调节器比例增益 功率调节器积分增益散热片温度调节器比例增益 散热片温度调节器积分增益散热片过温调节器比例增益 散热片温度调节器积分增益直流输入电压反馈串联电阻 IGBT 电压反馈串联电阻 输出电压反馈串联电阻IGBT 电压反馈比率输出电压反馈比率输出电压反馈并联电阻IGBT 电压反馈并联电阻直流输入电压反馈并联电阻2.20 其他比例/Misc.ScalingMisc.: miscellaneous 其他，各式各样 2.21 校准/Calibrate接地电流LEM 反馈比率 接地电流LEM 反馈负载电阻直流电流LEM 反馈比直流电流反馈负载电阻IGBT 电流LEM 反馈比IGBT 电流反馈负载电阻输出电流CT 反馈比率 中线电流CT 反馈比率 输出电流反馈负载电阻中线电流反馈负载电阻温度反馈串联电阻 温度反馈并联电阻直流输入路数电流LEM 反馈比率 直流输入路数电流反馈负载电阻Vdgim 浮地阻抗取样反馈串联电阻 Vdgim 反馈并联电阻接地保险电压取样串联电阻 接地保险电压取样并联电阻第二浮地阻抗取样反馈串联电阻 第二浮地阻抗取样反馈并联电阻2.22 温度/Thermal2.23 温度2/Thermal 2校准反馈 实际测量到的IGBT 的电压 实际测量到的直流输入电压 实际测量到的A 相电压实际测量到的B 相电压实际测量到的C 相电压温度过低保护门限风扇空气温度过低保护门限 散热片温度过低保护门限 风扇停止温度设定温度反馈路数温度过高保护门限风扇空气温度过高保护门限散热片温度过高保护门限风扇运转温度设定风扇最小转速PWR: power 功率FANON:fan on 风扇运转2.24 Modbus通讯/Modbus 2.25 系列号/serial 100%功率下风扇运转温度5%功率下风扇运转温度Modbus传输波特率Modbus访问代码Modbus数据位访问代码1 Modbus奇偶校验Modbus停止位从站地址nv: nonvolatile 非易失性 chksum ：checksum 校验和 prgm: program 程序 2.26 外部控制/Ext control系列号1输出频率跟踪 允许非易失性写入F206 校验和保存 程序校验和保存模拟功率因素控制1：外部继电器和4-20ma 功率因素控制 0：禁止外部控制最大功率因数范围功率控制开关1 功率控制开关2功率控制开关3功率控制开关4Ext: external 外部的 PF: power factor 功率因素 rng:range 范围 SW: switch 开关3 读取界面（只读参数）3.1 测量/meters3.2 相/Phases直流输入电压 直流连接电压 直流连接电流 输入功率IGBT 电压 IGBT 电流 输出线电压 输出线电流输出有功功率 输出无功功率 总兆瓦小时 输出视在功率 功率因素总千瓦小时 总瓦小时 直流输入准备时间中线电流 直流对地电流 对地阻抗 交流侧准备时间操作状态 电脑指令 远程指令 接地保险电压IGBT a相电流IGBT b相电流IGBT c相电流风扇转速2组IGBT a相电流2组IGBT b相电流2组IGBT c相电流输出线电流a相输出线电流c相输出线电流b相电流不平衡输出电压a相输出电压b相输出电压c相电压不平衡ab相之间输出电压bc相之间输出电压ca相之间输出电压锁相环路错误锁相环路频率3.3 每个机器/Per Unit平均直流输入电压平均直流电压平均直流电流平均IGBT电压平均IGBT电流d轴平均IGBT电流q轴平均IGBT电流平均输出电压平均输出电流d轴平均输出电流q轴平均输出电流平均输入功率平均输出功率平均无功功率平均视在功率平均输出频率平均频率错误平均中线电流功率因素d轴平均IGBT电压q轴平均IGBT电压简写注释avg: average 平均值err ：error 错误3.4 电流调节/I Regs3.5 电压调节/V RegsRef ：reference 参考 3.6 软件/Softwared 轴输出电流指令 d 轴输出电流错误 d 轴输出电流反馈 d 轴d 轴输出维持电流 d 轴电压控制 q 轴输出电流指令 q 轴输出电流指令q 轴输出电流错误 q 轴 q 轴输出维持电流 q 轴电压控制d 轴IGBT 电流错误 d 轴IGBT 平均电流 d 轴IGBT 电流错误 d 轴IGBTd 轴IGBT 维持电流 d 轴 q 轴IGBT 控制 q 轴IGBT 平均电流q 轴IGBT 电流错误 q 轴IGBT q 轴IGBT 维持电流 q 轴参考电压 反馈电压 错误电压 维持电压瞬间电压 直流参考电流d 轴输出电压控制q 轴输出电压控制 平均输入功率平均输出功率直流电压最低值 直流电压最高值REV ：revision 版本 param ：parameter 参数 calc ：calculation 计算 ini ：initial 初始化3.7 计时器/Timersecs: seconds 秒 cntr: control 控制FPGA 版本 F206版本 F240版本程序校验和计算 206程序校验和计算 参数校验和计算 数据校验和计算程序校验和保F206校验和保存参数校验和读取数据校验和读取最大dq 电流 仪表校验和保存 参数校验和保存d 轴电流升降速度控制 数据库初始化OK1数据库初始化OK2千瓦时控制AC 侧准备时间 直流输入准备时间 时间控制 尝试次数锁定标记 校验和错误 故障总和计时器1 风扇重置计时器 串行通讯接口校验和错误错误5 PWM 载波计数Modbus 超时 0功率时间限制串行通讯接口超时sci ：Serial Communications Interface 串行通讯接口 pwm ：Pulse Width Modulation 脉宽调制 3.8 温度/Thermalcab ：cabinet 箱，橱柜3.9 输入路数1/Strings 13.10 输入路数2/Strings 2风扇室空气温度 控制箱温度 散热片温度1风扇空气温度信号电压控制箱温度信号电压散热片温度信号电压1散热片最大温度 风扇转速 温度限定直流输入第一路电流直流输入所有路数平均电流直流输入第17路电流直流输入所有路数平均电流3.11路数千瓦小时1/String kWHr 1第一路千瓦时3.12 路数千瓦小时2/String kWHr 23.13 数字信号输入/DINDIN ：digital signal in 数字信号输入 DS ：disconnector 断路器 CR ：contactor 接触器 STAT ：status 状态LAC ：AC reactor 交流电抗器 TX: transformer 变压器 CB ：AC breaker 交流断路器 TSW ：temperature switch 温度开关 SURGE: surge suppressor 浪涌抑制 3.14数字信号输出/DOUT直流断路器 门开关或急停 直流接触器输入 接地保护监测风扇2状态 电抗器1温度开关 变压器温度开关 1组IGBT 保险2组IGBT 保险 交流接触器 电抗器2温度开关 交流断路器风扇状态 急停 1组逆变模块温度开关 1组逆变模块温度开关直流浪涌抑制器交流浪涌抑制器 操作开关选择 风扇1温度开关风扇2温度开关数字信号输入功率 数字信号输入功率因素DOUT: digital signal out 数字信号输出 3.15 模拟信号输入/AINAIN: analog signal in 模拟信号输入 NEUT: neutral 中线4 点阵显示界面4.1状态/Status数字信号输出1A 相输出电压模拟信号 A 相输出电流模拟信号IGBT 输入电压模拟信号 A 相输入电流模拟信号对地漏电流模拟信号 中线电流模拟信号 直流侧火线电流模拟信号直流输入电压浮地阻抗电压直流连接电压 路数1路数2 温度测量电压测试10：没有初始化1 ：锁相环路被禁止2 ：锁相环路没锁定3：正序（逆变发电）4 ：输出端没有准备好5 ：直流输入没有准备好6：没有准备好7：没有故障8：没有停机9 ：没有运行10 ：无功率输出11 ：没有接入电网12：门极信号测试关闭13 ：开环测试模式关闭14 ：闭环测试模式关闭15：无参数4.2 现场可编程门阵列/FPGA0：IGBT光纤驱动信号反馈11：IGBT光纤驱动信号反馈22：IGBT光纤驱动信号反馈33：IGBT光纤驱动信号反馈4 4 ：IGBT光纤驱动信号反馈5 5：IGBT光纤驱动信号反馈620：直流电源OK 21：硬件过流1 OK 22：硬件过流2 OK23：24：IGBT 光纤驱动信号A25：IGBT光纤驱动信号B 26：IGBT光纤驱动信号C 27：IGBT光纤驱动信号A2 28：IGBT光纤驱动信号B2 29：IGBT光纤驱动信号C232：重启33：门极信号允许34：门极测试35：运行指示灯36：故障指示灯37：38：逆变模块2错误掩码39：逆变器模块2允许简写注释：HW: hardware 硬件OC：over current 过流en: enable 使能flt: fault 故障，错误msk：mask 掩码4.3 输入/输出/INPUTS/OUTPUTS0:直流断路器断开1：门打开2: 直流接触器断开3：GFDI接地错误4：风扇2 OK 5：电抗器温度过高6：隔离变压器温度过高7：逆变模块1烧保险8：逆变模块2烧保险9：交流接触器断开10：电抗器2温度过高11：电路切断器12：风扇1 OK 13：急停14：逆变模块1温度过高15：逆变模块2温度过高16：直流浪涌抑制器17：交流浪涌抑制器18：操作选择开关19：风扇1温度开关20：风扇2温度开关32：门极信号复位指令33：断开交流接触器指令34：断开预充电回路指令35：断开直流接触器指令36：没有发电37：故障38：切断电路保护指令39：GFDI复位信号40：风扇继电器41：风扇2脉宽调制42：门极信号关闭43：辅助多路传输144：辅助多路传输245：多路模拟开关3 46：多路模拟开关4 47：风扇1脉宽调制简写注释：xfmr：transformer 变压器brbk：breaker 断路器SS：surge suppressor 浪涌抑制器Prechg:precharge 预充电Amux：auxiliary multiplex 多路复用4.4 故障1-3/Fault 1-30：直流输入没准备好1：联网输出端没有准备好2：停止指令3：停机指令4：急停5：供电电源太低被停止6：电流太小被停止7：保护延时故障8：门被打开9：直流断路器断开10：电路切断器断开11：DPCB板故障12：硬件故障13：IGBT故障14：温度故障16：直流输入过压17：直流输入欠压18：直流过压19：直流欠压20：直流输入接地故障21：联网输出端慢速过压22：联网输出端快速过压23：联网输出端慢速欠压24：联网输出端快速欠压25：电压不平衡26：频率过高27：频率慢速过低28：频率快速过低29：中线过流30：联网输出端瞬间过压32：程序校验和33：fpga版本34：数据拷贝135：数据拷贝2 36：参数A拷贝1 37：参数A拷贝2 38：参数A拷贝239：参数B拷贝240：电压反馈比例41：电流反馈比例42：IGBT电流反馈43：额定值改变44：F206版本45：f206校验和46：非易失性ram故障47 ：fpga故障简写注释：OV：over voltage 过压UV: under voltage 欠压4.5 故障4-6/Fault 4-60：+5V隔离电源1: +5V DPCB板电源2：+15V DPCB板电源3：-15V DPCB板电源4：看门狗5：浪涌抑制器6：1组逆变模块保险7：2组逆变模块保险8：1组逆变模块温度9：2组逆变模块温度10：变压器温度11：电抗器温度12：预充电故障13：测试模式14：开环测试15：闭环测试16：A相门极信号反馈17：B相门极信号反馈18：C相门极信号反馈19：A2相门极信号反馈20：B2相门极信号反馈21：C2相门极信号反馈22：直流输入过流23：直流输入瞬间过流24：直流瞬间欠压25：直流瞬间过压26：IGBT软件过流27:1组IGBT硬件过流28：2组IGBT硬件过流29：联网输出端过流30：电流不平衡32：控制箱温度过高33：风扇室空气温度过高34：散热片1温度过高35：散热片2温度过高36：散热片3温度过高37：散热片4温度过高38：散热片5温度过高39：散热片6温度过高40：控制箱温度过低41：风扇空气温度过低42：散热片1温度过低43：散热片2温度过低44：散热片3温度过低45：散热片4温度过低46：散热片5温度过低47：散热片6温度过低简写注释：iso：insolated power 隔离电源DPCB：digital power control board 数字电源控制板SW: software软件hi：high 高htsnk：heatsink散热片lo：low 低4.6 故障7/Fault 70：风扇1故障1：风扇2故障2：直流接触器没有断开3：直流接触器没有闭合4：交流接触器没有断开5：交流接触器没有闭合7：8：4.7 比例/CAL0：A相输出感应电压和实际测量电压相差过大1：IGBT电压检测相位错误2：输出电流检测CT相位错误3：IGBT电流检测LEM相位错误9：B相输出感应电压和实际测量电压相差过大10：C相输出感应电压和实际测量电压相差过大11：IGBT感应电压和实际测量电压相差过大12：直流感应电压和实际测量电压相差过大13：直流输入感应电压和实际测量电压相差过大4.8 点阵显示8/Bit Show 80：功率因素0 1：功率因素12：功率因素2 3：功率因素34：功率控制指令0 5：功率控制指令1 6：功率控制指令2 7：功率控制指令3简写注释：PF: power factor 功率因素Pcmd：power command 功率控制。
关于软件测试的外国文献
关于软件测试的外国文献软件测试是软件开发过程中至关重要的一环，而外国文献中关于软件测试的研究和实践也非常丰富。
下面我将从不同角度介绍一些相关的外国文献，以便更全面地了解软件测试的最新发展。
1. "Software Testing Techniques" by Boris Beizer:这本经典著作详细介绍了软件测试的各种技术和方法，包括黑盒测试、白盒测试、基于模型的测试等。
它提供了许多实用的指导和案例，对软件测试的理论和实践都有很深入的探讨。
2. "Testing Computer Software" by Cem Kaner, Jack Falk, and Hung Q. Nguyen:这本书介绍了软件测试的基础知识和常用技术，包括测试计划的编写、测试用例设计、缺陷管理等。
它强调了测试的全过程管理和质量保证，对于软件测试初学者来说是一本很好的入门指南。
3. "The Art of Software Testing" by Glenford J. Myers, Corey Sandler, and Tom Badgett:这本书从理论和实践的角度探讨了软件测试的艺术。
它介绍了测试的基本原则和策略，以及如何设计有效的测试用例和评估测试覆盖率。
这本书对于提高测试人员的思维和技巧非常有帮助。
4. "Foundations of Software Testing" by Aditya P. Mathur:这本书系统地介绍了软件测试的基本概念、技术和方法。
它涵盖了测试过程的各个阶段，包括需求分析、测试设计、执行和评估。
这本书还提供了丰富的案例和练习，帮助读者深入理解和应用软件测试的原理和技术。
5. "Software Testing: Principles and Practices" by Srinivasan Desikan and Gopalaswamy Ramesh:这本书介绍了软件测试的原则、实践和工具。
软件系统开发中英文对照外文翻译文献
软件系统开发中英文对照外文翻译文献(文档含英文原文和中文翻译)软件工程中的过程处理模型斯卡基沃尔特摘要软件系统从起初的开发，维护，再到一个版本升级到另一个版本，经历了一系列阶段。
这篇文章归纳和整理了一些描述如何开发软件系统的方法。
从传统的软件生命周期的背景和定义出发，即大多数教科书所讨论的，并且目前的软件开发实践所遵循的软件生命周期，接着讨论作为目前软件工程技术基石的更全面的软件开发模型。
关键词：软件生命周期；模型；原型1 前言软件业的发展最早可追溯到开发大型软件项目的显式模型，那是在二十世纪五十年代和六十年代间。
总体而言，这些早期的软件生命周期模型的唯一目的就是提供一个合理的概念计划来管理软件系统的开发。
因此，这种计划可以作为一个基础规划，组织，人员配备，协调，预算编制，并指导软件开发活动。
自20世纪60年代，出现了许多经典的软件生命周期的描述（例如，霍西尔1961年，劳斯莱斯1970年，1976年博伊姆，迪斯塔索1980年，1984年斯卡基，萨默维尔1999年）。
罗伊斯（1970）使用现在生活中熟悉的“瀑布”图表，提出了周期的概念，这个图表概括了开发大型软件系统是多么的困难，因为它涉及复杂的工程任务，而这些任务在完成之前可能需要不断地返工。
这些图表也通常在介绍性发言中被采用，主要针对开发大型软件系统的人们（例如，定制软件的客户），他们可能不熟悉各种各样的技术问题但还是要必须解决这些问题。
这些经典的软件生命周期模型通常包括以下活动一些内容：系统启动/规划：系统从何而来？在大多数情况下，不论是现有的信息处理机制以前是自动的，手工的，还是非正式的，新系统都会取代或补充它们。
● 需求分析和说明书：阐述一个新的软件系统将要开发的问题：其业务能力，其所达到的性能特点，支持系统运行和维护所需的条件。
● 功能或原型说明：潜在确定计算的对象，它们的属性和关系，改变这些对象的操作，约束系统行为的限制等。
●划分与选择：给出需求和功能说明书，将系统分为可管理的模块，它们是逻辑子系统的标志，然后确定是否有对应于这些模块的新的，现有的，或可重复使用的软件系统可以复用。
软件开发中英文对照外文翻译文献
软件开发中英文对照外文翻译文献(文档含英文原文和中文翻译)译文：仿真软件开发低大型复杂腔基于UG的二次开发摘要---射击和弹跳射线(SBR)二次开发的基础软件是由国标库(UG)。
射线跟踪的核心算法是基于优化的非均匀有理b样(NURBS)曲线表面相交算法建立在UG,导致非常高的射线路径跟踪的准确性没有啮合从而保持原有的空腔模型的准确性。
它也是有效的避免同任何复杂的蛀牙,因为即使工作屏蔽的过程。
两腔的几何建模及其散射模拟成一个统一的平台,形成一个易用的综合和环球环境电磁建模复杂的蛀牙。
在本文开发的软件对复杂腔散射建模引入了一些数值结果显示的准确性和效率关键词--电大型复杂cavit; 雷达截面; UG的二次开发; 射击和弹跳射线(SBR); 射线跟踪I.介绍雷达截面(RCS)的分析电等大型复杂洞进口或出口,双面或三面角反射器等,是计算电磁学中最重要的主题之一。
低大型复杂的空腔结构,只有基于高频方法如射击和弹跳射线(SBR)[1][2][3]是合适的。
传统上,为三步骤采用SBR首先,模型腔的CAD软件和网格表面的内墙,然后出口信息网格的结果;其次发现表面上的光线的反射点ray-surface十字路口和屏蔽计算;最后计算RCS即将离任的射线从腔。
虽然这些网基于射线跟踪可用于任意形状的蛀牙从理论上讲,它有不准确的缺点路径建立在复杂的蛀牙导致贫穷的RCS计算精度。
电大型复杂的蛀牙,射线跟踪的效率很低,由于分离腔建模与RCS计算复杂的仿真过程。
为了解决这些问题, 一个强大的CAD软件,模拟电大型复杂腔并计算其RCS在同一平台。
开发的软件具有以下优势: 1)腔建模和RCS计算在UG集成,因此仿真过程大大简化。
2)表面啮合没有必要而射线可以追踪精度高和效率在任何任意形状的空腔。
3)开发的软件是通用的电磁散射的凹面反射镜结构,如蛀牙和角落。
小说射线追踪方法的新的先进的软件是基于UG的二次开发将讨论下一步,和RCS仿真结果。
软件系统开发中英文对照外文翻译文献
软件系统开发中英文对照外文翻译文献(文档含英文原文和中文翻译)软件工程中的过程处理模型斯卡基沃尔特摘要软件系统从起初的开发，维护，再到一个版本升级到另一个版本，经历了一系列阶段。
这篇文章归纳和整理了一些描述如何开发软件系统的方法。
从传统的软件生命周期的背景和定义出发，即大多数教科书所讨论的，并且目前的软件开发实践所遵循的软件生命周期，接着讨论作为目前软件工程技术基石的更全面的软件开发模型。
关键词：软件生命周期；模型；原型1 前言软件业的发展最早可追溯到开发大型软件项目的显式模型，那是在二十世纪五十年代和六十年代间。
总体而言，这些早期的软件生命周期模型的唯一目的就是提供一个合理的概念计划来管理软件系统的开发。
因此，这种计划可以作为一个基础规划，组织，人员配备，协调，预算编制，并指导软件开发活动。
自20世纪60年代，出现了许多经典的软件生命周期的描述（例如，霍西尔1961年，劳斯莱斯1970年，1976年博伊姆，迪斯塔索1980年，1984年斯卡基，萨默维尔1999年）。
罗伊斯（1970）使用现在生活中熟悉的“瀑布”图表，提出了周期的概念，这个图表概括了开发大型软件系统是多么的困难，因为它涉及复杂的工程任务，而这些任务在完成之前可能需要不断地返工。
这些图表也通常在介绍性发言中被采用，主要针对开发大型软件系统的人们（例如，定制软件的客户），他们可能不熟悉各种各样的技术问题但还是要必须解决这些问题。
这些经典的软件生命周期模型通常包括以下活动一些内容：系统启动/规划：系统从何而来？在大多数情况下，不论是现有的信息处理机制以前是自动的，手工的，还是非正式的，新系统都会取代或补充它们。
● 需求分析和说明书：阐述一个新的软件系统将要开发的问题：其业务能力，其所达到的性能特点，支持系统运行和维护所需的条件。
● 功能或原型说明：潜在确定计算的对象，它们的属性和关系，改变这些对象的操作，约束系统行为的限制等。
●划分与选择：给出需求和功能说明书，将系统分为可管理的模块，它们是逻辑子系统的标志，然后确定是否有对应于这些模块的新的，现有的，或可重复使用的软件系统可以复用。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
中英文对照外文翻译文献(文档含英文原文和中文翻译)A Systematic Review on Software measurement ProgramsTouseef Tahir, Ali JafarDepartment of computer science, Comsats institute of information technology, Lahore, Pakistan Blekinge institute of technology, SE 371 79, Karlskrona, SwedenAbstractMost of the measurement programs fail to achieve targeted goals. This paper presents outcomes of systematic review on software measurement programs. The aim of the study was to analyse Applications, success factors, existing measurement models/frameworks and tools. 1579 research studies were reviewed in the beginning and on basis of predefined criteria 28 studies were chosen for analysis. The selection of research studies was done on the basis of structured procedure of systematic review. Outcome of this study consists of observations and suggestions on the basis of analysis of selected studies.Keywords:Measurement Program；Software；Measurement Models；Measurement Framework1.INTRODUCTIONSoftware measurement programs (MP) help in both management andimplementation of software processes at each level of the organization. In order to get accurate results, it manages flow of data within the processes. The software products are becoming larger and more complex. By managing such software projects require accurate and precise estimations that can be helpful to provide a quality product to the customer. There should be a technological support and well defined structured approach to gather and process the data continuously throughout the software development. This process is called the measurement process. This is used in the MPs which is basically a set of procedures and guidelines to gather, calculate and evaluate the measures.According to, software MPs usually fail after implementation in a software development process. In, 50-80% of the MPs fail after a year due to different reasons. The most important reason of the failure of the MPs includes the lack of appropriate knowledge available to gain the required measures and/or too abstract goals. The failure of the software MP depends on different factors relevant to product,process and resources. According to, software MPs usually fail as they require expert judgment for selecting appropriate number of measures in relation to the organizational goals.There is a need to improve the measurement process; when there is difference between the expected outcome of the process and the actual performance of the process. In recent years, there are different models and frameworks developed that are used to measure different attributes of the software process. In assessment of the MP can be done according to different views i.e. process, product, resource, value based,context and social.In recent years, MPs assist a quantitative approach to development processes. These MPs also used in order to increase the software process improvement. Software MPs give a competitive advantage over those who prefer traditional approaches. These programs have been an important part of software development life cycle (SDLC) like other processes i.e. design, testing, and implementation.Measurement activities are carried out during the software life cycle of project.Implementing a MP is a well defined structured approach in order to gather andprocess the data continuously throughout the software development lifecycle. The main purpose of software measures is to extract good from the raw data, and MPs are used to apply these software measures in management and technical aspects. Software measures are used to classify the best practices i.e. Software Process Improvement, estimating and planning projects effectively,manage budget effectively, and it also helps comparison of current practices and tools. Software MPs provide a source for industry comparison and facilitate effective communication between developer and customer. MPs start with definition of goals and their respective questions which leads to formation of metrics. At start, an organization needs to set proper objectives for what they are going to do and then start measuring.This paper presents a systematic review (SR) on MPs, their applications, measurement models/frameworks and tools.Section II presents SR process definition and research questions. Section III presents SR planning process. Section IV presents selected primary study. Section V presents reporting process of SR. Section VI presents analysis and discussion. Section VII presents implementation of SR analysis. Section VIII presents conclusions.2.SYSTEMATIC REVIEWAccording to, the purpose of systematic review is to provide more structured way to make an assessment, identification and interpretation of research which is relevant to the specific research question.It has three phases namely “planning the review”, “conducting the review” and “reporting the review”. In the planning phase, it is defined that how literature review have been conducted in a systematic manner and a review protocol is developed which acts as a search guide during systematic literature review. In the second step, systematic literature review is conducted which involves primary studies, quality assessment, data extraction and data synthesis. In the last step, literature review is reported.Systematic review is an iterative process instead of sequential, because it involves a number of iteration. Example would be inclusion and exclusion criteria,when actual review is conducted several primary studies are included and excluded.A. Research QuestionsFollowing research questions will be answered during the systematic review:（1）RQ_1a: How do Organizations use software measurement programs?（2）RQ_1b: What are the success factors in software measurement programs?（3）RQ_2: What are the models/frameworks, and tools developed for measurement programs?3.PLANNING THE REVIEWReview is planned according to the guidelines given in.B. Review ProtocolReview protocol consists of inclusion/ exclusion criteria, search keywords, databases to be searched, quality assessment checklist, data synthesis, data extraction form and research questions. Review Protocol developed to identify the current state of the art in MPs and goal definition from 01 Jan, 1997 to 01 June, 2011.C. Search strategyAppropriate Search keywords are very important for effecting search process. This process is done by following the guidelines in. This has been done by following steps（1）Identification of search keywords by analysing the context, objectives, relevant area of research questions.（2）Searched resources were analysed for further identification of keywords, including the keywords section of research resources.（3）Identification of synonyms, alternatives and hypernyms for each key word.（4）Boolean OR was used for synonyms, alternatives, and hypernyms.（5）Boolean AND was used to make a search string and make searching precise The resulted search string given below:(metric OR measure OR measurement) AND (program OR plan OR process) AND (success OR important Or successful OR success story or good practices or practices) AND (factor OR feature OR variable) AND (Software OR software application OR software development life cycle OR software development process ORsoftware system OR software industry) AND (models OR guidelines or practices) AND(framework or structure infrastructure) AND (tool OR instrument OR mechanism or device).D.Primary search processThe search process is divided into two steps: primary and secondary research. The primary search process consisted of searching online research databases, search engines, e-journals,conference proceeding and grey literature using set of keywords in the resulted search string.In the first step 1579 articles were scanned and 69 articles were selected on the basis of title and abstract. In the second step selected articles were reviewed completed and final set of articles after the second step consists of 28 articles 。