1 Ontology-based Tailoring of Software Process Models Ricardo Eito-Brun To cite this version: Ricardo Eito-Brun. Ontology-based Tailoring of Software Process Models. Terminology and Knowledge Engineering 2014, Jun 2014, Berlin, Germany. 10 p, <hal > HAL Id: hal https://hal.archives-ouvertes.fr/hal Submitted on 13 Jun 2014 HAL is a multi-disciplinary open access archive for the deposit and dissemination of scientific research documents, whether they are published or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers. L archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.
2 1 Ontology-based Tailoring of Software Process Models Ricardo Eíto-Brun Universidad Carlos III de Madrid. Abstract. This paper describes the development of an ontology to support the tailoring of complex process models in the software industry. The ontology is made up of three layers that represent: a) the process characteristics extracted through the analysis of an international standard, b) the tailoring of this standard made at the corporate level, and c) a final tailoring done in response to clientspecific, project-based requirements. The tailoring extends and refines the elements defined on the upper levels to support the customization of tasks and work products for different projects. The resulting ontology supports the tailoring of the process definitions and can also be used as an indexing tool for the easy identification of the requirements and constraints that have an impact on the elaboration of work products and on the planning, execution and monitoring of project activities. Keywords. Ontologies; Software Process; Software Engineering; Requirements management; SemanticWiki. 1 Introduction Software development standards provides organizations with prescriptive process models comprising the list of sub-processes, tasks and activities, their inputs and outputs, and the description of the roles involved in their execution. Compliance with these standards is usually considered a best-practice to ensure the successful completion of IT projects. The components defined in these prescriptive process models may be combined according to different life cycles widely known in the industry: waterfall, incremental, evolutionary, agile, etc. The combination of process models defining tasks, work products and roles -, with life cycles (waterfall, incremental, etc.) result in methodologies that will be enacted at individual projects and reflected in a project plan. This plan includes the result of tailoring the selected methodology to meet project specific needs. This process adaptation activity is possible because organizations developing software have at their disposal methodologies providing descriptions of the planned subprocesses, activities and tasks, their sequence and the work products to be generated. De-facto standard methodologies like RUP (Rational Unified Process), OpenUP (Open Unified Process) or international standards ISO/IEC or ISO/IEC are examples of these methodologies. Usually, companies adopt a particular methodology to develop their projects. Sharing a common methodology to plan, execute and control projects is a source of savings, as the execution of tasks is predictable, can be measured for further improvement, staff is trained on a common set of tasks and can be easily reallocated between different projects.
3 But complex projects usually require a wider, more flexible approach to accommodate additional tasks, activities and work products to those defined in the standard or corporate methodologies. Customers impose additional, project specific requirements that may affect both managerial and engineering activities and work products. These customer requirements introduce an additional complexity or understanding of corporate practices, and need to be incorporated or combined with the methodology applied by the company. For example, methodologies usually ask for the regular reporting of the project status to the project s stakeholders; this generic requirement should be reviewed and adapted, in different projects, to the specific customer requirements and preferences specifying different frequencies, layouts, formats or data to be reported. This paper presents a model that uses ontologies to organize the collaboration framework of software development teams. The proposed solution is not only valid to help engineers organize documents and records, but to serve as a compass that facilitates the understanding and comprehension of different requirements stated in separate standards: international standards used as normative frameworks, project corporate guidelines and customer requirements. The paper proposes a general approach that may be easily tailored to support different normative frameworks. 2 An layered-framework for process tailoring The proposed solution can be defined as a framework made up of three layers: 1. The core layer, based on internationally recognized process standards. 2. The corporate layer, based on the tailoring that individual companies make of the international standards to define their corporate policies and work procedures. 3. The project layer, based on the result of tailoring the corporate layer to accommodate specific requirements imposed by the customer or the project s stakeholders. The framework and its representation as an ontology is based on the process approach. Process approach has become one of the most value paradigms for the organization of work. Companies and organizations are asked to be process-oriented, and attributes related to processes performance, management and measurement are recognized as the right indicators to assess the maturity of the organizations. In addition, processes have become the way visualize how to do the work and how each person activities relate to those of other partners and colleagues. Following this approach, the starting point of the proposed framework and its representation as an Ontology is a process model comprising a set of tasks and activities, work products and roles shared at the organizational level. The process model and the layered architecture provide the context to understand the impact of the different requirements imposed by standards, corporate guidelines and policies, and customers. 2.1 The Core Layer To illustrate the proposed approach and define a widely reusable ontology, the study has taken as a reference the process model described in the international standard
4 ISO/IEC . This standard constitutes the core of the proposed framework, although it is remarked that any other recognized process standard or methodology could have been used as a reference. ISO/IEC Software engineering -- Lifecycle profiles for Very Small Entities (VSEs) is a recently published standard elaborated by ISO/IEC JTC 1 Information Technology SC7 Software and Systems engineering with the purpose of defining standard profiles specifying the software development life cycle processes for Very Small Entities (VSE). VSE are defined as organizations, departments or Project teams with no more than twenty five workers, although the standard could be used in bigger contexts. The contribution of these companies is quite relevant in to the global economy, and VSE are involved and participate in major initiatives developing and maintaining software components that are later integrated into bigger systems by upperlevel contractors. ISO/IEC tries to give answer to one of the traditional problems in process improvement at small companies: existing models like CMMI or SPiCE may result into complex, hard to complete projects, and impose an unaffordable overhead for this kind of companies, who cannot afford adopting and deploying these process improvement models from scratch as they require a significant investment in time, financial and human resources. ISO/IEC provides a simplified set of processes, focused on key activities and deliverables that may be adopted before moving to more complex process improvement models. From this standard, it is possible to identify the main elements, classes and properties of the target ontology. 2.2 The Corporate Layer Organizations involved in software development usually define and establish a set of work process based on existing standards. This is usually done in response to the complexity of methodologies like OpenUP, RUP or standards like ISO/IEC 12207, whose scope may be too wide and complex for the adopting organizations. A common practice is to tailor or adapt the process model defined in any of these standards. Tailoring removes those aspects that are not applicable to the organization, and emphasizes those that add value to their business. The organization s adopted methodology gives common guidelines to develop projects and to ensure a common understanding of processes among the different teams and staff. It constitutes the basis for a common management across projects. 2.3 The Project Layer The adaptation of the core processes done at the corporate level must be further developed at the project level. In some cases, projects may be executed directly enacting the process model defined at the corporate level, with no additional customization. In other cases, where the customer provides additional management or engineering requirements, the corporate process model needs to be refined: it is necessary to accommodate and reflect the impact of those requirements in processes and work
5 products. The project layer is the result of tailoring the process and work product model defined at the corporate layer. The result is a process definition that can be directly enacted or instantiated. The implementation of this layer can serve as an evidence of organizational maturity: in the software development industry, assessment models like CMMI or SPiCE define maturity level 3 as the capability of tailoring existing corporate procedures to respond to projects specific needs. 3 Designing the ontology The selection of ontologies, and the OWL language in particular, to represent the knowledge about process models embedded in standards and customer specifications was based on these assumptions: Ontologies provide a robust framework to represent concepts, their relations, and incorporate equivalent concepts and terms. Ontologies give the opportunity of managing multiple literals and translations for the same concept, and concepts with an equivalent meaning can be represented using the equivalence relationship built-in the OWL language. This aspect is relevant for software process modeling, as there are significant differences in the terminology used by different standards and methodologies to refer to the same concepts. The problem under analysis not only requires the creation of a data model or data structure, but the encoding of specific, particular data in a reusable way. Ontologies are a standard method to represent knowledge. Process models represented in this language can be easily reused by other applications and serve multiple purposes. The modular characteristics of ontologies make possible the management of process models and requirement set in separate modules. These modules can be maintained in separate files and combined as needed to create links and dependencies. The use of XML makes possible the exchange of the data with different process modeling tools supporting XML-based vocabularies like SPEM (Software Process Engineering Modeling) or BPMN (Business Process Modeling Notation). Integration of the ontology with the Semantic Wiki tool is easier. The design of the ontology starts with a set of competence questions [2, 3]. These are related to the information needs of the ontology s end users. In this particular case, typical questions are related to the constraints that the set of applicable requirements impose when planning or executing tasks or elaborating a work product or deliverable, for example: Which is the content that is expected for a particular document? Is there any requirement asking for reporting activities? Which is the format that needs to be used to deliver the software and related documentation?
6 Which is the version of the notation that needs to be applied in the design documents? One of the concerns leading to the design of the framework is that complexity is related to the fact that applicable requirements are spread across multiple specifications, and it is necessary to give engineers a common point of access to them: a place where they can easily locate all the requirements impacting a particular activity or work product, to ensure that activities are compliant with both corporate and client specific requirements. In other words, to answer competence questions the ontology needs to incorporate all the elements needed to contextualize the requirements in the work processes. These are in turn the result of the three-layer refinement described in the previous section. The first components of the ontology correspond to those in the core layer, extracted from the ISO/IEC international standard. This is a document set, and the ontology elaboration has focused on one of its guides: ISO/IEC , Software Engineering Lifecycle Profiles for Very Small Entities (VSEs) Part 5-1-2: Management and Engineering Guide - Basic VSE Profile. It corresponds to the Basic Profile. This profile defines processes for small companies and projects not developing critical software. The Basic Profile includes two processes: Software Implementation and Project Management. For each process, the related activities, tasks and work products are defined. This information constitutes the basis of the core layer. When modelling the ontology, processes, activities, tasks and work products in ISO/IEC have been modelled as subclasses of the generic Processes, Activities, Tasks and WorkProducts classes. This decision is based on the fact that the framework considers the possibility of having multiple instances of these items tailored to the different projects. It is also needed to keep the consistency with the metamodel defined by SPEM (Software Process Engineering Metamodel), a metamodel used to define process models used by the software industry. For example, the SI.6.6 task Perform delivery according to Delivery Instructions within the SI process is modelled as a subclass of the generic Tasks class: the different projects that enact the process following this process model shall instantiate the SI6.6 task within their projects. In addition, when it is necessary to customize or adapt the task definition and characteristics, process architects can create subclasses tailored according to the corporate or customer requirements. ISO/IEC provides with the core elements on the ontology, including a process meta-model with the different types of elements the standard deals with: processes, activities, tasks, work products, process objectives, process outcomes and roles. Similar meta-models for software processes have been proposed in the professional and academic literature in software engineering [4, 5, 6]. As previously stated, from this meta-model additional classes can be directly derived from the content of the ISO/IEC standard. Each process, activity, task, process objective and work product constitute a separate class. ISO/IEC makes possible to derive additional elements for the target ontology, mainly, the object properties that represent relationships between classes, including the relationships that delineate the se-
7 quencing and dependencies between tasks and activities. Dependencies between activities are in fact based on the usage that activities make of the work products generated by other activities. In this layer of the ontology, an initial set of relationships are identified, among others: includesactivity isincludedinprocess, between Processes and Activities. includestask isincludedinactivity, between Activities and Tasks. usesinput isusedasinput, between Tasks and Work Products. generatesoutput isgeneratedasinput, between Tasks and Work Products. participatesin isdoneby, between Tasks and Roles. produces isproducedby, between Roles and Work Products. dependsontask mustpreceed, between activities, and between tasks, to establish sequencing and order. To ensure that elements in the ontology are properly documented, for each element the following properties are systematically filled with the definitions in the ISO/IEC standard. The second phase in the design of the ontology corresponds to the addition of specializations to reflect the particular tailoring of the standard made by the company. In the case of the ISO/IEC 29110, the description provided for activities, work products and tasks may result quite general, and tailoring may consist of adding additional details, usually in the form of data properties that will be added to subclasses of the classes derived from ISO/IEC This tailoring can be completed using interviews or questionnaires that identify particular aspects of the process implementation made by the company. The third phase in the design of the ontology corresponds to the incorporation of the characteristics derived from the project specific requirements imposed by the customer. To complete this exercise, the following heuristics are proposed: If the requirement requires the incorporation or the adaptation of a new tasks, role or work product, a new subclass shall be added to the ontology as a subclass of the class being extended or tailored. The tailoring of the existing class may consist of incorporating new data individuals - or object properties to represent a characteristic of the element that was not present in the superclass. The limits of Semantic Web ontology languages to represent default values of data properties are one of the major constraints for the tailoring process. When doing the tailoring of an existing class it is necessary to maintain the traceability between the change incorporated and the specific requirement that justifies and provides the reasons for the change. This traceability ensures that all the requirements in the applicable specifications are taken into account and covered by the process model that the project will enact. But keeping this traceability using the Semantic Web languages is complex, due to the constraints to represent properties of properties. RDF and OWL focuses on binary relations between individuals or between an individual and a value. The proposed solution for dealing with the traceability is based on
8 the use of ontology patterns for representing n-ary relations in OWL described in the W3C note Defining N-ary Relations on the Semantic Web. The pattern represents the relation between more than two items as a class, being individual instances of the related classes instances of the relation. Additional properties provide binary links to each argument of the relation. This corresponds to the use case 1 described in the W3C document: additional attributes describing a relation. This case is used to represent additional attributes describing a relation (the example in the W3C note is a patient having a health problem with a specific probability). In the proposed pattern, an individual is created to represent the relation itself, containing links from the subject of the relation to this instance, and links from this instance to all participants that represent the additional information. Going back to the case under discussion, the individual corresponding to the Tasks Reporting to the Customer has a has_periodicity property whose value is another individual (_:Periodicity_Relation_1) that encapsulates the requirement and the standard from which it is taken. A different approach to model this case is based on incorporating to the ontology the set of applicable specifications and their requirements. This implies having separate classes for specifications and requirements. Particular requirements and documents will be represented as individuals of these classes. This would make possible the creation of relationships between classes representing tasks and work products and requirements, but it would not make possible adding constraints at the property level to indicate that its value is affected by a particular requirement. Regardless these aspects, the ontology supporting the process model must consider requirements from standards, and must provide the necessary classes and instances to handle these objects. 4 Views of the Process-framework: the Ontology s End User Perspective Different projects demonstrate the value of ontologies as valid tools for knowledge organization in software projects [7, 8]. In the case of the ontology described in this paper, it is aimed for process analysts in charge of modelling and engineers involved in the planning, execution and control of the project. All the staff participating in the project should have a clear knowledge of the processes that shall be enacted during project execution, and should know the impact that customer requirements and applicable standards have on their activities and on the product deliverables they need to produce, verify or validate. The process-framework organized in the three layers described above support two different views: the first one oriented to the process engineers and quality departments in charge of customizing and tailoring corporate processes, and the second oriented to the engineers working on a particular project. Both views are based on the OWL ontology that serves as the conceptual infrastructure of the framework. For process engineers, the ontology provides the model and the data that support a complex, corporate information system, whose complexity become greater as additional standards, projects and customer requirements are added to the framework. The
9 advantage of using an ontology is that the tailoring of the processes may be reused across different projects applying the same standards: process models can be further adapted by adding additional subclasses to the ontology. For engineers and staff involved in project execution, the ontology-based approach makes complex, related requirements affecting tasks and work products explicit, and put them in the context of the daily activities. Usually, company staff has the necessary knowledge to follow the procedures defined in the corporate quality system or guidelines. In the opposite, when dealing with customer-imposed, project specific requirements and standards, there is a risk of missing some aspects requested by these requirements, as staff is not used to apply them systematically in previous projects. The ontology serves this purpose and reduces or even eliminates this risk. Staff involved in projects need to be given an application where they can get answers to these two questions: which are the Customer requirements that have an impact on my activities? Is there any Customer requirement I need to take into account during the creation or validation of a specific work product? This application is delivered as a web publication built on top of Semantic Wiki. In this web, engineers can easily find detailed information about each tasks and work products. As the volume of information increases, the framework helps organize information and reduces the complexity implicit to the fact of dealing with additional requirements to those imposed by the organizational work procedures. For the publication of the resulting process adaptations (each project shall have its own adaptation) Semantic MediaWiki tool has been selected. Experiences with this tool are documented in previous research [9, 10]. The advantage of this tool with respect to other web publishing tools is that it supports searching and browsing to easily identify those requirements having an impact on the activities and work products in the process model. In addition, Wikis have become a popular tool to keep technical documentation and share knowledge between technical staff. Using a tool already known and deployed in a wide range of companies, help ensure the success of the process framework, as users do not need to learn how to use a new tool or keep separate bookmarks. Content edition capabilities provided by Wikis is also a relevant feature, as engineers can suggest additional relationships to those initially identified when modeling the particular adaptations of the corporate process model. 5 Conclusions Different ontologies have been proposed in the academic and professional literature to model software development processes and to create mappings between standards and methodologies. The case described in this paper demonstrates the feasibility of using software process model ontologies to improve the access to information in complex projects that need to be compliant with requirements stated in different sources. Starting from a core process model based on ISO/IEC 29110, subsequent adaptations of the standard at the corporate and at the project level are modelled by adding new elements to the core ontology. The core ontology identifies a set of tasks, activi-
10 ties, work products and roles that may be extended or tailored in response to the requirements imposed by the client. Dealing with requirements coming from different sources implies a risk, as staff involved in project planning and execution may disregard relevant requirements and information. In addition, dealing with separate documents and standards has a negative impact on productivity, due to the difficulties to remember at a given time all the applicable constraints. The proposed solution ensures a single, shared point of access to search and browse applicable requirements whatever their source - and assess their impact on activities and work products. When working on a specific deliverable or tasks, engineers can get the list of requirements that need to be considered. The basis of the proposed solution is an OWL ontology organized in three layers: The first layer, Core Layer, corresponding to the process model taken as a reference and based on a well-defined standard. ISO/IEC has been used in this prototype. This layer provides an initial list of processes, activities, tasks, roles and work products. The second layer, Corporate Layer, corresponds to the process definitions obtained after the tailoring of the processes defined in the Core Layer. This tailoring is based on the corporate standards. The third layer, Project Layer, corresponds to the definition of the processes done for specific projects, considering the constraints imposed by requirements imposed by the customer. Process definitions at this layer shall be enacted at project initialization. The ontology incorporates specifications imposing requirements. They may be international standards or customer-provided. These requirements are linked to other ontology classes representing activities, tasks and work products to provide traceability. These links or object relations enable the creation of a web publication where users can easily browse requirements impacting on tasks and work products. To ensure a wider access to the knowledge encoded in the ontology, this is incorporated into a Semantic Wiki that gives engineers the choice of incorporating additional knowledge about the impact of requirements. The semantic wiki support the work of engineers involved in projects as well as the work of process engineers. The prototype demonstrates the feasibility of using ontologies to represent the knowledge embedded in corporate and project-specific software process models and link them to particular requirements from different sources, building an integrated view of the processes and the constraints that impact project activities and work products, avoiding one of the most relevant challenges that engineers face today: information overload and intellectual control of multiple inputs affecting their activities. 6 Bibliography 1. Boucher, Q. et al.: Towards Configurable ISO/IEC Compliant Software Development Processes for Very Small Entities. In: Winkler, D., O'Connor, R., Messnarz, R. (eds) Systems, Software and Services Process Improvement, pp (2012)
11 2. Corcho, O: Building Legal Ontologies with METHONTOLOGY and WebODE. In: Law and the semantic web : legal ontologies, methodologies, legal information retrieval, and applications. Berlin: Springer, pp (2005) 3. Iqbal, R.: An Analysis of Ontology Engineering Methodologies: A Literature Review. Research journal of applied sciences, engineering and technology. 6 (16) (2013) 4. Alexis, O.: Rationale modeling for software process evolution. Software Process: Improvement and Practice 14(2) (2009) 5. Calero, C., Ruiz, F., Piattini, M.: Using Ontologies in Software Engineering and Technology. In: Ontologies for Software Engineering and Software Technology. Berlin : Springer (2006) 6. Uwe A. et al.: Ontology-Guided Software Engineering in the MOST Workbench. In: Ontology-Driven Software Development. Berlin : Springer. pp (2013) 7. Villela, K. et al.: The use of an enterprise ontology to support knowledge management in software development environments. Journal of the Brazilian Computer Society (11) (2005) 8. Smite, D. et al.: An empirically based terminology and taxonomy for global software engineering. Empirical Software Engineering. 19 (1) (2014) 9. Baumeister, J., Reutelshoefer, J., Puppe, F.: KnowWE: a Semantic Wiki for knowledge engineering. Applied Intelligence. 35(3) (2011) 10. Ribaud, V., Saliou, P.: Using a Semantic Wiki for Documentation Management in Very Small Projects. In: Sánchez-Alonso, S., Athanasiadis, I. (eds.) Metadata and Semantic Research. Berlin: Springer, (2010)
ibalance-abf: a Smartphone-Based Audio-Biofeedback Balance System Céline Franco, Anthony Fleury, Pierre-Yves Guméry, Bruno Diot, Jacques Demongeot, Nicolas Vuillerme To cite this version: Céline Franco,
Mobility management and vertical handover decision making in heterogeneous wireless networks Mariem Zekri To cite this version: Mariem Zekri. Mobility management and vertical handover decision making in
La mort du narrateur et l interprétation du roman. L exemple de Pedro Páramo de Juan Rulfo Sylvie Patron To cite this version: Sylvie Patron. La mort du narrateur et l interprétation du roman. L exemple
Virginia Woolf, Comment devrait-on lire un livre? ou le théoricien du commun François-Ronan Dubois To cite this version: François-Ronan Dubois. Virginia Woolf, Comment devrait-on lire un livre? ou le théoricien
Analyse échographique de la cicatrisation tendineuse après réparation arthroscopique de la coiffe des rotateurs Martin Schramm To cite this version: Martin Schramm. Analyse échographique de la cicatrisation
QASM: a Q&A Social Media System Based on Social Semantics Zide Meng, Fabien Gandon, Catherine Faron-Zucker To cite this version: Zide Meng, Fabien Gandon, Catherine Faron-Zucker. QASM: a Q&A Social Media
A graph based framework for the definition of tools dealing with sparse and irregular distributed data-structures Serge Chaumette, Jean-Michel Lepine, Franck Rubi To cite this version: Serge Chaumette,
Process Assessment Issues of the ISO/IEC 29110 emerging standard Vincent Ribaud, Philippe Saliou To cite this version: Vincent Ribaud, Philippe Saliou. Process Assessment Issues of the ISO/IEC 29110 emerging
A usage coverage based approach for assessing product family design Jiliang Wang To cite this version: Jiliang Wang. A usage coverage based approach for assessing product family design. Other. Ecole Centrale
Faut-il des cyberarchivistes, et quel doit être leur profil professionnel? Jean-Daniel Zeller To cite this version: Jean-Daniel Zeller. Faut-il des cyberarchivistes, et quel doit être leur profil professionnel?.
Knowledge based tool for modeling dynamic systems in education Krassen Stefanov, Galina Dimitrova To cite this version: Krassen Stefanov, Galina Dimitrova. Knowledge based tool for modeling dynamic systems
FP-Hadoop: Efficient Execution of Parallel Jobs Over Skewed Data Miguel Liroz-Gistau, Reza Akbarinia, Patrick Valduriez To cite this version: Miguel Liroz-Gistau, Reza Akbarinia, Patrick Valduriez. FP-Hadoop:
The CHI 2013 Interactive Schedule Arvind Satyanarayan, Daniel Strazzulla, Clemens Klokmose, Michel Beaudouin-Lafon, Wendy E. Mackay To cite this version: Arvind Satyanarayan, Daniel Strazzulla, Clemens
Additional mechanisms for rewriting on-the-fly SPARQL queries proxy Arthur Vaisse-Lesteven, Bruno Grilhères To cite this version: Arthur Vaisse-Lesteven, Bruno Grilhères. Additional mechanisms for rewriting
Study on Cloud Service Mode of Agricultural Information Institutions Xiaorong Yang, Nengfu Xie, Dan Wang, Lihua Jiang To cite this version: Xiaorong Yang, Nengfu Xie, Dan Wang, Lihua Jiang. Study on Cloud
VR4D: An Immersive and Collaborative Experience to Improve the Interior Design Process Amine Chellali, Frederic Jourdan, Cédric Dumas To cite this version: Amine Chellali, Frederic Jourdan, Cédric Dumas.
Auto-Scaling, Load Balancing and Monitoring in Commercial and Open-Source Clouds Eddy Caron, Luis Rodero-Merino, Frédéric Desprez, Adrian Muresan To cite this version: Eddy Caron, Luis Rodero-Merino, Frédéric
Towards Collaborative Learning via Shared Artefacts over the Grid Cornelia Boldyreff, Phyo Kyaw, Janet Lavery, David Nutter, Stephen Rank To cite this version: Cornelia Boldyreff, Phyo Kyaw, Janet Lavery,
Les identités féminines dans le conte traditionnel occidental et ses réécritures : une perception actualisée des élèves Sarah Brasseur To cite this version: Sarah Brasseur. Les identités féminines dans
Managing Risks at Runtime in VoIP Networks and Services Oussema Dabbebi, Remi Badonnel, Olivier Festor To cite this version: Oussema Dabbebi, Remi Badonnel, Olivier Festor. Managing Risks at Runtime in
A few elements in software development engineering education Vincent Ribaud, Philippe Saliou To cite this version: Vincent Ribaud, Philippe Saliou. A few elements in software development engineering education.
Discussion on the paper Hypotheses testing by convex optimization by A. Goldenschluger, A. Juditsky and A. Nemirovski. Fabienne Comte, Celine Duval, Valentine Genon-Catalot To cite this version: Fabienne
Aligning subjective tests using a low cost common set Yohann Pitrey, Ulrich Engelke, Marcus Barkowsky, Romuald Pépion, Patrick Le Callet To cite this version: Yohann Pitrey, Ulrich Engelke, Marcus Barkowsky,
Use of tabletop exercise in industrial training disaster. Alexis Descatha, Thomas Loeb, François Dolveck, Nathalie-Sybille Goddet, Valerie Poirier, Michel Baer To cite this version: Alexis Descatha, Thomas
Minkowski Sum of Polytopes Defined by Their Vertices Vincent Delos, Denis Teissandier To cite this version: Vincent Delos, Denis Teissandier. Minkowski Sum of Polytopes Defined by Their Vertices. Journal
ANIMATED PHASE PORTRAITS OF NONLINEAR AND CHAOTIC DYNAMICAL SYSTEMS Jean-Marc Ginoux To cite this version: Jean-Marc Ginoux. ANIMATED PHASE PORTRAITS OF NONLINEAR AND CHAOTIC DYNAMICAL SYSTEMS. A.H. Siddiqi,
An update on acoustics designs for HVAC (Engineering) Ken MARRIOTT To cite this version: Ken MARRIOTT. An update on acoustics designs for HVAC (Engineering). Société Française d Acoustique. Acoustics 2012,
Global Identity Management of Virtual Machines Based on Remote Secure Elements Hassane Aissaoui, P. Urien, Guy Pujolle To cite this version: Hassane Aissaoui, P. Urien, Guy Pujolle. Global Identity Management
A model driven approach for bridging ILOG Rule Language and RIF Valerio Cosentino, Marcos Didonet del Fabro, Adil El Ghali To cite this version: Valerio Cosentino, Marcos Didonet del Fabro, Adil El Ghali.
Expanding Renewable Energy by Implementing Demand Response Stéphanie Bouckaert, Vincent Mazauric, Nadia Maïzi To cite this version: Stéphanie Bouckaert, Vincent Mazauric, Nadia Maïzi. Expanding Renewable
Online vehicle routing and scheduling with continuous vehicle tracking Jean Respen, Nicolas Zufferey, Jean-Yves Potvin To cite this version: Jean Respen, Nicolas Zufferey, Jean-Yves Potvin. Online vehicle
Overview of model-building strategies in population PK/PD analyses: 2002-2004 literature survey. Céline Dartois, Karl Brendel, Emmanuelle Comets, Céline Laffont, Christian Laveille, Brigitte Tranchand,
202 A Comparison of SOA Methodologies Analysis & Design Phases Sandra SVANIDZAITĖ Institute of Mathematics and Informatics, Vilnius University Abstract. Service oriented computing is a new software engineering
Leveraging ambient applications interactions with their environment to improve services selection relevancy Gérald Rocher, Jean-Yves Tigli, Stéphane Lavirotte, Rahma Daikhi To cite this version: Gérald
From Microsoft Word 2003 to Microsoft Word 2007: Design Heuristics, Design Flaws and Lessons Learnt Yin-Leng Theng, Eng Kiat Ting, Xuehong Tao To cite this version: Yin-Leng Theng, Eng Kiat Ting, Xuehong
Towards Business Ontologies Matching for Inter-Enterprise Collaboration Platform in a Lean Manufacturing Strategy Ahlem Zayati, Lilia Sidhom, Youakim Badr, Frédérique Biennier, Mohamed Moalla To cite this
Information Technology Education in the Sri Lankan School System: Challenges and Perspectives Chandima H. De Silva To cite this version: Chandima H. De Silva. Information Technology Education in the Sri
An Automatic Reversible Transformation from Composite to Visitor in Java Akram To cite this version: Akram. An Automatic Reversible Transformation from Composite to Visitor in Java. CIEL 2012, P. Collet,
Territorial Intelligence and Innovation for the Socio-Ecological Transition Jean-Jacques Girardot, Evelyne Brunau To cite this version: Jean-Jacques Girardot, Evelyne Brunau. Territorial Intelligence and
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science The University Of Birmingham firstname.lastname@example.org www.cs.bham.ac.uk/~rzb Office 112 Y9- Computer Science Unit 1. Introduction
Information behaviour and practices of PhD students Thea Marie Drachen, Asger Væring Larsen, Eystein Gullbekk, Hilde Westbye, Karin Lach To cite this version: Thea Marie Drachen, Asger Væring Larsen, Eystein
Software Engineering So#ware Processes 1 The software process A structured set of activities required to develop a software system. Many different software processes but all involve: Specification defining
Design Specification for IEEE Std 1471 Recommended Practice for Architectural Description IEEE Architecture Working Group 0 Motivation Despite significant efforts to improve engineering practices and technologies,
Template Based MDE Matthieu Allon, Gilles Vanwormhoudt, Bernard Carré, Olivier Caron To cite this version: Matthieu Allon, Gilles Vanwormhoudt, Bernard Carré, Olivier Caron. Template Based MDE. 4ème Conférence
Training Management System for Aircraft Engineering: indexing and retrieval of Corporate Learning Object Anne Monceaux 1, Joanna Guss 1 1 EADS-CCR, Centreda 1, 4 Avenue Didier Daurat 31700 Blagnac France
Identifying Objective True/False from Subjective Yes/No Semantic based on OWA and CWA Duan Yucong, Christophe Cruz, Christophe Nicolle To cite this version: Duan Yucong, Christophe Cruz, Christophe Nicolle.
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Interlibrary loan and document supply in France the Montpellier meeting Joachim Schöpfel To cite this version: Joachim Schöpfel. Interlibrary loan and document supply in France the Montpellier meeting.
The Effectiveness of non-focal exposure to web banner ads Marc Vanhuele, Didier Courbet, Sylvain Denis, Frédéric Lavigne, Amélie Borde To cite this version: Marc Vanhuele, Didier Courbet, Sylvain Denis,
Computing Fine-grained Semantic of Texts Yue Ma, François Lévy To cite this version: Yue Ma, François Lévy. Computing Fine-grained Semantic of Texts. The 10th International Semantic Web Conference (ISWC11-PD),
Central Page 284 of 296 Application of software product quality international standards through software development life cycle Mladen Hosni, Valentina Kirinić Faculty of Organization and Informatics University
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
L exercice du théâtre à l école Mathilde Patteyn To cite this version: Mathilde Patteyn. L exercice du théâtre à l école. Éducation. 2013. HAL Id: dumas-00861849 http://dumas.ccsd.cnrs.fr/dumas-00861849
GDS Resource Record: Generalization of the Delegation Signer Model Gilles Guette, Bernard Cousin, David Fort To cite this version: Gilles Guette, Bernard Cousin, David Fort. GDS Resource Record: Generalization
The truck scheduling problem at cross-docking terminals Lotte Berghman,, Roel Leus, Pierre Lopez To cite this version: Lotte Berghman,, Roel Leus, Pierre Lopez. The truck scheduling problem at cross-docking
See discussions, stats, and author profiles for this publication at: http://www.researchgate.net/publication/47901002 Building Ontology Networks: How to Obtain a Particular Ontology Network Life Cycle?
Cobi: Communitysourcing Large-Scale Conference Scheduling Haoqi Zhang, Paul André, Lydia Chilton, Juho Kim, Steven Dow, Robert Miller, Wendy E. Mackay, Michel Beaudouin-Lafon To cite this version: Haoqi
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
What Development for Bioenergy in Asia: A Long-term Analysis of the Effects of Policy Instruments using TIAM-FR model Seungwoo Kang, Sandrine Selosse, Nadia Maïzi To cite this version: Seungwoo Kang, Sandrine
Business Business Services Services and Enterprise and Enterprise This Workshop Two parts Background: Business Value of Enterprise TOGAF s and the Business Services We will use the key steps, methods and
Application of ontologies for the integration of network monitoring platforms Jorge E. López de Vergara, Javier Aracil, Jesús Martínez, Alfredo Salvador, José Alberto Hernández Networking Research Group,
Rochester Institute of Technology RIT Scholar Works Presentations and other scholarship 2009 A Software process engineering course J. Scott Hawker Follow this and additional works at: http://scholarworks.rit.edu/other
An Ontological Approach to Oracle BPM Jean Prater, Ralf Mueller, Bill Beauregard Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065, USA email@example.com, firstname.lastname@example.org, email@example.com
Partial and Dynamic reconfiguration of FPGAs: a top down design methodology for an automatic implementation Florent Berthelot, Fabienne Nouvel, Dominique Houzet To cite this version: Florent Berthelot,
Purpose The purpose of this document is to provide guidance on the practice of Modeling and to describe the practice overview, requirements, best practices, activities, and key terms related to these requirements.
J.M. de Baat 09-10-2008 Table of contents 1 Introduction...3 1.1 Abbreviations...3 2 Some background information... 3 2.1 The organisation and ICT infrastructure... 3 2.2 Five layer SOA architecture...
Good Practices as a Quality-Oriented Modeling Assistant Vincent Le Gloahec, Régis Fleurquin, Salah Sadou To cite this version: Vincent Le Gloahec, Régis Fleurquin, Salah Sadou. Good Practices as a Quality-Oriented
2012 Joint Working Conference on Software Architecture & 6th European Conference on Software Architecture A Variability Viewpoint for Enterprise Software Systems Matthias Galster University of Groningen,
ControVol: A Framework for Controlled Schema Evolution in NoSQL Application Development Stefanie Scherzinger, Thomas Cerqueus, Eduardo Cunha de Almeida To cite this version: Stefanie Scherzinger, Thomas
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
Early Stage Adoption of ISO/IEC 29110 Software Project Management Practices: A Case Study Rory V. O Connor 1, 2 1 Lero, the Irish Software Engineering Research Centre, Ireland 2 Dublin City University,
Running an HCI Experiment in Multiple Parallel Universes,, To cite this version:,,. Running an HCI Experiment in Multiple Parallel Universes. CHI 14 Extended Abstracts on Human Factors in Computing Systems.
TECHNICAL REPORT ISO/IEC TR 29110-5-6-2 First edition 2014-08-15 Systems and software engineering Lifecycle profiles for Very Small Entities (VSEs) Part 5-6-2: Systems engineering Management and engineering
APPLYING CASE BASED REASONING IN AGILE SOFTWARE DEVELOPMENT AIMAN TURANI Associate Prof., Faculty of computer science and Engineering, TAIBAH University, Medina, KSA E-mail: firstname.lastname@example.org ABSTRACT
New implementions of predictive alternate analog/rf test with augmented model redundancy Haithem Ayari, Florence Azais, Serge Bernard, Mariane Comte, Vincent Kerzerho, Michel Renovell To cite this version:
Günter Böckle Klaus Pohl Frank van der Linden 2 A Framework for Software Product Line Engineering In this chapter you will learn: o The principles of software product line subsumed by our software product
ONTODESIGN; A DOMAIN ONTOLOGY FOR BUILDING AND EXPLOITING PROJECT MEMORIES IN PRODUCT DESIGN PROJECTS DAVY MONTICOLO Zurfluh-Feller Company 25150 Belfort France VINCENT HILAIRE SeT Laboratory, University
in Component-Based Software Architecture Abdelkrim Amirat, Mourad Oussalah To cite this version: Abdelkrim Amirat, Mourad Oussalah. Reusable Connectors in Component-Based Software Architecture. Ninth international
Software Life Cycle Lecture Objectives What happens in the life of software To look at the life cycle of a software To understand the software process and its related elements To relate to the different
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
SMEF 10-11 June, 2010 Software Quality Standards and Approaches from Ontological Point of View Konstantina Georgieva Otto-von-Guericke University Magdeburg Department of Computer Science, Software Engineering
SELECTIVELY ABSORBING COATINGS J. Vuletin, P. Kuli ik, M. Bosanac To cite this version: J. Vuletin, P. Kuli ik, M. Bosanac. SELECTIVELY ABSORBING COATINGS. Journal de Physique Colloques, 1981, 42 (C1),
Your consent to our cookies if you continue to use this website.