How to be a successful Agile tester. The presentation is about breaking barriers, giving a realistic picture of what is expected from testers in Agile Age!
This presentation explains the three layer API design which organisations can use to get most out of there systems with less development and maintenance time spent on fixing issues as a whole in org.
To view recording of this webinar please use below URL:
http://wso2.com/library/webinars/2015/09/event-driven-architecture/
Enterprise systems today are moving towards being dynamic where change has become the norm rather than the exception. Such systems need to be loosely coupled, autonomous, versatile and adaptive. There arises the need to model such systems, and event driven architecture (EDA) is how such systems can be modelled and explained.
This webinar will discuss
The basics of EDA
How it can benefit your enterprise
How the WSO2 product stack complements this architectural pattern
Your Challenge
Even though organizations are now planning for Application Integration (AI) in their projects, very few have developed a holistic approach to their integration problems resulting in each project deploying different tactical solutions.
Point-to-point and ad hoc integration solutions won’t cut it anymore: the cloud, big data, mobile, social, and new regulations require more sophisticated integration tooling.
Loosely defined AI strategies result in point solutions, overlaps in technology capabilities, and increased maintenance costs; the correlation between business drivers and technical solutions is lost.
Our Advice
Critical Insight
Involving the business in strategy development will keep them engaged and align business drivers with technical initiatives.
An architectural approach to AI strategy is critical to making appropriate technology decisions and promoting consistency across AI solutions through the use of common patterns.
Get control of your AI environment with an appropriate architecture, including policies and procedures, before end users start adding bring-your-own-integration (BYOI) capabilities to the office.
The data architecture of solutions is frequently not given the attention it deserves or needs. Frequently, too little attention is paid to designing and specifying the data architecture within individual solutions and their constituent components. This is due to the behaviours of both solution architects ad data architects.
Solution architecture tends to concern itself with functional, technology and software components of the solution
Data architecture tends not to get involved with the data aspects of technology solutions, leaving a data architecture gap. Combined with the gap where data architecture tends not to get involved with the data aspects of technology solutions, there is also frequently a solution architecture data gap. Solution architecture also frequently omits the detail of data aspects of solutions leading to a solution data architecture gap. These gaps result in a data blind spot for the organisation.
Data architecture tends to concern itself with post-individual solutions. Data architecture needs to shift left into the domain of solutions and their data and more actively engage with the data dimensions of individual solutions. Data architecture can provide the lead in sealing these data gaps through a shift-left of its scope and activities as well providing standards and common data tooling for solution data architecture
The objective of data design for solutions is the same as that for overall solution design:
• To capture sufficient information to enable the solution design to be implemented
• To unambiguously define the data requirements of the solution and to confirm and agree those requirements with the target solution consumers
• To ensure that the implemented solution meets the requirements of the solution consumers and that no deviations have taken place during the solution implementation journey
Solution data architecture avoids problems with solution operation and use:
• Poor and inconsistent data quality
• Poor performance, throughput, response times and scalability
• Poorly designed data structures can lead to long data update times leading to long response times, affecting solution usability, loss of productivity and transaction abandonment
• Poor reporting and analysis
• Poor data integration
• Poor solution serviceability and maintainability
• Manual workarounds for data integration, data extract for reporting and analysis
Data-design-related solution problems frequently become evident and manifest themselves only after the solution goes live. The benefits of solution data architecture are not always evident initially.
This presentation explains the three layer API design which organisations can use to get most out of there systems with less development and maintenance time spent on fixing issues as a whole in org.
To view recording of this webinar please use below URL:
http://wso2.com/library/webinars/2015/09/event-driven-architecture/
Enterprise systems today are moving towards being dynamic where change has become the norm rather than the exception. Such systems need to be loosely coupled, autonomous, versatile and adaptive. There arises the need to model such systems, and event driven architecture (EDA) is how such systems can be modelled and explained.
This webinar will discuss
The basics of EDA
How it can benefit your enterprise
How the WSO2 product stack complements this architectural pattern
Your Challenge
Even though organizations are now planning for Application Integration (AI) in their projects, very few have developed a holistic approach to their integration problems resulting in each project deploying different tactical solutions.
Point-to-point and ad hoc integration solutions won’t cut it anymore: the cloud, big data, mobile, social, and new regulations require more sophisticated integration tooling.
Loosely defined AI strategies result in point solutions, overlaps in technology capabilities, and increased maintenance costs; the correlation between business drivers and technical solutions is lost.
Our Advice
Critical Insight
Involving the business in strategy development will keep them engaged and align business drivers with technical initiatives.
An architectural approach to AI strategy is critical to making appropriate technology decisions and promoting consistency across AI solutions through the use of common patterns.
Get control of your AI environment with an appropriate architecture, including policies and procedures, before end users start adding bring-your-own-integration (BYOI) capabilities to the office.
The data architecture of solutions is frequently not given the attention it deserves or needs. Frequently, too little attention is paid to designing and specifying the data architecture within individual solutions and their constituent components. This is due to the behaviours of both solution architects ad data architects.
Solution architecture tends to concern itself with functional, technology and software components of the solution
Data architecture tends not to get involved with the data aspects of technology solutions, leaving a data architecture gap. Combined with the gap where data architecture tends not to get involved with the data aspects of technology solutions, there is also frequently a solution architecture data gap. Solution architecture also frequently omits the detail of data aspects of solutions leading to a solution data architecture gap. These gaps result in a data blind spot for the organisation.
Data architecture tends to concern itself with post-individual solutions. Data architecture needs to shift left into the domain of solutions and their data and more actively engage with the data dimensions of individual solutions. Data architecture can provide the lead in sealing these data gaps through a shift-left of its scope and activities as well providing standards and common data tooling for solution data architecture
The objective of data design for solutions is the same as that for overall solution design:
• To capture sufficient information to enable the solution design to be implemented
• To unambiguously define the data requirements of the solution and to confirm and agree those requirements with the target solution consumers
• To ensure that the implemented solution meets the requirements of the solution consumers and that no deviations have taken place during the solution implementation journey
Solution data architecture avoids problems with solution operation and use:
• Poor and inconsistent data quality
• Poor performance, throughput, response times and scalability
• Poorly designed data structures can lead to long data update times leading to long response times, affecting solution usability, loss of productivity and transaction abandonment
• Poor reporting and analysis
• Poor data integration
• Poor solution serviceability and maintainability
• Manual workarounds for data integration, data extract for reporting and analysis
Data-design-related solution problems frequently become evident and manifest themselves only after the solution goes live. The benefits of solution data architecture are not always evident initially.
IT Architecture’s Role In Solving Technical Debt.pdfAlan McSweeney
Technical debt is an overworked term without an effective and common agreed understanding of what exactly it is, what causes it, what are its consequences, how to assess it and what to do about it.
Technical debt is the sum of additional direct and indirect implementation and operational costs incurred and risks and vulnerabilities created because of sub-optimal solution design and delivery decisions.
Technical debt is the sum of all the consequences of all the circumventions, budget reduction, time pressure, lack of knowledge, manual workarounds, short-cuts, avoidance, poor design and delivery quality and decisions to remove elements from solution scope and failure to provide foundational and backbone solution infrastructure.
Technical debt leads to a negative feedback cycle with short solution lifespan, earlier solution replacement and short-term tactical remedial actions.
All the disciplines within IT architecture have a role to play in promoting an understanding of and in the identification of how to resolve technical debt. IT architecture can provide the leadership in both remediating existing technical debt and preventing future debt.
Failing to take a complete view of the technical debt within the organisation means problems and risks remained unrecognised and unaddressed. The real scope of the problem is substantially underestimated. Technical debt is always much more than poorly written software.
Technical debt can introduce security risks and vulnerabilities into the organisation’s solution landscape. Failure to address technical debt leaves exploitable security risks and vulnerabilities in place.
Shadow IT or ghost IT is a largely unrecognised source of technical debt including security risks and vulnerabilities. Shadow IT is the consequence of a set of reactions by business functions to an actual or perceived inability or unwillingness of the IT function to respond to business needs for IT solutions. Shadow IT is frequently needed to make up for gaps in core business solutions, supplementing incomplete solutions and providing omitted functionality.
Lecture 1: Introduction. The full teaching pack with 19 lectures, tests and other materials based on the book "The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment", which can be freely used for teaching purposes, adapted or translated with references to the original, is available on request to the author (visit http://kotusev.com)
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.
Integration Patterns and Anti-Patterns for Microservices ArchitecturesApcera
Integration Patterns and Anti-Patterns for Microservices Architectures
David Williams
Co-Founder and Partner, Williams Garcia
You can learn more about NATS at http://www.nats.io
Product Lifecycle Management (PLM) has many definitions, but do they really look at all the needs across the lifecycle? Are the commonly listed domains (Systems Engineering, Program Management, Product Design, Process Management for Manufacturing and Product Data Management) enough? This webinar helps define PLM in more depth and applies model-based systems engineering (MBSE) techniques and tools to show how to improve your PLM practice. It will include a demonstration of how Innoslate meets and exceeds the requirements for a PLM tool.
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.
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
Using Network balancer, we were able to limit the available network bandwidth according to our requirements and thus allowing us to test the application performance in a more realistic network situation. The stake holders were able to analyze the application stability under more real time situations.
IT Architecture’s Role In Solving Technical Debt.pdfAlan McSweeney
Technical debt is an overworked term without an effective and common agreed understanding of what exactly it is, what causes it, what are its consequences, how to assess it and what to do about it.
Technical debt is the sum of additional direct and indirect implementation and operational costs incurred and risks and vulnerabilities created because of sub-optimal solution design and delivery decisions.
Technical debt is the sum of all the consequences of all the circumventions, budget reduction, time pressure, lack of knowledge, manual workarounds, short-cuts, avoidance, poor design and delivery quality and decisions to remove elements from solution scope and failure to provide foundational and backbone solution infrastructure.
Technical debt leads to a negative feedback cycle with short solution lifespan, earlier solution replacement and short-term tactical remedial actions.
All the disciplines within IT architecture have a role to play in promoting an understanding of and in the identification of how to resolve technical debt. IT architecture can provide the leadership in both remediating existing technical debt and preventing future debt.
Failing to take a complete view of the technical debt within the organisation means problems and risks remained unrecognised and unaddressed. The real scope of the problem is substantially underestimated. Technical debt is always much more than poorly written software.
Technical debt can introduce security risks and vulnerabilities into the organisation’s solution landscape. Failure to address technical debt leaves exploitable security risks and vulnerabilities in place.
Shadow IT or ghost IT is a largely unrecognised source of technical debt including security risks and vulnerabilities. Shadow IT is the consequence of a set of reactions by business functions to an actual or perceived inability or unwillingness of the IT function to respond to business needs for IT solutions. Shadow IT is frequently needed to make up for gaps in core business solutions, supplementing incomplete solutions and providing omitted functionality.
Lecture 1: Introduction. The full teaching pack with 19 lectures, tests and other materials based on the book "The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment", which can be freely used for teaching purposes, adapted or translated with references to the original, is available on request to the author (visit http://kotusev.com)
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.
Integration Patterns and Anti-Patterns for Microservices ArchitecturesApcera
Integration Patterns and Anti-Patterns for Microservices Architectures
David Williams
Co-Founder and Partner, Williams Garcia
You can learn more about NATS at http://www.nats.io
Product Lifecycle Management (PLM) has many definitions, but do they really look at all the needs across the lifecycle? Are the commonly listed domains (Systems Engineering, Program Management, Product Design, Process Management for Manufacturing and Product Data Management) enough? This webinar helps define PLM in more depth and applies model-based systems engineering (MBSE) techniques and tools to show how to improve your PLM practice. It will include a demonstration of how Innoslate meets and exceeds the requirements for a PLM tool.
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.
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
Using Network balancer, we were able to limit the available network bandwidth according to our requirements and thus allowing us to test the application performance in a more realistic network situation. The stake holders were able to analyze the application stability under more real time situations.
By using the tools like Selenium webdriver using testing data driven framework was very robust for functional automation of web interface. This helped to perform regression testing in very short span of time. All the requirements of the client was fulfilled, trust and relationship between the client and us was strengthened.
By implementing scripts in such a way that each script first sets up pre-requisite data and completes execution, we were able to lessen the time for script execution. Jenkins CI tool was set up so that all the scripts are executed automatically and execution result was shared via email after script execution.
For informative discussions on software testing please see. http://forum.360logica.com/
Please see description below
A leader in Software Testing Services and Quality Assurance, 360logica Software Testing Company offers high end software testing program and test solutions to Independent Software Vendors (ISVs), Software product companies and SME's. 360logica is a company propelled by a team of bright, efficient & committed individuals, having acquired their professional acumen from India’s premier technological institutes. We are based in National Capital Region of India having sales offices in California and Florida. We have built strong practices and cover industry verticals like financial applications testing services, mobile software and applications testing, selenium automation testing, healthcare testing, functional automation, SCM, network security testing, E-commerce application testing, manufacturing and retail software testing.
Working with the client, 360Logica Testing Services was able to perform successful Performance testing session before going live. In addition, also achieved better performance when load and stress increased. Overall this was a time and cost saving activity for the client, performed by an offshore team. 360logica endeavors to provide the best possible and highest quality of QA consulting and independent software testing services at cost-effective price.
With a successful performance of Regression Testing, product delivered to the client was of extreme quality and designed as per the requirement. Using tools like SoapUI helped in functional testing and understanding of APIs. 360logica endeavors to provide the best possible and highest quality of QA consulting and independent software testing services at cost-effective price.
At some stage or other, a business enterprise feels the need to implement QA processes to standardize their operations, product delivery, and empower business solutions. Maintaining a full-fledged QA standard process is vital for a product-based environment. If a given QA standard is followed in a proper way, it leads to well-defined, user-oriented, and quality products.
Our client wanted a dedicated team with 12*7 support to keep them up-to-date with an hourly status of the articles published on their blog by various staff members and independent contributors associated with different channels and finance websites to ensure everything is functioning smoothly. We successfully fulfilled all their requirements and by providing every minute update when required we helped the client to be attentive for any hidden errors.
Working with the client, 360Logica Testing Services was able to give the best possible solution for Functional testing with tools like JIRA & Zephyr for JIRA that proved very beneficial to the client in mapping of requirements to Test cases and defects. Involvement in Root Cause Analysis helped team in understanding the common issues on production environment and decreased the issues over a period of time. Multiple review cycles assured that there was no requirement miss for testing. This further helped in reducing production issues, which needed patch releases, saving both time and money for the client.
Case study for agile software development: Joe Crespo
How Agile (Scrum) is working for our team. Take a look at our methodology, how we're organizing the project, how we're approaching the 4 ceremonies, and how our practice might work for you.
Required to work on Budgeting and Forecasting project where there is a short release cycle of 2-3 months we created multiple review cycles that assured that there was no requirement miss for testing. This further helped in reducing production issues, which needed patch releases, saving both time and cost for the client.
This is a case study of an user acceptace testing done for a large Global bank for Finacle 10.x; Finacle is a universal banking system from Infosys Technologies . Retail, corporate and other subsystems tested.
This session is dedicated to the possibility that we can apply the work of Nicholas Taleb, author of Antifragile, to business. Thinking this through is hard work because it requires the ability to take a difficult and abstract concept (antifragility) and apply to the hard ideas of business. If you enjoy abstract (in other words, way out of the box) thinking, please join in this panel conversation led by Ed Kless, Sage senior director of partner development and strategy.
Test Automation Strategies for the Agile WorldTechWell
With the adoption of agile practices in many organizations, the test automation landscape has changed. Bob Galen explores current disruptors to traditional automation strategies, and discusses relevant and current adjustments you need to make when developing your automation business case. Open source tools are becoming incredibly viable and beat their commercial equivalents in many ways―not only in cost, but also in functionality, creativity, evolutionary speed, and developer acceptance. Agile methods have fundamentally challenged our traditional automation strategies. Now we must keep up with incremental and emergent systems and architectures and their high rates of change. Bob explores new automation strategies, examining strategies for both greenfield applications and those pesky legacy projects. Learn how to wrap a business case and communication plan around them so you get the support you need. Leave the workshop with a serious game-plan for delivering on the promise of agile test automation.
Org life cycle management - Empowering managementCloud Analogy
It is essential for an Admin to keep in mind that no changes are done entirely in the production even if the change is for assigning permissions. One should test first in developer edition or sandboxes. Let’s have a look at what are the Things to do for admin:
Learn standard features
Every admin should have the good knowledge of all the standard features which are provided by Salesforce. It will help you work more efficiently and quickly.
Don’t reinvent the wheel
Experimenting new things is always good but not in this case. If the feature is already present in Salesforce then why to work hard building the same again.
Deliver excellence
The primary focus should always be to deliver the project as the end client demanded it. There should not be any loopholes. Thorough testing is very much necessary before delivering.
Focus on the HOW
Avoid starting working as soon as you get requirement. There is always a chance that you will be messily finishing things. First, figure out what needs to be done and whether you know how this can be done.
Keep business focused on underlying WHY
It is very much necessary to know that why this needs to be done.
Software Test Engineering - A guide to becoming successful testerAsim Kazmi
An slide deck for advising modern day software test engineering individuals on how to train your self to stay above the competition. Testing is not just automation or conformance with the requirements. Its much more than that and practicing the mentioned traits will help become a top notch testing professional.
Test Automation in Agile: A Successful ImplementationTechWell
Many teams feel that they are forced to make an either/or decision when it comes to investing time to automate tests versus executing them manually. Sometimes a “silver bullet” tool is purchased, and testers are forced to use it when there may be a better option; other times unskilled team members are designated the automation engineers; and often there is a lack of good guidance on what to automate. These pitfalls cause product owners to de-prioritize those tasks when there’s a better way. Melissa Tondi shares how test teams should evaluate automated tools, both open source and commercial; areas to be aware of when traditional manual testers transition to automation engineers; and recommended priorities for automating tests. By streamlining automation tasks in your project and incorporating these recommendations, you’ll find that your automation intersection becomes a clearly marked thruway to a successfully released product.
Agile is just a fad. Don't adopt agile because the world is. Adopt agile if it solves your problem. For which you need to know your real problems.
When you are new follow them as-is. But don't stay new too long.
Question everything. See beyond methodologies and manifestos. These are not perfect. There is scope of improvement in them too. Challenge them. Seek beyond and deeper.
Best of luck!
Discover the fundamentals of Agile Quality Engineering. This webinar will explore the intersection of Agile Mindset, various Agile and quality engineering practices. Rather than a presentation of buzz words, the session will attempt to facilitate a inner conversation and equip the participants with the awareness of agility and Innovation Games to face the upcoming challenge of Agile Quality Engineering.
Topics include:
- What is Agile Quality Engineering
- Agile Mindsets and Being Lean
- Agile Quality Engineer's Value Proposition
- Value Driven Quality and Scrum
- Test Automation, Continuous Integration & Continuous Deployment
- Testing Effort "illities"
- TDD, BDD & Exploratory Testing
- Foundation of sustainable Agile Quality Engineering
Presentation for Mile High PMI Workshop on November 15, 2008
Abstract:
There are always people who want agile projects to fail. This will probably be the case until agile is the preferred process methodology used for projects. Are you one of them? In this workshop Bob Hartman will give participants a how-to guide for causing agile process failure. Attendees will learn various failure modes and how to cause them. There will be group discussions and exercises exploring how the failure modes can manifest themselves in real projects. At the end of this workshop each attendee should have the ability to cause agile project failure in a variety of ways and under a variety of conditions.
Obviously the first paragraph is a bit tongue-in-cheek. Hopefully project managers do not want agile projects to fail, but they need to know how they could fail. This knowledge will translate into an ability to recognize the failure modes and take corrective action. Interestingly, many of the agile project failure modes are also failure modes in other project process methodologies. All project managers on agile projects or in organizations that are considering using an agile process should attend this workshop. Project managers in organizations which typically struggle with projects may also gain insight into their project failure modes.
• How Software Development Methodologies may increase the security level
• Detecting and handling vulnerabilities in dependencies in a pragmatic way
• High-level principles that ~always increase the security level
-Microsoft Security Development Lifecycle practices
-What is Dev SecOps
-Static and Dynamic Application Security Testing
Similar to Testing in Agile - A success story! (20)
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Hivelance Technology
Cryptocurrency trading bots are computer programs designed to automate buying, selling, and managing cryptocurrency transactions. These bots utilize advanced algorithms and machine learning techniques to analyze market data, identify trading opportunities, and execute trades on behalf of their users. By automating the decision-making process, crypto trading bots can react to market changes faster than human traders
Hivelance, a leading provider of cryptocurrency trading bot development services, stands out as the premier choice for crypto traders and developers. Hivelance boasts a team of seasoned cryptocurrency experts and software engineers who deeply understand the crypto market and the latest trends in automated trading, Hivelance leverages the latest technologies and tools in the industry, including advanced AI and machine learning algorithms, to create highly efficient and adaptable crypto trading bots
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Advanced Flow Concepts Every Developer Should KnowPeter Caitens
Tim Combridge from Sensible Giraffe and Salesforce Ben presents some important tips that all developers should know when dealing with Flows in Salesforce.
2. “
Simple can be harder than complex: You
have to work hard to get your thinking
clean to make it simple.
But its worth it in the end because once
you get there, you can move
mountains.
Steve Jobs
3. Hello!I am Asim Kazmi
◇I am here because I love to share ideas, meet
new people and above all improve the state of
software testing.
◇I am testing since 2005.
◇Currently Engaged with 10Pearls Pvt. Ltd. .
◇You can find me at:
Linked in: http://www.linkedin.com/in/arkazmi
Twitter: https://twitter.com/asimkazmi
Slide Share: www.slideshare.net/arkazmi
Blog: http://savantsark.blogspot.com/
4. Agile, What is it all
about?
- It is an umbrella term coined in 2001 at the “Snowbird”
meeting to describe a variety of methods including XP and
Scrum.
- Has its roots in iterative development.
- Emphasizes collaborative, integrated teams; frequent deliveries;
early feedback; and the ability to adapt to changing business
needs.
1
5. Agenda
◇ What the industry needs
◇ Test Planning and Execution: The Agile way
◇ What Managers are looking for
◇ Test for User Experience
◇ Closing
6. Trained
Testers◇ Industry is looking for
bright, smart quick and
analytical thinkers.
◇ Wear multiple hats at the
same time.
◇ Match expectations with
the delivered product.
7. ◇Session Based Test Management
◇Scenario Based Execution
◇Risk-based Focus
◇Context Driven Approach
Remember:
You are not Quality Police. Your Job is to test based on
acceptance criteria and help business understand risks.
Test Planning &
Execution
10. What is this
guy looking
for?
◇ A person who understand what is important.
◇ Some one who can help him identifying the risks early.
◇ A well equipped and technically sound confidante.
◇ A pragmatic and meticulous individual.
13. 95% Passing Tests….
Quality Product!
Bug Numbers do not
count as much as the
QUALITY of bugs found!
Total Bugs: 300 – High Severity: 230 – Functional Anomalies: 200 – User Experience Problems:
100
15. ◇ Remember to test your applications on all devices
and variants where customer wants it.
◇Learn design principles of every device.
◇ Think from an End-User Perspective!
UX is Key
17. Lets Recap…
◇ Be Smart, Be equipped, be adaptive and Keep
Learning!
◇ Plan for shorter, valuable test cycles
◇ Test Early and test often!
◇ Automate Smoke and Regression Tests!
◇ Think quality not the numbers.
◇ Keep an eye on User Experience
19. Credits
Special thanks to all the people who made and released
these awesome resources and ideas for free:
◇ Presentation template by SlidesCarnival
◇ Photographs by Unsplash by Getty Images
◇ Elisabeth Hendrickson
◇ Lisa Crispin
◇ James Bach
◇ Michael Bolton
◇ And Many Others!