1 - Architetture Software - Software as a productMajong DevJfu
This document discusses software as a product and industry. It covers how software is a key component in modern technologies and industries. The software industry has grown significantly in recent decades. The document discusses different types of software such as embedded software, middleware, and software as a service. It also covers topics like software architecture, engineering, components, ecosystems, and the challenges in developing software. Overall, the document provides an overview of software as an industrial product and the software development industry.
1 - Architetture Software - Software as a productMajong DevJfu
This document discusses software as a product and industry. It covers how software is a key component in modern technologies and industries. The software industry has grown significantly in recent decades. The document discusses different types of software such as embedded software, middleware, and software as a service. It also covers topics like software architecture, engineering, components, ecosystems, and the challenges in developing software. Overall, the document provides an overview of software as an industrial product and the software development industry.
Query Processor & Statistics: A Performance PrimerDavide Mauri
Le performance di un database sono strettamente legate al funzionamento del suo componente più "intelligente", il query processor, ai dati presenti nel database stesso, alle query che vengono scritte e - importantissime - alle stime di distribuzione dei dati che ogni RDBMS si mantiene per poter fare al meglio il proprio lavoro. In questa sessione vederemo come tutte queste cose concorrono a produrre performance ottimali - o meno - in SQL Server
This document discusses software services and cloud computing architectures. It begins by providing context on the growing service economy and how businesses are increasingly offering services rather than products. It then defines software-as-a-service (SaaS) and describes how SaaS delivers software applications over the internet, with updates and management occurring remotely. Finally, the document discusses service-oriented architectures and how they support the development and delivery of software services.
The document discusses architecture-centric software development processes. It describes traditional waterfall and iterative development models, and notes that iterative models allow for more flexibility to changing requirements. Agile development methods like eXtreme Programming (XP) are discussed, which emphasize iterative development, collaboration, and rapid delivery of working software. Key practices of XP are outlined, including user stories, testing, pair programming, refactoring, and continuous integration. The role of architecture in agile processes is also addressed.
This document discusses software product lines and product line architectures. It defines a software product line as a set of software systems that share a common set of features addressing a particular market segment. Product lines are developed from a common set of core assets in a prescribed way to reduce costs and increase reuse. A product line architecture is a common framework that standardizes components and maximizes reuse potential. It specifies common functionality and identifies variation points across related products. Variability management is important for providing flexibility without compromising commonality.
6 - Architetture Software - Model transformationMajong DevJfu
This document discusses model transformations in Model-Driven Architecture (MDA). It defines computation independent models (CIMs), platform independent models (PIMs), and platform specific models (PSMs). It explains that model transformations are used to map between these different abstraction levels and ensure consistency. It also discusses model mappings, approaches to transformations, and tools like EMF and ATL that support transformations in Eclipse.
5 - Architetture Software - Metamodelling and the Model Driven ArchitectureMajong DevJfu
The document discusses metamodeling and the Model Driven Architecture (MDA). It covers topics such as model driven engineering, metamodeling, metamodeling in UML, and the OMG technologies that support MDA. Metamodeling involves modeling modeling elements and their relationships. Metamodels define the structure of models, while models are instances that conform to metamodels. The MDA uses metamodels and models to develop and transform systems.
This document provides an overview of software architectures by presenting examples of architectures from various software systems. It begins with an introduction to software architecture and what it entails. It then shows numerous diagrams and visualizations of architectures for different types of systems, such as editors, compilers, operating systems, middleware, and web applications. These examples are intended to demonstrate common architectural patterns and styles. The document discusses analyzing and comparing the architectures visually and recognizing patterns within them.
The document discusses architectural styles and decomposition techniques for software systems. It describes layering and tiering as basic decomposition approaches, with layers representing different levels of abstraction and tiers representing peer modules within the same layer. Several common architectural styles are then introduced, including pipes and filters, repository, client/server, model-view-controller, service-oriented, and peer-to-peer. Closed and open layered architectures are contrasted, and examples of layered systems like virtual machines and the OSI model are provided. Finally, the document notes that complete decompositions often involve both layering and partitioning techniques.
The document discusses key concepts in software architecture, including:
1) Software architecture establishes the overall structure and organization of a system, including its components and relationships.
2) Architectural design involves decomposing a system into subsystems or modules to improve modifiability, reusability, and portability.
3) Key principles for architectural design include simplicity, modularity, low coupling, separation of concerns, abstraction, and postponing decisions.
10 - Architetture Software - More architectural stylesMajong DevJfu
The Microkernel pattern partitions an operating system into isolated, minimal components that communicate through a small, fixed message-passing interface, allowing components to be developed and upgraded independently while maintaining overall system stability and security.
The document discusses architectural UML and provides information on:
1) The elements of a software architecture including views, models, and diagrams.
2) How UML can be used to represent different architectural views including design, process, development, and physical views.
3) An example of using UML models and diagrams to represent different views of a chess game architecture.
UML allows for extending diagrams and modeling elements through three main techniques:
1. Stereotypes allow applying tags to existing modeling elements like classes, associations, etc. to add domain-specific meaning.
2. Profiles extend UML with new modeling elements tailored for specific domains or platforms.
3. Extension mechanisms allow precisely defining new constructs that integrate with the UML metamodel. Together these techniques make UML extensible for multiple domains.
The document discusses metamodeling and the Model Driven Architecture (MDA). It provides an overview of model driven engineering and metamodeling. Specifically, it discusses how metamodels define the structure of models through concepts like classes and relationships. The Model Driven Architecture uses metamodels and modeling to develop software systems from models.
Here are the key differences between objects and classes in UML:
- Classes define the general characteristics (attributes and operations) that objects of that class will have. Objects are specific instances of a class.
- Classes are static definitions, while objects are dynamic instances of classes that exist at run time.
- In class diagrams, classes are represented as boxes containing the attributes and operations. Objects are represented as boxes with the class name followed by a colon and the object name (e.g. Person:John).
- Classes define the common properties for a set of objects, while each object is a unique instance of a class with its own identity and particular values for attributes.
- Classes are abstractions,
Query Processor & Statistics: A Performance PrimerDavide Mauri
Le performance di un database sono strettamente legate al funzionamento del suo componente più "intelligente", il query processor, ai dati presenti nel database stesso, alle query che vengono scritte e - importantissime - alle stime di distribuzione dei dati che ogni RDBMS si mantiene per poter fare al meglio il proprio lavoro. In questa sessione vederemo come tutte queste cose concorrono a produrre performance ottimali - o meno - in SQL Server
This document discusses software services and cloud computing architectures. It begins by providing context on the growing service economy and how businesses are increasingly offering services rather than products. It then defines software-as-a-service (SaaS) and describes how SaaS delivers software applications over the internet, with updates and management occurring remotely. Finally, the document discusses service-oriented architectures and how they support the development and delivery of software services.
The document discusses architecture-centric software development processes. It describes traditional waterfall and iterative development models, and notes that iterative models allow for more flexibility to changing requirements. Agile development methods like eXtreme Programming (XP) are discussed, which emphasize iterative development, collaboration, and rapid delivery of working software. Key practices of XP are outlined, including user stories, testing, pair programming, refactoring, and continuous integration. The role of architecture in agile processes is also addressed.
This document discusses software product lines and product line architectures. It defines a software product line as a set of software systems that share a common set of features addressing a particular market segment. Product lines are developed from a common set of core assets in a prescribed way to reduce costs and increase reuse. A product line architecture is a common framework that standardizes components and maximizes reuse potential. It specifies common functionality and identifies variation points across related products. Variability management is important for providing flexibility without compromising commonality.
6 - Architetture Software - Model transformationMajong DevJfu
This document discusses model transformations in Model-Driven Architecture (MDA). It defines computation independent models (CIMs), platform independent models (PIMs), and platform specific models (PSMs). It explains that model transformations are used to map between these different abstraction levels and ensure consistency. It also discusses model mappings, approaches to transformations, and tools like EMF and ATL that support transformations in Eclipse.
5 - Architetture Software - Metamodelling and the Model Driven ArchitectureMajong DevJfu
The document discusses metamodeling and the Model Driven Architecture (MDA). It covers topics such as model driven engineering, metamodeling, metamodeling in UML, and the OMG technologies that support MDA. Metamodeling involves modeling modeling elements and their relationships. Metamodels define the structure of models, while models are instances that conform to metamodels. The MDA uses metamodels and models to develop and transform systems.
This document provides an overview of software architectures by presenting examples of architectures from various software systems. It begins with an introduction to software architecture and what it entails. It then shows numerous diagrams and visualizations of architectures for different types of systems, such as editors, compilers, operating systems, middleware, and web applications. These examples are intended to demonstrate common architectural patterns and styles. The document discusses analyzing and comparing the architectures visually and recognizing patterns within them.
The document discusses architectural styles and decomposition techniques for software systems. It describes layering and tiering as basic decomposition approaches, with layers representing different levels of abstraction and tiers representing peer modules within the same layer. Several common architectural styles are then introduced, including pipes and filters, repository, client/server, model-view-controller, service-oriented, and peer-to-peer. Closed and open layered architectures are contrasted, and examples of layered systems like virtual machines and the OSI model are provided. Finally, the document notes that complete decompositions often involve both layering and partitioning techniques.
The document discusses key concepts in software architecture, including:
1) Software architecture establishes the overall structure and organization of a system, including its components and relationships.
2) Architectural design involves decomposing a system into subsystems or modules to improve modifiability, reusability, and portability.
3) Key principles for architectural design include simplicity, modularity, low coupling, separation of concerns, abstraction, and postponing decisions.
10 - Architetture Software - More architectural stylesMajong DevJfu
The Microkernel pattern partitions an operating system into isolated, minimal components that communicate through a small, fixed message-passing interface, allowing components to be developed and upgraded independently while maintaining overall system stability and security.
The document discusses architectural UML and provides information on:
1) The elements of a software architecture including views, models, and diagrams.
2) How UML can be used to represent different architectural views including design, process, development, and physical views.
3) An example of using UML models and diagrams to represent different views of a chess game architecture.
UML allows for extending diagrams and modeling elements through three main techniques:
1. Stereotypes allow applying tags to existing modeling elements like classes, associations, etc. to add domain-specific meaning.
2. Profiles extend UML with new modeling elements tailored for specific domains or platforms.
3. Extension mechanisms allow precisely defining new constructs that integrate with the UML metamodel. Together these techniques make UML extensible for multiple domains.
The document discusses metamodeling and the Model Driven Architecture (MDA). It provides an overview of model driven engineering and metamodeling. Specifically, it discusses how metamodels define the structure of models through concepts like classes and relationships. The Model Driven Architecture uses metamodels and modeling to develop software systems from models.
Here are the key differences between objects and classes in UML:
- Classes define the general characteristics (attributes and operations) that objects of that class will have. Objects are specific instances of a class.
- Classes are static definitions, while objects are dynamic instances of classes that exist at run time.
- In class diagrams, classes are represented as boxes containing the attributes and operations. Objects are represented as boxes with the class name followed by a colon and the object name (e.g. Person:John).
- Classes define the common properties for a set of objects, while each object is a unique instance of a class with its own identity and particular values for attributes.
- Classes are abstractions,
The document discusses architectural styles and decomposition techniques. It describes layers as hierarchical sets of subsystems that provide related services by utilizing underlying layers. Tiers partition a system into peer subsystems responsible for classes of services. Common architectural styles include pipes and filters, repository, client/server, model-view-controller, service-oriented, and peer-to-peer. Layers and tiers are often combined for complete decomposition, with subsystems divided into tiers and each tier organized into layers. The pipe and filter style focuses on dynamic interaction by processing data streams through filters connected by pipes.
- Reference architectures that provide templates for common system types
- Design patterns that capture successful solutions to recurring problems
- Architectural patterns that describe best practices for system organization
- Legacy applications that can be analyzed for reusable architectural elements
This document discusses software as a product and the software industry. It covers topics such as why software is important, emerging technologies according to Gartner's hype cycle from 2005-2010, software being an industrial product, the size of the worldwide software industry, different types of software including embedded software and software as a service. It also discusses software components, software architecture and engineering issues, producing software is difficult due to complexity, low productivity in the industry, the software development process, different process models, lifecycle differences around the world, development activities, process models, and software standards.
This short document contains 5 headings but provides no other details or context. It lists the headings "My Heading Here First Second Third Fourth Fifth" but does not elaborate on or explain these headings.
This document provides an overview of various types of architectural standards including conceptual standards like IEEE 1471 and DoDAF that define viewpoints and views, notational standards like UML and SysML, and process standards like TOGAF and RUP. It discusses the benefits of standards in promoting interoperability and network effects while also noting drawbacks like limiting flexibility. The document advises deciding when to adopt a standard based on whether in the early or late phase of a project.
The document discusses architectural adaptation and software evolution. It characterizes different types of changes that can occur, including corrective changes, new features, and changes to the operating environment. It also describes different levels at which changes can be made, from the component interior to the overall system configuration. Effective adaptation requires techniques like explicit architectural models, adaptable connectors, and message-based communication. The roles of change agents, strategic and tactical planning, and quiescence are also outlined.
2. Database Esami
Il Database Esami rappresenta la situazione di Studenti,
Corsi, Docenti ed Esami:
S
S (Matr, SNome, Citta, ACorso)
Matr SNome Citta Acorso
C (CC, CNome, CD)
FK: CD REFERENCES D E
Matr CC Data Voto
D (CD, CNome, Citta)
E (Matr, CC, Data, Voto) C
CC CNome CD
FK: Matr REFERENCES S
FK: CC REFERENCES C D
CD CNome Citta
2 Esercizi di interrogazioni in SQL
4. Database Esami – interrogazioni semplici
Esami con voto compreso tra 24 e 28
SELECT *
FROM E
WHERE Voto >= 24
AND Voto <= 28
SELECT *
FROM E
WHERE Voto BETWEEN 24 AND 28
4 Esercizi di interrogazioni in SQL
7. Database Esami – interrogazioni semplici
Per ogni esame con voto superiore a 24 riportare il nome dello
studente e il codice del docente del corso
SELECT S.SNome, C.CD
FROM S,E,C
WHERE S.Matr=E.Matr
AND E.CC=C.CC
AND Voto > 24
7 Esercizi di interrogazioni in SQL
8. Database Esami – interrogazioni semplici
Coppie di studenti residenti nella stessa città
SELECT S1.Matr,S2.Matr
FROM S S1, S S2
WHERE S1.Citta = S2.Citta
AND S1.Matr < S2.Matr
8 Esercizi di interrogazioni in SQL
9. Database Esami – interrogazioni semplici
Matricole degli studenti che hanno sostenuto almeno uno
degli esami sostenuti dallo studente di nome 'PAOLA'
SELECT E1.Matr
FROM S, E E1, E E2
WHERE E2.Matr = S.Matr
AND E1.CC = E2.CC
AND S.SNome= 'PAOLA'
9 Esercizi di interrogazioni in SQL
10. Videonoleggio DVD
Si supponga di voler costruire un database per la gestione dei
noleggi di DVD di un negozio. Tale database, in una versione del
tutto semplicistica ed irreale, potrebbe essere rappresentato dalle
tabelle clienti, dvd e noleggi:
tabella clienti, relativa ai clienti del videonoleggio e contenente
informazioni quali il numero di tessera, il nome, il cognome (tutti
obbligatori) ed il numero di telefono.
tabella dvd, relativa ai dvd in possesso del videonoleggio (si assuma per
semplicità che le copie di ogni dvd siano illimitate, e che quindi più
clienti possano prendere a noleggio copie diverse di uno stesso dvd
contemporaneamente). Per ogni dvd la tabella tiene traccia del codice
(obbligatorio), del titolo, del regista, del voto della critica (da 1 a 10) e
della trama.
tabella noleggi, relativa ai noleggi di dvd in atto in quel momento. In
particolare, la tabella tiene traccia del codice del dvd noleggiato, del
numero di tessera del cliente che sta effettuando il noleggio e della data
in cui il cliente ha iniziato il noleggio.
10 Esercizi di interrogazioni in SQL
12. Videonoleggio DVD
CREATE TABLE CLIENTI (
TESSERA CHAR(5) NOT NULL,
NOME VARCHAR(60) NOT NULL,
COGNOME VARCHAR(60) NOT NULL,
TELEFONO VARCHAR(20),
PRIMARY KEY (TESSERA)
);
CREATE TABLE DVD (
CODICE CHAR(5) NOT NULL,
TITOLO VARCHAR(60),
REGISTA VARCHAR(60),
VOTO INT CHECK (VOTO BETWEEN 1 AND 10),
TRAMA VARCHAR(200),
PRIMARY KEY (CODICE)
);
12 Esercizi di interrogazioni in SQL
13. Videonoleggio DVD
CREATE TABLE NOLEGGI (
CODICE_DVD CHAR(5) NOT NULL REFERENCES DVD(CODICE),
TESSERA CHAR(5) NOT NULL REFERENCES CLIENTI(TESSERA),
DATA_NOLEGGIO DATE,
PRIMARY KEY (CODICE_DVD,TESSERA)
);
13 Esercizi di interrogazioni in SQL
14. Videonoleggio DVD
Popolare le tabelle create seguendo la traccia indicata di
seguito:
Provare ad inserire almeno un record “non valido” (che va
contro la definizione del vincolo espresso in fase di definizione
della tabella) per i vincoli di ciascuna tabella
Inserire alcuni record “validi” e consistenti per ogni tabella
(prevedendo anche la possibilità di valori nulli)
Aggiornare, aumentando di 3 unità il voto, il record della
tabella DVD relativo al codice ‘12345’
14 Esercizi di interrogazioni in SQL
15. Videonoleggio DVD
INSERT INTO CLIENTI
VALUES (‘00001’,’Carlo’, ‘Rossi’, ‘+390596606633’)
...
INSERT INTO DVD
VALUES (‘00001’,‘Braveheart’,‘M.Gibson’,8, ‘William Wallace
unites the 13th Century Scots in their battle to overthrow
English rule’)
...
UPDATE DVD
SET VOTO = VOTO + 3
WHERE CODICE = ‘12345’
15 Esercizi di interrogazioni in SQL
16. Videonoleggio DVD
Formulare le seguenti interrogazioni:
“Elenco dei DVD (distinti) che hanno un voto maggiore di 5”
“Telefono dei clienti di nome ‘Carlo’”
“Codici DVD noleggiati da clienti con tessere (‘00001’, ‘00002’,
‘00003’, ‘00004’)”
16 Esercizi di interrogazioni in SQL
17. Videonoleggio DVD
SELECT CODICE
FROM DVD
WHERE VOTO>5
SELECT TELEFONO
FROM CLIENTI
WHERE NOME=‘Carlo’
SELECT CODICE_DVD
FROM NOLEGGI
WHERE TESSERA IN (‘00001’,‘000002’,‘000003’,‘000004’)
17 Esercizi di interrogazioni in SQL