THE APPLICATION OF MODERN SOFTWARE ENGINEERING PRACTICES TO CONTROL ENGINEERING

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.

Author(s):  
GREG TWAITES ◽  
MICHELLE L. SIBILLA

Developing and delivering quality software in a timely fashion has proven to be a difficult goal to obtain. Defining a thorough and effective software development process lays the foundation for successful projects. The Software Engineering Institute's (SEI) Capability Maturity Model (CMM) defines the framework for such a process. This paper examines the implementation of an SEI Level 5 process within the Communication Systems Division at General Dynamics Decision Systems. A brief review of the CMM is presented followed by an overview of the organization. Examples of the organizations software development process are cited.


Respati ◽  
2020 ◽  
Vol 15 (1) ◽  
pp. 43
Author(s):  
Ita Permatahati ◽  
Wing Wahyu Winarno ◽  
Mei P Kurniawan

INTISARIMenerapkan standarisasi pada suatu perusahaan yang bergerak dibidang pengembangan perangkat lunak merupakan salah satu cara untuk meningkatkan kualitasnya. CMMI merupakan salah satu standarisasi yang penulis pilih untuk mengetahui tingkat kematangan dari divisi Innovation CenterAmikom. CMMI yang digunakan ialah CMMI for Development versi 1.3 yang fokus terhadap tingkat kematangan di level 2 dengan 6 proses area. Penelitian ini mengambil 1 sample proyek di Innovation Center(IC) yaitu apliksai presensi berbasis mobile. Berdasarkan hasil dari pengukuran yang telah dilakukan, proses pengembangan lunak di IC berada di tingkat 1 (Initial) yang diketahui bahwa belum semua praktik yang ada di masing-masing 6 proses area diterapkan. Kata kunci— proses pengembangan perangkat lunak, CMMI, CMMI-DEV, Representasi Bertingkat, Tingkat Kematangan. ABSTRACTApplying standards to a company engaged in the development of devices is one way to improve its quality. CMMI is one of the standards chosen by the author to find out the level of maturity of the Innovation Center at Amikom. CMMI is used for CMMI for Development version 1.3 which focuses on the level of maturity at level 2 with 6 process areas. This study took 1 sample project at the Innovation Center (IC), a mobile-based presence application. Based on the results of the measurements that have been made, the development process at the IC is at level 1 (Initial) related to all the practices that exist in each of the 6 process areas that are applied.Kata kunci—  software development process, CMMI, CMMI-DEV, Leveled Representation, Maturity Level.


2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.


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.


Author(s):  
Marco Liberato ◽  
João Varajão ◽  
Paulo Martins

Companies focus on software development in order to survive in a highly competitive world. They not only need to keep up to date with the changes that are occurring in their environment, but they also need to assure the effectiveness of their processes. One way to do that is pursuing high quality standards by continuously improving the development processes. In this chapter, the authors describe the project of CMMI (Capability Maturity Model Integration) implementation in a software company specialized in information technology services for banking. The project was initiated with the aim of optimizing the software development process. Throughout the chapter, various aspects of the project are covered, such as the actions taken to implement the CMMI maturity level 2, the tools used to support the implementation, and the obtained results. These are useful and could serve as a reference basis for companies that consider the implementation of a maturity model.


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.


2016 ◽  
Vol 29 (4) ◽  
pp. 35-48
Author(s):  
Mousumi Kabir ◽  
Lazar Rusu

In many research studies on IT project development process, the authors have noticed that different frameworks are used for this purpose. In fact, many companies choose specific frameworks to run their IT projects based on project type and face dissimilar problems during the execution. In this research the authors are presenting a framework for IT project development using Capability Maturity Model. The framework has been developed to improve the IT project development in a large company because of the lower rate of successfully IT projects in that company. To develop the framework, they have used design science research and evaluated this framework with the project managers from that large company. The result of this research is a framework for IT projects development that is based on generic Capability Maturity Model and is adapted to the specific needs of an IT project development environment. Moreover, the framework identifies for each key process area of IT project development, the goals and activities to be performed.


Author(s):  
Daniel M. Brandon

Software engineering is vital for the proper planning of IT projects, although it is not a formal part of project management. The software engineering embedded in the acquired products will significantly affect long-term project success factors, even for IT projects that primarily involve software acquisition and integration instead of software development,. In this chapter I review software engineering and its relation to IT project management.


Sign in / Sign up

Export Citation Format

Share Document