The document discusses using visualization techniques to improve the software development life cycle efficiency by addressing problems with traditional text-based requirements documentation. It identifies that 68% of projects fail or are challenged according to a CHAOS report. The document advocates building visual models and use cases instead of relying solely on text. This helps provide context visually, differentiate current and future states, and improve understanding compared to text-based approaches. Using visualization is argued to reduce requirements defects by 80% and project delivery times by 35% while shortening the requirements cycle by 30%. Leadership is needed to invest in new approaches and resist sticking with the status quo.
This document provides an overview of search and social media optimization. It discusses how SEO has changed with algorithm updates prioritizing content, links and local search. It recommends developing a keyword plan using tools like Google Keyword Planner, Google Trends and competitors' websites. The document also covers setting up Google AdWords accounts and campaigns, including keyword match types and writing effective ads. It concludes by recommending books, blogs and Twitter accounts to follow for additional information.
This document outlines the modules of an SEO course presented by Nguyen Anh Duc from Nakitech Corp. The course covers topics such as how search engines work, on-page and off-page optimization techniques, factors that influence search rankings, SEO tools, measuring SEO ROI, penalties for poor SEO practices, and best practices. The goal of the course is to provide insights into developing SEO strategies to increase website traffic through organic search results.
Bath City College SEO For Beginners Training | February 2017Josh Baldwin
This document provides an agenda and overview for an SEO training session hosted by Noisy Little Monkey. It introduces the trainers and their roles within the company. The agenda includes discussing technical aspects of websites, on-site optimization, off-site factors like links and citations, local and mobile search, and a question and answer period. Key areas that will be covered are speeds and redirects, keywords and content strategy, and acquiring links through events, blogs, and social media. The training aims to explain how Google evaluates websites and what it values in ranking pages highly.
This document discusses the death of traditional product roadmaps and the need for more agile and responsive approaches. It advocates for customer collaboration over contract negotiation, working software over comprehensive documentation, and responding to change over following a rigid plan. The document argues that effective product strategies need visibility into real capacity, responsiveness to select features just in time, space to support learning, and agility to welcome even late changes. It promotes establishing dynamic boards to plan work on demand rather than through pre-set roadmaps and priorities.
This document provides a glimpse into the two largest mobile commerce platforms in Germany and China, Taobao and Zalando. It summarizes some key features of each platform including product details, user comments, style recommendations, and calls to action designed to improve the user experience and increase conversion rates. The goal is to understand how these major players meet user needs through continuous testing and innovation in site design and new features.
The Woodbury University Library website was redesigned in Drupal to make it less static and more collaborative. The old site was becoming outdated and lacked visual elements and opportunities for user interaction. Redesign goals included adding more graphics, new book spotlights, and building an online community. The redesign took 15 months and was done remotely via Skype with a company in Eugene, Oregon. The new Drupal site launched in July 2010 and allowed for more flexible editing and content creation by the whole library staff, despite limitations of a small staff and budget.
This document provides an overview of search and social media optimization. It discusses how SEO has changed with algorithm updates prioritizing content, links and local search. It recommends developing a keyword plan using tools like Google Keyword Planner, Google Trends and competitors' websites. The document also covers setting up Google AdWords accounts and campaigns, including keyword match types and writing effective ads. It concludes by recommending books, blogs and Twitter accounts to follow for additional information.
This document outlines the modules of an SEO course presented by Nguyen Anh Duc from Nakitech Corp. The course covers topics such as how search engines work, on-page and off-page optimization techniques, factors that influence search rankings, SEO tools, measuring SEO ROI, penalties for poor SEO practices, and best practices. The goal of the course is to provide insights into developing SEO strategies to increase website traffic through organic search results.
Bath City College SEO For Beginners Training | February 2017Josh Baldwin
This document provides an agenda and overview for an SEO training session hosted by Noisy Little Monkey. It introduces the trainers and their roles within the company. The agenda includes discussing technical aspects of websites, on-site optimization, off-site factors like links and citations, local and mobile search, and a question and answer period. Key areas that will be covered are speeds and redirects, keywords and content strategy, and acquiring links through events, blogs, and social media. The training aims to explain how Google evaluates websites and what it values in ranking pages highly.
This document discusses the death of traditional product roadmaps and the need for more agile and responsive approaches. It advocates for customer collaboration over contract negotiation, working software over comprehensive documentation, and responding to change over following a rigid plan. The document argues that effective product strategies need visibility into real capacity, responsiveness to select features just in time, space to support learning, and agility to welcome even late changes. It promotes establishing dynamic boards to plan work on demand rather than through pre-set roadmaps and priorities.
This document provides a glimpse into the two largest mobile commerce platforms in Germany and China, Taobao and Zalando. It summarizes some key features of each platform including product details, user comments, style recommendations, and calls to action designed to improve the user experience and increase conversion rates. The goal is to understand how these major players meet user needs through continuous testing and innovation in site design and new features.
The Woodbury University Library website was redesigned in Drupal to make it less static and more collaborative. The old site was becoming outdated and lacked visual elements and opportunities for user interaction. Redesign goals included adding more graphics, new book spotlights, and building an online community. The redesign took 15 months and was done remotely via Skype with a company in Eugene, Oregon. The new Drupal site launched in July 2010 and allowed for more flexible editing and content creation by the whole library staff, despite limitations of a small staff and budget.
The document outlines a user-centered design process for creating websites that blend aesthetics and usability. It involves analyzing business and user objectives, organizing content and information architecture, designing visual and communication elements, and tying everything together in development and deployment while ensuring the design fulfills its intended purpose. The key is to focus on usability over aesthetics alone and validate design decisions through user research and testing.
Are you ready to fire your current business website because it isn’t performing the way you think it should? Or, maybe you just want to see if you can get more out of it (better return on investment). Even if you don’t have a website yet, this workshop is for you!
In this workshop for small business owners, we will cover important elements every website needs to be powerful. We will also discuss how to avoid the common pitfalls and how to correct them if you have fallen into them. There will be many examples and everyone should be able to leave with actionable items they can put to work right away!
This interactive workshop will include worksheets, some fun, and lots of time for Q&A. Bring your pen and a willingness to learn!
Everything You Always Wanted to Know About Content StrategyEthan Machado
The document provides an overview of content strategy from multiple perspectives:
- It discusses content strategy as understanding user and brand needs, and taking a clinical approach to organizing content.
- Content strategists are described as masters of organization, empathy, and rhetoric who use user research and testing.
- An audit process is outlined as inventorying a site, reviewing against standards, and providing recommendations.
- The relationship between content strategy and other disciplines like design, development and marketing is explored.
In-House Content Strategy - MinneWebCon April 2013m3ggiesue
Your organization's content needs help, and it's your job to fix it. But where do you begin? Change from within can be daunting. It may seem like the problems are too big for one person, or one team, to fix. Luckily, you can start to make a meaningful impact with just a few small changes.
This session will offer tips and tools for creating a content strategy from within your organization. You'll get a handful of easy-to-implement, start-today tactics, as well as insight into effecting meaningful longterm change.
Are you ready to fire your current business website because it’s not performing the way you think it should? Or, maybe you just want to see if you can get more out of it (better return on investment). Even if you don’t have a website yet, this workshop is for you!
In this workshop for small business owners, we will cover important elements every website needs to be powerful. We will also discuss how to avoid the common pitfalls and how to correct them if you have fallen into them. There will be many examples and everyone should be able to leave with actionable items they can put to work right away!
- The document provides an overview of designing a business website using WordPress, covering topics like understanding your brand, the design process, and digitally marketing your site.
- It introduces WordPress and discusses themes, plugins, and basic functionality. Tips are provided for defining your brand, audience, and goals for the site.
- The design process section covers picking a theme template and provides examples for non-profits and e-commerce sites. Methods for digital marketing like email, social media, and search engine optimization are also outlined.
The document discusses responsive design and some of its challenges. It notes that while responsive design aims to apply different styles based on screen size, screen size is really just a proxy for context. It argues that responsive design cannot fully account for factors like bandwidth, purpose, and context. The document concludes that responsive design is limited because CSS was not designed to make complex decisions based on non-visual factors, and a better approach is to focus on information architecture rather than trying to shoehorn everything into CSS.
StartupWeekend organizer Marsh Sutherland's formula to win StartupWeekend events. From Friday night pitches to secure your team with an emotional connection to your idea to crafting a final Sunday pitch to win the hearts and minds of the judges. Check it out!
The document summarizes the key aspects and goals of conducting a collaborative content audit. It discusses why audits are important for meeting organizational needs, improving user experience, and managing resources effectively. The audit process involves both quantitative and qualitative evaluation of current content through inventorying, analytics, and discussions with stakeholders. The goals are to clean up content, improve findability, determine what users engage with, and justify expenses. Conducting the audit is a collaborative process that helps align content with goals and users through consensus building.
Why Design Matters More Than Ever. Vivian Selbo's Media Next presentation 10/...Selbov
Responsive to what, when, where, and to whom? This talk walks through the Slate redesign goals outlining the point of view of all the stakeholders: editorial, business, engineering, and design. What they wanted and what they got.
Media Mosaic is an end-to-end digital marketing solutions provider that specializes in search engine optimization (SEO). They have expertise in contextual marketing and analytics. The company aims to bring global best practices to clients through strategic SEO, content creation, and technical optimization of websites. Key factors for SEO success discussed in the document include website architecture, accessibility, relevant and optimized content, backlinks, and ongoing changes to search engine algorithms. The document emphasizes that SEO requires a long-term commitment to see meaningful results.
The document provides an overview of an SEO seminar for the San Francisco Chamber of Commerce. It discusses what SEO is, the history of Google search algorithms, common lies and bad SEO practices to avoid, when to consider SEO for a website, and how to do basic SEO yourself. The seminar covers topics like keyword research, code optimization, and focusing on providing exceptional content for users rather than manipulative practices.
This document discusses best practices for building effective websites. It begins by outlining the main steps in building a website: planning, design, development, testing, and deployment. It emphasizes understanding why the site is being built and who the target audience is before starting. Key aspects to focus on include usability, accessibility, and knowing competitors. The document then provides tips for arranging information intuitively through keywords, content structure, and home page design. It stresses writing content tailored to the audience that is scannable, original, consistent, and engages the reader. Finally, it lists the top ten mistakes in web design to avoid, such as non-scannable text and violating design conventions.
OPA South Africa Workshops on Online Industry In SA Ben Wagner - Head of Crea...Theresa
Pushing creative boundaries in onlinbe advertising
Does creativity make a difference?
Does creativity need discipline?
OPA’s latest best practice guide to online advertising
Where does SA feature creatively?
The Good, The Bad, The Ugly
Inbound School Marketing: Is Your Website Helping The Bottom Line?Kyle James
The rules of the game have changed. Having a website is standard practice but your website is more than a branding piece for your institution. The majority of almost every school’s annual budget comes from tuition so helping increase enrollment has to be the site's top priority. Are you fully leveraging it for a marketing purpose? How is your social media, blogging, mobile efforts and search engine optimization coming together to help you meet these goals? In this presentation, you'll get a blue print for success. We will discuss the importance of your website in the marketing and recruitment funnel, how you can actually get a ROI on marketing and give you formulas and calculators to financially justify future projects.
http://2012.highedweb.org/EventDetail.aspx?guid=7ef9df82-b884-43ae-b5bd-b11066cb0ad4
A comprehensive overview to help small business owners plan their web design project. Download the companion workbook here: https://roundpeg.biz/2017/11/website-workout-plan/
Web Design & Development Trends PresentationRichard Bowden
The document discusses a user centered approach to website design. It covers principles of usability, usefulness and accessibility in web design. It emphasizes involving users throughout the design process to understand their needs and goals. This includes tools like storyboarding, persona analysis and wireframes. An agile development approach is recommended to allow flexibility in adapting the design based on user research and feedback. The document also briefly touches on open versus proprietary technologies.
The document outlines steps for designing a UX career, including setting goals, building a portfolio even without experience, branding yourself online, finding jobs, and preparing for interviews. The speaker encourages daily sketching, weekly community participation and study, and monthly reflection on goals. The key advice is to continuously learn, care about users, and use every opportunity to gain experience on the path to becoming a successful UX designer.
Things to Budget for When Planning a Drupal ImplementationDani Nordin
This presentation, done for the Drupal Business Summit in 2012, covers factors that must be considered when planning Drupal implementations of medium to high complexity.
The document outlines a user-centered design process for creating websites that blend aesthetics and usability. It involves analyzing business and user objectives, organizing content and information architecture, designing visual and communication elements, and tying everything together in development and deployment while ensuring the design fulfills its intended purpose. The key is to focus on usability over aesthetics alone and validate design decisions through user research and testing.
Are you ready to fire your current business website because it isn’t performing the way you think it should? Or, maybe you just want to see if you can get more out of it (better return on investment). Even if you don’t have a website yet, this workshop is for you!
In this workshop for small business owners, we will cover important elements every website needs to be powerful. We will also discuss how to avoid the common pitfalls and how to correct them if you have fallen into them. There will be many examples and everyone should be able to leave with actionable items they can put to work right away!
This interactive workshop will include worksheets, some fun, and lots of time for Q&A. Bring your pen and a willingness to learn!
Everything You Always Wanted to Know About Content StrategyEthan Machado
The document provides an overview of content strategy from multiple perspectives:
- It discusses content strategy as understanding user and brand needs, and taking a clinical approach to organizing content.
- Content strategists are described as masters of organization, empathy, and rhetoric who use user research and testing.
- An audit process is outlined as inventorying a site, reviewing against standards, and providing recommendations.
- The relationship between content strategy and other disciplines like design, development and marketing is explored.
In-House Content Strategy - MinneWebCon April 2013m3ggiesue
Your organization's content needs help, and it's your job to fix it. But where do you begin? Change from within can be daunting. It may seem like the problems are too big for one person, or one team, to fix. Luckily, you can start to make a meaningful impact with just a few small changes.
This session will offer tips and tools for creating a content strategy from within your organization. You'll get a handful of easy-to-implement, start-today tactics, as well as insight into effecting meaningful longterm change.
Are you ready to fire your current business website because it’s not performing the way you think it should? Or, maybe you just want to see if you can get more out of it (better return on investment). Even if you don’t have a website yet, this workshop is for you!
In this workshop for small business owners, we will cover important elements every website needs to be powerful. We will also discuss how to avoid the common pitfalls and how to correct them if you have fallen into them. There will be many examples and everyone should be able to leave with actionable items they can put to work right away!
- The document provides an overview of designing a business website using WordPress, covering topics like understanding your brand, the design process, and digitally marketing your site.
- It introduces WordPress and discusses themes, plugins, and basic functionality. Tips are provided for defining your brand, audience, and goals for the site.
- The design process section covers picking a theme template and provides examples for non-profits and e-commerce sites. Methods for digital marketing like email, social media, and search engine optimization are also outlined.
The document discusses responsive design and some of its challenges. It notes that while responsive design aims to apply different styles based on screen size, screen size is really just a proxy for context. It argues that responsive design cannot fully account for factors like bandwidth, purpose, and context. The document concludes that responsive design is limited because CSS was not designed to make complex decisions based on non-visual factors, and a better approach is to focus on information architecture rather than trying to shoehorn everything into CSS.
StartupWeekend organizer Marsh Sutherland's formula to win StartupWeekend events. From Friday night pitches to secure your team with an emotional connection to your idea to crafting a final Sunday pitch to win the hearts and minds of the judges. Check it out!
The document summarizes the key aspects and goals of conducting a collaborative content audit. It discusses why audits are important for meeting organizational needs, improving user experience, and managing resources effectively. The audit process involves both quantitative and qualitative evaluation of current content through inventorying, analytics, and discussions with stakeholders. The goals are to clean up content, improve findability, determine what users engage with, and justify expenses. Conducting the audit is a collaborative process that helps align content with goals and users through consensus building.
Why Design Matters More Than Ever. Vivian Selbo's Media Next presentation 10/...Selbov
Responsive to what, when, where, and to whom? This talk walks through the Slate redesign goals outlining the point of view of all the stakeholders: editorial, business, engineering, and design. What they wanted and what they got.
Media Mosaic is an end-to-end digital marketing solutions provider that specializes in search engine optimization (SEO). They have expertise in contextual marketing and analytics. The company aims to bring global best practices to clients through strategic SEO, content creation, and technical optimization of websites. Key factors for SEO success discussed in the document include website architecture, accessibility, relevant and optimized content, backlinks, and ongoing changes to search engine algorithms. The document emphasizes that SEO requires a long-term commitment to see meaningful results.
The document provides an overview of an SEO seminar for the San Francisco Chamber of Commerce. It discusses what SEO is, the history of Google search algorithms, common lies and bad SEO practices to avoid, when to consider SEO for a website, and how to do basic SEO yourself. The seminar covers topics like keyword research, code optimization, and focusing on providing exceptional content for users rather than manipulative practices.
This document discusses best practices for building effective websites. It begins by outlining the main steps in building a website: planning, design, development, testing, and deployment. It emphasizes understanding why the site is being built and who the target audience is before starting. Key aspects to focus on include usability, accessibility, and knowing competitors. The document then provides tips for arranging information intuitively through keywords, content structure, and home page design. It stresses writing content tailored to the audience that is scannable, original, consistent, and engages the reader. Finally, it lists the top ten mistakes in web design to avoid, such as non-scannable text and violating design conventions.
OPA South Africa Workshops on Online Industry In SA Ben Wagner - Head of Crea...Theresa
Pushing creative boundaries in onlinbe advertising
Does creativity make a difference?
Does creativity need discipline?
OPA’s latest best practice guide to online advertising
Where does SA feature creatively?
The Good, The Bad, The Ugly
Inbound School Marketing: Is Your Website Helping The Bottom Line?Kyle James
The rules of the game have changed. Having a website is standard practice but your website is more than a branding piece for your institution. The majority of almost every school’s annual budget comes from tuition so helping increase enrollment has to be the site's top priority. Are you fully leveraging it for a marketing purpose? How is your social media, blogging, mobile efforts and search engine optimization coming together to help you meet these goals? In this presentation, you'll get a blue print for success. We will discuss the importance of your website in the marketing and recruitment funnel, how you can actually get a ROI on marketing and give you formulas and calculators to financially justify future projects.
http://2012.highedweb.org/EventDetail.aspx?guid=7ef9df82-b884-43ae-b5bd-b11066cb0ad4
A comprehensive overview to help small business owners plan their web design project. Download the companion workbook here: https://roundpeg.biz/2017/11/website-workout-plan/
Web Design & Development Trends PresentationRichard Bowden
The document discusses a user centered approach to website design. It covers principles of usability, usefulness and accessibility in web design. It emphasizes involving users throughout the design process to understand their needs and goals. This includes tools like storyboarding, persona analysis and wireframes. An agile development approach is recommended to allow flexibility in adapting the design based on user research and feedback. The document also briefly touches on open versus proprietary technologies.
The document outlines steps for designing a UX career, including setting goals, building a portfolio even without experience, branding yourself online, finding jobs, and preparing for interviews. The speaker encourages daily sketching, weekly community participation and study, and monthly reflection on goals. The key advice is to continuously learn, care about users, and use every opportunity to gain experience on the path to becoming a successful UX designer.
Things to Budget for When Planning a Drupal ImplementationDani Nordin
This presentation, done for the Drupal Business Summit in 2012, covers factors that must be considered when planning Drupal implementations of medium to high complexity.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3Data Hops
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
2. What I Will Cover
• Identify a Problem
• Considered How We
Communicate
• Consider Text Based
Approaches
• A Vision for a Better Way
Through Visualization
3. Identifying the
Problem
• Standish Group CHAOS
Report, 2009
• 68% of all projects fail
• 44% were challenged
• 24% cancelled prior to
completion
18. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
Text Based Requirements
30.
31. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
Text Based Requirements
Iterative Walk-Throughs
(SME, Development, Q/A)
32. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
Text Based Requirements
Iterative Walk-Throughs
(SME, Development, Q/A)
33.
34.
35.
36.
37. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
Text Based Requirements
Iterative Walk-Throughs
(SME, Development, Q/A)
38. Subject Matter Expert
Architect
Visual Starting Point
Visual Use Case
Hot Spots and Navigation Links
Text Based Requirements
Iterative Walk-Throughs
(SME, Development, Q/A)
39.
40.
41.
42.
43. Why Is This Better?
• Building Context in the Mind’s
Eye
44. Why Is This Better?
• Building Context in the Mind’s
Eye
• Visual Model
45. Why Is This Better?
• Building Context in the Mind’s
Eye
• Visual Model
• To-Be Differentiated from As-
Is
46. Why Is This Better?
• Building Context in the Mind’s
Eye
• Visual Model
• To-Be Differentiated from As-
Is
• Think Properly With Use
Cases
47. Why Is This Better?
• Building Context in the Mind’s
Eye
• Visual Model
• To-Be Differentiated from As-
Is
• Think Properly With Use
Cases
• Text Based BE GONE!!!!!
48. Why Is This Better?
• Building Context in the Mind’s
Eye
• Visual Model
• To-Be Differentiated from As-
Is
• Think Properly With Use
Cases
• Text Based BE GONE!!!!!
49. Which Is Better?
• 68% of all projects fail • Requirements cycle is reduce
d by at least 30%.
• 44% were challenged
• Requirements defects are
reduced by at least 80%.
• 24% cancelled prior to
completion
• Project delivery times are
35% faster
OR?
50. Need For Leadership
• No One Likes Change
• People Naturally Resist
Change
• Are your Requirements
Valuable?
• Are we Producing Items For
No One that Cares?
• Invest Where it Matters
51. What Have We
Covered?
• Identified a Problem
• Considered How We
Communicate
• Threw Out Text Based
Approaches
• Gave a Vision for a Better Way
Through Visualization
My name is Greg Garner. I have my PMP, have worked in a .net development lead position and currently am working as a Business Analyst in a web-based Healthcare company.\n\nMy perspective is a bit different than most in that I’ve owned my own business’ for years and thus approach problems from an owner’s-mindset.\n\nThank you for allowing me to talk to you today.\n\nNEXT SLIDE\n
Back in the 80’s I was enamored by System Analysis and Design. It mainly consisted of data flow diagrams and the web was barely beginning to emerge. That was the first time I saw the power of connected logic in a visual medium.\n\nSince that time I’ve been involved in countless projects and companies that have produced tons and tons of text and boring documents all in the hopes of capturing all the details for our poor over-burdened developers to create something off of.\n\nNow I’m tired of that rat-race and so today I want to revisit what we all know about failed projects, and approach the problem from a simple common-sense - “what works for me in everything else I do” way.\n\nI want to compare that with the text based approach that most software projects are strapped with and then show how I’ve implemented a simple methodology to do it better.\n\nIt is my hope that you’ll find some simple concepts here that can radically change the way you gather requirements for software so that it all falls in place as it did for me with these concepts, on my projects.\n\nIf you remember just one thing as you leave here today remember that the future is about visualization and not text-based requirements.\n
According to the Standish Group Most Software Projects Fail.\n\nProduct doesn’t get what they envisioned\n\nPMs & Analysts create documents that are rarely used\n\nAnd we get something like what you see here - a haphazard mishmash of a product.\n
Developers can’t develop because of ambiguity in requirements\n\n& Users don’t use the technology – it misses the mark for them\n\nSome other pain points in requirements development are:\n•That No one has time to read text-based requirements – and hardly anyone really does.\n•Also, What is required is not immediately evident – you have to read everything and then go back to the author to get the picture before making the requirements even partially useable for your development process. - I don’t know how many times I have developers take my functional requirements, cursorily look over them, verbally approve them and then start talking to everyone else to figure out what they need to know to begin coding.\nHow many times have you got a word doc where you have to put your finger on a use case on page 5 and then flip to page 25 to see the user interface and at the same time get your finger on page 15 to see the requirements that support that use case - it’s just crazy and not really in this century anymore to have to fool with paper documents.\n\n\n\n
What we want may be clearly stated in these documents, but what ends up getting developed comes out in a way that misses the mark. How could that be with so much detail?\n•IT IS BECAUSE, Business Users Don’t know what they want until they see and interact with it. This typically only happens during QA or user acceptance testing when it’s far too late and far too expensive to make any difference at all.\n•Developers tend to ignore carefully developed requirements documents and do their own analysis. How can an analyst become indispensable to the developer versus just being another bureaucracy that developers have to navigate around to get to discrete programming of functionality?\n If we want a different outcome then we need to change the approach. We need to change the way we communicate requirements from the business to the development community.\n\n\n
So I asked myself the simple question, \nWhat is the best way to communicate anything? How do I learn best?\n•My Premise is that the more we go from a static representation to a dynamic representation the more we will end up in reality.\n•We see this in the maturity of communication mediums as shown here. From the dark ages where we had criers in the street, to written words, to radio, to TV, to digital, now to virtual reality. \n•We all live in real-time, so why not model in real-time?\n\n\n\n
•We all interact with people through our 5 senses – with touch, sound, taste, smell, and sight. With software we essentially only have sight and maybe a little bit of sound to work with for the most part. So if sight is the main interactive medium I want to capitalize on what communicates to someone in the fastest way using this medium.\n•So what do I have at my disposal to work with in the visual medium? \noWell of course se have Text\noVery few use Color\noThere’s Pictures\noVideo\noand what I call Spatial connection – 3d, seeing what connects to other things in space\n\n\n
•I would suggest that text based communication is the least useful medium for communicating. It is also the last medium learned by the human child for communicating visually. \n•On the other hand spatial connection is the most useful medium for communicating to human how a system is connected. Video, pictures, & color are some of the first things human children experience and understand, even before understanding anything verbally.\n•They say A picture is worth a thousand words – So I say, communicate visually throughout all parts of the business, and make the development process fun, fast, and financially more cost effective.\n\nStory: PICTURE WORTH A 1000 WORDS: If asked to describe what a person looks like in writing one would have to write a book describing the color of their skin, the length of their hair, how tall they are, etc. This process is expensive and you only get that boring book at the end of it. \n\n\n
Alternatively one could simply show a picture of the individual and the picture is self describing. After showing a picture one may only need to give a few clarifying details like Height and Weight to be discrete in their requirements, and that’s it.\n\nSo we know that we need to change our approach, and we know that we aren’t communicating optimally with a text-based approach.\n\n
♣What are text based, in software development requirements?\n•It is fast becoming known that lists of disparate, non-connected requirements, even if grouped logically, are not the best medium for communicating requirements.\n•Use cases are great in that they visually show actors and goals. However, they break down to the lowest level of communication medium when one goes into the textual based steps of the use case.\nEveryone loves a use case diagram and most people groan at a use case text blob. When reading the typical unspoken word is, “just freaking show me the thing.”\n
So I’m proposing A BETTER WAY - I want to create requirements real people will use and do away with all the other stuff that doesn’t add real value.\n\nWhat I’m going to do now is illustrate some of the concepts of how I build requirements in a visual manner. Throughout this walk-through I will continue to build a process flow as shown above.\n\nSo First, one should meet with “ONE” primary stakeholder who can best describe the vision, direction, visualization, and system goals in the most complete efficient manner. This really goes against the concept of confusing chaotic JAD sessions with multiple stakeholders. \n\nJAD sessions are typically led by PMs wearing the hat of a BSA. It feels more like a church business meeting than a useful requirements session. The outcome of these sessions is a whole list of ambiguous requirements. The JAD approach is mostly a left-­‐brain exercise. That is not  a bad\nthing of course, but when people talkabout their needs, they visualize it in their mind’s eye. Because everyone visualizes things differently, ambiguity and misunderstanding is introduced. It is long understood in education that people learn more effectively when both the left and right brain are engaged.\n\nLeaders provide order out of chaos - meeting with one person and getting a draft model put together can cut out a ton of confusion.\n\n
\nFrom this meeting I go to the next step. \n \nI want to place some Caution here that one should be sure to run everything by verbally with your system development architect, up front, before wasting time building something that is not supportable.\n
I then Start with the most visual element of the Project in mind - say a Website Landing Page. From this I will build context for the functionality. Building Context is a key part of this methodology. \n♣Every system - business or functional is either UI driven or can be illustrated with a visual process of some type.\n♣Probably 90% or more of software development projects revolve around or involve a user interface. So start on the screen where the user will interact with the system for the functionality you are going to build.\n♣If you are dealing with the 10% of software development that doesn’t involve a UI, then use the UML Actor and Use Case Goal visual depictions to create your visual starting point.\n\n
Keeping my starting point in mind, I want to build my visual use case. So I start doing that with a traditional UML diagram.\n\nIn this particular case I am showing my high level business use case at the top “Provide a Program” and an extend business use case “Provide a Challenge”. Off of that use case I have 3 system use cases that make up the Challenge - One can Join the Challenge, Interact with the challenge and configure the challenge.\n\n\n
From this model one can hyperlink to the next page using the link at the right where all the lines are pointing to.\n\nNote that hyperlinking from a hotspot is another key concept to this methodology.\n
So far I’ve met with one SME to get the main concept, run it by my architect, and then found my visual starting point.\n\nI am now going to deviate from typical UML Diagramming to show my Visual Use Case structure.\n
From the prior UML diagram you’ll recall seeing on the left side of this screen the 3 system uses cases of Join, Interact and Configuring the Challenge.\n\nThose 3 system use cases are now stacked top to bottom on the left, and here I have portioned off my visual Basic Path in the center and Alternate Path Realization Use Cases to the right.\n\nSo this is essentially a visual use case. I have a basic path and several alternate paths.\n \nIt is within these hyperlinked use cases that we will show the visual story board that takes users from screen to screen or activity flow to activity flow using hotspot hyperlinking.\n\nFrom here We are going into the Top Basic Path realization use case for “Join the Challenge” in the center swimlane as pointed to by the black arrow. This will realize my visual starting point for this Basic path.\n\n
So I’ve met with one SME to get the main concept, run it by my architect, then found my visual starting point and have now structured my visual use case.\n\nIn my process I am moving from beginning to build a visual use case to framing in the hyperlinked hotspots that give my wireframes a sense of prototype for the purpose of building context for navigation.\n
Immediately we are dropped into mockups that are familiar, visual, and in context with each other.\n\nNote that I am only building the amount of mockup needed to communicate functionality.\n•So now Working with my business definition folks, I now define as much detail as they know they want – ie. drop down boxes versus radio buttons, placement, coloring, etc. \nI always make a point to let my users know that whatever I mockup is only suggestive for design and not meant to dictate design. IT is meant to dictate functionality.\n•In this case I am focusing on changes to the left and right navigation primarily as shown by the black arrows.\n\n
It is interesting to note here several things:\n Any requirements that are needed beyond what is self-evident in the visual is placed on the mockup with its corresponding screen. As seen here requirement 8054 talked about overall branding needs and was most appropriately placed in my mind at the landing page in the basic path of my visual use case.\n I made a requirement here because the details of branding are not self evident in my visual.\n
In the top left we have a “back button” navigation to return the user back to the prior screen.\n \n While such a no-brainer simple concept, This maintains context with the visual use case and with the system navigation.\n It is these simple ideas of using click through hot spot navigation to prototype functional mockups that takes us away from that crazy activity of having to keep our fingers on 3 pages of a 100 page word doc to figure out what is required to build.\n
On this page, Links that take the user to the functionality that I want to focus on in the basic path are provided as shown here with the black arrow. So from a use case perspective we have\n the system shows the landing page, as the first step\n User clicks on the “Join the Challenge” link in the right hand navigation, as the next step\n System shows the Challenge page, next\n Finally, User clicks the “Join Now” button, which would take them to another page.\n We don’t need to dictate this to a text based use case. It has all the elements that we want from a use case. The only difference is that we marry the actual visual experience with the steps of the user and the system.\n \n ISN’T THIS BETTER?????\n
There are also links – like the center one in the right that can show configuration system user interface details for this screen.\n So if I click on that link - or you could call it an extension path - then I will see that configuration screen in my configuration system UI.\n
See how this provides so much more in-depth information than one would get in a typical use case text line.\n Now if we use the provided back navigation to go back.\n
We can see Other useful definition items that can be shown as seen through the left link as follows:\n\n
Here I placed a table that helps describe the left navgiation links depending on the state that the user is in at the time.\n\nAs mentioned – the real power here is in the identification of the hotspots that pertain to the case you are in and building in click-through functionality – this creates the pseudo-prototype.\n\nSo let’s traverse back up through the navigation hotspots to get back to where we started.\n \n\n
We’ll hit the back button here.\n
So from here we had gone down the Basic Path for “Join the Challenge” using the center swimlane. \n\nAs you envision alternate use paths that are not self-evident in the basic path - go ahead and visually build them with their starting points here in the right swim-lane.\n\nIn this case we would build them out in the same fashion of the basic path but use the right hand swimlane alternate path hotspot visual points - you see 5 of them here.\n\nOne thing to note on this screen is the functional requirement 7957 which was declined and is obviously declined in its status since it is in a Red color.\n\nAnother item I want to point out is that if I have functional requirements attached to screens in the basic path that could be repeated in alternate paths, I choose to only put those items in the basic path - this clears up a lot of clutter and keeps the detail on the basic path. Alternate paths show the concept of the alternate and I don’t need to repeat the details on those paths that I showed on the basic path.\n\nNow Since I have built a visual use case, why waste any time building a text-based use case? If you show all the steps in a visual process – why duplicate the wheel to do it again in a text based use case just to check the box to say you did it - it creates no value add for anyone? Alternatively why create activity flows if you have this visual use case - it is just redundant. Now If QA says they need the word doc - then encourage them to visualize and create their test cases from your visuals. They shouldn’t be using your text based use cases as crutches anyways for their process, right?\n\nFor whether or not I should add additional modeling - ie. text based use cases or activity flow in the case of my user interface experience modeling - I ask myself the question, “Does what I have modeled so far communicate what is needed for my audience?” If I have shown all the visual paths then why waste time on a text based use case – does it add value to communicate requirements more than what I’ve already modeled? If not, don’t do it. The goal is to do the least amount of communication and modeling required to completely communicate the requirements and the intended functionality both upstream to the business and downstream to development. REMEMBER - A PICTURE IS WORTH A THOUSANDS WORDS.\n\n
So far I’ve met with one SME to get the main concept, run it by my architect, then found my visual starting point and have now structured my visual use case. Along the way I’ve added hotspots and navigation links and visuals such as screens, excel tables, and links to other configuration systems to build context.\n\nAs you may have already noticed in the building of the visual use case I was adding text based visual requirements as needed.\n\n
oAlong the way one may have details that need to be defined to give a developer sufficient information to develop the functionality, beyond just what is self evident in the visuals.\noSo Decide if the visual is “self-evident” and don’t create textual functional requirements for those self-evident pieces. Why waste the time? In this case I don’t need to write a text requirement for describing that there are 6 text boxes and a submit button on this screen - it is self-evident on the mockup screen.\noFor anything else that can’t be readily “seen” as self-evident visually, then go ahead and create a textual functional requirement, but attach it in relation to a hot spot on the mockup or attach it to the screen in play, so there is no ambiguity about the context of the functional requirement. Functional requirements outside of the context of screens, use cases and/or activity flows are in many ways disconnected and non-useful requirements. What good is a listing of -functional requirements when you don’t know the context of the screens or activity flows that they relate to?\noIn this visual we see some text-based requirements on the left hand side. The difference in the way these are used and how most projects use them, is that these requirements will not typically be viewed outside of the context of the screen or use case or activity flow to which they pertain to. Also note that any definition shown on the screen is not described in a requirement – the screen itself, the navigation and hot spots, are themselves requirement elements, and it is self-evident to what is being required throughout the visual. One other thing to note is that one can attach any supporting documentation into the visual use case at the point that it is relevant – in this case at the top I have a link that is not apart of the basic path but again shows a configuration screen for this public facing user interface - providing additional detail and context for the person viewing the requirements.\nI’m not advocating doing away with all functional text requirements. I’m simply expanding the definition of a requirement to include screens, uses cases, links and other artifacts that visually describe functionality in a more robust way.\n
So far I’ve met with one SME to get the main concept, run it by my architect, then found my visual starting point and have now structured my visual use case. Along the way I’ve added hotspots and navigation links and visuals as well as dropping a few text based requirements visually next to the screens or elements they describe, only if needed - ie - the screen or activity flow was not self describing by itself, so it needed a text based requirement to fill it out and make it complete.\n\nNext, I would want to Conduct iterative user walk-throughs with larger and larger groups of SMEs \n \n
Seeking approval of every requirement element - \n
That includes Screens\n
Links off of those screens\n
. . . and each functional requirement\n\nAll of these items \n
. . . including my use case diagram are elemental functional elements that need reviewed as individual elements and approved by my stakeholders - be it product( or the business), then development, and finally Q/A, as individual elements.\n
oAs soon as a major concept is modeled – I walk my business stakeholders through it and ask “is this what you had in mind?” \nNote that I don’t wait for all concepts to be modeled before doing this - that builds agility into your process.\noYou can Change things on the fly and publish the changes immediately. \noYou can Obtain approval and/or capture issues, comments, new functionality, and changes on the fly.\noOne can Update text based and color based status indicators and communicate to development and the team that anything in the approved green status can be worked on immediately.\noRemember you met with one SME to get the vision. So your first walk-through is with them. \n
After that meeting, and another revision on your part, meet with all your product SMEs or business stakeholders. Once they all approve, bring development in \n
Finally, after development and the business are in agreement, bring in Q/A.\n\nNote the last step in this process shows the Mona Lisa being developed from ideation in small parts to the whole - that is agile, right?\n\nThat is the great concept I want you to catch here. We can get approval on any element (screens, links, text requirements) and still have many other elements outstanding in non-approved status. However, that doesn’t stop us from releasing what is approved and allows development to begin their work immediately on those items.\n\nNo more should we hear from a development manager, “well, we cannot provide you a development estimate on your requirements, project manager, until you baseline them all in a waterfall fashion.” \n\nNow we baseline on each element and each path of a use case, and once agreement is obtained from all decision makers we can immediately develop on those elements, while we continue to work to finish all the other requirements and get approval on those in play.\n\n\n
\nWhile we are here I’d like to open up one of the visual elements - could be a functional requirement, could be a screen, could be a link from one screen to another. In this case its a text based functional requirement and here is a view to the details of that element.\n\nIn the requirement here I want to highlight that change control can be obtained by using coloring and versioning (the numbers in brackets). \n\nIn this case I am at version 2.2 of this requirement, and down in the text comment box I show a date and change control notes at the top and in the text you see anything in blue with [2.2] to the right is added and anything in red is considered deleted with the same [2.2] notation to the right. All within the context of the elemental requirement in play.\n\n\n
Once approved, the status can be changed to green approved and that element is cleared for development. On this project approval was done by the business and by development lead on this one element.\n\nSo although many other requirements and elements are still unapproved, around this requirement - maybe even on the same user interface page. On this one, development can go ahead and begin their work immediately.\n\n
♣Why is this way different – why is it better?\n
\nIt’s better because, It builds context and never breaks context. \nMuch more important than showing functionality with a long list of text-based requirements, is showing context that the functionality sits within. If we fail to show context we fail to communicate why we are building functionality. \nI don’t question where this functionality sits in the system as I navigated to the functionality either through the User interface, use cases and/or activity flows. I know where the functionality sits. \nNo one on my team - be in business users, end users, UAT testers, or development wonders what I’ve asked them to build.\n
•This method models the system in the way we best understand it in reality – visually with screens and connected with hot spot navigation. \nThe web has changed the equation for requirements definition in that we now have tools that allow us to model in a visually connected way with hotspots and the ability to publish to a web-site for no-license navigation by our stakeholders. Let’s capitalize on this technology on our projects every time.\n\n
•This method puts functionality directly into context within the existing system. \n We see all the requirements from the perspective of the activities (in activity flows) or the screens (in UI) in the existing system. \nWe have context because we know how we got to the functionality from the starting point – ie. landing pages of a system or use cases.\nWe can see what is existing and what are new functionalities in the context of the as-is existing system.\nThis method Clearly demarks existing functionality from new functionality.\n
•With this method, We see all modalities of the functionality using use case methodology, understanding the typical basic path and all alternate paths a user could or should take.\nUsing use case methodology we can assure ourselves that we are thinking properly in the sense of fulfilling user’s goals and not being driven by just the UI elements.\n\n
•Also, We do away with text based listing of requirements as much as possible by capitalizing on the visual nature of the requirements. We don’t have to describe functionality for a screen that is self-evident in the picture.\nYou’ve heard people talk about chemistry and biology in this way. When asked what is the molecular weight and symbol for Gold, one can throw out a memory item or one can know where to get the information. What I’m doing is connecting everything so that one knows where to “get the information” on the functionality being asked for. Having a text based word doc is like trying to memorize the periodic table and then spit out in code in a user interface. THAT’S CRAZY!\nNo wonder our projects fail so much>>>>>\n
With this method, We can capture user’s changes dynamically as they make them and turn around approvals faster with as close to “real-time” change as possible. Walkthroughs are unambiguous.\n\n•Agility achieved by \noIdentifying all approved items clearly as they are approved and releasing development onto those items immediately. \noModeling can be done in real-time or in short review cycle sessions. \noWaterfall waiting and huge JAD confusion sessions are kept at a minimum. \noNavigation is clear from the start.\noElement level approval versus document FRS level approval is achieved – we can cut off the waterfall and quit looking all wet on our projects.\n\n
\nAnd most importantly the results achieved are simply amazing.\n\nWhich would you rather be apart of making - this shelf on the left or the one on the right.\nWhere 68% of all projects fail, 44% are challenged and 24% canceled.\n\nUsing Visualization teams are seeing \norequirements cycles being reduced by 30%.\no defect reduction by 80%.\no& Project delivery times coming in 35% faster\n\n
•Despite all of the compelling reasons for why we should consider visualization as a better way to define requirements for software development there will be those that will resist.\n•This is where we need to hold to our guns.\n•No one likes change and many people have a lot of time and investment into text-based processes that they aren’t going to want to give up on.\n•STORY: It is like asking people that have been riding bikes for years to consider a car that they have no concept of. They won’t stop using their bike and drive the car until you show them how to use it and give them a ride a few times. Once they catch on they likely will never go back to bike riding. People don’t know what they are missing if they’ve never had it. This methodology is just like that.\n•That is why it takes leadership to say “let’s try it” and then stake a project’s success on it.\n•Most organizations do all kinds of work just because that is the way we’ve always done it. Is having your requirements in a flat 1 dimensional text-based format just like that? We have to get to activities that add real value for those involved. \n•I think this is like my checkbook. STORY: I used to worry about every penny and reconcile every month. I’d spend hours doing this over several personal and business accounts and it really stressed me out. One day I stopped and asked myself – for whom is this activity for and what value does it add to me? When I thought about it I realized that reconciliation for the most part was for me to have proper accounting for the IRS and for tax time. My needs were that I needed to know there was money in there to pay the bills, that I was saving for future goals and to some extent I wanted to know how I was spending for budgeting purposes. Once I realized that the reconciliation process was more for the IRS and banks needs than my own I quit doing it. I don’t care about their needs. I still track my expenses by categories but I don’t care if I’m off by a few hundred dollars – who cares – I don’t. \n•In this same way we need to look at our requirements management processes and really see if the work we are doing is hitting or missing the mark for upstream and downstream stakeholder’s needs. \n•I’d propose that no one looks at old requirements and text based word documents – so don’t invest there. Invest in activities that communicate the requirements in a visual way and hit the mark for getting it right the first time.\n\n
So in my short time here I think we could all agree that most traditional software approaches are not working to achieve the results we all expect.\n\nInstead of approaching the problem from a SDLC approach I’ve simply considered the audience and how best to communicate to them.\n\nThis lead me to strongly believe that visualization is the common sense approach to all forms of best practice communication.\n\nI built my methodology around that premise and with the dynamic nature of web click through have been able to show you a much better way to gather and communicate your software requirements. Of course there is much more detail to all of this that I haven’t shown, but you get the idea.\n\nThey say A picture is worth a thousand words – So I say, communicate visually throughout all parts of the business, and make the development process fun, fast, and financially more cost effective.\n\nSo, as you leave here today, remember that the future is about visualization and not text-based requirements.\n\n