Effort and Risk Prediction for Healthcare Software Projects Delivered on the Web

2014 ◽  
pp. 107-122 ◽  
Author(s):  
Emilia Mendes
Keyword(s):  
Risk Prediction ◽  
Software Projects ◽  
The Web

scholarly journals Boa: a link between worlds

2016 ◽  
Author(s):  
Stephen Romansky ◽  
Sadegh Charmchi ◽  
Abram Hindle
Keyword(s):  
Business Models ◽  
Source Code ◽  
Data Sets ◽  
Additional Insight ◽  
Software Projects ◽  
Software Developers ◽  
Topic Analysis ◽  
Platform As A Service ◽  
Software Changes ◽  
The Web

The business models of software/platform as a service have contributed to developers dependence on the Internet. Developers can rapidly point each other and consumers to the newest software changes with the power of the hyper link. But, developers are not limited to referencing software changes to one another through the web. Other shared hypermedia might include links to: Stack Overflow, Twitter, and issue trackers. This work explores the software traceability of Uniform Resource Locators (URLs) which software developers leave in commit messages and software repositories. URLs are easily extracted from commit messages and source code. Therefore, it would be useful to researchers if URLs provide additional insight on project development. To assess traceability, manual topic labelling is evaluated against automated topic labelling on URL data sets. This work also shows differences between URL data collected from commit messages versus URL data collected from source code. As well, this work explores outlying software projects with many URLs in case these projects do not provide meaningful software relationship information. Results from manual topic labelling show promise under evaluation while automated topic labelling did not yield precise topics. Further investigation of manual and automated topic analysis would be useful.

What is Different about Web and Software Projects?

2008 ◽  
pp. 1-24
Author(s):  
Emilia Mendes
Keyword(s):  
Software Development ◽  
Effort Estimation ◽  
Quality Factors ◽  
Software Effort Estimation ◽  
Software Projects ◽  
Development Processes ◽  
The Web

The objective of this chapter is threefold. First is to introduce new terminology that relates specifically to hypertext, the model the Web is based upon. Second, it provides an overview of differences between Web and software development with respect to their development processes, technologies, quality factors, and measures. Third, it discusses the differences between Web effort estimation and software effort estimation.

scholarly journals La ingeniería de requisitos una base fundamental para el desarrollo de proyectos de TI en la web.

2015 ◽  
Vol 3 (1) ◽  
pp. 71-78
Author(s):  
Edwin Mejía ◽  
Walter Orozco
Keyword(s):  
Data Collection ◽  
Requirements Engineering ◽  
Web Applications ◽  
Software Projects ◽  
Web Based ◽  
Organization Level ◽  
Banking Organization ◽  
Education Market ◽  
Over Time ◽  
The Web

Los sistemas informáticos basados en la web han ido creciendo a pasos muy grandes. La web a través del tiempo se ha convertido en un lugar para localizar los documentos importantes de las instituciones, así como llevar a grandes volúmenes de información a nivel mercado bancario y educativo de la organización. Los sistemas basados en la web desde su creación envolvió toda esa sistematización para resolver problemas de negocios que tenían, pero sin utilizar ninguna metodologia para la construcción de los mismos. Por lo tanto, este artículo se presenta una breve introducción a las aplicaciones Web, metodologías de construcción de este tipo de aplicaciones, ingeniería de requerimientos en aplicaciones web, las técnicas utilizadas para la recolección de datos y los graves problemas que han pasado varias aplicaciones web, centrándose en la ingeniería de requisitos como el eje primordial en el desarrollo de proyectos de software. Abstract Computer systems based on the web have grown to very large steps. The web over time has become a place to locate important documents of the institutions and lead to large volumes of information and education market banking organization level. The web-based systems since its inception wrapped all this systematization to solve business problems they had, but without using any methodology for building them. Therefore, this article is a brief introduction to the Web applications, methodologies to build such applications, requirements engineering web applications, the techniques used for data collection and the serious problems that have passed several web applications focusing on requirements engineering as the linchpin in the development of software projects.

scholarly journals The Influence of Code Retrieval from the Web on Programmer’s Skills, Meth-odologies, and Coding Behaviors

2021 ◽  
Vol 36 (2) ◽  
pp. 160-166
Author(s):  
Alfaroq O.M. Mohammed ◽  
Ziad A. Abdelnabi ◽  
Abdalmunam Abdalla
Keyword(s):  
Source Code ◽  
The Internet ◽  
Software Projects ◽  
Analysis And Design ◽  
Software Developer ◽  
Software Production ◽  
The Web

The development of software projects consists of several stages, such as analysis and design. It also requires a set of skills that the software developer can use to work on the project, such as specifying the requirements and writing code. Developers usually search for source code on the internet for remix and reuse in software production. This paper aims to investigate the influence and effect of code retrieved from the web on programmers’ views, decisions, and skills. A questionnaire instrument was designed and distributed to programmers for their feedback. As a result, we were able to address some points and achieved a better understanding of the interaction between programmers and the code from the web, especially the code from programming forums such as Stack Over Flow.

Improving Project Management of Healthcare Projects through Knowledge Elicitation

2013 ◽  
pp. 750-769
Author(s):  
Emilia Mendes
Keyword(s):  
Expert Knowledge ◽  
Project Managers ◽  
Knowledge Elicitation ◽  
Healthcare Organisation ◽  
Effort Estimation ◽  
Software Projects ◽  
Risk Management Process ◽  
Using Data ◽  
The Web

This chapter describes a case study where Bayesian Networks (BNs) were used to construct an expert-based software effort and risk prediction model for use by a large healthcare organisation in Auckland (New Zealand) to manage healthcare software projects delivered on the Web. This model was solely elicited from expert knowledge, with the participation of seven project managers, and was validated using data from 22 past finished projects. The model led to numerous changes in process and also in business. The company adapted their existing effort and risk management process to be in line with the model that was created, and the use of a mathematically based model also led to an increase in the number of projects being outsourced to this company by other company branches worldwide. Their predictions improved significantly too. The results suggest that the use of a model that allows the representation of uncertainty, inherent in effort estimation, can outperform expert-based estimates.

Modeling Defects in E-Projects

2009 ◽  
pp. 317-330
Author(s):  
John D. Ferguson ◽  
James Miller
Keyword(s):  
Simple Model ◽  
Production Process ◽  
High Frequency ◽  
Rapid Development ◽  
Software Projects ◽  
Software Production ◽  
Defect Injection ◽  
Removal Processes ◽  
Tools And Techniques ◽  
The Web

It is now widely accepted that software projects utilizing the Web (e-projects) face many of the same problems and risks experienced with more traditional software projects, only to a greater degree. Further, their characteristics of rapid development cycles combined with high frequency of software releases and adaptations make many of the traditional tools and techniques for modeling defects unsuitable. This paper proposes a simple model to explain and quantify the interaction between generic defect injection and removal processes in e-projects. The model is based upon long standing and highly regarded work from the field of quantitative ecological population modeling. This basic modeling approach is then subsequently tailored to fit the software production process within an e-project context.

Probabilistic Approach to Predicting Risk in Software Projects Using Software Repository Data

2015 ◽  
Vol 25 (06) ◽  
pp. 1017-1032 ◽  
Author(s):  
Changkyun Jeon ◽  
Neunghoe Kim ◽  
Hoh Peter In
Keyword(s):  
Risk Prediction ◽  
Risk Estimation ◽  
Probabilistic Approach ◽  
Significant Risk ◽  
Project Managers ◽  
Risk Level ◽  
Software Project ◽  
Software Projects ◽  
Software Repository ◽  
Project Failures

Although the factors that need to be focused on for a successful software project appear to be difficult to define, risk management has become one of the key activities for achieving such success because significant risk is involved in each software development phase. Software project failures are often a result of insufficient and ineffective risk information regarding the future. To overcome this, software risk prediction should be performed in advance to allow project managers insight into providing more valuable information for decision making, such as scope coverage, resource allocation, and schedule changes. In this research, we propose a risk prediction model from the perspective of quality using a software repository. We evaluated the risk threat level by mapping some defect attributes that exist in the defect lifecycle, defined their risk threat transition states, and applied a Markov chain for predicting the potential risk level. We evaluated the proposed approach using practical real-industry mobile software projects. The experimental results confirm that our approach is applicable to software threat risk estimation.

scholarly journals Boa: a link between worlds

2016 ◽  
Author(s):  
Stephen Romansky ◽  
Sadegh Charmchi ◽  
Abram Hindle
Keyword(s):  
Business Models ◽  
Source Code ◽  
Data Sets ◽  
Additional Insight ◽  
Software Projects ◽  
Software Developers ◽  
Topic Analysis ◽  
Platform As A Service ◽  
Software Changes ◽  
The Web

The business models of software/platform as a service have contributed to developers dependence on the Internet. Developers can rapidly point each other and consumers to the newest software changes with the power of the hyper link. But, developers are not limited to referencing software changes to one another through the web. Other shared hypermedia might include links to: Stack Overflow, Twitter, and issue trackers. This work explores the software traceability of Uniform Resource Locators (URLs) which software developers leave in commit messages and software repositories. URLs are easily extracted from commit messages and source code. Therefore, it would be useful to researchers if URLs provide additional insight on project development. To assess traceability, manual topic labelling is evaluated against automated topic labelling on URL data sets. This work also shows differences between URL data collected from commit messages versus URL data collected from source code. As well, this work explores outlying software projects with many URLs in case these projects do not provide meaningful software relationship information. Results from manual topic labelling show promise under evaluation while automated topic labelling did not yield precise topics. Further investigation of manual and automated topic analysis would be useful.

Sign in / Sign up

Export Citation Format

Share Document