scholarly journals New life for cordless communication, old regrets for software projects

2021 ◽  
Vol 64 (10) ◽  
pp. 6-7
Author(s):  
Andrei Sukhov ◽  
Igor Sorokin ◽  
Doug Meil
Keyword(s):  
Internet Of Things ◽  
The Internet ◽  
Software Projects ◽  
Potential Benefits ◽  
Software Engineers ◽  
The Internet Of Things

The Communications website, http://cacm.acm.org, features more than a dozen bloggers in the BLOG@CACM community. In each issue of Communications , we'll publish selected posts or excerpts. twitter Follow us on Twitter at http://twitter.com/blogCACM http://cacm.acm.org/blogs/blog-cacm Andrei Sukhov and Igor Sorokin ponder the potential benefits of DECT to the Internet of Things, while Doug Meil considers how software engineers should reflect on their accomplishments.

scholarly journals COMPETENCE ASSESSMENT AND DEVELOPMENT FOR MANAGING HUMAN CAPITAL IN IT SECTOR

2022 ◽  
Vol 13 (1) ◽  
pp. 0-0
Keyword(s):  
Developing Nations ◽  
Technical Competence ◽  
Software Projects ◽  
It Industry ◽  
The Third ◽  
Software Engineers ◽  
Software Professionals ◽  
Increasing Demand ◽  
Set Up ◽  
Professional Occupation

With ever-increasing demand for software professionals, time has come for the information technology (IT) industry to unearth competencies required for software professionals. The majority of IT companies have been employing outsourcing software projects to inexpensive hubs in developing nations. Therefore expectations from highly skilled software professionals are rising. The purpose of the study is to recognize the technical competence levels associated with software professionals in a range of profiles which are found in India's major IT organizations. There are three basic objectives of the present study. The first objective is to conduct a literature survey of description of the software engineers in IT domain. The second objective is to quantify the competency levels of the software engineers in IT sector. Finally, the third objective is to conduct a survey-based empirical study on software engineers. The professional occupation is set up through seven successive profiles.

scholarly journals Using Agile Practice for Student Software Projects

2012 ◽  
Vol 3 (9) ◽  
pp. 280-290
Author(s):  
Fernando Almeida
Keyword(s):  
Software Development ◽  
Software Projects ◽  
Undergraduate Level ◽  
Entry Level ◽  
Software Engineers ◽  
Software Development Methodologies ◽  
Skill Improvement ◽  
Agile Software ◽  
Traditional Approaches ◽  
First Contact

Agile methodology as a relatively new approach to software engineering is becoming more popular in both industry and academia. Learning agile software development methodologies will unquestionably increase the capabilities and competences of our students as entry-level software engineers. However, how agile methods and techniques should be taught at the undergraduate level in additional to traditional approaches is still being debated. This study was conducted on a studentprogramming project, with sample size of 23 students from the Informatics Engineering course. The Scrum methodology was adopted and 28 user stories and 4 sprints were created. The results indicate a significant impact on students’ skill improvement and let them to have the first contact with real projects and clients. Besides that, the students agree that the adoption of the Scrum methodology helped them to improve the participation and collaboration. However, some issues were also detected in terms of communication and tasks planning. Therefore, we proposed some polities that could help and boost the software development process inside a classroom.

Software Project Costing

2012 ◽  
Vol 3 (4) ◽  
pp. 72-86 ◽  
Author(s):  
Liran Edelist ◽  
Roy Gelbard ◽  
Jeffrey Kantor
Keyword(s):  
Organizational Context ◽  
Project Managers ◽  
Software Project ◽  
Maturity Model ◽  
Software Projects ◽  
Capability Maturity ◽  
Body Of Knowledge ◽  
Organizational Perspective ◽  
Proposed Model ◽  
Software Engineers

This study puts forward a generic and comprehensive costing framework for software projects that aims for simplicity. This is achieved by integrating commonly used CMMI (Capability Maturity Model Integration) and PMBOK (Project Management Body of Knowledge) costing concepts in a broader organizational context. The costing framework comprises three layers: costing targets, costing activities, and policy evaluation. While the first two layers are derived from commonly used software engineering elements, the third integrates an organizational perspective through software engineers, project managers, accountants and top management. Employment of CMMI and PMBOK standards allows for easy adoption of the proposed model by organizations that are already relying on these standards.

Service Provision in a Software Technology Unit

2003 ◽  
Vol 18 (3) ◽  
pp. 195-209 ◽  
Author(s):  
Lars Mathiassen ◽  
Ingegerd Andersson ◽  
Kerstin Hanson
Keyword(s):  
Software Development ◽  
Service Provider ◽  
New Technologies ◽  
Software Projects ◽  
Traditional Role ◽  
Software Technology ◽  
Complex Diffusion ◽  
Software Engineers ◽  
Large Software ◽  
Software Organization

Large software organizations establish software technology units for managing the methods and tools aimed at supporting their software engineers. This division between software development and new technologies for software development establishes specialized competencies, supports standardization across software projects and departments and provides dedicated resources for innovation. However, such software technology units are faced with complex diffusion projects that are difficult and challenging to manage and that in many cases lead to unsatisfactory results. This paper reports from attempts to improve diffusion practices within a technology unit in a large software organization. Two complementary roles for software technology units, i.e. technology supplier and service provider, are presented and used for interpreting the experiences. The research suggests that technology units in large software organizations can improve their diffusion practices by complementing the traditional role as a technology supplier with that of a service provider. The paper offers lessons on how software organizations can take steps in that direction.

scholarly journals An Approach to Determining Software Projects with Similar Functionality and Architecture Process Based on Artificial Intelligence Methods

2018 ◽  
Author(s):  
Nadezhda Yarushkina ◽  
Gleb Guskov ◽  
Pavel Dudarin
Keyword(s):  
Artificial Intelligence ◽  
Language Processing ◽  
Source Code ◽  
Similarity Metrics ◽  
Software Projects ◽  
Two Phase ◽  
The World ◽  
Novel Method ◽  
Software Engineers ◽  
Processing Techniques

Software engineers from all over the world solve independently a lot of similar problems. In this condition the problem of code or even better architecture reusing becomes an issue of the day. In this paper two phase approach to determining the functional and structural likenesses of software projects is proposed. This approach combines two methods of artificial intelligence: natural language processing techniques with a novel method for comparing software projects based on ontological representation of their architecture automatically obtained from the projects source code. Additionally several similarity metrics are proposed to estimate similarity between projects.

scholarly journals Industrial and OSS developers’ profiles: a family of experiments to evaluate a pioneering neuro-linguistic method for preferred representational systems automatic detection

2021 ◽  
Vol 27 (1) ◽  
Author(s):  
Methanias Colaço Júnior ◽  
Breno Santana Santos ◽  
Manoel Mendonça ◽  
Daniela Corumba ◽  
Mario André de F. Farias
Keyword(s):  
Development Process ◽  
Specific Context ◽  
Software Projects ◽  
Software Developers ◽  
Software Comprehension ◽  
Representational System ◽  
New Approach ◽  
Mailing Lists ◽  
Software Engineers ◽  
Family Of Experiments

AbstractSoftware projects use mailing lists as the primary tool for collaboration and coordination. Mailing lists can be an important source for extracting behavioral patterns in the software development. A new approach for that is the use of Neurolinguistic theory to determine what is the Preferred Representational cognitive System (PRS) of software engineers in that specific context. Different resources and cognitive channels are used by developers in order to achieve software understanding. An important question on this matter is: What types of representational systems are preferred by software engineers? This paper presents a psychometrically based neurolinguistic method to identify the PRS of software developers. Experimental evaluation of the approach was carried out in three experiments to assess the Preferred Representational System of developers at Industrial and OSS (Apache server and Postgresql) mailing lists. For the OSS projects, the results showed that the PRS scores of the top-committers clearly differ from the general population of the projects. For industry, the experiment showed that the developers indeed have a PRS. Finally, for both scenarios, the qualitative analysis also indicated that the PRS scores obtained are aligned with the developers’ profiles, considering that alignment is essential to effective communication within the team and enhances the development process due to a better software comprehension.

scholarly journals Prediction of Personality Profiles in the Pakistan Software Industry–A Study

Psych ◽  
2019 ◽  
Vol 1 (1) ◽  
pp. 320-330 ◽  
Author(s):  
Ali Hasan ◽  
Sana Moin ◽  
Maruf Pasha
Keyword(s):  
Software Industry ◽  
Personality Type ◽  
Main Theme ◽  
Personality Profiles ◽  
Myers Briggs Type Indicator ◽  
Software Projects ◽  
Software Developers ◽  
Type Indicator ◽  
Software Engineers ◽  
Web Developers

Psychology says not everyone is able to do all type of tasks assigned to them. This point is valid for people working in the software industries as well. Therefore, when assigning the most suitable tasks to people according to their personality type, a software development company’s succession rate can be proliferated to a remarkable level. In this manner, the main theme of this empirical research is to find relationships that establish links between personality type and their job designation preferences in the software industry. For this purpose, this study is comprised of 44 Pakistan developers, who are working in different software houses and are directly involved in developing software projects. In addition, an MBTI (Myers-Briggs Type Indicator) test indicator is used for the link establishment. With respect to the reported results, tester, team lead, and project manager are found to be ENFJs, which is the least common type in software developers. However, for web developers and software engineers, ISFJ is found to be the most preferable type, with an edge over ENFJ.

Argumentation Schemes for Collaborative Debate of Requirement Risks in Software Projects

2017 ◽  
Vol 27 (09n10) ◽  
pp. 1613-1635 ◽  
Author(s):  
Denise da Luz Siqueira ◽  
Lisandra M. Fontoura ◽  
Rafael H. Bordini ◽  
Luis A. L. Silva
Keyword(s):  
Artificial Intelligence ◽  
Risk Management ◽  
Argumentation Schemes ◽  
Software Projects ◽  
Quality Requirements ◽  
Poor Understanding ◽  
Software Engineers ◽  
Client Needs ◽  
Significant Class

Managing risks in real-world software projects is of paramount importance. A significant class of such risks is related to the engineering of requirements, commonly involving the presentation and analysis of risk management arguments from both software engineers and clients involved in collaborative debates. In this work, drawing inspiration from argumentation theory in Artificial Intelligence, we introduce a number of “argumentation schemes” and associated “critical questions” to support such discussions. In doing so, we propose schemes related to risks due to excessive numbers of requirements; inadequate client representatives and poor understanding of client needs; incorrect, incomplete and conflicting requirements; complex and non-traceable requirements; non-stable requirements; and low quality requirements. We also discuss a case study and two experiments where the developed schemes supported the discussion of requirement risks in software projects. The overall results of these experiments indicate that our schemes are useful in the identification, proposition and analysis of requirement risks, adequately supporting debates on requirement risks.

Sign in / Sign up

Export Citation Format

Share Document