Supporting Software
•
0 likes•163 views
The document discusses expanding support for software users by providing multiple avenues of help including email lists, FAQs, tutorials, a public issue tracker, and chat rooms. It emphasizes being honest about quality of service commitments like response times, supported platforms and issue scope, as well as types of support offered such as general help or tailored solutions. Alternative resources are suggested to help users help each other through a public archive and code drops while still ensuring individual requests are addressed.
Report
Share
Report
Share
Recommended
Sustainability Training Workshop - Managing Sustainability into Software
Sustainability Training Workshop - Managing Sustainability into SoftwareSoftware Sustainability Institute
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.Governance for Software
The document discusses several key aspects of project governance, ownership, exploitation, and funding for software projects, including:
1) Governance models can range from a single leader to a meritocratic model, and the level of control needs to balance the originator's vision with expanding contribution.
2) Ownership is usually defined by copyright, but gets complicated with many contributors; contribution agreements and a single custodian can help define ownership and accountability.
3) Exploitation considers how the software can move forward commercially or as open source, targeting current and potential new users as well as integrators and partners.
4) Funding can come from grants, donations, services, licensing, or spin-
Preserving software workshop - Community engagement workshop
A presentation by Matt Shreeve from curtis+cartwright Consulting Ltd..
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010
Digital Economies Southampton
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Managing Code in Repositories
The document discusses code repositories and recommends hosting code online for open source projects. It describes how code repositories provide a safe place to store code, manage changes, and collaborate. It then discusses local versus internet repositories and recommends internet repositories for open source projects to avoid hosting burdens. Several popular online repositories are described, including SourceForge, Google Code, and GitHub.
Ssi maintainers
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
Lightning talks - Workshop for e-Infrastructure trainers
A summary and all the slides for the lightning talks session at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Introduction to the Software Sustainability Institute
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
Recommended
Sustainability Training Workshop - Managing Sustainability into Software
Sustainability Training Workshop - Managing Sustainability into SoftwareSoftware Sustainability Institute
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.Governance for Software
The document discusses several key aspects of project governance, ownership, exploitation, and funding for software projects, including:
1) Governance models can range from a single leader to a meritocratic model, and the level of control needs to balance the originator's vision with expanding contribution.
2) Ownership is usually defined by copyright, but gets complicated with many contributors; contribution agreements and a single custodian can help define ownership and accountability.
3) Exploitation considers how the software can move forward commercially or as open source, targeting current and potential new users as well as integrators and partners.
4) Funding can come from grants, donations, services, licensing, or spin-
Preserving software workshop - Community engagement workshop
A presentation by Matt Shreeve from curtis+cartwright Consulting Ltd..
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010
Digital Economies Southampton
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Managing Code in Repositories
The document discusses code repositories and recommends hosting code online for open source projects. It describes how code repositories provide a safe place to store code, manage changes, and collaborate. It then discusses local versus internet repositories and recommends internet repositories for open source projects to avoid hosting burdens. Several popular online repositories are described, including SourceForge, Google Code, and GitHub.
Ssi maintainers
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
Lightning talks - Workshop for e-Infrastructure trainers
A summary and all the slides for the lightning talks session at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Introduction to the Software Sustainability Institute
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
Engaging the software in research community
The document discusses the Software Sustainability Institute's community engagement efforts, including its Agents/Super Pals program and Fellows program. It recruits early-career and mid-career researchers to gather intelligence, run workshops, and provide feedback. The Fellows program has grown from 10 Agents in 2011 to 15 Fellows in 2013 across various research domains. The goals are to effectively serve the research community, maximize the Institute's impact, and promote awareness of software sustainability best practices.
How does the workshop work?
The document provides information about a workshop hosted at www.software.ac.uk, including details on how it works, the events team members, ways to provide feedback, announcements, an agents network, and collaborative ideas activities. Attendees are encouraged to meet new people, visit the website for information, email (but not attach) documents, and that the workshop is flexible.
The provision of support and training for e-Infrastructure users and potentia...
The provision of support and training for e-Infrastructure users and potentia...Software Sustainability Institute
Presented by Simon Hettrick at the e-Infrastructure Academic User Community Forum, this talk provides a number of recommendations for improving the provision of training for e-Infrastructure.Introductory Talk - Workshop for e-Infrastructure trainers
The introductory talk given by the Software Sustainability Institute's Simon Hettrick at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Preserving software workshop - Sustainability approaches
A presentation by Neil Chue Hong, Director of the Software Sustainability Institute.
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010.
Issue Tracking
Issue tracking allows organizations to manage changes and bugs in an ordered way. An issue can represent any query, occurrence, or task that may impact a project, such as a software bug, request for change, or action item from a meeting. When an issue is reported, it goes through a typical workflow of being assigned, accepted, worked on, and eventually closed or reopened. Popular open source bug trackers include Bugzilla, Trac, and JIRA, with Trac being a good example of a lightweight yet powerful option that allows cross-referencing with wikis and version control systems.
Coordinating Documentation and Support: Turning Complaints into Contributions
This talk describes a process to extend and integrate support and documentation contributor communities
Adopting Open Source Software for Longer-term Reuse
This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.
Why Good Software Sometimes Dies... and how to save it
A talk given by Neil Chue Hong at the JISC Innovation Forum 08 on software sustainability and the issues, challenges and potential solutions to improve the longevity and uptake of your research software.
Understanding Stakeholder Needs
The document discusses understanding stakeholder needs when developing requirements for a software system. It describes sources of requirements like customers and users, characteristics of different types of customers, potential problems that can be encountered, and techniques for eliciting requirements like workshops, brainstorming, use cases, interviews, and questionnaires.
Leveraging the Power of B2B Social Communities
Kellie Parker, leader of a four-person community team for SEGA of America, gives the inside scoop on setting up a B2B social community and discusses best practices. Included: choosing which tools you’ll need, understanding how to leverage reader-generated content and how much editorial involvement is needed for different types of social sites.
Building the Social Library Online - Copenhagen
The document discusses how social software can benefit libraries. It defines social software as tools that allow people to communicate, collaborate, and build community online. Examples include blogs, wikis, social networking sites, and more. The document outlines characteristics of social software like easy content creation and sharing. It explores how libraries can use social software to disseminate information, get feedback from users, provide remote services, and capitalize on collective intelligence. Finally, it provides strategies for implementing social software in libraries, such as involving staff, considering barriers to use, and starting small.
Project considerations etp
The document outlines Ed Tech Productions' process for developing instructional projects. It discusses conducting client consultations to determine project needs and goals, including topics, budget, timeline and requirements. A feasibility study may then examine the best technologies. Next is a drafting phase where the project components and their interactions are planned out in a blueprint. An approved blueprint marks the start of pre-production.
How to Effectively Lead Focus Groups: Presented at ProductTank Toronto
Topic: How to Effectively Lead Focus Groups
Tremis Skeete, NexTier Innovations
Talking to users can be a challenge and running a focus group is one of those tasks which most Product Managers would say is essential in getting real insights. Whether you want to test your user group's response to a new product or changes to features within an existing product, as a product person you need to have a creative set of analytical skills and strategies for how to steer the group toward productive discussions. In this presentation, Tremis will discuss how focus groups can truly work well for you, and how you can organize, coordinate, and effectively lead focus group sessions.
Requirement analysis
The document discusses software requirements and requirement engineering. It defines what requirements are, including different levels like business, user, and functional requirements. It explains that requirement engineering determines the goals, functions, and constraints of software systems. The document outlines the requirement engineering process and discusses common challenges like the "yes, but" syndrome where users provide additional feedback, and the "undiscovered ruins" syndrome where further requirements are uncovered. It provides examples of techniques to elicit requirements like interviewing stakeholders, workshops, brainstorming, storyboarding, use cases, and prototyping.
Lecture4 requirement engineering
This document discusses requirement engineering and techniques for requirements elicitation. It defines requirements and describes the different levels of requirements from business to functional to non-functional. The key techniques discussed for eliciting requirements include interviewing stakeholders, holding requirements workshops, brainstorming with users, creating storyboards and use cases, and building prototypes. Prototyping in particular is highlighted as an effective way to address common issues in requirements elicitation like the "yes, but" syndrome and discovering additional undisclosed needs.
How to improve Developer Documentations ?
The document proposes solutions to improve the Teams Dev Docs by addressing developer pain points. It identifies key pain points such as difficulty finding relevant content and understanding errors. Possible solutions include a chatbot that can quickly answer questions and documentation that allows coding in native languages. User research is cited to validate the identified pain points. A phased go-to-market strategy is proposed starting with targeted launches of the chatbot and native language support to capture early adopters. The solutions aim to reduce time spent on documentation and increase new developer adoption.
The biggest DevOps problems you didn't know you had and what to do about them
Slide deck from www.ReleaseIQ.io webinar on August 25, 2021. Learn about the biggest problems DevOps teams face. You might be surprised what keeps DevOps teams stuck in mid-evolution.
Concept Presentation
The document discusses testing a prototype for an online dictionary website. It describes the goal of allowing users to create accounts, save words to personal lexicons, and tag words. It then provides sample test questions to evaluate usability, such as how a user would log in, look up a word they previously saved, and save/tag a new word. Next, it lists heuristics for user interface design, such as maintaining visibility of system status, using natural language, allowing user control and undo/redo, consistency, and preventing errors.
Free (like a puppy) Web Tools for Nonprofits
The document discusses different types of "free" software options for non-profits, including open source software, freemium software, donations, and pro bono work, and notes that while the software itself may be free, there are often hidden costs associated with implementation, customization, support, upgrades, and ongoing maintenance that organizations should be aware of and plan for. It provides advice on evaluating options, understanding limitations and responsibilities, defining requirements, and developing a technology plan to successfully adopt new software solutions.
Using Technology to Enhance Events
The document discusses various technologies that can be used to enhance events, including blogs, podcasts, RSS feeds, social media, wikis, and more. It provides examples of how each technology could be used and highlights benefits like reaching a global audience, engaging people, and increasing productivity. The document also emphasizes understanding audiences, writing clearly for the web, establishing trust, and creating a strategic plan for adopting technologies.
The role of user services in 21st century
Academic libraries in the 21st century must learn to adapt to ever-changing technology and user requirements. Service is the key term - if users are unhappy with service, they will go elsewhere.
More Related Content
Viewers also liked
Engaging the software in research community
The document discusses the Software Sustainability Institute's community engagement efforts, including its Agents/Super Pals program and Fellows program. It recruits early-career and mid-career researchers to gather intelligence, run workshops, and provide feedback. The Fellows program has grown from 10 Agents in 2011 to 15 Fellows in 2013 across various research domains. The goals are to effectively serve the research community, maximize the Institute's impact, and promote awareness of software sustainability best practices.
How does the workshop work?
The document provides information about a workshop hosted at www.software.ac.uk, including details on how it works, the events team members, ways to provide feedback, announcements, an agents network, and collaborative ideas activities. Attendees are encouraged to meet new people, visit the website for information, email (but not attach) documents, and that the workshop is flexible.
The provision of support and training for e-Infrastructure users and potentia...
The provision of support and training for e-Infrastructure users and potentia...Software Sustainability Institute
Presented by Simon Hettrick at the e-Infrastructure Academic User Community Forum, this talk provides a number of recommendations for improving the provision of training for e-Infrastructure.Introductory Talk - Workshop for e-Infrastructure trainers
The introductory talk given by the Software Sustainability Institute's Simon Hettrick at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Preserving software workshop - Sustainability approaches
A presentation by Neil Chue Hong, Director of the Software Sustainability Institute.
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010.
Issue Tracking
Issue tracking allows organizations to manage changes and bugs in an ordered way. An issue can represent any query, occurrence, or task that may impact a project, such as a software bug, request for change, or action item from a meeting. When an issue is reported, it goes through a typical workflow of being assigned, accepted, worked on, and eventually closed or reopened. Popular open source bug trackers include Bugzilla, Trac, and JIRA, with Trac being a good example of a lightweight yet powerful option that allows cross-referencing with wikis and version control systems.
Viewers also liked (6)
The provision of support and training for e-Infrastructure users and potentia...
The provision of support and training for e-Infrastructure users and potentia...
Introductory Talk - Workshop for e-Infrastructure trainers
Introductory Talk - Workshop for e-Infrastructure trainers
Preserving software workshop - Sustainability approaches
Preserving software workshop - Sustainability approaches
Similar to Supporting Software
Coordinating Documentation and Support: Turning Complaints into Contributions
This talk describes a process to extend and integrate support and documentation contributor communities
Adopting Open Source Software for Longer-term Reuse
This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.
Why Good Software Sometimes Dies... and how to save it
A talk given by Neil Chue Hong at the JISC Innovation Forum 08 on software sustainability and the issues, challenges and potential solutions to improve the longevity and uptake of your research software.
Understanding Stakeholder Needs
The document discusses understanding stakeholder needs when developing requirements for a software system. It describes sources of requirements like customers and users, characteristics of different types of customers, potential problems that can be encountered, and techniques for eliciting requirements like workshops, brainstorming, use cases, interviews, and questionnaires.
Leveraging the Power of B2B Social Communities
Kellie Parker, leader of a four-person community team for SEGA of America, gives the inside scoop on setting up a B2B social community and discusses best practices. Included: choosing which tools you’ll need, understanding how to leverage reader-generated content and how much editorial involvement is needed for different types of social sites.
Building the Social Library Online - Copenhagen
The document discusses how social software can benefit libraries. It defines social software as tools that allow people to communicate, collaborate, and build community online. Examples include blogs, wikis, social networking sites, and more. The document outlines characteristics of social software like easy content creation and sharing. It explores how libraries can use social software to disseminate information, get feedback from users, provide remote services, and capitalize on collective intelligence. Finally, it provides strategies for implementing social software in libraries, such as involving staff, considering barriers to use, and starting small.
Project considerations etp
The document outlines Ed Tech Productions' process for developing instructional projects. It discusses conducting client consultations to determine project needs and goals, including topics, budget, timeline and requirements. A feasibility study may then examine the best technologies. Next is a drafting phase where the project components and their interactions are planned out in a blueprint. An approved blueprint marks the start of pre-production.
How to Effectively Lead Focus Groups: Presented at ProductTank Toronto
Topic: How to Effectively Lead Focus Groups
Tremis Skeete, NexTier Innovations
Talking to users can be a challenge and running a focus group is one of those tasks which most Product Managers would say is essential in getting real insights. Whether you want to test your user group's response to a new product or changes to features within an existing product, as a product person you need to have a creative set of analytical skills and strategies for how to steer the group toward productive discussions. In this presentation, Tremis will discuss how focus groups can truly work well for you, and how you can organize, coordinate, and effectively lead focus group sessions.
Requirement analysis
The document discusses software requirements and requirement engineering. It defines what requirements are, including different levels like business, user, and functional requirements. It explains that requirement engineering determines the goals, functions, and constraints of software systems. The document outlines the requirement engineering process and discusses common challenges like the "yes, but" syndrome where users provide additional feedback, and the "undiscovered ruins" syndrome where further requirements are uncovered. It provides examples of techniques to elicit requirements like interviewing stakeholders, workshops, brainstorming, storyboarding, use cases, and prototyping.
Lecture4 requirement engineering
This document discusses requirement engineering and techniques for requirements elicitation. It defines requirements and describes the different levels of requirements from business to functional to non-functional. The key techniques discussed for eliciting requirements include interviewing stakeholders, holding requirements workshops, brainstorming with users, creating storyboards and use cases, and building prototypes. Prototyping in particular is highlighted as an effective way to address common issues in requirements elicitation like the "yes, but" syndrome and discovering additional undisclosed needs.
How to improve Developer Documentations ?
The document proposes solutions to improve the Teams Dev Docs by addressing developer pain points. It identifies key pain points such as difficulty finding relevant content and understanding errors. Possible solutions include a chatbot that can quickly answer questions and documentation that allows coding in native languages. User research is cited to validate the identified pain points. A phased go-to-market strategy is proposed starting with targeted launches of the chatbot and native language support to capture early adopters. The solutions aim to reduce time spent on documentation and increase new developer adoption.
The biggest DevOps problems you didn't know you had and what to do about them
Slide deck from www.ReleaseIQ.io webinar on August 25, 2021. Learn about the biggest problems DevOps teams face. You might be surprised what keeps DevOps teams stuck in mid-evolution.
Concept Presentation
The document discusses testing a prototype for an online dictionary website. It describes the goal of allowing users to create accounts, save words to personal lexicons, and tag words. It then provides sample test questions to evaluate usability, such as how a user would log in, look up a word they previously saved, and save/tag a new word. Next, it lists heuristics for user interface design, such as maintaining visibility of system status, using natural language, allowing user control and undo/redo, consistency, and preventing errors.
Free (like a puppy) Web Tools for Nonprofits
The document discusses different types of "free" software options for non-profits, including open source software, freemium software, donations, and pro bono work, and notes that while the software itself may be free, there are often hidden costs associated with implementation, customization, support, upgrades, and ongoing maintenance that organizations should be aware of and plan for. It provides advice on evaluating options, understanding limitations and responsibilities, defining requirements, and developing a technology plan to successfully adopt new software solutions.
Using Technology to Enhance Events
The document discusses various technologies that can be used to enhance events, including blogs, podcasts, RSS feeds, social media, wikis, and more. It provides examples of how each technology could be used and highlights benefits like reaching a global audience, engaging people, and increasing productivity. The document also emphasizes understanding audiences, writing clearly for the web, establishing trust, and creating a strategic plan for adopting technologies.
The role of user services in 21st century
Academic libraries in the 21st century must learn to adapt to ever-changing technology and user requirements. Service is the key term - if users are unhappy with service, they will go elsewhere.
Foss Support Webinar0108
The document discusses various models of support for open source software (FOSS), including paid support options as well as community-based support. It outlines different types of community support like mailing lists, forums, and IRC channels. The key benefits of community support are its low cost and ability to provide quick answers from a diverse set of users. However, community support can be unpredictable in terms of response times and whether issues get resolved. The document encourages becoming involved in FOSS communities by contributing answers and code in order to receive more support in return.
Foss Support Webinar0108
The document discusses various models of support for open source software (FOSS), including paid support options as well as community-based support. It outlines different types of community support like mailing lists, forums, and IRC channels. The key benefits of community support are its low cost and ability to provide quick answers from a diverse set of users. However, community support can be unpredictable in terms of response time and whether issues get resolved. The document encourages becoming involved in FOSS communities by contributing answers and code in order to receive more support in return.
Introducing Crowdoscope
An outline of Crowdoscope, a new interactive survey and discussion tool for collecting real-time Collective Intelligence.
Open Source: What is It?
A discussion of the advantages, risks, and rewards of Open Source by Jonathan Markow, DuraSpace.
Presented June 2, 2011
Similar to Supporting Software (20)
Coordinating Documentation and Support: Turning Complaints into Contributions
Coordinating Documentation and Support: Turning Complaints into Contributions
Adopting Open Source Software for Longer-term Reuse
Adopting Open Source Software for Longer-term Reuse
Why Good Software Sometimes Dies... and how to save it
Why Good Software Sometimes Dies... and how to save it
How to Effectively Lead Focus Groups: Presented at ProductTank Toronto
How to Effectively Lead Focus Groups: Presented at ProductTank Toronto
The biggest DevOps problems you didn't know you had and what to do about them
The biggest DevOps problems you didn't know you had and what to do about them
More from Software Sustainability Institute
SPOTonLondon Data
Introduction from Neil Chue Hong, Director of the Software Sustainability Institute for session on "Publishing Research Data: What’s in it for me?" at Science, Policy, Outreach and Tools Online.
Collaborations Workshop Lightning Talks
These are the combined slides from the lightning talks sessions at the Collaborations Workshop 2012. For speaker information, see: http://www.software.ac.uk/cw12/cw12-topics-lightning-talks
How breakouts work
The document provides instructions for conducting breakout sessions, which include choosing a Chair and Scribe in the first 5 minutes to lead discussion on lessons learned, problems and solutions, further work needed, and resources. In the last 10 minutes, the Scribe distills the group's notes using a template, and the group chooses a presenter to report the results to the larger group via email.
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...Software Sustainability Institute
Neil Chue Hong's introduction to the Software Sustainability Institute, presented at the Collaborations Workshop 2012.Digital Social Research
David De Roure's introduction to the Digital Social Research project presented at the Collaborations Workshop 2012.
Sustainability Training Workshop - Intro to the SSI
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
Planning your project
Planning is essential for any project that produces software, even if it is research-oriented. Development plans should be detailed enough to provide guidance but not constrain the project. The plan should be useful to the project team and use tools that work best for the individuals involved. The plan should set regular milestones to release work in progress and review progress without locking in scope too early. A product-based approach to planning breaks work down into components that can be estimated, and the plan should include testing, integration, documentation, and release tasks.
More from Software Sustainability Institute (7)
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Sustainability Training Workshop - Intro to the SSI
Sustainability Training Workshop - Intro to the SSI
Recently uploaded
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Gursev Pirge, PhD
Senior Data Scientist - JohnSnowLabs
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
A Deep Dive into ScyllaDB's Architecture
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
What is an RPA CoE? Session 2 – CoE Roles
In this session, we will review the players involved in the CoE and how each role impacts opportunities.
Topics covered:
• What roles are essential?
• What place in the automation journey does each role play?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Demystifying Knowledge Management through Storytelling
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Day 2 - Intro to UiPath Studio Fundamentals
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
High performance Serverless Java on AWS- GoTo Amsterdam 2024
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Recently uploaded (20)
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
Poznań ACE event - 19.06.2024 Team 24 Wrapup slidedeck
Poznań ACE event - 19.06.2024 Team 24 Wrapup slidedeck
Demystifying Knowledge Management through Storytelling
Demystifying Knowledge Management through Storytelling
High performance Serverless Java on AWS- GoTo Amsterdam 2024
High performance Serverless Java on AWS- GoTo Amsterdam 2024
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Supporting Software
- 2. What users like to know What the software does How to use the software What help resources are available Where to ask for help and That their request was heard! Support will not disappear!
- 3. Tried-and-tested E-mail list Help users Help users help each other Public archive Understand issue context Proactive support
- 4. Alternative avenues FAQ Advisories How-tos and tutorials Features, bugs and issues tracker Public repository Intermediate code drops Support events Chat room
- 5. Be honest Quality of Service “We’ll reply to all e-mails within 24 hours” “We’ll reply on a best-effort basis” Scope of Service “We won’t support releases built by users from our repository” “We’ll only support use on recommended platforms/using recommended dependent components” Types of Service “Develop tailored solutions to complex issues” “Specific issue resolution only”