International Journal on Recent and Innovation Trends in Computing and Communication ISSN: 2321-8169

Volume: 6 Issue: 6 163 - 165

______________________________________________________________________________________
Motif and Conglomeration of Software Process Improvement Model

Poonam Chaudhary Dr. Sunita Chaudhary Dr. Amit Sanghi

Marudhar Engineering College, Marudhar Engineering College, Marudhar Engineering College,
Bikaner Bikaner Bikaner
er.girish@gmail.com er.sunita03@gmail.com dr.amitsanghi @gmail.com

Abstract:- SPI is defined as an organized system and regular process of making a software step up so that a business body or company can
produce and give classic software in a deadline of time as well as within the financial limitation. In the same concern I worked to produce a legal
and established model for the same. The work is fully dedicated towards development of classic quality oriented software and for the welfare of
the business body. The idea is fully based on the experience of the software project work of companies [1]. This work is with enclosed
estimation, progression improvement of the software, reasons and causes that sway on the process of SPI. The decisive reason was to build up a
model that could be practical in run through for the companies doing development work. There is a complete description of software principles,
process of the software and models of improvement. Here is a system model is purposed that is fully generic and that is beneficial for a small as
well as big organization. There are many existing models like CMM and Sigma Six and IDEAL. In the given work many drawbacks of these
models are removed to increase the performance. Many new things, steps and policies are applied to do the same. It has eliminated the
boundaries of the previous models. There are eight steps in the model those are if applied, used by any small, big company then there is a
guarantee of getting a classic product in term of quality, performance as compared to other models. In this a mixture of many corrective actions
has been used. The model is a growing and a step by step procedure but using the conventional method. It has limited the factor of risk up to a
good extent.
Keywords: - SPI, Software Principles, CMM, Six Sigma, IDEAL.
__________________________________________*****________________________________________________

I Introduction:- developed by the reputed organization SEI in the year of

In between 1960 to 1989, the field of software came under
emergency. The ratio of failure of the software was high at
that time due to software complexity of the development
procedure and comparative babyhood of the software
engineering as a business. The problems were over finance,
Time bounds, and Low excellence, Away from needs,
complicated code and uncontrollability [2].
In terms of software engineering the procedure of set of
tasks that are giving a product as a result are known as a
process. A simple software process improvement life cycle
is presented in the fig. 1.1
Define
Analysis Measurement
Change
Fig 1. A Software Life Cycle
1.1 Why SPI?
SPI converts an organization from undeveloped to mature an
undeveloped cannot develop can develop or produce well.
This is a biggest cause even many more cause can be there
[3].
1.2 Process Improvement Models
1.CMM or capability maturity models
It is a famous and well planned methods or technical to
improve the process of software engineering. It was
IJRITCC | June 2018, Available @ http://www.ijritcc.org
_______________________________________________________________________________________
1987. In the initial days it become so beneficial and famous
that soon a new version was issued called CMMI or
capability maturity models integration
In CMM five layers or levels are there. Each and every layer
is known as a level. The CMM is uses to assets the
companies to upgrade their method and techniques on the
basis of recent status of the process maturity and to know
about the crucial and complicated issued in improvement
and quality.
II IDEAL model
It is created by software engineering institute i.e. SEI. It is
basically an approach for the regular and ongoing step up by
using some special ordered steps those are crucial to achieve
a successful up gradation plan.
III SPICE Model
This model is a skeleton for the measurement of software
process. The scaffold is used by the enterprise going for the
arrangement, supervision, expansion, function, progress as
well as support of the software [2]. SPICE spots five levels
of process ability. These levels are so many matches with
SEICMM
So these models are upgrading the class of software product
within a time and financial limits. This proposed model is
known as SPIM model and removes the problems of
previous models. This proposed model eliminates many
drawbacks of CMM. It tells what to be done as well as how
the things will be done. It is an elastic model.
1. Problem Formulation
163
International Journal on Recent and Innovation Trends in Computing and Communication
Volume: 6 Issue: 6
______________________________________________________________________________________
Boundaries and Limitation of existing SPI Model:
By the review of literature we explore some boundaries of
the software as follows:
1. Limitations of CMM:
a. It tells what to be done but don’t tell how
b. It is based on redundant work.
c. It is basically a goal.
2. Limitation Regarding IDEAL model:
a. It is model of continual nature
b. It is a complete kind of method that is having no
recovery, so it is either succeeded or gets failure.
3. Boundaries of Six Sigma:
a. It concentrates on prioritization, concerning solution of
special problems. This is related to prioritize of strategy.
This is the only reason of faults in this model.
b. It is based on statistics.
c. This is an additional problem in Six Sigma that idea
concerning the thing that how a defect is constituted. In
case of no definition of defect, the defect or error cannot
be found.
d. Training of Six SIGMA is fully required to all the
employees but it is not possible to train them all, because
it is very hard to take all people away from their
responsibilities and to train all together, so there is a
need of proper time schedule as well as to take all people
to Six Sigma.
So these models are upgrading the class of software product
within a time and financial limits. This proposed model is
known as SPIM model and removes the problems of
previous models [7].
2. Implementation:-
SPI Model is a method or approach by which we get
excellence in project and process as compare to normal
process. A classic project is just the result of SPI. Because
SPI aims of good result with an available and committed
time and caring in terms of finance or budget [6]. SPI is
recommended by researchers. Here we are proposing a
method or SPIM which contains of eight sequential steps.
Fig.2 Software Process Improvement Model Steps
IJRITCC | June 2018, Available @ http://www.ijritcc.org
_______________________________________________________________________________________
ISSN: 2321-8169
163 - 165
3. Results:-
1. Comparison between CMM and SPIM
The main problem with the CMM model is that CMM give
the maturity level. That an organization across the level then
its entering the next level. But CMM does not specify the
implementation. In spite of this In SPIM model
implementation is defined and a proper document is
prepared for every process. CMM is works only a repeating
task. But SPIM model is not only repeating task but also
whole. If problem is change then this model works due to a
cyclic model. CMM is a goal and being used just as stamp
of approval. SPIM model is a method.
2. Comparison between IDEAL Model and SPIM
Ideal model is also a continuous model. But it is a full
method such that there is no recovery. Means either it is
success or fail.
But SPIM model is a cyclic model. So if any problem face
then it will work until improvement has not
completed.[8,10]
3. Comparison between Six Sigma and SPIM
SixSigma is a statistically-based process improvement
methodology that aims to reduce defects to a rate of 3.4
defects per million defect opportunities by identifying and
eliminating causes of variation in Business processes. But
SPIM model is a planned methodology of continuous
improvement methodology. Six Sigma methodology works
on two approaches DMAIC, DMADV. But SPIM works as
a full flash model [12, 13]. Six Sigma focuses on prioritizing
and solving specific problems which are selected based on
the strategic priorities of the company and the problems
which are causing the most defects. But SPIM model does
not focus on prioritizing and solving problems. SPIM model
solve all types of problems [14, 15].
IV Conclusion
The SPIM software procedure development model upgrades
a process in a conventional way. This model has proven an
iterative nature. It is a sequential model that enhances the
quality. It takes all user needs, software excellence pledge
as well as the view of the company or the enterprise. A lot
of factors can be originated in the association from by using
the SPIM model as administration assurance and teamwork
can be easily build up. SPIM model removes the constraints
of alive models (CMM, SIX SIGMA,IDEAL).As For
model, the main restraint of CMM in key rehearsal describes
what to be done but not able to explore that how to do [20,
21]. SPIM model depict the functioning and fix that how
things will be done. SPIM is a fully elastic model. In case of
any change or modification SPIM work in such a way that
changes can be reflected easily and lot of purgation can be
achieved successfully.
164
 International Journal on Recent and Innovation Trends in Computing and Communication ISSN: 2321-8169
Volume: 6 Issue: 6 163 - 165
______________________________________________________________________________________
V References [19] Pave1 Mach, Jessica Guhqueta Department of Electro
[1] Jesper Arent, Jacob Nørbjerg, Software Process Improvement technology Czech Technical University in Prague, Faculty of
as Organizational Knowledge Creation: A Multiple Case Electrical Engineering, Utilization of the Seven Ishikawa
Analysis, Proceedings of the 33rd Hawaii International Tools (Old Tools) in the Six Sigma Strategy, 24th
Conference on System Sciences – 2000 International Spring Seminar on Electronics Technology May
[2] Dr. David J. Szymanski and Capt. Thomas D. Neff, Defining 59,2001, Calimanesti-Caciulata, Romania
Software Process Improvement [20] Ian Sommerville, Lancaster University, UK, “Software
http://www.stsc.hill.af.mil/crosstalk/1996/02/defining.asp, Documentation, Printed 7/11/01.This paper is a revised
February 1996 version of Chapter 30 from my book Software Engineering,
[3] Laurie Honour Werth, “Lecture Notes on Software Process 4th edition, published by Addison Wesley in 1992”.
Improvement” document number CMU/SEI-93-EM-8, [21] Pierre Juliard, Juliard Associates Brookfield, Connecticut,
copyright 1993 by Carnegie Mellon University, Introduction total quality management - making the concept work
to Software Process Improvement.
[4] Mohd Hairul Nizam Md. Nasir, Rodina Ahmad, Noor Hafizah
Hassan, Resistance Factors in the Implementation of
Software Process Improvement Project, 978-1-4244-2328-
6/08/$25.00 © 2008 IEEE.
[5] Anthony Finkelstein, A Software Process Immaturity Model
Imperial College, 180 Queens Gate, London SW7.
[6] Donna K. Dunaway, Steve Masters, CMM SM -Based
Appraisal for Internal Process Improvement (CBA IPI):
Method Description, April 1996.
[7] http://cmmcmmi.wordpress.com/2007/01/16/history-of-
cmm/,History of CMM, Posted by obi on January 16, 2007.
[8] Mark C. Paulk, Charles V. Weber, and Mary Beth Chrissis
Software Engineering Institute, USA, The Capability Maturity
Model" for Software.
[9] Jianguo Li, Jinghui Li, and Hongbo Li, Research on Software
Process Improvement Model Based on CMM.
[10] Software Testing Standards-CMM Levels, url <
http://forum.onestoptesting.com/ forum_ posts.
asp?TID=3368>.
[11] Thomas Pyzdek, “The Six Sigma Project Planner: A Step-by-
Step Guide to Leading a Six Sigma Project Through
DMAIC“, McGraw-Hill, 2003.
[12] Zhedan Pan, Hyuncheol Park, Jongmoon Baik,Hojin Choi, A
Six Sigma Framework for Software Process Improvements
and its Implementation, 14th Asia-Pacific Software
Engineering Conference, School of Engineering, Information
and Communications University, 119 Munji-ro, Yuseong-Gu,
Daejeon, Republic of Korea
[13] Bhote, K. R. (1989). Motorola's long march to the Malcolm
Baldrige National Quality Award, National Productivity
Review, 8(4), pp. 365-376.
[14] Alain A. April, François Coallier, Trillium V3.0 A Model for
the Assessment of Telecom Software System Development
Capability.
[15] An Introduction to the Documents Url<
http://www.sqi.gu.edu.au/spice/suite/intro.html >
[16] D. H. Kitson, Relating the SPICE framework and SEI
approach to software process assessment, volume 5, number 3
/ september, 1996, 145-156.
[17] Mitchell K. D. Ram Department of Management Science and
Information Systems, University of Auckland., Total Quality
Management in Software Engineering] .
[18] Paulk.M,Tqm and CMM: Software CMM Q&A #4, Software
engineering Institute,April 7th 1997,Url:
http://www.sei.cmu.edu/activities/cmm/docs/q- aanda-.4.html

165
IJRITCC | June 2018, Available @ http://www.ijritcc.org
_______________________________________________________________________________________