The needs and business goals of France Telecom R&D are centered around achieving enhanced customer satisfaction and greater competitiveness. These key management concerns become drivers that initiate software process improvement with goals of higher software quality, lower development and maintenance costs, shorter time to market, and increased predictability and control of software products and processes.Software process improvement is considered as a continuous process; France Telecom R&D moves continually around a stabilization cycle, Standardize Do Check Act (SDCA) and an improvement cycle, Plan Do Check Act(PDCA). Within these cycles, in a series of steps of specific improvement, actions such as introducing new or improved practices into software processes are accomplished. The software process model is based on the ISO/IEC 12207 standard 'Software Life-Cycle Processes', and the assessment method uses the ISO/IEC 15504 standard 'Software process Assessment'. Some new processes are defined and used in the area of software engineering.
The cost of a telecom service development is correlated to the discontinuity and the complexity of the process. To solve this problem, we propose a method dedicated to telecom service development, called EA4UP method. The first EA4UP characteristic is the use of the Enterprise Architecture (EA) for the design activity. The EA promotes component reusing, and improves development process continuity thanks to a Model Driven Engineering approach. In this new method, EA enforces the transformation of an analysis model into a design model. The second EA4UP characteristic is to place functions in the core of the method (instead of data). The assessments of eleven projects allow to measure profits of this EA4UP method with regard to the previous ones.
Abstract. Requirements specification is initially scattered in numerous partial models (viewpoints), describing heterogeneous concerns (typically functional and non-functional ones). To define these concerns, requirements analysts prefer describing them separately with metamodels so that they can be properly identified, reused and tooled. The production of one unified view of requirements from separate viewpoints is a complex issue which requires a composition process working at two levels of modeling. At the meta-level, separate "of-the-shelf" metamodels allow defining either concerns or variation in the operational semantics. These metamodels have to be composed into a core metamodel, which captures the information and semantics needed for expressing and analyzing the requirements of a dedicated application domain (e.g. real-time critical systems, telecom services). At the instance-level, viewpoints are composed to produce a global requirements model, which has to be conformant with the core metamodel. Although the same composition mechanism is used for both levels, we emphasize in this paper the strong coupling between the two steps and the difficulty to make both compositions consistent with each other. We thus propose a process for dealing with two-level of composition. The process is illustrated in the context of a platform specialized for requirements analysis purposes.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.