Software requirements and estimates
•Download as PPTX, PDF•
0 likes•1,164 views
Requirements gathering and software estimation are important parts of the development process. There are many techniques for gathering requirements such as use cases, user stories, and interviews to understand necessary features and avoid ambiguity. Estimates are also important but there is uncertainty involved since many factors can change. Estimates should be iterative and refined over time using techniques like counting lines of code or tasks.
Report
Share
Report
Share
Recommended
A Sampling of Tools
This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Boots and Shoeboxes
Jonathan Jackson presented on Ember FastBoot, Ember's solution for server-side rendering. FastBoot allows rendering Ember applications on the server so they are crawlable by search engines and perform well on low-powered devices. It handles server-side routing, model fetching, and rendering so apps work like traditional server-rendered sites. Jackson demonstrated how to set up FastBoot and use it with Ember Serve, and where to get help if issues arise.
Automated Testing with Databases
This document discusses challenges with automated unit and integration testing involving databases. It presents RoundhousE and NDbUnit as tools that help address these challenges by managing database schema changes and ensuring data is in a known state before tests. Examples of how these tools work would be helpful to understand how they automate testing of database-related code.
Ext js 4 MVC
The document discusses Ext JS 4.0 MVC and provides an overview of its key concepts and components. The motivations for using MVC include creating clean, maintainable code that is easier to learn, leverage tooling for, and collaborate on. It then covers the basic components of MVC - views, models, stores, and controllers. Views should be balanced to avoid having too many or too few. Models represent types of data, stores manage that data, and controllers tie everything together by figuring out responsibilities, setting references, and listening to events.
How to choose a framework
This document discusses factors to consider when choosing a frontend framework, including the team and its evolution, popular JavaScript frameworks like Angular and Ember, and how the framework choice impacts code, testing, documentation, contributions, and recruitment. It recommends that some framework is needed but the developer must decide whether to use an existing one or build their own, considering support and how the framework may change over time.
Automated Testing: Obstacles, Pitfalls, and Dangers
The document discusses the motivation, principles, and obstacles of automated testing. It motivates automated testing by noting how it provides visibility into problems, detects issues early, and acts as an advance warning system. The principles discussed are having tests that are zero configuration, fast, provide clear results, and are easy to maintain. Obstacles covered include tests becoming too specific over time, reliance on system time/date, dependency on databases changing test data, and tests becoming too coupled through overuse of reuse. Examples are provided to illustrate the points.
Владимир Бронников (Senior .NET Developer, Perfectial) “Performance optimizat...
Владимир Бронников (Senior .NET Developer, Perfectial) “Performance optimization tips and tricks for .NET web applications. Practical experience”
Sahi Conference
Sahi is an open source web automation and testing tool. It uses JavaScript to automate tests on web applications from a proxy server, independently of the specific website. Some key features include support for scheduling test actions, suites that can run in multiple threads, and advantages over other tools like support for Ant, no proprietary language, and an active community.
Recommended
A Sampling of Tools
This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Boots and Shoeboxes
Jonathan Jackson presented on Ember FastBoot, Ember's solution for server-side rendering. FastBoot allows rendering Ember applications on the server so they are crawlable by search engines and perform well on low-powered devices. It handles server-side routing, model fetching, and rendering so apps work like traditional server-rendered sites. Jackson demonstrated how to set up FastBoot and use it with Ember Serve, and where to get help if issues arise.
Automated Testing with Databases
This document discusses challenges with automated unit and integration testing involving databases. It presents RoundhousE and NDbUnit as tools that help address these challenges by managing database schema changes and ensuring data is in a known state before tests. Examples of how these tools work would be helpful to understand how they automate testing of database-related code.
Ext js 4 MVC
The document discusses Ext JS 4.0 MVC and provides an overview of its key concepts and components. The motivations for using MVC include creating clean, maintainable code that is easier to learn, leverage tooling for, and collaborate on. It then covers the basic components of MVC - views, models, stores, and controllers. Views should be balanced to avoid having too many or too few. Models represent types of data, stores manage that data, and controllers tie everything together by figuring out responsibilities, setting references, and listening to events.
How to choose a framework
This document discusses factors to consider when choosing a frontend framework, including the team and its evolution, popular JavaScript frameworks like Angular and Ember, and how the framework choice impacts code, testing, documentation, contributions, and recruitment. It recommends that some framework is needed but the developer must decide whether to use an existing one or build their own, considering support and how the framework may change over time.
Automated Testing: Obstacles, Pitfalls, and Dangers
The document discusses the motivation, principles, and obstacles of automated testing. It motivates automated testing by noting how it provides visibility into problems, detects issues early, and acts as an advance warning system. The principles discussed are having tests that are zero configuration, fast, provide clear results, and are easy to maintain. Obstacles covered include tests becoming too specific over time, reliance on system time/date, dependency on databases changing test data, and tests becoming too coupled through overuse of reuse. Examples are provided to illustrate the points.
Владимир Бронников (Senior .NET Developer, Perfectial) “Performance optimizat...
Владимир Бронников (Senior .NET Developer, Perfectial) “Performance optimization tips and tricks for .NET web applications. Practical experience”
Sahi Conference
Sahi is an open source web automation and testing tool. It uses JavaScript to automate tests on web applications from a proxy server, independently of the specific website. Some key features include support for scheduling test actions, suites that can run in multiple threads, and advantages over other tools like support for Ant, no proprietary language, and an active community.
Design Reviews for Operations - Velocity Europe 2014
This document outlines best practices for conducting design reviews. It recommends reviewing applications layer by layer to understand deployment, operations, releases and outages. It provides a checklist of topics to cover including technologies, configurations, dependencies, monitoring, backups and contact information. Regular design reviews help operations teams understand new projects and provide input to support deployments and ongoing management.
Usability Testing - Adding a New Level to Your Toolbox
How many times have you seen a website or application stumble or crash once it gets to production, despite meeting the requirements perfectly? Have you felt like there was something missing in the development process? In this presentation, Norm Sun will talk about what usability testing is, why you should be doing it, and how you can start incorporating it into your development process.
Software Agility.pptx
This document discusses software agility. It begins by explaining why software agility is needed, such as to quickly deliver valuable products and respond to customer needs. It then discusses how software agility can be achieved, including choosing an agile framework, focusing on deliverables and speed, and changing organizational culture. Finally, it defines software agility, discusses common agile frameworks and methodologies, provides tips for choosing the right framework, and notes some common myths about agility.
The what, when, why and how of usability
The document provides an overview of usability testing and techniques. It discusses what usability is, when to conduct testing, and how different techniques like expert reviews, user testing, eye tracking, card sorting and paper prototyping work. The author is a senior user experience consultant who provides these services to help evaluate designs and ensure they meet users' needs.
Design Review Best Practices - SREcon 2014
Design reviews are the foundation for a successful product or feature launch. In this session we will broach a few of the critical questions an SRE asks during the design review process to ensure the design and deployment will result in a sustainable system. We will cover real world examples of the pitfalls of not engaging the operations/infrastructure team early in the process.
Software Engineering - Trends & Industry Practices
My short talk about trends and industry practices in Software Engineering in one of the classes in Master of Science in Information Technology at Ateneo de Davao University
Software Standards
This document discusses software standards, including:
- De jure standards are formally defined and documented standards developed through a rigorous process by independent standards bodies, while de facto standards emerge through widespread use but are managed by an individual organization.
- Standards can be open, allowing public participation, or closed/proprietary, only allowing participation by the standard's custodians.
- Software standards are important for interoperability, reusability, tool support, and economies of scale, but when adopting a standard there are tradeoffs between being an early influencer versus waiting for maturity.
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...Business of Software Conference
This document discusses strategies for scaling software development teams while minimizing technical debt. It advocates separating teams into roles including developers, team leaders, and engineering managers. Team leaders are responsible for driving cadence and morale, ensuring deadlines are met, and mentoring developers. Engineering managers focus on skills development and removing barriers. Regular, predictable delivery of features through steady cadence is emphasized over long release cycles to reduce technical debt. Separating concerns like architecture from UI helps determine appropriate processes along the agile-waterfall spectrum.Load testing with Visual Studio and Azure - Andrew Siemer
In this presentation we will look at what web performance testing is and the various types of testing that can be performed. We will then dig into Visual Studio 2013 Ultimate to see that the Visual Studio platform is now a real contender in performance testing automation. And we will see how the Visual Studio integration with Visual Studio Online and Azure can take your web performance tests and spin up impressive load tests in a truly useful way.
From User Personas to Testing: A Project Manager's Journey Towards Behat
With a strong desire to reduce our technical & product debt, or at the very least stop adding more, our team explored options to optimize our QA process. We have landed at the beginning of a new journey starting with user personas and ending with automated testing; behavior driven development (BDD) focuses on the users' experience as the primary deliverable.
"Behat is a tool that makes behavior driven development (BDD) possible. With BDD, you write human-readable stories that describe the behavior of your application. These stories can then be auto-tested against your application. And yes, it’s as cool as it sounds!"
The Process
- Create personas. Understand "who" is your user base.
- Write user stories. Figure out what they need/want.
- Write Behat tests. Make the desired outcome testable.
- Develop features. Match your specifications.
- Run Behat test suites. Confirm you didn't break any existing functionality.
In addition to giving detailed examples, showing snippets of "human-readable" code, and running tests, I'll share approaches to reach optimal code coverage.
I am pleased to share this collaboration framework that allows stake holders, developers and everyone in between to finally speak the same language. Easily defined and agreed upon goals, written by both the planning and development teams means a target that can be reached.
Adressing nfr-with-agile-practices (english) - dec 16th
The document discusses addressing non-functional requirements with agile practices. It defines non-functional requirements as specifying how well functional requirements must behave. Non-functional requirements are divided into external quality, like performance and usability, and internal quality, like maintainability and testability. External quality is addressed through expectations, which impose measurable constraints. Internal quality is ensured through engineering practices applied during development. The document provides examples of expectations and practices and recommends storing requirements and linking them to ensure they are addressed.
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Ensuring customer success is the the highest priority when we engage with customers. We need to strive to get the customers into production within the shortest time possible to make sure they have sustainable use of WSO2 products. The key to success is to understand the right products for the solution, define an iterative architecture, come up with an agile engagement model and define clarity in terms of scope and acceptance.
The WSO2 Delivery team is well experienced in ensuring customer success with their experiences in the support and services space. Join this session to learn how to best position WSO2 products and learn some best practices in the engagement models.
SOFTWARE ENGINEERING CONCEPT2.pptx
The document discusses various topics related to software engineering concepts including software development methodologies, requirements analysis, SWOT analysis, marketing mix (4Ps), software architecture, software testing, and test case preparation. It provides descriptions and comparisons of different software development methodologies like waterfall model, agile model, RAD model, spiral model, and scrum model. It also discusses software requirement analysis process, questions to consider for SWOT analysis, principles of software architecture around cohesion and coupling, and key fields to include in a test case.
Lifecycle Management with SharePoint Apps and Solutions
The document discusses application lifecycle management (ALM) from the perspective of SharePoint apps and solutions. It covers the main ALM phases including requirements management, software architecture, computer programming, software testing, release management, and software maintenance. Specific techniques are discussed for each phase as they relate to developing SharePoint apps and solutions, such as using Visual Studio, Office 365, and provider-hosted apps. The overall goal is to discuss best practices for managing the lifecycle of SharePoint customizations.
Test planning and software's engineering
The document discusses test planning and management. It covers topics like test strategy, test plan, test automation, mutation testing, defects in software engineering, manual vs automation testing challenges, skills of quality testers, agile testing, and the Selenium testing tool. It provides information on creating test plans according to IEEE standards and discusses the components, requirements, and benefits of test automation frameworks and tools.
Is there a Golden Ratio? Test Specialist to Developer in an Agile team
The document discusses developer to tester ratios on Agile teams. It notes that Agile teams typically include developers, testers, a Scrum Master, and Product Owner. Ratios can be higher in Agile development than non-Agile projects. Effective ratios depend on factors like the project phase and automation level. Cross-functional teams with specialized skills but no strict roles can adapt ratios easily between 1:1 and 4:1 or 8:1. This flexibility and solutions like crowd testing can help speed Agile adoption.
Accessibility Team of Zero
This document discusses tips for improving accessibility at small companies without dedicated accessibility teams. It recommends (1) focusing on changes that individual employees can control, like design and testing, (2) learning required accessibility standards, (3) conducting accessibility testing using free tools to identify issues, (4) organizing issues by type to identify patterns, (5) prioritizing fixes for major roadblocks, (6) scheduling fixes in releases, and (7) educating other employees about accessibility best practices. The overall message is that small teams can make progress on accessibility by leveraging individual efforts and taking a systematic approach to testing, organizing, and fixing accessibility issues over time.
Technical guidance in SaaS Startups
The document provides technical guidance for SaaS startups. It discusses challenges startups face like short funding runways and high failure rates. It recommends rapid prototyping techniques to quickly validate ideas. The document advises forming skilled teams and establishing best practices for version control, testing, and scalability. It also covers multi-tenancy, APIs, analytics, security, and balancing quality with timing to quickly obtain user feedback. The overarching message is to quickly build minimum viable products and prioritize early user validation over perfection.
Modern Perspectives on Recommender Systems and their Applications in Mendeley
Presentation given for one of Pearson's Data Research teams. It motivates the use of recommender systems, describes common approaches to building and evaluating them and gives examples of how they are used in Mendeley. Joint work with Kris Jack, Chief Data Scientist at Mendeley.
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck Hub
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck HubBlack Duck by Synopsys
This document provides an overview of open source license management best practices that have evolved over 16 years, from 2002 to 2018. It discusses how the risks have changed from lawsuits prompting code inspections to security vulnerabilities coming to the forefront. It also outlines the key functionality of Black Duck Hub for managing open source licenses, including predefined license groups, component usage settings, license risk modeling, policy management, license review workflows, and integrations. Finally, it proposes a suggested license management workflow involving license planning, policy creation, component reviews, attribution statements, and more.How to use SELINUX (No I don't mean turn it off)
Why do we turn off NSA-grade security features? Well early on, SELINUX was complex and confusing. However, the pains of dealing with SELINUX are long gone. In fact, the tools for working with SELINUX have long improved are now so easy, anyone can configure the security layer. Even one bad chmod on a server can leave you vulnerable. However, when SELINUX is running, rogue processes will be prevented from running havoc. You'll learn how easy it is to use SELINUX and how (with little effort) you can configure and troubleshoot this amazing security feature. Stop leaving gaps in your infrastructure and turn it back on.
Stop multiplying by 4 Laracon
Many developers are often asked by project owners to give time estimates for features or bug fixes. But how many developers have the ability to provide project owners a reasonable estimate? Many developers will just follow irrational formulas or arbitrary methods to create a number that is not only wrong, but costly. "Stop Multiplying by 4" will teach developers of all skill levels easy techniques to provide accurate estimations. We will start with a small calibration exercise to find out how good you are. We will then go over procedures to improve accuracy . At the end of the talk, you will possess the skills to get you started on improving the certainty of your estimates.
More Related Content
Similar to Software requirements and estimates
Design Reviews for Operations - Velocity Europe 2014
This document outlines best practices for conducting design reviews. It recommends reviewing applications layer by layer to understand deployment, operations, releases and outages. It provides a checklist of topics to cover including technologies, configurations, dependencies, monitoring, backups and contact information. Regular design reviews help operations teams understand new projects and provide input to support deployments and ongoing management.
Usability Testing - Adding a New Level to Your Toolbox
How many times have you seen a website or application stumble or crash once it gets to production, despite meeting the requirements perfectly? Have you felt like there was something missing in the development process? In this presentation, Norm Sun will talk about what usability testing is, why you should be doing it, and how you can start incorporating it into your development process.
Software Agility.pptx
This document discusses software agility. It begins by explaining why software agility is needed, such as to quickly deliver valuable products and respond to customer needs. It then discusses how software agility can be achieved, including choosing an agile framework, focusing on deliverables and speed, and changing organizational culture. Finally, it defines software agility, discusses common agile frameworks and methodologies, provides tips for choosing the right framework, and notes some common myths about agility.
The what, when, why and how of usability
The document provides an overview of usability testing and techniques. It discusses what usability is, when to conduct testing, and how different techniques like expert reviews, user testing, eye tracking, card sorting and paper prototyping work. The author is a senior user experience consultant who provides these services to help evaluate designs and ensure they meet users' needs.
Design Review Best Practices - SREcon 2014
Design reviews are the foundation for a successful product or feature launch. In this session we will broach a few of the critical questions an SRE asks during the design review process to ensure the design and deployment will result in a sustainable system. We will cover real world examples of the pitfalls of not engaging the operations/infrastructure team early in the process.
Software Engineering - Trends & Industry Practices
My short talk about trends and industry practices in Software Engineering in one of the classes in Master of Science in Information Technology at Ateneo de Davao University
Software Standards
This document discusses software standards, including:
- De jure standards are formally defined and documented standards developed through a rigorous process by independent standards bodies, while de facto standards emerge through widespread use but are managed by an individual organization.
- Standards can be open, allowing public participation, or closed/proprietary, only allowing participation by the standard's custodians.
- Software standards are important for interoperability, reusability, tool support, and economies of scale, but when adopting a standard there are tradeoffs between being an early influencer versus waiting for maturity.
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...Business of Software Conference
This document discusses strategies for scaling software development teams while minimizing technical debt. It advocates separating teams into roles including developers, team leaders, and engineering managers. Team leaders are responsible for driving cadence and morale, ensuring deadlines are met, and mentoring developers. Engineering managers focus on skills development and removing barriers. Regular, predictable delivery of features through steady cadence is emphasized over long release cycles to reduce technical debt. Separating concerns like architecture from UI helps determine appropriate processes along the agile-waterfall spectrum.Load testing with Visual Studio and Azure - Andrew Siemer
In this presentation we will look at what web performance testing is and the various types of testing that can be performed. We will then dig into Visual Studio 2013 Ultimate to see that the Visual Studio platform is now a real contender in performance testing automation. And we will see how the Visual Studio integration with Visual Studio Online and Azure can take your web performance tests and spin up impressive load tests in a truly useful way.
From User Personas to Testing: A Project Manager's Journey Towards Behat
With a strong desire to reduce our technical & product debt, or at the very least stop adding more, our team explored options to optimize our QA process. We have landed at the beginning of a new journey starting with user personas and ending with automated testing; behavior driven development (BDD) focuses on the users' experience as the primary deliverable.
"Behat is a tool that makes behavior driven development (BDD) possible. With BDD, you write human-readable stories that describe the behavior of your application. These stories can then be auto-tested against your application. And yes, it’s as cool as it sounds!"
The Process
- Create personas. Understand "who" is your user base.
- Write user stories. Figure out what they need/want.
- Write Behat tests. Make the desired outcome testable.
- Develop features. Match your specifications.
- Run Behat test suites. Confirm you didn't break any existing functionality.
In addition to giving detailed examples, showing snippets of "human-readable" code, and running tests, I'll share approaches to reach optimal code coverage.
I am pleased to share this collaboration framework that allows stake holders, developers and everyone in between to finally speak the same language. Easily defined and agreed upon goals, written by both the planning and development teams means a target that can be reached.
Adressing nfr-with-agile-practices (english) - dec 16th
The document discusses addressing non-functional requirements with agile practices. It defines non-functional requirements as specifying how well functional requirements must behave. Non-functional requirements are divided into external quality, like performance and usability, and internal quality, like maintainability and testability. External quality is addressed through expectations, which impose measurable constraints. Internal quality is ensured through engineering practices applied during development. The document provides examples of expectations and practices and recommends storing requirements and linking them to ensure they are addressed.
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Ensuring customer success is the the highest priority when we engage with customers. We need to strive to get the customers into production within the shortest time possible to make sure they have sustainable use of WSO2 products. The key to success is to understand the right products for the solution, define an iterative architecture, come up with an agile engagement model and define clarity in terms of scope and acceptance.
The WSO2 Delivery team is well experienced in ensuring customer success with their experiences in the support and services space. Join this session to learn how to best position WSO2 products and learn some best practices in the engagement models.
SOFTWARE ENGINEERING CONCEPT2.pptx
The document discusses various topics related to software engineering concepts including software development methodologies, requirements analysis, SWOT analysis, marketing mix (4Ps), software architecture, software testing, and test case preparation. It provides descriptions and comparisons of different software development methodologies like waterfall model, agile model, RAD model, spiral model, and scrum model. It also discusses software requirement analysis process, questions to consider for SWOT analysis, principles of software architecture around cohesion and coupling, and key fields to include in a test case.
Lifecycle Management with SharePoint Apps and Solutions
The document discusses application lifecycle management (ALM) from the perspective of SharePoint apps and solutions. It covers the main ALM phases including requirements management, software architecture, computer programming, software testing, release management, and software maintenance. Specific techniques are discussed for each phase as they relate to developing SharePoint apps and solutions, such as using Visual Studio, Office 365, and provider-hosted apps. The overall goal is to discuss best practices for managing the lifecycle of SharePoint customizations.
Test planning and software's engineering
The document discusses test planning and management. It covers topics like test strategy, test plan, test automation, mutation testing, defects in software engineering, manual vs automation testing challenges, skills of quality testers, agile testing, and the Selenium testing tool. It provides information on creating test plans according to IEEE standards and discusses the components, requirements, and benefits of test automation frameworks and tools.
Is there a Golden Ratio? Test Specialist to Developer in an Agile team
The document discusses developer to tester ratios on Agile teams. It notes that Agile teams typically include developers, testers, a Scrum Master, and Product Owner. Ratios can be higher in Agile development than non-Agile projects. Effective ratios depend on factors like the project phase and automation level. Cross-functional teams with specialized skills but no strict roles can adapt ratios easily between 1:1 and 4:1 or 8:1. This flexibility and solutions like crowd testing can help speed Agile adoption.
Accessibility Team of Zero
This document discusses tips for improving accessibility at small companies without dedicated accessibility teams. It recommends (1) focusing on changes that individual employees can control, like design and testing, (2) learning required accessibility standards, (3) conducting accessibility testing using free tools to identify issues, (4) organizing issues by type to identify patterns, (5) prioritizing fixes for major roadblocks, (6) scheduling fixes in releases, and (7) educating other employees about accessibility best practices. The overall message is that small teams can make progress on accessibility by leveraging individual efforts and taking a systematic approach to testing, organizing, and fixing accessibility issues over time.
Technical guidance in SaaS Startups
The document provides technical guidance for SaaS startups. It discusses challenges startups face like short funding runways and high failure rates. It recommends rapid prototyping techniques to quickly validate ideas. The document advises forming skilled teams and establishing best practices for version control, testing, and scalability. It also covers multi-tenancy, APIs, analytics, security, and balancing quality with timing to quickly obtain user feedback. The overarching message is to quickly build minimum viable products and prioritize early user validation over perfection.
Modern Perspectives on Recommender Systems and their Applications in Mendeley
Presentation given for one of Pearson's Data Research teams. It motivates the use of recommender systems, describes common approaches to building and evaluating them and gives examples of how they are used in Mendeley. Joint work with Kris Jack, Chief Data Scientist at Mendeley.
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck Hub
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck HubBlack Duck by Synopsys
This document provides an overview of open source license management best practices that have evolved over 16 years, from 2002 to 2018. It discusses how the risks have changed from lawsuits prompting code inspections to security vulnerabilities coming to the forefront. It also outlines the key functionality of Black Duck Hub for managing open source licenses, including predefined license groups, component usage settings, license risk modeling, policy management, license review workflows, and integrations. Finally, it proposes a suggested license management workflow involving license planning, policy creation, component reviews, attribution statements, and more.Similar to Software requirements and estimates (20)
Design Reviews for Operations - Velocity Europe 2014
Design Reviews for Operations - Velocity Europe 2014
Usability Testing - Adding a New Level to Your Toolbox
Usability Testing - Adding a New Level to Your Toolbox
Software Engineering - Trends & Industry Practices
Software Engineering - Trends & Industry Practices
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
Load testing with Visual Studio and Azure - Andrew Siemer
Load testing with Visual Studio and Azure - Andrew Siemer
From User Personas to Testing: A Project Manager's Journey Towards Behat
From User Personas to Testing: A Project Manager's Journey Towards Behat
Adressing nfr-with-agile-practices (english) - dec 16th
Adressing nfr-with-agile-practices (english) - dec 16th
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Lifecycle Management with SharePoint Apps and Solutions
Lifecycle Management with SharePoint Apps and Solutions
Is there a Golden Ratio? Test Specialist to Developer in an Agile team
Is there a Golden Ratio? Test Specialist to Developer in an Agile team
Modern Perspectives on Recommender Systems and their Applications in Mendeley
Modern Perspectives on Recommender Systems and their Applications in Mendeley
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck Hub
FLIGHT WEST 2018 Presentation - Open Source License Management in Black Duck Hub
More from Chuck Reeves
How to use SELINUX (No I don't mean turn it off)
Why do we turn off NSA-grade security features? Well early on, SELINUX was complex and confusing. However, the pains of dealing with SELINUX are long gone. In fact, the tools for working with SELINUX have long improved are now so easy, anyone can configure the security layer. Even one bad chmod on a server can leave you vulnerable. However, when SELINUX is running, rogue processes will be prevented from running havoc. You'll learn how easy it is to use SELINUX and how (with little effort) you can configure and troubleshoot this amazing security feature. Stop leaving gaps in your infrastructure and turn it back on.
Stop multiplying by 4 Laracon
Many developers are often asked by project owners to give time estimates for features or bug fixes. But how many developers have the ability to provide project owners a reasonable estimate? Many developers will just follow irrational formulas or arbitrary methods to create a number that is not only wrong, but costly. "Stop Multiplying by 4" will teach developers of all skill levels easy techniques to provide accurate estimations. We will start with a small calibration exercise to find out how good you are. We will then go over procedures to improve accuracy . At the end of the talk, you will possess the skills to get you started on improving the certainty of your estimates.
Stop multiplying by 4 Lone Star PHP
Many developers are often asked by project owners to give time estimates for features or bug fixes. But how many developers have the ability to provide project owners a reasonable estimate? Many developers will just follow irrational formulas or arbitrary methods to create a number that is not only wrong, but costly. "Stop Multiplying by 4" will teach developers of all skill levels easy techniques to provide accurate estimations. We will start with a small calibration exercise to find out how good you are. We will then go over procedures to improve accuracy. At the end of the talk, you will possess the skills to get you started on improving the certainty of your estimates.
Single page Apps with Angular and Apigility
This document discusses building single page applications using Angular and Apigility. It introduces Apigility as a REST API framework and Angular as a frontend framework. It then covers topics such as whether to make the Angular app public or bundle it as an asset, using Grunt for building, and Restangular for Angular-REST communication. The document ends by providing links to the Apigility, Angular, and Restangular websites as well as a link to view the full talk.
Zend Framework Foundations
Have you been working with other frameworks and feel ready to try something new? Why not try Zend Framework? Not only can you use it for the full stack of your application, but you can pull out the individual components into your existing application. Get ready for a course on how to build an ZF2 application from the ground up — from the basics of an MVC app to the more advanced components. When you leave this tutorial, you will have a great grasp on how the framework is structured
Stop multiplying by 4 nyphp
The document discusses techniques for estimating software development timelines. It recommends doubling the initial time estimate and rounding up to the next unit on the time scale. Factors like involving other people and unexpected issues mean schedules are difficult to accurately predict. Breaking tasks down into smaller parts and using historical data, testing, and confidence intervals can help. Prioritization methods include urgency matrices and spreadsheets weighing factors like benefits, costs, and risks. The document provides references for further reading on software estimation.
Stop multiplying by 4 PHP Tour 2014
The document discusses various techniques for estimating software project timelines and schedules. It recommends doubling your initial time estimate and then rounding up to the next unit on the time scale (e.g. hours to days). It also stresses accounting for impediments by padding estimates. Other estimation techniques mentioned include defining parameters, using historical data, confidence intervals, fuzzy logic based on lines of code, the Delphi method, and prioritizing requirements based on factors like benefit, penalty, cost and risk. The document recommends preferring hour estimates over days for easier scaling and warns against assuming more developers will solve scheduling problems or negotiating estimates. It provides references for further reading on software estimation.
Stop multiplying by 4: Practical Software Estimation
The document provides tips and techniques for estimating software development timelines. It recommends doubling the initial time estimate and rounding up to the next unit to account for uncertainties. Key aspects to define include requirements, parameters to validate, and historical data. Estimates should have confidence intervals rather than precise figures. Prioritization involves assessing features' relative benefits, costs and risks to determine priority. Communication and removing personal biases are also important.
How x debug restored partial sanity to the insane
The document discusses the XDebug PHP debugging tool, including how it provides debugging capabilities like breakpoints and navigation that bring sanity to PHP development. It covers XDebug's installation, features like variable inspection and profiling, and references Eclipse and PHP as related tools. The document provides logos and images from XDebug, Eclipse, and PHP sites to accompany the text.
More from Chuck Reeves (9)
Stop multiplying by 4: Practical Software Estimation
Stop multiplying by 4: Practical Software Estimation
Recently uploaded
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Essentials of Automations: Exploring Attributes & Automation Parameters
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
A Deep Dive into ScyllaDB's Architecture
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
Getting the Most Out of ScyllaDB Monitoring: ShareChat's Tips
ScyllaDB monitoring provides a lot of useful information. But sometimes it’s not easy to find the root of the problem if something is wrong or even estimate the remaining capacity by the load on the cluster. This talk shares our team's practical tips on: 1) How to find the root of the problem by metrics if ScyllaDB is slow 2) How to interpret the load and plan capacity for the future 3) Compaction strategies and how to choose the right one 4) Important metrics which aren’t available in the default monitoring setup.
Day 2 - Intro to UiPath Studio Fundamentals
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
From Natural Language to Structured Solr Queries using LLMs
This talk draws on experimentation to enable AI applications with Solr. One important use case is to use AI for better accessibility and discoverability of the data: while User eXperience techniques, lexical search improvements, and data harmonization can take organizations to a good level of accessibility, a structural (or “cognitive” gap) remains between the data user needs and the data producer constraints.
That is where AI – and most importantly, Natural Language Processing and Large Language Model techniques – could make a difference. This natural language, conversational engine could facilitate access and usage of the data leveraging the semantics of any data source.
The objective of the presentation is to propose a technical approach and a way forward to achieve this goal.
The key concept is to enable users to express their search queries in natural language, which the LLM then enriches, interprets, and translates into structured queries based on the Solr index’s metadata.
This approach leverages the LLM’s ability to understand the nuances of natural language and the structure of documents within Apache Solr.
The LLM acts as an intermediary agent, offering a transparent experience to users automatically and potentially uncovering relevant documents that conventional search methods might overlook. The presentation will include the results of this experimental work, lessons learned, best practices, and the scope of future work that should improve the approach and make it production-ready.
What is an RPA CoE? Session 1 – CoE Vision
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Gursev Pirge, PhD
Senior Data Scientist - JohnSnowLabs
MySQL InnoDB Storage Engine: Deep Dive - Mydbops
This presentation, titled "MySQL - InnoDB" and delivered by Mayank Prasad at the Mydbops Open Source Database Meetup 16 on June 8th, 2024, covers dynamic configuration of REDO logs and instant ADD/DROP columns in InnoDB.
This presentation dives deep into the world of InnoDB, exploring two ground-breaking features introduced in MySQL 8.0:
• Dynamic Configuration of REDO Logs: Enhance your database's performance and flexibility with on-the-fly adjustments to REDO log capacity. Unleash the power of the snake metaphor to visualize how InnoDB manages REDO log files.
• Instant ADD/DROP Columns: Say goodbye to costly table rebuilds! This presentation unveils how InnoDB now enables seamless addition and removal of columns without compromising data integrity or incurring downtime.
Key Learnings:
• Grasp the concept of REDO logs and their significance in InnoDB's transaction management.
• Discover the advantages of dynamic REDO log configuration and how to leverage it for optimal performance.
• Understand the inner workings of instant ADD/DROP columns and their impact on database operations.
• Gain valuable insights into the row versioning mechanism that empowers instant column modifications.
GlobalLogic Java Community Webinar #18 “How to Improve Web Application Perfor...
Під час доповіді відповімо на питання, навіщо потрібно підвищувати продуктивність аплікації і які є найефективніші способи для цього. А також поговоримо про те, що таке кеш, які його види бувають та, основне — як знайти performance bottleneck?
Відео та деталі заходу: https://bit.ly/45tILxj
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation F...
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation Functions to Prevent Interaction with Malicious QR Codes.
Aim of the Study: The goal of this research was to develop a robust hybrid approach for identifying malicious and insecure URLs derived from QR codes, ensuring safe interactions.
This is achieved through:
Machine Learning Model: Predicts the likelihood of a URL being malicious.
Security Validation Functions: Ensures the derived URL has a valid certificate and proper URL format.
This innovative blend of technology aims to enhance cybersecurity measures and protect users from potential threats hidden within QR codes 🖥 🔒
This study was my first introduction to using ML which has shown me the immense potential of ML in creating more secure digital environments!
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
Must Know Postgres Extension for DBA and Developer during Migration
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
Containers & AI - Beauty and the Beast!?!
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Keywords: AI, Containeres, Kubernetes, Cloud Native
Event Link: https://meine.doag.org/events/cloudland/2024/agenda/#agendaId.4211
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdf
So… you want to become a Test Automation Engineer (or hire and develop one)? While there’s quite a bit of information available about important technical and tool skills to master, there’s not enough discussion around the path to becoming an effective Test Automation Engineer that knows how to add VALUE. In my experience this had led to a proliferation of engineers who are proficient with tools and building frameworks but have skill and knowledge gaps, especially in software testing, that reduce the value they deliver with test automation.
In this talk, Lee will share his lessons learned from over 30 years of working with, and mentoring, hundreds of Test Automation Engineers. Whether you’re looking to get started in test automation or just want to improve your trade, this talk will give you a solid foundation and roadmap for ensuring your test automation efforts continuously add value. This talk is equally valuable for both aspiring Test Automation Engineers and those managing them! All attendees will take away a set of key foundational knowledge and a high-level learning path for leveling up test automation skills and ensuring they add value to their organizations.
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Recently uploaded (20)
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Essentials of Automations: Exploring Attributes & Automation Parameters
Essentials of Automations: Exploring Attributes & Automation Parameters
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
Getting the Most Out of ScyllaDB Monitoring: ShareChat's Tips
Getting the Most Out of ScyllaDB Monitoring: ShareChat's Tips
From Natural Language to Structured Solr Queries using LLMs
From Natural Language to Structured Solr Queries using LLMs
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
GlobalLogic Java Community Webinar #18 “How to Improve Web Application Perfor...
GlobalLogic Java Community Webinar #18 “How to Improve Web Application Perfor...
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation F...
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation F...
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
Must Know Postgres Extension for DBA and Developer during Migration
Must Know Postgres Extension for DBA and Developer during Migration
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdf
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdf
Software requirements and estimates
- 1. Software Estimations and Requirements
- 3. Requirements
- 4. Requirements How?
- 6. Requirements Avoid
- 7. Requirements Ambiguous •Acceptable / Adequate •Including / Not Limited Too •As much as Practicable •Several •Between •Shouldn’t •Depends on •State-Of-The-Art •Efficient •Normally •Fast / Rapid •Seamless / Transparent •Flexible •Support •Improved / Better / Faster / •Enable Superior •User Friendly / Simple
- 8. Requirements Use Case •Actors (User) •Priority •Description •Frequency Of Use •Pre-Conditions •Business Rule •Post-Conditions •Special Requirements •Normal Courses •Assumptions •Alternative Courses •Notes and Issues •Exceptions •Includes
- 10. Estimates What is a good Estimate?
- 11. Estimates
- 12. Estimates
- 15. Estimates What Can you do
- 16. Estimates Count Computer Compare
- 18. Citations •Images: •http://blogs.mentor.com/verificationhorizons/blog/author/hfoster/page/2 •http://www.flickr.com/photos/krazydad/4067542/sizes/z/in/photostream •http://www.frontrowreviews.co.uk/editorial/greatest-comic-spoof- movies/5900 •Books: •“Software Estimation” Steve McConnell 0-7356-0535-1 •“Software Requirements” Karl E Weigers 0-7356-1879-8 •References: •https://github.com/pmjones/php-framework-benchmarks •Tools: •Apache Benchmark •PHPMD and PHPUnit •Mylyn
Editor's Notes
- Keeps timeline shortEnsures Proper DeliveryHow names change
- Break up into groups:Business RequirementsBusiness Rules User RequirementsFunctional RequirementsQuality Attributes – Portability Constraints
- Break up into groups:Business RequirementsBusiness Rules User RequirementsFunctional RequirementsQuality Attributes – Portability Constraints
- Identifying the Actors (Users)Ask them what they need (Use case)Understanding the Goal
- Feature CreepGold Plating Ambiguous Terms
- Ambiguous Terms
- Per Requirement
- Change Controls need to be in placeDependencies For requirements will affect change
- Change Controls need to be in placeDependencies For requirements will affect change
- Measure what is mesuarble
- Over:Parkinson's Law (Project will fill the budget)Students Law (Procrastination)Under:Dependency FalloutFailure to Plan (Less time to work less time to plan)Project is late Cause other failures More Meetings Less Development Failure to Deliver Re-prioritization Interim Release Quick and Dirty Workarounds Which introduce bugs
- Describes how accurate an estimate will be in which phase of a projectEarlier in Design more inaccurate the estimate will be (This is based off skilled estimators your estimate will be more uncertin)
- Many Techniques exists but depend on project style
- Count what you canHours / FeatureHours / Web PageHours / Integration Points Hours / ClassesHours / Defects Hours / Complexity (CRAP Index with Unit testing or Cylomatic Complexity with PHP MD)
- Constantly Re-evaluate at every step
- Identifying the Actors (Users)Ask them what they need (Use case)Understanding the Goal