Knowledge work productivity effect on quality of knowledge work in software development process in SME

2016 ◽  
Author(s):  
Mohd Zairol Yusoff ◽  
Massudi Mahmuddin ◽  
Mazida Ahmad
Keyword(s):  
Software Development ◽  
Development Process ◽  
Work Productivity ◽  
Knowledge Work ◽  
Software Development Process ◽  
Productivity Effect

scholarly journals Quality of the Software Development Process

1983 ◽  
Vol 16 (18) ◽  
pp. 145-152 ◽  
Author(s):  
K. Frühauf ◽  
H. Sandmayr
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Development Process

scholarly journals Measuring the Quality Of the Development Process Academic System with E-GQM Method

2021 ◽  
Vol 5 (1) ◽  
Author(s):  
Sarwosri Sarwosri ◽  
Umi Laili Yuhana ◽  
Siti Rochimah ◽  
Rizky Januar Akbar ◽  
Maidina Choirun Nisa
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Development Project ◽  
Average Score ◽  
Software Development Process ◽  
Software Development Project ◽  
Software Products ◽  
Academic System

In a software development project, aspects of software quality are very important. All stakeholders expect high quality of software. To ensure the quality of software products, it is also necessary to ensure that the process that is carried out have a quality. Research that is mostly done is in terms of assessing the quality of software products. But the software process is also very important to be assessed from their quality too. In every software development process, the developer needs guidance in carrying out every aspect of it. In each of these aspects, it must be determined what goals are to be achieved and how to measure whether those goals have been achieved or not. One method that can be used for this is the Extended Goal Question Metric method. In this method, for each development process in software, will be determined what aspects must be achieved, from each aspect there are defined a number of goals to measure these aspects. For each goal, one or more goal will be determined one or more questions that are relevant to that. For each Question an appropriate metric will be determined. The next step is mapping between G to Q and Q to M. The measurement is done by calculating the goal value obtained from the metric calculation. From this metric, the value of each Goal will be obtained, whether it was achieved or not. Tests were carried out on the software process for the development of academic system features at DPTSI ITS. The value of each goal has exceeded 0.51 (for a scale of 0-1) so that it achieved the quality of the Software development process. The total average score was 0.889. 

Trust Elements in Open Source

2010 ◽  
pp. 334-342
Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Automatic Measurement ◽  
Automatic Process ◽  
Software Development Process ◽  
Software Products ◽  
Development Tools ◽  
On Line ◽  
Measurement Approach

The quality of a software development process is based on a large spectrum of various elements that must be identified and assessed. The majority of elements can be measured quantitatively and possibly using an automatic process. Some elements, however, are rather subjective and depend strongly on different opinions of people using or evaluating the software development process. An automatic measurement approach is difficult to achieve (for example by on-line questionnaires or surveys inserted inside software products or software development tools). The foundation for all assessments is a set of elements that will be at a certain point of development or use measured and evaluated.

Quality-Driven Software Development for Maintenance

2014 ◽  
pp. 1608-1638
Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Software Development ◽  
Software Maintenance ◽  
Development Process ◽  
Special Kind ◽  
Positive Influence ◽  
Quality Characteristics ◽  
Software Development Process ◽  
Development Paradigm ◽  
Further Development

Software maintenance is sometimes considered as a special kind of activity that is separated from a software development process. Meanwhile, the opposite is true; maintenance should be taken into account from the beginning of the software development process. Because a model-based software development is the prevailing software development paradigm, the maintainability should be considered within models that arise in software development process. We claim that the quality of the models arising in the software development process has a positive influence on their maintainability: the higher quality of the models, the more effective maintainability activity. The background for our consideration is MDA approach, and the scope of the consideration is limited to perfective maintenance only. The set of so called 6C quality characteristics is assumed to define a quality of MDA-models. Our selection of 6C quality characteristics is justified by the fact that they are related to activities performed on models within the maintenance. To assess MDA-models in the context of the maintainability, we define checklists for the 6C characteristics. These checklists are used for derivation of some measures which are useful in checking to what scope a given characteristics is satisfied. The main advantage of the approach is its independence of the knowledge of future changes of user requirements that trigger perfective maintenance. In the chapter, we demonstrate a simple example of how to assess the quality of PIM-models that are the realization of the CIM-model. Additionally, we discuss how to select, for further development, the best PIM-model from the set of possible solution.

scholarly journals Reuse Alternatives based on the Sources of Software Assets

2021 ◽  
Vol 10 (1) ◽  
Author(s):  
Anas AL-Badareen
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Reuse ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Products ◽  
Engineering Discipline

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages.

METHODS OF SELECTING ACCEPTABLE STRATEGIES OF SOFTWARE DEVELOPMENT

2018 ◽  
pp. 33-39
Author(s):  
V. A. Fedorova ◽  
T. A. Moiseeva ◽  
E. V. Poddubnaya
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Product ◽  
Collective Development ◽  
The Moment ◽  
The Cost ◽  
Development And Management

Currently, software is used in many areas of human activity. But the developers of software systems often have problems that leads to exceeding the time and budget of development, as well as reduces the quality and security of software. The paper proposes a methodology developed by the authors, which allows you to standardize the process of creating software. The proposed approach greatly facilitates the organization of the process of collective development and management of software development, improves the quality of the developed software, reduces the risks of the developer and the customer and also reduces the time spent on the creation of software and the cost of its development. The developed technique fully standardizes the software development process, from the moment of creation of specification and ending with the introduction and support of the software product.

scholarly journals Teknik Representasi Kebutuhan Pengguna Menggunakan User Persona (Studi Kasus: Relasi antara Presensi dengan Kemampuan Kompetensi)

2021 ◽  
Vol 8 (2) ◽  
pp. 245
Author(s):  
Wahyu Andhika ◽  
Muhammad Iqbal ◽  
Munifah Nur ◽  
Rizkhi Dwi Nugroho
Keyword(s):  
Problem Solving ◽  
Software Development ◽  
Development Process ◽  
User Involvement ◽  
Software Development Process ◽  
Basic Requirement ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
System User

<p class="Abstrak">Elisitasi kebutuhan dalam proses pengembangan perangkat lunak adalah fase yang sangat penting dalam <em>Software Development Lifecycle</em>. Karena dalam tahap ini ditentukan dengan tepat mengenai apa yang akan dibuat. Sebuah sistem baiknya memenuhi kebutuhan dari pengguna. Oleh karena itu, melibatkan pengguna dalam elisitasi kebutuhan menjadi salah satu fase yang sangat berguna dalam menentukan kualitas <em>persona</em><em> experience</em> dalam suatu sistem. Keterlibatan pengguna membuat pengembang harus memahami dengan baik apa saja yang akan menjadi kebutuhan pengguna. Pendekatan yang efektif dibutuhkan untuk mengenali pengguna dan merangkum kebutuhannya dengan baik dengan segala keunikan pada setiap individu yang mungkin terjadi. Menggunakan metode <em>persona</em>, penelitian ini akan menyelesaikan permasalahan berupa informasi dari pengguna yang tidak menggambarkan kebutuhan secara lengkap. Metode ini akan membantu menggambarkan seorang pengguna secara mendalam mulai dari kepribadian, kemampuan hingga perilaku pengguna terhadap suatu masalah. Dokumen mengenai pengguna secara detail kemudian disimpulkan agar didapatkan sebuah kebutuhan dasar untuk diimplementasikan menjadi sebuah sistem. Selain menggunakan metode <em>persona</em><em> </em>dalam meningkatkan elisitasi kebutuhan, penelitian ini juga berfokus pada nilai kualitatif informasi tersebut dengan menambahkan implementasi teori iteratif. Teori ini digunakan untuk meningkatkan akurasi penyelesaian masalah, yang mana pada setiap tahapnya akan menghasilkan informasi yang akan memudahkan pengembang dalam mendesain perangkat lunak yang berorientasi pada pengguna.</p><p class="Abstrak"> </p><p class="Abstrak"><em><strong>Abstract</strong></em></p><div><p><em>Elicitation of needs in the software development process is a very important phase in the Software Development Lifecycle. Because in this stage it is precisely determined what will be made. A good system meets the needs of personas. Therefore, involving personas in the elicitation of needs is one phase that is very useful in determining the quality of persona experience in a system. User involvement makes the developer must understand well what will be the persona's needs. An effective approach is needed to recognize the persona and summarize his needs well with all the uniqueness in each individual that might occur. By using the persona method, this research will solve problems in the form of information from personas who do not describe the needs in full. This method will help describe a persona in depth ranging from personality, ability to persona behavior towards a problem. The detailed persona document is then concluded in order to obtain a basic requirement to be implemented into a system. In addition to using the persona method in increasing the elicitation of needs, this research also focuses on the qualitative value of the information by adding iterative theory implementation. This theory is used to improve the accuracy of problem solving, which at each stage will produce information that will facilitate developers in designing persona-oriented software.</em></p></div><p class="Abstrak"><em><strong><br /></strong></em></p>

Object-Oriented Software Metrics

2005 ◽  
pp. 2150-2155
Author(s):  
Jana Polgar
Keyword(s):  
Software Development ◽  
Software Metrics ◽  
Development Process ◽  
Object Oriented ◽  
Software Development Process ◽  
Software Measurement ◽  
Software Projects ◽  
Critical View ◽  
Code Complexity

Software measurement is considered to be an efficient means to monitor the quality of software projects, predict cost of maintenance, assess reusability of components, provide prediction of faults in similar projects, and contribute to improvement of the software development process. This chapter surveys software metrics literature with particular focus on object-oriented metrics, and metrics for measuring code complexity. Furthermore, we provide a critical view of software metrics and their usability.

Sign in / Sign up

Export Citation Format

Share Document