首页 | 本学科首页   官方微博 | 高级检索  
文章检索
  按 检索   检索词:      
出版年份:   被引次数:   他引次数: 提示:输入*表示无穷大
  收费全文   84篇
  国内免费   1篇
  完全免费   15篇
  自动化技术   100篇
  2018年   7篇
  2017年   4篇
  2016年   1篇
  2015年   1篇
  2014年   3篇
  2013年   2篇
  2012年   1篇
  2011年   8篇
  2010年   4篇
  2009年   8篇
  2008年   10篇
  2007年   7篇
  2006年   8篇
  2005年   2篇
  2004年   3篇
  2003年   7篇
  2002年   4篇
  2001年   3篇
  2000年   3篇
  1999年   1篇
  1998年   4篇
  1997年   6篇
  1996年   1篇
  1992年   1篇
  1991年   1篇
排序方式: 共有100条查询结果,搜索用时 31 毫秒
1.
企业电子商务采纳与应用关键影响因素实证研究   总被引:5,自引:0,他引:5       下载免费PDF全文
以创新扩散理论与文献为依据构建了企业电子商务采纳与应用关键影响因素模型,并以长三角地区企业为主体进行了问卷调查。在利用SPSS对调查结果进行信度分析的基础上,采用结构方程模型对假设模型进行了实证,研究结论有助于企业认清自身所处的环境与条件,了解电子商务技术采纳行为形成的机理,有效管理电子商务技术采纳与应用活动。  相似文献
2.
回归测试中的测试用例优先排序技术述评   总被引:5,自引:4,他引:1       下载免费PDF全文
陈翔  陈继红  鞠小林  顾庆 《软件学报》2013,24(8):1695-1712
测试用例优先排序(test case prioritization,简称TCP)问题是回归测试研究中的一个热点.通过设定特定排序准则,对测试用例进行排序以优化其执行次序,旨在最大化排序目标,例如最大化测试用例集的早期缺陷检测速率.TCP问题尤其适用于因测试预算不足以致不能执行完所有测试用例的测试场景.首先对TCP问题进行描述,并依次从源代码、需求和模型这3个角度出发对已有的TCP技术进行分类;然后对一类特殊的TCP问题(即测试资源感知的TCP问题)的已有研究成果进行总结;随后依次总结实证研究中常用的评测指标、评测数据集和缺陷类型对实证研究结论的影响;接着依次介绍TCP技术在一些特定测试领域中的应用,包括组合测试、事件驱动型应用测试、Web服务测试和缺陷定位等;最后对下一步工作进行展望.  相似文献
3.
网络化软件的复杂网络特性实证   总被引:4,自引:2,他引:2       下载免费PDF全文
马于涛  何克清  李兵  刘婧 《软件学报》2011,22(3):381-407
互联网的普及和万维网的兴起,引发了软件技术的变革,催生了新的软件形态——网络化软件,为大众用户提供多样化、个性化的按需服务.随着应用领域的不断扩展和用户群的日益庞大,其规模与复杂度正以超越人类处理能力的速度增长,使得软件工程不得不面临一系列的挑战.为了科学地认识和理解这类规模庞大的人工复杂系统,从网络化-服务化-社会化的三维视角出发,对其基础设施、应用服务和大众交互三方面的复杂网络特性实证研究进行了综述分析,并系统论述了网络化软件中隐含的"小世界"和"无尺度"复杂网络特性对软件工程今后研究的影响和启示.软件工程与其他学科的交叉汇聚,将迸发新的观点和思想,为网络化软件的研究提供新的思维方式和方法论,有望实现软件工程理论、方法和关键技术的创新,从而推动我国软件服务业的快速发展.  相似文献
4.
Software Evolution and Software Evolution Processes   总被引:3,自引:0,他引:3  
Most of the software in regular use in businesses and organisations all over the world cannot be completely specified. It cannot be implemented, once and for all. Both the original implementation and the inevitable subsequent evolution (maintenance) are a continual learning experience driven, inter alia, by feedback from the results of the behaviour under execution of the software, as perceived by various stakeholders, by advances and growth in the user organisations and by adaptation to changes in the external world, both independent and as a result of installation and use of the software. Real world, termed type-E, software is essentially evolutionary in nature. The study of the processes of evolution of such software is of considerable interest, as is that of the domains that co-evolve with the software. After briefly discussing the meaning of the term evolution in the context of software, its technology, the software process and related domains, this paper describes some of the facets of the evolution phenomenon and implications to the evolution process as identified during many years of active interest in the topic.  相似文献
5.
Workflow Systems: Occasions for Success and Failure   总被引:3,自引:0,他引:3  
Workflow technologies have created considerable discussion within the computer supported cooperative work community. Although a number of theoretical and empirical warnings about the difficulties of workflow systems have appeared, the technologies continue to be built and sold. This paper examines the use of one workflow-like system and outlines three cases when the technology supported the work of its users. Comparing these successful occasions with some reports of difficulties, this paper draws conclusions about the circumstances that led to tool usage.  相似文献
6.
Persistent problems and practices in information systems development   总被引:1,自引:0,他引:1  
Abstract.  This paper identifies and discusses the persistent problems and development practices of information systems development (ISD). A critical examination and comparison of past times'traditional' and present-day 'web-based' development shows that contemporary ISD can be seen as an accentuated evolution – rather than a revolution – of well-known challenges and solutions. On this basis, (1) diversity; (2) knowledge; and (3) structure are identified as inherent and interrelated problems, while the practices for coping with these three challenges are (a) organization and specialization; (b) constant verbal communication and negotiation; and (c) pragmatic application of certain development methods and methodical concepts. We conclude that more research on the occurrence and interaction of problems and practices at, and between, different contextual levels (e.g. the business environment, company, project, team and individual levels) is needed to understand and assess (the gap between) 'observed practice' and 'good practice' across the many types of Web and non-Web ISD projects conducted today. We outline a possible research agenda to investigate these issues.  相似文献
7.
The influence of formal representation on solution specification   总被引:1,自引:1,他引:0  
The effectiveness and value of a notation is determined by how well its users are able to work with it. This paper reports upon an empirical study aiming at investigating the influence of employing the Z specification notation upon how users approach system development. The study illustrates how the desire to employ formality can have a significant influence upon preferred choice between different solution approaches. Despite the formal representation increasing the awareness of the characteristics of a given design problem, the notation is apparently detrimental in the subjects' consideration of good-quality generic solutions. The human factor issues of the notation need to be carefully considered and the notation should be embedded into a proper method if effective use is to be achieved.  相似文献
8.
An Empirically-Based Process for Software Architecture Evaluation   总被引:1,自引:0,他引:1  
Software systems undergo constant change causing the architecture of the system to degenerate over time. Reversing system degeneration takes extra effort and delays the release of the next version. Improved architecture is intangible and does not translate into visible user features that can be marketed. Due to a lack of representative metrics, technical staff has problems arguing that stopping degeneration is indeed necessary and that the effort will result in an improved architecture that will pay off. We believe that architectural metrics would give technical staff better tools to demonstrate that the architecture has improved. This paper defines and uses a set of architectural metrics and outlines a process for analyzing architecture to support such an argument. The paper reports on a case study from a project where we restructured the architecture of an existing client-server system written in Java while adding new functionality. The modules of the existing version of the system were library-oriented and had a disorganized communication structure. The new architecture is based on components and utilizes the mediator design pattern. The goal of the study is to evaluate the new architecture from a maintainability perspective. The paper describes our evaluation process, the metrics used, and provides some preliminary results. The architectural evaluation shows that the components of the system are only loosely coupled to each other and that an architectural improvement has occurred from a maintenance perspective. The process used to evaluate the architecture is general and can be reused in other contexts.  相似文献
9.
A case study of requirements engineering practice is reported. The application, a decision support system for the Greek Ministry of Health, was investigated by studying the process of requirements analysis through to design and implementation. A usability analysis was then conducted on the designed system with the users. Several usability problems were discovered, and interviews uncovered further problems with the system that could be attributed to failure in requirements engineering (RE). Even though requirements were explicitly stated and the system was an evolution from an existing legacy system, functionality was defective and usability was poor. The client’s prime concern for redeveloping the system was to improve usability; unfortunately communications problems in the RE process meant that the developers did not appreciate this. The implications for RE methods and understanding the RE process are discussed.  相似文献
10.
The mechanisms of project management of software development   总被引:1,自引:0,他引:1  
The changing environments of software development such as component-based, distributed and outsourced software development require matching changes by project managers to monitor, control and coordinate their projects. While the objectives of project management may be well established, the mechanisms with which those objectives are achieved are less well known. An empirical study was undertaken to investigate which mechanisms were used by practising project managers to monitor, control and coordinate software development projects.First, the types of mechanisms are discussed so that the mechanisms can be classified usefully. Then, the design of the empirical study is described. The data were collected through structured interview, which provided both quantitative and qualitative data. The data are analysed for each mechanism separately and the findings presented. The study found that project managers use multiple mechanisms to achieve project management objectives and use the same mechanism to serve multiple objectives. Further research is suggested to investigate project management from the opposite orientation, that is, which objectives are served by specific project management mechanisms.  相似文献
设为首页 | 免责声明 | 关于勤云 | 加入收藏

Copyright©北京勤云科技发展有限公司  京ICP备09084417号