This article looks at the decisions organizations make and what they do as they move up the scale in requirements management maturity (RMM).
Just as hiking up a mountain has a cost (in energy and time), so does this climb upward. Therefore, as we look at the benefits of reaching higher levels of maturity, we will not ignore the investment required in terms of time, effort, and money. In addition, we will analyze how automated requirements management (RM) tools can help support organizations striving for greater RM maturity.
An overview presentation of the IAG Requirements Maturity Model with description of the key capability areas and characteristics of the maturity levels.
The beginning of a checklist version of the CMMI guidelines. If you would like the original Excel version let me know, and let SlideShare know they need to support Excel files.
The objective of this ramp-up project is to
change from the old to the new layout. The
implementation requires a clear strategy to use
resources efficiently while compromising the
operations as least as possible.
Brian Schouten, Director of Technical Presales for PROSTEP INC describes the requirements, risks, strategy, and technical considerations of "do-it-yourself" PLM Migrations for ENOVIA 3D EXPERIENCE.
Presented at the May 2017 Capability Counts CMMI conference.
Presented shared an Business Architecture systems tools, and provided best practices and lessons learned related to codifying business processes into JIRA workflows.
An overview presentation of the IAG Requirements Maturity Model with description of the key capability areas and characteristics of the maturity levels.
The beginning of a checklist version of the CMMI guidelines. If you would like the original Excel version let me know, and let SlideShare know they need to support Excel files.
The objective of this ramp-up project is to
change from the old to the new layout. The
implementation requires a clear strategy to use
resources efficiently while compromising the
operations as least as possible.
Brian Schouten, Director of Technical Presales for PROSTEP INC describes the requirements, risks, strategy, and technical considerations of "do-it-yourself" PLM Migrations for ENOVIA 3D EXPERIENCE.
Presented at the May 2017 Capability Counts CMMI conference.
Presented shared an Business Architecture systems tools, and provided best practices and lessons learned related to codifying business processes into JIRA workflows.
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
Mettre en place un Contrat Agile avec SAFeAgile En Seine
Présenté par Hélène Malo Wittemberg (Digital Tango) et Esteban Martinez-Querol (Digital Tango) à Agile en Seine le 20 septembre 2023
Dans cette présentation, nous expliquerons pourquoi dans notre monde VUCA, il est nécessaire de faire évoluer la typologie des contrats traditionnels avec nos fournisseurs et comment mettre en place cette relation de confiance à l’aide du Framework SAFe, dès sa phase d’appel d’offres et tout au long de sa réalisation.
Nous aborderons les défis contractuelles et légaux que ce type de contrat et nous partagerons notre expérience concrètes dans des cadres privés et paragouvernementaux.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Follow us on www.techxpla.com
One of the key advantages of adopting an agile workflow is the ability of the team to estimate new work effectively. But teams new to agile sometimes have difficulty figuring out how to estimate requirements effectively.
Until a team has been working together for a while, attempts to generate accurate estimates for new requirement may feel awkward and loose.
Here Anushree Verma Certified Scrum Master and Agile Coach from Capgemini gave few estimation techniques for agile teams that can ease the transition through this phase. These techniques get everyone engaged in productive point estimation from the start, regardless of their level of experience with agile methods.
Topics covered in this slides are
1) Agile Estimation and its techniques
Concept of Story points
Relative versus Absolute estimation
Few examples of estimation Techniques
2) Agile Prioritization – Key success factor of Agile projects
Story Mapping and Prioritization
Few examples of Prioritization
Anushree's experience & Certifications :
IT Experience and Achievements:
Equipped with approx. 10 years of experience in Banking & Technology Industry and currently working as Technical Delivery Manager and Agile Coach in Capgemini. Associated with corporates like HSBC global technologies and Tieto Software Technologies in the past.
Certifications:
Certified Trainer/Facilitator - Train The Trainer [T.T.T] - Creating Wonders in facilitating - PMI USA
Certified Scrum Master (CSM) from Scrum Alliance (Member: 000433149).
ITIL V3,EXIN
Agile Certified Practitioner (ACP) )® trained, PMI USA
Project Management Professional (PMP) )® trained, PMI USA
AS400 Programmer Certification.
The 10 Steps to Becoming a Great Agile CoachLeadingAgile
Recently, at TriAgile 2020, Mike Cottmeyer presented his talk on how to become a great Agile coach. In it, he goes into the four primary areas that make up a great coach, the hard skills you'll need to develop, and how those apply to particular coaching roles.
You can check out the talk here: https://hubs.ly/H0pGFRH0
So you want to become a great Agile coach?
Join us for the premier of Mike Cottmeyer's remote talk that he delivered at TriAgile 2020 and learn the 10 steps you can take to do exactly that.
Watch as Mike explores the four primary skill areas that make a great coach and the hard skills you'll need to develop, and learn how those translate to specific types of coaching roles.
Learn how the Electric Reliability Council of Texas was able to replace multiple tools with a complete IT change management system running on JIRA. It provides end users a single point of entry for any hardware or software change, as well as saves the company millions by eliminating maintenance contracts on the old tools. What you learn may "shock" you – in the best possible way, of course.
Governance Model Powerpoint Presentation SlidesSlideTeam
Analyze the role of governance model framework to your corporate system with our professionally crafted PPT design named as governance model PowerPoint presentation slides. It is technically designed in accordance to the important elements of governance model which can be converted into business responsibilities, practices, and procedures. This governance model presentation is crafted with utmost care by our team of professionals to cover all the main aspects of the governance model. Since this PowerPoint slideshow is designed to increase the abilities of the business management and the board of directors of the company to have a better overview of growth and to assist employees to fulfill their role of governance. Thus, utilize this effective governance framework PPT for representing the components of the business management. It is also one of the most effective tools used by the board of directors and management. Download this amazing Governance structure PowerPoint template for your perusal now. Enfold your thoughts in our Governance Model Powerpoint Presentation Slides. They will stay safe and secure. https://bit.ly/3gETI75
10 Critical Aspects of IT Service Continuity to Protect Your Company's Digita...Jesse Andrew
Watch the webinar: http://go.italerting.com/pink-elephant-it-service-continuity
Life is never certain or predictable, however it seems like every other week we hear of some devastating natural disaster, massive security breach or major man-made crisis flooding the airwaves and going viral on social media. So much so that It almost seems that the unpredictable has become common place and the rare occurrence our weekly update.
Based on this new global reality and the business dependence on digital automation it is more crucial than ever for businesses to take up the old Boy Scout motto, "Be Prepared". In this informative webinar Troy DuMoulin, VP of Research and Development at Pink Elephant and Vincent Geffray, Senior Director of Product Marketing at Everbridge provide an overview and practical guidance on the critical governance, management capabilities and plans for dealing with the un-expected in a digital and data dependent world.
This schema represents a general view of the demand management framework. Developed using lean, kanban, project management and software engineering concepts, this framework covers from the business to IT.
The challenge of alignment, integration and change in the development of e-services has gave attention to enterprise architecture. It provide the framework of engagement and thinking tool to define, elaborate, document, agree and communicate the strategic baseline, strategic intent, strategic architecture, strategic change and strategic resources in the development and improvement of e-services within the defined context and perspectives of time, stakeholders, performance, funds, environment, leadership and technology. The shared open presentation is a product of direct engagement with people of decision and work who are enabled to participate the formulation of enterprise architecture that matters to their performance.
Presented on Oct 28, 2014 at the Greater Atlanta Chapter IIBA.
People seek to make connections of items to make sense of them in a larger context. As children (or adults), we connect the dots to form a picture of something recognizable. As a business analyst, we connect requirements and other analysis outputs to get the bigger picture of an initiative and to check the completeness of our work.
We will explore how IIBA® has defined requirement traceability, how traceability works, and the benefits of the practice to the current project and future analysis.
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
Mettre en place un Contrat Agile avec SAFeAgile En Seine
Présenté par Hélène Malo Wittemberg (Digital Tango) et Esteban Martinez-Querol (Digital Tango) à Agile en Seine le 20 septembre 2023
Dans cette présentation, nous expliquerons pourquoi dans notre monde VUCA, il est nécessaire de faire évoluer la typologie des contrats traditionnels avec nos fournisseurs et comment mettre en place cette relation de confiance à l’aide du Framework SAFe, dès sa phase d’appel d’offres et tout au long de sa réalisation.
Nous aborderons les défis contractuelles et légaux que ce type de contrat et nous partagerons notre expérience concrètes dans des cadres privés et paragouvernementaux.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Follow us on www.techxpla.com
One of the key advantages of adopting an agile workflow is the ability of the team to estimate new work effectively. But teams new to agile sometimes have difficulty figuring out how to estimate requirements effectively.
Until a team has been working together for a while, attempts to generate accurate estimates for new requirement may feel awkward and loose.
Here Anushree Verma Certified Scrum Master and Agile Coach from Capgemini gave few estimation techniques for agile teams that can ease the transition through this phase. These techniques get everyone engaged in productive point estimation from the start, regardless of their level of experience with agile methods.
Topics covered in this slides are
1) Agile Estimation and its techniques
Concept of Story points
Relative versus Absolute estimation
Few examples of estimation Techniques
2) Agile Prioritization – Key success factor of Agile projects
Story Mapping and Prioritization
Few examples of Prioritization
Anushree's experience & Certifications :
IT Experience and Achievements:
Equipped with approx. 10 years of experience in Banking & Technology Industry and currently working as Technical Delivery Manager and Agile Coach in Capgemini. Associated with corporates like HSBC global technologies and Tieto Software Technologies in the past.
Certifications:
Certified Trainer/Facilitator - Train The Trainer [T.T.T] - Creating Wonders in facilitating - PMI USA
Certified Scrum Master (CSM) from Scrum Alliance (Member: 000433149).
ITIL V3,EXIN
Agile Certified Practitioner (ACP) )® trained, PMI USA
Project Management Professional (PMP) )® trained, PMI USA
AS400 Programmer Certification.
The 10 Steps to Becoming a Great Agile CoachLeadingAgile
Recently, at TriAgile 2020, Mike Cottmeyer presented his talk on how to become a great Agile coach. In it, he goes into the four primary areas that make up a great coach, the hard skills you'll need to develop, and how those apply to particular coaching roles.
You can check out the talk here: https://hubs.ly/H0pGFRH0
So you want to become a great Agile coach?
Join us for the premier of Mike Cottmeyer's remote talk that he delivered at TriAgile 2020 and learn the 10 steps you can take to do exactly that.
Watch as Mike explores the four primary skill areas that make a great coach and the hard skills you'll need to develop, and learn how those translate to specific types of coaching roles.
Learn how the Electric Reliability Council of Texas was able to replace multiple tools with a complete IT change management system running on JIRA. It provides end users a single point of entry for any hardware or software change, as well as saves the company millions by eliminating maintenance contracts on the old tools. What you learn may "shock" you – in the best possible way, of course.
Governance Model Powerpoint Presentation SlidesSlideTeam
Analyze the role of governance model framework to your corporate system with our professionally crafted PPT design named as governance model PowerPoint presentation slides. It is technically designed in accordance to the important elements of governance model which can be converted into business responsibilities, practices, and procedures. This governance model presentation is crafted with utmost care by our team of professionals to cover all the main aspects of the governance model. Since this PowerPoint slideshow is designed to increase the abilities of the business management and the board of directors of the company to have a better overview of growth and to assist employees to fulfill their role of governance. Thus, utilize this effective governance framework PPT for representing the components of the business management. It is also one of the most effective tools used by the board of directors and management. Download this amazing Governance structure PowerPoint template for your perusal now. Enfold your thoughts in our Governance Model Powerpoint Presentation Slides. They will stay safe and secure. https://bit.ly/3gETI75
10 Critical Aspects of IT Service Continuity to Protect Your Company's Digita...Jesse Andrew
Watch the webinar: http://go.italerting.com/pink-elephant-it-service-continuity
Life is never certain or predictable, however it seems like every other week we hear of some devastating natural disaster, massive security breach or major man-made crisis flooding the airwaves and going viral on social media. So much so that It almost seems that the unpredictable has become common place and the rare occurrence our weekly update.
Based on this new global reality and the business dependence on digital automation it is more crucial than ever for businesses to take up the old Boy Scout motto, "Be Prepared". In this informative webinar Troy DuMoulin, VP of Research and Development at Pink Elephant and Vincent Geffray, Senior Director of Product Marketing at Everbridge provide an overview and practical guidance on the critical governance, management capabilities and plans for dealing with the un-expected in a digital and data dependent world.
This schema represents a general view of the demand management framework. Developed using lean, kanban, project management and software engineering concepts, this framework covers from the business to IT.
The challenge of alignment, integration and change in the development of e-services has gave attention to enterprise architecture. It provide the framework of engagement and thinking tool to define, elaborate, document, agree and communicate the strategic baseline, strategic intent, strategic architecture, strategic change and strategic resources in the development and improvement of e-services within the defined context and perspectives of time, stakeholders, performance, funds, environment, leadership and technology. The shared open presentation is a product of direct engagement with people of decision and work who are enabled to participate the formulation of enterprise architecture that matters to their performance.
Presented on Oct 28, 2014 at the Greater Atlanta Chapter IIBA.
People seek to make connections of items to make sense of them in a larger context. As children (or adults), we connect the dots to form a picture of something recognizable. As a business analyst, we connect requirements and other analysis outputs to get the bigger picture of an initiative and to check the completeness of our work.
We will explore how IIBA® has defined requirement traceability, how traceability works, and the benefits of the practice to the current project and future analysis.
Objectives:
1. To understand the different processes in the realm of ‘Requirements Engineering’.
2. To see the challenges in requirements development and the importance of getting requirements right in an IT project.
3. To understand the different techniques used in different phases and processes of requirements development and management.
This affects the quality of software and increases the production cost of ... effectiveness of every method, it is useful to select the particular elicitation
http://www.imran.xyz
Importance of successful change management ; Change management principles ; Change management process ; Resistance to change ; ; Building culture for change ; ADKAR Model ; Change management strategies; John P Kotter's change management strategies
INFORME SEGUNDO DEBATE PROYECTO DE LEY DE RECURSOS HIDRICOS, USO Y APROVECHAM...Jaime Abril Abril
# Trámite 31435
Tipo de documento MEMORANDO INTERNO
Fecha recepción 11-may-2010 11:15
Fecha vencimiento
Numeración documento AN-CE7-P-247
Fecha oficio 11-may-2010
Dirigido a ARQ. FERNANDO CORDERO
Remitente ABRIL JAIME
“Without changing our patterns of thought, we will not be able to solve the problems we created with our current patterns of thought.”
- Albert Einstein
Discussions between chief financial officers (CFOs) and heads of IT departments most often center on the the funding of projects, or need to continue funding, as if a simple commodity-based relationship existed between fiscal outlay and value received. But this “pattern of thought,” to use Einstein’s term, hinders a much more productive mode of discussion that these two business leaders might engage in. In this paper, I will illustrate a new way of thinking about the funding of IT software projects, one that considers funding in terms of investment, and value as an expansive, longitudinal variable.
"Research Data: Management, Access, Control" Symposium at the University at B...Charles Lyons
Symposium held November 14, 2011 at the University at Buffalo. These are just the introductory slides.
More information: http://library.buffalo.edu/scholarly/.
In today’s global marketplace, successful companies must be able to integrate and quickly view quality audit information from their manufacturing sites all over the world. This strategic capability has become even more important as manufacturers have moved offshore and have become more complex. The value and immediacy of quality assurance data is a critical element to the survival of competitive manufacturing organizations. Software systems can address these issues.
Source:
Lyons Information Systems, Inc
http://www.lyonsinfo.com
The Ultimate Workflow Management Software Buyers Guide 2023Kashish Trivedi
Workflow management software can do wonders for an organization that struggles to find consistency in recurring processes. They can save time and money, reduce errors, and make life easier for employees and customers alike. But what should you look for when buying a workflow management software? Well, lucky for you, we make one ourselves. It’s kind of our whole thing. So we promise to steer you in the right direction toward the software that’s best for you.
The Top Process Management Software That Will Make Your 2023 GreatKashish Trivedi
Recurring work is an absolute pain. With all your responsibility, the last thing you want to do is spend your valuable time doing work that doesn’t need to be done. The answer? Process management software. But that isn’t the real issue, is it? You understand that process management software can help you increase productivity while saving you time and money. The problem is that there are tons of software options on the market. You’re likely overwhelmed with the endless products presented to you in a single Google search. This list will give you all the information you need to understand your team’s needs and ensure you make the best purchase decision.
All of us must have heard this proverb umpteen number of times in our lives. However, when it comes to elicitation, we tend to forget the same.Elicitation is possibly the most important job we business analysts do. I am surprised that many of us understand only few facets of elicitation such as requirements gathering and recording.Elicitation is much more than requirements gathering and recording. A good elicitation activity can significantly reduce effort in changes in requirements and subsequent changes to design, construction and testing activities.Here is an attempt to make our elicitation exercises more effective.
Learn How to Maximize Your ServiceNow InvestmentStave
Understand how leading companies are adopting an aPaaS strategy
Learn the evolution of ServiceNow's platform capabilities
Assert IT's influence over shadow IT practices
DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...IBM Rational software
Interconnect 2015,
DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS Next Generation!
By:
Paul Strachan (IBM)
Alex Ivanov (Raytheon)
Yianna Papadakis-Kantos (IBM)
Slides used during DAG-2848 workshop at InterConnect2017. The objective of this workshop is to demonstrate, through an interactive, hands-on experience, the power of IBM Rational Team Concert to support agile projects and facilitate the adoption of the IBM DevOps approach. By going through the exercises, you play different scrum roles to focus on activities that are helpful to agile teams (continuous planning and collaborative development). Whether you are involved in an agile project or you plan to start an agile initiative soon, attend this workshop to see how Rational Team Concert can help your team be more collaborative and more productive in your lean and agile initiatives. (No development skills are needed to complete this workshop.)
Essentials of UrbanCode Deploy 6.1 is an introductory course about the product. This slideset introduces the key aspects of the course such as objectives, agenda and also gives a solid product introduction.
IBM Innovate is now IBM InterConnect. Share your DevOps, agile, engineering or development expertise by submitting a speaker proposal: https://www-950.ibm.com/events/tools/interconnect/2015ems/
Factors to consider when starting a brand-new requirements management project...IBM Rational software
Some preparation work is required before starting a requirements management project. Ask the right questions, then capture decisions in a requirements plan. Implement the requirements plan in IBM Rational DOORS Next generation.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Elizabeth Buie - Older adults: Are we really designing for our future selves?
The Five Levels of Requirements Management Maturity
1. Copyright Rational Software 2003 http://www.therationaledge.com/content/feb_03/f_managementMaturity_jh.jsp
The Five Levels of Requirements Management
Maturity
by Jim Heumann
Requirements Evangelist
Rational Software
Maturity: the quality of sound
judgment associated with adult
humans.
-- The Wordsmyth English
Dictionary/Thesaurus
Being mature means being able to see
the big picture and make good choices.
In a business context, that means
basing decisions on a clear
understanding of the full range of both
the costs and benefits of doing one
thing over another.
This article looks at the decisions organizations make and what they do as
they move up the scale in requirements management maturity (RMM).
Just as hiking up a mountain has a cost (in energy and time), so does this
climb upward. Therefore, as we look at the benefits of reaching higher
levels of maturity, we will not ignore the investment required in terms of
time, effort, and money. In addition, we will analyze how automated
requirements management (RM) tools can help support organizations
striving for greater RM maturity.
Those familiar with the CMM (Capability Maturity Model) from the Software
Engineering Institute (SEI) will note some similarities to our parallel
model, which has no direct relationship to the CMM save one: Achieving
Level Five of the RMM will assuredly help an organization get to at least
Level Three of the CMM. Of course, it's important to keep in mind that
attaining a high level of maturity in a single area, such as requirements
management, is easier than attaining overall organizational process
maturity.
The five levels of maturity for our RMM are: 1) written 2) organized 3)
structured 4) traced, and 5) integrated. We will use these categories to
2. partition requirements management practices, starting at the lowest level
(One) and moving up through Level Five.
Chaos: No Requirements
Actually, there is one other level on the requirements maturity scale: Level
Zero -- no requirements. At Level Zero, organizations fly by the seat of
their pants; they make broad assumptions that they know what to build;
they gamble that the time they save by not gathering requirements will
not be squandered later because they deliver either too much or too little.
Sometimes this gamble works, but more often than not, a product is
released that is missing functionality, has functions that are not needed,
or is of poor quality. These problems will have varying degrees of impact,
depending on the customer and the criticality of the software, but if the
consequences are severe enough, they may prompt the organization to
start "doing requirements" (and to create an RM process along the way).
Level One --Written Requirements
The first step up from the chaos of no requirements is simply to write the
requirements. White boards and sticky notes don't count. Any medium
that cannot be backed-up and restored is so fraught with risk that we will
not consider it here.
Once you write requirements, several benefits become obvious.
First, you have a real basis for a contract with your customer. If you write
them well, the requirements can clearly state your understanding of what
the customer wants you to build, and they can read the requirements and
agree (or disagree).
Second, everyone on your development team has a basis for doing his or
her work. This obviously includes the architects and designers, who can
start thinking about how to architect the system to meet customer
expectations, but it also includes the testers, who can get a very early
start writing test cases, upon which they can later base test procedures
and scripts.
Third, as you staff up the project, new members, too, will have a source
for figuring out what the application or system is supposed to do. And
because written requirements can be backed up and restored if necessary,
you will have taken a big step toward reducing risk.
How about the cost? Someone -- or perhaps a team of people -- must take
the time to do the writing. And unless the team is making up the
requirements, there is effort involved in talking to the customer to find out
what they want. Maintenance is also a time/cost factor; unless they are
kept up-to-date, the requirements will become useless. And whoever is
responsible for maintenance must learn and implement some "tool" to do
the writing, even if it is simply Word or Notepad.
Is it worth the time and effort? To answer this question, you have to
compare the cost to the potential consequences of not expending the
3. effort to record the requirements. What will happen if you don't build and
deliver what your customer wants? What will happen if you build too
much? If the answer is "not much," then it's not a problem. But if
delivering the wrong system would mean a major drop in your stock price
or an unhappy customer, well, then you might want to make the
investment.
Level Two -- Organized
At this level an organization deals with things like the quality of the
requirements, their format, their security, where they are stored, and how
to keep track of different versions.
The goal of a requirement is to clearly communicate the proposed
behavior of the software to a diverse set of constituents: users,
customers, and other stakeholders, as well as the development team. This
is a tall order and not easily accomplished. A good set of requirements
does this job well; a bad one does not. Good requirements are
understandable by stakeholders who specify them; they are also usable by
the architect, developers, and testers. To achieve this, they must be not
only readable, but also unambiguous and testable.
Formatting
Requirements must also be formatted effectively. Consistent numbering
schemes, headers, fonts, and a good table of contents make your
documents easier to read, understand, and use. Even a well-written
requirement can be rendered useless if it's poorly formatted. Formatting is
a simple thing, but it's often overlooked in the rush to get the
requirements "done." Document templates can help, as can simple
formatting standards for requirements documents.
Accessibility, Security, and Version Control
Have you ever become frustrated because you couldn't find a
requirements document? At Level Two, you need a central, well known
location for the requirements, one that is accessible by all users. Think
about security, too. Whether you use simple file system security or a more
sophisticated technique, limiting the ability to modify requirements to
authorized persons only can help ensure the requirements' integrity.
Instituting version control for your requirements can also save time and
prevent frustration by ensuring that you always know whether or not you
are working on the most current versions of the specifications. In addition,
you will always know who has made a change and why they made it.
These are not the only benefits of getting to Level Two, because you will
automatically enhance the advantages of Level One. When your
requirements are more readable and easier to understand (and more
trustworthy), you will have a better basis for a contract with the customer,
the development team will find the requirements easier to use, and new
staff will be able to come up to speed more quickly.
4. Costs associated with getting to Level Two relate mostly to training and
review. Writing quality requirements is not a simple task. Unless you are
lucky enough to have skilled analysts already on staff, you will have to
train your team. Getting to, and staying at, a given maturity level will
require consistent review of requirements documents and some level of
"process enforcement." These are additional tasks that take time.
Of course, these costs are counterbalanced by the obvious advantages in
ensuring that the requirements are right: less rework and better customer
acceptance, to name two. If you have to get it right the first time, the
costs are probably worth it.
Level Three -- Structured
Getting to Level Three involves being more specific about the "types" of
requirements you gather. Are they functional or nonfunctional? Business
or system? Features or software requirements? How about customer,
marketing, and user requirements? Making these distinctions helps you
get a better understanding of the requirements and manage them better.
Getting to Level Three also means adding information about the
requirements, beyond the basic text. You can provide this additional
information in the form of "attributes," which will help you take a big step
up in managing and reporting on the requirements.
Getting Your Types Straight
As you think about the many possible types of requirements, you should
consider two particular issues.
The first issue arises if you do not distinguish among different types of
requirements. If your current requirements specification simply contains a
big list of requirements with no indication of their type, it is likely that the
list contains a mix of different types. For example, one requirement might
be "The supplier's help desk shall respond to 90 percent of all trouble
tickets within four hours," and another might be "The system shall support
automatic checking of prerequisites."
Although these are both valid requirements, they are clearly directed at
different concerns. The first is a requirement for the support organization
of the company supplying the software; the second is a specification for
what the software must do. Without indications of type, a long list of
requirements can cause confusion and waste readers' time. Those looking
for software requirements will get distracted by the support requirements,
and vice versa. It is also difficult to run a report, for example, to show all
of the software requirements.
The second issue relates to having requirement types but no agreement
on what they mean. An interesting exercise in such a case is to ask team
members who must use the requirements to write definitions for the
various requirement types. You might be surprised at the variety of
interpretations. Clearly, if one person defines a "user requirement" as "a
business need the end user thinks the future system must perform so that
he can do his job" and another defines it as "a requirement for the user
5. experience," then there is a problem.
Attributes
Let's turn now to the concept of requirements attributes, another Level
Three capability. All requirements are not created equal: Some are more
important than others; some are more stable than others; some may be
intended for one release, some for another release. These are important
things to keep track of, and adding attributes for requirements can help
you do so. Attributes include information that supplements the
requirement text and helps you better understand and manage your
requirements.
But how do you know what attribute information is needed? It depends on
the needs of those who will use the requirements information. One
common mistake is to blindly use a predefined set of attributes from
another project or requirements tool (like the one that comes with
Rational® RequisitePro,® for example). Project templates are a great
start, but you will likely have to modify the template to your needs.
Otherwise, it may saddle you with attributes that you don't need and omit
many you do need. For a large project that assigns requirements to
different analysts, an "owner" attribute would be very useful; but such an
attribute may not make sense for a small project on which one person
"owns" all the requirements. You need to understand how the
requirements will be used in order to understand what attributes are
necessary. What reports and queries will you need to support? What
metrics must you keep? Getting answers to these questions up front will
help you start on the right foot.
Benefits of getting to Level Three revolve around better understanding and
easier management. Well-structured requirements clearly identify different
requirement types, and attributes provide the ability to query and filter
groups of requirements; this means that team members have to do far
less detective work and guesswork to identify their responsibilities and
tasks. Better typing of requirements also provides greater assurance that
the team has identified all important requirements. The main cost of
getting to Level Three is in planning and maintenance. Determining
appropriate requirement types and attributes is not a trivial task. A mini-
project in itself, it involves talking to the requirements users to determine
what they need. Usually this information is captured in a Requirements
Management Plan (RMP). Then, requirements attributes are of little use if
they are not kept up-to-date, so there is a maintenance burden that goes
beyond the one for Level Two. There is an increased cost too, because
determining the correct attribute values takes time. Often, when
organizations get to Level Three, they institute the use of a requirements
management tool (like Rational RequisitePro). This has large benefits that
often outweigh the cost of purchasing, updating, and administering the
software.
Level Four -- Traced
Implementing the previous three levels will get you to the point where you
can determine and track requirements relationships. Most systems of any
6. significant complexity will have a hierarchy of requirements. In a systems
engineering environment, this hierarchy starts with system requirements
and moves down to subsystem requirements, program requirements, and
element requirements. In the Rational Unified Process, the hierarchy starts
with user needs, proceeds to features, and then goes on to use cases. The
ability to keep track of these relationships is commonly called traceability,
and it entails identifying and documenting the derivation path (upward)
and allocation/flowdown path (downward) of requirements in the
hierarchy. Traceability provides the ability to understand how changes to
one requirement might affect others (impact analysis) and can also help
determine if your requirements are complete (coverage analysis).
Usually, an organization at Level Four will develop an explicit traceability
strategy prior to starting a project and then document it in the
requirements management plan. The strategy will define the requirements
levels and how they fit in the hierarchy. In addition, it will lay down some
"rules" for requirements relationships. For example, one rule might be that
for every "user need" there must at least be one "feature," and for each
feature there must be at least one use case. Implementing a requirements
management process like this sets up capability for sophisticated
reporting, as we described earlier.
Coverage analysis reports show whether each high-level requirement has
a lower level requirement associated with it. This helps you determine
whether you have coverage holes. For example, if you have a feature that
does not have a use case associated with it, the resulting software may be
missing functionality. Or if you have a use case with no associated feature,
you may be implementing functionality with no business value.
Impact analysis reports are primarily intended for managing change. They
clearly show how a change to one requirement may impact others, which
makes it much easier to either justify or resist changes. For example, if
someone desires to change a feature, and an impact report shows that
doing so will cause changes to several use cases (and slow down the
project schedule), it is easier to see how to weigh costs against benefits
for the feature change.
These benefits of tracing requirements are significant, but again, they are
not without cost. The effort involved in entering and maintaining the trace
relationships is not trivial. Defining, running, and analyzing the coverage
and impact reports takes time and effort. Requirements tracing can be
done manually via simple tables in Word or Excel in very small projects,
but complex projects often need a requirements management tool like
Rational RequisitePro. The benefits of using such a tool are significant, but
as we noted earlier, there is a cost associated with purchasing,
maintaining, and providing training for the tool.
Level Five -- Integrated
It is often the case that requirements are used up front to get agreement
from the customer on what the software is supposed to do, but then those
requirements are not really tied in to the way the software is developed.
This results in stale requirements and software that doesn't meet its
7. objectives. Reaching Level Five means integrating the requirements
management process with the rest of your software development
environment. It means using requirements directly in software design,
change management, testing, and project management.
Software that does what the customer expects is built to comply with the
requirements -- that is, the team's software development process uses the
requirements as a key input. The system's architects and designers follow
a process to ensure that all of the requirements are implemented in the
design; the Rational Unified Process does this by treating use cases as the
input artifact for the analysis and design discipline.
Integrating requirements into your change management process helps
ensure that no changes are made to requirements without review and
approval. And relating each change request to an existing or new
requirement helps to limit feature creep.
Requirements-based testing is also an important part of verifying that the
software meets its objectives. Just as designers must use requirements to
design the system, testers must use them to create test cases and other
testing artifacts.
Since requirements are the basis for the whole development process,
project managers should have direct access to a project's status in relation
to the requirements. This includes metrics about new requirements,
requirements implemented, requirements tested, and requirement change
requests.
A comprehensive, requirements-based software development process as
described here takes significant planning, training, and process
enforcement. Software development tools are also an important part of
implementing such a process. Visual modeling tools such as Rational
Roseý or Rationalý XDE,ý change management tools such as Rationalý
ClearQuest,ý requirements management tools such as Rational
RequisitePro, and project status reporting tools such as Rationalý
ProjectConsole, can all significantly enhance your organization's ability to
get to the highest level of RM maturity. Again, although these tools have
clear benefits, they also have associated costs for purchase, maintenance,
and training.
Requirements Management Tool Support
Until Level Five, it is theoretically possible to do everything that we have
talked about either "manually" or with general-purpose tools like a word
processor and spreadsheet. However, starting at Level Two, an RM tool
can help you be far more efficient and consistent. Table 1 shows how the
important features of Rational RequisitePro support key characteristics of
the five RM maturity levels.
Table 1: How Rational RequisitePro Supports RMM Levels
8. Rational RequisitePro Feature Maturity Level
Dynamic integration between Microsoft Word ® and One -- Written
requirements database Two --Organized
Secure central requirements repository Two -- Organized
User security Two -- Organized
Requirements revision history Two -- Organized
Web interface Two -- Organized
Requirements project templates Three -- Structured
User-defined requirement types, requirements
Three -- Structured
attributes, and document types
Requirements attributes and query capability Three -- Structured
Requirements traceability and coverage analysis Four -- Traced
Impact of requirement change Four -- Traced
Integrations with other software development tools Five -- Integrated
RUP Support
The five levels we have been talking about encompass a requirements
management process. A process determines and documents who does
what, when they do it, and what things they produce. It takes time and
effort to decide what the process should be and then to document it. An
organization can save resources by not reinventing the wheel, and by
adapting a standard process to suit their own needs. The Rational Unified
Process (RUP), for example, is divided into disciplines, one of which is the
Requirements Management Discipline. If you look at that discipline, you
will notice that it contains a workflow detailing many of the concepts we
have talked about here. Starting with RUP can give an organization a
valuable head start on improving RM maturity.
Evaluate and Move Up
The goal of this article has been to describe the best practices
organizations adopt as their requirements management efforts mature,
and they move to new levels of sophistication. The five levels we described
should provide a framework for you to evaluate your own organization and
understand where you stand and what needs improvement. It should also
provide a way for you to understand the benefits and costs involved in
moving up to higher levels of requirements management maturity.
For more information on the products or services discussed in this
9. article, please click here and follow the instructions provided.
Thank you!
Copyright Rational Software 2003 | Privacy/Legal Information