scholarly journals Towards Specific Software Engineering Practices for Early-Stage Startups

Author(s):  
Jorge Melegati ◽  
Rafael Chanin ◽  
Afonso Sales ◽  
Rafael Prikladnicki

Abstract In this position paper, our goal is to argue the need for specific software development practices to early-stage startups. In order to reach this goal, we discuss the consequences of innovative and market-driven contexts, which are two of the key elements when describing software startups. We also argue that these practices could be applied to innovative initiatives within established companies since they share similar characteristics and challenges as those from startups.

2000 ◽  
Vol 8 (4) ◽  
pp. 211-230 ◽  
Author(s):  
Philip W. Grant ◽  
Magne Haveraaen ◽  
Michael F. Webster

It has long been acknowledged that the development of scientific applications is in need of better software engineering practices. Here we contrast the difference between conventional software development of CFD codes with a method based on coordinate free mathematics. The former approach leads to programs where different aspects, such as the discretisation technique and the coordinate systems, can get entangled with the solver algorithm. The latter approach yields programs that segregate these concerns into fully independent software modules. Such considerations are important for the construction of numerical codes for practical problems. The two approaches are illustrated on the coating problem: the simulation of coating a wire with a polymer.


Software industries have been growing with the rise of automation technologies and looking for change in their software development practices to gain the benefits of automation technologies for achieving their business goals. Agile Business Process Reengineering (ABPR) is trending approach for Software Engineering Management (SEM) in software industries, which helps software development organization in transformation of software development practices. Scrum and Kanban are fascinating Agile methodologies adopted by Software Engineering Management practitioners. Scrumban, a mixture of both Scrum and Kanban, has derived strengths of both frameworks, in formation of a robust framework against challenges of Agile Software Engineering (ASE) methodologies like work flow control, lead time management, product delivery that could not be solved by Scrum or Kanban as a standalone framework. But still some of challenges, which are out of scope of Scrumban like project requirement documentation, planning, scheduling, estimation and clear product vision at initial stage of the project. Such issues have raised a request of research for Software Process Reengineering (SPR) in Scrumban by customizing its structure for to form the next level of hybrid framework. The Traditional SDLC methodology ‘Waterfall’ has answers for such issues. An empirical analysis, for resolution of such issues, with the help of ‘Waterfall’ model and its life cycle protocols is the main goal this research study by integrating Scrum and Kanban with Waterfall to form a hybrid framework ‘Scrumbanfall’ aligning Kanban in center of integration under the boundary of Scrum rules. This research also highlights limitations of Scrumbanfall like team members and their roles and capabilities for the large scaled project having team members in distributed environment, which open the door for next level of research to overcome such challenges using further hybridization of Scrumbanfall.


2003 ◽  
Vol 02 (01) ◽  
pp. 127-141 ◽  
Author(s):  
BRAIN A. BERENBACH ◽  
PETER R. SPOOL ◽  
DIETER BITTERLE

Over the years, control systems have become increasingly dependent on custom software. As hardware has gotten cheaper, attention has focused on improving the processes associated with developing control system software by using approaches such as the Software Engineering Institute's Capability Maturity Model (CMM),1,2 and enabling reuse and long term cost reduction with component-based software development. This paper discusses the application of the CMM to the software process used in control engineering and the use of component based software development. We also discuss some advanced features of the Siemens SIMATIC STEP 7 Universal Development Environment that provides the tools to plan, configure, evelop, test, troubleshoot, document and support not only PLC programs, but also entire auto, ation projects. STEP 7 also enables and support process improvement and component-based software development.


2012 ◽  
pp. 1627-1645
Author(s):  
Doncho Petkov ◽  
Denis Edgar-Nevill ◽  
Raymond Madachy ◽  
Rory O’Connor

The chapter provides possible directions for the wider application of the systems approach to information systems development. Potential improvement of software development practices is linked by some leading experts to the application of more systemic ideas. However, the current state of the practice in software engineering and information systems development shows the urgent need for improvement through greater application of systems thinking.


2021 ◽  
Vol 172 ◽  
pp. 110848
Author(s):  
Elvira-Maria Arvanitou ◽  
Apostolos Ampatzoglou ◽  
Alexander Chatzigeorgiou ◽  
Jeffrey C. Carver

Author(s):  
Michael Felderer ◽  
Wilhelm Hasselbring ◽  
Heiko Koziolek ◽  
Florian Matthes ◽  
Lutz Prechelt ◽  
...  

AbstractThe need to improve software engineering practices is continuously rising and software development practitioners are highly interested in improving their software systems and the methods to build them. And well, software engineering research has numerous success stories. The Ernst Denert Software Engineering Award specifically rewards researchers that value the practical impact of their work and aim to improve current software engineering practices. This chapter summarizes the awards history as well as the current reward process and criteria.


2022 ◽  
Vol 8 ◽  
pp. e839
Author(s):  
Adeeb Noor

Background Bioinformatics software is developed for collecting, analyzing, integrating, and interpreting life science datasets that are often enormous. Bioinformatics engineers often lack the software engineering skills necessary for developing robust, maintainable, reusable software. This study presents review and discussion of the findings and efforts made to improve the quality of bioinformatics software. Methodology A systematic review was conducted of related literature that identifies core software engineering concepts for improving bioinformatics software development: requirements gathering, documentation, testing, and integration. The findings are presented with the aim of illuminating trends within the research that could lead to viable solutions to the struggles faced by bioinformatics engineers when developing scientific software. Results The findings suggest that bioinformatics engineers could significantly benefit from the incorporation of software engineering principles into their development efforts. This leads to suggestion of both cultural changes within bioinformatics research communities as well as adoption of software engineering disciplines into the formal education of bioinformatics engineers. Open management of scientific bioinformatics development projects can result in improved software quality through collaboration amongst both bioinformatics engineers and software engineers. Conclusions While strides have been made both in identification and solution of issues of particular import to bioinformatics software development, there is still room for improvement in terms of shifts in both the formal education of bioinformatics engineers as well as the culture and approaches of managing scientific bioinformatics research and development efforts.


: DevOps is the form of software engineering practices for software used to have better collaboration among teams and help deliver the business product in a timely manner and meet the business requirements. The growing demands from the customers and the competition among similar products give rise to better principles in DevOps than ever before. There exists current trend in industry to adopt cloud based solutions as compared to other solutions. This gives rise to certain evolution in the way DevOps is done in industry. This main purpose of this paper is to address the changes in the way DevOps is carried in industry and the scope of it due to evolving industry needs and newer emerging tools. The paper is structured in to provide an introduction to modern DevOps and the necessity of adoption of DevOps, DevOps applied in SDLC phases, tool concerning DevOps, Evolution of DevOps in modern software development and conclusion.


Sign in / Sign up

Export Citation Format

Share Document