Vision talk on artificial intelligence techniques in requirements engineering gave at the RE@40 seminar on April 25, 2017 in Kappel am Albis, Switzerland.
The document discusses various approaches to software design, including skipping design phases and starting coding immediately (the programmer's approach) versus completing all analysis and design using UML diagrams before writing any code (the architect's approach). It also discusses principles of software design like separation of concerns, information hiding, high cohesion, low coupling, and SOLID principles. The document advocates designing software using the IDEAL CHALK principles: program to interfaces, follow the DRY principle, encapsulate what varies, depend on abstractions, apply the least knowledge principle, favor composition over inheritance, follow the Hollywood principle, apply design patterns, and strive for loosely coupled systems.
This document discusses dumb software development methodologies used by incompetent managers. It identifies 12 problematic methodologies: Development by Crisis, Not Allowed To Do Development, Budget Driven Development, Axxhole Driven Development, Client Wants It Anyway, Completely Redundant Application Process, Just One More Feature Outside Schedule, Document Driven Development, Next Shiny Thing Development, Everything is High Priority, I Wish I Was Somewhere Else mode, and concludes by calling to eliminate unprofessional practices from the software industry.
From Human Intelligence to Machine IntelligenceNUS-ISS
This in an introductory talk to get ready for the AI era, and will talk about human intelligence, the model view of intelligence and machine/artificial intelligence. There will be some coverage of AI roots and subfields.
Joel Spolsky "Joel Spolsky on Hiring Great Tech Talent"Talent42
The document discusses differences between recruiters and programmers and what programmers look for in a workplace. It notes that recruiters enjoy ambiguity, competition, and commissions, while programmers prefer predictable environments where they can focus without distractions. Programmers want pleasant workspaces with good equipment and independence, as well as engineering quality, working on products they identify with, and learning opportunities at smart organizations where their boss and teammates are also programmers.
Developing Open Source MDE Tools / Eclipse Stories and Lessons Learned - OSS4...Hugo Bruneliere
The document discusses different approaches for developing open source modeling tools, including developing tools independently, through collaborative projects, and through industrial partnerships. It outlines pros and cons of each approach and provides examples of tools developed using each approach. Key lessons learned include choosing an open source license, integrating with an active community, following a structured development process, relying on a reference framework, and getting support from one's host institution. The document advocates that there is no single best approach and that the approach depends on the specific context.
Open Source Applications For Designer Developed E LearningJared Palmer
Highlighting the available options for Instructional Designers with the technical aptitude to use open-source applications to translate their effective designs into eLearning.
Software development methodologies of dumb and cunningNalaka Gamage
This document discusses dumb software development methodologies used by incompetent managers. It identifies 12 problematic methodologies: Development by Crisis, Not Allowed To Do Development, Budget Driven Development, Axxhole Driven Development, Client Wants It Anyway, Completely Redundant Application Process, Just One More Feature Outside Schedule, Document Driven Development, Next Shiny Thing Development, Everything is High Priority, I Wish I Was Somewhere Else mode, and concludes by calling to eliminate unprofessional practices from the software industry.
The document provides tips on how recruiters can better manage hiring managers during the candidate matching and selection process. It suggests recruiters identify the hiring manager's needs, search for suitable candidates using the right keywords, and pitch candidate profiles that align with the roles while also highlighting potential alternative fits. The document also discusses common challenges faced by both candidates and hiring managers to provide context around expectations.
The document discusses various approaches to software design, including skipping design phases and starting coding immediately (the programmer's approach) versus completing all analysis and design using UML diagrams before writing any code (the architect's approach). It also discusses principles of software design like separation of concerns, information hiding, high cohesion, low coupling, and SOLID principles. The document advocates designing software using the IDEAL CHALK principles: program to interfaces, follow the DRY principle, encapsulate what varies, depend on abstractions, apply the least knowledge principle, favor composition over inheritance, follow the Hollywood principle, apply design patterns, and strive for loosely coupled systems.
This document discusses dumb software development methodologies used by incompetent managers. It identifies 12 problematic methodologies: Development by Crisis, Not Allowed To Do Development, Budget Driven Development, Axxhole Driven Development, Client Wants It Anyway, Completely Redundant Application Process, Just One More Feature Outside Schedule, Document Driven Development, Next Shiny Thing Development, Everything is High Priority, I Wish I Was Somewhere Else mode, and concludes by calling to eliminate unprofessional practices from the software industry.
From Human Intelligence to Machine IntelligenceNUS-ISS
This in an introductory talk to get ready for the AI era, and will talk about human intelligence, the model view of intelligence and machine/artificial intelligence. There will be some coverage of AI roots and subfields.
Joel Spolsky "Joel Spolsky on Hiring Great Tech Talent"Talent42
The document discusses differences between recruiters and programmers and what programmers look for in a workplace. It notes that recruiters enjoy ambiguity, competition, and commissions, while programmers prefer predictable environments where they can focus without distractions. Programmers want pleasant workspaces with good equipment and independence, as well as engineering quality, working on products they identify with, and learning opportunities at smart organizations where their boss and teammates are also programmers.
Developing Open Source MDE Tools / Eclipse Stories and Lessons Learned - OSS4...Hugo Bruneliere
The document discusses different approaches for developing open source modeling tools, including developing tools independently, through collaborative projects, and through industrial partnerships. It outlines pros and cons of each approach and provides examples of tools developed using each approach. Key lessons learned include choosing an open source license, integrating with an active community, following a structured development process, relying on a reference framework, and getting support from one's host institution. The document advocates that there is no single best approach and that the approach depends on the specific context.
Open Source Applications For Designer Developed E LearningJared Palmer
Highlighting the available options for Instructional Designers with the technical aptitude to use open-source applications to translate their effective designs into eLearning.
Software development methodologies of dumb and cunningNalaka Gamage
This document discusses dumb software development methodologies used by incompetent managers. It identifies 12 problematic methodologies: Development by Crisis, Not Allowed To Do Development, Budget Driven Development, Axxhole Driven Development, Client Wants It Anyway, Completely Redundant Application Process, Just One More Feature Outside Schedule, Document Driven Development, Next Shiny Thing Development, Everything is High Priority, I Wish I Was Somewhere Else mode, and concludes by calling to eliminate unprofessional practices from the software industry.
The document provides tips on how recruiters can better manage hiring managers during the candidate matching and selection process. It suggests recruiters identify the hiring manager's needs, search for suitable candidates using the right keywords, and pitch candidate profiles that align with the roles while also highlighting potential alternative fits. The document also discusses common challenges faced by both candidates and hiring managers to provide context around expectations.
The rocket internet experience @ PHP.TO.START 2013 in TurinAlessandro Nadalin
This document outlines an agenda for building a startup team at Rocket Internet. It discusses contextualizing the work, defining responsibilities, building the team through hiring young developers and ignoring CVs, getting work started by adopting a domain-driven design approach, adapting to different situations, mutating the team and work over time, delegating responsibilities as the team grows to 12 then 150 people, and provides a bonus invitation to join the startup.
Javantura v7 - Learning to Scale Yourself: The Journey from Coder to Leader - Daniel Strmečki
Your success depends on others, a 1-man army can only achieve so much. The only way to progress from coder to leader is to learn how to scale yourself. Nowadays, you can become a Senior Developer with just a few years of experience. After that, there are many roads and possibilities you can take. Whether you decide for a developer, architect, manager or a mixed career, at one point, you will need to become a leader. In the first chapter of the lecture we will start a discussion on how to get there. Since your time is limited, you need to mentor, coach, motivate and engage others. Start with making a stable foundation, like setting up a proper onboarding process. If you help people around you, they will for sure talk about it, and your manager will hear it. Also, demonstrate ability in everyday work: coding, project management, client-focus, communication and care about others. Always stick to your values and keep high standards. In the second chapter we will discuss the challenges that turn up once you get there. At that point you will deal with people more than technology. You will need to step away from coding for meetings very often. Interruptions will happen every day and it we be very hard to maintain “the flow”. You will need to learn how to delegate and drive topics without implementing them yourself. Visit the lecture to find out some techniques for dealing with interruptions, meetings, prioritization, people and their motivation.
AgileNCR 2019 _ The Soft Side of Software Development.pptxRajaNagendraKumar1
The document discusses the importance of human factors in software engineering for modern complex systems. It covers 5 key psychological factors:
1) Attention - Developers must focus on their work and learn strategies like planning and saying no to improve focus.
2) Learning - Teams must have a learning mindset and share knowledge through practices like building junior developers and learning from first principles.
3) Teamwork - Bigger/less focused teams produce less secure code, so collaboration strategies like clear roles and psychological safety are important.
4) Decision making - Overcoming cognitive biases and using second-order thinking helps make better decisions.
5) Leadership - Regular 1:1 meetings, finding the right incentives, and
Waterfalls are great to watch... Iterative Design Thinkingnois3
But when you work on digital products working with waterfall methodologies is way too risky. Worst: you start building something on wrong assumptions and it takes forever to deliver.Either you are a big enterprise or a small startup, building great mobile products “per sé” doesn’t make any sense. You’ll always need to build them for your people.I will be presenting you the set of methods we use in nois3:Iterative Design based on multidisciplinary teams working on Jams/Sprints is fantastic to Define, Prototype, and Repeat. Adding a flavor of Data Driven UX will be your game changer to Discover.
Rethinking Object Orientation - By Kathleen Dollard
Decades after object orientation design altered programming, it’s still evolving, and we’re still learning to use it better. Many changes in the tools we use and how we write applications affect the approach we take to OOD. Some of these changes relate to architecture where approaches like SOA and the layering revolution behind Silverlight alter the place of traditional OOD within the bigger picture of architecture. Other changes are language improvements that alter the very meaning of the phrase “object” from a design point of view. Language features that alter our implementation of logical objects include generics, extension methods, delegates/lambda expressions, partial classes/methods, reflection, anonymous types, and declarative programming.
We’ll also explore the growing role of interfaces as a contractual base in composable applications and explore differences between traditional applications and ecosystem empowering applications. I’m really excited to give this talk to a group with diverse skillsets! Come ready for multi-way conversations because I want to learn from you.
Everyone seems to have an intuitive understanding of ‘architecture’ as the process and product of planning, designing, and constructing. The problem is most people don’t have the same understanding which leads to disagreements about what the process and product entails. The transition from software shipped on physical media to software delivered as services further complicated the conversation as operating services introduces other factors that must be considered on an ongoing basis. These misunderstandings have only been exacerbated as greater speed and scale create new problems necessitating novel emergent solutions. This presentation will attempt to highlight the need for new language with dense semantics about the emerging architectures (because just saying ‘microservices’ is causing more problems than it solves) while also pointing out that many of the struggles people have delivering software are rooted in architecture.
This document provides advice and recommendations from an expert on various topics related to web development and Drupal. Some of the key points covered include:
- Testing, especially automated testing, is very important for quality assurance and maintaining reliability. Simplicity is also important for reliability.
- Small teams and clients are preferable to large ones, as they have less bureaucracy, noise and agendas interfering with objectives.
- Planning is essential, especially software architecture planning, but plans will change over time as the project evolves.
- Tools like Ansible, PHPQA tools, Robo, and JetBrains PHPStorm can help with tasks like provisioning, testing, deployment and development. Drupal tools like Drush
Usability in Virtual Worlds (Metaverse08)Markus Breuer
This document discusses usability in virtual worlds and provides recommendations for improving usability based on user-centered design principles. It summarizes challenges with current usability in virtual worlds and provides examples of poor usability. The document recommends using user interviews, personas, scenarios and iterative user testing to understand users and improve designs. Conducting user research and testing designs with target users early and often is emphasized as key to achieving better usability.
Gluing it all together: How teams can build enterprise JavaScript application...Codemotion
Should everyone write code in one language? Would you hire a team to build a house with only hammers? Companies, large ones, are trying to port huge systems to the browser. Is one language really the perfect tool for presentation and business logic?
This session disagrees with the single tool premise and discusses an approach to help companies integrate existing skills, web standards, and resources with different skills together, and still target the browser.
The document discusses various types of failures in organizations and projects, including failures due to trivial issues that receive disproportionate attention ("bikeshedding"), entrepreneurs who overpromise and underdeliver, and behavioral patterns among team members that can contribute to failure, such as passing blame and not taking responsibility for issues ("chain of irresponsibility"). Specific examples of failures are provided for projects, methodologies, and individuals to illustrate different kinds of failures and how they can be avoided or overcome through learning from mistakes.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
CWIN17 san francisco-rob vellinga - Interaction between AI and peopleCapgemini
The document discusses the history of artificial intelligence from 1936 to the present. It notes key developments like Alan Turing inventing the Turing test in 1950 and IBM's Deep Blue beating world chess champion Gary Kasparov in 1997. The document advocates for user-centered design of AI and outlines an evolution from 2D to 3D and outcome-based designs. It stresses that AI should be designed to serve people and achieve intended outcomes rather than replace humanity.
business model, business model canvas, mission model, mission model canvas, customer development, lean launchpad, lean startup, stanford, startup, steve blank, entrepreneurship, I-Corps, Stanford
Project Manager - which superpower do you have?Stoneseed Ltd
The document discusses 7 "superpowers" that project managers possess: 1) Time travel and time manipulation through efficiently managing resources and timelines, 2) Superhuman endurance in working long hours to complete projects, 3) Breathing under water by remaining calm under high stress and pressure, 4) Super night vision from late nights working, 5) Telepathy and precognition in anticipating future needs and issues, 6) Mind control through strong negotiation and communication skills, and 7) Immortality through the lasting impact and legacy of the solutions they implement. The document argues that while project managers may not have literal superpowers, they exhibit superhuman abilities in successfully delivering complex projects under demanding constraints.
Engineers tend to start most of the technology startups. While this gives them an inherent advantage as far as engineering the product goes, it also tends to put them at a disadvantage when it comes to designing (non-technically) and commercializing the product.
This slide deck takes up the key concepts from PdM that apply to startup-mode products. This is not a case for having Product Managers onboard, 80% of the startups don’t need a dedicated PM.
Towards the end, it introduces the funky concept of Product Entropy.
Oleksander Krakovetskyi "Explaining a Machine Learning blackbox"Fwdays
As Data Scientists we want to understand machine learning models we have built. “Why did my model make this mistake?”, “Does my model discriminate?”, “How can I understand and trust the model's decisions?”, “Does my model satisfy legal requirements?” are commonly asked questions.
In this presentation we will talk about machine learning explainability and interpretability - two concepts that could help us really understand ML models.
Website: https://fwdays.com/en/event/data-science-fwdays-2019/review/explaining-a-machine-learning-blackbox
Remote Sensing and Computational, Evolutionary, Supercomputing, and Intellige...University of Maribor
Slides from talk:
Aleš Zamuda: Remote Sensing and Computational, Evolutionary, Supercomputing, and Intelligent Systems.
11th International Conference on Electrical, Electronics and Computer Engineering (IcETRAN), Niš, 3-6 June 2024
Inter-Society Networking Panel GRSS/MTT-S/CIS Panel Session: Promoting Connection and Cooperation
https://www.etran.rs/2024/en/home-english/
The rocket internet experience @ PHP.TO.START 2013 in TurinAlessandro Nadalin
This document outlines an agenda for building a startup team at Rocket Internet. It discusses contextualizing the work, defining responsibilities, building the team through hiring young developers and ignoring CVs, getting work started by adopting a domain-driven design approach, adapting to different situations, mutating the team and work over time, delegating responsibilities as the team grows to 12 then 150 people, and provides a bonus invitation to join the startup.
Javantura v7 - Learning to Scale Yourself: The Journey from Coder to Leader - Daniel Strmečki
Your success depends on others, a 1-man army can only achieve so much. The only way to progress from coder to leader is to learn how to scale yourself. Nowadays, you can become a Senior Developer with just a few years of experience. After that, there are many roads and possibilities you can take. Whether you decide for a developer, architect, manager or a mixed career, at one point, you will need to become a leader. In the first chapter of the lecture we will start a discussion on how to get there. Since your time is limited, you need to mentor, coach, motivate and engage others. Start with making a stable foundation, like setting up a proper onboarding process. If you help people around you, they will for sure talk about it, and your manager will hear it. Also, demonstrate ability in everyday work: coding, project management, client-focus, communication and care about others. Always stick to your values and keep high standards. In the second chapter we will discuss the challenges that turn up once you get there. At that point you will deal with people more than technology. You will need to step away from coding for meetings very often. Interruptions will happen every day and it we be very hard to maintain “the flow”. You will need to learn how to delegate and drive topics without implementing them yourself. Visit the lecture to find out some techniques for dealing with interruptions, meetings, prioritization, people and their motivation.
AgileNCR 2019 _ The Soft Side of Software Development.pptxRajaNagendraKumar1
The document discusses the importance of human factors in software engineering for modern complex systems. It covers 5 key psychological factors:
1) Attention - Developers must focus on their work and learn strategies like planning and saying no to improve focus.
2) Learning - Teams must have a learning mindset and share knowledge through practices like building junior developers and learning from first principles.
3) Teamwork - Bigger/less focused teams produce less secure code, so collaboration strategies like clear roles and psychological safety are important.
4) Decision making - Overcoming cognitive biases and using second-order thinking helps make better decisions.
5) Leadership - Regular 1:1 meetings, finding the right incentives, and
Waterfalls are great to watch... Iterative Design Thinkingnois3
But when you work on digital products working with waterfall methodologies is way too risky. Worst: you start building something on wrong assumptions and it takes forever to deliver.Either you are a big enterprise or a small startup, building great mobile products “per sé” doesn’t make any sense. You’ll always need to build them for your people.I will be presenting you the set of methods we use in nois3:Iterative Design based on multidisciplinary teams working on Jams/Sprints is fantastic to Define, Prototype, and Repeat. Adding a flavor of Data Driven UX will be your game changer to Discover.
Rethinking Object Orientation - By Kathleen Dollard
Decades after object orientation design altered programming, it’s still evolving, and we’re still learning to use it better. Many changes in the tools we use and how we write applications affect the approach we take to OOD. Some of these changes relate to architecture where approaches like SOA and the layering revolution behind Silverlight alter the place of traditional OOD within the bigger picture of architecture. Other changes are language improvements that alter the very meaning of the phrase “object” from a design point of view. Language features that alter our implementation of logical objects include generics, extension methods, delegates/lambda expressions, partial classes/methods, reflection, anonymous types, and declarative programming.
We’ll also explore the growing role of interfaces as a contractual base in composable applications and explore differences between traditional applications and ecosystem empowering applications. I’m really excited to give this talk to a group with diverse skillsets! Come ready for multi-way conversations because I want to learn from you.
Everyone seems to have an intuitive understanding of ‘architecture’ as the process and product of planning, designing, and constructing. The problem is most people don’t have the same understanding which leads to disagreements about what the process and product entails. The transition from software shipped on physical media to software delivered as services further complicated the conversation as operating services introduces other factors that must be considered on an ongoing basis. These misunderstandings have only been exacerbated as greater speed and scale create new problems necessitating novel emergent solutions. This presentation will attempt to highlight the need for new language with dense semantics about the emerging architectures (because just saying ‘microservices’ is causing more problems than it solves) while also pointing out that many of the struggles people have delivering software are rooted in architecture.
This document provides advice and recommendations from an expert on various topics related to web development and Drupal. Some of the key points covered include:
- Testing, especially automated testing, is very important for quality assurance and maintaining reliability. Simplicity is also important for reliability.
- Small teams and clients are preferable to large ones, as they have less bureaucracy, noise and agendas interfering with objectives.
- Planning is essential, especially software architecture planning, but plans will change over time as the project evolves.
- Tools like Ansible, PHPQA tools, Robo, and JetBrains PHPStorm can help with tasks like provisioning, testing, deployment and development. Drupal tools like Drush
Usability in Virtual Worlds (Metaverse08)Markus Breuer
This document discusses usability in virtual worlds and provides recommendations for improving usability based on user-centered design principles. It summarizes challenges with current usability in virtual worlds and provides examples of poor usability. The document recommends using user interviews, personas, scenarios and iterative user testing to understand users and improve designs. Conducting user research and testing designs with target users early and often is emphasized as key to achieving better usability.
Gluing it all together: How teams can build enterprise JavaScript application...Codemotion
Should everyone write code in one language? Would you hire a team to build a house with only hammers? Companies, large ones, are trying to port huge systems to the browser. Is one language really the perfect tool for presentation and business logic?
This session disagrees with the single tool premise and discusses an approach to help companies integrate existing skills, web standards, and resources with different skills together, and still target the browser.
The document discusses various types of failures in organizations and projects, including failures due to trivial issues that receive disproportionate attention ("bikeshedding"), entrepreneurs who overpromise and underdeliver, and behavioral patterns among team members that can contribute to failure, such as passing blame and not taking responsibility for issues ("chain of irresponsibility"). Specific examples of failures are provided for projects, methodologies, and individuals to illustrate different kinds of failures and how they can be avoided or overcome through learning from mistakes.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
CWIN17 san francisco-rob vellinga - Interaction between AI and peopleCapgemini
The document discusses the history of artificial intelligence from 1936 to the present. It notes key developments like Alan Turing inventing the Turing test in 1950 and IBM's Deep Blue beating world chess champion Gary Kasparov in 1997. The document advocates for user-centered design of AI and outlines an evolution from 2D to 3D and outcome-based designs. It stresses that AI should be designed to serve people and achieve intended outcomes rather than replace humanity.
business model, business model canvas, mission model, mission model canvas, customer development, lean launchpad, lean startup, stanford, startup, steve blank, entrepreneurship, I-Corps, Stanford
Project Manager - which superpower do you have?Stoneseed Ltd
The document discusses 7 "superpowers" that project managers possess: 1) Time travel and time manipulation through efficiently managing resources and timelines, 2) Superhuman endurance in working long hours to complete projects, 3) Breathing under water by remaining calm under high stress and pressure, 4) Super night vision from late nights working, 5) Telepathy and precognition in anticipating future needs and issues, 6) Mind control through strong negotiation and communication skills, and 7) Immortality through the lasting impact and legacy of the solutions they implement. The document argues that while project managers may not have literal superpowers, they exhibit superhuman abilities in successfully delivering complex projects under demanding constraints.
Engineers tend to start most of the technology startups. While this gives them an inherent advantage as far as engineering the product goes, it also tends to put them at a disadvantage when it comes to designing (non-technically) and commercializing the product.
This slide deck takes up the key concepts from PdM that apply to startup-mode products. This is not a case for having Product Managers onboard, 80% of the startups don’t need a dedicated PM.
Towards the end, it introduces the funky concept of Product Entropy.
Oleksander Krakovetskyi "Explaining a Machine Learning blackbox"Fwdays
As Data Scientists we want to understand machine learning models we have built. “Why did my model make this mistake?”, “Does my model discriminate?”, “How can I understand and trust the model's decisions?”, “Does my model satisfy legal requirements?” are commonly asked questions.
In this presentation we will talk about machine learning explainability and interpretability - two concepts that could help us really understand ML models.
Website: https://fwdays.com/en/event/data-science-fwdays-2019/review/explaining-a-machine-learning-blackbox
Similar to The Automated Requirements Engineer: utopia or dystopia (20)
Remote Sensing and Computational, Evolutionary, Supercomputing, and Intellige...University of Maribor
Slides from talk:
Aleš Zamuda: Remote Sensing and Computational, Evolutionary, Supercomputing, and Intelligent Systems.
11th International Conference on Electrical, Electronics and Computer Engineering (IcETRAN), Niš, 3-6 June 2024
Inter-Society Networking Panel GRSS/MTT-S/CIS Panel Session: Promoting Connection and Cooperation
https://www.etran.rs/2024/en/home-english/
Or: Beyond linear.
Abstract: Equivariant neural networks are neural networks that incorporate symmetries. The nonlinear activation functions in these networks result in interesting nonlinear equivariant maps between simple representations, and motivate the key player of this talk: piecewise linear representation theory.
Disclaimer: No one is perfect, so please mind that there might be mistakes and typos.
dtubbenhauer@gmail.com
Corrected slides: dtubbenhauer.com/talks.html
Current Ms word generated power point presentation covers major details about the micronuclei test. It's significance and assays to conduct it. It is used to detect the micronuclei formation inside the cells of nearly every multicellular organism. It's formation takes place during chromosomal sepration at metaphase.
ESPP presentation to EU Waste Water Network, 4th June 2024 “EU policies driving nutrient removal and recycling
and the revised UWWTD (Urban Waste Water Treatment Directive)”
ESR spectroscopy in liquid food and beverages.pptxPRIYANKA PATEL
With increasing population, people need to rely on packaged food stuffs. Packaging of food materials requires the preservation of food. There are various methods for the treatment of food to preserve them and irradiation treatment of food is one of them. It is the most common and the most harmless method for the food preservation as it does not alter the necessary micronutrients of food materials. Although irradiated food doesn’t cause any harm to the human health but still the quality assessment of food is required to provide consumers with necessary information about the food. ESR spectroscopy is the most sophisticated way to investigate the quality of the food and the free radicals induced during the processing of the food. ESR spin trapping technique is useful for the detection of highly unstable radicals in the food. The antioxidant capability of liquid food and beverages in mainly performed by spin trapping technique.
The technology uses reclaimed CO₂ as the dyeing medium in a closed loop process. When pressurized, CO₂ becomes supercritical (SC-CO₂). In this state CO₂ has a very high solvent power, allowing the dye to dissolve easily.
Describing and Interpreting an Immersive Learning Case with the Immersion Cub...Leonel Morgado
Current descriptions of immersive learning cases are often difficult or impossible to compare. This is due to a myriad of different options on what details to include, which aspects are relevant, and on the descriptive approaches employed. Also, these aspects often combine very specific details with more general guidelines or indicate intents and rationales without clarifying their implementation. In this paper we provide a method to describe immersive learning cases that is structured to enable comparisons, yet flexible enough to allow researchers and practitioners to decide which aspects to include. This method leverages a taxonomy that classifies educational aspects at three levels (uses, practices, and strategies) and then utilizes two frameworks, the Immersive Learning Brain and the Immersion Cube, to enable a structured description and interpretation of immersive learning cases. The method is then demonstrated on a published immersive learning case on training for wind turbine maintenance using virtual reality. Applying the method results in a structured artifact, the Immersive Learning Case Sheet, that tags the case with its proximal uses, practices, and strategies, and refines the free text case description to ensure that matching details are included. This contribution is thus a case description method in support of future comparative research of immersive learning cases. We then discuss how the resulting description and interpretation can be leveraged to change immersion learning cases, by enriching them (considering low-effort changes or additions) or innovating (exploring more challenging avenues of transformation). The method holds significant promise to support better-grounded research in immersive learning.
Authoring a personal GPT for your research and practice: How we created the Q...Leonel Morgado
Thematic analysis in qualitative research is a time-consuming and systematic task, typically done using teams. Team members must ground their activities on common understandings of the major concepts underlying the thematic analysis, and define criteria for its development. However, conceptual misunderstandings, equivocations, and lack of adherence to criteria are challenges to the quality and speed of this process. Given the distributed and uncertain nature of this process, we wondered if the tasks in thematic analysis could be supported by readily available artificial intelligence chatbots. Our early efforts point to potential benefits: not just saving time in the coding process but better adherence to criteria and grounding, by increasing triangulation between humans and artificial intelligence. This tutorial will provide a description and demonstration of the process we followed, as two academic researchers, to develop a custom ChatGPT to assist with qualitative coding in the thematic data analysis process of immersive learning accounts in a survey of the academic literature: QUAL-E Immersive Learning Thematic Analysis Helper. In the hands-on time, participants will try out QUAL-E and develop their ideas for their own qualitative coding ChatGPT. Participants that have the paid ChatGPT Plus subscription can create a draft of their assistants. The organizers will provide course materials and slide deck that participants will be able to utilize to continue development of their custom GPT. The paid subscription to ChatGPT Plus is not required to participate in this workshop, just for trying out personal GPTs during it.
When I was asked to give a companion lecture in support of ‘The Philosophy of Science’ (https://shorturl.at/4pUXz) I decided not to walk through the detail of the many methodologies in order of use. Instead, I chose to employ a long standing, and ongoing, scientific development as an exemplar. And so, I chose the ever evolving story of Thermodynamics as a scientific investigation at its best.
Conducted over a period of >200 years, Thermodynamics R&D, and application, benefitted from the highest levels of professionalism, collaboration, and technical thoroughness. New layers of application, methodology, and practice were made possible by the progressive advance of technology. In turn, this has seen measurement and modelling accuracy continually improved at a micro and macro level.
Perhaps most importantly, Thermodynamics rapidly became a primary tool in the advance of applied science/engineering/technology, spanning micro-tech, to aerospace and cosmology. I can think of no better a story to illustrate the breadth of scientific methodologies and applications at their best.
The Automated Requirements Engineer: utopia or dystopia
1. The Automated Requirements Engineer:
Utopia or Dystopia?
Fabiano Dalpiaz
Requirements Engineering Lab
Department of Information and Computing Sciences
Utrecht University
RE@40 Seminar – April 25, 2017
2. Disclaimer
This talk is provocative and intended to
trigger discussion!
@2017 Fabiano Dalpiaz2
4. 1. The Automated Req. Engineer: Vision
Most of today’s RE tasks extensively rely on humans
Is that necessary?
Dan Berry (REFSQ 2012) distinguishes between
Clerical RE activities: simple, repetitive – tools may do this job
Thinking-required activities that require human analysts
@2017 Fabiano Dalpiaz4
5. 1. The Automated Req. Engineer: Vision
Most of today’s RE tasks extensively rely on humans
Is that necessary?
Dan Berry (REFSQ 2012) distinguishes between
Clerical RE activities: simple, repetitive – tools may do this job
Thinking-required activities that require human analysts
I argue for swapping the roles: from tool-assisted RE
to human-assisted RE
@2017 Fabiano Dalpiaz5
6. 1. The Automated Req. Engineer: Vision
You may already say this is a dystopic vision…
… I will try to convince you it is a utopic vision instead
@2017 Fabiano Dalpiaz6
7. 2.Traits of a Good Requirements Engineer
@2017 Fabiano Dalpiaz7
8. 2. Traits of a Good Req. Engineer
What makes a requirements engineer good?
Many characteristics, among which*
1. Competence
2. Ethicality
3. Creativity
* Disclaimers: (1) the list is very incomplete; (2) I picked traits that fit well my claims
@2017 Fabiano Dalpiaz8
9. 2. Traits of a Good Req. Engineer
Let me illustrate what I mean, rather than provide definitions
1. Competence
Can employ the most suitable elicitation techniques, has effective
social skills for negotiation etc., can turn needs into specs, …
2. Ethicality
Responsibility for actions, respect for privacy & other values, …
3. Creativity
Continuously seeking for innovation? Out-of-the-box thinking?
@2017 Fabiano Dalpiaz9
10. 2. Traits of a Good Req. Engineer
1. Competence
2. Ethicality
3. Creativity
… will the automated requirements engineer possess all
these qualities?
How and when?
@2017 Fabiano Dalpiaz10
11. 3. Realizing the vision:
where do we stand and where do we go?
@2017 Fabiano Dalpiaz11
12. 3. Realizing the vision: competence
What did the RE community
achieve so far?
NLP analysis of textual requirements
Defects, ambiguity, tacit knowledge,
extraction of models
(Semi-)automated traceability
Logic reasoning on req. models
E.g., goal model analysis, spec
verification, variants derivation
@2017 Fabiano Dalpiaz
Results on simple tasks are
quite impressive…
12
13. 3. Realizing the vision: competence
But we are in the infancy of automated reasoning.Take NLP
(from Kambria &White’s Jumping NLP Curves paper)
@2017 Fabiano Dalpiaz13
14. 3. Realizing the vision: competence
Why is this so hard? Examples
Every branch of the bank that is built on a bank shall store its
servers above the water level
From Facebook: “We analyze the content of your posts…”
Meaning: “we can” – permission
“We delete data after 15 days”
Meaning,“we must?” – obligation
Pragmatics is needed:“… because of the right-to-be-forgotten law”
@2017 Fabiano Dalpiaz
Bottom line: as per today, humans understand this way better than software
14
15. 3. Realizing the vision: ethicality
Does the requirements engineer act ethically?
Impartially
Following a code of conduct
Respecting privacy
Preventing potential software misuse
Transparently
Respecting the customers/users ethical values
@2017 Fabiano Dalpiaz15
16. 3. Realizing the vision: ethicality
Do we really trust humans for this?
Power and politics in RE (Neil Maiden)
Wouldn’t an algorithm be less biased, auditable, consistent
in its judgment?
Perhaps not a dystopia after all…
Challenges: who is held responsible for the algorithm’s decisions?
@2017 Fabiano Dalpiaz16
17. 3. Realizing the vision: creativity
Creative thinking is important in RE, we do not want just
the basic requirements!
How do we define
creativity?
Often correlated with
novelty and originality
But how many unique
ideas are there?
Can a tool look for creative
ideas by scraping the web?
@2017 Fabiano Dalpiaz17
19. 4. Conclusion and Discussion
The automated requirements engineer
Swapping roles: human-assisted RE as opposed to tool-assisted RE
Is still utopic: many years of good RE research are needed
Is perhaps not that dystopic
Depends on advances in information retrieval, machine learning,
natural language processing, …
@2017 Fabiano Dalpiaz19
20. Thanks from the Requirements
Engineering Lab at Utrecht University!
@2017 Fabiano Dalpiaz
Fabiano Dalpiaz
Sjaak Brinkkemper
F. Basak Aydemir
Sietse Overbeek
Marcela Ruiz
Garm Lucassen
GerardWagenaar
Davide dell’Anna
Govert-Jan Slob
20