Wyniki wyszukiwania - BazTech

1

Requirement Elicitation Techniques for Software Projects in Ukrainian IT: An Exploratory Study

Gobov Denys, Huchenko Inna

Annals of Computer Science and Information Systems

|

2020

|

Vol. 21

673--681

EN

Elicitation is a core business analysis/requirements engineering activity that provides inputs for others like analysis, specification, confirmation, management. There is a significant number of specialized techniques that are used for requirement elicitation. The selection of the appropriate techniques considerably influences a project plan and success of a change as a whole. This paper is intended to analyze the industrial standards and experience of business analysts and requirement engineers in the part of elicitation activities. We conducted a survey study involving 328 specialists from Ukrainian IT companies and a series of interviews with experts to interpret the survey results. Furthermore, this paper provides the guideline in selecting a particular elicitation technique with respect to the type of project and situation.

2

Komentarze w kodach wybranych programów

Skhut Sviatoslav, Iholkina Kateryna

Biuletyn Naukowy Wrocławskiej Wyższej Szkoły Informatyki Stosowanej. Informatyka

|

2018

|

vol. 8, nr 1

24--28

EN

Writing comments is as important as writing code. The main purpose of using comments is to improve readability of our code but frequently thoughtless comment writing decrease understandability of source code. Comments must be concise and precise simultaneously. Also, when our code is changed, comments for this code must be changed too. While using comments in our code we must realize that if expressiveness of our programming language allows us to express clearly what we want in code, there is no need to write comments at all. And if we decide to use comments, they must be extremely accurate and understandable, because another person must understand, what we do and most importantly, why we do it. Frequently comments can be replaced with good clear names of variables, functions or classes. Also, we can replace our comments with assertions. Comments should clarify and explain our intentions. Copyrights and an authorship can be implemented using comments too. But our IDE can do these things automatically.

3

Trust and Risk Assessment Model of Popular Software Based on Known Vulnerabilities

Janiszewski M., Felkner A., Olszak J.

International Journal of Electronics and Telecommunications

|

2017

|

Vol. 63, No. 3

329--336

EN

This paper presents a new concept of an approach to risk assessment which can be done on the basis of publicly available information about vulnerabilities. The presented approach uses also the notion of trust and implements many concepts used in so called trust and reputation management systems (which are widely used in WSN, MANET or P2P networks, but also in ecommerce platforms). The article shows first outcomes obtained from the presented model. The outcomes demonstrate that the model can be implemented in real system to make software management more quantified and objective process, which can have real and beneficial impact on institutional security. In article, however the emphasis was set not on the model itself (which can be easily changed) but on the possibility of finding useful information about vulnerabilities.