The document discusses several techniques for requirements elicitation and analysis including acceptance and evaluation criteria definition, benchmarking, business rules analysis, data dictionary and glossary, data flow diagrams, data modeling, document analysis, estimation, focus groups, functional decomposition, interface analysis, and interviews. Each technique is described in terms of its purpose, description, elements, and usage considerations to help define requirements and evaluate solutions.
Discover, analyze, and combine customer experiences and successfully reflect them into strategy
Purpose of the text analysis
Recognize relevance, assess the situation and act purposefully
The solution uses the Natural Language Processing (NLP) to „understand” facts, sentiments and their context.
The barriers of otherwise isolated data silos can be overcome and joint analysis of structured and unstructured information (text flow) enabled.
The relevant information will be detected, extracted, and semantically enriched with company-specific metadata. Purpose: creation of customer or product-specific documentation to ensure the end-to-end management using workflow engine.
NLP allows to extract information about interesting entities and their relationships in order to derive precise and relevant RDF-Triples (Subject <> Predicate <> Object). In this way, the causes of events can be determined – the answer to the question of "why something happens" – in order then to act
targeted and appropriate to the situation.
The new chances
The early discovering of new trends and the correct action towards the changed customer behavior.
Industrialization of processes and benchmarking (Best Practice incl. KPI).
Linking macro-analysis with micro-analyses for improved understanding of natural and human-caused risks.
Macro-analyses: Identification of trends and patterns for the determination of the strategy and methodology (discover new insights about the opportunities, behavior, performance, etc.)
Micro-analyses: Knowledge about single customers or support of single activities, like diagnoses, assessments and consultations.
Ability to discover operational challenges and opportunities in real time and to answer them proactively.
Semantics as a Solution
Semantics are based on relationships between data and are therefore ideal tool for linking and searching for complex structured and unstructured data with the standard query SPARQL.
With semantic solutions, all sources are linked and isolated data silos avoided.
Solving Semantic Disparity and Explanation Problems in Regulatory Compliance Dr.-Ing. Sagar Sunkle
Modern enterprises increasingly face the challenge of keeping pace with regulatory compliances. Semantic disparity between regulation texts, their interpretations, and operational specifics of enterprise often leads enterprises to situations where it becomes difficult for them to establish what compliance means, how they are supposed to affect it in the operational practices, and how to prove that they comply when asked for explanations of (non-)compliance. We take a step toward reducing the semantic disparity by using semantic vocabularies to map regulations with available operational details of enterprise and utilize them in enacting compliance. We also propose to provide explanations of proofs of (non-)compliance. We report our ongoing work in this regard using the design science research (DSR) paradigm. Initial iterations of design cycle from DSR have been useful to us in identifying and matching stakeholder-specific goals in solving these problems.
Itlc hanoi ba day 3 - thai son - data modellingVu Hung Nguyen
https://www.facebook.com/events/535707009911719/
(ITLC HN) BA DAY3: CHIẾN LƯỢC THIẾT KẾ MÔ HÌNH DỮ LIỆU
1.Thời gian: 18:30 - 21:00, 10/9/2015 (Tối thứ 5)
2. Địa điểm: HATCH - Tầng 14 - 195B Đội Cấn (http://nest.hatch.vn/nest-14.html)
3. Tổ chức: Ban tổ chức sự kiện ITLC Hà Nội
4. Chương trình:
18:30 - 18:45: Đón khách
18:45 - 19:00: Nguyễn Mạnh Cường (Fis) Giới thiệu ITLC Hà Nội
19:00 - 19:30: Thái Sơn chia sẻ “Một số mô hình dữ liệu mẫu trong phân tích nghiệp vụ”
19:30 - 19:50: Lê Phú Cường chia sẻ “Chiến lược lưu giữ dữ liệu lịch sử”
19:50 - 20:50: Panel cùng với: Thái Sơn, Lê Phú Cường, Lê Văn Duy
20:50 - 21:00: Tổng kết sự kiện và chụp hình kỷ niệm
5. Đăng ký: theo form sau đây http://topi.ca/baday3
6. Phí tham gia: 100K
7. Liên hệ, giải đáp: Lê Đại Nam: 0902-261-239
Xem thêm sự kiện BA1 tại đây: https://www.facebook.com/events/1616821285258614/
Xem thêm sự kiện BA2 tại đây: https://www.facebook.com/events/1669594633274443/
Example data specifications and info requirements framework OVERVIEWAlan D. Duncan
This example framework offers a set of outline principles, standards and guidelines to describe and clarify the semantic meaning of data terms in support of an Information Requirements Management process.
It provides template guidance to Information Management, Data Governance and Business Intelligence practitioners for such circumstances that need clear, unambiguous and reliable understanding of the context, semantic meaning and intended usages for data.
A template defining an outline structure for the clear and unambiguous definition of the discreet data elements (tables, columns, fields) within the physical data management layers of the required data solution.
Business Semantics for Data Governance and StewardshipPieter De Leenheer
Data quality and regulations are perpetual drivers for Data Governance and Stewardship solutions that systematically monitor the execution of data policy. And yet, there is a long road ahead to achieve Trust in Data. It is still a relatively unknown topic or comes with trauma from past failed attempts; there is no political framework with executive champions, leading to reactive rather than proactive behavior, and software support is marginal.
Data Governance and Stewardship requires automation of business semantics management at its nucleus, in order to achieve a wide adoption and confluence of Data Trust between business and IT communities in the organization.
In this lecture, we start by reviewing 'C' in ICT and reflect on the dilemma: what is the most important quality of data: truth or trust? We review the wide spectrum of business semantics. We visit the different phases of data pain as a company grows, and we map their situation on this spectrum of semantics.
Next, we introduce the principles and framework for business semantics management to support data governance and stewardship focusing on the structural (what), processual (how) and organizational (who) components. We illustrate with stories from the field.
Discover, analyze, and combine customer experiences and successfully reflect them into strategy
Purpose of the text analysis
Recognize relevance, assess the situation and act purposefully
The solution uses the Natural Language Processing (NLP) to „understand” facts, sentiments and their context.
The barriers of otherwise isolated data silos can be overcome and joint analysis of structured and unstructured information (text flow) enabled.
The relevant information will be detected, extracted, and semantically enriched with company-specific metadata. Purpose: creation of customer or product-specific documentation to ensure the end-to-end management using workflow engine.
NLP allows to extract information about interesting entities and their relationships in order to derive precise and relevant RDF-Triples (Subject <> Predicate <> Object). In this way, the causes of events can be determined – the answer to the question of "why something happens" – in order then to act
targeted and appropriate to the situation.
The new chances
The early discovering of new trends and the correct action towards the changed customer behavior.
Industrialization of processes and benchmarking (Best Practice incl. KPI).
Linking macro-analysis with micro-analyses for improved understanding of natural and human-caused risks.
Macro-analyses: Identification of trends and patterns for the determination of the strategy and methodology (discover new insights about the opportunities, behavior, performance, etc.)
Micro-analyses: Knowledge about single customers or support of single activities, like diagnoses, assessments and consultations.
Ability to discover operational challenges and opportunities in real time and to answer them proactively.
Semantics as a Solution
Semantics are based on relationships between data and are therefore ideal tool for linking and searching for complex structured and unstructured data with the standard query SPARQL.
With semantic solutions, all sources are linked and isolated data silos avoided.
Solving Semantic Disparity and Explanation Problems in Regulatory Compliance Dr.-Ing. Sagar Sunkle
Modern enterprises increasingly face the challenge of keeping pace with regulatory compliances. Semantic disparity between regulation texts, their interpretations, and operational specifics of enterprise often leads enterprises to situations where it becomes difficult for them to establish what compliance means, how they are supposed to affect it in the operational practices, and how to prove that they comply when asked for explanations of (non-)compliance. We take a step toward reducing the semantic disparity by using semantic vocabularies to map regulations with available operational details of enterprise and utilize them in enacting compliance. We also propose to provide explanations of proofs of (non-)compliance. We report our ongoing work in this regard using the design science research (DSR) paradigm. Initial iterations of design cycle from DSR have been useful to us in identifying and matching stakeholder-specific goals in solving these problems.
Itlc hanoi ba day 3 - thai son - data modellingVu Hung Nguyen
https://www.facebook.com/events/535707009911719/
(ITLC HN) BA DAY3: CHIẾN LƯỢC THIẾT KẾ MÔ HÌNH DỮ LIỆU
1.Thời gian: 18:30 - 21:00, 10/9/2015 (Tối thứ 5)
2. Địa điểm: HATCH - Tầng 14 - 195B Đội Cấn (http://nest.hatch.vn/nest-14.html)
3. Tổ chức: Ban tổ chức sự kiện ITLC Hà Nội
4. Chương trình:
18:30 - 18:45: Đón khách
18:45 - 19:00: Nguyễn Mạnh Cường (Fis) Giới thiệu ITLC Hà Nội
19:00 - 19:30: Thái Sơn chia sẻ “Một số mô hình dữ liệu mẫu trong phân tích nghiệp vụ”
19:30 - 19:50: Lê Phú Cường chia sẻ “Chiến lược lưu giữ dữ liệu lịch sử”
19:50 - 20:50: Panel cùng với: Thái Sơn, Lê Phú Cường, Lê Văn Duy
20:50 - 21:00: Tổng kết sự kiện và chụp hình kỷ niệm
5. Đăng ký: theo form sau đây http://topi.ca/baday3
6. Phí tham gia: 100K
7. Liên hệ, giải đáp: Lê Đại Nam: 0902-261-239
Xem thêm sự kiện BA1 tại đây: https://www.facebook.com/events/1616821285258614/
Xem thêm sự kiện BA2 tại đây: https://www.facebook.com/events/1669594633274443/
Example data specifications and info requirements framework OVERVIEWAlan D. Duncan
This example framework offers a set of outline principles, standards and guidelines to describe and clarify the semantic meaning of data terms in support of an Information Requirements Management process.
It provides template guidance to Information Management, Data Governance and Business Intelligence practitioners for such circumstances that need clear, unambiguous and reliable understanding of the context, semantic meaning and intended usages for data.
A template defining an outline structure for the clear and unambiguous definition of the discreet data elements (tables, columns, fields) within the physical data management layers of the required data solution.
Business Semantics for Data Governance and StewardshipPieter De Leenheer
Data quality and regulations are perpetual drivers for Data Governance and Stewardship solutions that systematically monitor the execution of data policy. And yet, there is a long road ahead to achieve Trust in Data. It is still a relatively unknown topic or comes with trauma from past failed attempts; there is no political framework with executive champions, leading to reactive rather than proactive behavior, and software support is marginal.
Data Governance and Stewardship requires automation of business semantics management at its nucleus, in order to achieve a wide adoption and confluence of Data Trust between business and IT communities in the organization.
In this lecture, we start by reviewing 'C' in ICT and reflect on the dilemma: what is the most important quality of data: truth or trust? We review the wide spectrum of business semantics. We visit the different phases of data pain as a company grows, and we map their situation on this spectrum of semantics.
Next, we introduce the principles and framework for business semantics management to support data governance and stewardship focusing on the structural (what), processual (how) and organizational (who) components. We illustrate with stories from the field.
Explanation of Proofs of Regulatory (Non-)Compliance Using Semantic VocabulariesDr.-Ing. Sagar Sunkle
With recent regulatory advances, modern enterprises have to not only comply with regulations but have to be prepared to provide explanation of proof of (non-)compliance. On top of compliance checking, this necessitates modeling concepts from regulations and enterprise operations so that stakeholder-specific and close to natural language explanations could be generated. We take a step in this direction by using Semantics of Business Vocabulary and Rules to model and map vocabularies of regulations and operations of enterprise. Using these vocabularies and leveraging proof generation abilities of an existing compliance checking technique, we show how such explanations can be created. Basic natural language explanations that we generate can be easily enriched by adding requisite domain knowledge to the vocabularies.
RuleML2015: Explanation of proofs of regulatory (non-)complianceusing semanti...RuleML
With recent regulatory advances, modern enterprises have to not only comply with regulations but have to be prepared to provide explanation of proof of (non-)compliance. On top of compliance checking, this necessitates modeling concepts from regulations and enterprise operations so that stakeholder-specific and close to natural language explanations could be generated. We take a step in this direction by using Semantics of Business Vocabulary and Rules to model and map vocabularies of regulations and operations of enterprise. Using these vocabularies and leveraging proof generation abilities of an existing compliance engine, we show how such explanations can be created. Basic natural language explanations that we generate can be easily enriched by adding requisite domain knowledge to the vocabularies.
The data analyst occupational brief. This document provides coverage for the minimum requirement expected in the level 4 data analyst apprenticeship. As this document is no longer maintained by the tech partnership and is essential to the apprenticeship it is worth having a copy. Information is accurate for the level 4 data analyst apprentice as of March 2020.
03. Business Information Requirements TemplateAlan D. Duncan
A template for the clear and unambiguous definition of business data and information requirements. (cf. “Business Requirements Document”, “Functional Specification” or similar from standard SDLC processes). As such, the contents will typically form the basis for population and publication of a business glossary of information terms.
The importance of capturing metadata has been a topic of many webinars, teleconferences, and white papers over the last several years. There’s has also been an increasing emphasis on “building metadata repositories”.
Agility by Design - Building Software to Lasteprentise
The implementation of enterprise systems brings with it great promise of better information, consistent systems, and reduced operational costs. Achieving that promise, however, is an immense challenge.
View the original Blog post: http://www.eprentise.com/blog/data-systems/agility-by-design-building-software-to-last/
Website: www.eprentise.com
Twitter: @eprentise
Google+: https://plus.google.com/u/0/+Eprentise/posts
Facebook: https://www.facebook.com/eprentise
Chapter 2 LabDo the two programming exercises listed below. YouEstelaJeffery653
Chapter 2 Lab
Do the two programming exercises listed below. You will create a separate C++ program for each of the two exercises using the following naming conventions: yourlastname_Ch2lab.n.cpp where “n” is the exercise number.
1. Flash Drive Price - An electronics company makes 64 gigabyte USB flash drives that cost them $8.00 apiece to produce. Write a program to determine how much the company should sell them for if it wants to make a 35 percent profit. Display the result on the screen. Output should look like this:
2. Basketball Player Height –The star player of a high school basketball team is 75 inches tall. Write a program to compute and display the height in feet/inches form. Hint: Try using the modulus and integer divide operations.
Your programs should conform to the Programming Style Requirements as listed in Blackboard under Course Content. In addition, all output should be labeled appropriately (Ex. Number of slices are: nn). Turn in your 2 source (.cpp) files to Blackboard (be sure to attach all files before pressing SUBMIT).
Assignment 1: Individual Report – Developing an evidence base for your recommendations. Weight: 30%
Length: Maximum of 1500 words (+/- 10%)
Executive Summary (not counted in word count)
You need to provide a summary of the following information in PARAGRAPH format:
· Purpose of the report (e.g., analysis of two aspects of management that might be implicated in the uptake of a product currently being developed at REIDS-SPORE)
· Identify the two management theories and sub-theories, e.g. Ethics, CSR, HRM matters, Leadership, you use to analyse product uptake at client firms. Provide a brief justification/rationale of what advantages these frameworks offer.
· Say -- in your own words – the importance of getting the management systems right when adopting a new energy technology
Introduction (150 - 200 words)
An introduction is the overall ‘roadmap’ for the report document. In this section, you are meant to provide the context for the report’s topic. You are also meant to outline the topics that will be covered in each subsequent section of the report. Finally, you will articulate the main AIM of the report (what are you trying to accomplish here). In other words, restate the problem as a research question which this report will answer
Part 1 Macro, Meso & Micro Context of Singapore and your chosen sector (350-450 words)
Topics to cover here include but are not limited to:
· Overview of Sinagpore’s energy needs and how hydrogen might be used to address them (e.g., as described in white papers issued by energy institutions, by industry peak bodies, etc.)
· Overview of the sustainability challenge in Singapore towards meeting those energy needs with a reducing carbon footprint (e.g., to meet the Paris COP 2015 targets)
· Examples of what has been tried in your chosen sector (whether successful or not), what is being planned for - this may come from industry journ ...
06. Transformation Logic Template (Source to Target)Alan D. Duncan
This document template defines an outline structure for the clear and unambiguous definition of transmission of data between one data storage location to another. (a.k.a. Source to Target mapping)
This short presentation briefly describes how to effectively elicit, analyze, communicate and manage requirements from the business all the way down to the system level. Currently under development by Perry McLeod, CBAP, PMP it argues that requirements must be examined in focus, perspective and depth. Perry welcomes any feedback you may have which will help to develop this model for publication to the business analysis community.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Explanation of Proofs of Regulatory (Non-)Compliance Using Semantic VocabulariesDr.-Ing. Sagar Sunkle
With recent regulatory advances, modern enterprises have to not only comply with regulations but have to be prepared to provide explanation of proof of (non-)compliance. On top of compliance checking, this necessitates modeling concepts from regulations and enterprise operations so that stakeholder-specific and close to natural language explanations could be generated. We take a step in this direction by using Semantics of Business Vocabulary and Rules to model and map vocabularies of regulations and operations of enterprise. Using these vocabularies and leveraging proof generation abilities of an existing compliance checking technique, we show how such explanations can be created. Basic natural language explanations that we generate can be easily enriched by adding requisite domain knowledge to the vocabularies.
RuleML2015: Explanation of proofs of regulatory (non-)complianceusing semanti...RuleML
With recent regulatory advances, modern enterprises have to not only comply with regulations but have to be prepared to provide explanation of proof of (non-)compliance. On top of compliance checking, this necessitates modeling concepts from regulations and enterprise operations so that stakeholder-specific and close to natural language explanations could be generated. We take a step in this direction by using Semantics of Business Vocabulary and Rules to model and map vocabularies of regulations and operations of enterprise. Using these vocabularies and leveraging proof generation abilities of an existing compliance engine, we show how such explanations can be created. Basic natural language explanations that we generate can be easily enriched by adding requisite domain knowledge to the vocabularies.
The data analyst occupational brief. This document provides coverage for the minimum requirement expected in the level 4 data analyst apprenticeship. As this document is no longer maintained by the tech partnership and is essential to the apprenticeship it is worth having a copy. Information is accurate for the level 4 data analyst apprentice as of March 2020.
03. Business Information Requirements TemplateAlan D. Duncan
A template for the clear and unambiguous definition of business data and information requirements. (cf. “Business Requirements Document”, “Functional Specification” or similar from standard SDLC processes). As such, the contents will typically form the basis for population and publication of a business glossary of information terms.
The importance of capturing metadata has been a topic of many webinars, teleconferences, and white papers over the last several years. There’s has also been an increasing emphasis on “building metadata repositories”.
Agility by Design - Building Software to Lasteprentise
The implementation of enterprise systems brings with it great promise of better information, consistent systems, and reduced operational costs. Achieving that promise, however, is an immense challenge.
View the original Blog post: http://www.eprentise.com/blog/data-systems/agility-by-design-building-software-to-last/
Website: www.eprentise.com
Twitter: @eprentise
Google+: https://plus.google.com/u/0/+Eprentise/posts
Facebook: https://www.facebook.com/eprentise
Chapter 2 LabDo the two programming exercises listed below. YouEstelaJeffery653
Chapter 2 Lab
Do the two programming exercises listed below. You will create a separate C++ program for each of the two exercises using the following naming conventions: yourlastname_Ch2lab.n.cpp where “n” is the exercise number.
1. Flash Drive Price - An electronics company makes 64 gigabyte USB flash drives that cost them $8.00 apiece to produce. Write a program to determine how much the company should sell them for if it wants to make a 35 percent profit. Display the result on the screen. Output should look like this:
2. Basketball Player Height –The star player of a high school basketball team is 75 inches tall. Write a program to compute and display the height in feet/inches form. Hint: Try using the modulus and integer divide operations.
Your programs should conform to the Programming Style Requirements as listed in Blackboard under Course Content. In addition, all output should be labeled appropriately (Ex. Number of slices are: nn). Turn in your 2 source (.cpp) files to Blackboard (be sure to attach all files before pressing SUBMIT).
Assignment 1: Individual Report – Developing an evidence base for your recommendations. Weight: 30%
Length: Maximum of 1500 words (+/- 10%)
Executive Summary (not counted in word count)
You need to provide a summary of the following information in PARAGRAPH format:
· Purpose of the report (e.g., analysis of two aspects of management that might be implicated in the uptake of a product currently being developed at REIDS-SPORE)
· Identify the two management theories and sub-theories, e.g. Ethics, CSR, HRM matters, Leadership, you use to analyse product uptake at client firms. Provide a brief justification/rationale of what advantages these frameworks offer.
· Say -- in your own words – the importance of getting the management systems right when adopting a new energy technology
Introduction (150 - 200 words)
An introduction is the overall ‘roadmap’ for the report document. In this section, you are meant to provide the context for the report’s topic. You are also meant to outline the topics that will be covered in each subsequent section of the report. Finally, you will articulate the main AIM of the report (what are you trying to accomplish here). In other words, restate the problem as a research question which this report will answer
Part 1 Macro, Meso & Micro Context of Singapore and your chosen sector (350-450 words)
Topics to cover here include but are not limited to:
· Overview of Sinagpore’s energy needs and how hydrogen might be used to address them (e.g., as described in white papers issued by energy institutions, by industry peak bodies, etc.)
· Overview of the sustainability challenge in Singapore towards meeting those energy needs with a reducing carbon footprint (e.g., to meet the Paris COP 2015 targets)
· Examples of what has been tried in your chosen sector (whether successful or not), what is being planned for - this may come from industry journ ...
06. Transformation Logic Template (Source to Target)Alan D. Duncan
This document template defines an outline structure for the clear and unambiguous definition of transmission of data between one data storage location to another. (a.k.a. Source to Target mapping)
This short presentation briefly describes how to effectively elicit, analyze, communicate and manage requirements from the business all the way down to the system level. Currently under development by Perry McLeod, CBAP, PMP it argues that requirements must be examined in focus, perspective and depth. Perry welcomes any feedback you may have which will help to develop this model for publication to the business analysis community.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
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…
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
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!
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
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.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
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.
1. Acceptance and Evaluation Criteria Definition
Purpose
o To define the REQthat mustbe metinorder fora solutiontobe consideredacceptable
Description
o Determine whichREQcanmost effectivelybe usedasevaluationcriteria.
Acceptance – To determine apossiblesolution
Evaluation – To compare multiple solutions(usingbanknotes)
Elements
o Testability –The REQ must be:
Detailedintonaatomicform/ UC forsolutiontest
o Determine ranking
Determine the orderof importance forthe requirements
The Moscow technique
o Determine scoring
Customersolutionforthe REQ
o Stakeholdermustagree onthe criteria
o The Moscow technique –Divide the REQintofour categories
Must – essential,highpriority,successof the solution
Should– important,buthave the workaround
Could– lowpriority,canbe implemented
Won’t– will notbe implemented(maybe inthe future)
Usage Considerations
o Advantages
Agile methodologiesmayrequire thatall the REQ be expressedinthe formof testable
acceptance criteria
Acceptance criteriawhenthe REQexpresscontractual obligations
o Disadvantages
Difficultchangesdue contractual obligation,bothforlegal andpolitical reasons
2. Benchmarking
Purpose
o To compare the strengthsandweaknessesof anORG againstitspeersand competitors.
Description
o Studiesare conductedtocompare organizational practicesagainstthe best-in-classpracticesthat
existwithincompetitorsenterprise ingovernmentorindustry,determininghow theses
companiesachieve theirsuperiorperfomance
o Focusedonstrategies,operationsandprocesses
Elements
o Benchmarkingrequires:
Identifythe areatobe studiedandorganizationsthatare leadersinthe sector
Conducta surveyto understandtheirspractices
Arrange for visitstobest-in-classorganizations
Developaprojectproposal toimplementthe bestpractices
Usage considerations
o Advantages
Providesforthe enterpriseinformationsaboutnew anddifferentmethods,ideiasandtools
o Disadvantages
Benchmarkingistime consuming
Organizationsmaynothave the expertisetoconductthe analysisandacquire or interpret
useful competitive information
Benchmarkingdoesnotprovide competitive advantageandmarketinnovative solutions,since
the solutionisalreadyusedbyothercompanies
3. Business Rules Analysis
Purpose
o To define the rulesthatgoverndecisionsinnaORG andthat define ,constrainor enable
organizational operations
Description
o Directe constrainthe organizationandoperationsof naorganization
o A businesspolicyisanon-actionable thatsuportsabusinessgoal
o A businessrule isaspecific,actionable,testable,thatsuportsabusinesspolicy
Particularycomplex rulesmaybe expressedasa decisiontable ordecisiontree
o The businessrulesshouldbe:
Statedinappropriate terminologytoenable domainSMEsto validate the rules
Documentedandstatedat the atomiclevel
Separatedfromthe processes
Mainteinedinamannerthat enablesthe ORGto monitorandadapt the rules
Elements
o Businessrulesrequire adefinedglossaryof termsandrelationships
o Insure thattheyare independentof anyimplementation,informationorassumptions
o Operative rules
Guiding/forcing/preventingthe actionsof people
Violable:“Allowhome boardingwith23kgof luggage”
In thiscase,whatNeste caso,what are the penaltiesandexceptions(additional rule)
“Charge the excessof baggage”
o Structural Rules
Helpdetermine whensomethingisoris nottrue
Notviolable:“Embarkonlywithboarding”
Usage considerations
o Strengths – Changesto policywithoutalteringthe process,easyevaluation
o Weaknesses –Lengthylistsof businessrulesandconflictbetweenthem.
4. Data Dictionary and Glossary
Purpose
o Defineskeytermsanddatarelevanttoa businessdomain
Description
o Usedto formallyidentifyanddefine all terminologyusedbythe organizationororganizational
unit.
Elements
1. Glossary
o Documentstermesunique tothe domain,inordertoensure thatall stakeholdersunderstood
whatis meantwhencertainwordsare used
o A termrelevanttothe domainanda unique definitionforeach,aswell ascross-referencing
aliases
2. Data Dictionary
o Stantarddefinitionsof dataelements,theirmeanings,andallowable values.Contains
definitionsof eachprimitive dataelementandindicateshow those elementscombine into
composite dataelements
o Primitive DataElements
Name – unique,referencedbythe compositedataelements
Aliases –alternate names
Values/Meanings –listof acceptable values
Description –definitioninthe contextof the solution
o Composite DataElements
Sequences –primitivedatainorder
Repetitions –Multiple occurrencesof the primitive element
Optional Elements –may or may notoccur
Usage Considerations
o Is useful forensuringthatall the stakeholdersare inagreementonthe formatand contentof
relevantinformation,ensuringthatthese termswill be usedconsistently
5. Data Flow Diagrams
Purpose
o Showhowthe informationisinput,processed,stored,andoutputfromasystem
Description
o Providesavisual representationof how the informationis movedthroughasystem:
External Entitiesthatprovide orreceive data
The Processesthattransformdata
The Data Storescollectedforsome periodof time
The Data flowsmovesbetweenexternal entities,processesanddatastores
Elements
1. External Entities
o Source or destinationof data
o Labeledrectangle
2. Data Store
o Locationwhere datais not movingortransforming,butisbeingstoredforfuture use
o Labeledrectangle withasquare
3. Data Process
o Transformsthe data insome way (combining,reordering,converting,filtering,etc).Naasterisk
isusedto identifydataprocessesthathave furtherdecompositionmodels.
o Circle or a rectangle withcurvedcorners
4. Data flow
o Where data isbeingmovedbetweenprocessandnaexternal entity
o Can be specifiedintoresultflows,control flowsandupdate flows
o Single ouforketline labeledwithadescriptorof the databeingmoved
Usage considerations
o Usedas part of a structuredanalysisapproach
o Understandthe range of data withinthe domain
o Usedafter a contextdiagramhas beencompleted
o Prerequisite orconcurrentactivitytodatamodeling
o Strengths
Discoveryforprocessesanddata
Verificationof afunctional decompositionordatamodel
Easy to understand,useful deliverfordevelopingstructuredprogramming
o Weaknesses
Cannoteasilyshowwhoisresponsible forperformingthe workandcannotshow alternative
pathsthrough the same process
6. Data Modeling
Purpose
o Describe the conceptsrelevanttoadomain,the relationshipsbetweenthose concepts,and
information associatedwiththem
Description
o The model takesthe formof a diagram, supportedbytexts
o Representsthe typesof people,places,thingsandconcepts,attributesandrelationships,
importantforbusiness
o Supportedbythe data dictionaryandglossaryandanalysisof businessrules
o Two types:
Entity-relationshipdiagram –relational database
Classdiagram– objectorientation
o Determinedratingbythe technologyplatformof the ORG
Elements
o Logical data modelsdescribe the intormationrelevanttoanORG
o Highlevel ->Descriptionsof the pointsof mostimportance
o Detailed ->Descriptionsof all points
o Physical ->Descriptionsof storage anddata management
o Concept– Somethingof significance forthe domainbeingdescribed,whichdatathe ORGneeds,
musthave a unique identifier,are referredasentitiesorclasses
o Attributes –Definesaparticularpiece of informationassociatedwithaconcept,suchas allowable
valuesandtype of information
o Relacionships –Associationsbetweenthe businessconcept,how informationisusedinthe
operationof the businessandcardinality(numberof relationshipsallowed)
o Metadata – data about the data, context,use andvalidityof businessinformation,determine
whenandwhyna informationstoredinasystemhasbeenchanged
Usage Consideration
1. Advantages
o Offerflexibilityindifferentlevelsof description
o Consistentapproachsupportsthe transitionfromplanning,analysis,designand
implementation
o Strongfoundationinmathematical conceptsandintegrityof information
2. Disadvantages
o Can be complex anddeal withconceptsthatmay notbe familiartothose whohave no
backgroundinTI
o Can be difficulttounderstantforusers
7. Document Analysis
Purpose
o ElicitREQ throughthe studyof the available DOCof existingand comparable solutions,and
identifyrelevantsINFO
Description
o Analysisof businessplans,marketstudies,contracts,requestsforproposals,statementsof work,
memos,guidelines,procedures,trainingguides,custumersuggestions,specificationsof existing
systems,etc
o Usedwhenthe objective istocollectdetailsof existingsolutions,includingRN,entitiesand
attributesforinclusioninthe newsolutionorupgrade the currentsolution
o It isalso appliedinsituationswhere expertsinthe fieldof the soluutionisnotmore onthe
organization,orare not available duringthe elicitation
Elements
1. Preparation
o Evaluate whichexistingDOCaboutthe businessandsystemare relevant,available and
appropriate
2. Documentreview
o Studythe material,identifyingand documentingrelevantdetails
3. Wrap-up
o Reviewandconfirmthe detailsselected
o Organize informationinthe formof REQ
Usage Considerations
0. Advantages –Analysispartof something,use existingmaterials,checkREQindifferent
techniques(ex:interview)
1. Disadvantages –limitedto“as-is”,outdateddocumentation,timeconsumptioncanbe excessive
and tediousprocess
8. Estimation
Purpose
o Forecastcost and effortinvolvedinfindingthe progressof anactivity
Description
o Developabetterunderstandingof possible magnitudeof the costsand effortsassociatedwith
any initiative,whenit’spossibletodetermine the exactcost
o Can not eliminate the uncertainty,seekstoachieve reasonable assessmentof requiredcostsand
efforts
o The lessinformation,more the uncertainty
o Revisionemerge asmore information
o Supportfor historical records
o Importantto evaluate the extentof uncertainty
Elements
1. Analogousestimation –Top-Down,use of similarproject,isnotwell knownatthe begginingof
the project,orderof magnitude (ROM– roughorder of maginitude)
2. ParametricEstimation –Parametersx numberof hours,requireshistorical ascomparative basis
(COCOMOII,functionpoints,pointsof use casesandstorypoints)
3. Bottom-upestimation–Collectsand gathersthe deliveries,activities,tasksandestimatesfor
estimatingsmall items
4. RollingWave – Refinementof estimates,review of future deliveriesbasedonwhatwasdelivered
5. Three-PointsEstimation –Basedon the scenarios(notaverage):
o Optimistic
o Pessimistic
o The most likely
6. Historical Analysis –similartoanalogousestimating,butusedtotop-downandbottom-up.Needs
historical repository
7. Evaluationof specialist –experience of internal orexternal experts
8. Estimationof Delphi –Combinationof the evaluationof the expertandhistory(top-downe
bottom-up),sharingtothe consensus,averageof the three estimates
Usage considerations
0. Advantages –Helpmakingdecisionsbased
1. Disadvantages –Treatmentof the estimate asa compromise,usuallyalteredtoattendthe most
influential stakeholders
9. Focus Groups
Purpose
o Elicitideasandattitudesabouta product,service oropportunityspecificininteractive group,
sharingimpressions,preferencesandneeds
Description
o Similartobrainstorming, more structured,withlessbreadth,creativityandexaggerations
o Meetinginthe same room or remotely
o Sharingand re-evaluationof prospects
o Moderator managesthe work,facilitatesthe session,producesthe report
o Observerrecordsormonitorsthe group,withoutparticipation
o Resultsare analyzedandreportedasthemes
o Mediumusedduringanystage of the cycle
ProductDevelopment –Update of the REQ
Productin production – Reviewsforthe nextdelivery
Elements
1. Preparation
o Participants
6 to 12 participants (canbe extended),varieswiththe topic
Composition
Homogeneous –Similarfeatures,differentperspectivesare notshared
Heterogeneous –Differenthistorical andperspectives,self-censorshipbecause of
discomfort
o Moderator andrecorder
Promote discussion,open-endedquestions,groupinteraction,keepingfocus,neutral,
adaptable andflexible
o DiscussionGuide
Goals/Objectivesof the session(5,6 openquestions)
o Local and Services
Local,support,equipmentsforthe session
2. Conductfocusgroup session
o Moderator guidesthe discussion1-2hoursby a pre-plannedscrip(transparent),toensure
reachinggoals
o Recordercapturesthe group’scomments
3. Produce the report
o Moderator analyzesanddocumentsthe areasof agreementornotbetweenthe participants
and synthesizesonthemes
Usage considerations
0. Advantages –Elicitgroup data ina single sessionsabestime andcost,tounderstandattitudes,
experiencesanddesires,active discussion(personalvisionandperspective)
1. Disadvantages –Distrustand indisposition aboutsensitive topics,difficultyinschedulingthe
group,doen’thelpthe elicitationof ideiasaboutanew product
10. Functional Decomposition
Purpose
o To decompose processes,functional areasordeliveriesintheircomponentparts,allowing
independentanalysisof eachpart
Description
o Breakbiggerproblemintofunctions/smallerdeliveries
o Ensure that the problemisseparatedintosubproblems
Elements
o Identifyhigh-level functionsof naORG or solution
o Breakingtasksintosmallerpieces(sup-processes, activities,recourses)
o HighLevel Function ->Sub-function ->Process ->Activity
Until it can’t be brokenanymore
o Representationbyahierarchydiagram, tree or numbering
o EAP -> Breakthe scope of the projectinphases,workpackagesand deliveries
Usage Considerations
1. Advantages
o Conceptual model of the completedworktodeliveranew businesssolution
o Providesaconsistentview of the scope of the effort
o Assistsestimatinginthatestimatescanbe made forsmaller
2. Disadvantages
o There isno guarantee that all componentswere captured
o Create a inappropriate structure if there isnocomplete understandingof the relationship
betweenthe partsof the problem
11. Interface Analysis
Purpose
o Identifyinterfacesbetweensolutionsand/orcomponentsof the solutionanddefineREQthat
describe howtheywill interact
Description
o Interface isa conexionbetweentwocomponents
o Applicationsof softwarerequireonormore interfaces,of the type:
Users interactingdirectlywiththe system
Amongexternal applications
Betweenhardware devices
o Helpto clarifythe bondariesbetweenapplications
o Distinguishwhichapplicationprovidesspecificfunctionalitieswiththe needsof inputandoutput
data
o Confirmstakeholderswhowill use the interface
o Model for the subsequent analysisof the detailedREQ
o Alsouseful foranon-software solution
Elements
1. Preparate forinterface identification
o Reviewthe actual documentationcontainingindicationsof REQ
2. ConductInterface Identification
o Identifywhatinterfacesare neededfor eachstakeholder:
Describe the interface purpose
Evaluate whichtype of interface isappropriate
Elicithighlevel details,dependingonitstype
Usuary-System–Use prototyping
System-System–Contentandname of the events
3. Define interfaces
o REQ focusedondescribingthe inputsandoutpusof the interface
o Validationrulesandeventsthattriggerinteractions
o Interactionsspecifiedindividually
Usage Considerations
0. Advantages
o Highlevel viewof interoperability
o Planimpacton deliverydate,more accurate andpotential timesavingsandcost
o Planthe collaborationwithothersystemsorprojects
o Negotiationandcooperationbetweenleadersof the involvedapplications
o Preventdifficultiesof integratingmultiple components
1. Disadvantages
o It doesn’tprovide insightsaboutotheraspectsof the solution
o It doesn’tevaluate internalcomponents
12. Interviews
Purpose
o Elicitinformationsfromapersonorgroup oof people throughaconvertationwithna
interviewee,withquestionsanddocumentedresponses
Description
o The interviewermake questionsthathe formuledtoa stakeholder
o Obtainresponsesthatwill be usedtocreate REQ
o StructuredInterview –pre-definedsetof questions
o Non-StructuredInterview –Nopre-definedquestions,opendiscussionof topics
o SuccessFactors
Understandingof the fieldbythe interviewer
Experience inconductinginterviews/Empathy(Rapport)
Skill indocumentingdiscussions
Alertnessandclarityof the interviewee ->Provideinformation
Elements
1. Preparationforthe interview
o Define the focusorthe interview goal
o Identifythe intervieweesinpotencial
Who holdsa confiable/authentic/currentINFO
What’sthe stake inthe initiative
o Designthe interview,adaptedforeachinterviewee
Closedquestions –Unique response (Yes/No)
Openedquestions–Conversation,responseswithjustifatives
Organizationof the questions–Logical orderor priority
Localizationof the participants –Personalyorremote
Time and local of the interview
Necessityornotof scribe or recording
o Contact the interviewees inpotencial
Justificate the interview goal
2. Conductof the interview
o Openingthe interview
Purpose statementandnotestome made and sharedat the end
o Duringthe interview
Focuson goalsand pre-definedquestions
Concernsof the interviewee attendedduringthe interview ordocumentedforfuture
interview
Active listeningtoconfirmthe understandingof the INFO
o Closingthe interview
Checkfor neglectedissues
Summarize the session
Rememberthe reviewprocessandthankthe interviewee
3. Follow-upinterview andconfirmation
o Organize information,sendforreview of the interviewee
o Viewof all the relatedcontext,pointingoutincorrectormissingitems
o Documentinginformationandnottoevaluate the REQ
Usage Considerations
o Advantages
13. Encouragesparticipants andestablishesempathy,simple anddirect
Discussion,comprehensiveexplanations,observingnon-verbal aspects,expressopinions
privatly
o Disadvantages
It doesnotestablishconsensusgroup,andtrainingisnecessarytoconductthe business
domain,riskof influence
Transcriptioncomplex andexpensive,subjecttointerpretation
14. Lessons Learned Process
Purpose
o Compile anddocumentsuccesses,opportunitiesforimprovement,gapsandrecommendations
for improvingperfomance
Description
o Sessionsmayinclude anyformof meetingorforum
Elements
o Reviewof activities,processesanddeliveriesof NA,final product,questionsormanagerial
concerns,performance x plan,rootcause of variations,recommendedcorrectiveactions
Usage Considerations
1. Advantages –Identificationof improvementopportunitiesandassiststaff motivation
2. Disadvantages –Requirespreparationof the teamtoavoidsessionof complaints/guilty,honest
discussioncannothappen,staff maybe reluctantto discussproblems
15. Metrics and Key Performance Indicators
Purpose
o Measuringthe perfomance of solutions,componentsandotherissuesof interesttostakeholders
Description
o Metric: a quantifiable levelindicatortomeasure progress
o Indicator:identifies specificnumerical measure thatrepresentsthe degreeof progresstoward
achievingagoal,objective,outputoractivity
o Keyperformance indicator:Measure the progresstowardagoal or strategicobjective
o Report:Processto informthe partsabout the metricsof the indicatorsinspecifiedformatsand
rangers
o The main componentsare:
Monitoring– Continuousdatacollectiontodeterminehow well asolutionwasimplementedx
expectedresults
Evaluation – Systematicjudgment,determine statusandeffectiveness of the solution,identify
howto improve solution
Elements
1. Indicators
o Identifiesaspecificnumerial measure formeta,impact,output,activityorinput.Five
characteristics:
Clear/ Relevant/Economic/ Adequate /Quantifiable
Interestsof the stakeholderare alsoimportant
o Weaknessescanbe identifiedinsome indicators
o Considerthe source,method,andresponsible forthe collectionandcost
2. Metrics
o Quantifiablelevelsof indicatorsthatare measuredata specificpointintime
Target metric– goal to be achievedoveraperiodof time
o Importantto clearlyunderstandthe baselinestartingpoint,the resourcesdevotedtothe
improvementof the factorsand issuescoveredbythe indicator/political concerns
o Can be a specificpointorrange limit
3. Structure
o Monitoringandevaluationsystemrequiresprocedure of:
Collection –Unitsof analysis,samplingandinstruments
Analysis –Conductinganalysisandconsumerdata
Report– Models,addresses,frequencyandmethods
o Keyfactorsfor qualityassessment:
Reliability –Stabilityandconsistencyof datacollection
Validity –Cleardata anddirectmeasurementof perfomance
Opportunity –Adequacyof the frequencyandlatencydata
4. Reports
o Compare the base-linecurrentmetricsandandtargetmetrics,with calculationsof the
differencespresentedinabsoluteandrelativeterms
o Visual presentationsare more effective thantables,whensupportedbyatextto explainthe
qualitative data
Usage Considerations
0. Advantages
16. o Allowsstakeholderstounderstandhow the solutionmeetsthe goal andhow effectivewere
the inputsandactivitiesforthe developmentof output/solution
o Facilitate organizational alignmentlinkinggoalstoobjectives,supportsolutions,keytasksand
resources
1. Disadvantages
o Collectingtoomuch datathan necessarywill resultinunnecessaryexpensesinthe collection,
analysisandreporting
o Program metricsbureaucraticfailure tocollectdatawithoutgeneratingreportsuseful
17. Non-Functional Requirements Analysis
Purpose
o Describe the qualitiesrequired forasystem, ina complementary functional requirements
character
Description
o Importantfor users anddevelopers
In practice applies whendevelopingasoftware
Elements
1. Category – Checklistof characteritics
o Reliability- Availablewhenneeded
o Performance –Time for implementingactivities
o Operability- Usability
o Security- TrustedInformation
o Compatibility –coexistwithotherapplications
o Maintainability- Changecomponentwithout affectingother
o Portability- Executableindifferentenvironments
2. Measurement
o It mustbe includedasuccessmeasure inthe definitionof REQthat can be tested
3. Documentation
o Declarative descriptions (Ex:The systemshouldprovide 90% of the responses inuptwo
seconds), aspart of the document total of REQ
Usage Considerations
0. Advantages
o Influence onthe acceptance orrejection of the systemby users
1. Disadvantages
o Difficulttodefine, qualityexpectations cannotbe described, the accuracy can impactthe cost
and feasibilityof developing
o
18. Observation
Purpose
o Evaluation of the workenvironment of the stakeholder, todocumentthe detailsof the current
processes toimprove orchange the current process
Description
o Studyingpeopleincarryingoutits functions (jobshadowing/followingpeople around)
o Assistthe execution of the workforunderstandingof itsflow
o Approaches
Passive /invisible –noquestioning,just log
Active / visible –Interactwith the user, questioningthe reasonforthe execution of some
action
o Can participate in the actual workfor practical experience
o It can become a temporary apprentice
o Assistdemonstrationof the process ortask-specificexecuted
Elements
1. Prepare forthe observation
o Determine samplingof userswillbe observedand whatactivities andquestions toask
2. Observe
o Presenttothe observed
o Ensure to the observed thatthere isno question abouthiswork,only observationto study
o Explainthatthere maybe disruptionto questions
o Suggest“thinkingaloud”while working
o Observe the work, take notesnecessary withorwithoutquestions
3. PointObservationWrap-Up–DocumentationandConfirmation
o Get answerstothe original or new
o Summarize the notesforrevisionandclarification
o Many users: compile notes (commonpoints)
Usage Considerations
0. Advantages
o Practical and realisticvisionof the business (“handson”)
o Detailsof the informal communicationand formof the currentwork
1. Disadvantages
o Onlyforexistingprocesses
o Can consume a lotof time
o Can disruptthe observed
o Unusual circumstances orexceptionsmaynotoccur duringthe observation
o It may notwork whenthe currentprocess istoo complex orinvolve otherdifficultworkto
observe
19. Organization Modeling
Purpose
o Describe roles,responsibilitiesandchain ina ORG, alignedwithorganizational goals
Description
o Define the scope andhowan ORG or an unitis structured, formal relationships, rolesand
interfaces
Elements
1. Organizational PurposeandStructure
o Functions – Groupingpeople basedon theirskills orareasof expertise,standard of work, cost
managementeasierandreduces duplicationof work
o Markets – Focus on customers, market,sector, tendstodevelop inconsistenciesandduplicate
work
o Matrix – Differentmanagersin functional areas andproducts, service orgroups
2. Roles
o Specificsetof skills,knowledgeandresponsibilities
3. Interfaces
o Work packages,with REQ qualitystandard,formal orinformal
4. Org Charts
o Chart, featuring:
ORG units– teams,departments, divisions
Reportinglines –Continuous (directauthority) x Dashed(temporarysituation ortransfer
of information)
Rolesandpeople
Usage Considerations
o Advantages –Almostall the ORG have it
o Disadvantages –The organizational redesign maybe controversial, the existence of
informal linesof authority andcommunication are notreflected
20. Problem Tracking
Purpose
o Organizedapproachto screening, managementandresolution of defects, issues,problemsand
risksoverthe activities of AN, ina timelymannertoensure success.
Description
o Problems mayinclude issues, questions,scratches,defects,conflicts,concernsthatmustbe
trackedintothe resolution
o Ensure that issues are notneglected orlost
o For each issue, include anidentification, statusupdate,description of stocks,
monitoring, resolution outcomes, actionsand decisions,priority andimpact
o Currentsituation mustbe communicated torelevantparts
o Eliminate negative impacts
o Allocate resources tosolve problems
o Identifythe rootcausesof problems
Elements
1. Recordof problems
o Clearand concise description, whoidentified anddate,impact, priority(high,medium,
low), date,owner(managinguntil closing), status(open, assigned, resolved, canceled),needed
actionto solve, responsibleforaction, actioncompletion date (estimated oractual) andresult
2. Managementof problems
o Problemmustbe trackedand managed tobe resolved, ornoactiontaken
o Regularreview ensures visibilityandfocus onproblems
o Escalate if there isno solutionin reasonabletime
3. Metrics
o Measure and reportthe problem(forsituationand priority, time between identification
and resolution)
Usage Considerations
0. Advantages
o Organizedmethod fortrackingandresolutionof risks,issuesand defects
o Mechanismforreportingproblems tothe team
o Helpskeepthe focuson openissues, keepingthe focus until itis solved
1. Disadvantages
o Outdatedandirrelevantlist andirrelevantwhennotprioritized andmanaged
o Leadingmembers unavailable ->slow process
o Secondarymanagement (lowerpriority) if there isany deadline fordelivery of the solution
o RCA can take more time and resourcesthan are available
21. Process Modeling
Purpose
o Understand howwork involvingmultiple departments androlesisplayedinanorganization
Description
o Process describe as multiplepersonsorgroupscooperate overaperiodof time to
performa labor
o Involve anumberof activitieslinked byaflow sequence, repeatable and canhave manyways
to complete
o Startedby an eventinthe fieldof business, actionscanbe takenbya person, rulesorthe
passage of time
o The model is a visual representation thatmayinvolvemanual activities, automatedor
combinationof both, endswhen the objective orgoal of the processiscompleted
Elements
o There are several differentnotations, suchas flow diagramandactivitydiagramof UML,
and BPMN
o Elementsof notation
Activities –Stepsthatmustbe completed
Decisions –bifurcations where the flow…
Events– Outside the scope of the process, actionsor messages
Flow – Direction of the sequence stepbystep of the flow
Paper– Type of personor group
Streaksand pools – Activitiesperformed byarole
Endpoints – Start or end of a process or flow
o Processimprovements
Six Sigma,Lean and otherapproaches
Value streammapping, analysisand statistical control,process simulation,benchmarking and
other
Commonchanges:
Identify andremove activitiesthatdonot addvalue
Reducingthe time required tocompletethe process
Improvingthe interfaces
Reductionoreliminationof bottlenecksand backlogs
Usage Considerations
o Advantages
Comfortof stakeholders withthe basicelements andconceptsbehind the model, are
effectiveinpresentinghowtohandle large numberof scenarios
o Disadvantages
Can become complex if notstructuredcarefully
22. Prototyping
Purpose
o Details of the REQ userinterface, integrateswith REQas use cases, scenarios, dataandbusiness
rules, methodstoidentify,describe andvalidate interface needs
Description
o Functional scope
Horizontal – Surface and comprehensive,withno businesslogic
Vertical – Limitedanddeepslice of functionality
o Use throughoutthe life cycle of the systemdevelopment
Disposable:
Clarify interface requirements, simpletool
Featureswith conflictingviews
Evolutionary/Functional:
From initial requirements tofullyfunctional systemrequires specialized prototypingtools
Elements
1. Preparationforprototyping
o Determine the approach
Disposable x evolutionary+Vertical x Horizonal
o Identifyfunctionalitytobe modeled
2. Prototyping
o Iterative process, initial effortonhigh-level view
o Future iterations mayadddetails
o Report– Listof attributes REQdata, selectioncriteriaandrules foraggregation, until detailed
layout
o Interface (screen device)–Understandingthe full flow of the interface, addeddetailswhen
appropriate
o Storyboard – Paths navigation components,abstraction screenswith directional arrowsinthe
flow
o Graphical representation of the elements
3. Evaluate the prototype
o Verifylogical elementsof the interface x usuaryREQ
o Validate representationneeds(testthe interface)
Usage Considerations
0. Advantages
o User interactionand earlyfeedback
o Discoverand confirmREQ range beyondthe interface
o Demonstrate whatis feasibleorgapswithtechnology
o Inputto designers aboutthe interface needs
1. Disadvantages
o Complex case,ittakes a longtime, requiresknowledge of technology, generatesnot
realisticexpectations inusers
o It may looklike afunctional system,limiting the conceptionof solutionand
developmentidentical tothe prototype
23. Requirements Workshops
Purpose
o Structuredway of capturingREQ, usedtoinvestigate, discover,define,prioritizeandachieve
the closure of the REQ
o Effective wayto deliverpromptly highqualityREQ,promoting trust, mutual understanding
and strongcommunication amongstakeholders,producing deliverablesthatstructure and
guide future analysis
Description
o Eventhighlyproductive andfocused, withthe participation of keystakeholders andsubject
matterexperts, selectedforashortand intense work
Facilitatedbyateam member
Scribe / recorderdocumentsthe elicitedREQandquestions
AN shouldbe the facilitatororscribe, or serve asa participantof the workshop (withcaution, not
to influence/confuse)
o Generate ideasfornew featuresorproducts
o Consensus onanissue or revise REQ
Elements
1. Prepare forthe workshopof REQ
o To clarify stakeholderneeds andpurpose of the workshop
o Identify critical stakeholders toparticipate
o Setagendaand determine the means of documentation
o Schedule sessions andorganize logisticsof the room, seating andequipment
o Sendmaterialsinadvance
o Conductpre-workshop interviews toensure understanding of the purpose of the workshop
o Determine the numberof participants
2. Conductthe workshopof REQ
o Elicit, analyze and documentREQ
o Obtainconsensuson conflictingviews,maintaining focus
o Facilitator
Establish objective andprofessional tone forthe meeting
Presentgoalsandagendaof the meeting
Imposingdiscipline,basicrulesandmanage the meeting
Facilitate decision makingand buildingconsensus, ensuringthatall views wereheard
3. Closingpost-workshopof REQ
o Track openitems of recordedactionsinthe meeting
o Complete anddistributedocumentation tostakeholders
Usage Considerations
0. Advantages
o A wayto elicitdetailedREQina short period of time
o Provides collaborativeenvironmentforstakeholders tomake decisionsand mutual
understanding
o Generallylowercostto conductseveral interviews
o Workingtogethertoachieve consensus
o Immediate feedback,interpretation providedimmediately
1. Disadvantages
o Availability of stakeholders
24. o Successhighlydependenton the skill of the facilitatorand participants’knowledge
o Many participantsmay make the process slow
o Few participantscanignore REQ
25. Requirements Workshops
Purpose
o Structuredway of capturingREQ, usedtoinvestigate, discover,define,prioritizeandachieve
the closure of the REQ
o Effective wayto deliverpromptly highqualityREQ,promoting trust, mutual understanding
and strongcommunication amongstakeholders,producing deliverablesthatstructure and
guide future analysis
Description
o Eventhighlyproductive andfocused, withthe participation of keystakeholders andsubject
matterexperts, selectedforashortand intense work
Facilitatedbyateam member
Scribe / recorderdocumentsthe elicitedREQandquestions
AN shouldbe the facilitatororscribe, or serve asa participantof the workshop (withcaution, not
to influence/confuse)
o Generate ideasfornew featuresorproducts
o Consensus onanissue or revise REQ
Elements
1. Prepare forthe workshopof REQ
o To clarify stakeholderneeds andpurpose of the workshop
o Identify critical stakeholders toparticipate
o Setagendaand determine the means of documentation
o Schedule sessions andorganize logisticsof the room, seating andequipment
o Sendmaterialsinadvance
o Conductpre-workshop interviews toensure understanding of the purpose of the workshop
o Determine the numberof participants
2. Conductthe workshopof REQ
o Elicit, analyze anddocumentREQ
o Obtainconsensuson conflictingviews,maintaining focus
o Facilitator
Establish objective andprofessional tone forthe meeting
Presentgoalsandagendaof the meeting
Imposingdiscipline,basicrulesandmanage the meeting
Facilitate decisionmakingandbuildingconsensus, ensuringthatall views wereheard
3. Closingpost-workshopof REQ
o Track openitems of recordedactionsinthe meeting
o Complete anddistributedocumentation tostakeholders
Usage Considerations
0. Advantages
o A wayto elicitdetailedREQina short period of time
o Provides collaborativeenvironmentforstakeholders tomake decisionsand mutual
understanding
o Generallylowercostto conductseveral interviews
o Workingtogethertoachieve consensus
o Immediate feedback, interpretation provided immediately
1. Disadvantages
o Availability of stakeholders
26. o Successhighlydependenton the skill of the facilitatorand participants’knowledge
o Many participantsmay make the process slow
o Few participantscanignore REQ
27. Root Cause Analysis
Purpose
o Determine the implicityformof a problem
Description
o Structured examination of aspectsof a situation toestablishthe rootcausesand effectsresulting
fromthe problem
o Keyelementtoensure challengethe thoughtof the businessandprocesses
Elements
1. Diagram Fishbone /Ishikawa/Cause andEffect
o Capture the question inabox at the top of the diagram
o Draw linesonthe categoriesof potential causes
o Draw minorlines onthe deepercauses
o Use brainstormingtosearchforcategories andcauses
o Analyze the results (future detail)
o Use brainstormingtofindsolutions
2. Five whys
o Questionandanswerprocess toexplore the nature and cause of a problem, throughrepeated
questions
o Write the problemandask (1x + 4x):
“Why do youthinkthe problemoccurs?”+ “Why?”
o Use singlyoras part of the diagramof Ishikawa
Usage Considerations
0. Advantages
o Provides astructuredmethod toidentify the rootcauses of the identifiedandunderstood
problems
1. Disadvantages
o It worksbetterwhen someone trainedfacilitates the expertsteam, the facilitatormustremain
objective
28. Scenarios and use Cases
Purpose
o Describe how anactor interactswith asolutiontoachieve one ormore goals of the actor, or
respondingto anevent
Description
o Scenariodescribes only one wayinwhich aplayercan reacha targetin particular,through a
seriesof stepsperformed bythe actors
o Use case describes all possible outcomes of anattemptto achieve aparticulargoal
that supports the solution throughvarious scenariosinthe formof primaryflow (basic,simplest)
and alternative (specialsituationsand exceptions)
Elements
1. Name – Unique inside the project, describes the goal oreventwhichhe treatsandincludes a
verb+ noun
2. Actors – A person,system orexternal eventtothe system thatinteractswiththe systemthrough
the use case, unique name that represents the role, shouldneverbe the name of a person
3. Preconditions –Any fact that the solution musttake as true for whenthe use case begins
4. Flowof events – Describeswhatthe actor andthe system are doingwhile runningthe scenario
or use case,primary or alternate
5. Postconditions –Any fact thatmust be true whenthe use case iscomplete
6. Relationships
o Associations –Between actorsanduse cases
o Stereotypes –Between the use cases. ExtensionorInclusion.
Usage Considerations
o Advantages
Good to clarify the scope andprovidingahigh-level understandingof the goals of user
behavior, normal situations, alternativesorexceptions
o Disadvantages
There are manyresources tosupportthe interactionordiscoveryof elements incommon
29. Scope Modeling
Purpose
o Usedto describe the scope of the analysis orscope of the solution
Description
o Serve asthe basisforthe definition anddelimitationof the scope of workof the AN and of the
project
o Allowthe definitionof “complete”scope,containing the boundariesof abusinessdomain
Elements
1. ContextDiagram
o DFD high-level, usesaunique dataprocess todescribe the scope andfeatures external
entities anddatastoresthatprovide and receive datafrom SYS
2. Events
o Occur in an external entity,time determinedby businessrules,how toprovide response tothe
event
3. Resources
o High-level abstractions of the solution expandedin functional andadditional requirements
4. Use Case Diagrams
o Usually describes the use cases,actors andrelationships betweenthem
5. BusinessProcess
o High-level model tomodel the scope
Usage Considerations
0. Advantages
o Make iteasierto determinewhichshouldbe insideandoutof the scope toa solution
1. Disadvantages
o Can leave detailstobe investigated further
30. Sequence Diagrams
Purpose
o Model the logicof usage scenarios throughthe presentationof information passed
between objectsinthe system, fromthe execution of the scenario
Description
o Showshow objectsandclasses interactduringone scenario
o Usedto show how the components of the userinterface orsoftware componentsinteract
Key Features
o Presents particularinstancesof eachobject,with alifeline beneatheach object,whenitis
createdand destroyed
o Specifies the orderof events,not the exacttime
o Procedural Flow ->Senderdoesnotact until the returnmessage isreceived
o Asynchronousstream ->Processingcontinuesaftersendingsignal
Usage Considerations
1. Advantages
o Usedin orientedanalysisof objects tovalidate the classdiagramx use case diagram
2. Disadvantages
o Must be definedforeachpossible scenario,requiringafullydefined model of classes
31. State Diagrams
Purpose
o Showshowthe behaviorof a concept, entityorobjectchanges inresponse toevents
Description
o Specifiesthe sequence of statesthatanobjectgoesthrough duringits lifetime and defines
whicheventscause atransitionbetween these states
o State Machine Diagram, State TransitionDiagram, Diagramof Entity Life Cycle
Elements
1. States
o Represents aunique conditionthat anobjectmaybe or the state that he mayhave, can only
be in one state at a time, musthave aninitial state and manyintermediateandfinal states
2. Transitions
o Represents adynamicbehaviorthatmoves anitemfromone state to another,are
triggeredforcompletedactivities, eventsorothersstimulations
Usage Considerations
0. Advantages
o Useful toclarifyconfude orconflictingREQ
1. Disadvantages
o Each state mustbe validatedtodetermineif itisrelevanttothe scope of the solution, careful
not to expandthe scope
32. Survey/Questionnaire
Purpose
o Elicitinformationfrommany people(anonymousornot) in a shortperiodof time,collecting
information aboutcustomers,products,workpractices andattitudes
Description
o Setof writtenquestionstothe stakeholdersand expertsonthe subject, requestinganindication
of the degree of agreement inrelationto aseriesof statements, toanalyze the responses and
distribute toappropriate parties
o Closedquestions –Selectingarange of responsesavailable well understood, easyto
analyze, linkedtonumerical coefficients, quantitative language
o Openquestions –answerfree questions,questionsare known butthe answersare
not known, larger/higherspectrum, qualitative language
Elements
1. Prepare
o Define the purpose of researchand targetgroup
o Identify goalsandgroup tobe searched
o Choose the type of search: Semi-structuredinterview (openquestions) x structured (closed
questions)
o Selectthe sample group:Small interview of all/ Grandsubsetof users
o Geographical distribution, regulatory differences,lackof standardization inoffice orbusiness
processes
o Selectdistributionmethods
o Projectingdesiredlevel of response (% acceptable return)
o Relyingonindividual interviews
Preliminary –Ideal forall surveyquestions
PostResearch– Specificresponses andfuture themes
o Communicate the purpose, goalsandreasonof the search
o Be aware of group characteristics, historical,environment andterminology
o Focuson REQ, the questionsmustbe directedtowardsthe statedobjectives
o Easy search, quick to be answered, limitedandordered
o Clearand concise questions,addressing aspecifictheme
o Avoidnegative,complex anduncomfortable questions
o Testthe search for possible adjustments
2. To send the surveybasedon:
o Organizational policies
o Urgency inobtainingresults
o Securitylevel required
o Geographical distribution of participants
3. To documentsearch results:
o Collectthe responses,evaluate detailsandemergingthemesof openquestions
o Analyze andsummarize the results
o Reportfindings tothe sponsor
Usage Considerations
0. Advantages
o Closedquestions effective forstatistical analysis
o OpenQuestions effectivetobringthe insightsandopinions
33. o It doesn’trequires timeandcangenerate large numberof responses
1. Disadvantages
o Openquestions require highanalysis
o Resultsare notbiased, andquestionsare notanswered
34. SWOT Analysis
Purpose
o Tool to analyze various aspectsof the currentstate of businessprocesses thatare goingthrough
changes
Description
o EnglishacronymforStrengths,Weaknesses,Opportunities andThreats
o Framework forstrategicplanning, opportunityanalysis, competitive analysis,product
developmentandbusiness
Elements
o Stepsto conductthe SWOT analysis
Draw a grid or matrix
Describe the issue orproblemunderdiscussion
Conductbrainstormingsessiontocomplete the sectionsof:
Strengths /Weaknesses /Opportunities /Threats
Facilitate discussion toanalyze the results
Conductsolutionsbrainstorming tosolve the problem
Usage Considerations
1. Advantages
o Assistsanalysisof various aspectsof the currentstate of the ORG andthe environment
2. Disadvantages
o Highlevel view,more detailedanalysisisalmostalwaysneeded
35. User Stories
Purpose
o Brief descriptionsof functionalityneeded forusers inresponsetoa needand businessgoal
Description
o Textaboutthings that the solution mustallow the usertodo
o One or two sentences describingwho usesthe history, the goal tobe achievedandadditional
informationforunderstandingthe history
Key Features
o Short description of the problem fromthe userperspective
Includes actor(benefited),description (highlevel) andbenefit(amountgiven)
Whento Use
1. Advantages
o Create environmentof customerproperty inrelation toresourcesand prioritiesincrementally
and iteratively
2. Disadvantages
o It may notbe accessible in environmentswith regulatoryrestrictions
36. Vendor Assessment
Purpose
o To evaluate the abilityof apotential suppliertoattendcommitments inrelation toaproduct or
service
Description
o For solutions providedby external suppliersoroutsourcedsolution,theremayhave
specificREQinrelationtothe involvement of thirdparties
o Ensure that the supplieris financiallysecure, able tomaintain specificlevelsof personnel,
design skilledemployees tosupportthe solution
o Non-functional REQcan be usedto define level of expectedservice
Elements
o Validation andevaluationof scenarios tomitigate the risksof notattendingthe following
considerations:
1. KnowledgeandExpertise –the supplierhas knowledge andskill not availablein the ORG?The
skill will be transferred?Whatisthe capacityof the suppliertodoit?
2. Licensingandpricingmodels –Case of purchasingoroutsourcingsolutionora
component, determinewhichoptions offerthe bestcost-benefit
3. Reputationand marketposition of the product– How manycustomers are currentlyusing the
productor service?
4. Termsand conditions –The servicesprovided are temporary orpermanent?
5. Experience and reputationof the supplier–Reviewed forconformity andcompliance
to external standards andrelevantquality,safety andprofessionalism
6. Stabilityof supplier–The supplierwill be able to provide the services inthe future?
Usage Considerations
1. Advantages –Reduces riskof relationshipwithinappropriate supplier
2. Disadvantages –High consumptionof time tomultiple suppliers