This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Why our brain is not built for softwareengineering. It is a mental process and a limited mental resource (Ashcraft, 2002). In fact, simple heuristics can actually lead to better, quicker decisions than theoretical optimal procedures (Gigerenzer, 2002). Limitations of attention. Limitations of thinking. References.
2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So SCRUM and productivity in software projects: a systematic literature review. In 14th International Conference on Evaluation and Assessment in SoftwareEngineering (EASE) (pp. A survey study of critical success factors in agile software projects.
"A Quick Estimation Approach to Software Cost Estimation," Leckraj Nagowah, Hajrah BibiBenazir, and Bachun, African Conference on SoftwareEngineering and Applied Computing , . "A A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10
Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense SoftwareEngineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 8, August 2002 pp.
People who specialize in testing software will need technical skills more-or-less on par with competent softwareengineers. In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Contracts vs. Promises.
Facts and Fallacies of SoftwareEngineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli. Great Planning Disasters by Peter Hall (University of California Press, 1982), recommended by Sean Doull-Connolly , a Senior Process Engineer at TIAA.
"Managing Requirements for Business Value," John Favaro, IEEE Software , March/April 2002. Aligning Software Investment Decisions with the Markets ," Hakan Erdogmus. " Application of Real Options Theory to SoftwareEngineering for Strategic Decision Making in Software Related Capital Investments ," Albert O.
Managing Project Risk and Uncertainty: A Constructively Simple Approach to Decision Making , Chris Chapman and Stephen Ward, John Wiley & Sons, 2002. SoftwareEngineering Risk Management: Finding your Path Through the Jungle, Version 1.0 , Dale Karolak, IEEE Computer Society, 1998.
“Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Softwareengineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 9, Issue 3, No.
The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. Planning and Executing Time-Bound Projects,” Eduardo Miranda, IEEE Computer , March 2002, pp. 5 Oct 1990, Page 21.
Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, SoftwareEngineering Institute, June 1993. IEEE Transactions on SoftwareEngineering , Vol. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.
Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, SoftwareEngineering Institute, June 1993. IEEE Transactions on SoftwareEngineering , Vol. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.
Compliance became especially important to IT organizations after the passage of certain laws intended to provide improved security for investors, including Sarbanes-Oxley (US, 2002), and the Gramm-Leach-Bliley act (US, 1999). Some of those affect the way we carry out our work in the IT department.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content