The document discusses the importance of taking a top-down approach to network design that begins by analyzing business goals and constraints. It emphasizes understanding the organization, applications, and information flows before designing network structures and technologies. The network design process involves gathering requirements, developing logical and physical designs, testing and optimizing the network, and then operating and maintaining it over time.
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
“The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.” [1]
“A conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives.”[2]
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
“The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.” [1]
“A conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives.”[2]
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
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
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
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.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
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/
2. Top-Down Network Design
• Network design should be a complete
process that matches business needs to
available technology to deliver a system that
will maximize an organization’s success.
– In the LAN area it is more than just buying a few
devices.
– In the WAN area it is more than just calling the
phone company.
3. Start at the Top
• Don’t just start connecting the dots.
• Analyze business and technical goals first.
• Explore divisional and group structures to
find out who the network serves and where
they reside.
• Determine what applications will run on the
network and how those applications behave
on a network.
• Focus on Layer 7 and above first.
4. Layers of the OSI Model
Application
Presentation
Session
Transport
Network
Data Link
Physical
Layer 1
Layer 7
Layer 6
Layer 5
Layer 4
Layer 3
Layer 2
5. Structured Design
• A focus is placed on understanding data flow, data types, and
processes that access or change the data.
• A focus is placed on understanding the location and needs of
user communities that access or change data and processes.
• Several techniques and models can be used to characterize the
existing system, new user requirements, and a structure for the
future system.
• A logical model is developed before the physical model.
– The logical model represents the basic building blocks, divided by
function, and the structure of the system.
– The physical model represents devices and specific technologies and
implementations.
6. Systems Development Life
Cycles
• SDLC: Does it mean Synchronous Data
Link Control or Systems Development Life
Cycle?
• The latter for the purposes of this class!
• Typical systems are developed and continue
to exist over a period of time, often called a
systems development life cycle (SDLC).
8. Network Design Steps
• Phase 1 – Analyze Requirements
– Analyze business goals and constraints
– Analyze technical goals and tradeoffs
– Characterize the existing network
– Characterize network traffic
9. Network Design Steps
• Phase 2 – Logical Network Design
– Design a network topology
– Design models for addressing and naming
– Select switching and routing protocols
– Develop network security strategies
– Develop network management strategies
10. Network Design Steps
• Phase 3 – Physical Network Design
– Select technologies and devices for campus
networks
– Select technologies and devices for enterprise
networks
11. Network Design Steps
• Phase 4 – Testing, Optimizing, and
Documenting the Network Design
– Test the network design
– Optimize the network design
– Document the network design
12. The PDIOO Network Life Cycle
Plan
Design
Implement
Operate
Optimize
Retire
13. Business Goals
• Increase revenue
• Reduce operating costs
• Improve communications
• Shorten product development cycle
• Expand into worldwide markets
• Build partnerships with other companies
• Offer better customer support or new
customer services
14. Recent Business Priorities
• Mobility
• Security
• Resiliency (fault tolerance)
• Business continuity after a disaster
• Network projects must be prioritized based
on fiscal goals
• Networks must offer the low delay required
for real-time applications such as VoIP
16. Collect Information Before the
First Meeting
• Before meeting with the client, whether
internal or external, collect some basic
business-related information
• Such as
– Products produced/Services supplied
– Financial viability
– Customers, suppliers, competitors
– Competitive advantage
17. Meet With the Customer
• Try to get
– A concise statement of the goals of the
project
• What problem are they trying to solve?
• How will new technology help them be
more successful in their business?
• What must happen for the project to
succeed?
18. Meet With the Customer
• What will happen if the project is a failure?
– Is this a critical business function?
– Is this project visible to upper management?
– Who’s on your side?
19. Meet With the Customer
• Discover any biases
– For example
• Will they only use certain company’s
products?
• Do they avoid certain technologies?
• Do the data people look down on the
voice people or vice versa?
– Talk to the technical and
management staff
20. Meet With the Customer
– Get a copy of the organization chart
• This will show the general structure of the organization
• It will suggest users to account for
• It will suggest geographical locations to account for
21. Meet With the Customer
– Get a copy of the security policy
• How does the policy affect the new design?
• How does the new design affect the policy?
• Is the policy so strict that you (the network designer)
won’t be able to do your job?
– Start cataloging network assets that security
should protect
• Hardware, software, applications, and data
• Less obvious, but still important, intellectual
property, trade secrets, and a company's reputation
22. The Scope of the Design Project
• Small in scope?
– Allow sales people to access network via a VPN
• Large in scope?
– An entire redesign of an enterprise network
• Use the OSI model to clarify the scope
– New financial reporting application versus new
routing protocol versus new data link (wireless, for
example)
• Does the scope fit the budget, capabilities of staff
and consultants, schedule?
23. Gather More Detailed Information
• Applications
– Now and after the project is completed
– Include both productivity applications and
system management applications
• User communities
• Data stores
• Protocols
• Current logical and physical architecture
• Current performance
25. Summary
• Systematic approach
• Focus first on business requirements and
constraints, and applications
• Gain an understanding of the customer’s
corporate structure
• Gain an understanding of the customer’s
business style
26. Review Questions
• What are the main phases of network design per the
top-down network design approach?
• What are the main phases of network design per the
PDIOO approach?
• Why is it important to understand your customer’s
business style?
• What are some typical business goals for
organizations today?
Editor's Notes
Layer 8 of the OSI model encompasses office politics, budgets, training, and other human factors.
Resiliency means how much stress a network can handle and how quickly the network can rebound from problems, including security breaches, natural and unnatural disasters, human error, and catastrophic software or hardware failures.
Some experts, including Howard Berkowitz, have a mild dislike of the word “resiliency” as it sounds too much like a stretched rubber band or a trampoline. As Berkowitz says in his excellent book, WAN Survival Guide (Wiley 2001), “I avoid designing networks that stretch too far, bounce up and down, or oscillate between normal and backup states.”
So he likes “fault tolerance,” but he points out that it does not mean “immune to any conceivable threat.” Berkowitz states that, “A sufficient quantity of explosives can overcome the tolerance of any network.” :-)
User communities, data stores, protocols, and the current architecture and performance will be discussed in the next few chapters. This chapter focuses on business needs and applications, which should be the first area of research in a top-down network design project. Network design is iterative, however, so many topics are addressed more than once as the designer gathers more detailed information and conducts more precise planning. So, gaining a general understanding of the size and location of user communities, for example, might be appropriate at this stage of the design project, but user communities should be investigated again when characterizing network traffic.