Introducción a la arquitectura software
•
1 like•787 views
This document discusses software architecture and key concepts. It defines architecture as a formal description or plan that guides a system's implementation and structure. It also discusses important architectural principles like dividing a system into components, how they interact through interfaces, and prioritizing what is most important. The document also briefly touches on optimization laws, predominant web architectures of the past versus today, and fundamental database concepts like ACID properties and the CAP theorem.
Report
Share
Report
Share
Download to read offline
Recommended
Tipos de software en el área de diseño
Este documento describe diferentes tipos de software de diseño, incluyendo AutoCAD, Archicad, Autodesk 3ds Max, Microstation, ChieftArchitect, TurboCAD, Sketchup, Revit, Vectorworks, y Cinema 4D. Cada programa se especializa en un área como arquitectura, ingeniería, animación 3D, o modelado, y ofrece ventajas para diseñadores, ingenieros, y otros profesionales.
Diseño de software
Cómo un buen diseño de software es capaz de evitar antipatrones: siguiendo unos principios y buenos patrones de diseño
Diseño de software
El documento presenta información sobre diferentes tipos de interfaces de hardware y sistemas en tiempo real. Describe las diferencias entre tiempo real blando y duro, e introduce conceptos como arquitectura distribuida, base de datos y capacidad de evolución. También resume que el diseño por análisis estructurado se enfoca en el desarrollo de especificaciones modulares e independientes funcionalmente y considera requerimientos no funcionales como la confiabilidad y eficiencia.
TAREA UNIDAD VI DISEÑO DE SOFTWARE
El documento describe las características del software de tiempo real. Este tipo de software responde a problemas en un tiempo dictado por el problema mismo y está muy vinculado al mundo externo. Debe cumplir estrictos límites de tiempo para garantizar un comportamiento correcto, por lo que su diseño considera tanto la arquitectura de hardware como de software.
Bases dedatos
Una base de datos es una colección de información organizada que permite el acceso rápido a los datos. Las bases de datos se pueden clasificar como estáticas o dinámicas dependiendo de si los datos son de solo lectura o pueden modificarse. Existen diferentes tipos de bases de datos como MySQL, PostgreSQL, Oracle, Access y SQL Server.
Creating An Incremental Architecture For Your System
Talk about creating an incremental software architecture presented at OOP 2017 in Munich on the 2nd of February 2017
Software projects management system ( full documentation )
This document describes a software project management system (SPMS) presented for fulfillment of a diploma in computer science. The system aims to automate software project management processes like tasks and work initiation to help managers track projects more efficiently. It will allow different user roles like developers, testers and managers to organize tasks, report and track issues. The system will be a web-based application with a backend database to store project information and generate reports. Requirements were gathered through interviews and observation of current manual processes. The system is intended to reduce time spent on planning and systemize the development process for better quality and efficiency.
Sda 2
This document provides an overview of software architectures and architectural structures. It discusses different types of architectural structures, including module structures, component-and-connector structures, and allocation structures. Module structures focus on modules and their relationships, component-and-connector structures examine runtime components and connectors, and allocation structures show how software elements map to environments. The document then examines specific architectural structures like modules, layers, classes, processes, repositories, and deployment. It emphasizes that an architect should focus on a few key structures like logical, process, development, and physical views to validate that the architecture meets requirements.
Recommended
Tipos de software en el área de diseño
Este documento describe diferentes tipos de software de diseño, incluyendo AutoCAD, Archicad, Autodesk 3ds Max, Microstation, ChieftArchitect, TurboCAD, Sketchup, Revit, Vectorworks, y Cinema 4D. Cada programa se especializa en un área como arquitectura, ingeniería, animación 3D, o modelado, y ofrece ventajas para diseñadores, ingenieros, y otros profesionales.
Diseño de software
Cómo un buen diseño de software es capaz de evitar antipatrones: siguiendo unos principios y buenos patrones de diseño
Diseño de software
El documento presenta información sobre diferentes tipos de interfaces de hardware y sistemas en tiempo real. Describe las diferencias entre tiempo real blando y duro, e introduce conceptos como arquitectura distribuida, base de datos y capacidad de evolución. También resume que el diseño por análisis estructurado se enfoca en el desarrollo de especificaciones modulares e independientes funcionalmente y considera requerimientos no funcionales como la confiabilidad y eficiencia.
TAREA UNIDAD VI DISEÑO DE SOFTWARE
El documento describe las características del software de tiempo real. Este tipo de software responde a problemas en un tiempo dictado por el problema mismo y está muy vinculado al mundo externo. Debe cumplir estrictos límites de tiempo para garantizar un comportamiento correcto, por lo que su diseño considera tanto la arquitectura de hardware como de software.
Bases dedatos
Una base de datos es una colección de información organizada que permite el acceso rápido a los datos. Las bases de datos se pueden clasificar como estáticas o dinámicas dependiendo de si los datos son de solo lectura o pueden modificarse. Existen diferentes tipos de bases de datos como MySQL, PostgreSQL, Oracle, Access y SQL Server.
Creating An Incremental Architecture For Your System
Talk about creating an incremental software architecture presented at OOP 2017 in Munich on the 2nd of February 2017
Software projects management system ( full documentation )
This document describes a software project management system (SPMS) presented for fulfillment of a diploma in computer science. The system aims to automate software project management processes like tasks and work initiation to help managers track projects more efficiently. It will allow different user roles like developers, testers and managers to organize tasks, report and track issues. The system will be a web-based application with a backend database to store project information and generate reports. Requirements were gathered through interviews and observation of current manual processes. The system is intended to reduce time spent on planning and systemize the development process for better quality and efficiency.
Sda 2
This document provides an overview of software architectures and architectural structures. It discusses different types of architectural structures, including module structures, component-and-connector structures, and allocation structures. Module structures focus on modules and their relationships, component-and-connector structures examine runtime components and connectors, and allocation structures show how software elements map to environments. The document then examines specific architectural structures like modules, layers, classes, processes, repositories, and deployment. It emphasizes that an architect should focus on a few key structures like logical, process, development, and physical views to validate that the architecture meets requirements.
Lecture-_-5-_SDA_software design and architecture.doc
This lecture discusses software architecture. It begins by explaining that software architecture refers to the structure of a system, including its software elements, their properties, and relationships. An example diagram is shown but it is noted that the diagram alone does not represent the full architecture. Common architectural structures like patterns, reference models, and reference architectures are introduced. The lecture emphasizes that architecture is important because it enables communication between stakeholders, represents early critical design decisions, and can provide reusable abstractions of systems.
Se
DEFINITION OF SOFTWARE AND SOFTWARE ENGINEERING.
EVOLVING ROLE OF SOFTWARE AND SOFTWARE ENGINEERING AS A LAYERED STRUCTURE.
Design patterns
The document discusses various software design patterns including Singleton, MVC, Factory Method, and Observer. It provides examples of when and how each pattern is used. For instance, the Singleton pattern ensures only one instance of a resource exists, like a database connection. The MVC pattern separates business logic from presentation logic. The Factory Method creates object instances by defining an interface, while the Observer pattern allows objects to watch others for state changes. Design patterns provide proven solutions to common software problems and facilitate communication between designers.
Function Oriented and Object Oriented Design,Modularization techniques
Design activity & its objectives – Function Oriented and Object Oriented Design- Modularization techniques - module structure and its representation, interface and information hiding, categories, specific techniques to accommodate change, stepwise refinement, top-down and bottom-up design - Handling anomalies.
software engineering
This document provides an overview and introduction to the book "Software Engineering: A Hands-On Approach" by Roger Y. Lee. The book aims to teach key principles of software engineering through hands-on learning and a project-based approach. It uses common tools like the Unified Modeling Language and object-oriented design patterns. The book is divided into two parts - the first introduces software engineering concepts, and the second guides readers through a software project from requirements to implementation and testing. The goal is to help students bridge the gap between academic learning and real-world practice of software engineering.
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
Advantages And Disadvantages Of The Activities Of Software...
The document discusses and compares various software development models including waterfall, prototype, rapid application development, incremental, spiral, build and fix, and V-shaped models. It outlines the advantages and disadvantages of each model. The aim is to select reliable and cost-effective models for software development. A comparative study is presented of the different models along with their defects and features to determine the most appropriate model for a given project.
Wanna see your open source project succeed? - Nurture your community
Many open source projects stagnate after an initial push and end-up fading away. In this talk, we will argue that, most of the time, the reason has nothing to do with the quality of the software itself but with the project's inability to attract and support a healthy community around it. A community of contributors but also a community of users that must take an active role in the project as well.
We will review several actions and strategies that OSS project managers could put into practice to reverse this situation, mostly taken from atypical disciplines (for a software talk) like social science, economy and political science. As an example, we will talk about transparency and democracy in OSS, matching market design and software ecosystems.
Creating An Incremental Architecture For Your System
The version for ACCU 2018. With many improvements, and new thoughts and insights compared with previous versions.
Design patterns
Design patterns are commonly used to address problems relating to application architecture and design. The concept originated from Christopher Alexander's work noting common building design problems and solutions. Design patterns ensure problems are addressed through well-known solutions, and most problems have likely been solved before. Common patterns include observer/subject to separate user interface from business logic, singleton to control object construction, strategy to allow multiple algorithms, and template method to define an algorithm's structure. The facade pattern provides different views of subsystems to users by hiding implementation details. The command pattern encapsulates requests as objects with a known interface to decouple senders and receivers.
UNIT3 PART2.pptx dhfdifhdsfvgudf dhfbdhbffdvf
The document discusses key concepts in software design including abstraction, architecture, patterns, modularity, coupling and cohesion, and information hiding. It defines software design as transforming user requirements into an implementable form using programming languages. The software design process exists between requirements and programming and yields architectural, high-level, and detailed designs. It also outlines characteristics of good design like correctness, efficiency, and understandability.
Architectural Styles And The Design Of Network-Based Software Architectures
This document summarizes an academic paper on architectural styles for network-based software architectures. It defines key terms related to software architecture like elements, configurations, properties, and styles. It discusses how architectural styles can be used to guide the design of network-based application software and classify styles based on the properties they induce. It specifically introduces the Representational State Transfer (REST) architectural style and how it was used to guide the design of the modern Web architecture.
Ooad
This document contains a chapter from a course manual on Object Oriented Analysis and Design. The chapter discusses the inherent complexity of software systems. It identifies four main reasons for this complexity: 1) the complexity of the problem domain and changing requirements, 2) the difficulty of managing large software development teams, 3) the flexibility enabled by software which can lead to more demanding requirements, and 4) the challenges of characterizing the behavior of discrete systems. Software systems can range from simple to highly complex, depending on factors like purpose, lifespan, number of users, and role in research.
Technology Integration Pattern For Distributed Scrum of Scrum
This document discusses technology integration patterns for distributed scrum projects. It notes that past work has addressed integration issues for distributed components using scrum, but has ignored the technology factor - components may use different technologies that affect functionality. The document proposes a new pattern to control technology integration for distributed components in scrum projects. It found this pattern increases project survival chances by 80% by reducing risks and improving maintainability and scalability. Previous patterns for distributed scrum of scrum are also discussed.
Modularity | By Amir Yousefi
The document discusses different definitions and perspectives on software architecture. It defines architecture as the important components and interfaces that all developers understand. It says architecture represents significant design decisions that shape a system. The goal of architecture should be to eliminate the impact and cost of change. However, making a system too flexible to enable change can paradoxically make it more complex. Modularity, reuse, and shared understanding can help reduce complexity that arises from flexibility.
1- Modularity - Amir yousefi
The document discusses different definitions and perspectives on software architecture. It defines architecture as the important components and interfaces that all developers understand. It says architecture represents significant design decisions that shape a system. The goal of architecture should be to eliminate the impact and cost of change. However, making a system too flexible to enable change can paradoxically make it more complex. Modularity, reuse, and shared understanding can help reduce complexity when managing architecture and enabling evolution.
Software Architectures, Week 1 - Monolithic Architectures
This document provides an overview of system architecture and design patterns. It discusses layer architecture and the separation of concerns principle. While MVC is a design pattern for user interfaces, layers separate components by role and allow for modular development. The document cautions against "sinkholes" where requests pass through layers without processing. It recommends separating concerns into modules to address specific functionality. The document advocates starting with a monolithic architecture for early-stage projects, and explores when to transition to microservices. It summarizes a candidate architecture for a wishlist application using Ruby, Hanami, and other technologies that enforce separation of concerns.
The Four Main Values Of The Agile Methodologies In...
The document discusses transitioning a business to use the Scrum agile methodology for software development projects. It notes that client organizations are increasingly looking to agile methods like Scrum to minimize risks. Scrum is an iterative development process where new working versions are released at the end of each "sprint." It enables daily face-to-face communication among cross-functional team members. The document will provide an outline of the Scrum methodology and how it facilitates communication and collaboration.
Runnics at ProductHunt Madrid
This document appears to be notes from various months listing topics such as the team, first days, strategies, platforms, designs, backends, and APIs. It also thanks the viewer for their time and asks if they have any questions. The notes cover various aspects of a project from January to August including the initial team and days, changes to strategy, the development of platforms and editions, work on the backend and design, and partnerships.
Otogami at Tetuan Valley
This document discusses various myths about startups and engineering. It touches on topics such as the differences between science and engineering, working for trendy startups with toys and coffee shops, using the latest technologies, prioritizing innovative over useful solutions, and whether users are dumb. The document encourages keeping engineering simple and focusing on providing value rather than getting distracted by unnecessary things.
More Related Content
Similar to Introducción a la arquitectura software
Lecture-_-5-_SDA_software design and architecture.doc
This lecture discusses software architecture. It begins by explaining that software architecture refers to the structure of a system, including its software elements, their properties, and relationships. An example diagram is shown but it is noted that the diagram alone does not represent the full architecture. Common architectural structures like patterns, reference models, and reference architectures are introduced. The lecture emphasizes that architecture is important because it enables communication between stakeholders, represents early critical design decisions, and can provide reusable abstractions of systems.
Se
DEFINITION OF SOFTWARE AND SOFTWARE ENGINEERING.
EVOLVING ROLE OF SOFTWARE AND SOFTWARE ENGINEERING AS A LAYERED STRUCTURE.
Design patterns
The document discusses various software design patterns including Singleton, MVC, Factory Method, and Observer. It provides examples of when and how each pattern is used. For instance, the Singleton pattern ensures only one instance of a resource exists, like a database connection. The MVC pattern separates business logic from presentation logic. The Factory Method creates object instances by defining an interface, while the Observer pattern allows objects to watch others for state changes. Design patterns provide proven solutions to common software problems and facilitate communication between designers.
Function Oriented and Object Oriented Design,Modularization techniques
Design activity & its objectives – Function Oriented and Object Oriented Design- Modularization techniques - module structure and its representation, interface and information hiding, categories, specific techniques to accommodate change, stepwise refinement, top-down and bottom-up design - Handling anomalies.
software engineering
This document provides an overview and introduction to the book "Software Engineering: A Hands-On Approach" by Roger Y. Lee. The book aims to teach key principles of software engineering through hands-on learning and a project-based approach. It uses common tools like the Unified Modeling Language and object-oriented design patterns. The book is divided into two parts - the first introduces software engineering concepts, and the second guides readers through a software project from requirements to implementation and testing. The goal is to help students bridge the gap between academic learning and real-world practice of software engineering.
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
This document provides course notes on software architecture. It begins with an overview of the course and its modules. Module 1 covers UML architecture diagrams, including Kruchten's 4+1 View Model (logical, process, development, physical views and scenarios). It describes component diagrams, package diagrams, deployment diagrams, and activity diagrams. Module 2 will cover architectural styles like layered systems and pipes and filters. Module 3 discusses quality attributes, architecture analysis, trade-off analysis, and product lines.
Advantages And Disadvantages Of The Activities Of Software...
The document discusses and compares various software development models including waterfall, prototype, rapid application development, incremental, spiral, build and fix, and V-shaped models. It outlines the advantages and disadvantages of each model. The aim is to select reliable and cost-effective models for software development. A comparative study is presented of the different models along with their defects and features to determine the most appropriate model for a given project.
Wanna see your open source project succeed? - Nurture your community
Many open source projects stagnate after an initial push and end-up fading away. In this talk, we will argue that, most of the time, the reason has nothing to do with the quality of the software itself but with the project's inability to attract and support a healthy community around it. A community of contributors but also a community of users that must take an active role in the project as well.
We will review several actions and strategies that OSS project managers could put into practice to reverse this situation, mostly taken from atypical disciplines (for a software talk) like social science, economy and political science. As an example, we will talk about transparency and democracy in OSS, matching market design and software ecosystems.
Creating An Incremental Architecture For Your System
The version for ACCU 2018. With many improvements, and new thoughts and insights compared with previous versions.
Design patterns
Design patterns are commonly used to address problems relating to application architecture and design. The concept originated from Christopher Alexander's work noting common building design problems and solutions. Design patterns ensure problems are addressed through well-known solutions, and most problems have likely been solved before. Common patterns include observer/subject to separate user interface from business logic, singleton to control object construction, strategy to allow multiple algorithms, and template method to define an algorithm's structure. The facade pattern provides different views of subsystems to users by hiding implementation details. The command pattern encapsulates requests as objects with a known interface to decouple senders and receivers.
UNIT3 PART2.pptx dhfdifhdsfvgudf dhfbdhbffdvf
The document discusses key concepts in software design including abstraction, architecture, patterns, modularity, coupling and cohesion, and information hiding. It defines software design as transforming user requirements into an implementable form using programming languages. The software design process exists between requirements and programming and yields architectural, high-level, and detailed designs. It also outlines characteristics of good design like correctness, efficiency, and understandability.
Architectural Styles And The Design Of Network-Based Software Architectures
This document summarizes an academic paper on architectural styles for network-based software architectures. It defines key terms related to software architecture like elements, configurations, properties, and styles. It discusses how architectural styles can be used to guide the design of network-based application software and classify styles based on the properties they induce. It specifically introduces the Representational State Transfer (REST) architectural style and how it was used to guide the design of the modern Web architecture.
Ooad
This document contains a chapter from a course manual on Object Oriented Analysis and Design. The chapter discusses the inherent complexity of software systems. It identifies four main reasons for this complexity: 1) the complexity of the problem domain and changing requirements, 2) the difficulty of managing large software development teams, 3) the flexibility enabled by software which can lead to more demanding requirements, and 4) the challenges of characterizing the behavior of discrete systems. Software systems can range from simple to highly complex, depending on factors like purpose, lifespan, number of users, and role in research.
Technology Integration Pattern For Distributed Scrum of Scrum
This document discusses technology integration patterns for distributed scrum projects. It notes that past work has addressed integration issues for distributed components using scrum, but has ignored the technology factor - components may use different technologies that affect functionality. The document proposes a new pattern to control technology integration for distributed components in scrum projects. It found this pattern increases project survival chances by 80% by reducing risks and improving maintainability and scalability. Previous patterns for distributed scrum of scrum are also discussed.
Modularity | By Amir Yousefi
The document discusses different definitions and perspectives on software architecture. It defines architecture as the important components and interfaces that all developers understand. It says architecture represents significant design decisions that shape a system. The goal of architecture should be to eliminate the impact and cost of change. However, making a system too flexible to enable change can paradoxically make it more complex. Modularity, reuse, and shared understanding can help reduce complexity that arises from flexibility.
1- Modularity - Amir yousefi
The document discusses different definitions and perspectives on software architecture. It defines architecture as the important components and interfaces that all developers understand. It says architecture represents significant design decisions that shape a system. The goal of architecture should be to eliminate the impact and cost of change. However, making a system too flexible to enable change can paradoxically make it more complex. Modularity, reuse, and shared understanding can help reduce complexity when managing architecture and enabling evolution.
Software Architectures, Week 1 - Monolithic Architectures
This document provides an overview of system architecture and design patterns. It discusses layer architecture and the separation of concerns principle. While MVC is a design pattern for user interfaces, layers separate components by role and allow for modular development. The document cautions against "sinkholes" where requests pass through layers without processing. It recommends separating concerns into modules to address specific functionality. The document advocates starting with a monolithic architecture for early-stage projects, and explores when to transition to microservices. It summarizes a candidate architecture for a wishlist application using Ruby, Hanami, and other technologies that enforce separation of concerns.
The Four Main Values Of The Agile Methodologies In...
The document discusses transitioning a business to use the Scrum agile methodology for software development projects. It notes that client organizations are increasingly looking to agile methods like Scrum to minimize risks. Scrum is an iterative development process where new working versions are released at the end of each "sprint." It enables daily face-to-face communication among cross-functional team members. The document will provide an outline of the Scrum methodology and how it facilitates communication and collaboration.
Similar to Introducción a la arquitectura software (20)
Lecture-_-5-_SDA_software design and architecture.doc
Lecture-_-5-_SDA_software design and architecture.doc
Function Oriented and Object Oriented Design,Modularization techniques
Function Oriented and Object Oriented Design,Modularization techniques
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
_773d48108e2dda1c1a731bf69b06c3be_Software-Architecture_Course-Notes.pdf
Advantages And Disadvantages Of The Activities Of Software...
Advantages And Disadvantages Of The Activities Of Software...
Wanna see your open source project succeed? - Nurture your community
Wanna see your open source project succeed? - Nurture your community
Creating An Incremental Architecture For Your System
Creating An Incremental Architecture For Your System
Architectural Styles And The Design Of Network-Based Software Architectures
Architectural Styles And The Design Of Network-Based Software Architectures
Technology Integration Pattern For Distributed Scrum of Scrum
Technology Integration Pattern For Distributed Scrum of Scrum
Software Architectures, Week 1 - Monolithic Architectures
Software Architectures, Week 1 - Monolithic Architectures
The Four Main Values Of The Agile Methodologies In...
The Four Main Values Of The Agile Methodologies In...
More from Yeray Darias
Runnics at ProductHunt Madrid
This document appears to be notes from various months listing topics such as the team, first days, strategies, platforms, designs, backends, and APIs. It also thanks the viewer for their time and asks if they have any questions. The notes cover various aspects of a project from January to August including the initial team and days, changes to strategy, the development of platforms and editions, work on the backend and design, and partnerships.
Otogami at Tetuan Valley
This document discusses various myths about startups and engineering. It touches on topics such as the differences between science and engineering, working for trendy startups with toys and coffee shops, using the latest technologies, prioritizing innovative over useful solutions, and whether users are dumb. The document encourages keeping engineering simple and focusing on providing value rather than getting distracted by unnecessary things.
Runnics en Betabeers Madrid
Este documento presenta una cronología de los hitos y desafíos clave en el desarrollo de un proyecto de software desde sus primeros días en febrero hasta septiembre. Comienza con la formación del equipo en enero y febrero, luego describe cómo el software comenzó a funcionar en febrero y marzo pero surgieron cuellos de botella que requirieron subcontratar diseño. Más adelante se completaron el frontend, backend y API y el software estuvo listo para producción en junio, aunque surgieron problemas de estabilidad en
Agile and Scrum
The document discusses Agile and Scrum frameworks for software development. It introduces the Agile Manifesto which values individuals and interactions, working software, customer collaboration, and responding to change over processes, documentation, contract negotiation, and following a plan. It then describes Scrum roles of Product Owner, Scrum Master, and Team as well as ceremonies of Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. It also mentions Scrum artifacts like the Product Backlog, Sprint Backlog, and Burndown Chart. Finally, it notes that Agile is about delivering maximum value in minimum time and invites any questions.
Coffee Script
CoffeeScript is a programming language that compiles to JavaScript. It addresses issues in JavaScript like global variables, semicolons, and reserved words by generating proper JavaScript code. CoffeeScript also improves control flow, functions, classes, and other aspects of JavaScript. It allows everything to be an expression, uses chained comparisons, and string interpolation to make code more concise and readable.
Scrum
These are my slides for a Scrum course I did in May 2012. Obviously if you were not in the course they are not too much explanatory.
SOLID principles
This document discusses the SOLID principles of object-oriented design:
1. Single responsibility principle - each class should have a single responsibility and only one reason to change.
2. Open-closed principle - code should be open for extension but closed for modification. New features can be added without changing existing code.
3. Liskov substitution principle - subclasses should be substitutable for their parent classes without errors occurring.
4. Interface segregation principle - large classes should define interfaces for groups of methods to decrease dependency.
5. Dependency inversion principle - classes should not create dependencies directly but use dependency injection through setters or constructors for flexibility.
Introducción a jQuery
Charla de introducción a jQuery en la Tenerife Lan Party 2011. Si no has asistido es muy posible que no te sirva de mucho :-P
Integración Continua - TLP+i 2K10
El documento presenta una introducción a la integración continua realizada por Fran Reyes Perdomo y Yeray Darias Camacho. Explican que la integración continua implica construir el software con cada cambio realizado y tener un proceso que permita corregir errores tempranamente. También describen los pasos clave de la integragración continua como la construcción, pruebas y despliegue continuos para lograr feedback constante y mejorar la calidad del código.
More from Yeray Darias (9)
Recently uploaded
Using Xen Hypervisor for Functional Safety
An update on making Xen hypervisor functionally safe and enhancing its usage in automotive and industrial use cases
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
GraphSummit Paris - The art of the possible with Graph Technology
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
Recently uploaded (20)
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
GraphSummit Paris - The art of the possible with Graph Technology
GraphSummit Paris - The art of the possible with Graph Technology
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
Introducción a la arquitectura software
- 1. Arquitectura Software Manual de supervivencia Yeray Darias Camacho @ydarias
- 2. ¿Quién soy?
- 9. Equipo
- 11. Metodología
- 14. Antes de proseguir ... yo uso el lenguaje que más me conviene y punto.
- 15. ¿Qué es la arquitectura del software?
- 16. 1. “A formal description of a system, or a detailed plan of the system at component level to guide its implementation.” The Open Group Architecture Framework
- 17. 2. “The structure of components, their inter- relationships, and the principles and guidelines governing their design and evolution over time.” The Open Group Architecture Framework
- 18. “In most successful software projects, the expert developers working on that project have a shared understanding of the system design. This shared understanding is called “architecture.” This understanding includes how the system is divided into components and how the components interact through interfaces. These components are usually composed of smaller components, but the architecture only includes the components and interfaces that are understood by all the developers ... Architecture is about the important stuff. Whatever that is.” Martin Fowler
- 19. Las tres leyes de la optimización
- 20. #1 No optimizar
- 21. #2 No optimizar aún
- 22. #3 Si optimizas hazlo en función de una medida
- 23. Arquitectura web predominante hace 5 años Petición HTTP Respuesta HTML
- 25. Arquitectura web actual??? Petición AJAX Respuesta JSON Petición AJAX Respuesta JSON
- 27. Petición HTTP (Ajax) Respuesta JSON
- 31. Teorema CAP Consistency Partition tolerance* Availability *Se da por hecho en sistemas distribuidos modernos
- 34. Veamos que hay bajo el capó