SOFTWARE ENGINEERING IN AN SEI LEVEL-5 ORGANIZATION

2002 ◽  
Vol 09 (04) ◽  
pp. 347-365 ◽  
Author(s):  
GREG TWAITES ◽  
MICHELLE L. SIBILLA
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Communication Systems ◽  
Development Process ◽  
Maturity Model ◽  
Software Development Process ◽  
Decision Systems ◽  
Capability Maturity ◽  
General Dynamics ◽  
Timely Fashion

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.

Penerapan Capability Maturity Model Integration Untuk Mengukur Tingkat Kematangan Organisasi Dalam Proses Pengembangan Perangkat Lunak (Studi Kasus: Direktorat Innovation Center Universitas Amikom Yogyakarta)

Respati ◽  
2020 ◽  
Vol 15 (1) ◽  
pp. 43
Author(s):  
Ita Permatahati ◽  
Wing Wahyu Winarno ◽  
Mei P Kurniawan
Keyword(s):  
Software Development ◽  
Development Process ◽  
Model Integration ◽  
Maturity Model ◽  
Software Development Process ◽  
Maturity Level ◽  
Capability Maturity ◽  
Level 1 ◽  
A Company ◽  
Level 2

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.

Practical Experience in Customization for a Software Development Process for Small Companies Based on RUP Process and MSF

2011 ◽  
pp. 71-93 ◽  
Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Practical Experience ◽  
Software Development Process ◽  
Small Companies ◽  
Engineering Process ◽  
Software Projects ◽  
Software Engineering Process ◽  
Unified Process

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).

Boosting the Competitiveness of Organizations With the Use of Software Engineering

2021 ◽  
pp. 198-216
Author(s):  
Mirna Muñoz
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Research Work ◽  
Software Development Process ◽  
The Core ◽  
Development Organizations ◽  
Technological Base ◽  
The One

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.

A Proposed Pragmatic Software Development Process Model

2018 ◽  
pp. 448-462
Author(s):  
Sanjay Misra ◽  
M. Omorodion ◽  
Amit Mishra ◽  
Luis Fernandez
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Rapid Growth ◽  
Process Model ◽  
Development Process ◽  
Technological Development ◽  
Software Development Process ◽  
The World ◽  
Society Today

The rapid growth in technology and the dynamism in our society today poses a lot of problems for Software Engineering practitioners. The result is a series of software development process methods that can be used to combat or meet up with the problems. What we can do is evolve, grow, and adapt to the changes that come along with development. This is the dynamism inherent in man—to adapt to change and improve ourselves and our existing systems—since the world is a far cry from what it was a few decades ago. On this basis lay the need to develop the model proposed in this chapter to meet the variations that exist as a result of technological development.

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.

SOFTWARE WAREHOUSE: ITS DESIGN, MANAGEMENT AND APPLICATION

2004 ◽  
Vol 14 (04) ◽  
pp. 395-406 ◽  
Author(s):  
HONGHUA DAI ◽  
WEI DAI ◽  
GANG LI
Keyword(s):  
Data Mining ◽  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Innovative Approach ◽  
Design Management ◽  
Software Development Process ◽  
Software Applications ◽  
High Efficient ◽  
Efficient Software

To have an effective and efficient mechanism to store, manage and utilize software sources is essential to the automation of software engineering. The paper presents an innovative approach in managing software resources using software warehouse where software assets are systematically accumulated, deposited, retrieved, packaged, managed and utilized, driven by data-mining and OLAP technologies. The results lead to streamlined high efficient software development process and enhance the productivity in response to modern challenges of the design and development of software applications.

SyBeL: A SYSTEM MODELLING LANGUAGE ENHANCING AUTOMATIC SUPPORT IN THE SOFTWARE DEVELOPMENT PROCESS

2013 ◽  
Vol 23 (02) ◽  
pp. 223-257
Author(s):  
GIUSEPPE DELLA PENNA ◽  
SERGIO OREFICE ◽  
BENEDETTO INTRIGILA ◽  
DANIELE MAGAZZENI ◽  
ROBERTO DEL SORDO ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
System Modelling ◽  
Test Cases ◽  
Practical Case ◽  
Software Development Process ◽  
Functional Requirements ◽  
Modelling Language ◽  
System Behaviour

In this paper we present SyBeL (System Behaviour modelling Language), an XML based formalism for software system modelling. In particular, SyBeL focuses on the description of the system behaviour in order to capture its functional requirements and has been designed to fulfill some of the most trendy software engineering issues. The use of the underlying XML language makes the artifacts generated by SyBeL immediately available to further automatic manipulation (e. g., to automatically generate test cases) without the need of intermediate models, as usually done in semi-formal approaches. Moreover, we are experimenting SyBeL on a variety of practical case studies.

A Systematic Approach to Generate and Conduct Destructive Security Test Sets

2011 ◽  
Vol 403-408 ◽  
pp. 4495-4498
Author(s):  
K. Madhuri ◽  
M. Suman ◽  
M. Nalini Sri ◽  
K. Ravi Kumar ◽  
U. Jyothi Kameswari
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Systematic Approach ◽  
Functional Testing ◽  
Software Development Process ◽  
Security Testing ◽  
Software Engineers ◽  
Test Sets ◽  
Security Test

Security testing involves two approaches; the question of who should do it has two answers. Standard testing organizations using a traditional approach can perform functional security testing. For example, ensuring that access control mechanisms work as advertised is a classic functional testing exercise. Systematic security testing approaches should be seamlessly incorporated into software engineering curricula and software development process. Traditional software engineering textbooks failed to provide adequate methods and techniques for students and software engineers to bring security engineering approaches to software development process generating secure software as well as correct software. This paper argues that a security testing phase should be added to software development process with systematic approach to generating and conducting destructive security test sets following a complete coverage principle. Software engineers must have formal training on writing secure code. The security testing tasks include penetrating and destructive tests that are different from functional testing tasks currently covered in software engineering textbooks Moreover, component-based development and formal methods could be useful to produce secure code, as well as automatic security checking tools. Some experience of applying security testing principles in our software engineering method teaching is reported.

Sign in / Sign up

Export Citation Format

Share Document