The document provides an overview of the key steps needed to start a new technology company:
1) Establish a vision, mission, and business goals for the company.
2) Generate product/service ideas and develop initial designs.
3) Determine the necessary resources and timing.
4) Develop marketing, business, and financial strategies.
5) Perform all five steps concurrently rather than sequentially.
Business modelling in the fuzzy front end of innovation camera ready 29june11Sander Limonard
How to inform technological decision making in long term, networked innovation? This presentation proposes a methodology that enables decision makers in networked R&D projects to select, align and enrich strategy formation, business model identification and technology design.
Business modelling in the fuzzy front end of innovation camera ready 29june11Sander Limonard
How to inform technological decision making in long term, networked innovation? This presentation proposes a methodology that enables decision makers in networked R&D projects to select, align and enrich strategy formation, business model identification and technology design.
INTELLIGENT DISK SUBSYSTEMS – 2, I/O TECHNIQUES – 1
Caching: Acceleration of Hard Disk Access; Intelligent disk subsystems; Availability of disk subsystems. The Physical I/O path from the CPU to the Storage System; SCSI.
I/O TECHNIQUES – 2, NETWORK ATTACHED STORAGE
Fibre Channel Protocol Stack; Fibre Channel SAN; IP Storage. The NAS Architecture, The NAS hardware Architecture, The NAS Software Architecture, Network connectivity, NAS as a storage system.
SAN ARCHITECTURE AND HARDWARE DEVICES : Overview, creating a Network for storage; SAN Hardware devices, The fibre channel switch, Host Bus adaptors; Putting the storage in SAN; Fabric operation from a Hardware perspective
FILE SYSTEM AND NAS: Local File Systems; Network file Systems and file servers; Shared Disk file systems; Comparison of fiber Channel and NAS.
STORAGE VIRTUALIZATION: Definition of Storage virtualization; Implementation Considerations; Storage virtualization on Block or file level; Storage virtualization on various levels of the storage Network; Symmetric and Asymmetric storage virtualization in the Network
INTRODUCTION : Server Centric IT Architecture and its Limitations; Storage – Centric IT Architecture and its advantages; Case study: Replacing a server with Storage Networks; The Data Storage and Data Access problem; The Battle for size and access.
INTELLIGENT DISK SUBSYSTEMS – 1
Architecture of Intelligent Disk Subsystems; Hard disks and Internal I/O Channels, JBOD, Storage virtualization using RAID and different RAID levels;
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
CH 10 Part 2.docxFigure 10-2 The layout of a data inpu.docxcravennichole326
CH 10 Part 2.docx
Figure 10-2 The layout of a data input form using a coding sheet
1. Narrative overview
2. Sample design
3. Testing and usability assessment
Figure 10-3A A data input screen designed as a wireframe
Figure 10-3B A data input screen designed in Microsoft’s Visual Basic.NET
The first section of a design specification contains a general overview of the characteristics of the target users, tasks, system, and environmental factors in which the form or report will be used. The purpose is to explain to those who will actually develop the final form why this form exists and how it will be used so that they can make the appropriate implementation decisions. In this section, you list general information and the assumptions that helped shape the design. For example, Figure 10-4 shows an excerpt of a design specification for a Customer Account Status form for Pine Valley Furniture (PVF). The first section of the specification, Figure 10-4a, provides a narrative overview containing the relevant information to developing and using the form within PVF. The overview explains the tasks supported by the form, where and when the form is used, characteristics of the people using the form, the technology delivering the form, and other pertinent information. For example, if the form is delivered on a visual display terminal, this section would describe the capabilities of this device, such as whether it has a touch screen and whether color and a mouse are available.
Figure 10-4 Design specification for the design of forms and reports
In the second section of the specification, Figure 10-4b, a sample design of the form is shown. This design may be hand drawn using a coding sheet, although in most instances it is developed using standard development tools. Using actual development tools allows the design to be more thoroughly tested and assessed. The final section of the specification, Figure 10-4c, provides all testing and usability assessment information. Procedures for assessing designs are described later in this chapter. Some specification information may be irrelevant when designing some forms and reports. For example, the design of a simple Yes/No selection form may be so straightforward that no usability assessment is needed. Also, much of the narrative overview may be unnecessary unless intended to highlight some exception that must be considered during implementation.
Figure 10-5 Contrasting customer information forms (Pine Valley Furniture)
Figure 10-5 (b) Improved design for form
Figure 10-6 Customer account status display using various highlighting techniques (Pine Valley Furniture)
Figure 10-7 Contrasting the display of textual help information
(b) An improved design for a help screen
Figure 10-8 Contrasting the display of tables and lists (Pine Valley Furniture)
Figure 10-8 (b) Improved design for form
Figure 10-9 Tabular report illustrating numerous design guidelines (Pine Valley Furnit ...
The concept generation process begins with a set of customer needs and target specifications and results in a set of product concepts from which the team will make a final selection.
Project Schedule
Name
Institutional Affiliation
Set-up of Microsoft Project
The project that will be set up by the entire team will be the creation of the entire project schedule that will play a pivotal role in the sake of a new product in the market. The project schedule will focus on the CRM implementation, marketing program and training. The name of the project would be the SPM Project Schedule and will be handled by two departments namely the Marketing and the Information Technology departments.
The SPM Project Schedule will be in two parts. One is the sales and training program in which the objectives of the sales training will be determined. In addition, there would be the determination of then various activities that the sales training program will entails including Identifying focus group targets, Preparing focus group objectives, Performing focus group, Performing survey, Performance analysis, Creating market research findings and Review market research findings among other tasks (Norman, Brotherton & Fried, 2008). .
The second part would involve the creation or the preparation of the work breakdown structure given the fact that it is the epitome of the entire project schedule and as such, it musts be prepared to offer direction on how the various tasks and activities in the schedule will be conducted on the time frame that the same will be completed and by who. The work breakdown structure will be the representation of the hierarchical decomposition of the work to be executed by the two project teams. It should be noted that it is a work breakdown structure that will determine the phases of the project schedule (Haugan, 2002). The development of the sales and training program will be by an individual while the work breakdown structure will be developed by the entire project team.
Phases
There will be five crucial phases of the entire project Schedule to address the marketability and salability of the new product which forms the reason for the project scheduling (Dyché, 2001).
new product
market research
product design
product development
marketing
project management
design
bill of
production design
marketing strategy
focus group
research
materials
production testing
marketing plan
surveys
evaluation
initial prototype
production QA
marketing collateral
research analysis
design
prototype testing
design
brochures
market research findings
documentation
production
production
advertising
concept
dev. Sign off
plan sign off
commercials
models
design
selection
Phase 1: Market research
Under phase one of the project schedules, focus will be on finding out what the customers want and how their needs can be satisfied (Robinson, 1959). The market Research phase of the project schedule will have different variables namely survey conduction, research analysis, and market research analysis.
The first variable which is conduction of the survey will aim a ...
From Product Vision to Story Map - Lean / Agile Product shapingJérôme Kehrli
A lot of Software Engineering projects fail for a lack of shared vision due to poor communication among people involved in the project.
A sound maintenance of the product backlog can only be achieved if all the people have a good understanding of what they have to do (common vision).
Roman Pichler, in a post originally written in Jul 16 2012, has proposed a really interesting approach: use various canvas to create and share product vision and product backlog creation and refinement.
This presentation is a drive through these various boards and canvas that should be designed in prior to any product development: the Product Vision, the Lean Canvas, The Product Definition and the Story Map.
INTELLIGENT DISK SUBSYSTEMS – 2, I/O TECHNIQUES – 1
Caching: Acceleration of Hard Disk Access; Intelligent disk subsystems; Availability of disk subsystems. The Physical I/O path from the CPU to the Storage System; SCSI.
I/O TECHNIQUES – 2, NETWORK ATTACHED STORAGE
Fibre Channel Protocol Stack; Fibre Channel SAN; IP Storage. The NAS Architecture, The NAS hardware Architecture, The NAS Software Architecture, Network connectivity, NAS as a storage system.
SAN ARCHITECTURE AND HARDWARE DEVICES : Overview, creating a Network for storage; SAN Hardware devices, The fibre channel switch, Host Bus adaptors; Putting the storage in SAN; Fabric operation from a Hardware perspective
FILE SYSTEM AND NAS: Local File Systems; Network file Systems and file servers; Shared Disk file systems; Comparison of fiber Channel and NAS.
STORAGE VIRTUALIZATION: Definition of Storage virtualization; Implementation Considerations; Storage virtualization on Block or file level; Storage virtualization on various levels of the storage Network; Symmetric and Asymmetric storage virtualization in the Network
INTRODUCTION : Server Centric IT Architecture and its Limitations; Storage – Centric IT Architecture and its advantages; Case study: Replacing a server with Storage Networks; The Data Storage and Data Access problem; The Battle for size and access.
INTELLIGENT DISK SUBSYSTEMS – 1
Architecture of Intelligent Disk Subsystems; Hard disks and Internal I/O Channels, JBOD, Storage virtualization using RAID and different RAID levels;
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
CH 10 Part 2.docxFigure 10-2 The layout of a data inpu.docxcravennichole326
CH 10 Part 2.docx
Figure 10-2 The layout of a data input form using a coding sheet
1. Narrative overview
2. Sample design
3. Testing and usability assessment
Figure 10-3A A data input screen designed as a wireframe
Figure 10-3B A data input screen designed in Microsoft’s Visual Basic.NET
The first section of a design specification contains a general overview of the characteristics of the target users, tasks, system, and environmental factors in which the form or report will be used. The purpose is to explain to those who will actually develop the final form why this form exists and how it will be used so that they can make the appropriate implementation decisions. In this section, you list general information and the assumptions that helped shape the design. For example, Figure 10-4 shows an excerpt of a design specification for a Customer Account Status form for Pine Valley Furniture (PVF). The first section of the specification, Figure 10-4a, provides a narrative overview containing the relevant information to developing and using the form within PVF. The overview explains the tasks supported by the form, where and when the form is used, characteristics of the people using the form, the technology delivering the form, and other pertinent information. For example, if the form is delivered on a visual display terminal, this section would describe the capabilities of this device, such as whether it has a touch screen and whether color and a mouse are available.
Figure 10-4 Design specification for the design of forms and reports
In the second section of the specification, Figure 10-4b, a sample design of the form is shown. This design may be hand drawn using a coding sheet, although in most instances it is developed using standard development tools. Using actual development tools allows the design to be more thoroughly tested and assessed. The final section of the specification, Figure 10-4c, provides all testing and usability assessment information. Procedures for assessing designs are described later in this chapter. Some specification information may be irrelevant when designing some forms and reports. For example, the design of a simple Yes/No selection form may be so straightforward that no usability assessment is needed. Also, much of the narrative overview may be unnecessary unless intended to highlight some exception that must be considered during implementation.
Figure 10-5 Contrasting customer information forms (Pine Valley Furniture)
Figure 10-5 (b) Improved design for form
Figure 10-6 Customer account status display using various highlighting techniques (Pine Valley Furniture)
Figure 10-7 Contrasting the display of textual help information
(b) An improved design for a help screen
Figure 10-8 Contrasting the display of tables and lists (Pine Valley Furniture)
Figure 10-8 (b) Improved design for form
Figure 10-9 Tabular report illustrating numerous design guidelines (Pine Valley Furnit ...
The concept generation process begins with a set of customer needs and target specifications and results in a set of product concepts from which the team will make a final selection.
Project Schedule
Name
Institutional Affiliation
Set-up of Microsoft Project
The project that will be set up by the entire team will be the creation of the entire project schedule that will play a pivotal role in the sake of a new product in the market. The project schedule will focus on the CRM implementation, marketing program and training. The name of the project would be the SPM Project Schedule and will be handled by two departments namely the Marketing and the Information Technology departments.
The SPM Project Schedule will be in two parts. One is the sales and training program in which the objectives of the sales training will be determined. In addition, there would be the determination of then various activities that the sales training program will entails including Identifying focus group targets, Preparing focus group objectives, Performing focus group, Performing survey, Performance analysis, Creating market research findings and Review market research findings among other tasks (Norman, Brotherton & Fried, 2008). .
The second part would involve the creation or the preparation of the work breakdown structure given the fact that it is the epitome of the entire project schedule and as such, it musts be prepared to offer direction on how the various tasks and activities in the schedule will be conducted on the time frame that the same will be completed and by who. The work breakdown structure will be the representation of the hierarchical decomposition of the work to be executed by the two project teams. It should be noted that it is a work breakdown structure that will determine the phases of the project schedule (Haugan, 2002). The development of the sales and training program will be by an individual while the work breakdown structure will be developed by the entire project team.
Phases
There will be five crucial phases of the entire project Schedule to address the marketability and salability of the new product which forms the reason for the project scheduling (Dyché, 2001).
new product
market research
product design
product development
marketing
project management
design
bill of
production design
marketing strategy
focus group
research
materials
production testing
marketing plan
surveys
evaluation
initial prototype
production QA
marketing collateral
research analysis
design
prototype testing
design
brochures
market research findings
documentation
production
production
advertising
concept
dev. Sign off
plan sign off
commercials
models
design
selection
Phase 1: Market research
Under phase one of the project schedules, focus will be on finding out what the customers want and how their needs can be satisfied (Robinson, 1959). The market Research phase of the project schedule will have different variables namely survey conduction, research analysis, and market research analysis.
The first variable which is conduction of the survey will aim a ...
From Product Vision to Story Map - Lean / Agile Product shapingJérôme Kehrli
A lot of Software Engineering projects fail for a lack of shared vision due to poor communication among people involved in the project.
A sound maintenance of the product backlog can only be achieved if all the people have a good understanding of what they have to do (common vision).
Roman Pichler, in a post originally written in Jul 16 2012, has proposed a really interesting approach: use various canvas to create and share product vision and product backlog creation and refinement.
This presentation is a drive through these various boards and canvas that should be designed in prior to any product development: the Product Vision, the Lean Canvas, The Product Definition and the Story Map.
Future proof event on 13 sept 18 - Innovation & IP - by Bagaar & GeversDavid Gillain
The future is digital, there’s no doubt about that. But what does it mean for your business and how can you make sure you get on board?
What makes or breaks an idea and how can you protect it? What is it worth and how can you monetize it? What influence does technology have on your business and how can you benefit from it?
In this presentation, we use the development process of a digital electricity meter as a case to illustrate the importance of Intellectual Property for an innovation project.
INTRODUCTION
In order to stay successful in the face of maturing products, companies need a continuous stream of new ideas successfully developed into new products. The way to obtain new products is to have a structured and carefully executed new product development process (NPD).
But companies face a problem: Although they must develop new products, the odds weigh heavily against success. Among thousands of products entering the process at the top, only a handful eventually reach the market. Therefore, it is of crucial importance to understand consumers, markets, and competitors in order to develop new products that deliver superior value to customers.
In other words, there is no way around a systematic, customer-driven new product development process for finding and growing new products. We will go into the eight major steps in the new product development process.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
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.
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.
Welocme to ViralQR, your best QR code generator.ViralQR
Welcome to ViralQR, your best QR code generator available on the market!
At ViralQR, we design static and dynamic QR codes. Our mission is to make business operations easier and customer engagement more powerful through the use of QR technology. Be it a small-scale business or a huge enterprise, our easy-to-use platform provides multiple choices that can be tailored according to your company's branding and marketing strategies.
Our Vision
We are here to make the process of creating QR codes easy and smooth, thus enhancing customer interaction and making business more fluid. We very strongly believe in the ability of QR codes to change the world for businesses in their interaction with customers and are set on making that technology accessible and usable far and wide.
Our Achievements
Ever since its inception, we have successfully served many clients by offering QR codes in their marketing, service delivery, and collection of feedback across various industries. Our platform has been recognized for its ease of use and amazing features, which helped a business to make QR codes.
Our Services
At ViralQR, here is a comprehensive suite of services that caters to your very needs:
Static QR Codes: Create free static QR codes. These QR codes are able to store significant information such as URLs, vCards, plain text, emails and SMS, Wi-Fi credentials, and Bitcoin addresses.
Dynamic QR codes: These also have all the advanced features but are subscription-based. They can directly link to PDF files, images, micro-landing pages, social accounts, review forms, business pages, and applications. In addition, they can be branded with CTAs, frames, patterns, colors, and logos to enhance your branding.
Pricing and Packages
Additionally, there is a 14-day free offer to ViralQR, which is an exceptional opportunity for new users to take a feel of this platform. One can easily subscribe from there and experience the full dynamic of using QR codes. The subscription plans are not only meant for business; they are priced very flexibly so that literally every business could afford to benefit from our service.
Why choose us?
ViralQR will provide services for marketing, advertising, catering, retail, and the like. The QR codes can be posted on fliers, packaging, merchandise, and banners, as well as to substitute for cash and cards in a restaurant or coffee shop. With QR codes integrated into your business, improve customer engagement and streamline operations.
Comprehensive Analytics
Subscribers of ViralQR receive detailed analytics and tracking tools in light of having a view of the core values of QR code performance. Our analytics dashboard shows aggregate views and unique views, as well as detailed information about each impression, including time, device, browser, and estimated location by city and country.
So, thank you for choosing ViralQR; we have an offer of nothing but the best in terms of QR code services to meet business diversity!
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.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
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/
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.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...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.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4
Ism 80 lecture notes
1. Strting a New Technology Company = Innovation & Entrepreneurship<br />Overview<br />Problem: How does one create a new technology company?<br />Approach/Process: 5 key steps<br />Setup a VISION, a MISSION and Business Goals for the company<br />Like: how much Revenue you hope to make<br />Growth (%)<br />Product Strategy<br />Generate Ideas for products and services<br />Design and develop the product/service<br />Resources needed (people, equipment, space, …)<br />Timing (when?)<br />Market Strategy<br />Market segmentation of the products and potential customers<br />Market sizing ($)<br />Market Mix (the 4 p’s)<br />Product (features,…)<br />Price<br />Promotion (advertising,…)<br />Placement (distribution channels,…)<br />Business Strategy<br />What industry/market combination is your company operating in? (consumer electronics industry, healthcare industry…)<br />Who are tehe major players (or companies) in that industry? <br />What is the competitive strategy of each player?<br />How is your company going to operate in that space?<br />Financial Strategy<br />Cash flows (revenues, costs, profit) for 3-5 years<br />Funding<br />Who will finance the new company? (friends and family, government, venture capital,…)<br />Financial structure (ownership, shares and stock,…)<br />How do you obtain the necessary funding?<br />These Five steps (^^) have to be performed concurrently as opposed to sequentially. <br />Skills To be learned in this course<br />Problem Solving <br />Da Vinci circa 1450s<br />Edison around 1850s<br />How to start a new technology company<br />Tools, Methods within each of the five steps<br />Applications<br />Covered in lectures and homework<br />Mastery of the tools<br />Through the comprehensive midterm and final<br />By creating a startup as part of a team project<br />HW – every other Thursday<br />Team Project Report – every other other thursday<br />Idea Generation: One Popular method for idea Generation is: <br />STRUCTURED BRAINSTROMING<br />Idea Generation<br />Quantity of ideas (not quality) is emphasized<br />No criticism<br />Quantity is more important that quality<br />“wilder the better”<br />one person should act as a facilitator and another person records ideas as they are being generated.<br />Todays Problem: Highway 17 is extremely dangerous, especially when it rains.<br />Generate: 30 – 50 ideas to make highway 17 safer<br />Structure the ideas into 3 groups<br />A: ideas of immediate usefulness (“low-hanging” fruit)<br />B: ideas for further exploration<br />C: radically new approaches<br />Agenda:<br />Review<br />Project teams<br />Project kick-off & hw number 1<br />Problem solving<br />Product/service dissection – (reverse engineering)<br />Project Kick-off<br />2 levels of brainstorming<br />Level 1:<br />Brainstorm on societal/customer/market needs (25-50 needs):<br />i.e. clean drinking water for everyone<br />better transportation<br />alternate fuels….etc.<br />Level 2:<br />reduce to 3-5 for close examination<br />get specific within the ideas/needs<br />specify ideas to solve or satisfy these needs<br />Create a project proposal<br />main body - A prioritized list of 5-7 ideas, with a brief description of each idea (2-3 pages).<br />Include an appendix (larger set of needs and ideas generated with all details of brainstorming activities)<br />Structured problem solving<br />High-level process: <br />Define the real problem<br />Plan the approach (a set of steps)<br />Execute the plan<br />Check your work<br />Learn/Generalize (drawing conclusions)<br />Product/service dissection – (reverse engineering)<br />Comment: The word “product” refers to a spectrum of offereing.<br />Before we can create new products and services, we need to understand how to analyze (or dissect) existing products<br />Step 1: Problem definition<br />What does the product do? (functions)<br />What is the form of the product? (how are the functions realized)<br />Step 2: Plan the approach<br />How does the product work?<br />Define function and form in a more formal fashion<br />Create a structured (organized) diagram that relates the functions to the form<br />Draw conclusions at the end about the product that was dissected.<br />Step 3: Execute the approach<br />Understand how the product works<br />Find a real product and play with it<br />Define function and form<br />Function is a noun-verb combination that indicates the purpose, i.e., what a product does, or what a sub-system does, or what a component does.<br />Agenda:<br />Review<br />Product Dissection<br />HW #1<br />Function Structure<br />Review<br />The importance of having and using a structured problem solving approach<br />There are 5 key steps outlined in the last lecture<br />We applied this method to “product dissection”<br />See handout for details<br />Product dissection<br />The FAST (function analysis system technique)<br />Is a systematic (structured) way of organizing the functions (whys) and the forms (hows) of a product service<br />Key idea: organize the product in a FAST diagram with the whys to the right and the hows to the left<br />Product Dissection<br />Useful hints (for complex products like our hw)<br />Draw a little sketch of the system you are trying to dissect and make a list of the key subsystems and components <br />Work from both ends of the FAST diagram; the process is an ITERATIVE TRIAL and ERROR process<br />The FAST diagram stops when you reach the level of subsystems and components in your list<br />HW PROBLEM NUMBER 1<br />Step 1: define the real problem<br />Assess existing home computers and then develop guidelines or recommendations for improving home computers with respect to each one of these needs<br />What are user (customer) needs?<br />How well do existing computers satisfy these needs?<br />How can we improve?<br />Step 2: Create a plan<br />What are the different types of home computers, and which type am I going to focus on?<br />Assumption: Focus on laptop? (<br />Identify key user needs for the home-computer (key functions, WHYs)<br />Identify the key subsystems of the home computer<br />Create a FAST diagram that relates <br />Assess how well existing home computers satisfy user needs (starting with your own experience, other users, internet research…)<br />Create a table summarizing your assessment and providing guidelines + recommendations for improvement using structured brainstorming<br />Column 1: customer need, performance, UI/experience, reliability, price, etc…<br />Column 2: assessment (use a scale)<br />Column 3: guidelines for improvement<br />Product Design<br />A useful tool in product design is the function structure (FS)<br />Question: Is there a solution-neutral representation (mental model) of existing products or new products that will enable us to create several different realizations of the product.<br />“solution neutral” does not suggest or imply a single solution<br />FS is useful for enetarting several alternative design concepts<br />Came in late….<br />Step 3: Create a morphological matrix, showing alternatives, called solution principles for each sub-function (refer to notebook)<br />Important note: the morphological matrix is constructed, one row (i.e. one sub-function) at a time. NOT one column at a time.<br />Step 4: combine the solution principles (in the morphological matrix) to create alternative design concepts<br />Use experience, logic, discussion, to determine appropriate combinations<br />Design concept 1: existing breathe-right nasal strip<br />It is the combination of a plastic spring strip to open the nasal passages, which attaches to the nose (how stuff works)<br />Step 5<br />Step 6: Select 1-2 feasible alternatives based on the slection criteria for further development<br />Criteria:<br />Performance (effectiveness, etc…)<br />Price attractiveness<br />Safety<br />Project Phase 1: Need high-level criteria to narrow down the list of 5-7 potential ides (from the prelim proposal) to 1 or 2 ideas as a basis for a the startup<br />Criteria:<br />Technical feasibility of the idea. <br />Can it be physically realized in a reasonable amount of time and at a reasonable cost?<br />Commercialization potential of the idea<br />Is there a market for the idea?<br />Construct a 2x2 matrix<br />Agenda<br />Remarks on the morphological matrix<br />Product strategy<br />The resources need to develop the product<br />Expertise: skill sets, tools<br />Infrastructure: space, computing<br />Source: From where? Are we outsourcing?<br />Timing: when?<br />Business (competitive) strategy<br />Problem:<br />How do you characterize the industry/market in which the company (startup) wants to operate<br />What competitive strategy should a company adjust to successfully operate (ie make profit, grow) in that industry / market landscape?<br />Market => customer or buyer for the product<br />Industry => types of market<br />Consumer electronics industry, entertainment industry, health care…<br />Players: competitors, new entrants, substitutes<br />Barriers to entry (of market)<br />Capital<br />Brand<br />Economies of scale<br />Etc…<br />Near term/Long term strategy:<br />Near term for start-up is “focus”<br />Long term: splits into cost effective or differentiated.<br />Step 3: development a business model how to deal with the different sets of players in the the undustry market landscape<br />For each force, F1…, determine the strength (high, medium, low) of the key factors (called determinants) that influence the force see table 1 of the five forces handout <br />START OF LECTURE:<br />Agenda:<br />Complete the five forces business/competitive strategy discussion<br />HW #2<br />HW 2: Problem 2<br />Market and competitive analysis for the digital camera industry<br />Apple the structured problem solving approach<br />Step 1: define the problem<br />Understand and characterize the market (buyers & industry (competitors, suppliers, new entrants…) for digital cameras.<br />Market analysis: 5-step process (lecture #5)<br />Industry analysis: 3-step process (lecture six + handout)<br />In particular, determine:<br />Types of digital camera products – product segmentation<br />Types of digital camera customers (or buyers) – customer segmentation<br />Manufacturers or makers of digital cameras – competitors<br />Market size of the digital camera<br />Step 2: Plan<br />Do some internet-based research to collect the information needed<br />Create a document to collect and organize the information as you go along. (note that you may not obtain exactly the information you are looking for)<br />Chapter 1: Idea<br />It is a substitute for pen and paper<br />How to acquire/contact with a good set of collaborators<br />Be careful about sharing ideas (intellectual capital)<br />Chapter 2: The deal<br />Interaction with the venture capitalists<br />Competition between VC’s benefits the entrepreneur<br />Chapter 3: Creation<br />Resources (people and physical)<br />Planning<br /> <br />