Test Harness Environment for Embedded Java Applications

The debate on how to integrate Design Thinking and Lean Startup into the agile process has been addressed in the literature over the past few years. Researchers argue that Design Thinking can contribute to software development by offering support on how to understand user needs in order to derive solution and product options, whereas Lean Startup helps to learn about business and scaling strategies. Based on these viewpoints, we developed InnoDev, which is an approach that combines Design Thinking, Lean Startup and Scrum to create an agile software development process that can deliver the innovative customer-oriented products and services required by competitive companies. This study aims to describe InnoDev in detail by depicting all its phases. Our findings provide complementary perspectives regarding software development strategies, roles and techniques. This study will advance the knowledge of Design Thinking and software development by providing a detailed description of a tool that combines best practices for creating more innovative software products. The results of this investigation can help managers to evaluate their software development process in order to improve its effectiveness and create more efficient user-driven solutions.

YaM is a software development framework with tools for facilitating the rapid development of software in a concurrent software development environment. YaM provides solutions for thorny development challenges associated with software reuse, managing multiple software configurations, developing of software product-lines, and multiple platform development and build management. YaM uses release-early, release-often development cycles to allow developers to incrementally integrate their changes into the system on a continual basis. YaM facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort YaM uses modules and packages to organize and share software across multiple software products. It uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One side-benefit is the enforcement of a strong module-level encapsulation of a module's functionality and interface. This increases design transparency, system stability as well as software reuse. YaM is in use by several mid-size software development teams including several developing mission-critical software.

<p>In software development, one size does not fit all. Contingencies shape the alignment between the project and its environment, and between software development and project success. Yet the conditions favouring a particular software development methodology (e.g., waterfall or scrum) are not well understood. The current research aims to answer two questions: (1) What are the important factors in software development methodology (SDM) fit? (2) What is the role of SDM fit in project success? A review of the IT literature revealed two kinds of SDMs. On the one hand, there are traditional, plan-driven methodologies that seek compliance to a pre-established plan and existing processes. On the other hand, there are agile methodologies that seek to embrace the increasing changes and uncertainty involved in software development projects. The literature review established that there is no agreement on the contingencies associated with the use of each methodology, nor agreement on how to measure project success. Exploratory research was undertaken to identify contingencies in software development. Preliminary interviews of projects workers, using a card sort procedure, helped to identify key constructs and to generate and refine a set of measurement items. Then an international survey of software development project workers was conducted. Data analysis revealed two factors that are important in SDM fit: one is organizational culture; and the other is empowerment of the project team. The first factor encapsulates variables related to the project environment such as the level of entrepreneurship and methodology supported by top management. The second factor is related to the characteristics of the project and includes variables such as procedural empowerment and project uncertainty. No support was found for factors such as project size, criticality and the need for personnel supervision that are generally considered important contingencies. The current study also demonstrates that SDM fit is one of the predictors of project success, and affirms prior claims that one methodology does not fit all projects. The current research contributes to the SDM fit literature a contingency model that includes the impact of factors associated with the project and the project environment, on SDM fit and project success. The contingencies identified and evaluated by this research may assist practitioners to select the most appropriate methodology, and to achieve higher project success rates.</p>

Many undergraduate IT programs recognize that their graduates will find jobs as software developers. As such, software development (analysis and design) courses are often a core requirement of IT undergraduate degree programs. This paper presents an analysis and comparison of the content of software development courses at several colleges and universities. In particular, the software development methodologies presented in the courses are examined. The comparison is based on two main criteria; the development methodologies presented through the textbook assigned to the class, and the development methodologies presented through the class lectures.A software development methodology is "a recommended collection of phases, procedures, rules, techniques, tools, documentation, management, and training used to develop a system" (Avison 2003). There are hundreds of software development methodologies. An ongoing debate has existed for several years as to what methodology is best. Prior research has shown that no methodology is best all the time and that practitioners are modifying methodologies to suit their needs. This research shows that IT software development courses have not been modified to reflect current trends in the practical application of development methodologies and students may not be learning the tools and techniques that they need to become successful practitioners. Key inadequacies and the associated pedagogical significance are discussed.

The process of software development life cycle (SDLC) is an important element of development phases to develop the application. In fact, there are needs to upgrade the sequence of methodology in software development. The SDLC methodology is the highest level of abstraction and is defined as a collection of problem-solving methods governed by a set of principles and common philosophies in solving targeted problems for extended project timeline teamwork as well as a decrease of a high team collaboration and understanding in the software development. Thus, the SDLC is very crucial in order for them to ensure the quality of skills is placed accordingly in the workflow. This research contributes to the development of a new approach in system development workflow with the aim to properly manage system development projects. It started by providing some background data related to the previous mode of operation in the teamwork samples as shared by the stakeholders of the transformation projects and the new proposed Analysis System Development Framework (ASDF) method team members. Then, the key findings related to themes of 1) input for User Requirement Specification (URS) and 2) System Requirement Specification (SRS), 3) proses for module, 4) process for database, 5) process for User Acceptance Testing (UAT) 6) output for Final Acceptance Testing (FAT) and empowerment for the whole level based on ASDF method. This research contributes mainly to the findings, more than previous research has found, that significantly support the perception that a high quality of skills in a teamwork results in better performance of software development.

Delivering quality software is every software developer's responsibility. The use of software development methodologies increases chances of delivering quality software, within stipulated timelines and budget. Limited research exists on solo software development methodologies, thus solo developers resort to adapting team software development methods for their development efforts. The dilemma is that adaptation of team software methodologies may compromise the quality of the resulting methodologies. This paper addresses this dilemma by presenting results of a qualitative meta-synthesis conducted to synthesize the existing few solo software development methodologies into a high-quality solo software development framework. Articles published between January 2000 and December 2017 were identified using a predefined search string. Six primary studies were included in the synthesis after meeting the criteria set for the study. Using meta-ethnography, the identified solo software development methodologies were interpreted and translated into each other resulting in a six staged solo software development framework. The six stages are: Management Buy-in and Standards adoption; Requirements Elicitation; Release and Sprint Planning; Development; Sprint Review and Close; and Evaluation. This study therefore contributes to knowledge through theory building in solo (freelance) software development. Freelance developers can adopt this framework to enhance the quality of their software. Further research on the derived framework should validate the framework empirically creating more knowledge in the field of solo software development.

Putting the user at the center of the process has been considered key to achieve quality in modern software development. Discovering and framing the user needs are necessary activities to produce better quality software that fits the customer’s needs and their satisfaction. User-centered Design approaches such as Design Thinking (DT) help to establish a creative mindset through convergent and divergent working spaces that allow for the team to better understand, to create empathy, to brainstorm ideas, to prototype, and to test innovative solutions in software development. However, navigating in this world is still challenging. Literature reports on the use of a large spam of techniques to support DT. Selecting an appropriate set of techniques considering the project context, the stakeholders’ profiles, and other characteristics may be challenging, mainly to novice professionals. Thus, as part of an on-going long-term research project, we propose Helius, a collaborative recommender system for DT techniques in software development. Helius provides features supporting recommendations of DT Techniques based on the user previous experiences, techniques’ evaluation ratings, and community feedback. This paper focuses on our preliminary results upon the tool proposal–on a comparison of Helius features with other related tools using the DESMET method. This comparison shows that Helius brings new features for the recommendation of DT techniques, thus, contributing to process quality improvement.

Process models form the heart of software engineering since software development process spans the life cycle of any given project. Even though waterfall model forms the basis of all software development models, the demand for new models with design and implementation occurring in parallel is on the increase. This research aims at the evaluation of a vision oriented software development model. In this study, the subjects are final year post graduate students working for their final term projects for small organizations in and around our city. The group of students applied two techniques for software development and it was found that VOSDM was more effective and improved reliability. The productivity did not show any significant improvement

Combining formal and agile techniques in software development has the potential to minimize change-related problems.

In recent years, with the rapid development of information technology, the application of computer technology has become increasingly widespread. In order to meet the needs of modern society for computer technology, computer software needs to be constantly developed. In the development of computer software, layered technology occupies a very important position. It is essential for the development of computer software. It can achieve multi-level technology across. Therefore, the various layering techniques in computer software development are analysed, in order to explore the application of layered technology in computer software development.

The emergence of software offshore outsourcing phenomena hits every country positively and one of the offshore client/vendor attractng factor is CMM certification. CMM is a well recognized and globally accepted standard in software development to process control, quality improvement, and measurement of software firm's capability. Therefore, Pakistani software firms (SMEs) are striving to achieve the CMM certifications to earn profit from offshore clients. In fact, CMM certification is not easy to adopt for all level of firms. Pakistan software industry is at its initial stage, so it is not recommendable to jump for CMM by software firms (SMEs) directly. The present research paper suggests that these software firms (SMEs) should go for adaptation of agile development methodology for excellent performance on the foot steps of CMM. In this way, software firms (SMEs) can leads toward CMM after agile maturity. The authors used the eXtreme Programming (XP) as an example that proves Agile Development Methodology can well fit the CMM framework and software development firms (SMEs) can achieve their objectives to participate in offshore outsourcing phenonmena.

The application “Disaster Risk Management Guide” for interactive Digital Terrestrial Television (iDTT), has been implemented based on the design that considers Learning Objects (LO) adapted to iDTT, where the receiving medium is the television and the main element of interaction is the remote control. The contents were worked on in coordination with the National Service for Risk and Emergency Management (SNGRE by its acronym in Spanish) of Ecuador, an organization that was also in charge of the validation. The implementation process, tests and improvements of the application are detailed, which includes three Learning Objects (LO) and a section with geographic information on emergency alerts in real time, obtained from a map server. Each LO addresses informational and educational topics, as well as a self-assessment for the viewer. The methodology for software development has been incremental, based on constant deliveries and progressive advances. The application has been developed in the Ginga NCL (Nested Context Language)-LUA programming language, and the tests have been carried out in two environments: 1) simulation with Ginga-NCL emulators and 2) using the Set Top Box (STB) EiTV Smartbox receiver equipment. The tests mainly detail the processes carried out to identify the audio and video formats supported in the two environments, the most appropriate options for integrating text in the interfaces, and the solution of problems encountered during the process. Finally, a usability analysis of the application is included with tests carried out in different age groups.

The paper focuses on enhancing the current or modern software development practices in Information Technology (IT) organizations. The research paper aims to address the gap between various hybrid software development approaches and existing practices that contribute to software development practices. The methodology adopted here is to obtain data from software professionals and understand how the current practices in the software development industry have contributed to the productivity of the employees and the IT organization, which has been done with the help of a survey questionnaire and by analyzing existing research articles and papers on the software development practices. This research is a conceptual model focused on a modern hybrid approach for software development, rather than focusing on a single software development approach, which can help IT organization increase productivity and deliver business value beyond customer expectations. The cost to build and time to market a software product or a software service can reduce by integrating the required software development practices. Today, staying relevant in the competitive market can be made easier by choosing the best available software development practices, frameworks, and models to fit an organization’s value and knowledge system. The conceptual model aims to reduce the gap between various hybrid software development approaches and existing practices contributing to software development. The paper concludes by discussing the benefits of the hybrid software development approach and urge IT organizations to adopt it as per their software development requirements and customer requirements.

One of the main goals of Software Engineering is to produce software with quality. But with the increasing use of agile methodologies in software development, it is observed that the existing quality assurance models do not adapt easily to these methods. In this context, the objective of this research is to propose critical factors of success (CFS) and tools for software development and management environment using agile methods, focusing on quality. Thus, initially, a literature review was conducted in SCOPUS and SCIELO bases, identifying 21 CFS, which were grouped into three categories: Individual; Organizational; and Technical / Process. Based on these factors, a questionnaire was applied to specialists in software management and development, reaching the sample of 101 respondents, with the most important CFS belonging to the Personal category, which reinforces the need for investment in this area. After this field research, a case study was done in a public company that uses traditional methods, making it possible to propose a development and management environment of software, adding the best practices, tools and CFS with the purpose of improve the quality of delivery of the final product. It was also observed the applicability of the agile Scrum method, allied to Kanban, taking advantage of the best practices of both, and how much was relevant in the context of the company, demonstrating the importance of agile methods to improve the quality and productivity of the whole team, including customers and sponsors. In addition, the present work generates an CFS base for knowledge of the academic community.

Until recently, the most software development tools and techniques were concentrated on views from the sequential model of program execution. Software developers who only familiarize with the sequential model will face unusual challenges of software projects that require multi-core or parallel programming. In this paper, we addresses the challenges that developers face as their projects requiring multi-core or parallel programming by applying design patterns. In general, design patterns are usually regarded as the role of quality-improver for improving software quality, but they could be the role of design-facilitator for facilitating design activities. To address this issue, we propose an approach for specifying the applicable contexts and refactoring steps of patterns systematically, as well as automating the refactoring process for lightening the burden of developers. We also extract a multi-core pattern ParallelWhile which is derived from the template class parallel_while of Intel ® TBB library to introduce our approach. Furthermore, we demonstrate our approach by a real-world multicore embedded system PVE (Parallel Video Encoder), where Command Pipeline pattern is designed for the design enhancement and platform migration. It aids developers identifying operations which could be parallel processing, and revising a sequential design as an Intel ® TBB parallel structure. In addition, our approach can promote the extensibility of parallel operations.