Abstract: This paper presents an approach based on a practical experience in applying agile and lean practices in a software development process performed into an organization evaluated CMMI level 5. As a result of a theoretical review on agile and lean practices, and the organization's needs, an integrated proposal between these practices and CMMI was found and was also put into practice. The work carried out by the organization using this proposal led to a successful integration experience in order to innovate, improve product quality, get clients' satisfaction, and the most important, show the feasibility of coexisting of CMMI and agile practices resulting in a significant improvement for the organization.

Abstract: During the last decade, software engineering researchers have tried to identify the success and obstacle factors to the software development. Conclusions from many of the researches related to the issue show that software process is one of the most important subjects contributing into the success or failure to the software development. Among the Capability Maturity Model Integration (CMMI), the ISO9000 series, Total Quality Management, and other best process practices, the CMMI is the one specially focusing on the software development. However, as evolving from the Capability Maturity Model for Software (SW-CMM), the CMMI has inherited some process issues that can severely degrade the effectiveness of process maturity of an organization. In this paper, we demonstrate some of the issues existing in current version of the CMMI. The upward only maturity level certification method is a major issue. Another major issue for the CMMI is its lack of process practice(s) for organizations and their suppliers that have higher maturity level than they do. Some possible remedies for those issues are also proposed to improve the CMMI.

Abstract: Software development is a knowledge-intensive work and the main attention is how to manage it. The systematic reviews of empirical studies presents, how knowledge management is used in software engineering and development work. This paper presents how knowledge is used in agile software development and how knowledge is transferred to agile software using agile manifesto. It then argues for the need to scale agile development strategies in knowledge management to address the full delivery. The paper explores the eight agile software scaling factors with knowledge management and their implication for successfully scaling of agile software delivery to meet the real world needs of software development organization.

Abstract: Organizations delivering offshore software development services have traditionally focused on CMMI framework to deliver quality software. With agile methodologies gaining more wide spread acceptance, such organizations cannot stay away from them. There are concerns about combining agile methodologies with offshoring. There are also concerns about mismatch of agile methodologies with CMMI framework.In this paper we have looked at the problem from the perspective of an offshore software development organization and recounted our experience in adopting agile methodology in executing fixed price agile project. The challenges we have faced comes from three different dimensions. First is to address the issue of having an agile team split across two different countries. The second is to execute the agile project within the framework prescribed under CMMI. Here the challenge is not only to address the actual gap between CMMI and agile methodologies but also to address the perceived shortcomings of agile methodologies. The third dimension is to execute the project as a fixed price one where the requirement is not frozen at the beginning of the project.We have listed the challenges that we have faced. They can be categorized under requirements management, contract management, team management, distributed working, when to design, role of a specialist, testing challenges and CMMI adherence. The different solutions tried and the levels of success in overcoming them have also been included. Our experience indicates that agile methodologies can coexist with offshoring and CMMI framework.

Abstract: In the software industry, a large number of projects fail and billions of dollars are spent on failed software projects. Lacks of poor selection process of software development life cycle (SDLC) models is some of the top reason of such failure. By selecting right software process model a better and high quality product can be found within budget and time. In this paper, an approach is proposed to select an appropriate SDLC model based on different project characteristic categories. In this paper, a comparison approach of SDLC process is introduced, which is based on project characteristic categories and then categories are classified. Paper described about comparison tables of SDLC models, and better selection process of SDLC models.

Abstract: Validation is one of the software engineering disciplines that help build quality into software. The major objective of software validation process is to determine that the software performs its intended functions correctly and provide information about its quality and reliability. This paper identifies general measures for the specific goals and its specific practices of Validation Process Area (PA) in Capability Maturity Model Integration (CMMI). CMMI is developed by Software Engineering Institute (SEI). CMMI is a framework for improvement and assessment of a software development process. CMMI needs a measurement program that is practical. The method we used to define the measures is to apply the Goal Question Metrics (GQM) paradigm to the specific goals and its specific practices of Validation Process Area in CMMI.

Abstract: with the advent of CMMI in the late 1990s, software companies tried to use a kind of score to rank themselves in the market. Being a CMMI level five company for a long time represented the epitome of highly qualified company. This phenomenon is also emerging in the agile software development with the emergence of methods such as Nokia or comparative test agility. This paper presents an analysis of how these methods are placed in the context of agile software development and its contribution to the improvement of software process in the same context from a case study developed in real companies.

Abstract: : Capability Maturity Model Integration (CMMI) is a process improvement approach that provides the essential elements of effective processes that ultimately improve organizational performance. It is estimated that over 1,200,000 people worldwide work in organizations that have conducted process appraisals using CMMI. Early versions of the CMMI paid little attention to architecture, agility, product lines, and other modern engineering practices. A significant change to the CMMI V1.3 models (released in November 2010) is the new emphasis on the role of architecture in the design process. This presentation will address the basics of architecture-centric engineering and show where and how these practices are now reflected in the CMMI models. Topics will include: process improvement and CMMI; structure of the CMMI models; essential architecture-centric engineering practices; architecture-centric engineering practices in CMMI V1.3; additional modern engineering practices in CMMI V1.3.

Abstract: i ACKNOWLEDGMENTS ii TABLE OF CONTENTS iii LIST OF TABLES vi LIST OF FIGURES vii ABBREVATIONS viii

Abstract: Rational unified process is an advanced software development process,unified modeling language is a powerful visual modeling languageThis paper combines with the information system of shopping membership card,follows the RUP phase of the life cycle,and uses UML modeling systemIn the process of system modeling,model building can be corresponded derivation and conversionThe guidance of software development combined RUP with UML,improves the quality and efficiency of software development and maintenance

Abstract: Risk is everywhere in the software development process,how to control the software project risks is one of important problems in software engineering research field.Software development process methodology has a positive effect on the control software risks,RUP,CMM can control software project risks well.Many scholars have used different methods or techniques to analyse or manage the software project risk.

Abstract: Aspect-Oriented Software Development (AOSD) concentrates on determination and modularization of orthogonal concerns that cut across system modules. An aspect-oriented extension framework helps transform existing methodologies into processes which support AOSD. The authors propose a framework for extending agile methodologies with AOSD features. The stages required for constructing the framework have been identified by scrutinizing existing aspect-oriented methodologies and practices in order to extract the AOSD-specific stages required in each phase of the agile development process. Analysis shows that a methodology extended through this framework can be superior in agility in comparison to a general aspect-oriented methodology.

Abstract: In this paper, we propose a theoretical framework for software quality within the healthcare sector. The aim of this framework is to improve the quality of software produced within the healthcare and medical device industries, while assisting the manufacturers in achieving compliance with existing regulation. To develop this framework, we undertook an evaluation of the healthcare and medical legislation. This was followed by an evaluation of existing software quality standards and models. The CMMI model was chosen as the model on which to base this framework. An initial mapping between CMMI and the US FDA Code of Federal Regulations was undertaken. We present some of the examples the mapping here.

Abstract: CMMI model, a model for the improvement and evaluation processes for the development, maintenance and operation of software systems. Any software company just because there is at level 1. To improve the way people work and get better results should advance to level 2 CMMI, and it should acquire the skills needed to interpret the practices defi ned in level 2 of CMMI, understand the benefi ts, understand the stages of implementation of a process improvement aligned to CMMI, what

Abstract: Recent empirical research have been conducted identifying a number of advantages of agile software development methods by comparing them to traditional methodologies. However, from the first waterfall to current agile methodology there still have some obstacles that makes software delivery challenging and heavy-duty work. In order to make a clear distiction and insight into the theoretical and practical value of agile and traditional methodologies, in this paper a qualitative comparison of MSF, as representatnive of iterative methodology, and Scrum, as representative of agile methodologies, are presented.