SFScon19 - Riccardo Felluga Andrea Janes - Personas-Driven Approach to Test Case Generation
•
0 likes•58 views
Testing a software product is an essential part of the development process. The tests have the goal to improve/optimize defined quality attributes of the product. Unfortunately, sometimes software is developed based on the needs of a single programmer or just because a recent technology enables new product developments, and later—once a prototype is available—the question arises for whom this product might be interesting. In such cases, it is difficult to develop the appropriate requirements that best fit the needs of the final user. In this talk we describe a personas-driven testing approach, which derives personas based on an initial product idea. Based on the derived personas, we define requirements and tests to guide the further development of the product. The talk will present a case study in which we applied the method: from the initial prototype, we derive four personas that use the prototype in various ways, we extract requirements and tests.
Report
Share
Report
Share
Download to read offline
Recommended
To document or not to document? An exploratory study on developers' motivatio...
This document summarizes a study on developers' motivation to document code. Through interviews and surveys, researchers identified hindering and motivating factors for code documentation. Hindering factors included documentation being tedious, difficult, time-consuming, and interrupting coding work. Motivating factors included documentation improving code comprehensibility, order, and quality. The researchers propose designing a solution to encourage documentation by emphasizing motivating factors and mitigating hindering ones. They plan to further validate findings through a quantitative questionnaire. The goal is to increase developers' internal motivation to document code.
overview introduction to Software Engineering
Software Engineering 1 overview introduction to software engineering. First Lecture of Software engineering for BSCS , BSIT BCS MCS
Software engineering
The document discusses key lessons that can be learned from software engineering. It notes that software has become intertwined with society and addresses both functional and non-functional requirements. The document also outlines several principles of software engineering, such as rigor and formality, abstractions, separation of concerns, and modularity. It discusses the Capability Maturity Model and the evolution of software engineering approaches across different decades from the 1960s to the 2000s. Lastly, it provides recommendations for improving the software engineering process such as defining goals, separating requirements, and identifying the root causes of bugs.
Software aging
The document discusses software aging, which refers to the progressive degradation of software performance over time. It notes that software aging can occur even if the software itself is not changed, simply because needs and expectations change. The document outlines two types of aging: lack of movement, where the software is not updated to meet changing needs, and ignorant surgery, where changes are made by people who do not fully understand the software. It suggests several factors that can cause aging, such as environmental changes, competition, and increasing complexity, and recommends strategies for preventing aging, such as documentation, planning for future changes, and periodic updates.
Unit 1 sepm software myths
Software Engineering and Project Management ppts for Unit 1. Reference : Software Engineering by Roger Pressman
Topic : Software Myths
To document or not to document? An exploratory study on developers' motivatio...
Abstract: Technical debt represents the situation in a project where developers accept compromises in one dimension of a system in order to meet urgent demands in other dimensions. These compromises incur a “debt”, on which “interest” has to be paid to maintain the long-term health of the project. One of the elements of technical debt is documentation debt due to under-documentation of the evolving system. In this exploratory study, our goal is to examine the different aspects of developers' motivation to document code. Specifically, we aim to identify the motivating and hindering aspects of documentation as perceived by the developers. The motivating aspects of code documenting we find include improving code comprehensibility, order, and quality. The hindering aspects include developers’ perception of documenting as a tedious, difficult, and time consuming task that interrupts the coding process. These findings may serve as a basis for developing guidelines toward improving documentation practices and encouraging developers to document their code thus reducing documentation debt.
Reducing Technical Debt
Technical debt is a metaphor for the gap between the current state of
a software system and its hypothesized ‘ideal’ state. One of the significant and
under-investigated elements of technical debt is documentation debt, which
may occur when code is created without supporting internal documentation,
such as code comments. Studies have shown that outdated or lacking
documentation is a considerable contributor to increased costs of software
systems maintenance. The importance of comments is often overlooked by
software developers, resulting in a notably slower growth rate of comments
compared to the growth rate of code in software projects. This research aims to
explore and better understand developers’ reluctance to document code, and
accordingly to propose efficient ways of using persuasive technology to
encourage programmers to document their code. The results may assist software
practitioners and project managers to control and reduce documentation debt.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
Recommended
To document or not to document? An exploratory study on developers' motivatio...
This document summarizes a study on developers' motivation to document code. Through interviews and surveys, researchers identified hindering and motivating factors for code documentation. Hindering factors included documentation being tedious, difficult, time-consuming, and interrupting coding work. Motivating factors included documentation improving code comprehensibility, order, and quality. The researchers propose designing a solution to encourage documentation by emphasizing motivating factors and mitigating hindering ones. They plan to further validate findings through a quantitative questionnaire. The goal is to increase developers' internal motivation to document code.
overview introduction to Software Engineering
Software Engineering 1 overview introduction to software engineering. First Lecture of Software engineering for BSCS , BSIT BCS MCS
Software engineering
The document discusses key lessons that can be learned from software engineering. It notes that software has become intertwined with society and addresses both functional and non-functional requirements. The document also outlines several principles of software engineering, such as rigor and formality, abstractions, separation of concerns, and modularity. It discusses the Capability Maturity Model and the evolution of software engineering approaches across different decades from the 1960s to the 2000s. Lastly, it provides recommendations for improving the software engineering process such as defining goals, separating requirements, and identifying the root causes of bugs.
Software aging
The document discusses software aging, which refers to the progressive degradation of software performance over time. It notes that software aging can occur even if the software itself is not changed, simply because needs and expectations change. The document outlines two types of aging: lack of movement, where the software is not updated to meet changing needs, and ignorant surgery, where changes are made by people who do not fully understand the software. It suggests several factors that can cause aging, such as environmental changes, competition, and increasing complexity, and recommends strategies for preventing aging, such as documentation, planning for future changes, and periodic updates.
Unit 1 sepm software myths
Software Engineering and Project Management ppts for Unit 1. Reference : Software Engineering by Roger Pressman
Topic : Software Myths
To document or not to document? An exploratory study on developers' motivatio...
Abstract: Technical debt represents the situation in a project where developers accept compromises in one dimension of a system in order to meet urgent demands in other dimensions. These compromises incur a “debt”, on which “interest” has to be paid to maintain the long-term health of the project. One of the elements of technical debt is documentation debt due to under-documentation of the evolving system. In this exploratory study, our goal is to examine the different aspects of developers' motivation to document code. Specifically, we aim to identify the motivating and hindering aspects of documentation as perceived by the developers. The motivating aspects of code documenting we find include improving code comprehensibility, order, and quality. The hindering aspects include developers’ perception of documenting as a tedious, difficult, and time consuming task that interrupts the coding process. These findings may serve as a basis for developing guidelines toward improving documentation practices and encouraging developers to document their code thus reducing documentation debt.
Reducing Technical Debt
Technical debt is a metaphor for the gap between the current state of
a software system and its hypothesized ‘ideal’ state. One of the significant and
under-investigated elements of technical debt is documentation debt, which
may occur when code is created without supporting internal documentation,
such as code comments. Studies have shown that outdated or lacking
documentation is a considerable contributor to increased costs of software
systems maintenance. The importance of comments is often overlooked by
software developers, resulting in a notably slower growth rate of comments
compared to the growth rate of code in software projects. This research aims to
explore and better understand developers’ reluctance to document code, and
accordingly to propose efficient ways of using persuasive technology to
encourage programmers to document their code. The results may assist software
practitioners and project managers to control and reduce documentation debt.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
Introduction To Software Engineering
The importance of software since there is were the motivation for software engineering lies and then and introduction to software engineering mentioning the concept and stages of development and working in teams
software myths
The document discusses several common myths about software engineering. It presents myths such as the idea that requirements can easily be changed, that adding more programmers will solve scheduling problems, and that coding is the major effort. For each myth, it provides the reality, such as how requirement changes often degrade software, coordination gets harder with more programmers, and coding is usually only 10% of the effort while other post-delivery activities account for 50-70% of the work. The document advocates for formal reviews, documentation, and a team approach rather than relying on individuals.
Some Myths in Software Development
Developers are knowledge workers, not just encoders or typists. Coding is just a small part of software development, which is primarily about understanding people and business needs. Modern programming requires knowledge of multiple languages and technologies, and developers will use existing packages rather than writing all code themselves.
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Big Ball of Mud (BBoM) architectures are viewed as the culmination of many design decisions that, over time, result in a system that is hodgepodge of steaming and smelly anti-patterns. It can be arguably claimed that one of the reasons for the growth and popularity of agile practices is partially due to the fact that the state of the art of software architectures was not that good. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with evolving architectures (possibly muddy) and keeping systems working while making significant improvements and adding functionality. Time has also shown that Agile practices are not sufficient to prevent or eliminate Mud. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture.
This talk will examine the paradoxes that underlie Big Balls of Mud, what causes them, and why they are so prominent. I’ll explore what agile practices can help us avoid or cope with mud. I’ll also explain why continuous delivery and TDD with refactoring is not enough to help ensure clean architecture and why it is important to understand what is core to the architecture and the problem at hand. Understanding what changes in the system and at what rates can help you prevent becoming mired in mud. By first understanding where a system’s complexities are and where it keeps getting worse, we can then work hard (and more intelligently) at sustaining the architecture. This can become a key value to the agile team. The results will leave attendees with practices and patterns that help clean your code (refactor) as well as keeping the code clean or from getting muddier.
Additionally, I’ll talk about some practices and patterns that help keep the code clean or from getting muddier. Some of these include: Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftmanship and the like.. The original Big Ball of Mud paper described some best practices such as SHEARING LAYERS and SWEEPING IT UNDER THE RUG as a way to help deal with muddy architectures. Additionally there are some other practices such as PAVING OVER THE WAGON TRAIL and WIPING YOUR FEET AT THE DOOR that can make code more habitable.
ADUF - Adaptable Design Up Front
In the context of Iterative Software Development, we ask the question: How much design should be done "up front"?
We propose the approach of Adaptable Design Up Front, which focuses on capturing the essential aspects of the system and plans for extensibility and adaptability.
Myths in Software Requirements
Sheraz Pervaiz will present on myths in software requirements. He has over 14 years of experience working in various roles in software development. Common myths include clients fully knowing their requirements, requirements being fixed, and one solution fitting all problems. Specific myths to be covered are that clients know everything, requirements are now fully known after initial meetings, requirements will not change during the project, assumptions can replace explicitly stating requirements, and there is a single definition of what makes a good requirement. The presentation will be followed by a Q&A section. Future presentations in this series will focus on handling myths and the relationship between myths and project management.
Got Myth? Myths in Software Engineering
The document summarizes a working session on software engineering myths held on October 4, 2007 in Paris. The session included discussions of common myths in areas such as complexity, bugs, clones, aspect-oriented programming, and project management. Participants shared and debated myths in small group discussions. Some examples of myths discussed include the ideas that complexity leads to more bugs, clones are always bad, and aspect-oriented programs are inherently easier to maintain. The session aimed to evaluate whether such perceptions are truly myths or if aspects of them have been found to hold true in various studies.
software characteristics
software characteristics for Software engineering,All characteristics and details about software For bscs , bsit , mcs , bcs
Software engineering lectures
Software Development in 21st Century
- Many software projects fail to be completed on time and on budget due to unrealistic deadlines, poor estimation of tasks, and changing requirements. Architectural flaws and lack of domain knowledge also contribute to project failures.
- Common problems include inadequate testing, poor code quality, lack of documentation, and developers not wanting to work on code they did not write themselves. Traditional software engineering practices have not changed much over the past 30 years.
- A better approach focuses on rapid feedback through small iterative releases, collaboration with customers, responding flexibly to change, and empowering self-organizing teams. Continuous integration and testing also help catch problems early.
Introduction to software Engineering
Software is ubiquitous in modern society and can have huge impacts, both positive and negative. However, simply programming a software is not enough - software engineering principles must be followed to develop reliable, high-quality software that meets customer needs. Some common software development issues include not fulfilling customer requirements, being difficult to improve or extend, and lacking documentation. Following a systematic process involving requirements analysis, design, implementation, testing, and maintenance can help address these issues and produce software delivered on time and budget that works as intended.
An Introduction To Software Engineering
This is an presentation which I gave on GRSC 7770 course. Which is a course to train all Grad students how to teach under-graduate students.
Software Engineering Unit-1
The document provides an introduction to software engineering concepts. It discusses how software engineering aims to develop reliable software products using well-defined scientific principles and methods. It covers software evolution, different software paradigms including development, design and programming paradigms. It also discusses different software life cycle models like waterfall, incremental, prototyping and spiral models. Finally, it talks about characteristics of good software products and causes of software crisis.
Unit1
This document provides an overview of software engineering and its models. It discusses the evolution of software engineering from the 1960s to present day. It describes key software engineering concepts like the software development life cycle, capability maturity models, and various software development models including waterfall, iterative enhancement, prototyping, spiral, and RAD approaches. The document emphasizes that software engineering applies systematic and disciplined processes to software development in order to address challenges like increasing complexity, high costs, and quality issues.
Software Engineering - Ch1 introduction
Software Engineering - Ch1 introduction
This material is based on chapter 1 of “Software Engineering (l0th Edition)” by Ian Sommerville. Addison Wesley, 2015, ISBN-10: 0137035152.
https://iansommerville.com/software-engineering-book/
Why structure matters
This document discusses the importance of software structure and how it impacts development. It provides quotes highlighting that complexity kills productivity and structured software is delivered faster and with fewer bugs. The document also notes that well-structured code improves estimates, reduces risks, and enables focused testing and reuse. Developer productivity is a key benefit, as researchers found developers spend up to 78% of their time understanding unstructured code.
introduction to software enginering
Software engineering is an engineering discipline that applies scientific principles and methods to the development of software. It aims to deliver reliable and efficient software on time and within budget by defining processes and procedures. The need for software engineering has arisen due to factors like increasing changes in user requirements and environments, large and complex software projects, ensuring scalability and cost-effectiveness, and managing quality.
Difference between traditional and agile software development
To gain knowledge on difference between the traditional software development and Agile Software Development
Professional Software Development, Practices and Ethics
The document discusses professional software development practices and ethics. It begins by showing code for hacking into a system using SSH and resetting the root password. It then discusses disabling grid nodes in a system. The rest of the document discusses the experience and background of Lemi Orhan Ergin, a senior software engineer, including his education and work history. It also provides an agenda for a presentation on how to become an ethical software developer, covering topics like waterfall development, Agile development, software craftsmanship practices, ethics in software engineering, and ethics in development.
10x programmers - What lies beneath
The document discusses the traits of highly skilled "10x" programmers. It notes that programming is a creative profession requiring logic-based creativity. It argues that strong programmers derive strength from principles, values, behaviors and practices that are not always visible, like an iceberg with most of its mass underwater. These include qualities like purpose, autonomy, mastery, communication, simplicity, flexibility, testing principles, learning, knowledge sharing and enjoying the work. Clean code results from craftsmanship rather than following rules, and programmers should focus on producing value rather than just code.
Sepm t1
There are three main types of software:
1) System software which operates the computer hardware and provides basic functionality and a platform for other software. This includes operating systems, drivers, servers, and utilities.
2) Programming software which are tools used by developers to create, debug, and maintain other programs and applications, such as compilers, debuggers, and text editors.
3) Application software which allows users to perform specific tasks, such as web browsers, office suites, graphics software, and media players. Application software runs on top of system software and may use programming software during development.
Unit 1 OOSE
Introduction to Software Engineering, Software Process, Perspective and Specialized Process Models – Introduction to Agility – Agile process – Extreme programming – XP process - Estimation-FP,LOC and COCOMO I and II,Risk Management, Project Scheduling.
Clicker v4m report
The document provides details about the Clicker Android Native Application project completed by an internship team at IIT Bombay under the guidance of Prof. D. B. Phatak. It includes an acknowledgment section thanking the mentors and administrative support. It then lists the team members and mentors who guided the project. The abstract provides an overview of the Clicker software and how the native Android application aims to reduce load on the server. Finally, it outlines the various chapters that will describe the project details such as architecture, design considerations, implementation, and future work.
More Related Content
What's hot
Introduction To Software Engineering
The importance of software since there is were the motivation for software engineering lies and then and introduction to software engineering mentioning the concept and stages of development and working in teams
software myths
The document discusses several common myths about software engineering. It presents myths such as the idea that requirements can easily be changed, that adding more programmers will solve scheduling problems, and that coding is the major effort. For each myth, it provides the reality, such as how requirement changes often degrade software, coordination gets harder with more programmers, and coding is usually only 10% of the effort while other post-delivery activities account for 50-70% of the work. The document advocates for formal reviews, documentation, and a team approach rather than relying on individuals.
Some Myths in Software Development
Developers are knowledge workers, not just encoders or typists. Coding is just a small part of software development, which is primarily about understanding people and business needs. Modern programming requires knowledge of multiple languages and technologies, and developers will use existing packages rather than writing all code themselves.
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Big Ball of Mud (BBoM) architectures are viewed as the culmination of many design decisions that, over time, result in a system that is hodgepodge of steaming and smelly anti-patterns. It can be arguably claimed that one of the reasons for the growth and popularity of agile practices is partially due to the fact that the state of the art of software architectures was not that good. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with evolving architectures (possibly muddy) and keeping systems working while making significant improvements and adding functionality. Time has also shown that Agile practices are not sufficient to prevent or eliminate Mud. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture.
This talk will examine the paradoxes that underlie Big Balls of Mud, what causes them, and why they are so prominent. I’ll explore what agile practices can help us avoid or cope with mud. I’ll also explain why continuous delivery and TDD with refactoring is not enough to help ensure clean architecture and why it is important to understand what is core to the architecture and the problem at hand. Understanding what changes in the system and at what rates can help you prevent becoming mired in mud. By first understanding where a system’s complexities are and where it keeps getting worse, we can then work hard (and more intelligently) at sustaining the architecture. This can become a key value to the agile team. The results will leave attendees with practices and patterns that help clean your code (refactor) as well as keeping the code clean or from getting muddier.
Additionally, I’ll talk about some practices and patterns that help keep the code clean or from getting muddier. Some of these include: Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftmanship and the like.. The original Big Ball of Mud paper described some best practices such as SHEARING LAYERS and SWEEPING IT UNDER THE RUG as a way to help deal with muddy architectures. Additionally there are some other practices such as PAVING OVER THE WAGON TRAIL and WIPING YOUR FEET AT THE DOOR that can make code more habitable.
ADUF - Adaptable Design Up Front
In the context of Iterative Software Development, we ask the question: How much design should be done "up front"?
We propose the approach of Adaptable Design Up Front, which focuses on capturing the essential aspects of the system and plans for extensibility and adaptability.
Myths in Software Requirements
Sheraz Pervaiz will present on myths in software requirements. He has over 14 years of experience working in various roles in software development. Common myths include clients fully knowing their requirements, requirements being fixed, and one solution fitting all problems. Specific myths to be covered are that clients know everything, requirements are now fully known after initial meetings, requirements will not change during the project, assumptions can replace explicitly stating requirements, and there is a single definition of what makes a good requirement. The presentation will be followed by a Q&A section. Future presentations in this series will focus on handling myths and the relationship between myths and project management.
Got Myth? Myths in Software Engineering
The document summarizes a working session on software engineering myths held on October 4, 2007 in Paris. The session included discussions of common myths in areas such as complexity, bugs, clones, aspect-oriented programming, and project management. Participants shared and debated myths in small group discussions. Some examples of myths discussed include the ideas that complexity leads to more bugs, clones are always bad, and aspect-oriented programs are inherently easier to maintain. The session aimed to evaluate whether such perceptions are truly myths or if aspects of them have been found to hold true in various studies.
software characteristics
software characteristics for Software engineering,All characteristics and details about software For bscs , bsit , mcs , bcs
Software engineering lectures
Software Development in 21st Century
- Many software projects fail to be completed on time and on budget due to unrealistic deadlines, poor estimation of tasks, and changing requirements. Architectural flaws and lack of domain knowledge also contribute to project failures.
- Common problems include inadequate testing, poor code quality, lack of documentation, and developers not wanting to work on code they did not write themselves. Traditional software engineering practices have not changed much over the past 30 years.
- A better approach focuses on rapid feedback through small iterative releases, collaboration with customers, responding flexibly to change, and empowering self-organizing teams. Continuous integration and testing also help catch problems early.
Introduction to software Engineering
Software is ubiquitous in modern society and can have huge impacts, both positive and negative. However, simply programming a software is not enough - software engineering principles must be followed to develop reliable, high-quality software that meets customer needs. Some common software development issues include not fulfilling customer requirements, being difficult to improve or extend, and lacking documentation. Following a systematic process involving requirements analysis, design, implementation, testing, and maintenance can help address these issues and produce software delivered on time and budget that works as intended.
An Introduction To Software Engineering
This is an presentation which I gave on GRSC 7770 course. Which is a course to train all Grad students how to teach under-graduate students.
Software Engineering Unit-1
The document provides an introduction to software engineering concepts. It discusses how software engineering aims to develop reliable software products using well-defined scientific principles and methods. It covers software evolution, different software paradigms including development, design and programming paradigms. It also discusses different software life cycle models like waterfall, incremental, prototyping and spiral models. Finally, it talks about characteristics of good software products and causes of software crisis.
Unit1
This document provides an overview of software engineering and its models. It discusses the evolution of software engineering from the 1960s to present day. It describes key software engineering concepts like the software development life cycle, capability maturity models, and various software development models including waterfall, iterative enhancement, prototyping, spiral, and RAD approaches. The document emphasizes that software engineering applies systematic and disciplined processes to software development in order to address challenges like increasing complexity, high costs, and quality issues.
Software Engineering - Ch1 introduction
Software Engineering - Ch1 introduction
This material is based on chapter 1 of “Software Engineering (l0th Edition)” by Ian Sommerville. Addison Wesley, 2015, ISBN-10: 0137035152.
https://iansommerville.com/software-engineering-book/
Why structure matters
This document discusses the importance of software structure and how it impacts development. It provides quotes highlighting that complexity kills productivity and structured software is delivered faster and with fewer bugs. The document also notes that well-structured code improves estimates, reduces risks, and enables focused testing and reuse. Developer productivity is a key benefit, as researchers found developers spend up to 78% of their time understanding unstructured code.
introduction to software enginering
Software engineering is an engineering discipline that applies scientific principles and methods to the development of software. It aims to deliver reliable and efficient software on time and within budget by defining processes and procedures. The need for software engineering has arisen due to factors like increasing changes in user requirements and environments, large and complex software projects, ensuring scalability and cost-effectiveness, and managing quality.
Difference between traditional and agile software development
To gain knowledge on difference between the traditional software development and Agile Software Development
Professional Software Development, Practices and Ethics
The document discusses professional software development practices and ethics. It begins by showing code for hacking into a system using SSH and resetting the root password. It then discusses disabling grid nodes in a system. The rest of the document discusses the experience and background of Lemi Orhan Ergin, a senior software engineer, including his education and work history. It also provides an agenda for a presentation on how to become an ethical software developer, covering topics like waterfall development, Agile development, software craftsmanship practices, ethics in software engineering, and ethics in development.
10x programmers - What lies beneath
The document discusses the traits of highly skilled "10x" programmers. It notes that programming is a creative profession requiring logic-based creativity. It argues that strong programmers derive strength from principles, values, behaviors and practices that are not always visible, like an iceberg with most of its mass underwater. These include qualities like purpose, autonomy, mastery, communication, simplicity, flexibility, testing principles, learning, knowledge sharing and enjoying the work. Clean code results from craftsmanship rather than following rules, and programmers should focus on producing value rather than just code.
Sepm t1
There are three main types of software:
1) System software which operates the computer hardware and provides basic functionality and a platform for other software. This includes operating systems, drivers, servers, and utilities.
2) Programming software which are tools used by developers to create, debug, and maintain other programs and applications, such as compilers, debuggers, and text editors.
3) Application software which allows users to perform specific tasks, such as web browsers, office suites, graphics software, and media players. Application software runs on top of system software and may use programming software during development.
What's hot (20)
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Difference between traditional and agile software development
Difference between traditional and agile software development
Professional Software Development, Practices and Ethics
Professional Software Development, Practices and Ethics
Similar to SFScon19 - Riccardo Felluga Andrea Janes - Personas-Driven Approach to Test Case Generation
Unit 1 OOSE
Introduction to Software Engineering, Software Process, Perspective and Specialized Process Models – Introduction to Agility – Agile process – Extreme programming – XP process - Estimation-FP,LOC and COCOMO I and II,Risk Management, Project Scheduling.
Clicker v4m report
The document provides details about the Clicker Android Native Application project completed by an internship team at IIT Bombay under the guidance of Prof. D. B. Phatak. It includes an acknowledgment section thanking the mentors and administrative support. It then lists the team members and mentors who guided the project. The abstract provides an overview of the Clicker software and how the native Android application aims to reduce load on the server. Finally, it outlines the various chapters that will describe the project details such as architecture, design considerations, implementation, and future work.
Project Management (2).pdf
The document discusses various aspects of software project management including the management scope, people, product, process, and project. It also covers the W5HH principle for defining key project characteristics including why the system is being developed, what will be done, when it will be done, who is responsible, where people are located, how the job will be done technically and authoritatively, and how many resources are needed. Finally, it discusses software metrics for measuring aspects like size, quality, and productivity.
Software Development Craftsmanship
The document discusses the need for more emphasis on training software developers as individual "craftsmen" through the use of closed-loop personal quality systems and metrics for continuous self-improvement. It argues that while many methodologies focus on the team and organizational level, making each developer a "craftsman" through education and process would improve foundational software development skills. The ideal solution proposed is a formal process like Watts Humphrey's Personal Software Process that guides developers from apprentice to journeyman and craftsman levels of expertise.
Test Engineer_NanYang
Nan Yang is a software tester with over 7 years of experience testing mobile apps and web applications. She has expertise in manual testing, writing test cases, and executing test plans to find bugs. Some of her projects involved testing Tencent mobile apps, an IBM application, and a Japanese mobile sales system. She is proficient with testing tools like QTP and knowledgeable about mobile platforms like Android and iOS.
Bridging the gap: Successful collaboration between engineering & design
When a genius new product idea is brewing, whether it be through a hackathon, user research, or a stakeholder, the process of getting the idea to implementation heavily relies on developers. The collaboration between product, design, and engineering can sometimes be tricky because they don't always speak the same technical language and are viewing the concept through very different lenses. Shutterstock's Software Development Manager, Anusha Dayananda, will provide her perspective of how to ensure buy-in from the engineering team.
Anusha Dayananda, Software Development Manager, Shutterstock
unit 1 ppt.pptx
Software engineering focuses on building software systems, studying software only, and following structured processes for checking, verifying, and removing errors. It involves areas like software development, testing, and quality assurance. Computer science studies how computers perform theoretical and mathematical tasks, involving both software and hardware. It includes areas like networking, artificial intelligence, and database systems.
Some key challenges in software engineering include maintaining and updating legacy software to meet changing user needs over time, developing platform-independent software that can run on different systems, delivering extremely large systems on time without compromising quality, ensuring software is trustworthy and reliable, and dealing with risks in safety-critical applications where failures could have massive costs.
Costs in software engineering are
Overview of project planning
The document discusses the key steps in project planning:
1. Establishing project objectives, scope, and stakeholders. This includes identifying success measures and how communication will occur.
2. Defining the project infrastructure such as how it relates to strategic plans and who is involved.
3. Analyzing project characteristics like risks and determining the overall approach, which for this scenario may involve prototyping.
4. Identifying products, their relationships, and the activities needed to create each one. This involves creating a product breakdown structure and activity network.
application development analyst roles and responsibilities.pdf
Imagine being at the vanguard of developing cutting-edge software programs that change industries and enhance user experiences. Understanding the tasks and functions involved with this fascinating position is essential if you're interested in the field of application development and thinking of working as an application development analyst. This post will walk you through the essential responsibilities, necessary abilities, and available possibilities for an application development analyst.
ElizabethPrattConsulting_DellPortfolio
This document summarizes Elizabeth Pratt's work as a UX team lead for Dell Data Protection security software from 2011-2014. Through user research, design thinking, and iterative testing, the team transformed DDP from bloated software to a visually stunning and usable solution. Key outcomes included DDP becoming Dell's most successful software in 2014, earning reader's choice awards, and influencing Dell's adoption of the software and unified UX approach.
Agile software development
This document discusses agile software development processes. It outlines some common reasons for challenged, failed, and successful projects. Some key problems with the traditional waterfall model are that mistakes are hard to find early on and requirements often change. The document then introduces agile concepts like iterative development, test-driven development, extreme programming, scrum, and their benefits like producing working software earlier, adapting to change, and improved communication.
importance of resources allocation in formal method of software engineering ...
This document discusses key concepts related to project management including resource allocation, software risks, differences between products and projects, discount factors, net present value, and net profit.
The main points are:
1) Resource allocation in project management is important for planning, scheduling, and controlling workload to improve team effectiveness. It involves identifying and tracking resources like budget, tools, and time.
2) The top five software risks are inherent schedule flaws, requirements inflation, employee turnover, specification breakdown, and poor productivity. Agile methods aim to mitigate these risks through practices like iterative planning and prioritization.
3) The key difference between a product and project is that a product is manufactured and sold while a project is built to
Introduction of Software Engineering
This document discusses software engineering and provides definitions and explanations of key concepts:
- Software engineering is defined as an engineering discipline concerned with all aspects of software production. It focuses on practical software development and delivery, whereas computer science focuses more on theory.
- Good software should deliver required functionality, performance, and be maintainable, dependable, usable and acceptable to users.
- A software engineering approach is layered, with quality, process models, methods and tools. Process models define activities for effective delivery. Methods provide tasks for requirements, design, coding and testing. Tools support the process and methods.
- Generic software processes involve communication, planning, modeling, construction and deployment activities in an iterative fashion to develop
Overview of project planning
Project planning involves multiple processes that facilitate software production before actual development begins. It establishes the objectives, stakeholders, and infrastructure needed for a project. The key steps in project planning include selecting the project, identifying objectives and measures of success, establishing leadership and communication methods, analyzing the project, and estimating tasks and resources required. An example scenario describes planning the development of a psychometric testing software package to evaluate team compatibility for new projects.
KARTHICK_PROFILE
Karthick D is seeking a position as an Android developer. He has a B.E in Computer Science and 1 year 4 months of experience developing Android apps. His skills include Java, XML, SQLite, and designing user-friendly interfaces. Some of his projects include a video calling app, sensor app, and law library app developed for multiple platforms using PhoneGap. He is proficient in OOPs concepts and aims to continuously learn new technologies.
lecture 1-5.pdf
Here are the key characteristics of engineering:
1. Engineers proceed by making a series of decisions, carefully evaluating options and choosing appropriate approaches at each decision point based on tradeoff analysis of costs and benefits.
2. Engineers measure things quantitatively when appropriate, calibrate and validate measurements, and use approximations based on experience.
3. Engineers design things, whether physical systems, software systems, or business processes. Design involves establishing requirements, generating alternative solutions, evaluating alternatives, and choosing a solution.
4. Engineers build or construct things, whether physical prototypes or software systems. They integrate components and ensure everything works together as intended.
5. Engineers test things, whether by simulation, experimentation, or operational trials,
Perspective presentation
Larger presentation about the LMU Munich school-project "Perspective" as well as the technology making it possible and the work leading up to the final version.
unit-1.ppt
This document outlines the objectives and content of the IT8075 Software Project Management course. The course aims to teach students how to plan, manage, and deliver successful software projects. It covers topics such as project planning, estimation techniques, risk management, project monitoring and control, and people management. The course is divided into 5 units which cover areas such as the software development life cycle, effort estimation methods, scheduling, risk analysis, and staff management in projects. The intended learning outcomes include understanding basic project management principles and gaining knowledge of processes, estimation, risk identification, and using principles to define project structure and track progress.
An Actionable Framework for Understanding and Improving Developer Experience
Authors: Michaela Greiler, Margaret-Anne Storey, Abi Noda
Abstract:
Developer experience is an important concern for software organizations as enhancing developer experience improves productivity, satisfaction, engagement and retention. We set out to understand what affects developer experience through semi-structured interviews with 21 developers from industry, which we transcribed and iteratively coded. Our findings elucidate factors that affect developer experience and characteristics that influence their respective importance to individual developers. We also identify strategies employed by individuals and teams to improve developer experience and the barriers that stand in their way. Lastly, we describe the coping mechanisms of developers when developer experience cannot be sufficiently improved. Our findings result in the DX Framework, an actionable conceptual framework for understanding and improving developer experience. The DX Framework provides a go-to reference for organizations that want to enable more productive and effective work environments for their developers.
Journal First Presentation of a TSE paper
Preprint: https://arxiv.org/abs/2205.06352
YouTube link for video of talk (pre conference): https://youtu.be/ChaQ9E2ZIiE
How to become a Software Engineer Carrier Path for Software Developer
Software engineers are responsible for creating different software programs that power many technologies and applications we use everyday. There are many types and roles for software engineers, including developing applications, systems, security features, and ensuring quality. Becoming a software engineer involves obtaining a relevant degree, mastering programming skills, databases, algorithms, software engineering theory, and gaining experience through projects. Experience can then be used to find jobs through websites, recruiters, freelancing, or networking in local tech communities. The field continues to evolve, with growing opportunities in areas like cloud, AI, blockchain, and cybersecurity.
Similar to SFScon19 - Riccardo Felluga Andrea Janes - Personas-Driven Approach to Test Case Generation (20)
Bridging the gap: Successful collaboration between engineering & design
Bridging the gap: Successful collaboration between engineering & design
application development analyst roles and responsibilities.pdf
application development analyst roles and responsibilities.pdf
importance of resources allocation in formal method of software engineering ...
importance of resources allocation in formal method of software engineering ...
An Actionable Framework for Understanding and Improving Developer Experience
An Actionable Framework for Understanding and Improving Developer Experience
How to become a Software Engineer Carrier Path for Software Developer
How to become a Software Engineer Carrier Path for Software Developer
More from South Tyrol Free Software Conference
SFSCON23 - Rufai Omowunmi Balogun - SMODEX – a Python package for understandi...
SFSCON23 - Rufai Omowunmi Balogun - SMODEX – a Python package for understandi...South Tyrol Free Software Conference
The complexity of agricultural droughts requires a consistent, reliable, and systematic method for monitoring and reporting. Amongst the various indices used to monitor this phenomenon, the soil moisture anomaly has been proven to be a more reliable predictor. However, the datasets required for computing this index are often large and computationally demanding. To address this challenge, we have developed SMODEX, a Python package that enables scalable, fast, and open-source standard-compliant computation and visualization of soil moisture anomalies.
SMODEX simplifies the computation and visualization of time-series for soil moisture and soil moisture anomalies from high-dimensional climate datasets. It allows for quick and easy parallelization of the computation on a daily, weekly, and monthly timescale. Additionally, SMODEX implements a straightforward workflow for automating the use of FAIR (Findable, Accessible, Interoperable, and Reusable) principles in producing and sharing outputs by leveraging the open source STAC API. The package is extendible and provides information on how to contribute to the project, test suites, test coverage, and a use case for the South Tyrol region, all provided in the package repository. In the future, additional agricultural drought indices and indicators would be included to serve to even larger community of researchers, policy makers, and individual users.SFSCON23 - Roberto Innocenti - From the design to reality is here the Communi...
SFSCON23 - Roberto Innocenti - From the design to reality is here the Communi...South Tyrol Free Software Conference
The Open Hardware PowerPC Notebook designed around GNU/Linux will be showed at NOI Techpark. We had presented here its motherboard design in 2018. We will updates regarding last developments for u-boot AMD video drivers, re-design of heat pipes, and CE test certification process. We will give future availability milestones of this notebook and details regarding the GNU/Linux distributions or other OS that could runs on it.SFSCON23 - Martin Rabanser - Real-time aeroplane tracking and the Open Data Hub
SFSCON23 - Martin Rabanser - Real-time aeroplane tracking and the Open Data HubSouth Tyrol Free Software Conference
RMBtec proposes using the Open Data Hub as the real-time data backbone for a start-up creating an aircraft tracking application. The Open Data Hub offers data providers visibility, infrastructure to publish data, documentation, analytics and support. It describes how aircraft position data captured by sensors could be preprocessed and sent to the Open Data Hub via MQTT, then streamed in real-time and stored in a data mart via transformers. The Open Data Hub provides an alternative to cloud services and has capabilities that could support publishing and consuming aircraft tracking data.SFSCON23 - Marianna d'Atri Enrico Zanardo - How can Blockchain technologies i...
SFSCON23 - Marianna d'Atri Enrico Zanardo - How can Blockchain technologies i...South Tyrol Free Software Conference
The transition from Web 2.0 to Web 3.0 has fueled the need for a secure and decentralized cloud storage solution for digital assets. Web 2.0 was characterized by centralized platforms where user data was under the control of companies. In contrast, Web 3.0 aims to empower individuals and foster a decentralized web that supports and benefits the Free Software and Open Data Communities.
Blockchain technologies facilitate seamless collaboration and interoperability among diverse stakeholders in the Free Software and Open Data communities. Developers can establish open and transparent ecosystems where data can be shared, verified, and integrated across multiple platforms.
Beez, with its own blockchain infrastructure, offers a secure and transparent platform for digital asset exchanges, bolstering transaction integrity and trust. By distributing data across a network of nodes, Beez ensures security and mitigates the risk of single points of failure. Users retain control over their data, safeguard their privacy, and can take advantage of the incentive mechanisms offered by blockchain networks.
During our presentation, we will explore the role of AI within Beez's ecosystem, facilitating accelerated data processing, correlation, and intelligent automation. AI unlocks valuable insights from blockchain data, and we will touch upon the use of Inductive Logic Programming (ILP) to enhance programming performance.
The integration of Blockchain and AI technologies holds great potential for advancing the safety and efficiency of the Open Data ecosystem. By combining decentralized data storage, trust-building mechanisms, and intelligent data processing, Beez is paving the way for a more secure, transparent, and user-centric digital landscape.SFSCON23 - Lucas Lasota - The Future of Connectivity, Open Internet and Human...
SFSCON23 - Lucas Lasota - The Future of Connectivity, Open Internet and Human...South Tyrol Free Software Conference
We are becoming more and more dependent on the Internet for our work, education, communication, personal relations and entertainment. Our digital devices conquered an unprecedented level of importance in our life.
However, we are facing a loss of control over our smartphones, tablets and other devices for internet connection. It's time to resolve monopolies and re-establish democratic control over the technology we most depend upon.
This talk will present the challenges end-users are facing to get more control over their devices and how Free Software is key for a consumer re-empowerement.
The talk will present real-life examples of policy demands against gatekeepers on digital markets, such as the struggle for Router Freedom in the last years and how Device Neutrality can serve as an important instrument for pushing forward end-user-oriented digital policies.SFSCON23 - Giovanni Giannotta - Intelligent Decision Support System for trace...
SFSCON23 - Giovanni Giannotta - Intelligent Decision Support System for trace...South Tyrol Free Software Conference
MOSH and MOAH are the abbreviation of two groups of chemical compounds found in mineral oils. “MOSH” stands for Mineral Oil Saturated Hydrocarbons. MOAH stands for Mineral Oil Aromatic Hydrocarbons. Both of them are under European deeply evaluation because there are two food contaminants. According to the current state of scientific knowledge, there is no sufficient toxicological evidence to prove a health risk to humans from saturated mineral oil fractions (MOSH). Meanwhile, MOAH are suspected to be carcinogenic (especially PAH-like compounds with 3-7 ring systems), therefore their levels in food should be reduced according to the ALARA-principle (as low as reasonably achievable). Gruppo FOS with CNR ( MOSH and MOAH are the abbreviation of two groups of chemical compounds found in mineral oils. “MOSH” stands for Mineral Oil Saturated Hydrocarbons. MOAH stands for Mineral Oil Aromatic Hydrocarbons. Both of them are under European deeply evaluation because there are two food contaminants. According to the current state of scientific knowledge, there is no sufficient toxicological evidence to prove a health risk to humans from saturated mineral oil fractions (MOSH). Meanwhile, MOAH are suspected to be carcinogenic (especially PAH-like compounds with 3-7 ring systems), therefore their levels in food should be reduced according to the ALARA-principle (as low as reasonably achievable). Gruppo FOS with CNR (Consiglio Nazionale delle Ricerche), Santagata 1907 and Enginius are searching the system for finding and trace their presence in the virgin and extra virgin olive oils by using open fingerprints methods, open hardware and open source blockchain and AI technologies.SFSCON23 - Elena Maines - Embracing CI/CD workflows for building ETL pipelines
SFSCON23 - Elena Maines - Embracing CI/CD workflows for building ETL pipelinesSouth Tyrol Free Software Conference
Up-to date measurements of surface meteorological variables are essential to monitor weather conditions, their spatio-temporal variability and the potential effects on a wide range of sectors and applications. Moreover, when included in continuous records of long historical observations spanning several decades, they become essential for assessing long-term climate variability and change locally and on a regional level.
Automated pipelines capable of retrieving and processing near-real time meteorological data satisfy the primary prerequisites towards the development and advancement of effective and operational climate services.
With a public and operational near real-time monitoring web platform in mind, we present automated pipelines to collect and process up-to-date daily temperature and precipitation records for Trentino South Tyrol (Italy) and surrounding areas, and to derive their spatially interpolated fields at sub-km scale. Our pipelines are composed by multiple steps including data download, sanity checks, reconstruction of missing daily records, integration into the historical archive, spatial interpolation and publication onto online FAIR catalogues as (openEO) “datacubes”. The different APIs, data formats and structure across the various data sources, and the need to merge the data onto harmonized meteorological layers, make this a typical case of the so-called Extract, Transform and Load (ETL) pipelines, and, in order to follow the principles of data reproducibility and Open Science, we embraced open-source automated workflow management through GitLab’s Continuous Integration / Continuous Development (CI/CD) capabilities.
CI/CD workflows greatly help the management of the relatively complex graphs of tasks required for our climate application, ensuring seamless orchestration with thorough flow monitoring, application logs, transactions rollbacks, and exception handling in general. Native pipeline-oriented software development also fosters a clean separation of roles among the tasks, and a more modular architecture. This effectively reduces barriers to collaborative development and paves the way for robust operational climate services for researchers and decision makers in the face of the changing climate.SFSCON23 - Christian Busse - Free Software and Open Science
The Open Science movement aims to increase the transparency, reproducibility and inclusiveness of academic research. One of its central goals is therefore to make research outputs broadly available, e.g., manuscripts (Open Access) or research data (Open Data). While software/code created in the course of scientific research is a key artifact of scientific research that is clear distinct from the latter two, it has until recently not received the same attention as manuscripts or data, although it follows its own set of paradigms.
In this talk I will present an overview on how the core concepts of Free Software and the FAIR (findable, accessible, interoperable, reuseable) Principles intersect, what this means for managing code as research output and recent initiatives on the European level that will provide support for these issues.
SFSCON23 - Charles H. Schulz - Why open digital infrastructure matters
SFSCON23 - Charles H. Schulz - Why open digital infrastructure mattersSouth Tyrol Free Software Conference
Software freedom can be defined in many ways but in legal terms it is squarely defined by a set of approved FSF and OSI software licenses. Yet everyone realizes that beyond these licenses the goal of software freedom and digital sovereignty cannot be achieved without the ability to master and create hardware components and systems - and beyond that, to rely on open digital infrastructure (servers, datacenters, and resources) . This talk will present the challenges around these topics and what we, collectively in Europe already do and can do to ensure our independence and our freedoms.SFSCON23 - Andrea Vianello - Achieving FAIRness with EDP-portal
This document discusses efforts to make environmental data from the Environmental Data Platform (EDP) more FAIR (Findable, Accessible, Interoperable, Reusable) compliant. It describes the components of EDP including data repositories, a metadata catalog, web portal, and tools. It outlines work done to improve metadata quality for humans and interoperability for machines through signposting. This includes adding DOIs, citations, and linked data/linkset JSON files. The document emphasizes that maintaining high quality metadata requires significant ongoing effort.
SFSCON23 - Thomas Aichner - How IoT and AI are revolutionizing Mass Customiza...
SFSCON23 - Thomas Aichner - How IoT and AI are revolutionizing Mass Customiza...South Tyrol Free Software Conference
The document discusses how artificial intelligence (AI) and the Internet of Things (IoT) are revolutionizing mass customization. Traditional mass customization allows customers to customize products online through selection of options. AI enables more intuitive customization by learning customer preferences and offering dynamic, individual recommendations. IoT connects devices to customize the usage experience based on a person's context and needs. The integration of these technologies has the potential to transform mass customization by enabling mood-based and natural language processing for customization as well as products designed through AI with minimal user input.SFSCON23 - Stefan Mutschlechner - Smart Werke Meran
Since 2020 Stadtwerke Meran have realized 5 Use cases:
- Control of the control cabinets of public lighting.
- Optimizing the service on Waste Press container.
- Bike Boxes
- Just Nature Project , temperature measuring over Lorawan
- Smart Lighting , communication with single light points over Lorwan.
SFSCON23 - Mirko Boehm - European regulators cast their eyes on maturing OSS ...
SFSCON23 - Mirko Boehm - European regulators cast their eyes on maturing OSS ...South Tyrol Free Software Conference
As open source software becomes the foundation to build digital products, to run the backbones of ICT infrastructure and to ensure digital sovereignty and cyber resilience, both the technology as well as the communities that develop it inevitably move into the focus of regulators. The European Union is advancing a number of policy initiatives that regulate liability, cyber security, data handling and AI applications in digital products, among others. This is a challenge for the still quite decentralised and globally operating open source community. How could the open source community participate in legislative processes, and what may be the potential impacts of the upcoming regulation on the open source development process and community dynamics?SFSCON23 - Marco Pavanelli - Monitoring the fleet of Sasa with free software
SFSCON23 - Marco Pavanelli - Monitoring the fleet of Sasa with free softwareSouth Tyrol Free Software Conference
The public transport in South Tyrol is going through a huge transformation: new investments, many new green vehicles and a brand new software. Transition will take time and how do we develop a fleet monitoring system to use during the transition without spending a fortune ? maybe with free software!SFSCON23 - Marco Cortella - KNOWAGE and AICS for 2030 agenda SDG goals monito...
SFSCON23 - Marco Cortella - KNOWAGE and AICS for 2030 agenda SDG goals monito...South Tyrol Free Software Conference
AICS is the Italian Agency for Development Cooperation that started operating in 2016 with the ambition of aligning Italy with the main European and international partners in the commitment to development. KNOWAGE Labs are developing for AICS a platform that is probably unique in the world and will allow both the Agency and the public to access all the major indicators on the UN Sustainable Development Goals provided by international sources (World Bank, WTO, ILO..) and easily compare them. The solution will allow analysis to start from 3 different touch points: the infographic of SDG goals, the advanced search criteria, and the virtual assistant. Then, a customized dashboard will be provided to the user, allowing to further expand the analysis by interacting with charts, maps, tables, etc. This talk will show the state of art of the solution, highlighting objectives and expected results of the project, but also the new developments of KNOWAGE related to AI.SFSCON23 - Lina Ceballos - Interoperable Europe Act - A real game changer
SFSCON23 - Lina Ceballos - Interoperable Europe Act - A real game changerSouth Tyrol Free Software Conference
Interoperability is a core element of the ongoing digitalisation of Europe. With the Interoperable Europe Act, the EU is aiming to create a dedicated legal framework for interoperability and to enhance cross-border digital public services across the European Union. This talk will give an overview of the state of play of this proposed regulation in the ongoing EU legislative process, some of its flaws, and the important role that Free Software and its community can play in it.SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...
SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...South Tyrol Free Software Conference
How to sharpen the demand for public code across Europe and monitor progress with TEDective
For six years, the Free Software Foundation Europe has been calling with a broad alliance for publicly funded software to be published as Free Software. This initiative has become a great success: Our demand "Public Money? Public Code!" has found its way into government strategy papers, party programs, as well as coalition treaties, and is being discussed in public administrations across Europe.
At the same time, we see less progress than expected and vendor lock ins remain a crucial issue. Digital sovereignty is redefined bypassing Free Software. There is openwashing in publicly funded companies, and government projects in favour of Free Software remain empty words. Public statistics on the procurement of Free Software are largely unavailable.
It is therefore no longer enough to promote the idea of "Public Money? Public Code!". We as the Free Software community should be even more vigilant than before – continuing to praise small steps in the right direction, but pointing out and criticising omissions and lack of implementation. We should become more like watchdogs.
In the talk we will look at some examples of lack of implementation of Free Software policies. We will discuss how we, as civil society, can identify such shortcomings and how to deal with them. We will present our initiative TEDective – a free-software solution that makes European public procurement data explorable for non-experts, aiming to provide you with a powerful tool to keep an eye on real progress towards "Public Money? Public Code!" across Europe.SFSCON23 - Gabriel Ku Wei Bin - Why Do We Need A Next Generation Internet
SFSCON23 - Gabriel Ku Wei Bin - Why Do We Need A Next Generation InternetSouth Tyrol Free Software Conference
The Internet today forms the backbone of the digitisation of our society and economy. As connectivity increases, the boundaries between the real and digital world get increasingly blurred. However, there has been an erosion of trust in the Internet following revelations about the exploitation of personal data, large-scale cybersecurity and data breaches, and growing awareness of the proliferation and impacts of online disinformation.
What can be done to improve the Internet as a platform for future generations? What initiatives are currently in place to build key technological blocks of an Internet that supports human-centric values, such as privacy, security, and inclusion, while reflecting the values and norms all citizens should enjoy in Europe?
This talk will explore why the current state of the internet must be re-imagined and re-engineered in order to support healthy societies, the existing European Commission initiative to work towards doing so, and the role of Free Software in accomplishing these goals.SFSCON23 - Edoardo Scepi - The Brand-New Version of IGis Maps
2023 saw the launch, after a long and well-structured revision and development process, all based on a fruitful collaboration between several departments of the Autonomous Province of Bolzano, most of the township in South Tyrol, Informatica Alto Adige (SIAG - Technical partner) and the Consortium of Municipalities of the Province of Bolzano, of the new version of the integrated geographic data management system IGis Maps. In use for years in South Tyrol, has in the Consortium one of its most enthusiastic contributors and supporters.
The very first version was released about eight years ago and its implementation was based on the idea of creating a multi-purpose GIS management system that could support different types of users, that was highly customizable, and, above all, that could be widely shared among the various management entities, both public and private, present within our territory.
After years of use and ad-hoc developments, we can finally present the new version of the IGis Maps system, which incorporates all the technical and technological improvements we realized the system needed.
It was not just a major update together with new functionalities combined inside the previous software structure, but a true re-engineering that led, among other things, to a new and more efficient user interface, a major advancement regarding the internal security, an optimization and improvement of the entire editing section as well as an optimization of the section regarding the automatic geo-processes.
A mobile version is currently under development to better support any field activities, for which a very powerful option will be included, the possibility of creating special work sessions in off-line mode so as to be able to operate even in areas without a proper cellular line network coverage.
Other very important peculiarities concern that the system is developed using a totally free software code and infrastructure, that a detailed documentation has been produced to ensure sustainability to any further future evolution, even in case of technical partner turnover, and finally, that by taking advantage of the high standards and levels of security access can be guaranteed to any type of user. From professional users, through dedicated access and qualifications or, using the ordinary SPID, to the private citizen.
We will show examples of how different types of users and stakeholders now permanently use the system for the management of a variety of tasks related to their activities, and how it was possible to customize IGis Maps to create visualization and data management contexts that best meet their needs.
We will also present a related project concerning the updating and the correction of the new technical basal cartography, built upon the new Basic Core specification, achieved through the automatic conversion implemented by the SIAG team starting from the previous National Core cartography. With the new IGis Maps it was possible to create an a
SFSCON23 - Davide Vernassa - Empowering Insights Unveiling the latest innova...
SFSCON23 - Davide Vernassa - Empowering Insights Unveiling the latest innova...South Tyrol Free Software Conference
KNOWAGE is the open source analytics and business intelligence suite made in Italy. KNOWAGE aims to provide company and organizations with analytical capabilities to exploit data to increase their efficiency and sustainability. Also thanks to the open source community support, the suite is constantly evolving combining the reliability of the most popular business intelligence solutions with the security and the transparency guaranteed by open source.
This talk will show the last year advancements and new features towards a more mobile, accessible and user-friendly product, focusing on the newly rewritten dashboarding tool.More from South Tyrol Free Software Conference (20)
SFSCON23 - Rufai Omowunmi Balogun - SMODEX – a Python package for understandi...
SFSCON23 - Rufai Omowunmi Balogun - SMODEX – a Python package for understandi...
SFSCON23 - Roberto Innocenti - From the design to reality is here the Communi...
SFSCON23 - Roberto Innocenti - From the design to reality is here the Communi...
SFSCON23 - Martin Rabanser - Real-time aeroplane tracking and the Open Data Hub
SFSCON23 - Martin Rabanser - Real-time aeroplane tracking and the Open Data Hub
SFSCON23 - Marianna d'Atri Enrico Zanardo - How can Blockchain technologies i...
SFSCON23 - Marianna d'Atri Enrico Zanardo - How can Blockchain technologies i...
SFSCON23 - Lucas Lasota - The Future of Connectivity, Open Internet and Human...
SFSCON23 - Lucas Lasota - The Future of Connectivity, Open Internet and Human...
SFSCON23 - Giovanni Giannotta - Intelligent Decision Support System for trace...
SFSCON23 - Giovanni Giannotta - Intelligent Decision Support System for trace...
SFSCON23 - Elena Maines - Embracing CI/CD workflows for building ETL pipelines
SFSCON23 - Elena Maines - Embracing CI/CD workflows for building ETL pipelines
SFSCON23 - Christian Busse - Free Software and Open Science
SFSCON23 - Christian Busse - Free Software and Open Science
SFSCON23 - Charles H. Schulz - Why open digital infrastructure matters
SFSCON23 - Charles H. Schulz - Why open digital infrastructure matters
SFSCON23 - Andrea Vianello - Achieving FAIRness with EDP-portal
SFSCON23 - Andrea Vianello - Achieving FAIRness with EDP-portal
SFSCON23 - Thomas Aichner - How IoT and AI are revolutionizing Mass Customiza...
SFSCON23 - Thomas Aichner - How IoT and AI are revolutionizing Mass Customiza...
SFSCON23 - Stefan Mutschlechner - Smart Werke Meran
SFSCON23 - Stefan Mutschlechner - Smart Werke Meran
SFSCON23 - Mirko Boehm - European regulators cast their eyes on maturing OSS ...
SFSCON23 - Mirko Boehm - European regulators cast their eyes on maturing OSS ...
SFSCON23 - Marco Pavanelli - Monitoring the fleet of Sasa with free software
SFSCON23 - Marco Pavanelli - Monitoring the fleet of Sasa with free software
SFSCON23 - Marco Cortella - KNOWAGE and AICS for 2030 agenda SDG goals monito...
SFSCON23 - Marco Cortella - KNOWAGE and AICS for 2030 agenda SDG goals monito...
SFSCON23 - Lina Ceballos - Interoperable Europe Act - A real game changer
SFSCON23 - Lina Ceballos - Interoperable Europe Act - A real game changer
SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...
SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...
SFSCON23 - Gabriel Ku Wei Bin - Why Do We Need A Next Generation Internet
SFSCON23 - Gabriel Ku Wei Bin - Why Do We Need A Next Generation Internet
SFSCON23 - Edoardo Scepi - The Brand-New Version of IGis Maps
SFSCON23 - Edoardo Scepi - The Brand-New Version of IGis Maps
SFSCON23 - Davide Vernassa - Empowering Insights Unveiling the latest innova...
SFSCON23 - Davide Vernassa - Empowering Insights Unveiling the latest innova...
Recently uploaded
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Recently uploaded (20)
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
SFScon19 - Riccardo Felluga Andrea Janes - Personas-Driven Approach to Test Case Generation
- 1. Riccardo Felluga Supervisor: Andrea Janes
- 2. #1 Problem statement #2 Problem solution #3 Discussion and conclusion
- 4. engineering
- 5. Can we use ?
- 6. How can we test cases to validate a given piece of software using personas?
- 9. Creation of the personas Study of the personas Derivation of requirements Test cases development
- 10. We followed 10 steps1 1 Lene Nielsen. Personas - User Focused Design. Human–Computer Interaction Series. 2nd ed. 2019.. edition, 2019
- 15. P5: As a developer, I want that Booster measures the download rate
- 18. Len Bass, P. Clements, and R. Kazman. Software Architecture in Practice. SEI Series in Software Engineering. Pearson Education, 2012
- 19. Human engineering, usability and maintainability Reliability Performance Security
- 20. Reliability
- 22. • Developers are hard to convince • Waterfall approaches are not a solution in cases such as ours • Our method is flexible and can be adapted (e.g. IoT) • Not all personas are considered • Some personas will inevitably overlap
- 23. • Evaluation of the usefulness of the developed personas in context of the ongoing development of Booster • Evaluation of the coverage: not all the requirements are covered by test cases, e.g. Portability • Adapt personas as first users start to use the product
- 24. • We created the requirements and test cases of an early-stage software • Persona-based approach • Lessons learned applying our method on a real project under development