Model Transformations Carried by the Traceability Framework for Enterprises in Software Industry

Capability Maturity Model Integration (CMMI) for Optimizing Object-Oriented Analysis and Design (OOAD)

Software evolution is a process that is a current need of the software industry and software users, either it is an organization or an individual. In this paper, an analysis of different things related to software evolution will be seen. It is a study towards some mature software evolution process which Capability Maturity Model Integration (CMMI). We will see an aspect of software evolution in Pakistan. CMMI history will be under the discussion of how it evolves and the benefits of using it. We will make a comparison of different evolution process models with CMMI to have a look at its competencies. We will have a view of Lehman Law and finally CMMI involvement in the Pakistan software industry. Section 1 will be the Introduction and the importance of software evolution in Pakistan. Section 2 CMMI History will be discussed, and Sect. 3, depicts CMMI Comparison. Section 4.1 will introduce Lehman Law, and finally, Sect. 5 is Analysis.KeywordsCMMISoftware evolutionLehman lawRequirement changes

CMMI(Capability Maturity Model Integration) is a process framework which is organized by goals, practice and process area. The Maturity Level 3 stressed that the project level process must be tailored from the organization level process, that is to say, no matter how the project level process changes, it must satisfy the constraints of the organization level process. However, companies usually prefer to choose detailed and operational single-layered process models for applying CMMI. If some activities in process have been changed, the process model must be totally redesigned, this reduces the flexibility and increases the cost of adopting CMMI. In order to solve the above problems, this paper presents a multi-layered model, in which the upper layer is used to describe the CMMI organization level process (i.e., the software development lifecycle) and the lower layer is used to describe the project level process model (i.e., the procedure of each development group). At the same time, we provide delegation relationship in multi-layered process model to build the constraints between the upper layer and the lower layer process model, it brings the flexibility that the lower layered model (the project process) can change its activities on the premise that obeying the constraints of upper layered model (the organization process). Finally, in order to validate the practical effectiveness of this model, a CMMI case from GUODIAN Nanjing Automation Cd., LTD is provided.

Pakistan's software industry is quite young as compare to the developed world and particularly in comparison with India. This report presents different statistics about Pakistan's software industry; especially current number of Software-Capability Maturity Model (SW-CMM) / Capability Maturity Model Integration (CMMI) appraisals and efforts made by different institutions like Pakistan Software Export Board (PSEB), Ministry of IT and Pakistan Software Houses Association (PASHA). This study shows that even after introducing attractive incentives and packages by PSEB and Ministry of IT, Pakistan's IT industry is still moving slowly towards adopting the CMMI framework. The reason for this is being highlighted in this paper after a comprehensive study on the topic and software industry's data analysis. On the basis of this analysis few recommendations are also made.

Capability Maturity Model Integration or CMMI (Capability Maturity Model Integration) is a combination of process improvement models for what is systems engineering, and software, is derived from CMM, differentiating itself from this by the integration of some quality models such as the Electronic Industries Alliance Interim Standard (EIA / IS) 731. Basically the CMMI, is a global certification to measure the maturity of an organization in the design and development of software, to give us an idea of this certification, just There are 117 organizations around the world that can boast of having it. Currently it is one of the most used models worldwide in the software industry, which when applied mainly allows the reduction of costs and decreases the repetition of work.

This paper explores a way to expand business using ethnography as an industrial service or product. First, a challenge that companies are facing and trying to deal with, which is industrialization is described. In the software industry, as computer prices go down, the requirements for software development involve accurate estimates of the cost, the time and the resources involved in the process. Due to these new market demands, software development reached a level of maturity, which required a new approach to product development. Likewise, as ethnography grows into more intricate realms, there is a need for a more robust approach to ethnography application in business to help it achieve the right maturity level of industrialized processes. In this context of complexity, case studies from Fujitsu and examples from literature were used to test the Capability Maturity Model Integration (CMMI) framework to use to evaluate the practice of ethnography in business. As a result, a brief assessment of ethnography using the CMMI framework is shown. It describes how ethnomethodology can be used in a repeatable manner and provides results within a small margin of difference in quality. Finally, a reflection on the value of experts in this new trend in ethnography is described.

Many studies have been carried out to investigate what makes up good quality software. Some of the early models that define the quality of software come from Boehm (1976) and McCall (1977). Works in this field of quality models have traditionally focused on quality of the final software product. Since the 1970’s models of software have been used and this has recently attracted much attention through the popularity of model-driven software development (MDSD). However, quality of software models has rarely been considered (Lange & Chaudron, 2005). In the software development life cycle, the ability to assure software quality long before the testing phase may save a lot of money since less defects found in the testing phase will mean less effort to be allocated for rework. Currently, the importance of model quality is starting to gain attention from computer scientists. Work in this area has since focused on developing tools, metrics, and frameworks to improve the quality of models that guide implementation, particularly in the context of UML modeling which has become the de facto standard for building object oriented software. Quality of models can be considered from many different perspectives. In this chapter, we will consider the following perspectives: Firstly, is the model complete in the sense that it describes the information that developers need to know about a system? Secondly, we look at the degree in which a model of a system and an implementation correspond. This degree of correspondence indicates to what extent analyses of—or predictions based on the model are valid for the implementation. We present the main findings from case studies into quality of modeling in the software industry as well as findings from a survey amongst professional software developers. We also provide a discussion on the contemporary methods for design quality assessments.

Since Gamma et al. published their design patterns, patterns are very popular in the area of software engineering. They provide best practice to handle recurring problems during the software development phase. Three years later, security patterns appeared and provided solutions for security problems. Besides the name analogy, design and security patterns should be very similar except for the security factor. In research and industry software engineering with design patterns is widespread. However, some researchers suspect that security-pattern engineering is made difficult by some issues such as terminology or description form. Detecting adoption problems can help to improve security patterns in future. Thus, they can promote the awareness of security especially in the software maintenance phase where many programmers first give attention to security problems. Therefore, we will compare design and security patterns to find indicators for negative impact on security pattern engineering in software development. We address this issue on inspecting the aspects classification, description form, provided code examples, and usage in the software life-cycle. We determine the degree of maturity of software-security patterns by comparing them to the well-explored design patterns. To achieve the objective, we inspect the pattern terminology and conducted a study on the used description forms including provided UML diagrams and code examples. Moreover, a literature review is conducted to compare their state of research w.r.t. the software life-cycle. The maturity degree of security patterns compared to common design patterns differs and we depict further research opportunities on security patterns.

By defining requirement management rules in the early project phase, the developed product can usually be assured to satisfy customer requirements and increase customer satisfaction. The capability maturity model integration (CMMI) requirement management process area is proved to be the best-practice model for requirement management. However, many investigators have claimed that the introduction of the process area creates two challenges for software engineering: (1) it is difficult to trace and measure requirements, and (2) it requires preparation and management of a large amount of inevitable documentation jobs. This research implements a shark-tooth software development model and scenario analysis of aspectual use case to develop a collaborative requirement management system which complies with CMMI. A case study is used to investigate the practical benefits of the system. Application results have helped the company improve the software development environment in many aspects including easier requirement management, more effective development cycle, and better resource integration.KeywordsRequirement managementcapability maturity model integration (CMMI)shark-tooth software development modelaspectual use case

Business intelligence (BI) is a managerial concept helping managers and organizations to manage information and make factual decisions. Some have introduced Business Intelligence as a process of turning data into information and then into knowledge. This concept has become a popular trend for businesses interested in adding value to their decision making processes. Measurement of maturity in implementing Business Intelligence process in organizations is considered a critical issue. Business intelligence like software development is a process, which expressed in terms of components such as artifacts and workflows. Capability Maturity Model Integrated (CMMI) is developed to define different levels of software process maturity. The concepts underlying CMMI have been defined different maturity levels for a business intelligence process. The current methods for measurement of Business Intelligence maturity are reviewed introducing the application of CMMI as a new measurement tool for this purpose. The main contribution of this research is to apply CMMI model in BI field, specifically in banking industry in Iran. Also this paper makes a contribution on the empirical knowledge on the topic. It determines in which level of maturity Iranian banks stand in case of implementing Business Intelligence process.

Capability Maturity Model Integration (CMMI) is used for Software Process Improvement (SPI) worldwide. Research reveals that CMMI adoption needs a lot of resources in terms of training, funds, and professional workers. Software Small & Medium Enterprises (SSMEs) cannot, however, reserve resources for the purpose. One of the challenges of CMMI adoption is that CMMI identifies “What-to-Do” as a requirement to fulfill and leaves “How-To-Do” to implementers. Implementation of Configuration Management Process Area (CM-PA), being one of the umbrella activities, presents more obstacles generally to the software industry and particularly to SSMEs as compared to other PAs. Establish software baselines is the first Specific Goal (SG-1) needed by CMMI for the effective implementation of CM-PA. Workflow Models (WFMs), an identified set of activities performed in a logical sequence to accomplish a specific practice with probable actors and potential work products, were designed for implementation of its three contributing Specific Practices (SPs). The proposed WFMs were evaluated through the Expert Panel Review (EPR) process. Additionally, a case study was conducted to validate the proposed models. The results of the EPR/Case Study showed that the proposed WFMs are useful, easy to use, supportive in the achievement of SG-1, and applicable to SSMEs. It is important to mention that this research work adds to the empirical software engineering body of knowledge as well as contribute to the implementation of CM-PA.

Software Risk Management (RM) within Medical Device (MD) companies is a critical area. Failure of the software can have potentially catastrophic effects, leading to injury of patients or even death. Therefore regulators penalise MD manufacturers that do not devote sufficient attention to the areas of hazard analysis and RM throughout the software lifecycle. This paper describes the experience of a MD software development organization when they engaged in a research project to improve their RM practices. We explain how this was achieved through the development of a software process improvement RM model that integrates regulatory MD RM requirements with the goals and practices of the Capability Maturity Model Integration (CMMI). This model is known as the Risk Management Capability Model (RMCM). The authors describe the complete project lifecycle and evaluate the success of the project.

Software process is the most important part of software project management, and software process models are important means of implementing the software process in any software organization. When there is need to improve the software process, then the need to improve the work-task part (software process models) of the software process must arise. As, there is need of increasing the commitment of software project managers through out the software development life cycle (SDLC), so we need to give them the list of activities in Waterfall Model, which should be made efficient by the software development team, to get the 80% productivity (output) easily, by reducing the effort of software development and ultimately increasing the performance of the software process. So, the idea of 80/20 rule (Pareto Principle, 1935) can be applied in the software engineering process model, in this regard. The Pareto Principle (1935) directed us to focus on what is really important in any field and field's work. Software process is most important part of software project management (SPM). This is also then ultimately needed for software project management (SPM) improvement. Our main research work is to improve the work-task part of the software process (i.e. software process models by applying the Pareto Principle - 80/20 Rule (1935) (or law of vital few) (1935), in the software engineering process models (or work-task part of the software process). This will be to facilitate the software project manager, using the software process models practically more efficient than without application of 80/20 Rule in software engineering Waterfall model. This has resulted in the reduction of the software development effort and increase in the performance of the software process. The results (efficient and improved software process models) will be implemented in the software industry, by software project managers, by focusing on the list of activities giving 80 percent of the overall productivity of the software process. The results will be the list of activities having the capability to give 20 percent of the overall productivity of the software Waterfall process, to be ignored, eliminated or designated to reduce the effort.

The Capability Maturity Model Integration (CMMI) is a structured representation of software development processes that can support an organi-sation’s software process improvement (SPI) strategies. However, CMMI and SPI initiatives generally exhibit low levels of adoption and limited success. One of the major reasons for these shortcomings is that many organisations undertake SPI initiatives without knowing whether or not they are ready to undertake them. Our previous research has enabled us to develop a software process improvement readiness model/framework to address this problem.This paper reports on the implementation of the SPI readiness model in three large-scale case studies. We have found that organisations with higher CMMI levels are more ready for SPI initiatives than organisations with low CMMI levels. We suggest that organisations at higher CMMI levels have developed capabilities that enable them to further leverage SPI than organisations at lower CMMI levels.KeywordsSoftware Process ImprovementCase StudyOrganisational Readiness

Enterprises today face many challenges related to lack of interoperability. Enterprise applications and software systems need to be interoperable in order to achieve seamless business across organisational boundaries and thus achieve virtual networked organisations. IEEE defines interoperability as “the ability of two or more systems or components to exchange information and to use the information that has been exchanged”. MDA is the OMG instantiation of an approach to software development kown as Model Driven Engineering (MDE) or Model Driven Development (MDD). MDD focuses on Models as the primary artefacts in the development process, with Transformations as the primary operation on models, used to map information from one model to another. There is presently an important paradigm shift in the field of software engineering that may have important consequences on the way information systems are built and maintained. Model-driven development (MDD), and in particular OMG's Model-Driven Architecture ® (MDA®), is emerging as the state of practice for developing modern enterprise applications and software systems. The MDD paradigm improves the way of addressing and solving interoperability issues compared to earlier non-modelling approaches. However, developing correct and useful models is not an easy task. We believe that there is a need for an interoperability framework that provides guidance on how MDD should be applied to address interoperability. A key to the success of MDD is the development of ontologies supporting the mapping from one model to another, either at the same level of abstraction or at different levels. Various approaches have been proposed and tested, starting from common ontologies, shared by all the models, to local ontologies, specific to each software. We propose here to discuss the applicability of MDD to the urban civil engineering (UCE) field. This should help to establish the requirements for ontologies to be applied for interoperability of systems commonly used in this domain. In the first section of this paper, we briefly introduce some key principles of the MDA approach and the role of ontologies in model transformation approaches. The following section describes the Model Driven Development (MDD) interoperability framework. The last part presents a way of applying the MDA techniques to urban civil engineering projects, with the objective of testing the feasibility and relevancy of the approach to this domain.