scholarly journals Integración de marcos de trabajo para desarrollo de software: Scrum, PSP e ISO 25000 [Integrating software development frameworks: Scrum, PSP and ISO25000]

2015 ◽  
Author(s):  
Jhon Alexander Holguín Barrera
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Industry ◽  
Positive Contribution ◽  
Software Development Process ◽  
Single Application ◽  
Small And Medium Enterprise ◽  
Quality Costs ◽  
Medium Enterprise ◽  
Definition Of

Actualmente la industria del software tiene grandes retos para la construcción y mantenimiento del software en términos de calidad, costos y tiempo. Para esto se han generado diversidad de metodologías, marcos de trabajo, normas y modelos que permiten afrontar estos retos, pero es complejo que la aplicación de solo un referente logre cumplir con todo lo requerido, y por lo general se toman elementos de varios modelos o metodologías. El presente estudio contiene la definición de un proceso de desarrollo de software en una PYME a través de la integración de varios de estos marcos de trabajo (Scrum, PSP e ISO 25000) analizados bajo los lineamientos dados por SWEBOK y apoyados por tecnicas como GQM, que permitan dar un aporte positivo en el cumplimiento de estos objetivos.Palabras Claves: ISO25000, Procesos, PSP, Scrum, SWEBOKCurrently, the software industry has big challenges for the construction and maintenance of software in terms of quality, costs and time. For this the industry generated diversity of methodologies, frameworks, standards and models that meet these challenges, but is complex to accomplish this with the single application of only one reference that meets the goal, usually elements from various models and methodologies are taken. This study contains the definition of a software development process inside of a SME (Small and Medium Enterprise), through the integration of several of this frameworks (Scrum, PSP, and ISO25000) analyzed under the guidelines given by SWEBOK and supported by techniques such as GQM, that allow to make a positive contribution to meet this goals.Keywords: ISO25000, Process, PSP, Scrum, SWEBOK

Ethics in Software Engineering

2011 ◽  
pp. 266-272 ◽  
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Public Interest ◽  
Unethical Behavior ◽  
Development Process ◽  
Software Industry ◽  
Software Development Process ◽  
Bottom Line ◽  
Legal Implications ◽  
Software Engineers

There are various reasons for discussing the issue of ethics within a software engineering context. By participating in a software development process, software engineers can influence the final product, namely the software itself, in different ways including those that may be contrary to public interest. In other words, they could engage in an unethical behavior, inadvertently or deliberately. This could lead to personal harm, and potentially result in loss of confidence in software and loss of trust in organizations that own them. This can adversely affect the acceptance of software as a useful product, question the credibility of software engineering as a profession, lead to legal implications, and impact the bottom line of the software industry at-large.

scholarly journals Wiki support for automated definition of software test cases

Kybernetes ◽  
2019 ◽  
Vol 49 (4) ◽  
pp. 1305-1324
Author(s):  
Leandro Antonelli ◽  
Mariángeles Hozikian ◽  
Guy Camilleri ◽  
Alejandro Fernandez ◽  
Julian Grigera ◽  
...  
Keyword(s):  
Software Development ◽  
Test Generation ◽  
Development Process ◽  
Early Stage ◽  
Software Test ◽  
Test Cases ◽  
Software Development Process ◽  
Content Type ◽  
Definition Of ◽  
Method Model

Purpose The design of tests is a very important step in the software development process because it allows us to match the users’ expectations with the finished product. Considered as a cumbersome activity, efforts have been made to automatize and alleviate the burden of test generation, but it is still a largely neglected step. The study aims to propose taking advantage of existing requirement artifacts, like scenarios that describe the dynamic of the domain in a very early stage of software development, to obtain tests from them. Design/methodology/approach In particular, the approach proposed complement the scenarios that are textually described with a glossary, the language extended lexicon. Thus, a set of rules to derive tests from scenarios is also proposed. The tests are then described using the task/method model. Findings The main findings of this study consist of an extension of a previously presented set of rules. And, a tool based on a media wiki platform that makes possible to record scenarios and the language extended lexicon and implement the rules to obtain the tests. Originality/value The main originality of this study is the glossary which complements scenarios, the semantic support to obtain tests and the tool to automatize the approach.

scholarly journals Activity Oriented Teaching Strategy for Software Engineering Course: An Experience Report

10.28945/4116 ◽  
2018 ◽  
Vol 17 ◽  
pp. 181-200
Author(s):  
Jeevamol Joy Kochumarangolil ◽  
Renumol V G
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Learning Process ◽  
Development Process ◽  
Practical Knowledge ◽  
Software Industry ◽  
Teaching Strategy ◽  
Virtual Classroom ◽  
Software Development Process ◽  
Professional Skills

Aim/Purpose: This paper presents the findings of an Activity-Oriented Teaching Strategy (AOTS) conducted for a postgraduate level Software Engineering (SE) course with the aim of imparting meaningful software development experience for the students. The research question is framed as whether the activity-oriented teaching strategy helps students to acquire practical knowledge of Software Engineering and thus bridge the gap between academia and software industry. Background: Software Engineering Education (SEE) in India is mainly focused on teaching theoretical concepts rather than emphasizing on practical knowledge in software development process. It has been noticed that many students of CS/IT background are struggling when they start their career in the software industry due to inadequate familiarity with the software development process. In the current context of SE education, there is a knowledge gap between the theory learned in the classroom and the actual requirement demanded by the software industry. Methodology: The methodology opted for in this study was action research since the teachers are trying to solve the practical problems and deficiencies encountered while teaching SE. There are four pedagogies in AOTS for fulfilling the requirements of the desired teaching strategy. They are flipped classroom, project role-play for developing project artifacts, teaching by example, and student seminars. The study was conducted among a set of Postgraduate students of the Software Engineering programme at Cochin University of Science and Technology, India. Contribution: AOTS can fulfil both academic and industrial requirements by actively engaging the students in the learning process and thus helping them develop their professional skills. Findings: AOTS can be molded as a promising teaching strategy for learning Software Engineering. It focuses on the essential skill sets demanded by the software industry such as communication, problem-solving, teamwork, and understanding of the software development processes. Impact on Society: Activity-oriented teaching strategies can fulfil both academic and industrial requirements by actively engaging the students in the SE learning process and thus helping them in developing their professional skills. Future Research: AOTS can be refined by adding/modifying pedagogies and including different features like an online evaluation system, virtual classroom etc.

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Sign in / Sign up

Export Citation Format

Share Document