全文获取类型
收费全文 | 56518篇 |
免费 | 2380篇 |
国内免费 | 2309篇 |
专业分类
电工技术 | 1882篇 |
技术理论 | 24篇 |
综合类 | 6261篇 |
化学工业 | 5962篇 |
金属工艺 | 1413篇 |
机械仪表 | 2356篇 |
建筑科学 | 13635篇 |
矿业工程 | 3515篇 |
能源动力 | 1718篇 |
轻工业 | 3779篇 |
水利工程 | 3001篇 |
石油天然气 | 3963篇 |
武器工业 | 266篇 |
无线电 | 1911篇 |
一般工业技术 | 2523篇 |
冶金工业 | 4233篇 |
原子能技术 | 174篇 |
自动化技术 | 4591篇 |
出版年
2024年 | 113篇 |
2023年 | 361篇 |
2022年 | 952篇 |
2021年 | 1222篇 |
2020年 | 1264篇 |
2019年 | 811篇 |
2018年 | 722篇 |
2017年 | 1036篇 |
2016年 | 1218篇 |
2015年 | 1350篇 |
2014年 | 3745篇 |
2013年 | 2897篇 |
2012年 | 3561篇 |
2011年 | 4159篇 |
2010年 | 3634篇 |
2009年 | 3511篇 |
2008年 | 3164篇 |
2007年 | 3971篇 |
2006年 | 4032篇 |
2005年 | 3590篇 |
2004年 | 3052篇 |
2003年 | 2695篇 |
2002年 | 2214篇 |
2001年 | 1899篇 |
2000年 | 1568篇 |
1999年 | 1086篇 |
1998年 | 809篇 |
1997年 | 578篇 |
1996年 | 428篇 |
1995年 | 313篇 |
1994年 | 248篇 |
1993年 | 163篇 |
1992年 | 149篇 |
1991年 | 95篇 |
1990年 | 77篇 |
1989年 | 70篇 |
1988年 | 44篇 |
1987年 | 38篇 |
1986年 | 36篇 |
1985年 | 47篇 |
1984年 | 28篇 |
1983年 | 17篇 |
1982年 | 18篇 |
1981年 | 21篇 |
1980年 | 14篇 |
1979年 | 16篇 |
1965年 | 11篇 |
1964年 | 11篇 |
1959年 | 11篇 |
1955年 | 16篇 |
排序方式: 共有10000条查询结果,搜索用时 15 毫秒
121.
The evolution of the amorphous structure of starch was characterized during the drying process by real‐time X‐ray wide‐angle scattering. The X‐ray diffractograms of injection‐molded starch show two superposed, rather broad, scattering maxima indicative of noncrystalline structures. The location of the two peaks has been associated to disordered starch single helices. A third maximum that arises upon drying the material in vacuum is associated to the scattering emerging from regions containing double helices. A model for the starch network is proposed, assuming a primary and a secondary component. The wider, temperature stable component appearing first, is correlated to the entanglement network of the melt. The narrower network component, which is created later, at lower temperature (secondary network), is explained by the formation of double helix regions that densify the wider primary network. The secondary network is increased strongly by the drying process. X‐ray experiments performed during the penetration of water, provoking a higher molecular mobility, reveal a better‐packed helical structure that becomes the precursor of a double helix crystalline formation. When temperature increases, the secondary network is dissolved and water molecules arrange themselves in better‐organized crystals as strongly bound crystal water. © 2005 Wiley Periodicals, Inc. J Appl Polym Sci 99: 1880–1886, 2006 相似文献
122.
123.
介绍了15kt/a本体苯乙烯-丙烯腈(SAN)装置试生产打火机专用SAN树脂的生产情况,确定了主要工艺配方及参数:进料组成为乙苯浓度为6%-11%、丙烯腈浓度为30%-42%,聚合温度130-145℃、压力0.40-0.46MPa,搅拌转速60-90r/min,脱挥温度215-250℃、压力小于等于4kPa;并对影响打火机志用SAN树脂性能的主要工艺条件及因素进行了讨论。结果表明,聚合温度、结合丙烯腈含量、熔体流动指数、转化率是影响打火机专用SAN树脂生产工艺及产品性能的主要因素。 相似文献
124.
《Information and Software Technology》2014,56(1):6-19
ContextIn the era of globally-distributed software engineering, the practice of global software testing (GST) has witnessed increasing adoption. Although there have been ethnographic studies of the development aspects of global software engineering, there have been fewer studies of GST, which, to succeed, can require dealing with unique challenges.ObjectiveTo address this limitation of existing studies, we conducted, and in this paper, report the findings of, a study of a vendor organization involved in one kind of GST practice: outsourced, offshored software testing.MethodWe conducted an ethnographically-informed study of three vendor-side testing teams over a period of 2 months. We used methods, such as interviews and participant observations, to collect the data and the thematic-analysis approach to analyze the data.FindingsOur findings describe how the participant test engineers perceive software testing and deadline pressures, the challenges that they encounter, and the strategies that they use for coping with the challenges. The findings reveal several interesting insights. First, motivation and appreciation play an important role for our participants in ensuring that high-quality testing is performed. Second, intermediate onshore teams increase the degree of pressure experienced by the participant test engineers. Third, vendor team participants perceive productivity differently from their client teams, which results in unproductive-productivity experiences. Lastly, participants encounter quality-dilemma situations for various reasons.ConclusionThe study findings suggest the need for (1) appreciating test engineers’ efforts, (2) investigating the team structure’s influence on pressure and the GST practice, (3) understanding culture’s influence on other aspects of GST, and (4) identifying and addressing quality-dilemma situations. 相似文献
125.
《Information and Software Technology》2014,56(5):477-494
ContextAlthough Agile software development models have been widely used as a base for the software project life-cycle since 1990s, the number of studies that follow a sound empirical method and quantitatively reveal the effect of using these models over Traditional models is scarce.ObjectiveThis article explains the empirical method of and the results from systematic analyses and comparison of development performance and product quality of Incremental Process and Agile Process adapted in two projects of a middle-size, telecommunication software development company. The Incremental Process is an adaption of the Waterfall Model whereas the newly introduced Agile Process is a combination of the Unified Software Development Process, Extreme Programming, and Scrum.MethodThe method followed to perform the analyses and comparison is benefited from the combined use of qualitative and quantitative methods. It utilizes; GQM Approach to set measurement objectives, CMMI as the reference model to map the activities of the software development processes, and a pre-defined assessment approach to verify consistency of process executions and evaluate measure characteristics prior to quantitative analysis.ResultsThe results of the comparison showed that the Agile Process had performed better than the Incremental Process in terms of productivity (79%), defect density (57%), defect resolution effort ratio (26%), Test Execution V&V Effectiveness (21%), and effort prediction capability (4%). These results indicate that development performance and product quality achieved by following the Agile Process was superior to those achieved by following the Incremental Process in the projects compared.ConclusionThe acts of measurement, analysis, and comparison enabled comprehensive review of the two development processes, and resulted in understanding their strengths and weaknesses. The comparison results constituted objective evidence for organization-wide deployment of the Agile Process in the company. 相似文献
126.
《Information and Software Technology》2014,56(10):1403-1420
ContextSystem of systems (SoS) is a set or arrangement of systems that results when independent and useful systems are to be incorporated into a larger system that delivers unique capabilities. Our investigation showed that the development life cycle (i.e. the activities transforming requirements into design, code, test cases, and releases) in SoS is more prone to bottlenecks in comparison to single systems.ObjectiveThe objective of the research is to identify reasons for bottlenecks in SoS, prioritize their significance according to their effect on bottlenecks, and compare them with respect to different roles and different perspectives, i.e. SoS view (concerned with integration of systems), and systems view (concerned with system development and delivery).MethodThe research method used is a case study at Ericsson AB.ResultsResults show that the most significant reasons for bottlenecks are related to requirements engineering. All the different roles agree on the significance of requirements related factors. However, there are also disagreements between the roles, in particular with respect to quality related reasons. Quality related hinders are primarily observed and highly prioritized by quality assurance responsibles. Furthermore, SoS view and system view perceive different hinders, and prioritize them differently.ConclusionWe conclude that solutions for requirements engineering in SoS context are needed, quality awareness in the organization has to be achieved end to end, and views between SoS and system view need to be aligned to avoid sub optimization in improvements. 相似文献
127.
《Information and Software Technology》2014,56(5):506-515
ContextWhile project management success factors have long been established via the golden triangle, little is known about how project iteration objectives and critical decisions relate to these success factors. It seems logical that teams’ iteration objectives would reflect project management success factors, but this may not always be the case. If not, how are teams’ objectives for iterations differing from the golden triangle of project management success factors?ObjectiveThis study identifies iteration objectives and the critical decisions that relate to the golden triangle of project management success factors in agile software development teams working in two-week iterations.MethodThe author conducted semi-structured interviews with members across three different agile software development teams using a hybrid of XP and Scrum agile methodologies. Iteration Planning and Retrospective meetings were also observed. Interview data was transcribed, coded and reviewed by the researcher and two independently trained research assistants. Data analysis involved organizing the data to identify iteration objectives and critical decisions to identify whether they relate to project management success factors.ResultsAgile teams discussed four categories of iteration objectives: Functionality, Schedule, Quality and Team Satisfaction. Two of these objectives map directly to two aspects of the golden triangle: schedule and quality. The agile teams’ critical decisions were also examined to understand the types of decisions the teams would have made differently to ensure success, which resulted in four categories of such decisions: Quality, Dividing Work, Iteration Amendments and Team Satisfaction.ConclusionThis research has contributed to the software development and project management literature by examining iteration objectives on agile teams and how they relate to the golden triangle of project management success factors to see whether these teams incorporate the golden triangle factors in their objectives and whether they include additional objectives in their iterations. What’s more, this research identified four critical decisions related to the golden triangle. These findings provide important insight to the continuing effort to better assess project management success, particularly for agile teams. 相似文献
128.
《Information and Software Technology》2014,56(8):873-889
ContextEmpowerment of employees at work has been known to have a positive impact on job motivation and satisfaction. Software development is a field of knowledge work wherein one should also expect to see these effects, and the idea of empowerment has become particularly visible in agile methodologies, in which proponents emphasise team empowerment and individual control of the work activities as a central concern.ObjectiveThis research aims to get a better understanding of how empowerment is enabled in software development teams, both agile and non-agile, to identify differences in empowering practices and levels of individual empowerment.MethodTwenty-five interviews with agile and non-agile developers from Norway and Canada on decision making and empowerment are analysed. The analysis is conducted using a conceptual model with categories for involvement, structural empowerment and psychological empowerment.ResultsBoth kinds of development organisations are highly empowered and they are similar in most aspects relating to empowerment. However, there is a distinction in the sense that agile developers have more possibilities to select work tasks and influence the priorities in a development project due to team empowerment. Agile developers seem to put a higher emphasis on the value of information in decision making, and have more prescribed activities to enable low-cost information flow. More power is obtained through the achievement of managing roles for the non-agile developers who show interest and are rich in initiatives.ConclusionAgile developers have a higher sense of being able to impact the organisation than non-agile developers and have information channels that is significantly differently from non-agile developers. For non-agile teams, higher empowerment can be obtained by systematically applying low-cost participative decision making practices in the manager–developer relation and among peer developers. For agile teams, it is essential to more rigorously follow the empowering practices already established. 相似文献
129.
《Expert systems with applications》2014,41(5):2222-2230
Using competitions to motivate students is a well-known practice that has proved to be successful. Nevertheless, grading students only through their results in the competition could unfairly limit the range of grades that each student can get: regardless of the quality of the different teams participating, one student must necessarily win the tournament, another must be second, and so on until the last place. In fact, player rankings are relative assessments that are conditioned by the performance of every student. In this paper, we propose solving this issue by making students do a code review before betting on the competition. By betting, the grade of students depends both on the performance of their own solution and the one they bet on. This way, grades represent not only coding skills, but also code analysis skills, widening the attainable range of grades and allowing for a fairer grade distribution. As a result, students that are not so proficient in coding are rewarded if they demonstrate they can do a good analysis of the source code written by others, which is a very valuable skill in the professional world. We provide a case study in an undergraduate course, showing positive results. 相似文献
130.