Peter Stephan Andreas is honored for excellence as an award-winning photographer of over 40 years

The updated infographic reflects the state of technology and integration within the CRE and facilities space, with many core elements from the 2012 framework still remaining relevant today.

Taught since 2019, this course has helped hundreds students

Randi Stroh, MM, shared her professional achievements and industry expertise in Architectural Digest

Joseph Yuss Simon shared his professional achievements and industry expertise in Architectural Digest

Explore Ron Gordon Watch Repair's blog on the new 30-story Rolex tower, a symbol of both innovation and heritage, mirroring the excellence of their watch repair services.

Keith Wyndel Downey is a talk show host and board member of the Galveston International Juneteenth Museum

Charmides Von Owens lends years of expertise to his work with MarketStar, Inc.

P&T Interiors, the New York based high-end interior design firm lead by Interior Designer Pol Theis, is featured in Nicole England's latest book Resident Dog Volume Two, a great coffee table book that showcases amazing architecture.

A New York appellate court ruled that the owners of a private residence and their architect were entitled to summary judgment dismissing the Labor Law and negligence claims against them…

This article is a show case of the relationship between architecture and graphic design. In fact, surprisingly few architects use typographical elements in their design. For this overview of projects that do make good use of lettering, I’ve probably browsed through more than thousand Architectural Designs. Below you’ll find ten buildings on integrated architectural lettering and signage

I can only guess about the reason why architects make so little use of typhographical elements on their buildings. The main reason will be that the building design doesn’t need it. Most buildings can make their function clear without the use of signage on the façade. As you will find on the buildings listed below, architects used the signage to show the name of the building to the world; there is no building to be found with its function printed on it. The function is supposed to be clear.

A famous architect once stated: ‘form follows function’. That’s why you know what the particular function of a building is. Architects follow their mantra.

This is a guest post by Frank van Leersum, a Dutch student architecture who likes to write about architecture and books. Visit his Dutch weblog Aureon.

The emergence of AI software in the field of architecture and design has sparked a significant shift in how professionals approach their work. With advancem ...

Keith Doyle, Salford University explains that the aim of information architecture is to improve the information ecology which is made up of the interaction between users, content and context. What is the process and methodology required to develop an information architecture? What are the key tools and enabling services which are required to implement information architecture? How is this process evolving at Salford? There will be a chance to look at the information architecture of institutional web sites, tips for improving the design of sub-sites, and we will look at and discuss real world examples.

Keith Doyle has written a guest blog post for "Brian Kelly's UK Web Focus: Reflections On The Web" blog [2007-06-05]

During Keith Doyle, Salford University talk, delegates will discover how, by taking the information architecture approach as their next step, they can improve the user experience and business benefits. Information architecture gives delegates a framework and benchmarks for managing web provision at an institutional level. This should be an engaging and entertaining talk which would help delegates decide whether a formal IA role is appropriate to their organisation. Helping delegates consider their institutional strategic approach: What is IA? How is the role covered at the moment? Should it be a specific post rather than something that's squeezed in with everything else we do?

Duncan Davidson, Information Manager, University of Abertay Dundee and Donna Wilkinson, Information Specialist, University of Abertay Dundeed will look at their University's development plans, the related projects - University Portal and Information Architecture, where we have been, current work and the road ahead.

ETSI NFV announces new features to its architecture to support 5G

Sophia Antipolis, 1 July 2019

ETSI NFV has enhanced the system as well as designed new features to support 5G networks. Specifically, 5G resource management and orchestration aspects were added on top of the NFV Release 2 architecture framework.

Read More...

ETSI introduces a new end-to-end architectural framework for network and service automation

that can span multiple standards and open source based domain-specific network automation projects

Sophia Antipolis, 24 October 2019

ETSI is pleased to announce two major specifications released by the ETSI Zero-touch network and Service Management (ZSM) Industry Specification Group. ETSI GS ZSM 001 describes ZSM Requirements and ETSI GS ZSM 002 defines the ZSM Reference Architecture. The glossary of terms and concepts related to ZSM is provided in ETSI GS ZSM 007 that was published along with these specifications.

Read More...

Artificial Intelligence for networks: understanding it through ETSI ENI use cases and architecture

Sophia Antipolis, 20 April 2020

On 17 April, ETSI officials from the Experiential Network Intelligence group (ISG ENI) gave a webinar entitled Artificial Intelligence for networks: understanding it through ETSI ENI use cases. This webinar attracted more than 150 online attendees including operators, vendors, research institutions, and international standards development organizations.

Read More...

New ETSI white paper: Harmonizing standards for edge computing, a synergized architecture leveraging ETSI ISG MEC and 3GPP specifications

Sophia Antipolis, 27 July 2020

Members and officials of the ETSI Multi-access Edge Computing group and the 3GPP SA WG6 have just published a new white paper which aims to harmonize standards for edge computing. The white paper highlights the role of standards for edge when edge computing is deployed in conjunction with mobile networks. It also reviews the leading efforts in the industry and introduces a synergized architecture which leverages the ETSI ISG MEC and 3GPP specifications. This paper highlights the value proposition of different standards streams and how those standards may be combined when it comes to deployments. Some deployment options are discussed.

Read More...

ETSI releases first specification on 5^th Generation Fixed Network (F5G) architecture

Sophia Antipolis, 12 May 2022

ETSI's 5^th Generation Fixed Network group (ISG F5G) has released its first specification for F5G Network Architecture ETSI GS F5G 004. This architecture will deliver a variety of services to residential and business customers over a single physical network with guaranteed SLAs (service level agreements).

Read More...

ETSI OSM launches Release THIRTEEN with a new scalable architecture for massive closed-loop operations

Sophia Antipolis, 15 December 2022

The ETSI Open Source MANO community is proud to announce OSM Release THIRTEEN, meeting the already established cadence of two releases per year, alternating between Long Term Support (LTS) releases such as Release TWELVE (2 years’ support) and Standard releases (6 months support).

Read More...

Sophia Antipolis, 26 January 2023

The ETSI Industry Specification Group for Network Functions Virtualization (ISG NFV) has just published its next drop of specifications around new enhancements of the NFV architecture that will support cloud-native network functions.

Read More...

Sophia Antipolis, 26 July 2023

The ETSI Open Source MANO community is proud to announce OSM Release FOURTEEN. Release FOURTEEN is a Long-Term-Support (LTS) release of ETSI OSM, providing two years of continuous support with bug fixes and security patches, and including significant improvements in many key areas.

Read More...

بنية القطاع الزراعي السوداني ومساهمته في الاقتصاد بين عامي 1990 و2021

As refrigerant regulations grow more stringent, manufacturers are beginning to offer new refrigeration architectures that utilize low-GWP refrigerants.

This is the first of a series of Episodes on Software Architecture. Alex, Michael and Markus talk about rather fundamental topics in this episode, we'll go into much more detail in subsequent episodes in that series. Topics in this episode include:

• What is architecture, how is it different from design
• what different kinds of architecture are there in addition to software architecture
• the role of the architect, do we have one or more?
• architecture in agile software development
• tasks of the architect
• architect vs. the technical project lead
• architecture and project politics
• architecture requirements, estimating, team assembling

In this Episode, Michael and Markus continue the discussion about the fundamentals of software architecture (we're doing it without Alex, because it is really hard to find a suitable time for all of us on the phone :-)). We talk about the various quality attributes (such as performance, scalability, maintainability and many more) and how they relate to each other.

SOA (Service Oriented Architecture) appears to be just another hype - after all we have been building distributed systems for quite a while now. But the real value of SOA is non-technical. In this episode Eberhard and Markus discuss the advantages and disadvantages, what SOA actually is and how it compares to other approaches that have been tried out before.

In this third Episode on software architecture, Michael and Markus talk about the basic tools that an architect uses when architecting systems. These tools include things like separation, abstraction, compression and sharing. We also relate these tools to the quality attributes we introduced in previous archtecture episodes.

In this, as well as in the next episode Eberhard and Markus continue their discussion about SOA (the episode got too long, so we had to split it into two ... SOA 2a and SOA 2b). In this episode, we talk about the various perspectives on SOA (CBD, EAI, BPM), about fundamental requirements towards an SOA, and we discuss the role of models in defining sustainable architectures. We also discuss how a programming model based on the described approach typically looks like. We then discuss a number of issues any large-scale SOA faces (and for which the SOA paradigm does not really provide an out-of-the-box solution: In this episode we discuss data type ownership and (weak) typing of data types.

This is the second snippet of the SOA 2 double-episode. Eberhard and Markus continue the discussion with the issue of service reuse and a couple of development process issues. We also look at the duality between infrastructure development and application development in the context of an SOA. We then discuss the great spaghetti misunderstanding :-). We conclude this episode with a look at how to integrate BPM into the conceptual SOA framework we've built up to now, and we'll also briefly skim over a number of technologies related to SOA. Note that this episode, as well as the last one, is based on a set of slides; these can be downloaded from here. This episode covers slides 39 through 74.

In this episode Markus and our Guest Andy Longshaw talk about enterprise architecture. More specifically, we talk about some of the patterns in Andy Longshaw's and Paul Dyson's book Architecting Enterprise Solutions: Patterns for High-Capability Internet-based Systems. These includes things like replication, load balancing, monitoring and application management.

This is the fourth and final episode on the fundamentals of Software Architecture. We talk mainly about architectural styles and patterns, as introduced in the POSA 1 Book. We also discuss a little bit the process of actually using those patterns for architecting systems.

In this episode we talk about the relationship between software architecture and the business. Based on his book, Beyond Software Architecture we discuss how things such as branding, licensing, updating or different deployment scenarios influence the technical architecture of a system. We also discuss issues such as portability that add a huge amount of complexity, although from a business perspective it often does not make much sense. In the second part of the interview we discuss how the technical team and the business team can improve the way they work together. We look at some of the games (such as Buy a Feature or Give them a Hot Tub) from his new book Innovation Games, which discusses how to use collaborative play to be more creative and innovative in product creation.

Enterprise Architecture is already common practice in most Fortune 100 companies. As the topic is comparably young, knowledge about it is not so widespread in the Software Architects Community, who deals mostly with project architectures. In this episode Alex speaks with Wolfgang Keller who has practical experience as an enterprise architect and has written a book on the topic. He is a Partner with BusinessGlue Consulting. They are specializing in the relationship between EAM and SOA. This episode gives a rough overview what Enterprise Architecture actually is touches the standards in the field and also gives hints on the practical work of Enterprise Architects.

In this episode, Markus talks to Rebecca Wirfs-Brock on what she has learned from architecture reviews. This is a very complement to the earlier episode on architecture evaluation.

In this episode we talk with Klaus Marquardt about building systems out of plugins. After briefly introducing the concept of a plugin in contrast to modules and related software engineering concepts, we discuss different views on plugins and different ways of working with plugins for developing software. We are looking at plugins for embedded systems as well as large business systems, at how plugins change the working mode and team organization, and discuss the possibilities of why and when to use plugins for implementing software systems.

In this episode we discuss with Randy Shoup, Distinguished Architect at eBay, about architectural pinciples and patterns used for building the highly scalable eBay infrastructure. The discussion is structured into four main ideas: partition everything, use asynchrony everywhere, automate everything, and design the system keeping in mind that everything fails at some point in a large distributed system.

During Evolution of a software system, it becomes more and more difficult to understand the originally planned software architecture. Often an architectural degeneration happens because of various reasons during the development phases. In this session we will be looking how to avoid such architectural decay and degeneration and how continuous monitoring can improve the situation (and avoid architectural violations). In addition we will look at "refactoring in the large" and how refactoring can be simulated. A new family of "lint like tools for software architectures" is currently emerging in the marketplace I will show some examples and how they scale and support you in real world projects.

This is a discussion with Eoin Woods about his collection of top 10 software architecture mistakes. Looking at things that don't work is always a good way to learn what you should actually do.

This is another episode recorded at OOP 2009, thanks to SIGS Datacom and programme chair Frances Paulisch for making this possible. Here is the abstract from the conference program: Many software systems have fragile architectures that are based on brittle assumptions or rigid architectures that reduce options and make change difficult. On the one hand, an architecture needs to be fit for the present day, suitable for immediate use, and on the other it needs to accommodate the future, absorbing reasonable uncertainty. However, an approach that is overly focused on today's needs and nothing more can create an inflexible architecture. An approach that becomes obsessed with possible future changes creates an overly complex architecture that is unfit for both today's and tomorrow's needs. Both approaches encourage an early descent into legacy for a system. The considerations presented in this talk reflect an approach that is more about thinking in the continuous present tense than just the present or the future tense. This includes principles from lean thinking, practices common in agile processes and techniques for loosely coupled design.

This time we have John Wiegand on the mic for an episode on architectures and agile software development. We talk about the role of architectures in an agile world and why architectures change and need to change over time. We discuss the characteristics of those living architectures, using the Eclipse and the Jazz projects as examples, and the surrounding development methods for such environments.

In this episode, Robert talks with Nati Shalom about the emergence of large-system architectures consisting of a grid of high-memory nodes.

Micro services is an emerging trend in software architecture that focuses on small, lightweight applications as a means to avoid large, unmaintainable, monolithic systems. This approach allows for individual technology stacks for each component and more resilient systems. Micro services uses well-known communication schemes such as REST but also require new technologies for the implementation. […]

Gernot Starke talks about arc42: an open-source set of templates he developed to document software architecture based on his practical experience with real projects. Also Gernot and host Eberhard then discuss how documenting architecture fits into agile processes and how to find the right amount of documentation for a system. They walk through the different parts of the arc42 templates covering requirements and the context of the system and the solution structure, including building blocks, runtime, and deployment. They discuss tooling, versioning, testing documentation, and how to keep documentation up to date.

Mike Barker talks with Sven Johann about the architecture of the LMAX system. LMAX is a low-latency, high-throughput trading platform. Their discussion begins with what LMAX does; the origins of LMAX; and extreme performance requirements faced by LMAX. They then delve into systems that LMAX communicates with; LMAX users; the two main components of the system (broker and exchange); Mechanical Sympathy as an architectural driver; message flow using the Disruptor library; and lock-free algorithms. Mike and Sven wrap up by discussing how a well modeled domain model can improve the performance of any system; automated (performance) tests; continuous delivery; and measuring response times.

Neal Ford chats with Kim Carter about the required skills of a Software Architect, creating and maintain them, transition roles. The importance of history, developing soft skills, and dealing with losing technical skills.