Resource1 spm
•Download as PPTX, PDF•
0 likes•183 views
Extreme Programming (XP) is a widely used agile method that takes an extreme approach to iterative development. It was first started in 1996 and has proven successful for companies of all sizes. Key practices of XP include incremental planning, small releases, test-first development, pair programming, collective ownership, continuous integration, and customer involvement. The customer is part of the development team and helps define requirements, prioritize features, and develop acceptance tests.
Report
Share
Report
Share
Recommended
Resource1 spm
Extreme Programming (XP) is a widely used agile method that takes an extreme approach to iterative development. It was first started in 1996 and has proven successful for companies of all sizes. Customer involvement is key to XP, with the customer part of the development team to help define requirements, prioritize features, and develop acceptance tests.
extreme programming
Extreme Programming (XP) is an agile software development methodology formulated in 1999. It embraces change and values simplicity, communication, feedback, and courage. XP practices include whole team involvement, short planning iterations, customer acceptance tests, small regular releases, test-driven pair programming, continuous integration and refactoring. The goal is sustainable development of high quality, evolving code through frequent feedback and collective code ownership. Critics argue XP is too programmer-focused and unrealistic for large projects.
Devops insights
The document discusses key DevOps principles and practices including continuous integration, continuous delivery, and continuous deployment. It defines each practice, with continuous integration requiring code integration and verification several times a day, continuous deployment automatically releasing any passed code changes, and continuous delivery enabling reliable releases at any time. The document also discusses ways to measure DevOps success, such as release frequency, infrastructure recovery speed, reduction in downtime, efficiency, and increased automation.
Growing Object Oriented Software
The document discusses test-driven development (TDD) and how it helps software development through continuous feedback loops. TDD involves writing automated tests before code is written to drive the development process. This results in code that is modular, well-structured, and easy to modify through refactoring. The process of writing tests first helps clarify requirements and encourages loose coupling between components to facilitate testing. Multiple levels of testing, from unit to acceptance, provide feedback at different stages of development.
Agile A to Z Chapter 4 Feedback Loop Part 2 DevOps
This document discusses DevOps practices for improving software development processes through feedback loops, collaboration, visibility, and shared responsibility. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing strategies, continuous integration, continuous delivery, deployment pipelines, infrastructure considerations, monitoring, analytics, performance, and security. The overall aim is to build, test, and release software faster and more reliably through automation, visibility, and collaboration between teams.
Continuous Integration
The document discusses continuous integration, which describes software engineering practices that decrease integration times and allow for near-immediate feedback. It involves integrating code and running tests after each code commit. This allows errors to be detected rapidly. Benefits include minimizing integration risk, easier defect diagnosis, and enabling good practices like test-driven development.
Selenium and Continuous Intergration
This document discusses full scale automation using Selenium. It covers the history of continuous integration, the key principles of a CI manifest including committing code frequently and fixing broken builds immediately. Continuous integration systems use Selenium to automate main actions like triggering tests, updating code, analyzing results, and deploying changes. Adopting these practices helps reduce risks, remove repetitive manual processes, and establish greater confidence in the software from automated testing.
Agile a to z chapter 4 feedback loop
The document discusses various DevOps practices for improving feedback loops, including breaking down silos, enabling easier collaboration, improving visibility, encouraging more engagement, sharing responsibility and ownership. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing automation, continuous integration, continuous delivery, deployment pipelines, infrastructure and virtualization, application monitoring and alerting, analytics, and application performance monitoring. The overall goal is to establish a feedback loop to find and address issues more quickly in order to improve software quality.
Recommended
Resource1 spm
Extreme Programming (XP) is a widely used agile method that takes an extreme approach to iterative development. It was first started in 1996 and has proven successful for companies of all sizes. Customer involvement is key to XP, with the customer part of the development team to help define requirements, prioritize features, and develop acceptance tests.
extreme programming
Extreme Programming (XP) is an agile software development methodology formulated in 1999. It embraces change and values simplicity, communication, feedback, and courage. XP practices include whole team involvement, short planning iterations, customer acceptance tests, small regular releases, test-driven pair programming, continuous integration and refactoring. The goal is sustainable development of high quality, evolving code through frequent feedback and collective code ownership. Critics argue XP is too programmer-focused and unrealistic for large projects.
Devops insights
The document discusses key DevOps principles and practices including continuous integration, continuous delivery, and continuous deployment. It defines each practice, with continuous integration requiring code integration and verification several times a day, continuous deployment automatically releasing any passed code changes, and continuous delivery enabling reliable releases at any time. The document also discusses ways to measure DevOps success, such as release frequency, infrastructure recovery speed, reduction in downtime, efficiency, and increased automation.
Growing Object Oriented Software
The document discusses test-driven development (TDD) and how it helps software development through continuous feedback loops. TDD involves writing automated tests before code is written to drive the development process. This results in code that is modular, well-structured, and easy to modify through refactoring. The process of writing tests first helps clarify requirements and encourages loose coupling between components to facilitate testing. Multiple levels of testing, from unit to acceptance, provide feedback at different stages of development.
Agile A to Z Chapter 4 Feedback Loop Part 2 DevOps
This document discusses DevOps practices for improving software development processes through feedback loops, collaboration, visibility, and shared responsibility. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing strategies, continuous integration, continuous delivery, deployment pipelines, infrastructure considerations, monitoring, analytics, performance, and security. The overall aim is to build, test, and release software faster and more reliably through automation, visibility, and collaboration between teams.
Continuous Integration
The document discusses continuous integration, which describes software engineering practices that decrease integration times and allow for near-immediate feedback. It involves integrating code and running tests after each code commit. This allows errors to be detected rapidly. Benefits include minimizing integration risk, easier defect diagnosis, and enabling good practices like test-driven development.
Selenium and Continuous Intergration
This document discusses full scale automation using Selenium. It covers the history of continuous integration, the key principles of a CI manifest including committing code frequently and fixing broken builds immediately. Continuous integration systems use Selenium to automate main actions like triggering tests, updating code, analyzing results, and deploying changes. Adopting these practices helps reduce risks, remove repetitive manual processes, and establish greater confidence in the software from automated testing.
Agile a to z chapter 4 feedback loop
The document discusses various DevOps practices for improving feedback loops, including breaking down silos, enabling easier collaboration, improving visibility, encouraging more engagement, sharing responsibility and ownership. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing automation, continuous integration, continuous delivery, deployment pipelines, infrastructure and virtualization, application monitoring and alerting, analytics, and application performance monitoring. The overall goal is to establish a feedback loop to find and address issues more quickly in order to improve software quality.
03. Agile Development
Agile Software Development is a method of software development that works for small projects to provide quick and efficient solution.
Xp Slideshow
Extreme Programming (XP) is a software development methodology that focuses on rapid iterations and frequent feedback. Some key practices of XP include pair programming, small iterative releases, simple design, testing, and planning games. XP values simplicity, communication, respect, and feedback. While XP enables rapid development and adaptation, it may encounter issues with unstable requirements and lack of documentation.
Incremental and iterative stratergy
The document discusses the incremental model of software development. It involves constructing a partial initial implementation and then gradually adding more functionality through subsequent releases. Each release builds on previous ones by delivering additional features. The incremental model allows for early delivery of basic functionality, customer feedback, and a divide and conquer approach. However, it requires good planning, design of the complete system upfront, and well-defined module interfaces. The incremental model is best for projects that need early benefits, lengthy development schedules, or new technologies.
Lets talk about CI CD Pipeline in Agile
Continuous integration is a practice where developers integrate code into a shared repository frequently, such as daily, and automated builds and tests are used to detect errors. Continuous deployment is an approach where teams release software in short cycles to ensure it can be reliably released at any time. The principles of continuous integration and continuous deployment (CI/CD) include automating all build, test and deployment processes; keeping everything in version control; committing code frequently; and not merging broken code. CI/CD aims to release software faster through automation and frequent integration and deployment.
DevOps
This document discusses why organizations are looking at DevOps. It notes that with traditional software development, each new feature added to the testing queue for QA teams to re-test the entire product. This leads to challenges like some test cases being overlooked or defects in the final product. It also discusses how handing code off between development and operations teams for deployment can lead to issues. The document advocates that DevOps is the solution as it allows engineers to focus on programming while automating other tasks like testing, building, and deploying using tools and machines.
Agile Engineering
The document discusses agile engineering practices for software development, including user stories/use cases, test-driven development, continuous integration, precise design, merciless refactoring, collective code ownership, coding conventions, pair programming, code reviews, and steps for adopting agile practices. It provides an overview of each practice and emphasizes adopting test-driven development first when transitioning to agile.
Development and test infrastructure
This document discusses proposed improvements to development and test infrastructure at a Q1 2016 hackfest. It outlines 6 improvements: 1) including more unit testing in verify jobs; 2) using clearer multi-scenario naming conventions; 3) allowing local testing of code changes; 4) updating dashboards automatically; 5) using a node label parameter plugin for lab resource pooling; and 6) implementing an ELK logging system.
Iterative model
The iterative model breaks a project into small modules that can be delivered incrementally. A working version is produced in the first module, with each subsequent release adding additional functionality until the full system is complete. It allows for quick releases during development and makes it easier to develop and test in smaller iterations while incorporating customer feedback at each stage. However, it requires more resources than traditional models and skilled management to avoid increased costs over time.
CI-CD and DevOps with Ruby
DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing
Continous integration
At J and Beyond 2011, I presented a session about using Continuous integration processes during Joomla and PHP development. I present the concepts of CI, and give some direction where to start setting it up yourself.
Using Continuous Integration To Ensure Project Health New
This document discusses the principles and practices of continuous integration. Continuous integration involves developers integrating code changes frequently, at least daily, and having an automated build and test process to verify the code integration and detect errors early. It emphasizes source control, automated builds, self-testing builds, automated deployment, and using a continuous integration server to manage the process.
DevOps Tactical Adoption Theory: Continuous Testing
DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, our model indicates concrete activities rather than general statements.
Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
In the session, it is planned to demonstrate “DevOps Tactical Adoption Theory” with focus on Delivery Pipeline/Testing Practices sectioned "Continuous Testing in DevOps".
Continous Integration: A Case Study
One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool.
The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.
continous integration and delivery
This document discusses continuous integration (CI), continuous delivery (CD), and DevOps. It defines CI as integrating code changes frequently, such as daily, and verifying them through automated builds and tests. CD builds on CI by making software deployable at any time by prioritizing deployments over new features and enabling anyone to deploy any version on demand. For developers, CD provides immediate feedback and the ability to test in production-like environments. For system admins, CD allows automating environments for developer testing. For businesses, CD lowers deployment risks and improves market responsiveness.
Continuous integration
Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.
Test Like A Badger
The document provides guidance on establishing an effective testing strategy that utilizes both manual and automated testing. It advocates that manual testing is time-consuming and reduces productivity and confidence, while automated testing improves maintenance, feedback, and regression when implemented properly. The key steps outlined are gaining stakeholder buy-in, building quality into the process, focusing initial automation on builds and unit tests, adding integration and acceptance testing, and establishing visibility and accountability measures.
Agile Evolution
Presentation from AgileEE 2012 in Kiev (October 2012) and XP Days Ukraine 2012 in Kiev (November 2012) about evolution of Agile processes in team during project lifecycle.
Continuous Integration
Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.
Presentation_TDD
TDD is a process where test code is written before or alongside production code to drive the design and development of a project. It involves writing automated unit tests to force decoupling of dependencies and provide comprehensive testing. TDD helps think through requirements and design before coding to catch early bugs. It is an incremental process where tests are written and run continuously to build confidence with each new feature added. The key steps are to write a test, make it compile even if it fails, run it to failure, implement the code to pass the test, then refactor and repeat the process.
Cloud for Agile Testing - Burak Koyuncu
This document discusses using cloud testing for agile development. It introduces agile principles and practices like continuous integration. It then discusses how the cloud allows automated cross-browser testing across different browsers and platforms in parallel. This saves time compared to local testing. Cloud testing services can integrate with CI systems and provide detailed reports. They allow testing on many browser and OS combinations, mobile load testing, and integrating with monitoring tools.
Lightning Talk on Mobile Access at Leeds Met
Slides from my lightning talk at the Mobile technologies in libraries: information sharing event in Birmingham on the 08/05/2012
More Related Content
What's hot
03. Agile Development
Agile Software Development is a method of software development that works for small projects to provide quick and efficient solution.
Xp Slideshow
Extreme Programming (XP) is a software development methodology that focuses on rapid iterations and frequent feedback. Some key practices of XP include pair programming, small iterative releases, simple design, testing, and planning games. XP values simplicity, communication, respect, and feedback. While XP enables rapid development and adaptation, it may encounter issues with unstable requirements and lack of documentation.
Incremental and iterative stratergy
The document discusses the incremental model of software development. It involves constructing a partial initial implementation and then gradually adding more functionality through subsequent releases. Each release builds on previous ones by delivering additional features. The incremental model allows for early delivery of basic functionality, customer feedback, and a divide and conquer approach. However, it requires good planning, design of the complete system upfront, and well-defined module interfaces. The incremental model is best for projects that need early benefits, lengthy development schedules, or new technologies.
Lets talk about CI CD Pipeline in Agile
Continuous integration is a practice where developers integrate code into a shared repository frequently, such as daily, and automated builds and tests are used to detect errors. Continuous deployment is an approach where teams release software in short cycles to ensure it can be reliably released at any time. The principles of continuous integration and continuous deployment (CI/CD) include automating all build, test and deployment processes; keeping everything in version control; committing code frequently; and not merging broken code. CI/CD aims to release software faster through automation and frequent integration and deployment.
DevOps
This document discusses why organizations are looking at DevOps. It notes that with traditional software development, each new feature added to the testing queue for QA teams to re-test the entire product. This leads to challenges like some test cases being overlooked or defects in the final product. It also discusses how handing code off between development and operations teams for deployment can lead to issues. The document advocates that DevOps is the solution as it allows engineers to focus on programming while automating other tasks like testing, building, and deploying using tools and machines.
Agile Engineering
The document discusses agile engineering practices for software development, including user stories/use cases, test-driven development, continuous integration, precise design, merciless refactoring, collective code ownership, coding conventions, pair programming, code reviews, and steps for adopting agile practices. It provides an overview of each practice and emphasizes adopting test-driven development first when transitioning to agile.
Development and test infrastructure
This document discusses proposed improvements to development and test infrastructure at a Q1 2016 hackfest. It outlines 6 improvements: 1) including more unit testing in verify jobs; 2) using clearer multi-scenario naming conventions; 3) allowing local testing of code changes; 4) updating dashboards automatically; 5) using a node label parameter plugin for lab resource pooling; and 6) implementing an ELK logging system.
Iterative model
The iterative model breaks a project into small modules that can be delivered incrementally. A working version is produced in the first module, with each subsequent release adding additional functionality until the full system is complete. It allows for quick releases during development and makes it easier to develop and test in smaller iterations while incorporating customer feedback at each stage. However, it requires more resources than traditional models and skilled management to avoid increased costs over time.
CI-CD and DevOps with Ruby
DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing
Continous integration
At J and Beyond 2011, I presented a session about using Continuous integration processes during Joomla and PHP development. I present the concepts of CI, and give some direction where to start setting it up yourself.
Using Continuous Integration To Ensure Project Health New
This document discusses the principles and practices of continuous integration. Continuous integration involves developers integrating code changes frequently, at least daily, and having an automated build and test process to verify the code integration and detect errors early. It emphasizes source control, automated builds, self-testing builds, automated deployment, and using a continuous integration server to manage the process.
DevOps Tactical Adoption Theory: Continuous Testing
DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, our model indicates concrete activities rather than general statements.
Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
In the session, it is planned to demonstrate “DevOps Tactical Adoption Theory” with focus on Delivery Pipeline/Testing Practices sectioned "Continuous Testing in DevOps".
Continous Integration: A Case Study
One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool.
The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.
continous integration and delivery
This document discusses continuous integration (CI), continuous delivery (CD), and DevOps. It defines CI as integrating code changes frequently, such as daily, and verifying them through automated builds and tests. CD builds on CI by making software deployable at any time by prioritizing deployments over new features and enabling anyone to deploy any version on demand. For developers, CD provides immediate feedback and the ability to test in production-like environments. For system admins, CD allows automating environments for developer testing. For businesses, CD lowers deployment risks and improves market responsiveness.
Continuous integration
Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.
Test Like A Badger
The document provides guidance on establishing an effective testing strategy that utilizes both manual and automated testing. It advocates that manual testing is time-consuming and reduces productivity and confidence, while automated testing improves maintenance, feedback, and regression when implemented properly. The key steps outlined are gaining stakeholder buy-in, building quality into the process, focusing initial automation on builds and unit tests, adding integration and acceptance testing, and establishing visibility and accountability measures.
Agile Evolution
Presentation from AgileEE 2012 in Kiev (October 2012) and XP Days Ukraine 2012 in Kiev (November 2012) about evolution of Agile processes in team during project lifecycle.
Continuous Integration
Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.
Presentation_TDD
TDD is a process where test code is written before or alongside production code to drive the design and development of a project. It involves writing automated unit tests to force decoupling of dependencies and provide comprehensive testing. TDD helps think through requirements and design before coding to catch early bugs. It is an incremental process where tests are written and run continuously to build confidence with each new feature added. The key steps are to write a test, make it compile even if it fails, run it to failure, implement the code to pass the test, then refactor and repeat the process.
Cloud for Agile Testing - Burak Koyuncu
This document discusses using cloud testing for agile development. It introduces agile principles and practices like continuous integration. It then discusses how the cloud allows automated cross-browser testing across different browsers and platforms in parallel. This saves time compared to local testing. Cloud testing services can integrate with CI systems and provide detailed reports. They allow testing on many browser and OS combinations, mobile load testing, and integrating with monitoring tools.
What's hot (20)
Using Continuous Integration To Ensure Project Health New
Using Continuous Integration To Ensure Project Health New
DevOps Tactical Adoption Theory: Continuous Testing
DevOps Tactical Adoption Theory: Continuous Testing
Viewers also liked
Lightning Talk on Mobile Access at Leeds Met
Slides from my lightning talk at the Mobile technologies in libraries: information sharing event in Birmingham on the 08/05/2012
Resource2 spm
The document discusses issues with traditional project management approaches that focus on task completion, including projects going over budget, missing specs or scope, and long lead times. It then introduces an alternative "whole system" approach called Theory of Constraints that places buffers between tasks to protect due dates, shortening overall lead times by 15-25% while making schedules more robust to variation and uncertainty.
Mps
The document outlines a project to develop the Merlin application using ExtJs from January 1-5, 2012. It discusses the application overview, project schedule, resources including two developers and laptops, and steps for training, creating the interface, and testing. The conclusion states that OpenProj helped schedule tasks and organize the project to rapidly define tasks.
Give Yourself the Slight Edge
How to turn simple daily disciplines into habits that will bring you success in work and life - using principles from Jeff Olson's book, The Slight Edge.
Library Services in HE Mobile Access
Slides from the The Yorkshire University Libraries Information Skills Group - Mobile Access Presentation on the 11/05/2012
Barcelona´s cathedral
The document summarizes information about Barcelona Cathedral and architect Antoni Gaudi. It discusses how the first stone of the Cathedral was laid in 1882 and blessed later that year. It then focuses on Gaudi's work on the Holy Family church, providing details on his education and career, including working on the church from 1883 until his death in 1926. It also briefly mentions a rose window Gaudi designed for the Cathedral that was sculpted in Galicia and returned to Barcelona to be installed.
Barcelona´s cathedral
The document summarizes information about Barcelona Cathedral and architect Antoni Gaudi. It discusses how the first stone of the Cathedral was laid in 1882 and blessed later that year. It then focuses on Gaudi's work on the Holy Family church, providing details on his education and career, including working on the church from 1883 until his death in 1926. It also briefly mentions a rose window Gaudi designed for the Cathedral that was sculpted in Galicia and returned to Barcelona to be installed.
Outreach 2.0 the digital revolution of pr
Presentation at ALAMW with David Lee King about Facebook as a platform for public awareness for libraries and strategies to take advantage of the platform.
Segundo cicloprueba de ensayo de computacion
Este documento calcula el aumento salarial del 30% para los empleados del Hotel Escuela La Casa Lojana. El empleado con el sueldo más alto es Narcisa de Jesus Zapatero Murillo con un nuevo sueldo de $3,640. El empleado con el sueldo más bajo es Gloria Altamirano Rojas con un nuevo sueldo de $383.96. El aumento total en la nómina es de $2,670.53 para un total de $11,572.28.
Is That a Library In Your Pocket?
The document discusses how libraries are developing mobile websites and apps to provide services to patrons on the go. It outlines the benefits of a mobile website over an app, including being platform independent and not requiring downloads. It then lists several services that can be accessed from a mobile library site, such as branch information, catalog searches, downloading ebooks and audiobooks, research assistance, events calendars, social media, and suggested reading recommendations. Usage statistics for one site are also presented.
Go home library. You're Drunk!
The document outlines a marketing plan for a library. It discusses forming a creative team to develop an overarching theme using various marketing channels like ecards, billboards, posters, postcards, branding, newspaper stories, radio, television, and social media. The goal is to transform the library's image using entertaining and engaging content while respecting humor and informing the community. Quality programming and delivering value are emphasized over direct advertising. Contact details are provided for the creative leads.
Marketing on the Edge
Marketing strategy at the Craighead County Jonesboro Public Library presented at the 2012 Arkansas Library Association state conference in Springdale, AR and 2012 Internet Librarian conference in Monterey, CA.
Promoting Adult Library Programming
This document outlines general marketing strategies for promoting adult programs at a public library. It discusses choosing appropriate mediums like posters, newspapers, radio, and television. It emphasizes establishing an overarching theme and branding across mediums and programs. Costs and return on investment are considered for different mediums. The document provides tips for tone, continuity, and engaging audiences on Facebook. It stresses the importance of memorable, informative, and entertaining content to transform perceptions rather than reinforce existing views.
Resource1
Extreme Programming (XP) is a widely used agile method that takes an extreme approach to iterative development. It was first started in 1996 and has proven successful for companies of all sizes. Customer involvement is key in XP, with the customer part of the development team to help define requirements, prioritize features, and develop acceptance tests.
Viewers also liked (18)
Similar to Resource1 spm
Agile Values, Principles and Practices
This presentation reviews the Agile Manifesto and shows how the practices should be in alignment with values and principles.
Introduction to Software Engineering
The document provides an overview of the Rational Unified Process (RUP) and Extreme Programming (XP). RUP is a configurable software development process that uses iterative development, UML modeling, and documentation of artifacts. It consists of four main phases - inception, elaboration, construction, and transition. XP is an agile methodology based on values of communication, simplicity, feedback, and courage, and practices like planning games, test-driven development, pair programming, and frequent integration.
Adm Initial Proposal
This document proposes adopting an iterative development methodology that borrows from agile techniques like Scrum and XP. It suggests dividing projects into shorter 30-day iterations, with features estimated and designed at the start of each iteration. At the end of an iteration, working code would be completed along with automated testing. This approach aims to provide more accurate estimates, earlier feedback, better designed features, and more predictable development cycles compared to the current waterfall model. Key aspects to retain include code reviews, continuous integration, testing, and transparency of work.
Lecture - 20-23.pptx
This document discusses agile software development and extreme programming (XP). It describes XP as taking an extreme approach to iterative development with new versions built several times per day and increments delivered every two weeks. The key principles of XP are discussed, including incremental development, customer involvement, maintaining simplicity through refactoring, and supporting change through regular releases. Extreme programming practices like test-first development, pair programming, and continuous integration are explained. Requirements are expressed as user stories and scenarios and the customer prioritizes stories for each release. Refactoring involves continuous code improvements to keep the code simple and make future changes easier.
Chap 3 - Agile - XP.ppt
Extreme Programming (XP) is an agile software development framework that focuses on customer satisfaction, rapid and flexible response to change, simplicity, communication, and feedback. The core practices of XP include the planning game, simple design, metaphor, continuous testing, pair programming, collective code ownership, and continuous integration. Tests are written and automated before code is written to ensure customer requirements are met. Customers are involved throughout development providing feedback and acceptance tests. Frequent small releases are made, often multiple times per day, to get working software into customers' hands quickly.
Extreme programming (xp)
This document provides an overview of Extreme Programming (XP), an agile software development methodology. It discusses XP's history and features, which include short 2-week development cycles, pair programming, test-driven development, and frequent refactoring. The core principles of XP are also examined, such as incremental planning, small releases, simple design, and sustainable pace. Various phases of the XP process are outlined, from exploration to productionizing. Requirements are captured as scenarios and prioritized by the customer. Automated testing is a key practice in XP. Both advantages like collective code ownership and disadvantages like its unsuitability for large projects are noted.
Extreme programming
Extreme Programming (XP) is an agile software development methodology that focuses on rapid feedback, simplicity, communication, and responsiveness to change. The core practices of XP include: short iterative release cycles, frequent planning games, simple design, pair programming, unit testing, collective code ownership, continuous integration, on-site customers, and 40-hour work weeks. By following these practices, XP aims to deliver working software frequently in a way that is adaptable to changing requirements.
Agile - Software - Development Powerpoint
The document discusses agile software development methods. It describes how agile methods emerged in the late 1990s to address the need for rapid and iterative software development in a changing business environment. Key aspects of agile development covered include rapid and incremental delivery, customer involvement, an iterative approach, minimal documentation and a focus on working code over design. Specific agile techniques discussed include extreme programming, scrum, test-driven development and pair programming. The document also addresses challenges in scaling agile methods to larger projects.
Agiel sw development
Dissatisfaction with the overheads involved in software design methods of the 1980s and 1990s led to the creation of agile methods
ch2-Agile-Software-Development-engineerning.pdf
This document provides an overview of agile software development and extreme programming (XP). It discusses how agile methods aim to rapidly develop and deliver working software through an iterative process with customer collaboration. Key aspects of XP are described, including planning with user stories, small incremental releases, test-driven development, pair programming, collective code ownership, and continuous integration. The document contrasts plan-driven and agile development approaches and outlines some principles and practices of XP such as simple design, refactoring, and sustainable pace of work.
DevOps - Introduction to data science
Lecture: Introduction to Data Science
given 2017 at Technical University of Kaiserslautern, Germany
topic: DevOps and professional development
Extreme programming
Extreme Programming (XP) is an agile software development methodology that values adaptability over predictability. It prescribes day-to-day practices meant to embody values like communication, simplicity, feedback, and courage. XP aims to create software that is more responsive to changing customer needs through practices like pair programming, test-driven development, and frequent small releases. The XP life cycle involves short iterative planning, designing, coding, testing, and listening phases to incorporate frequent customer feedback.
eXtreme programming (XP) - An Overview
Extreme Programming (XP) is an agile software development framework that focuses on rapid software development and frequent delivery of working software. It utilizes practices like pair programming, test-driven development, continuous integration, collective code ownership and small, frequent releases. The core values of XP include communication, simplicity, feedback and courage. An XP team consists of programmers, a customer representative, a coach and utilizes roles, practices and values to develop high quality software through collaboration and rapid, adaptive responses to changing requirements.
Extreme Programming (XP) as A Popular Agile methodology.
This document provides an overview of Extreme Programming (XP), a popular agile software development methodology. It discusses the core principles and practices of XP, including rapid feedback, simplicity, incremental changes, embracing change, quality work, pair programming, collective code ownership, continuous integration, testing, refactoring, coding standards, and more. The document also outlines the values that XP is based on such as simplicity, communication, feedback, respect, and courage. It concludes that XP brings the development team together to create quality software that can adapt to changing requirements.
DevOps interview questions and answers
The document provides information on various DevOps concepts through a question and answer format. It defines design patterns as solutions to common problems faced by developers that represent best practices. It describes continuous deployment as instrumenting important project life cycle steps when moving code to production. It distinguishes between functional testing which targets business goals and requirements, and non-functional testing which focuses on aspects like performance and security. It explains the differences between white box testing which uses internal knowledge and black box testing which does not. It provides examples of resilience test tools like Hystrix and Chaos Monkey. It describes extreme programming as an agile methodology focused on customer satisfaction and team collaboration. It defines pair programming as two programmers working together on the same code. Finally
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Lecture - 24-25.pptx
This document discusses agile software development practices used in extreme programming (XP), including test-driven development, incremental testing, customer involvement in testing, test automation, pair programming, and challenges with XP testing. Key points covered include writing tests before code to clarify requirements, having customers help develop acceptance tests, using an automated test framework to quickly rerun all tests when new code is added, and pair programming helping spread knowledge and acting as an informal code review process.
Periodic Table of Agile Principles and Practices
Recently I fell by chance on the Periodic Table of the Elements... Long time no see... Remembering my physics lessons in University, I always loved that table. I remembered spending hours understanding the layout and admiring the beauty of its natural simplicity.
So I had the idea of trying the same layout, not the same approach since both are not comparable, really only the same layout for Agile Principles and Practices.
The result is in this presentation: The Periodic Table of Agile Principles and Practices:
Agile method
This slid is all about AGILE METHOD ,after reading this you will get idea about AGILE METHOD ,that how it can be use in software engineering field.
Similar to Resource1 spm (20)
Extreme Programming (XP) as A Popular Agile methodology.
Extreme Programming (XP) as A Popular Agile methodology.
Recently uploaded
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.
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.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
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 .
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Artificial Intelligence and Electronic Warfare
Artificial Intelligence and Electronic WarfarePapadakis K.-Cyber-Information Warfare Analyst & Cyber Defense/Security Consultant-Hellenic MoD
AI & Electronic WarfareAstute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Recently uploaded (20)
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
Essentials of Automations: Exploring Attributes & Automation Parameters
Essentials of Automations: Exploring Attributes & Automation Parameters
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Resource1 spm
- 2. Perhaps the best-known and most widely used agile method Extreme Programming (XP) takes an ‘extreme’ approach to iterative development
- 3. The first Extreme Programming project was started March 6, 1996. Extreme Programming has already been proven to be very successful at many companies of all different sizes and industries world wide.
- 4. Incremental planning Requirements are recorded on Story Cards and the Stories to be included in a release are determined by the time available and their relative priority. The developers break these Stories into development Ō TasksÕ . Small Releases The minimal useful set of functionalit y that provides business value is developed first. Releases of the system are frequent and incrementally add functionalit y to the first release. Simple Design Enough design is carried out to meet the current requirements and no more. Test first development An automated unit test framework is used to write tests for a new piece of functionalit y before that functionality itself is implemented. Refactoring All developers are expected to refactor the code continuously as soon as possible code improvements are found. This keeps the code simple and maintainable.
- 5. Pair Programming Developers work in pairs, checking each other’s work and providing the support to always do a good job. Collective Ownership The pairs of developers work on all areas of the system, so that no islands of expertise develop and all the developers own all the code. Anyone can change anything. Continuous Integration As soon as work on a task is complete it is integrated into the whole system. After any such integration, all the unit tests in the system must pass. Sustainable pace Large amounts of over-time are not considered acceptable as the net effect is often to reduce code quality and medium term productivity On-site Customer A representative of the end-user of the system (the Customer) should be available full time for the use of the XP team. In an extreme programming process, the customer is a member of the development team and is responsible for bringing system requirements to the team for implementation.
- 7. Customer involvement is a key part of XP where the customer is part of the development team. The role of the customer is: ◦ To help develop stories that define the requirements ◦ To help prioritise the features to be implemented in each release ◦ To help develop acceptance tests which assess whether or not the system meets its requirements.
- 8. www.cs.st-andrews.ac.uk http://www.extremeprogramming.org/