The ROLE SRE Approach - Getting more concrete
•Download as PPT, PDF•
2 likes•1,016 views
The document discusses the ROLE SRE (Social Requirements Engineering) approach, which aims to better support niche communities of practice (CoPs) and long-tail requirements. It outlines services and tools to facilitate explicit and implicit requirements elicitation from CoP members, including communication services, elicitation services, monitoring services, analysis services, and decision support services. Open issues discussed include requirements analysis targets, data gathering, and requirements mining algorithms.
Report
Share
Report
Share
![The ROLE SRE Approach – Support for the Long Tail ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Presentation ECSA
This document presents research on evaluating the architectural openness of mobile software platforms. It introduces the topic, defines key terms, and outlines the research questions and scope. The methodology involves a literature review and qualitative interviews with developers. Results include an architectural openness model with factors, and an analysis of openness in five major platforms (Android, Symbian, Windows Mobile, Blackberry, iPhone). The model shows how platform strategies affect architecture and accessibility. Interviews validated conclusions but found developers care more about functionality than openness. Further interviews with manufacturers are recommended.
The Social Requirements Engineering (SRE) Approach to Developing a Large-scal...
The Social Requirements Engineering (SRE) Approach to Developing a Large-scale Personal Learning Environment Infrastructure
Effie Lai-Chong Law, Arunangsu Chatterjee, Dominik Renzel and Ralf Klamma
Department of Computer Science, University of Leicester, UK
Chair of Computer Science 5 - Information Systems, RWTH Aachen University, Germany
EC-TEL 2012, Saarbrücken, Germany
September 21, 2012
Sre con16 tier 1 metamorphosis
Tier 1 engineers provide 24/7 monitoring of company systems but face issues like repetitive tasks, lack of career growth, and low morale. The company addressed this by creating automated remediation engines to handle alerts and escalations, freeing up engineers' time. They also established career paths for engineers to become subject matter experts, implemented dedicated project time, and transitioned their network operations culture to a site reliability culture to boost morale and retention of Tier 1 staff.
SRE in Startup
SRE (Site Reliability Engineering) is responsible for availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of services. An SRE team uses an "error budget" approach where new features can be launched if the service is within its agreed SLA, but launches are frozen if the SLA is not being met until enough of the error budget is earned back. SRE teams hire only coders who can speak the same language as developers and rotate developers into operations work. The goal of SRE is to minimize impact and prevent recurrence of outages through practices like post-mortem analysis and constant improvement of processes.
SouthBay SRE Meetup Jan 2016
The document discusses how LinkedIn performs traffic shifting to mitigate user impact from infrastructure issues, validate disaster recovery plans, test capacity headroom across datacenters, and perform maintenance. It describes how edge and datacenter traffic shifts are done using techniques like withdrawing IPVS routes and marking user buckets as online/offline. Single master failovers are also discussed as an extreme option that leverages distributed locking in Zookeeper. Regular practice of traffic shifts through testing and automation helps LinkedIn prepare for potential disasters.
Scio Saa S Readiness Evaluation Sre V1.0
This document discusses SaaS readiness evaluation (SRE) services. SRE is a brief consulting engagement to help companies transition existing software to a software-as-a-service model. It evaluates technical requirements, business implications, and provides a roadmap. Key deliverables include a business case, financial projections, and functional prototype. SRE helps answer questions around competitive positioning, technology architecture, pricing, financial impact, and customer support in a SaaS model. Typical engagements last 2-3 weeks and cost $5,000-$20,000.
Stephen McHenry - Chanecellor of Site Reliability Engineering, Google
The document discusses Google's mission to organize the world's information and make it universally accessible. It provides an overview of Google's history from its early systems using Lego disks to store data to its current large scale data centers. The document discusses Google's challenges in dealing with the ever increasing amounts of data and computational needs required by its services. It outlines Google's strategies for planning for failure, expansion of applications, infrastructure and hardware. Key systems developed by Google to manage large scale data and computing needs include Google File System, MapReduce and BigTable.
Recommended
Presentation ECSA
This document presents research on evaluating the architectural openness of mobile software platforms. It introduces the topic, defines key terms, and outlines the research questions and scope. The methodology involves a literature review and qualitative interviews with developers. Results include an architectural openness model with factors, and an analysis of openness in five major platforms (Android, Symbian, Windows Mobile, Blackberry, iPhone). The model shows how platform strategies affect architecture and accessibility. Interviews validated conclusions but found developers care more about functionality than openness. Further interviews with manufacturers are recommended.
The Social Requirements Engineering (SRE) Approach to Developing a Large-scal...
The Social Requirements Engineering (SRE) Approach to Developing a Large-scale Personal Learning Environment Infrastructure
Effie Lai-Chong Law, Arunangsu Chatterjee, Dominik Renzel and Ralf Klamma
Department of Computer Science, University of Leicester, UK
Chair of Computer Science 5 - Information Systems, RWTH Aachen University, Germany
EC-TEL 2012, Saarbrücken, Germany
September 21, 2012
Sre con16 tier 1 metamorphosis
Tier 1 engineers provide 24/7 monitoring of company systems but face issues like repetitive tasks, lack of career growth, and low morale. The company addressed this by creating automated remediation engines to handle alerts and escalations, freeing up engineers' time. They also established career paths for engineers to become subject matter experts, implemented dedicated project time, and transitioned their network operations culture to a site reliability culture to boost morale and retention of Tier 1 staff.
SRE in Startup
SRE (Site Reliability Engineering) is responsible for availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of services. An SRE team uses an "error budget" approach where new features can be launched if the service is within its agreed SLA, but launches are frozen if the SLA is not being met until enough of the error budget is earned back. SRE teams hire only coders who can speak the same language as developers and rotate developers into operations work. The goal of SRE is to minimize impact and prevent recurrence of outages through practices like post-mortem analysis and constant improvement of processes.
SouthBay SRE Meetup Jan 2016
The document discusses how LinkedIn performs traffic shifting to mitigate user impact from infrastructure issues, validate disaster recovery plans, test capacity headroom across datacenters, and perform maintenance. It describes how edge and datacenter traffic shifts are done using techniques like withdrawing IPVS routes and marking user buckets as online/offline. Single master failovers are also discussed as an extreme option that leverages distributed locking in Zookeeper. Regular practice of traffic shifts through testing and automation helps LinkedIn prepare for potential disasters.
Scio Saa S Readiness Evaluation Sre V1.0
This document discusses SaaS readiness evaluation (SRE) services. SRE is a brief consulting engagement to help companies transition existing software to a software-as-a-service model. It evaluates technical requirements, business implications, and provides a roadmap. Key deliverables include a business case, financial projections, and functional prototype. SRE helps answer questions around competitive positioning, technology architecture, pricing, financial impact, and customer support in a SaaS model. Typical engagements last 2-3 weeks and cost $5,000-$20,000.
Stephen McHenry - Chanecellor of Site Reliability Engineering, Google
The document discusses Google's mission to organize the world's information and make it universally accessible. It provides an overview of Google's history from its early systems using Lego disks to store data to its current large scale data centers. The document discusses Google's challenges in dealing with the ever increasing amounts of data and computational needs required by its services. It outlines Google's strategies for planning for failure, expansion of applications, infrastructure and hardware. Key systems developed by Google to manage large scale data and computing needs include Google File System, MapReduce and BigTable.
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
The document discusses new approaches for building software systems, including microservices, cloud native architectures, and Site Reliability Engineering (SRE) and chaos engineering. It notes that microservices, cloud platforms, and DevOps have established new best practices for software development. Namely, it emphasizes designing systems for failure and testing systems using chaos engineering approaches to improve reliability.
Software Reliability Engineering
This document introduces a simplified model for software reliability engineering (SRE). It outlines three phases: error introduction during development, defect identification during testing, and failure manifestation during operation. For each phase, it identifies key influencing factors and proposes potential measures and metrics to assess those factors, such as design complexity, code coverage, and how thoroughly contexts of use are considered. The goal is to provide a standardized yet practical approach to SRE.
You got a couple Microservices, now what? - Adding SRE to DevOps
This talk goes over the infrastructure needed to run Microservices in production by answers the following questions:
* Why do I want to run my software in Containers?
* What is a Kubernetes or Mesos?
* Am I going to need a DevOps or SRE team? What will they do?
* How will my Continuous Integration/Delivery will look like?
SRE Tools
software reliability, software reliability tools, software reliability tool, software engineering, computer engineering, computer science
SRE From Scratch
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
Load balancing in the SRE way
The document discusses load balancing for a large GitHub Enterprise cluster with zero downtime requirements. It describes using OpenResty (Nginx + Lua) as a scripting platform to conduct traffic via code and enable features like customized request rate limiting. It also discusses using a blue/green deployment approach with two load balancer stacks and switching DNS records to route traffic between stacks for experiments. Key aspects of the infrastructure include testing Docker images and hosts with RSpec and Serverspec, using Vault for secret management, and blocking mode protection with Signal Sciences.
SRE - drupal day aveiro 2016
Site Reliability Engineering enables agility and stability.
SREs use Software Engineering to automate themselves out of the Job.
My advice, if you want to implement this change in your company is to start with action items, alter your training and hiring, implement error budgets, do blameless postmortems and reduce toil.
Site Reliability Engineering Helps Google Conquer The World
The Vistara Blog provides insights on IT operations to help IT professionals. It offers perspectives on challenges in IT operations and strategies to address them. Regular posts explore ways to optimize systems, streamline processes, and ensure high performance and availability of critical applications and infrastructure.
The ROLE Requirements Bazaar
A presentation on the ROLE Requirements Bazaar and the ROLE Social Requirements Engineering approach going in the direction of implementation.
PlanetData: Consuming Structured Data at Web Scale
PlanetData project was presented by Elena Simperl and Barry Norton from Karlsruhe Institute of Technology at the 1st International Symposium on Data-driven Process Discovery and Analysis on June 30, 2011 in Campione d’Italia, Italy
Planetdata simpda
The document summarizes the PlanetData project, which aims to establish an interdisciplinary community for managing large-scale structured data on the web. Its objectives include addressing challenges through integrated research, providing data and technology through a lab, and having impact through training, standards, and networking. The work plan highlights include publishing and managing streaming data, assessing linked data quality, and developing applications using linked services and processes.
Web APIs - Infrastructure for the (Intelligent) Programmable Web (R&D Talk)
A couple of weeks I had the pleasure of visiting the CETINA Research Institute at URJC (http://www.cetinia.urjc.es/) in Madrid for an Invited Talk. I pulled together some thoughts from 3scale and some R&D worked I've been involved in to muse about how the web will evolve. Fun to be there - thanks to CETINA and Sascha in particular for the invite!
Rich Internet Applications
This document proposes selecting appropriate Rich Internet Application (RIA) technologies to meet user and business demands. It presents RIA technologies like AJAX, Adobe Flex, and Microsoft Silverlight, compares their features, and recommends usage scenarios. As a case study, it evaluates developing the Palestinian Encyclopedia (PalPedia) using RIA best practices for user experience, performance, and compatibility. The document concludes by discussing developing PalPedia further and including additional RIA technologies in future comparisons.
One Standard to rule them all?: Descriptive Choices for Open Education
One Standard to rule them all?: Descriptive Choices for Open Education, OCWC2010 Hanoi, May 5-7 2010
R. John Robertson1, Lorna Campbell1, Phil Barker2, Li Yuan3, and Sheila MacNeill1 1Centre for Academic Practice and Learning Enhancement, University of Strathclyde, 2Institute for Computer Based Learning, Heriot-Watt University 3Institute for Cybernetic Education, University of Bolton
AGI2011-Open Source Software Stack & Standards - Integration and Geograph...
Presentation based on the experiences of implementing a web mapping application using open source software stack and integrating with proprietary systems.
Web 2.0 workshop
Some slides and activities exploring the implications of web 2.0 for higher education - the workshop took about 90 minutes.
The path to an hybrid open source paradigm
Open Source project failure often stems from not setting clear objectives or having a shared vision from the start. That said there are many success stories, including two well known Statistical examples: Demetra; and Eurostat SDMX tools (SDMX-RI). However, in all these examples there was at first a founding organisation/entity that created the right environment for its successful path into a new paradigm. In the context of my presentation this being the Statistical Information System Collaboration Community (SIS-CC / http://siscc.oecd.org).
Presented at the International Marketing and Output DataBase Conference, Gozd Martuljek, September 18 - 22, 2016.
Pistoia Alliance Sequence Services Programme Phase 2
Presentation by Simon Thornber, lead of the Pistoia Alliance sequence services working group, about the RFP issued for the second phase of the project.
Web 2.0 Core Concepts, Applications, and Implications
The document discusses the concepts of Web 2.0 including its core characteristics and applications. It provides examples of Web 1.0 applications and their Web 2.0 successors. It also analyzes the functionality and qualities that Web 2.0 services provide like user participation, content sharing and contextualization. The document further discusses trends in Web 2.0 including identity consolidation, universal accessibility, interoperability and the semantic web.
Sample project requirements document
The library needs a new blog system to effectively communicate with users. A task force was created to review products and implement a new system by fall 2011. It must allow commenting, have mobile support, and work across browsers. The current system from 2008 lacks necessary features. The new system should be open source if locally hosted, support authentication and APIs, and have robust documentation. Usability testing is constrained by the timeline. Progress updates will be shared internally and the new blog announced to campus once ready.
WEB 2.0 For Interns(Surya)
The document discusses the origins and key concepts of Web 2.0. It defines Web 2.0 as the network being the platform, spanning all connected devices, with applications that harness the collective intelligence of users by delivering continually-updated services, consuming and remixing data from multiple sources, creating network effects through participation, and going beyond the page metaphor of Web 1.0. The document outlines several axes along which Web 2.0 design patterns and business models differ from Web 1.0, such as embracing collective intelligence and treating data as a valuable asset.
Colt inter-provider SDN NNIs and APIs
As SDN & NFV services become commercially available, the industry needs to approach once again the reach issue. There is not a single service provider with complete reach; that is why we build NNIs and need a wider SDN/NFV Ecosystem.
More Related Content
Viewers also liked
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
The document discusses new approaches for building software systems, including microservices, cloud native architectures, and Site Reliability Engineering (SRE) and chaos engineering. It notes that microservices, cloud platforms, and DevOps have established new best practices for software development. Namely, it emphasizes designing systems for failure and testing systems using chaos engineering approaches to improve reliability.
Software Reliability Engineering
This document introduces a simplified model for software reliability engineering (SRE). It outlines three phases: error introduction during development, defect identification during testing, and failure manifestation during operation. For each phase, it identifies key influencing factors and proposes potential measures and metrics to assess those factors, such as design complexity, code coverage, and how thoroughly contexts of use are considered. The goal is to provide a standardized yet practical approach to SRE.
You got a couple Microservices, now what? - Adding SRE to DevOps
This talk goes over the infrastructure needed to run Microservices in production by answers the following questions:
* Why do I want to run my software in Containers?
* What is a Kubernetes or Mesos?
* Am I going to need a DevOps or SRE team? What will they do?
* How will my Continuous Integration/Delivery will look like?
SRE Tools
software reliability, software reliability tools, software reliability tool, software engineering, computer engineering, computer science
SRE From Scratch
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
Load balancing in the SRE way
The document discusses load balancing for a large GitHub Enterprise cluster with zero downtime requirements. It describes using OpenResty (Nginx + Lua) as a scripting platform to conduct traffic via code and enable features like customized request rate limiting. It also discusses using a blue/green deployment approach with two load balancer stacks and switching DNS records to route traffic between stacks for experiments. Key aspects of the infrastructure include testing Docker images and hosts with RSpec and Serverspec, using Vault for secret management, and blocking mode protection with Signal Sciences.
SRE - drupal day aveiro 2016
Site Reliability Engineering enables agility and stability.
SREs use Software Engineering to automate themselves out of the Job.
My advice, if you want to implement this change in your company is to start with action items, alter your training and hiring, implement error budgets, do blameless postmortems and reduce toil.
Site Reliability Engineering Helps Google Conquer The World
The Vistara Blog provides insights on IT operations to help IT professionals. It offers perspectives on challenges in IT operations and strategies to address them. Regular posts explore ways to optimize systems, streamline processes, and ensure high performance and availability of critical applications and infrastructure.
Viewers also liked (8)
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
You got a couple Microservices, now what? - Adding SRE to DevOps
You got a couple Microservices, now what? - Adding SRE to DevOps
Site Reliability Engineering Helps Google Conquer The World
Site Reliability Engineering Helps Google Conquer The World
Similar to The ROLE SRE Approach - Getting more concrete
The ROLE Requirements Bazaar
A presentation on the ROLE Requirements Bazaar and the ROLE Social Requirements Engineering approach going in the direction of implementation.
PlanetData: Consuming Structured Data at Web Scale
PlanetData project was presented by Elena Simperl and Barry Norton from Karlsruhe Institute of Technology at the 1st International Symposium on Data-driven Process Discovery and Analysis on June 30, 2011 in Campione d’Italia, Italy
Planetdata simpda
The document summarizes the PlanetData project, which aims to establish an interdisciplinary community for managing large-scale structured data on the web. Its objectives include addressing challenges through integrated research, providing data and technology through a lab, and having impact through training, standards, and networking. The work plan highlights include publishing and managing streaming data, assessing linked data quality, and developing applications using linked services and processes.
Web APIs - Infrastructure for the (Intelligent) Programmable Web (R&D Talk)
A couple of weeks I had the pleasure of visiting the CETINA Research Institute at URJC (http://www.cetinia.urjc.es/) in Madrid for an Invited Talk. I pulled together some thoughts from 3scale and some R&D worked I've been involved in to muse about how the web will evolve. Fun to be there - thanks to CETINA and Sascha in particular for the invite!
Rich Internet Applications
This document proposes selecting appropriate Rich Internet Application (RIA) technologies to meet user and business demands. It presents RIA technologies like AJAX, Adobe Flex, and Microsoft Silverlight, compares their features, and recommends usage scenarios. As a case study, it evaluates developing the Palestinian Encyclopedia (PalPedia) using RIA best practices for user experience, performance, and compatibility. The document concludes by discussing developing PalPedia further and including additional RIA technologies in future comparisons.
One Standard to rule them all?: Descriptive Choices for Open Education
One Standard to rule them all?: Descriptive Choices for Open Education, OCWC2010 Hanoi, May 5-7 2010
R. John Robertson1, Lorna Campbell1, Phil Barker2, Li Yuan3, and Sheila MacNeill1 1Centre for Academic Practice and Learning Enhancement, University of Strathclyde, 2Institute for Computer Based Learning, Heriot-Watt University 3Institute for Cybernetic Education, University of Bolton
AGI2011-Open Source Software Stack & Standards - Integration and Geograph...
Presentation based on the experiences of implementing a web mapping application using open source software stack and integrating with proprietary systems.
Web 2.0 workshop
Some slides and activities exploring the implications of web 2.0 for higher education - the workshop took about 90 minutes.
The path to an hybrid open source paradigm
Open Source project failure often stems from not setting clear objectives or having a shared vision from the start. That said there are many success stories, including two well known Statistical examples: Demetra; and Eurostat SDMX tools (SDMX-RI). However, in all these examples there was at first a founding organisation/entity that created the right environment for its successful path into a new paradigm. In the context of my presentation this being the Statistical Information System Collaboration Community (SIS-CC / http://siscc.oecd.org).
Presented at the International Marketing and Output DataBase Conference, Gozd Martuljek, September 18 - 22, 2016.
Pistoia Alliance Sequence Services Programme Phase 2
Presentation by Simon Thornber, lead of the Pistoia Alliance sequence services working group, about the RFP issued for the second phase of the project.
Web 2.0 Core Concepts, Applications, and Implications
The document discusses the concepts of Web 2.0 including its core characteristics and applications. It provides examples of Web 1.0 applications and their Web 2.0 successors. It also analyzes the functionality and qualities that Web 2.0 services provide like user participation, content sharing and contextualization. The document further discusses trends in Web 2.0 including identity consolidation, universal accessibility, interoperability and the semantic web.
Sample project requirements document
The library needs a new blog system to effectively communicate with users. A task force was created to review products and implement a new system by fall 2011. It must allow commenting, have mobile support, and work across browsers. The current system from 2008 lacks necessary features. The new system should be open source if locally hosted, support authentication and APIs, and have robust documentation. Usability testing is constrained by the timeline. Progress updates will be shared internally and the new blog announced to campus once ready.
WEB 2.0 For Interns(Surya)
The document discusses the origins and key concepts of Web 2.0. It defines Web 2.0 as the network being the platform, spanning all connected devices, with applications that harness the collective intelligence of users by delivering continually-updated services, consuming and remixing data from multiple sources, creating network effects through participation, and going beyond the page metaphor of Web 1.0. The document outlines several axes along which Web 2.0 design patterns and business models differ from Web 1.0, such as embracing collective intelligence and treating data as a valuable asset.
Colt inter-provider SDN NNIs and APIs
As SDN & NFV services become commercially available, the industry needs to approach once again the reach issue. There is not a single service provider with complete reach; that is why we build NNIs and need a wider SDN/NFV Ecosystem.
Web2 0 Incredibles
Web 2.0 emphasizes online collaboration, sharing, and user participation through technologies like AJAX, RSS, and SOAP. It is now being adopted in enterprises, though challenges remain around enterprise context, security, and cultural differences. A market study found satisfactory returns on investment for Web 2.0 applications. Web 3.0, also called the semantic web, aims to organize the world's information by enabling computers to reason about data.
Web 2.0 - principles and implications
The document discusses the principles and definitions of Web 2.0. It defines Web 2.0 as transitioning websites from isolated information silos to platforms serving applications to users, with an emphasis on open communication, decentralization, sharing content, and collective intelligence. Key aspects of Web 2.0 include user participation, tagging content to organize it, and mixing online services together. Examples provided include Wikipedia, Flickr, and social media platforms. The implications discussed are students and users helping create and contribute content, and a more personalized web experience with greater sharing of information.
tip oopt pse-summit2017
Optical Planning Tool, Common-AP. First Open Source Optical Planner for Packet-Optical integration and Multi-Layer Optimization
WP2 1st Review
This document summarizes work from the INSEMTIVES project on developing models and methods for creating and using lightweight, structured knowledge on the semantic web. It discusses problems with current web annotations like synonymy, polysemy, and specificity gaps. The project aims to address these by developing models to enrich web annotations with semantics and associated services. Key challenges include determining the right level of semantic complexity for users and algorithms for bootstrapping annotations, reaching consensus on vocabularies, and evolving annotations over time.
What open source lovers want?
This session tries to give insights into what the people using, developing and supporting OpenOffice.org want. For this purpose, data from different OpenOffice.org surveys and metrics will be analyzed and presented. One key data source for the presentation will be the ongoing OpenOffice.org user survey which gets completed by about 2000 people every day. In addition, OpenOffice.org developer surveys, external surveys and various OpenOffice.org user and developer metrics will be brought into the picture as well. The session will try to provide answers to questions like “What functionality do different OpenOffice.org users need?”, “How do people want to contribute to OpenOffice.org?”, “What motivates people to contribute to OpenOffice.org?”, etc.
Onos summit roadmap dec 9
The document outlines the roadmap for ONOS, an open source SDN controller, in 2015. Key points include:
- Regular 3 month release cadence, with names like Avocet and Blackbird. Blackbird release in February 2015 will focus on stability, performance, and high availability.
- Areas of focus for 2015 include building out the distributed core using RAFT, improving the intent framework, adding southbound drivers, and exploring new use cases.
- Planned proof of concepts and deployments include AT&T use cases, NTT/NEC optical networking, an Internet2 deployment, and community labs.
- Goals for 2015 include expanding the developer community, influencing standards,
Similar to The ROLE SRE Approach - Getting more concrete (20)
PlanetData: Consuming Structured Data at Web Scale
PlanetData: Consuming Structured Data at Web Scale
Web APIs - Infrastructure for the (Intelligent) Programmable Web (R&D Talk)
Web APIs - Infrastructure for the (Intelligent) Programmable Web (R&D Talk)
One Standard to rule them all?: Descriptive Choices for Open Education
One Standard to rule them all?: Descriptive Choices for Open Education
AGI2011-Open Source Software Stack & Standards - Integration and Geograph...
AGI2011-Open Source Software Stack & Standards - Integration and Geograph...
Pistoia Alliance Sequence Services Programme Phase 2
Pistoia Alliance Sequence Services Programme Phase 2
Web 2.0 Core Concepts, Applications, and Implications
Web 2.0 Core Concepts, Applications, and Implications
The ROLE SRE Approach - Getting more concrete
- 1. The ROLE SRE Approach – Getting More Concrete Dominik Renzel Chair of Computer Science 5, RWTH Aachen University, Germany WP1 Workshop May 14, 2010 - Leicester, UK
- 3. ROLE Social RE – i* Strategic Rationale
- 5. ROLE CoP Communication Services & Media
- 7. Social RE in Android Market – Developer Contact
- 8. ROLE CoP Requirements Elicitation Services
- 10. Web 2.0 RE Tool Example – Bubble Annotation Tool
- 11. Social RE in Android Market – Recommendation Area Explicit Requirements in Comments Ratings + Comments Conditional Ratings (connected with Requirements)
- 12. ROLE CoP Monitoring Services 28.02.09
- 14. ROLE CoP Requirements Analysis Services 28.02.09
- 17. ROLE CoP Requirements Decision Support Services 28.02.09
Editor's Notes
- Good start for long tail, but for what happens, if too successful (from tail to shoulder to hype)