Статті в журналах з теми "Requirements changes"

Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Requirements changes.

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Requirements changes".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.

1

Pimentel, João, Emanuel Santos, Jaelson Castro, and Xavier Franch. "Anticipating Requirements Changes-Using Futurology in Requirements Elicitation." International Journal of Information System Modeling and Design 3, no. 2 (April 2012): 89–111. http://dx.doi.org/10.4018/jismd.2012040104.

Повний текст джерела
Анотація:
It is well known that requirements changes in a later phase of software developments is a major source of software defects and costs. Thus, the need of techniques to control or reduce the amount of changes during software development projects. The authors advocate the use of foresight methods as a valuable input to requirements elicitation, with the potential to decrease the number of changes that would be required after deployment, by anticipating them. In this paper, the authors define a process for using a foresight method, namely Futures Wheel, for requirements elicitation. To illustrate the use of this approach, the authors perform a case study using a route planning system.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Loeb, Josh. "Changes ahead for EMS requirements." Veterinary Record 191, no. 9 (November 2022): 358. http://dx.doi.org/10.1002/vetr.2396.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Lin, Lan, and Jesse H. Poore. "Pushing requirements changes through to changes in specifications." Frontiers of Computer Science in China 2, no. 4 (November 6, 2008): 331–43. http://dx.doi.org/10.1007/s11704-008-0034-7.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Zhang, Yirui, Ying Jin, Jianxiu Bai, and Jing Zhang. "A Negotiation Framework for Managing the Requirements Changes." Cybernetics and Information Technologies 13, Special-Issue (December 1, 2013): 75–87. http://dx.doi.org/10.2478/cait-2013-0039.

Повний текст джерела
Анотація:
Abstract The consistent system requirements set is the basis of successful software projects. The requirements change is very usual in a software project, and it may cause inconsistency of the requirements set, and become the key factor that affects the quality of the requirements and the software. Aiming at the problem of requirements inconsistencies caused by the requirements change, this paper proposes a compromise-based negotiation framework to manage the requirements changes, illustrates the efficiency of the proposed method by a software engineering case, gives a contrast experiment with the current mainstream method, and finally gives a comparison with the related work and a conclusion. The experimental results show that the framework proposed in this paper is more flexible and accurate than the results of the current popular framework, so it is more suitable for the requirement changes management.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Al-Saiyd, Nedhal A. "A Multistep Approach for Managing the Risks of Software Requirements Volatility." Computer and Information Science 9, no. 1 (January 31, 2016): 101. http://dx.doi.org/10.5539/cis.v9n1p101.

Повний текст джерела
Анотація:
<p><span style="font-size: 10.5pt; font-family: 'Times New Roman','serif'; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 宋体; mso-font-kerning: 1.0pt; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;" lang="EN-US">Software is changed continuously in order to respond to different users and business needs. Requirements are changed dynamically to improve software usability and increase its value, but requirement volatility sometimes cause failures for many projects because of inadequate understanding of the changing causes and the consequences of these changes. This research highlights the importance of managing requirement changes, classify them, and control the impact risks of requirement volatility on software project. The proposed model is designed based on software requirements risks factors and how to reduce their impacts. Generally, requirements changing is considered as a difficult, costly and time-consumed task, and consequently it is too important to study the inter-relationships between the changes and their impacts on the other phases of software system. The good understanding of the changing causes and their consequences can improve and support requirements management process and also lead successfully to the predicted goals of changes. The high quality of the requirements influences the success of a software project during software development and maintenance processes.</span></p>
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Liew, Su May. "Changes to manuscript requirements and website." Malaysian Family Physician 16, no. 1 (March 25, 2021): 1. http://dx.doi.org/10.51866/ed0001.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Brandom, Barbara W., and Peter J. Davis. "Changes in drug requirements during growth." Current Opinion in Anaesthesiology 5, no. 3 (June 1992): 374–79. http://dx.doi.org/10.1097/00001503-199205030-00014.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Dodd, Leslie G. "Changes to cytopathology training program requirements." Diagnostic Cytopathology 42, no. 5 (September 18, 2013): 373–74. http://dx.doi.org/10.1002/dc.23037.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Kohl, R. J. "Requirements engineering changes for COTS-intensive systems." IEEE Software 22, no. 4 (July 2005): 63–64. http://dx.doi.org/10.1109/ms.2005.104.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Klamert, Patricia Coleen, and Joy E. Wachs. "Complying with Changes in OSHA's Recordkeeping Requirements." AAOHN Journal 50, no. 7 (July 2002): 324–35. http://dx.doi.org/10.1177/216507990205000710.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
11

Wetzel, R. G. "Freshwater ecology: changes, requirements, and future demands." Limnology 1, no. 1 (April 28, 2000): 3–9. http://dx.doi.org/10.1007/s102010070023.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
12

Bai, Jianxiu, Ying Jin, Yirui Zhang, and Jing Zhang. "An Improved Framework for Managing Requirements Changes." International Journal of Hybrid Information Technology 6, no. 6 (November 30, 2013): 249–58. http://dx.doi.org/10.14257/ijhit.2013.6.6.22.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
13

Janes, Andrea, Tadas Remencius, Alberto Sillitti, and Giancarlo Succi. "Managing changes in requirements: an empirical investigation." Journal of Software: Evolution and Process 25, no. 12 (June 5, 2013): 1273–83. http://dx.doi.org/10.1002/smr.1602.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
14

Abdullahi, Shamsu, Musa Ahmed Zayyad, Naziru Yusuf, Lawal Idris Bagiwa, Amina Nura, Abubakar Zakari, and Babangida Dansambo. "Software Requirements Negotiation: A Review on Challenges." International Journal of Innovative Computing 11, no. 1 (April 28, 2021): 1–6. http://dx.doi.org/10.11113/ijic.v11n1.264.

Повний текст джерела
Анотація:
Requirements negotiation involves discussion on the requirements conflict to have some compromise that will satisfy the participating stakeholders of a software project. The output of a requirement negotiation is a set of satisfied requirements of two or more parties. In this paper, we present a systematic review of requirements negotiation challenges. The study adopted 34 papers from the final study selection process which were analyzed based on the requirements negotiation challenges they addressed. The identified challenges are decision-making, communication, performance, managing requirement changes, and conflict resolution. The output of the study indicates that decision-making is addressed by 33% of the studies reviewed, followed by the performance with 22%, conflict resolution with 19%, while 16% focus on stakeholders’ communication, and managing requirements changes has 10%.
Стилі APA, Harvard, Vancouver, ISO та ін.
15

Wahlström, Åsa, and Mari-Liis Maripuu. "Additional requirement to the Swedish nearly zero energy requirements." E3S Web of Conferences 246 (2021): 14002. http://dx.doi.org/10.1051/e3sconf/202124614002.

Повний текст джерела
Анотація:
This study has analysed which options would be appropriate to use as additional requirements to the main requirement of primary energy number in the new Swedish building regulations. The starting point is to ensure that buildings are built with good qualitative properties in terms of the building envelope so that low energy use can be maintained throughout the life of the building despite changes in installation systems or the building’s occupancy. The additional requirements should aim to minimize energy losses, i.e., to ensure that the building's total energy demand is low. The following possible additional requirements have been examined: net energy demand, net energy demand for heating, heat power demand, heat loss rate and average heat transfer coefficient. In order to ensure that the additional requirements will work as desired and to explore possibilities with, and identify the consequences of, the various proposals, calculations have been made for four different categories of buildings: single-family houses, apartment buildings, schools and offices. The results show that the suggested option net energy demand will not contribute to any additional benefits in relation to primary energy number. The other options analysed have both advantages and disadvantages and it is difficult to find a single additional requirement that fulfils all the pre-set demands.
Стилі APA, Harvard, Vancouver, ISO та ін.
16

Tan, Qian. "Development of Automatic English Translation System Based on Fuzzy Matching and Software Simulation." Mobile Information Systems 2022 (July 20, 2022): 1–10. http://dx.doi.org/10.1155/2022/7795836.

Повний текст джерела
Анотація:
Software requirements are changeable, and the changes in requirements have led to many technical, economic, and management problems in the software development process, which are also considered to be the main source of software development risks. Based on the relationship between software requirements and design, this article analyzes the propagation process of requirement changes and the two dimensions of requirement change risk, opportunity and impact, and discusses software architecture customization that combines requirements, software architecture, and risk. On the basis of QFD and DSM, a composite relationship matrix is created according to requirements and software architecture, and two aspects of software architecture adaptability are analyzed from the perspective of the risk of changes in requirements. With the advent of the 5G era, this issue has gradually been paid attention to in its evolution. In order to further improve the intelligence level of the English translation system and improve the accuracy of English translation, this paper designs a translation algorithm that takes the changes in software requirements as the basis. On this basis, cross-compilation and multithreaded phrase translation loading methods are used to automate the translation system. System test results show that the system has high translation accuracy and good intelligence. Overall, the development of an automatic English translation system based on software change management and 5G networks will further enhance the intelligence and automation of English translation.
Стилі APA, Harvard, Vancouver, ISO та ін.
17

Ledashcheva, Tatyana N., and Vladimir E. Pinaev. "Environmental baseline assessment - changes 2022." RUDN Journal of Ecology and Life Safety 29, no. 4 (December 30, 2021): 381–85. http://dx.doi.org/10.22363/2313-2310-2021-29-4-381-385.

Повний текст джерела
Анотація:
The article examines the changes in the requirements of the legislation of the Russian Federation on the assessment of the current state of the environment carried out within the framework of engineering and environmental surveys and the requirements for the preparation of project documentation in terms of environmental impact assessment. Taking into account the updated requirements of legislation is important, not only in the preparation of project documentation - environmental impact assessment and a list of environmental protection measures, but also in the training of environmental specialists. It is essential that the graduate students are aware of the requirements of the legislation and understands that the legislation is subject of change.
Стилі APA, Harvard, Vancouver, ISO та ін.
18

Jerabek,, Zbynek, and Eva Caposova. "INSTITUTIONAL CHANGES AND QUALIFICATION REQUIREMENTS OF A COMPANY." Polish Journal of Management Studies 14, no. 2 (June 2016): 93–103. http://dx.doi.org/10.17512/pjms.2016.14.2.09.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
19

Hammill, M. O., M. Ryg, and D. Chabot. "Seasonal Changes in Energy Requirements of Harp Seals." Journal of Northwest Atlantic Fishery Science 42 (April 20, 2010): 135–52. http://dx.doi.org/10.2960/j.v42.m660.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
20

Moran, Mark. "Changes in MOC Requirements Could Ease Certification Process." Psychiatric News 49, no. 22 (November 21, 2014): 1. http://dx.doi.org/10.1176/appi.pn.2014.11b4.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
21

Allen, Richard G., Francis N. Gichuki, and Cynthia Rosenzweig. "CO2‐Induced Climatic Changes and Irrigation‐Water Requirements." Journal of Water Resources Planning and Management 117, no. 2 (March 1991): 157–78. http://dx.doi.org/10.1061/(asce)0733-9496(1991)117:2(157).

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
22

Lukaski, Henry C., and James G. Penland. "Functional Changes Appropriate for Determining Mineral Element Requirements." Journal of Nutrition 126, suppl_9 (September 1, 1996): 2354S—2364S. http://dx.doi.org/10.1093/jn/126.suppl_9.2354s.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
23

AULT, ALICIA. "CMS Proposes Changes to Ease E-Prescribing Requirements." Cardiology News 9, no. 7 (July 2011): 35. http://dx.doi.org/10.1016/s1544-8800(11)70234-2.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
24

Mian, Shehzad L., and Clifford W. Smith. "Incentives associated with changes in consolidated reporting requirements." Journal of Accounting and Economics 13, no. 3 (October 1990): 249–66. http://dx.doi.org/10.1016/0165-4101(90)90033-z.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
25

Hron, J. "New economy and manager behaviour changes." Agricultural Economics (Zemědělská ekonomika) 50, No. 1 (February 24, 2012): 9–12. http://dx.doi.org/10.17221/5160-agricecon.

Повний текст джерела
Анотація:
The article reflects recent developments in factors affecting business behaviour both externally and internally. Derived form these changes, business managers&rsquo; competences are assessed in accordance with changing requirements on managers&rsquo; behaviour. Competences are then described in terms of specific and technical competences.
Стилі APA, Harvard, Vancouver, ISO та ін.
26

Norsworthy, Jason K., and Marcos J. Oliveira. "Changes inSenna obstuifoliaGermination Requirements over 12 Months under Field Conditions." International Journal of Agronomy 2009 (2009): 1–5. http://dx.doi.org/10.1155/2009/935205.

Повний текст джерела
Анотація:
Senna obtusifoliaseeds were collected in Fall 2003 and immediately field sown to assess dormancy alleviation and effect of after-ripening over a 12-month period on light and temperature requirements for germination. Seeds did not exhibit physical dormancy at maturation and readily germinated over a broad range of light and thermal conditions. Dormancy gradually increased during Winter months, resulting in only a small fraction of the population capable of germination by early Spring. Dormancy break did not occur at a specific time of the year nor did dormancy alleviation increase over the 12-month period following maturation. Conditions during Spring and Summer coincided with thermal requirements for germination of the nondormant fraction of the population.Senna obtusifoliaseeds were nonresponsive to red and far-red lights, and seeds did not acquire a light requirement following burial for 6 months.
Стилі APA, Harvard, Vancouver, ISO та ін.
27

Joshi, Shraddha, and Joshua D. Summers. "Requirements change: Understanding the type of changes in the requirements document of novice designers." International Journal of Mechanical Engineering Education 43, no. 4 (October 2015): 286–304. http://dx.doi.org/10.1177/0306419015612348.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
28

Vaux, D. L., S. Wilhelm, and G. Häcker. "Requirements for proteolysis during apoptosis." Molecular and Cellular Biology 17, no. 11 (November 1997): 6502–7. http://dx.doi.org/10.1128/mcb.17.11.6502.

Повний текст джерела
Анотація:
The key effector proteins of apoptosis are a family of cysteine proteases termed caspases. Following activation of caspases, biochemical events occur that lead to DNA degradation and the characteristic morphological changes associated with apoptosis. Here we show that cytoplasmic extracts activated in vitro by proteinase K were able to cleave the caspase substrate DEVD-7-amino-4-methylcoumarin, while neither proteinase K nor nonactivated extracts were able to do so alone. Caspase-like activity was inhibited by the specific caspase inhibitor DEVD-aldehyde and by the protease inhibitor iodoacetamide, but not by N-ethylmaleimide. When added to isolated nuclei, the activated extracts caused internucleosomal DNA degradation and morphological changes typical of apoptosis. As DNA cleavage and morphological changes could be inhibited by N-ethylmaleimide but not by iodoacetamide, we conclude that during apoptosis, caspase activation causes activation of another cytoplasmic enzyme that can be inhibited by N-ethylmaleimide. Activity of this enzyme is necessary for activation of endonucleases, DNA cleavage, and changes in nuclear morphology.
Стилі APA, Harvard, Vancouver, ISO та ін.
29

Liu, Wei, Chen Wan He, and Zai Wen Feng. "Requirement Uncertainty Modeling for Service Oriented Self-Adaptive Software." Advanced Materials Research 433-440 (January 2012): 4798–801. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.4798.

Повний текст джерела
Анотація:
Service-oriented software utilizes services as fundamental elements for developing applications that have the capability to autonomously modify their behavior at run-time in response to changes in their environment. While a few techniques have been developed to support the modeling and analysis of requirements for self-adaptive systems, limited attention has been paid to the description of service requirements and uncertainty in requirements of service-oriented software. In this paper, we propose a task solving strategy for requirement analysis and modeling framework as a fundamental of self-adaptation evolution. We introduce task solving strategy method for requirement analysis process; a context snapshot model to represent uncertainty in requirement with domain knowledge; goal-oriented context requirement to model user requirements and process-oriented context requirement to model service requirements; and finally, propose means-c-end analysis to relate user and service requirement with context condition.
Стилі APA, Harvard, Vancouver, ISO та ін.
30

Gupta, Varun, D. S. Chauhan, and Kamlesh Dutta. "Regression Testing-Based Requirement Prioritization of Mobile Applications." International Journal of Systems and Service-Oriented Engineering 3, no. 4 (October 2012): 20–39. http://dx.doi.org/10.4018/jssoe.2012100102.

Повний текст джерела
Анотація:
Mobile software application development process must be matured enough to handle the challenges (especially market related) associated with the development of high quality mobile software development. Ever increasing number of both mobile users and mobile applications had presented software engineers with the challenge of satisfying billions of users with high quality software applications to be delivered within deadline and budgets. Always there had been a lot of pressure to develop complex software categorized by thousands of requirements, under resource constrained environment. Requirement prioritization is one of the activities undertaken by software engineer to deliver partial software product to its customers such that most important requirements are implemented in the earliest releases. During next releases some changed and pending requirements are implemented, an activity that generates ripple effects. Such ripple effects need to be tested by executing modified source code against test cases of previous releases (regression testing). Regression testing is a very effortful activity that requires a software tester to select test cases that have high fault detection capability, execute the modified code against selected test cases and performing debugging. This regression testing activity can be lowered to the maximum extend by considering dependencies between requirements during the time of requirement prioritization. Thus requirement prioritization will be carried out not only against aspects like cost, time, risks, business values etc but against dependencies also. The aim is to implement almost all dependent highest priority requirements in current release so that implementation of new requirements is unlikely to have ripple effects. Changes in requirements might not be related to variable usage and definition and might not involve a change in functionality. In such cases there is no need to select already executed test cases of previous versions. Module dependencies can lead to test case selections of previous versions if changes of requirement lead to ripple effects. This paper aims to implement highest priority requirements such that regression testing is performed to minimum thereby improving development process of mobile applications. The proposed technique had been successfully evaluated on Android based notification software application that meets the specification of Aakash tablets.
Стилі APA, Harvard, Vancouver, ISO та ін.
31

Stauffer, Robert F. "Back to Basics: Reserve Requirements and Money Stock Changes, 1929–1936." American Economist 44, no. 1 (March 2000): 62–69. http://dx.doi.org/10.1177/056943450004400108.

Повний текст джерела
Анотація:
This paper explains how the shift of deposits from nonmember banks and country banks to larger member banks increased the average or “effective” reserve requirement in the 1929–1936 period. The result was an inappropriate tightening of monetary conditions, along with liquidity problems for those banks most susceptible to failure. A basic money multiplier model is developed to help clarify the possible impact of increases in effective reserve requirements. The resulting perspective strengthens the usual charges against the Federal Reserve of monetary policy malfeasance during the Great Depression.
Стилі APA, Harvard, Vancouver, ISO та ін.
32

Jayatilleke, Shalinka, Richard Lai, and Karl Reed. "Managing software requirements changes through change specification and classification." Computer Science and Information Systems 15, no. 2 (2018): 321–46. http://dx.doi.org/10.2298/csis161130041j.

Повний текст джерела
Анотація:
Software requirements changes are often inevitable due to the changing nature of running a business and operating the Information Technology (IT) system which supports the business. As such, managing software requirements changes is an important part of software development. Past research has shown that failing to manage software requirements changes effectively is a main contributor to project failure. One of the difficulties in managing requirements changes is the lack of effective methods for communicating changes from the business to the IT professionals. In this paper, we present an approach to managing requirements change by improving the change communication and elicitation through a method of change specification and a method of classification. Change specification provides a way such that communication ambiguities can be avoided between business and IT staff. The change classification mechanism identifies the type of the changes to be made and preliminary identification of the actions to be taken. We illustrate the usefulness of the methods by applying them to a case study of course management system.
Стилі APA, Harvard, Vancouver, ISO та ін.
33

Battistoni, Paolo, and Gabriele Fava. "Fish Processing Wastewater Treatment Requirements by Line Production Changes." Water Science and Technology 29, no. 9 (May 1, 1994): 111–19. http://dx.doi.org/10.2166/wst.1994.0455.

Повний текст джерела
Анотація:
An Italian seafood factory, engaged in the preparation of retail fish products, was investigated. The behaviour of the wastewater treatment plant constituted by a low load biological oxidation, with nitrogen denitrification was studied. Operative difficulties connected with the quali-quantitative changes in the industrial production are evidenced. The major points outlined are: start-up at design conditions, four years' management at extended oxidation (SRT = 80 days), discharge lines organization to assure plant efficiency after introducing seafood prefrying production.
Стилі APA, Harvard, Vancouver, ISO та ін.
34

NAKATANI, Takako, Shouzo HORI, Naoyasu UBAYASHI, Keiichi KATAMINE, and Masaaki HASHIMOTO. "A Case Study of Requirements Elicitation Process with Changes." IEICE Transactions on Information and Systems E93-D, no. 8 (2010): 2182–89. http://dx.doi.org/10.1587/transinf.e93.d.2182.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
35

Larson, David B. "Major Changes in Radiology Residency Program Requirements Are Coming." American Journal of Roentgenology 188, no. 1 (January 2007): 3–4. http://dx.doi.org/10.2214/ajr.07.6100.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
36

D. Aljohani, Mohammad, and M. Rizwan J. Qureshi. "Management of Changes in Software Requirements during Development Phases." International Journal of Education and Management Engineering 6, no. 6 (November 8, 2016): 12–26. http://dx.doi.org/10.5815/ijeme.2016.06.02.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
37

Gaiser, Robert. "Do Physiological Changes in Pregnancy Change Defibrillation Energy Requirements?" Survey of Anesthesiology 46, no. 3 (June 2002): 148–49. http://dx.doi.org/10.1097/00132586-200206000-00031.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
38

Bustard, D. W., and A. C. Winstanley. "Making changes to formal specifications: requirements and an example." IEEE Transactions on Software Engineering 20, no. 8 (1994): 562–68. http://dx.doi.org/10.1109/32.310666.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
39

Griffith, Richard. "Deprivation of liberty safeguard deaths: changes to reporting requirements." British Journal of Nursing 26, no. 7 (April 13, 2017): 428–29. http://dx.doi.org/10.12968/bjon.2017.26.7.428.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
40

Avigad, Gideon, Erella Eisenstadt, and Oliver Schuetze. "Handling changes of performance requirements in multi-objective problems." Journal of Engineering Design 23, no. 8 (November 14, 2011): 597–617. http://dx.doi.org/10.1080/09544828.2011.630656.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
41

R. F. Stevenson, D. R. Buckmaster, and P. M. Anderson. "Energy Requirements and Quality Changes in Steam-blanched Alfalfa." Transactions of the ASAE 37, no. 5 (1994): 1409–15. http://dx.doi.org/10.13031/2013.28221.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
42

Ector, Walton L., Melissa A. Campbell, and Paul M. Darden. "Recent Changes in Residency Requirements for Pediatrics: Who Agrees?" Clinical Pediatrics 37, no. 10 (October 1998): 625–30. http://dx.doi.org/10.1177/000992289803701006.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
43

Nanson, J., D. Elcock, M. Williams, and C. D. Deakin. "Do physiological changes in pregnancy change defibrillation energy requirements?" British Journal of Anaesthesia 87, no. 2 (August 2001): 237–39. http://dx.doi.org/10.1093/bja/87.2.237.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
44

Mu, Ke-Dian, Weiru Liu, Zhi Jin, Jun Hong, and David Bell. "Managing Software Requirements Changes Based on Negotiation-Style Revision." Journal of Computer Science and Technology 26, no. 5 (September 2011): 890–907. http://dx.doi.org/10.1007/s11390-011-0187-y.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
45

van Ooijen, P. M. A., P. J. M. ten Bhomer, and M. Oudkerk. "PACS storage requirements—influence of changes in imaging modalities." International Congress Series 1281 (May 2005): 888–93. http://dx.doi.org/10.1016/j.ics.2005.03.038.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
46

Strife, Janet L., and E. Stephen Amis. "Changes in ACGME program requirements for pediatric radiology fellowships." Pediatric Radiology 40, no. 7 (May 25, 2010): 1312–14. http://dx.doi.org/10.1007/s00247-010-1679-6.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
47

Bennett, Porter B. "Changes and Marketing Requirements of the Electric Generation Market." Natural Gas 10, no. 3 (August 20, 2008): 1–7. http://dx.doi.org/10.1002/gas.3410100302.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
48

Bosshardt, William, Michael Watts, and William E. Becker. "Course Requirements for Bachelor's Degrees in Economics." American Economic Review 103, no. 3 (May 1, 2013): 643–47. http://dx.doi.org/10.1257/aer.103.3.643.

Повний текст джерела
Анотація:
We conducted a national survey of department Chairs to investigate whether departments of economics changed course requirements for bachelors degrees since the Siegfried and Bidani (1992) paper using 1980 data. There have been few changes to course requirements. Most notable are a large increase in the number of departments requiring econometrics and a drop in departments requiring courses such as money, banking and economic history--courses once required in many business schools.
Стилі APA, Harvard, Vancouver, ISO та ін.
49

Dai, Peng, Li Yang, Yawen Wang, Dahai Jin, and Yunzhan Gong. "Constructing Traceability Links between Software Requirements and Source Code Based on Neural Networks." Mathematics 11, no. 2 (January 7, 2023): 315. http://dx.doi.org/10.3390/math11020315.

Повний текст джерела
Анотація:
Software requirement changes, code changes, software reuse, and testing are important activities in software engineering that involve the traceability links between software requirements and code. Software requirement documents, design documents, code documents, and test case documents are the intermediate products of software development. The lack of interrelationship between these documents can make it extremely difficult to change and maintain the software. Frequent requirements and code changes are inevitable in software development. Software reuse, change impact analysis, and testing also require the relationship between software requirements and code. Using these traceability links can improve the efficiency and quality of related software activities. Existing methods for constructing these links need to be better automated and accurate. To address these problems, we propose to embed software requirements and source code into feature vectors containing their semantic information based on four neural networks (NBOW, RNN, CNN, and self-attention). Accurate traceability links from requirements to code are established by comparing the similarity between these vectors. We develop a prototype tool RCT based on this method. These four networks’ performances in constructing links are explored on 18 open-source projects. The experimental results show that the self-attention network performs best, with an average Recall@50 value of 0.687 on the 18 projects, which is higher than the other three neural network models and much higher than previous approaches using information retrieval and machine learning.
Стилі APA, Harvard, Vancouver, ISO та ін.
50

Gräßler, Iris, Henrik Thiele, Christian Oleff, Philipp Scholle, and Veronika Schulze. "Method for Analysing Requirement Change Propagation based on a Modified Pagerank Algorithm." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 3681–90. http://dx.doi.org/10.1017/dsi.2019.375.

Повний текст джерела
Анотація:
AbstractComplexity of products and systems is increasing through digitalization, interdisciplinarity as well as high technology maturity and new business models. In consequence, new product development (NPD) projects need to manage and satisfy a large number of requirements from a broad range of stakeholders. Yet, NPD projects are often delayed due to requirement changes. In this paper, a new method for analyzing requirement change propagation is presented. The method is based on the assessment of requirement interrelations structured in a requirements structure matrix by a modified page-rank algorithm. By the method, a high number of strongly interrelated requirements can be analyzed in an efficient manner. Additionally, higher-level interrelations as well as the relative weights of requirements are also incorporated in the analysis. Hereby, an efficient holistic approach towards the analysis of requirement change propagation is proposed.
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії