There are many approaches to reuse in software engineering. Among them, patterns hold a prominent position. "Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" (Alexander, 1979). We are interested in the use of patterns for the requirements analysis stage, namely Software Requirement Patterns. The patterns applicability to this context is clear, since requirements that appear over and over in requirements books could be identified as the solution to particular problems in a given context (the classical context-problem-solution scenario of patterns).
Presentation of Software Requirement Patterns in the PABRE framework.
Objectives:
1. To understand the different processes in the realm of ‘Requirements Engineering’.
2. To see the challenges in requirements development and the importance of getting requirements right in an IT project.
3. To understand the different techniques used in different phases and processes of requirements development and management.
System of Systems modeling comes with a tough decision for practitioners using traditional SysML V1 tools. Do I go with SysML V1, or do I look at Unified Architecture Framework? Capella eliminates that challenge with one notation that can be used for both.
By Tony Komar (Siemens)
Tony Komar has been practicing and supporting systems engineering for over 35 years.
Today he is a key contributor to the development and deployment of model-based system engineering products for Siemens Digital Industries Software.
CEBoK for Software Past Present Future - Megan JonesNesma
The Cost Estimation Body of Knowledge for Software is in development for a number of years within ICEAA. First as a section of the general CEBoK, but it will be established as a separate CEBoK-S for Software, since software is becoming very prominent within the cost estimation community.
In this Business Analysis training session, you will learn about Requirement Elicitation Techniques. Topics covered in this session are:
• Requirements Engineering
• Project Scope
• Landscape of Requirements
• Properties of Requirements
• Types of Requirements
• Stakeholder
• Requirements Elicitation
• Techniques
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/become-a-business-analyst-with-hands-on-practice/
Solution Architecture And Solution SecurityAlan McSweeney
This describes an approach to embedding security within the technology solution landscape. It describes a security model that encompasses the range of individual solution components up to the entire solution landscape. The solution security model allows the security status of a solution and its constituent delivery and operational components to be tracked wherever those components are located. This provides an integrated approach to solution security across all solution components and across the entire organisation topology of solutions. It allows the solution architect to validate the security of an individual solution. It enables the security status of the entire solution landscape to be assessed and recorded. Solution security is a wicked problem because there is no certainly about when the problem has been resolved and a state of security has been achieved. The security state of a solution can just be expressed along a subjective spectrum of better or worse rather than a binary true or false. Solution security can have negative consequences: prevents types of access, limits availability in different ways, restricts functionality provided, makes solution harder to use, lengthens solution delivery times, increases costs along the entire solution lifecycle, leads to loss of usability, utility and rate of use.
Información sobre Ingeniería Requisitos a partir de:
Análisis y Diseño de Sistemas de Kendall y Kendall, 8va Edición
Software Engineering de Ian Sommerville, novena edición
Ingeniería del Software, un enfoque práctico, de Roger S. Pressman, séptima edición
Sistemas de Información Gerencial, de Kenneth C. Laudon y Jane P. Laudon, decimo segunda edición
Notas del Curso Análisis de Requerimientos de María del Carmen Gómez Fuentes, 2011
IEEE SWEBOK versión 3.0, de Pierre Bourque y Richard E. (Dick) Fairley
Objectives:
1. To understand the different processes in the realm of ‘Requirements Engineering’.
2. To see the challenges in requirements development and the importance of getting requirements right in an IT project.
3. To understand the different techniques used in different phases and processes of requirements development and management.
System of Systems modeling comes with a tough decision for practitioners using traditional SysML V1 tools. Do I go with SysML V1, or do I look at Unified Architecture Framework? Capella eliminates that challenge with one notation that can be used for both.
By Tony Komar (Siemens)
Tony Komar has been practicing and supporting systems engineering for over 35 years.
Today he is a key contributor to the development and deployment of model-based system engineering products for Siemens Digital Industries Software.
CEBoK for Software Past Present Future - Megan JonesNesma
The Cost Estimation Body of Knowledge for Software is in development for a number of years within ICEAA. First as a section of the general CEBoK, but it will be established as a separate CEBoK-S for Software, since software is becoming very prominent within the cost estimation community.
In this Business Analysis training session, you will learn about Requirement Elicitation Techniques. Topics covered in this session are:
• Requirements Engineering
• Project Scope
• Landscape of Requirements
• Properties of Requirements
• Types of Requirements
• Stakeholder
• Requirements Elicitation
• Techniques
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/become-a-business-analyst-with-hands-on-practice/
Solution Architecture And Solution SecurityAlan McSweeney
This describes an approach to embedding security within the technology solution landscape. It describes a security model that encompasses the range of individual solution components up to the entire solution landscape. The solution security model allows the security status of a solution and its constituent delivery and operational components to be tracked wherever those components are located. This provides an integrated approach to solution security across all solution components and across the entire organisation topology of solutions. It allows the solution architect to validate the security of an individual solution. It enables the security status of the entire solution landscape to be assessed and recorded. Solution security is a wicked problem because there is no certainly about when the problem has been resolved and a state of security has been achieved. The security state of a solution can just be expressed along a subjective spectrum of better or worse rather than a binary true or false. Solution security can have negative consequences: prevents types of access, limits availability in different ways, restricts functionality provided, makes solution harder to use, lengthens solution delivery times, increases costs along the entire solution lifecycle, leads to loss of usability, utility and rate of use.
Información sobre Ingeniería Requisitos a partir de:
Análisis y Diseño de Sistemas de Kendall y Kendall, 8va Edición
Software Engineering de Ian Sommerville, novena edición
Ingeniería del Software, un enfoque práctico, de Roger S. Pressman, séptima edición
Sistemas de Información Gerencial, de Kenneth C. Laudon y Jane P. Laudon, decimo segunda edición
Notas del Curso Análisis de Requerimientos de María del Carmen Gómez Fuentes, 2011
IEEE SWEBOK versión 3.0, de Pierre Bourque y Richard E. (Dick) Fairley
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the first unit in the syllabus are covered. I hope it will be helpful to the students.
Test Driven Development (TDD) is a core practice in the SDLC, especially ones that run using the agile mindset and leverage the practices of eXtreme programming. Since its inception and rediscovery by Kent beck in the late 1990s, it has gained popularity among many software development teams. However, like any popular software development practices, teams lose interest in TDD overtime and drop the practice all together. The main reason behind this is practicing it "the wrong way".
In this session, I present 7 anti-patterns that can ruin the TDD experience of a software development team. I also present how to counter these anti-patterns to fully leverage the benefits of TDD.
During the last years we have seen the evolution of Xamarin Forms that has brought new improvements, as well as great contributions from the community. This implies that perhaps in the way that some things were done some time ago, there are currently better and simpler ways of doing it. In this talk we will discuss best practices when programming in Xamarin Forms, as well as architecture, dependency injection, performance, use of plugins and components, among others.
MDD - Desarrollo de software dirigido por modelos que funciona (de verdad!)Jordi Cabot
Consejos para tener éxito en la adopción de una estrategia MDD en vuestro proceso de desarrollo.
Más sobre estos temas (UML, DSLs, MDA, generación de código,..) en http://modeling-languages.com
Applying Systems Thinking to Solve Wicked Problems in Software EngineeringMajed Ayyad
Software systems are essentially socio-technical systems
and they are not isolated from other systems engineering processes. Unconsciously or by intention, we implement systems thinking in multi-agent systems, microservices, DevOps, distributed systems, API-led integrations and lean based software development life cycles. However, the concrete relationship between systems thinking and software engineering is still a green area and barely highlighted as a common practice among software engineers. In this presentation, we will
elaborate how systems thinking helps us to understand the socio-technical aspects of software engineering. We will discuss why systems thinking is important in the field of software engineering, provide examples where it is currently used and show the general areas where systems thinking applies to tackle complex software problems
LML to SysML and Back - Systems Engineering LanguagesElizabeth Steiner
Steven Dam, Ph.D., ESEP shares his knowledge of the Lifecycle Modeling Language and the Systems Modeling Language. He discusses SysML's and LML's vast capabilities and how they work together in Innoslate®. The live presentation also demonstrates both LML and SysML diagrams as they have been developed for Innoslate®.
Metodología de desarrollo de software basada en componentesEmmanuel Fontán
Metodología de desarrollo de software basada en componentes, trabajo para la Cátedra de Metodología de Sistemas 1 de la Universidad Nacional de Entre Ríos, en el año 2010
Kong Summit 2018 - Microservices: decomposing applications for testability an...Chris Richardson
In this presentation, I describe the essential characteristics of the microservice architecture. You will learn about the benefits and drawbacks of the microservice architecture and when it makes sense to use it. I discuss how the microservice architecture is not a silver bullet. You will learn about the microservice pattern language, which is a collection of patterns that solve architecture and design issues that you will encounter when using microservices.
Lenguajes de trazabilidad expresiones regularesGiovani Ramirez
Permiten filtrar textos para encontrar coincidencias, comprobar la validez de fechas, documentos de identidad o contraseñas, se pueden utilizar para reemplazar texto con unas características concretas por otro, y muchos más usos como mostrar si hay errores en todo el proceso
A brief history of Blinkist backend time. I gave this talk at the Adidas Developer conference in Erlangen. The Adidas developer community is awesome! Go check out their Github repositories for all the project they've contributed https://github.com/adidas
Strategies and Tools for Model Reuse with CapellaObeo
How to manage libraries and building blocks?
Reusing models or parts of models with Capella
is not only conceptually appealing, it is a real productivity enabler.
But it is also a true challenge!
Technical solutions initially dedicated to simple duplication
and synchronisation of model parts have recently evolved
and now enable multiple, classical use cases of reusing models.
In this webinar, we will illustrate:
How the Capella technology of replicable elements (aka REC/RPL) both enables
flexible design workflows (including instance-driven modeling) and
makes possible the modeling of architectures by assembly of building blocks.
How Yuzu leverages Capella to help manage the life-cycle
of building blocks and model assets, their dependencies,
their versioning, their publication, etc.
PABRE System - Software Requirement PatternsGESSI UPC
This presentation describes the PABRE tools for the USE, MANAGEMENT AND EVOLUTION OF SOFTWARE REQUIREMENT PATTERNS FOR REQUIREMENTS ENGINEERING ELICITATION.
PABRE framework: http://www.upc.edu/gessi/PABRE/
PABRE system: http://www.upc.edu/gessi/PABRE/Tools.html
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the first unit in the syllabus are covered. I hope it will be helpful to the students.
Test Driven Development (TDD) is a core practice in the SDLC, especially ones that run using the agile mindset and leverage the practices of eXtreme programming. Since its inception and rediscovery by Kent beck in the late 1990s, it has gained popularity among many software development teams. However, like any popular software development practices, teams lose interest in TDD overtime and drop the practice all together. The main reason behind this is practicing it "the wrong way".
In this session, I present 7 anti-patterns that can ruin the TDD experience of a software development team. I also present how to counter these anti-patterns to fully leverage the benefits of TDD.
During the last years we have seen the evolution of Xamarin Forms that has brought new improvements, as well as great contributions from the community. This implies that perhaps in the way that some things were done some time ago, there are currently better and simpler ways of doing it. In this talk we will discuss best practices when programming in Xamarin Forms, as well as architecture, dependency injection, performance, use of plugins and components, among others.
MDD - Desarrollo de software dirigido por modelos que funciona (de verdad!)Jordi Cabot
Consejos para tener éxito en la adopción de una estrategia MDD en vuestro proceso de desarrollo.
Más sobre estos temas (UML, DSLs, MDA, generación de código,..) en http://modeling-languages.com
Applying Systems Thinking to Solve Wicked Problems in Software EngineeringMajed Ayyad
Software systems are essentially socio-technical systems
and they are not isolated from other systems engineering processes. Unconsciously or by intention, we implement systems thinking in multi-agent systems, microservices, DevOps, distributed systems, API-led integrations and lean based software development life cycles. However, the concrete relationship between systems thinking and software engineering is still a green area and barely highlighted as a common practice among software engineers. In this presentation, we will
elaborate how systems thinking helps us to understand the socio-technical aspects of software engineering. We will discuss why systems thinking is important in the field of software engineering, provide examples where it is currently used and show the general areas where systems thinking applies to tackle complex software problems
LML to SysML and Back - Systems Engineering LanguagesElizabeth Steiner
Steven Dam, Ph.D., ESEP shares his knowledge of the Lifecycle Modeling Language and the Systems Modeling Language. He discusses SysML's and LML's vast capabilities and how they work together in Innoslate®. The live presentation also demonstrates both LML and SysML diagrams as they have been developed for Innoslate®.
Metodología de desarrollo de software basada en componentesEmmanuel Fontán
Metodología de desarrollo de software basada en componentes, trabajo para la Cátedra de Metodología de Sistemas 1 de la Universidad Nacional de Entre Ríos, en el año 2010
Kong Summit 2018 - Microservices: decomposing applications for testability an...Chris Richardson
In this presentation, I describe the essential characteristics of the microservice architecture. You will learn about the benefits and drawbacks of the microservice architecture and when it makes sense to use it. I discuss how the microservice architecture is not a silver bullet. You will learn about the microservice pattern language, which is a collection of patterns that solve architecture and design issues that you will encounter when using microservices.
Lenguajes de trazabilidad expresiones regularesGiovani Ramirez
Permiten filtrar textos para encontrar coincidencias, comprobar la validez de fechas, documentos de identidad o contraseñas, se pueden utilizar para reemplazar texto con unas características concretas por otro, y muchos más usos como mostrar si hay errores en todo el proceso
A brief history of Blinkist backend time. I gave this talk at the Adidas Developer conference in Erlangen. The Adidas developer community is awesome! Go check out their Github repositories for all the project they've contributed https://github.com/adidas
Strategies and Tools for Model Reuse with CapellaObeo
How to manage libraries and building blocks?
Reusing models or parts of models with Capella
is not only conceptually appealing, it is a real productivity enabler.
But it is also a true challenge!
Technical solutions initially dedicated to simple duplication
and synchronisation of model parts have recently evolved
and now enable multiple, classical use cases of reusing models.
In this webinar, we will illustrate:
How the Capella technology of replicable elements (aka REC/RPL) both enables
flexible design workflows (including instance-driven modeling) and
makes possible the modeling of architectures by assembly of building blocks.
How Yuzu leverages Capella to help manage the life-cycle
of building blocks and model assets, their dependencies,
their versioning, their publication, etc.
PABRE System - Software Requirement PatternsGESSI UPC
This presentation describes the PABRE tools for the USE, MANAGEMENT AND EVOLUTION OF SOFTWARE REQUIREMENT PATTERNS FOR REQUIREMENTS ENGINEERING ELICITATION.
PABRE framework: http://www.upc.edu/gessi/PABRE/
PABRE system: http://www.upc.edu/gessi/PABRE/Tools.html
The customer will typically be required to provide or choose a billing address, a mailing address, a delivery option, and payment details like a credit card number. As soon as the order is placed, a customer notification email is delivered.
Clipper: A Low-Latency Online Prediction Serving System: Spark Summit East ta...Spark Summit
Machine learning is being deployed in a growing number of applications which demand real-time, accurate, and robust predictions under heavy query load. However, most machine learning frameworks and systems only address model training and not deployment.
In this talk, we present Clipper, a general-purpose low-latency prediction serving system. Interposing between end-user applications and a wide range of machine learning frameworks, Clipper introduces a modular architecture to simplify model deployment across frameworks. Furthermore, by introducing caching, batching, and adaptive model selection techniques, Clipper reduces prediction latency and improves prediction throughput, accuracy, and robustness without modifying the underlying machine learning frameworks. We evaluated Clipper on four common machine learning benchmark datasets and demonstrate its ability to meet the latency, accuracy, and throughput demands of online serving applications. We also compared Clipper to the Tensorflow Serving system and demonstrate comparable prediction throughput and latency on a range of models while enabling new functionality, improved accuracy, and robustness.
Best practice adoption (and lack there of)John Pape
This is a short presentation I created some time ago that details some of the developmental, procedural, and infrastructure best practices that I discovered while working with various customers.
[SEBD2020] OLAP Querying of Document Stores in the Presence of Schema VarietyUniversity of Bologna
Paper presented at SEBD 2020
Document stores are preferred to relational ones for storing heterogeneous data due to their schemaless nature. However, the absence of a unique schema adds complexity to analytical applications. In a previous paper we have proposed an original approach to OLAP on document stores; its basic idea was to stop fighting against schema variety and welcome it as an inherent source of information wealth in schemaless sources. In this paper we focus on the querying phase, showing how queries can be directly rewritten on a heterogeneous collection in an inclusive way, i.e., also including the concepts present in a subset of documents only.
Authors: Matteo Francia, Enrico Gallinucci, Matteo Golfarelli, Stefano Rizzi
The field of machine programming — the automation of the development of software — is making notable research advances. This is, in part, due to the emergence of a wide range of novel techniques in machine learning. In today’s technological landscape, software is integrated into almost everything we do, but maintaining software is a time-consuming and error-prone process. When fully realized, machine programming will enable everyone to express their creativity and develop their own software without writing a single line of code. Intel realizes the pioneering promise of machine programming, which is why it created the Machine Programming Research (MPR) team in Intel Labs. The MPR team’s goal is to create a society where everyone can create software, but machines will handle the “programming” part.
This is episode 3 of the building the perfect PHP app for the enterprise webinar series. Your application is your reputation – how do you ensure it's always available and meets demand without breaking the bank? Learn techniques and tools to quickly pinpoint and fix bugs, crashes, and stability issues in production.
iStarJSON: A Lightweight Data-Format for i* ModelsGESSI UPC
JSON is one of the most widely used data-interchange format. There is a large number of tools open for modelling with i*. However, none of them provides supporting for JSON. In this paper we propose iStarJSON language, a JSON-based proposal for interchanging i* models. We also, present an open source software that transforms XML-based format models to JSON models that expose a set of web services for mining iStarJSON models.
Towards iStarML 2.0: Closing Gaps from Evolved RequirementsGESSI UPC
iStarML is an XML-based format for enabling interoperability among i* tools. Its main design focus was to support data interchange even when involved tools implement different i* variants. In this paper we analyse required changes to the format from two main sources (i) the evolution of i* into a consistent and clear set of core concepts expressed in the new iStar 2.0 specification and (ii) recurrent necessities due to a wide use of i* modelling. In order to address these requirements, we propose new XML elements to be considered in a new version of iStarML: iStarML2.0
Organizations are increasingly becoming Open Source Software (OSS) adopters, either as a result of a strategic decision or just as a consequence of technological choices. The strategy followed to adopt OSS shapes organizations’ businesses; therefore methods to assess such impact are needed. In this paper, we propose OSSAP, a method for defining OSS Adoption business Processes, built using a Situational Method Engineering (SME) approach. We use SME to combine two well-known modelling methods, namely goal-oriented models (using i*) and business process models (using BPMN), with a pre-existing catalogue of goal-oriented OSS adoption strategy models. First, we define a repository of reusable method chunks, including the guidelines to apply them. Then, we define OSSAP as a composition of those method chunks to help organizations to improve their business processes in order to integrate the best fitting OSS adoption strategy. We illustrate it with an example of application in a telecommunications company.
Aligning Business Goals and Risks in OSS AdoptionGESSI UPC
Increasing adoption of Open Source Software (OSS) requires a change in the or-ganizational culture and reshaping IT decision-makers mindset. Adopting OSS software components introduces some risks that can affect the adopter organiza-tion’s business goals, therefore they need to be considered. To assess these risks, it is required to understand the socio-technical structures that interrelate the stake-holders in the OSS ecosystem, and how these structures may propagate the po-tential risks to them. In this paper, we study the connection between OSS adop-tion risks and OSS adopter organizations’ business goals . We propose a model-based approach and analysis framework that combines two existing frameworks: the i* framework to model and reason about business goals, and the RiskML no-tation to represent and analyse OSS adoption risks. We illustrate our approach with data drawn from an industrial partner organisation in a joint EU project.
Jcis 2015-Towards Assessing Open Source Communities' Health using SOC ConceptsGESSI UPC
Quality of an open source software ecosystem (OSS ecosystem) is key for dierent ecosystem actors such as contributors or adopters. In fact, the consideration of several quality aspects(e.g., activeness, visibility, interrelatedness, etc.) as a whole may provide a measure of the healthiness of OSS ecosystems. The more health a OSS ecosystem is, the
more and better contributors and adopters it will gather. Some research tools have been developed to gather specic quality information from open source community data sources. However, there exist no frameworks available that can be used to evaluate their quality as a whole in order to obtain the health of an OSS ecosystem. To assess the health of these ecosystems, we propose to adopt robust principles and methods from the Service Oriented Computing field.
RISCOSS: Gestión del riesgo en proyectos open source (Open Expo Day2015)GESSI UPC
Presentación de la metodología de gestión de riesgos en la adopción de proyectos OSS y la plataforma software que integra toda la cadena de toma de decisiones, teneinendo en cuenta criterios tecnológicos y estratégicos. Incluyendo métodos para identificar, gestionar y mitigar riesgos asociados con la integración de software open source. El proyecto RISCOSS (FP7) provee una solución completa para habilitar que los desarrolladores de producto integren de manera segura software open source en sus desarrollos. La comunidad RISCOSS está abierta a contribuciones de terceros, para permitir el desarollo continuo tanto de la plataforma como de las metodologias, juntamente con los servicios y el producto comercial.
Presentación de la metodología de gestión de riesgos en la adopción de proyectos OSS y la plataforma software que integra toda la cadena de toma de decisiones, teneinendo en cuenta criterios tecnológicos y estratégicos. Incluyendo métodos para identificar, gestionar y mitigar riesgos asociados con la integración de software open source. El proyecto RISCOSS (FP7) provee una solución completa para habilitar que los desarrolladores de producto integren de manera segura software open source en sus desarrollos. La comunidad RISCOSS está abierta a contribuciones de terceros, para permitir el desarollo continuo tanto de la plataforma como de las metodologias, juntamente con los servicios y el producto comercial.
Open source software ecosystem modelling has emerged asan important research area in software engineering. Several models havebeen proposed to identify and analyse the complex relationships in OSS-ecosystems. However, there is a lack of formal models, methodologies,tool support, and standard notations for OSS-ecosystems. In this paperwe propose a general framework for support the OSS-ecosystems mod-elling process. This framework will allow the representation, synthesis,analysis, evaluation, and evolution of OSS-ecosystems. Design sciencemethodology is proposed to create several artefacts and investigatingthe suitability of these artefacts in the OSS-ecosystem context.
Increasing adoption of Open Source Software (OSS) in information system engineering has led to the emergence of different OSS business strategies that affect and shape organizations’ business models. In this context, organizational modeling needs to reconcile efficiently OSS adoption strategies with business strategies and models. In this paper, we propose to embed all the knowledge about each OSS adoption strategy into an i* model that can be used in the intentional modeling of the organization. These models describe the consequences of adopting one such strategy or another: which are the business goals that are supported, which are the resources that emerge, etc. To this aim, we first enumerate the main existing OSS adoption strategies, next we formulate an ontology that comprises the activities and resources that characterise
these strategies, then based on the experience of 5 industrial partners of the RISCOSS EU-funded project, we explore how these elements are managed in each strategy and formulate the corresponding model using the i* vframework.
QuESo: a Quality Model for Open Source Software EcosystemsGESSI UPC
Open source software has witnessed an exponential growth in the last two decades and it is playing an increasingly
important role in many companies and organizations leading to the formation of open source software
ecosystems. In this paper we present a quality model that will allow the evaluation of those ecosystems in
terms of their relevant quality characteristics such as health or activeness.
To take maximum advantage of open source software (OSS), the understanding, management and mitigation of OSS adoption risks is crucial. We describe the empirical application of the tactical workshops with the purpose of obtaining the domain expert evaluation.
MoDRE 2014 @ RE keynote -- NFR-Aware MDD ProcessesGESSI UPC
Software systems cannot be successful without taking non-functional requirements (NFRs) into account. But still there seems to be a lopsided emphasis on the functionality of the system, even though the functionality is not useful or usable when NFRs do not hold. MDD is not an exception to this rule. In this keynote, we will first analyse the state of the art in MDD with respect to NFR treatment. Next, we will reflect on the possible ways to fit NFRs in the MDD process and the consequences of each alternative. At the end, we will discuss a research agenda. Based on research done with other members of the GESSI group in collaboration with other research teams
Quantifying the Impact of OSS Adoption Risks with the help of i* ModelsGESSI UPC
Dolors Costal, Daniel Gross, Lidia Lopez, Mirko Morandini, Alberto Siena, Angelo Susi: Quantifying the Impact of OSS Adoption Risks with the help of i* Models. 7th i* Int. Workshop held at CAiSE 2014. Paper at http://ceur-ws.org/Vol-1157/paper10.pdf. Adopting Open Source Software (OSS) components in or ganisational settings requires evaluating the possible impact of adoption decisions on business goals. Measures available in OSS, capturing indicators such as the quality of open source code and the activeness of the developing community, can be used as a driver to assess various risks
in component adoption. In this paper we illustrate how risk and impact models are used to relate measures obtained from the component under analysis to business goals in i* -based OSS business strategy models.
Applying Business Strategy Models in OrganizationsGESSI UPC
Lidia López, Xavier Franch: Applying Business Strategy Models in Organizations. 7th i* Int. Workshop held at CAiSE 2014. Paper at http://ceur-ws.org/Vol-1157/paper6.pdf.
Abstract. Increasing adoption of Open Source Software (OSS) in information system engineering has led to the emergence of different OSS business strategies that affect and shape organizations’ business models. In order to obtain the specific organizational model for a concrete organization that is adhering to a specific OSS business strategy, we need to instantiate the general knowledge included in this business strategy. This paper describe the process in which this general knowledge is instantiated and define a set of operations over i* models to implement the instantiation concept. Although conceived in the field of OSS, the approach is generalizable to any kind of business strategy.
A Context Ontology for Service Provisioning and ConsumptionGESSI UPC
Nowadays services as those provided by smart cities, health smart services, as well as common services (e.g., telephonic services, e-mail services), have a great economic impact for organisations and represent an important mean to deliver value to their consumers. The malfunctions of both the services themselves as well as the entities responsible for their execution and consumption might cause economic losses, consumers’ dissatisfaction and even shorten the service life cycle, among other risks. To avoid malfunctions beyond maintaining quality levels desired, it is important to take into account the widest possible context information that cause either positive or negative effects around services and entities involved in their provisioning and consumption. In this paper, we propose an upper ontology for service provisioning and consumption from a service-centric perspective. Specifically, we focus on software services, although
we could argue for more generic applications. The contribution is the analysis, evaluation and reuse of existing proposals on context models to identify the strengths and weaknesses of its current status as well as to identify contexts not yet considered, and
consolidate an integrated view of these proposals. The ultimate intention is to provide a well-defined and consolidated infrastructure of context information as a common body of
knowledge, that could be instantiated on variety of use cases, for example, to be instantiated by monitors as context information useful to be monitored, or to be used as context information that allows knowing which contexts affect a service when a user
consumes it, among others.
Practical Experiences in Designing and Conducting Empirical Studies in Indust...GESSI UPC
Research paper at Second Intl. Workshop on Conducting Empirical Studies in Industry. CESI 2014 - An ICSE 2014 Workshop (2nd June 2014)
http://www.essi.upc.edu/~franch/cesi2014/program.html
Research paper at Second Intl. Workshop on Conducting Empirical Studies in Industry. CESI 2014 - An ICSE 2014 Workshop (2nd June 2014)
http://www.essi.upc.edu/~franch/cesi2014/program.html
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
4. GESSI: Software Requirement Patterns
Context
Patterns
RequirementsEl
icitationStage
(less global errors)
RequirementsB
ook
Patterns
(more reqs. quality)
Requirement
(natural
language)
The system shall provide
the user interface available
in languagesSet languages.
4
5. GESSI: Software Requirement Patterns
What is the problem?
•
•
PROBLEM: Most of the requirements books contains ambiguous,
incomplete or incoherent requirements, and sometimes they are stated
in an unsystematic way.
SOLUTION: Software Requirement Patterns (SRP).
Pattern
– Alexander, 1979 ‘‘each pattern describes a problem which occurs over and
over again in our environment, and then describes the core of the solution
to that problem’’
Requirement Pattern
– Withall, 2007 ‘‘a requirement pattern is a guide to writing a particular type
of requirement’’
Patterns
•
BENEFITS
1. +↑ quality of requirements
2. −↓ time and effort spent during requirements elicitation ( economic saving).
Requirements
Elicitation Stage
(less global errors)
Requirements
Book
Patterns
(more reqs. quality)
Requirement
(natural
language)
The system shall provide
the user interface available
in languagesSet languages.
5
6. A Specific Organization
GESSI: Software Requirement Patterns
SSI department, Centre de Recherche Publique Henri Tudor (CRPHT)
• Helping SME with no experience in Requirements Engineering.
• Designing requirement books to conduct Call-For-Tender processes for
selecting Off-The-Shelf solutions.
1. The system must be available 22 hours
per day and 7 days per week.
2. Should be possible to use the system in English
or French.
3. The system should not stop more than 1
hour per working day. The solution’s
availability rate should be 98% minimum.
4. The solution should permit to trace all the user
actions. The data to trace are: user name, date,
accessed or modified data.
• More than 40 projects done.
• Appliedreuse: starting a new projectbyeditingthemost similar one.
• Better capitalization of requirements in a high-level manner.
• Avoiding ambiguous, incomplete or incoherent requirements.
Strategy
• Software RequirementsPatterns (SRP).
6
8. Example: Failure Alerts
GESSI: Software Requirement Patterns
Pattern’s Goal: Having system that provides alerts when system failures occur.
How do their requirements look like?
The solution should alert of disks close to their capacity .
alert
disks closetotheircapacity
In case of a network orserver disk crash the solution should alert immediately.
networkor server disk crash,
alert
The system should alert the administrator of the resources (physical or logical)
alert
resources (physicalorlogical)
closetotheircapacity
close to their capacity.
Requirement
template
The system shall trigger alerts in case of
failuresSet failures.
failuresSet : set of possibleFailures
o possibleFailures: server crash | disk crash …
8
9. Example: Failure Alerts
GESSI: Software Requirement Patterns
Requirement Pattern Failure Alerts
Goal: Satisfy the customer need of having a system that provides alerts when system failures occur.
Template
The system shall trigger an alert in case of failure.
Extended
Fixed Part
multiplicity(Alerts Types) = 0..1 and
Parts
Constraint multiplicity(Failure Types) = 0..1
Requirement
Extended Part
Form
Homogeneous Alert Types
Failure Alerts
Template
The solution shall trigger %alertsSet% alerts in case of failure
Metric
Parameter
alertsSet alertsSet: Set(AlertType) Fax | Sound ….
AlertType: SMS | Mail |
Template
The system shall trigger alerts in case of %failuresSet% failures
Metric
Extended Part Parameter
Failure Types
failuresSet failuresSet: Set(FailureType) crash …
FailureType: server crash | disk
Template
Fixed Part
Requirement
Form
Heterogeneous
Failure Alerts
Thesystemshalltriggerdifferenttypes
failure.
of
alertsdependingonthetype
Extended
Parts
Constraint
of
Multiplicity(Alerts for Failure Types) = 0..*
Thesystemshalltrigger %alertsSet% alerts in case of %failuresSet%
failures.
Metric
Parameter
alertsSet alertsSet: Set(AlertType) Fax | Sound ….
AlertType: SMS | Mail |
failuresSet failuresSet: Set(FailureType) crash …
FailureType: server crash | disk
Template
Extended Part
Alerts for
Failure Types
9
11. GESSI: Software Requirement Patterns
Metamodel – SRP Structure
A patternrepresents a cluster of
requirements (a group of
interrelatedrequirements).
Example:
Failure Alerts
A requirement
pattern…
A form captures a particular context that may
be the most appropiatefor a software project.
… has several
forms …
Examples:
Homogeneous Failure Alerts
Heterogeneous Failure Alerts
... and several
constrainst(s).
… that are made of 1
fixed part …
... and several
extended part(s)…
For declaring multiplicities or dependencies
among parts.
Examples:
excludes, requires …
A fixed partcontainsthemost
abstractexpression of a requirement.
A extended part contains other ways to
express a requirement (often with parameters).
Example:
The system shall trigger an
alert in case of failure.
Examples:
The system shall trigger an alert in
case of failure.
alert: SMS | Mail | Fax | Sound | …
failure: network crash | disk crash | …
11
12. GESSI: Software Requirement Patterns
Metamodel - Overview
CatalogueClas
sification
/
Core: SRP
Relationship
Application
PartsRelationshipexample:
Alerts for Failure Types↔ Data Integrity by Failure
(Failure Alerts)
(Recovery Procedures)
The system shall trigger alertsSet alerts in case
of failuresSet failures
Data shall be protected in case of failuresSet
failures.
12
14. GESSI: Software Requirement Patterns
SRP Catalogue
•Set of all defined SRPs.
• SRP catalogue: organizedaccording to differentClassificationSchemas:
Hierarchical classification to index SRP.
Goals:
Makeeasierunderstanding and reuse of patterns.
Improvecatalogue’susability and portability.
14
15. SRP Catalogue – current version
GESSI: Software Requirement Patterns
• 29 non-functional & 3 non-technical requirement patterns.
• SRP catalogue according to ISO/IEC 9126-1 classification schema.
Functionality
Reliability
Suitability
-
Maturity
Failure alerts
Accuracy
Data precision
Fault Tolerance
Alternative data storage, Availability, Downtime, Uptime
Interoperability
Data exchange,Interoperability with external systems
Recoverability
Backups, Log
Security
Authentication, Authorization, Automatic logoff, Data
transmission protection, Stored data protection
R. Compliance
-
F. Compliance
-
Analyzability
-
Changeability
-
Stability
-
Usability
Maintainablity
Understandability
Interface Language, Interface type
Learnability
Online help, Interface learnability, Documentation
Testability
-
Operability
Failure alerts, Recovery procedures, Installation
procedures, Update procedures
M. Compliance
-
Attractiveness
-
Portability
U. Compliance
-
Adaptability
Development language
Installability
Platform
Efficiency
Time Behaviour
Interface load time, Concurrent users capacity
Coexistence
-
Resource Utilisation
Data capacity, Users capacity
Replaceability
-
E. Compliance
Backups, Log
P. Compliance
-
15
16. GESSI: Software Requirement Patterns
SRP Catalogue - construction
7 Requirement Books
Analysis of books
Focus on Non-Functional Requirements (NFR).
48 NFR Patterns
Refinement
1. Case studies (post-mortem analysis of some
requirement books).
2. Experts review (iterations between SSI & GESSI ).
3. Literature review (GESSI).
29 NFR Patterns
3 Non-Technical Patterns
16
18. GESSI: Software Requirement Patterns
PABRE Method
Knowledge of the
Reqt. pattern
catalogue
Needs
IT Consultant
Customer
•PABRE: PAtternBasedRequirementsElicitation.
Supplier
Supplier
Supplier
6
•Method to create and useSRPs.
Requirements Elicitation
•Goals:
Patterns
Exploration
Parts
Exploration
Requirem.
Extraction
Call for
tenders
Requirements
1. Generation of theneededrequirementsbook.
Book
Requirem.
2. Help in therequirementselicitationphase:
Creation
Less time to do it.
Less errors in theresult.
Reqt.
Patterns
Catalogue
Knowledge of
previous projects
Forms
Exploration
Catalogue
Evolution
Feedback
Repository
Requirements
Expert
OTS-based
Solution
Heavy Process
Why don’t we
use tools?
18
21. GESSI: Software Requirement Patterns
Validation
• During building the catalogue and metamodel:
SSI conducted two case studies to do an initial
validation:
1. Improve the contents and the metamodel of the catalogue:
the first one (a digital library system).
2. Catalogue validation: the second one (a CRM SaaS project)
used fro validation to obtain feedback of the adequacy of the
resulting catalogue.
• All the approach:
SSI did a small project for a company (July 2010):
• 29 NFRs stated using 21 different SRPs.
(only 2 reqs didn’t become from SRPs!)
21
25. GESSI: Software Requirement Patterns
Future Work
•
Validation of the approach (catalogue, method, tool,
etc.):
Call-for-tender processes: collaboration of SSI-CPRHT and
CASSIS consultants.
Other different domains.
•
Improve and expand tools’ functionalities.
Interoperability with other requirement engineering tools (Irqa,…).
•
•
Expand SRP catalogue with other types of requirements
(non-technical, functional).
Automatic computation of patterns from requirement
books.
25
27. GESSI: Software Requirement Patterns
Other approaches
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
Scope
General purpose
General purpose
Business applications
General purpose
Embedded systems
Security requirements
Security requirements
General purpose
General purpose
Notation
Natural language
Object models
Event-Use case
Semi-formal models
Logic-based
UML class diagrams
Natural language
Natural language
Problem frames + i*
Application
Req. elicitation
Variability modeling
Identify patterns
Writing req. models
From informal to formal reqs.
Security goals elicitation
Req. elicitation in SOC
Writing SRS
Knowledge management
Metamodel?
Just templates
Yes
No
Yes
No
No
No
Just template
No
Ours
General purpose
Natural language
Writing SRSs
Yes
5. A. Durán, B. Bernárdez, A. Ruíz, M. Toro. “A Requirements Elicitation Approach Based in Templates and
Patterns”. WER 1999.
6. B. Moros, C. Vicente, A. Toval. “Metamodeling Variability to Enable Requirements Reuse”. EMMSAD 2008.
7. S. Robertson. “Requirements Patterns Via Events/Use Cases”. PLoP 1996.
8. O. López, M.A. Laguna, F.J. García. “Metamodeling for Requirements Reuse”. WER 2002.
9. S. Konrad, B.H.C. Cheng. “Requirements Patterns for Embedded Systems”. RE 2002.
10. D. Matheson, I. Ray, I. Ray, S. H. Houmb. “Building Security Requirement Patterns for Increased Effectiveness
Early in the Development Process”. SREIS 2005.
11. A. Mahfouz, L. Barroca, R. C. Laney, B. Nuseibeh. Patterns for Service-Oriented Information Exchange
Requirements. PLoP, 2006.
12. J. Withall. Software Requirements Patterns. Microsoft Press, 2007.
13. J. Yang, L. Liu. “Modelling Requirements Patterns with a Goal and PF Integrated Analysis Approach”. COMPSAC
2008.
27
28. GESSI: Software Requirement Patterns
Metamodel - Relationships
… pattern
relationship, …
… form
relationship
and…
Implies all the forms
and all the parts of
the related patterns.
Implies all the
parts of the
related forms.
… part
relationship.
Only applying to
these 2 parts.
A general relationship
is specified in…
If A is related to B and A is applied in a project, is mandatory know
the type of this relationship: for instance, apply or avoid B.
Example:
Authorization pattern
IMPLIES
Authentication pattern
But relationship types not defined more flexibility.
28
29. GESSI: Software Requirement Patterns
Metamodel - Classification
… is compossed for 1 or more Root
Classifiers and each one of them…
A Classification
Schema…
Hierarchical classification to index patterns.
Example:
Usability, Portability, Efficiency …
Example:
ISO/IEC 9126-1
/
… contains 1 or more
Classifiers. A Classifier
can be…
Example:
Attractiveness, U. Compliance,
Operability, Learnability …
… a Basic Classifier or…
… a Compound Classifier.
Contains only SRP.
Again contains 2 or more classifiers.
Example:
The basic classifier Operability
contains the following patterns:
Installation Procedures, Recovery
Procedures, Failure Alerts …
Example:
The compound classifier Reliability
contains the following classifiers:
Fault Tolerance, Maturity,
Recoverability …
29
30. SRP Catalogue - construction
•1st phase result: 1st version of the catalogue (48 SRPs) and
GESSI: Software Requirement Patterns
metamodel
1. Analysis req. books focus on Non-functional requirements.
2. GESSI - UPC academic experts + SSI experts knowledge.
3. GESSI - UPC knowledge: analysis structure, relationship and
organization of requirements in req. books.
4. SSI experts knowledge: feedback, suggestions, requirements
on the pattern structure.
1st catalogue
1stmetamodel
•2nd phase result: 2nd version of the catalogue (29 NFR & 3
Non-technical SRPs) and metamodel
1. Use req.books to validate catalogue: applying patterns for recreating
them.
2. SSI experts knowledge + requirement engineers experienced in OTS:
review first catalogue version.
3. SSI experts knowledge: 2 case studies
1) To improve the contents of the catalogue.
2) For validation: to obtain feedback about the adequacy of the
resulting catalogue.
4. Literature review (3 types of sources).
5. SSI experts knowledge + requirement engineers experienced in OTS:
review catalogue structure ( metamodel). Relevant attributes and
new elements in the pattern structure (as questions).
2nd catalogue
2ndmetamodel
30
31. GESSI: Software Requirement Patterns
PABRE-Man (Patterns Management Tool)
•SRP repository management. Create, update and delete:
SRPs.
Metrics.
Classification schemas.
•SRP repository
exploration:
Browsing of SRP repository according to different classification schemas.
Browsing of all defined metrics.
•SRP use:
Import an xml concerning to a project to update the statistics about the
use of patterns.
Consult use of different SRPs with the aim to update the SRP catalogue.
• SRP catalogue exportation:
Pdf or rtf.
31
33. GESSI: Software Requirement Patterns
PABRE-Cft(Projects Management Tool)
•Projects repository management:
Create, copy, update and delete projects.
Create, update and delete requirements:
a. Created as an instance of a SRP.
b. Created from scratch.
•Project and SRP repository browsing:
Browsing of projects and their requirements.
Browsing of SRP repository.
•Generation of call-for-tenders document.
• Exporting projects:
Xml or pdf.
• Exporting SRPs use.
33