Professional Documents
Culture Documents
Relatore: Candidato:
Prof.ssa Ing. Marina Mongiello Marco Vanadia
Matricola 509591
Correlatore:
Dott. Ing. Francesco Nocera
Marco Vanada,
Bari, 28 marzo 2017
Dedicato a Giulia.
Nessun calcolatore 9000 ha mai commesso un errore o alterato uninformazione.
Noi siamo, senza possibili eccezioni di sorta, a prova di errore, incapaci di sbagliare.
elaboratore Hal 9000
2001: A Space Odyssey
Stanley Kubrick, 1968
,
So di non sapere
Socrate
INDICE
prologo xvii
vii
viii indice
ii appendici 149
esa space engineering 151
bibliografia 157
ELENCO DELLE FIGURE
ix
E L E N C O D E L L E TA B E L L E
xi
SOMMARIO
ABSTRACT
xiii
Homo faber fortunae suae
(loc. latina)1
Il filosofo artefice del proprio destino.
visione delluomo di Giordano Bruno
RINGRAZIAMENTI
Ringrazio la mia famiglia senza il cui sostegno non sarei mai potuto
arrivare a concludere questo lungo percorso.
1 rielaborazione di Faber est suae quisque fortunae, Epistulae ad Caesarem senem de re pubblica
(De rep., 1, 1, 2) attribuita nellopera di Sallustio al console Appio Claudio Cieco
xv
PROLOGO
Il mio progetto di Tesi ispirato dalla curiosit umana, dal piacere del-
la scoperta e dal desiderio di mettere in campo tutta la passione per la
scienza e la tecnologia e applicare le conoscenze acquisite di ingegnere
informatico ad un caso di business reale e poter dare il mio contributo a
spingere oltre la frontiera.
Le attivit dellAgenzia Spaziale Europea, organizzazione internazio-
nale fondata nel 1975 per lo sviluppo dei progetti spaziali di 22 Stati Mem-
bri, hanno ricadute nelle nostre vite: dalle previsioni meteo alle comuni-
cazioni cellulari e satellitari, ai sistemi di posizionamento e navigazione
delle flotte, allosservazione della terra, al supporto allagricoltura, alla
sperimentazione scientifica nei materiali e scienze della vita.
Il nostro futuro dipende dalla gestione oculata delle risorse del nostro
pianeta e capire le interazioni complesse dellintera ecosfera richiede una
prospettiva globale che solo lo spazio pu dare. Le nostre conoscenze
sul cambiamento climatico, limpatto delle attivit umane nellatmosfera,
come il buco nello strato di ozono, sono possibili solo da misure effettuate
dallo spazio. I satelliti meteo da soli fanno risparmiare centinaia di milioni
xvii
xviii prologo
Marco Vanada
prologo xix
P R O C E S S O U N I F I C ATO
Caso di Studio
Sviluppo Software
oevolu rat
ivoevo
iv
tiv lu
olutivoite
ti v
o it e r a t
oi oi
te te
ra r
ev t
iv
oe
vo
lutiv
ol lu
oev
ut tiv
iv oit
o
o e r a ti v
ev
iter o
a ti v
P R O C E S S O U N I F I C ATO
ideazione
Iterazione iniziale in cui viene eseguita una indagine del caso di stu-
dio al fine di stabilire la portata del progetto e una visione gene-
rale con una analisi dei casi duso e requisiti funzionali pi critici,
per elaborare delle stime approssimative dello sforzo e determinare
la fattibilit economica e sostenere la decisione di proseguire con il
progetto.
elaborazione
Ad ogni iterazione lanalisi dei requisiti viene approfondita, la mag-
gior parte viene scoperta e stabilizzata; vengono raffinati gli scenari
duso partendo da quelli pi importanti; si esegue lanalisi orientata
agli oggetti modellando il dominio informativo, ovvero le informa-
zioni e le relazioni che devono essere gestite dal software, e si de-
finisce il modello di interazione con le sequenze di operazioni del
sistema, e loro contratti, e le comunicazioni tra oggetti; la proget-
tazione, limplementazione e i test con codice di qualit a livello di
xxv
xxvi processo unificato
Modellazione di business
Requisiti
Progettazione
Implementazione
Test
Rilascio
Gestione delle Confi-
gurazioni e Modifiche
Gestione del progetto
Infrastruttura
1.2 Requisiti
1.3 Progettazione
1.4 Implementazione
1.5 Test
1.6 Rilascio
1.8 Infrastruttura
Released
10/02/2017 10:00 am
Description
Part of the Italian island of Sicily is pictured in this false-colour image from the Sentinel-2A satellite.
This image was captured on 8 January during a period of unusual cold and snowfall across parts of southern Europe. As
a consequence the mountains of Sicily are visible in white across the northern part of the island. While Italys northern
regions experienced little snowfall this winter, the central and southern areas have seen abnormally cold conditions
and snowfall in mountainous areas.
Mount Etna, an active volcano, is visible at upper right. Positioned over the zone where the African plate collides with
and slips under the Eurasian plate, Etnas frequent eruptions are often accompanied by large lava flows, smoke and
ash.
Sentinel-2 provides optical data for land and vegetation monitoring. Its main instrument has 13 spectral bands, and
this false-colour image was processed including the near-infrared channel which explains why vegetation appears
red.
The varying shades of red and other colours across the entire image indicate how sensitive the instrument is to
differences in chlorophyll content. This is used to provide key information on plant health; brighter reds indicate
healthier vegetation.
Sentinel-2 is a two-satellite mission for Europes Copernicus programme. While the first satellite was launched in June
2015, its Sentinel-2B twin is set for launch from French Guiana on 7 March 2017 at 01:49 GMT.
This image is featured on the Earth from Space video programme.
Source
http://www.esa.int/spaceinimages/Images/2017/02/Sicilian_snow
1 VISIONE
Cronologia revisioni
Iterazione Descrizione
I.1 Ideazione elaborato Visione, opportunit e concorrenza
1.1 introduzione
Si vuole realizzare un sistema informativo software per la gestione di
progetti dellindustria aerospaziale, a supporto dei processi di garanzia di
qualit e tracciamento delle non conformit, secondo gli standard dellESA/
ECSS.
3
4 visione
5.5.2 Documentation
Nonconformance database
1.4 concorrenza
Sul mercato sono disponibili numerosi sistemi software di project ma-
nagement che offrono strumenti di comunicazione e collaborazione per la
gestione documentale, organizzazione del lavoro e attivit, gestione dei
workflow e processi di business, sistemi di issue/bug tracking. Fra que-
sti solo uno, a nostra conoscenza, specificatamente progettato tenendo
conto dei requisiti ECSS per lindustria aerospaziale: Nonconformance
Tracking System (NCTS) di Sapienza Consulting.
Lapplicazione web rilasciata per la prima volta nel 2005, ha supporta-
to 29 progetti ESA e pi di 5.000 utenti nella registrazione, segnalazione
e revisione di pi di 20.000 non conformit di prodotto1 . NCTS stato
supportato e promosso dallESA come strumento principale per limple-
mentazione dei processi di gestione delle non conformit secondo gli stan-
dard rilevanti dellECSS, in particolare i requisiti specificati nello standard
ECSS-Q-ST-10-09C Nonconformance control system.
Nel 2009 Sapienza ha integrato e aggiornato il tool software basato sugli
standard ECSS per ottenere una suite di applicazioni software modulare
nominata Eclipse[Ben+10] per il Project Management (PM), Product As-
surance (PA) e Quality Assurance (QA). Larchitettura a layer implemen-
ta i processi di business in moduli applicativi dedicati e le funzioni di
supporto in un layer di servizi di base (tab. 2).
Problema Lo scambio dei dati affidabile ed efficiente tra sistemi informativi ri-
chiede interfacce comuni tra le diverse parti coinvolte. Per contro pra-
ticamente impossibile standardizzare gli strumenti di gestione e archivio
delle basi dati dellintera industria aerospaziale, per i diversi obiettivi di
business tra clienti e fornitori, lesistenza di sistemi legacy e per limpatto
dei costi e dei tempi di sviluppo di applicazioni software.
Non desiderabile standardizzare gli strumenti perch il mercato li-
bero promuove linnovazione e la competizione sana tra gli sviluppato-
ri di soluzioni, di cui beneficiano tutti gli utilizzatori e lintero settore
industriale.
Inoltre non possibile richiedere ai subappaltatori e i fornitori di basso
livello ladozione e lutilizzo del completo set di strumenti di gestione
dei processi utilizzati dai loro clienti e i primi appaltatori. Acquisire e
mantenere le conoscenze necessarie per lutilizzo di ogni strumento spesso
implica costi proibitivi di licenza e di formazione, in particolare per le
piccole e medie imprese.
Soluzione La standardizzazione dello scambio dei dati deve essere ottenuta al li-
vello semantico. Per garantire che standardizzazione abbia successo sul
lungo periodo in un mondo tecnologico in rapida evoluzione necessario
definirne una implementazione indipendente da ogni specifica tecnologia,
come ad esempio formato dei file XML/XSD, API o protocolli basati su
Web Services.
Linteroperabilit semantica consente di superare il concetto di reposi-
tory unico contenente tutti i dati del sistema spaziale in un database mo-
nolitico e centralizzato, ma piuttosto di ottenere la federazione di basi di
dati disperse geograficamente e temporalmente ma logicamente integrate
in un modo che lo scambio di dati sia possibile ed affidabile. I dati non
vengono duplicati ma linformazione distribuita e i riferimenti ad oggetti
esterni sono persistenti.
Attore Obiettivo
Account Gestire account utenti e societ
Manager Gestire campi custom
Project Gestire i progetti
Manager Assegnare membri ai progetti
Gestire e assegnare ruoli e permessi
Gestire il repository e workflow documenti
Ricevere notifiche di operazioni richieste/concluse
Action Item Gestire, assegnare, revisionare Action Item
Manager Ricevere notifiche di operazioni richieste/concluse
Configuration Gestire il ciclo di vita del prodotto
Manager Gestire configurazioni di elementi, parti, manufatti
Generare baseline di prodotto
Ricevere notifiche di operazioni richieste/concluse
Quality Gestire e ispezionare manufatti
Assurance Gestire rapporti di ispezione
Member Gestire rapporti di non conformit
Convocare consigli di revisione di non conformit
(NRB)
Assegnare le azioni correttive e preventive
Registrare le disposizioni del NRB
Ricevere notifiche di operazioni richieste/concluse
Project Member Autenticare identit
Gestire il proprio account utente personale
Ottenere accesso alle informazioni in base al ruolo
Ricevere notifiche di operazioni richieste/assegnate
Operare sugli Action Item assegnati
Pianificare e gestire verbali riunioni
Visualizzare, gestire, revisionare, firmare documenti
Accedere alla struttura gerarchica a pi livelli del
prodotto
Gestire la documentazione di progetto di parti del
prodotto
Generare la distinta base di parti assemblate
Visualizzare i rapporti di ispezione e non conformit
1.6 stima dello sforzo di sviluppo (modello cocomo ii) 11
Released
10/02/2017 10:00 am
Description
Koreas Kompsat-2 satellite captured this image over the sand seas of the Namib Desert on 7 January 2012. The blue
and white area is the dry river bed of the Tsauchab. Black dots of vegetation are concentrated close to the rivers
main route, while salt deposits appear bright white. Running through the river valley, a road connects Sossusvlei to
the Sesriem settlement. At the roads 45th kilometre, seen at the lower-central part of the image, a white path shoots
off and ends at a circular parking area at the base of a dune. This is Dune 45, a popular tourist stop on the way to
and from Sossusvlei. In this image, there appears to be some shadow on the western side. From this we can deduce
that the image was acquired during the late morning.
ESA supports Kompsat as a Third Party Mission, meaning it uses its ground infrastructure and expertise to acquire,
process and distribute data to users.
This image is featured on the Earth from Space video programme.
Source
http://www.esa.int/spaceinimages/Images/2013/04/Namib_Desert
2 REGOLE DI DOMINIO
Cronologia revisioni
Iterazione Descrizione
I.1 Studio degli standard ECSS
E.1 Raccolta e selezione regole di dominio da standard ECSS
15
16 regole di dominio
ECSS-<X>-<Tipo>-<Numero><Versione>
dove X rappresenta la branca (P, M, Q), il tipo (ST, HB, TM), il numero
una o due coppie di cifre, la versione una lettera da A a seguire.
Source
http://www.spacetelescope.org/news/heic1509/
3 GLOSSARIO
Cronologia revisioni
Iterazione Descrizione
I.1 Definizione termini e abbreviazioni da standard ECSS
E.1 Raffinamento termini e definizione dizionario dati
3.1 termini
Termini generali standard ECSS-S-ST-00-01C Glossary of terms
assembly
<act> physically combining parts, components, equipment or seg-
ment elements to form a larger entity
business agreement
legally binding agreement, for the supply of goods or services, be-
tween two or more actors in the customersupplier chain
NOTE Business agreements are recorded in a variety of forms, such
as:
Contracts,
Memoranda of understanding,
27
28 glossario
Inter-governmental agreements,
Inter-agency agreements,
Partnerships,
Bartering agreements, and
Purchase orders.
conformance
fulfilment of a requirement
customer
organization or person that receives a product as part of a business
agreement
NOTE A customer can be internal or external to the supplier organi-
zation.
defect
non-fulfilment of a requirement related to an intended or specified
use
NOTE 1 The distinction between the concepts defect and nonconfor-
mance is important as it has legal connotations, particularly those
associated with product liability issues. Consequently the term de-
fect should be used with extreme caution.
NOTE 2 The intended use as intended by the customer can be af-
fected by the nature of the information, such as operating or mainte-
nance instructions, provided by the supplier.
dependability
the extent to which the fulfilment of a required function can be justi-
fiably trusted
NOTE 1 Its main components are reliability, availability and main-
tainability.
NOTE 2 Dependability shall be considered in conjunction with safety.
design
<result> set of information that defines the characteristics of a prod-
uct
design
<activity> process used to generate the set of information defining
the characteristics of a product
NOTE The design is completed at CDR closure
deviation
formal authorization to depart from the originally specified require-
ments for a product, prior to its production
NOTE Waiver is an a posteriori decision whereas deviation is an a
priori decision with respect to the production phase.
3.1 termini 29
failure
the event resulting in an item being no longer able to perform its
required function
NOTE "Failure" is an event, as distinguished from "fault" which is a
state.
function
intended effect of a product
normative
providing requirements for activities or their results
NOTE 1 A normative document covers documents such as stan-
dards, technical specifications, codes of practice and regulations.
NOTE 2 A normative reference" incorporates requirements from a
cited publication into a normative document.
performance
quantifiable characteristics of a function
procedure
documented way to carry out an activity or process in a controlled
manner
process
set of interrelated or interacting activities which transform inputs
into outputs
NOTE Inputs to a process are generally outputs of other processes.
product
result of a process
NOTE 1 There are four generic product categories:
services
software
hardware
processed materials.
NOTE 2 Adapted from ISO 9000:2005.
product tree
hierarchical breakdown of a product into successive levels of product
project
set of coordinated and controlled activities with start and finish dates,
undertaken to achieve an objective conforming to specific require-
ments, including constraints of time, cost and resources
quality
degree to which a set of characteristics of a product or process fulfils
requirements
30 glossario
requirement
documented demand to be complied with
supplier
organization or person that provides a product as part of a business
agreement
NOTE A supplier can be internal or external to the customer organi-
zation.
tailoring
process by which standards are made applicable to a specific project
by selection of existing requirements, with or without modification,
or addition of new ones
test
measurement of product characteristics, performance or functions
under representative environments
validation
process which demonstrates that the product is able to accomplish
its intended use in the intended operational environment
NOTE 1 The status of the product following validation is validated.
NOTE 2 Verification is a pre-requisite for validation.
verification
process which demonstrates through the provision of objective ev-
idence that the product is designed and produced according to its
specifications and the agreed deviations and waivers, and is free of
defects
NOTE 1 A waiver can arise as an output of the verification process.
NOTE 2 Verification can be accomplished by one or more of the
following methods: analysis (including similarity), test, inspection,
review of design.
NOTE 3 The status of the product following verification is verified.
waiver
formal authorization to accept products which during production,
or after having been submitted to inspection or tests, are found to
depart from specified requirements
NOTE 1 Deviation is an a priori decision whereas waiver is an a
posteriori decision with respect to the production phase.
NOTE 2 The term concession is synonymous and may be used for
materials as per Q-ST-70C.
alert
formal notification to users, informing them of failure or nonconfor-
mance of items, already released for use or not, which could also be
present on other items already delivered [e.g. items with identical
design concept, materials, components or processes]
NOTE An alert can also be raised when a deficiency in the specified
requirements, which can affect the fitness for purpose in the defined
application, has been identified.
corrective action
action to eliminate the cause of a detected nonconformance, or other
undesirable situation
NOTE 1 There can be more than one cause for a non-conformance.
NOTE 2 Corrective action is taken to prevent recurrence whereas
preventive action is taken to prevent occurrence.
critical item
potential threat to the schedule, cost, performance and quality of a
project or programme that is controlled by a specific action plan in
order to mitigate emanating risks and to prevent undesirable conse-
quences
NOTE Examples of critical items are:
item not qualified or validated for the application in question
(or has caused problems previously which remained unresolved).
item for which it is difficult to demonstrate design performance.
item highly sensitive to the conditions under which it is pro-
duced or used (e.g. contamination, radiation).
item having the potential to degrade the quality of the product
significantly, and hence the ability of the end-product to accom-
plish defined mission objectives.
item for which major difficulties or uncertainties are expected
in the procurement, manufacturing, assembly, inspection, test,
handling, storage and transportation, that have the potential to
lead to a major degradation in the quality of the product
inspection
conformance evaluation by observation and judgement accompanied
as appropriate by measurement, testing or gauging
[ISO 9000:2005]
major nonconformances
nonconformances which can have an impact on the customers re-
quirements in the following areas and cases:
32 glossario
minor nonconformances
nonconformances which by definition cannot be classified as major
NOTE For example, the following EEE discrepancies after deliv-
ery from the manufacturer can be classified as minor:
random failures, where no risk for a lot-related reliability or qual-
ity problem exists;
if the form, fit or function are not affected;
minor inconsistencies in the accompanying documentation.
nonconformance
non-fulfilment of a requirement
NOTE The term nonconformity is synonymous but deprecated.
preventive action
action to eliminate the cause of a potential nonconformance or other
undesirable potential situation
NOTE 1 There can be more than one cause for a potential non-
conformance.
NOTE 2 Preventive action is taken to prevent occurrence whereas
corrective action is taken to prevent recurrence.
repair
action to correct a defect of a product that leads to a configuration
item change
NOTE 1 Unlike rework, repair affects or modifies parts of the defec-
tive product.
NOTE 2 An NCR needs to be raised for the CI change.
rework
action to correct a defect of a product that does not lead to a config-
uration item change
NOTE 1 Unlike repair, rework does not affect or modify parts of the
defective product.
NOTE 2 No NCR needs to be raised.
3.1 termini 33
acceptance
<process> that part of the verification process which demonstrates
that the product meets specified acceptance margins
approval
formal agreement by a designated management official to use or ap-
ply an item or proceed with a proposed course of action
NOTE 1 Approvals must be documented.
NOTE 2 Approval implies that the approving authority has verified
that the item conforms to its requirements.
audit
systematic, independent and documented process for obtaining au-
dit evidence and evaluating it objectively to determine the extent to
which audit criteria are fulfilled
NOTE 1 Internal audits, sometimes called first-party audits, are con-
ducted by, or on behalf of, the organization itself for management
review and other internal purposes, and may form the basis for an
organizations declaration of conformity. In many cases, particularly
in smaller organizations, independence can be demonstrated by the
freedom from responsibility for the activity being audited.
NOTE 2 External audits include those generally termed second- and
third-party audits. Second-party audits are conducted by parties hav-
ing an interest in the organization, such as customers, or by other
persons on their behalf. Third-party audits are conducted by ex-
ternal, independent auditing organizations, such as those providing
certification/registration of conformity to ISO 9001 or ISO 14001.
NOTE 3 When quality and environmental management systems are
audited together, this is termed combined audit.
NOTE 4 When two or more auditing organizations cooperate to au-
dit a single auditee jointly, this is termed joint audit.
[ISO 9000:2005]
product assurance
discipline devoted to the study, planning and implementation of ac-
tivities intended to assure that the design, controls, methods and
techniques in a project result in a satisfactory degree of quality in a
product
qualification
that part of verification which demonstrates that the product meets
specified qualification margins
NOTE This can apply to personnel, products, manufacturing and
assembly processes.
34 glossario
quality assurance
part of quality management focused on providing confidence that
quality requirements will be fulfilled
[ISO 9000:2005]
review
activity undertaken to determine the suitability, adequacy and effec-
tiveness of the subject matter to achieve established objectives
NOTE 1 Review can also include the determination of efficiency.
NOTE 2 Examples are: management review, design and develop-
ment review, review of customer requirements and nonconformity
review.
[ISO 9000:2005]
risk
undesirable situation or circumstance that has both a likelihood of
occurring and a potential negative consequence on a project
NOTE 1 Risks are inherent to any project, and can arise at any time
during the project life cycle.
NOTE 2 Predictability and control of events facilitate risk reduction.
NOTE 3 The terms risk assessment, risk mitigation and risk
control are in common use in ECSS.
NOTE 4 Adapted from ISO 17666:2003.
safety
state where an acceptable level of risk is not exceeded
NOTE Risk relates to:
fatality,
injury or occupational illness,
damage to launcher hardware or launch site facilities,
damage to an element of an interfacing manned flight system,
the main functions of a flight system itself,
pollution of the environment, atmosphere or outer space, and
damage to public or private property.
traceability
ability to track the history, location or application by means of docu-
mented records
NOTE When considering a product, traceability can relate to:
the origin of materials and parts,
the processing history, or
the distribution and location of the product after delivery.
3.1 termini 35
inspectability
ability of an item of being inspected
producibility
ability of an item of being producible
testability
ability of an item of being tested
consumer
body specifying a project or (product) through a high level require-
ment document (such as mission statement or SFS and STS) and pro-
viding the necessary financial resources for its realization.
review authority
body appointed by the consumer organization, having the mandate to is-
sue recommendations to the customer and issue decisions relating to the re-
view process
NOTE This is also referred to as the review board.
review item discrepancy (rid)
issue, identified by a reviewer, that is not compliant with a require-
ment, a review objective or a design goal
review prerequisite
conditions necessary to be fulfilled prior to the start of the review
review team
body appointed by the review authority, having the mandate to eval-
uate the status of the project under review
review team leader
person responsible for the review team activities and issuing the re-
view team report
discipline
specific area of expertise within a general subject
NOTE The name of the discipline normally indicates the type of ex-
pertise (e.g. in the ECSS System, system engineering, mechanical en-
gineering, software and communications are disciplines within the
Engineering domain)
configuration
interrelated functional and/or physical characteristics of a product
defined in configuration documents subject to configuration manage-
ment
NOTE Adapted from ISO 10007:2003.
3.1 termini 37
configuration baseline
approved status of requirements and design of a product at a project
key milestone that serves as a reference for activities throughout the
life cycle of the product
NOTE Adapted from ISO 10007:2003.
configuration control
coordinated activities for controlling modifications to a configuration
baseline
NOTE Requests for deviation are also considered modifications to a
baseline.
configuration document
document that defines the requirements for function, design, build,
production, and verification for a configuration item
NOTE For space standards, configuration documents can include
documents relating to operation and disposal of the configuration
item.
configuration identification
coordinated activities to establish rules for configuration item selec-
tion, configuration baseline content definition, and product and doc-
ument identifiers definition
configuration item
aggregation of hardware, software, processed materials, services or
any of its discrete portions, that is designated for configuration man-
agement and treated as a single entity in the configuration manage-
ment process
NOTE A configuration item can contain other configuration item(s).
configuration management
activity for establishing and maintaining consistent records of the
performance parameters of a product and its functional and physical
attributes compared to product design and operational requirements
NOTE 1 Configuration management is applied throughout the entire
life cycle of the product (i.e. development, production, deployment,
operation and disposal).
NOTE 2 Adapted from ISO 10007:2003.
change control
activity for control of changes or departures to the product after for-
mal approval of its configuration baseline
NOTE Adapted from ISO 10007.
information/documentation management
process for ensuring timely and effective creation, collection, review, de-
livery, storage, and archiving of project information
38 glossario
information system
set of resources, procedures and data required in support of project
management processes
metadata
metadata are structured, encoded data that describe characteristics of in-
formation bearing entities to aid in the identification, discovery, as-
sessment, and management of the described entities
NOTE Adapted from Committee on Cataloguing Task Force on
metadata Summary Report.
product item
element of the product tree having a unique identifier
self-signed certificate
certificate auto-generated by the signer
emits code
Codice univoco rilasciato dallESA per imprese dellindustria aero-
spaziale registrate nel database EMITS2
[a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[a-b8-9][a-f0-9]{3}-[a-f0-9]{12}
Source
http://www.spacetelescope.org/news/heic1509/
4 MODELLO DEI CASI DUSO
Cronologia revisioni
Iterazione Descrizione
I.1 Raccolta casi duso nel primo workshop dei requisiti in fase
di ideazione
E.1 Prima iterazione di elaborazione, dettaglio dei casi duso
principali
E.2 Seconda iterazione di elaborazione, dettaglio di ulteriori
casi duso
Lelaborato Modello dei Casi duso, nellambito della disciplina dei re-
quisiti, raccoglie in forma scritta i casi duso che descrivono come possa es-
sere utilizzato il sistema per soddisfare gli obiettivi dei suoi utenti. Questo
lapproccio sistematico principale definito nel processo unificato per indi-
viduare, documentare e tracciare i requisiti funzionali e comportamentali
del sistema che si vuole sviluppare.
Un caso duso raccoglie scenari di utilizzo correlati tra loro dal soddi-
sfacimento di un obiettivo specifico per un attore che interagisce con il
sistema. Ogni scenario un particolare percorso duso di successo o insuc-
cesso descritto da una sequenza di interazioni tra il sistema e uno o pi
attori. Secondo le linee guida sono scritti in modo conciso e completo e
in stile essenziale evitando i dettagli di interazione con linterfaccia uten-
te e concentrandosi sullo scopo reale dellutente e sulle responsabilit del
sistema.
45
46 modello dei casi duso
Account Management
Account Management
UC4: Manage
Personal Information
Project Member
include
UC3: Manage
Custom Information
Account Manager
include
Estensioni:
Estensioni:
Estensioni:
Problemi aperti:
Estensioni:
Project Management
Project Management
UC6: Manage
Repository
UC7: Mana-
include ge Project
Members
include
UC5: Manage Project
include
include UC8: Manage
Roles and
Project Manager
Permissions
UC9: Manage
Reference
Paradigm
UC11: Work on
Action Item
Project Member
Assign
Action Item
include
UC10: Manage
Action Item
Action Item Manager include
Review
Action Item
Meeting Management
Meeting Management
Edit Minutes
of Meeting
UC10: Manage
Action Item
include
include
Request Review
UC12: Manage include of Meeting
Meeting
Project Member include
UC13: Review
include Minutes of
Meeting
Close Meeting
Review
3e. LAction Item Manager dispone lelenco degli Action Items associa-
ti al meeting eseguendo UC10: Manage Action Item. Di default
lautore sar lassigner dellAI.
Requisiti speciali:
Document Management
Document Management
View Document
Create Document
include
include Modify
Document
include
UC14: Manage
Document Request
include
Document
Project Member Review
include
include
UC15: Review
Release Document
Document
include
UC16: Apply
Digital Sign
UC6: Manage
Repository
Requisiti speciali:
Configuration Management
Configuration Management
Generate
Product
Baseline
include
UC19: Manage
Part and Assembly
include
UC17: Navigate
Product Tree
Project Member
include
include
UC18: Manage
Configuration
Item
Configuration Manager
UC20: Manage
Manufactured
Part
QA Member
View Inspection
Report
UC10: Manage
Project Member Action Item
include
UC17: Navigate
Product Tree include
include
UC21: Manage
Inspection Report
QA Member include
include
UC22: Close
Inspection Report
UC23: Manage Non
Conformance
Report
View Non
Conformance
Report
Project Member
UC12: Manage
Meeting
Release NCR
UC24: Review Non
Conformance Report
Figura 12: Diagramma UML casi duso di gestione Non Conformance Report
Released
15/12/2014 12:00 pm
Description
While the pastel tones and fine texture of this image may bring to mind brush strokes on an artists canvas, they are in fact a visualisation of data from
ESAs Planck satellite. The image portrays the interaction between interstellar dust in the Milky Way and the structure of our Galaxys magnetic
field. Between 2009 and 2013, Planck scanned the sky to detect the most ancient light in the history of the Universe the cosmic microwave
background. It also detected significant foreground emission from diffuse material in our Galaxy which, although a nuisance for cosmological studies,
is extremely important for studying the birth of stars and other phenomena in the Milky Way.
Among the foreground sources at the wavelengths probed by Planck is cosmic dust, a minor but crucial component of the interstellar medium
that pervades the Galaxy. Mainly gas, it is the raw material for stars to form. Interstellar clouds of gas and dust are also threaded by the Galaxys
magnetic field, and dust grains tend to align their longest axis at right angles to the direction of the field. As a result, the light emitted by dust grains
is partly polarised it vibrates in a preferred direction and, as such, could be caught by the polarisation-sensitive detectors on Planck.
Scientists in the Planck collaboration are using the polarised emission of interstellar dust to reconstruct the Galaxys magnetic field and study its
role in the build-up of structure in the Milky Way, leading to star formation.
In this image, the colour scale represents the total intensity of dust emission, revealing the structure of interstellar clouds in the Milky Way. The
texture is based on measurements of the direction of the polarised light emitted by the dust, which in turn indicates the orientation of the magnetic
field. This image shows the intricate link between the magnetic field and the structure of the interstellar medium along the plane of the Milky Way.
In particular, the arrangement of the magnetic field is more ordered along the Galactic plane, where it follows the spiral structure of the Milky Way.
Small clouds are seen just above and below the plane, where the magnetic field structure becomes less regular.
From these and other similar observations, Planck scientists found that filamentary interstellar clouds are preferentially aligned with the direction
of the ambient magnetic field, highlighting the strong role played by magnetism in galaxy evolution. The emission from dust is computed from a
combination of Planck observations at 353, 545 and 857 GHz, whereas the direction of the magnetic field is based on Planck polarisation data at
353 GHz.
Source
http://www.esa.int/spaceinimages/Images/2014/12/The_magnetic_field_along_the_Galactic_plane
5 S P E C I F I C H E S U P P L E M E N TA R I
Cronologia revisioni
Iterazione Descrizione
I.1 Raccolta caratteristiche alto livello nel primo workshop dei
requisiti di ideazione
E.1 Catalogazione dei requisiti su modello FURPS+
E.2 Raffinamento requisiti architetturali non funzionali
1 Robert Grady. Practical Software Metrics for Project Management and Process Improvement.
Prentice-Hall, 1992.
83
84 specifiche supplementari
notifiche
R1 Il sistema deve fornire supporto per la notifica allutente di at-
tivit intercorse nel sistema in sua assenza o eventi in tempo reale
che coinvolgono risorse con le quali in relazione o di cui diretto
destinatario.
reporting
R2 Il sistema deve creare report e documenti in formato stampabile
contenenti riferimenti ipertestuali navigabili nel formato elettronico.
security
R3 Il sistema deve consentire laccesso solo ad utenti che autenticano
la propria identit, ad esempio tramite username e password.
tagging
R7 Il sistema fornisce supporto per creare riferimenti univoci ai re-
cord, applicando paradigmi personalizzabili che utilizzano i campi
e attributi del record e numeri progressivi.
versioning
R9 Il sistema deve fornire supporto per la gestione di versione dei
record (versioning). Ogni volta che si modifica un record viene
creata automaticamente una nuova versione del record.
workflow
R10 Il sistema deve fornire supporto per la gestione dei processi di
revisione dei documenti (approval workflow). Alla modifica di
5.1 requisiti furps+ 85
5.1.2 Usabilit
accessibilit
R11 Il sistema deve consentire di inserire facilmente nei campi del-
lapplicazione tag per creare riferimenti a:
utenti, utilizzando il simbolo @ seguito dal nome utente,
record del progetto, usando il simbolo # seguito dal riferimento
secondo il paradigma adottato dal progetto.
consistenza
R14 Lapplicazione deve dare accesso a tutti i membri del progetto e
ai clienti utilizzando lo stesso indirizzo web. Ogni utente autenticato
visualizza in modo consistente le informazioni in base al proprio
ruolo sia che abbia un collegamento diretto ad un server interno sia
che acceda dallesterno.
estetica
R15 Il sistema deve offrire un interfaccia grafica responsiva e reattiva
in linea con gli attuali livelli di qualit della user experience delle
applicazioni web.
guida in linea
R17 Il sistema deve fornire aiuto tramite guida in linea accessibi-
le dallinterfaccia utente circa il contenuto dei form e i processi di
gestione documentale con riferimenti ai termini degli standard ECSS.
86 specifiche supplementari
manuale utente
R18 Il sistema deve fornire la documentazione daiuto per luten-
te: il manuale duso utente e il manuale per lamministrazione del
sistema.
5.1.3 Affidabilit
disponibilit
R19 Le edizioni enterprise a pagamento del software devono offri-
re livelli di servizio timeup conformi agli accordi (service level
agreement (SLA)).
integrit
R20 Il sistema deve poter certificare lintegrit dei record che hanno
seguito un processo di revisione apponendo la firma digitale.
logging
R21 Il sistema deve utilizzare un servizio di logging per consentire
il debugging dellapplicazione nella fase di sviluppo e di rilascio.
capacit di recupero
R22 Il sistema deve consentire la definizione di una politica di bac-
kup personalizzabile e lesecuzione programmata in dati giorni della
settimana. (v. R23)
5.1.4 Prestazioni
tempo di recupero
R23 Il sistema deve essere ripristinato da un precedente backup
minimizzando i tempi di recupero. (v. R22)
tempo di risposta
R24 Lapplicazione web deve avere dei tempi di risposta ragionevo-
li per lutente. Attese di uno o due secondi nel caricamento delle
pagine sono tollerabili.
throughput
R25 Il sistema deve supportare lutilizzo concorrente di decine di uti-
lizzatori contemporanei per ogni installazione su server onpremise e
migliaia di utilizzatori su servizi Cloud in modalit multitenant.
5.1.5 Sostenibilit
verificabilit
R26 Il sistema deve eseguire il processo di auditing in modo siste-
5.1 requisiti furps+ 87
configurabilit
R27 I file caricati nel sistema informativo devono essere memorizzati
su un repository configurabile, ad esempio database, file system loca-
le, nel file system di rete, server FTP, sistema di controllo di versione
distribuito.
installabilit
R29 Il sistema deve essere progettato per essere installato come un
servizio web accessibile su un server interno aziendale (on premise) o
sfruttando servizi di hosting esterni (Cloud).
localizzazione
R30 Il sistema deve presentare linterfaccia utente e il manuale di
amministrazione del sistema in lingua inglese. I termini chiave del
dominio devono essere riportati in lingua inglese come definiti negli
standard ECSS.
scalabilit
R32 Il sistema deve essere in grado di gestire grandi volumi dati per
mantenere lo storico delle versioni dei record e documenti.
testabilit
R33 Il processo di sviluppo deve essere guidato dai test di verifica
delle unit, di integrazione e di interfaccia.
Vincoli di progettazione
Raffinamento dei vincoli determinati nellanalisi che forniscono una pri-
ma soluzione indipendente dallimplementazione.
88 specifiche supplementari
R36 Ogni documento allegato a ogni tipo di record deve essere me-
morizzato in una sottocartella della cartella di progetto (v. R35) dedi-
cata al tipo di record (AI, MOM, IRPT, NCR, . . . ).
R37 Ogni documento caricato nel file server deve essere rinomina-
to per includere un prefisso contenente un riferimento basato su
un paradigma definito (ad esempio il tipo di record e un numero
progressivo).
grafica
R38 Le dashboard che presentano le informazioni di progetto e per-
sonali possono presentare pannelli contenenti grafici di analisi stati-
stica e tendenziale delle performance.
information exchange
R39 Il sistema deve supportare limportazione e lesportazione dei
technical data package (TDP) in formato XML e archivio ZIP.
licensing
R40 Il sistema rilasciato sotto licenza open source (permesso dauto-
re), include il codice sorgente, che pu essere utilizzato, studiato, mo-
dificato, distribuito, ceduto, senza discriminazioni, senza restrizioni,
lasciando intatti i diritti morali sullopera.
mail
R42 Il sistema deve fornire servizio di posta elettronica per linvio di
messaggi diretti ad utenti del sistema per la notifica e la richiesta di
intervento necessaria nei processi di gestione delle non conformit e
workflow di approvazione e revisione dei documenti.
5.1 requisiti furps+ 89
persistence
R43 Il sistema deve supportare i servizi di objectrelational mapping
(ORM) per la persistenza dei dati compatibile con i database dei
maggiori vendor.
resource management
R44 Il sistema deve fornire informazioni indicative delle risorse di
storage impegnate nel repository dei documenti e la quantit di
banda utilizzata nei trasferimenti di rete.
scheduling
R45 Il sistema deve offrire servizi di pianificazione e schedulazione
di operazioni:
timeconsuming come il backup
cpuconsuming come la crittografia per la firma digitale
networkconsuming come linvio di mail a numerosi utenti
system management
R46 Il sistema deve offrire supporto per strumenti di gestione, mo-
nitoring e configurazione a runtime.
time services
R47 Il sistema deve memorizzare e riportare le informazioni tem-
porali sul riferimento del tempo coordinato universale UTC (ISO
8601).
Vincoli di implementazione
componenti di terze parti
R49 Il sistema deve far uso di tecnologie e componenti opensource.
90 specifiche supplementari
linguaggi di implementazione
R50 Il sistema di backend pu essere sviluppato su piattaforma
Java Enterprise Edition e framework Spring.
piattaforma di supporto
R52 Il sistema di accounting deve poter supportare e integrarsi in
futuro con sistemi di autenticazione basata su protocollo LDAP o
OpenID.
resource limits
R53 Il sistema deve fornire supporto alla gestione di quote di spazio
nel repository e quote di invio email del sistema di notifica.
standard di conformit
R54 Il sistema deve essere conforme ai requisiti normativi conte-
nuti negli standard ECSS, per le discipline e i principi applicabili
e i processi operati a ogni livello della catena clientefornitore del
progetto/programma spaziale.
Vincoli di interfaccia
formati di interfaccia
R55 Il sistema deve offrire servizi di presentazione, accesso e trasfe-
rimento dello stato delle risorse con architettura REST. Ogni risorsa
deve essere identificata e localizzata da un URL.
5.2 fattori architetturali 91
Source
http://www.spacetelescope.org/news/heic1608/
6 MODELLO DI DOMINIO
Cronologia revisioni
Iterazione Descrizione
E.1 Elaborazione dei diagrammi delle classi concettuali
1 Martin Fowler. Analysis Patterns: Reusable Object Models. Addison-Wesley, 1996. isbn:
978-0-201-89542-1.
2 Craig Larman. Applicare UML e i pattern. Analisi e progettazione orientata agli oggetti. A cura
di Luca Cabibbo. 4a ed. Pearson Italia S.p.A., 2016, p. 708. isbn: 9788891901033, cap. 12.6.
97
98 modello di dominio
Project
Role * * 1 customer
* Company
Employee
name
name Account acronym
surname 1 1 address
type
email * 1 ESA registration number
username
photo legal tax number
password
phone EMITScode
mobile logo
Employment website
employee number
*
job description 1
* *
acronym * * type
title
*
type
customer * description *
Company
1 status Permission
1
Repository 1
Project 1
1 Inspection Report
*
*
Action Item 0..1
* reference
* 1 assigner *
title
organizer Employee description
1 verification
start date
attendee * * 1 assignee deadline
* priority
status
* * MOM approved
*
* Meeting
0..1
reference
title datapackage Document
type 1 *
*
date
agenda 1
place
status 1 minutes 1
1
Figura 15: Diagramma UML delle classi concettuali Meeting e Action Item
Management
1 * author
*
Document
* reference
*
title
Repository type
1 * docfile
status
issue
revision
1
* 1 author
*
Inspection Report
reference
0..1 title *
type Nonconformance Report
report 1 *
date
facility
0..1
status
AIT
*
* inspected item
Manifactured Item NC item
1
Employee Project 1
Company
responsible * 1
0..* 0..* manufacturer 1
child assembly
* *
*
Configuration Item Part
Manifactured Item
* name name
description * description * description
status status status
1
type 1 type 1
1 1
1
1 * attachment 1 Serial
CI Code Document * Part Number
batch
attachment
part no serial
Action Item
Assigned
Created
assign
start
withdraw [verification]
restart
restart
Withdrawn
pause reject[explanation]
Paused Rejected
We cast this message into the cosmos . . . Of the 200 billion stars in the Milky Way galaxy, some perhaps many may have inhabited
planets and space faring civilizations. If one such civilization intercepts Voyager and can understand these recorded contents, here is
our message: This is a present from a small distant world, a token of our sounds, our science, our images, our music, our thoughts,
and our feelings. We are attempting to survive our time so we may live into yours. We hope some day, having solved the problems
we face, to join a community of galactic civilizations. This record represents our hope and our determination and our goodwill in a
vast and awesome universe.
Source
https://en.wikipedia.org/wiki/Contents_of_the_Voyager_Golden_Record
7 M O D E L LO D E I DAT I
Iterazione Descrizione
E.1 Elaborazione modello concettuale dei dati
E.2 Elaborazione modello logico relazionale dei dati
Entit Company
105
106 modello dei dati
Entit Account
Entit Project
Entit Repository
Cardinalit N:1
Partecipazione obbligatoria
Chiave primaria (employee, company)
Chiavi esterne (company, employee), company
Attributi employee_number, description
Business rules
108 modello dei dati
Cardinalit N:N
Partecipazione Obbligatoria
Chiave primaria (company, employee, project)
Chiavi esterne (company, employee), project
Attributi type
Business rules
BR24: vincolo integrit campo (company,employee) riferimento a
Employee
BR25: vincolo integrit campo project riferimento a Project
BR26: vincolo dominio campo enumerativo
type = {project manager, deputy manager, configuration
manager, AIT manager, QA manager, AIT engineer, QA engineer,
system engineer, mechanical engineer, thermal engineer,
testing engineer, electronic engineer, support, customer}
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, meeting, company, attendee)
Chiavi esterne (project, meeting), (company, attendee)
Business rules
BR41: vincolo integrit campo (project,meeting) riferimento a Mee-
ting
BR42: vincolo integrit campo (company,attendee) riferimento a
Employee
110 modello dei dati
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, meeting, actionitem)
Chiavi esterne (project, meeting), (project, actionitem)
Business rules
BR43: vincolo integrit campo (project,meeting) riferimento a Mee-
ting
BR44: vincolo integrit campo (project,actionitem) riferimento
a ActionItem
Cardinalit N:N
Partecipazione Obbligatoria
Chiave primaria (project, document, company, author)
Chiavi esterne (project, document), (company, author)
Business rules
BR51: vincolo integrit campo (project,document) riferimento a
Document
BR52: vincolo integrit campo (company,author) riferimento a Em-
ployee
7.1 modello concettuale 111
Cardinalit N:N
Partecipazione Obbligatoria
Chiave primaria (project, document, company, revisor)
Chiavi esterne (project, document), (company, revisor)
Attributi remarks
Business rules
BR53: vincolo integrit campo (project,document) riferimento a
Document
BR54: vincolo integrit campo (company,revisor) riferimento a Em-
ployee
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, company, responsible)
Chiavi esterne (project, ci_code), (company, responsible)
Business rules
BR61: vincolo integrit campo (project, ci_code) riferimento a
ConfigurationItem
112 modello dei dati
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, attachment)
Chiavi esterne (project, ci_code), (project, attachment)
Business rules
BR63: vincolo integrit campo (project,ci_code) riferimento a Con-
figurationItem
BR64: vincolo integrit campo (project,attachment) riferimento
a Document
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, part_number, attachment)
Chiavi esterne (project, ci_code, part_number), attachment
Business rules
BR72: vincolo integrit campo (project, ci_code, part_number)
riferimento a Part
BR73: vincolo integrit campo attachment riferimento a Document
Entit Material
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, part_number, material)
Chiavi esterne (project, ci_code, part_number), material
Business rules
BR74: vincolo integrit campo (project, ci_code, part_number)
riferimento a Part
BR75: vincolo integrit campo material riferimento a Material
Entit Finishing
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, part_number, finishing)
Chiavi esterne (project, ci_code, part_number), finishing
Business rules
BR76: vincolo integrit campo (project, ci_code, part_number)
riferimento a Part
BR77: vincolo integrit campo finishing riferimento a Finishing
Entit Process
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, part_number, process)
Chiavi esterne (project, ci_code, part_number), process
Business rules
BR78: vincolo integrit campo (project, ci_code, part_number)
riferimento a Part
BR79: vincolo integrit campo process riferimento a Process
Entit Property
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ci_code, part_number, property)
Chiavi esterne (project, ci_code, part_number), property
Attributi value
Business rules
BR81: vincolo integrit campo (project, ci_code, part_number)
riferimento a Part
BR82: vincolo integrit campo property riferimento a Property
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, irpt, actionitem)
Chiavi esterne (project, irpt), (project, actionitem)
Business rules
Cardinalit N:1
Partecipazione non obbligatoria
Chiave primaria (project, ncr, facility)
Chiavi esterne (project, ncr), (project, facility)
Business rules
Cardinalit N:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, witness)
Chiavi esterne (project, ncr), (company, witness)
Business rules
BR111: vincolo integrit campo (project, ncr) rif. a NonConfor-
manceReport
BR112: vincolo integrit campo (company, witness) riferimento a
Employee
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, meeting)
Chiavi esterne (project, ncr), (project, meeting)
Attributi disposition
Business rules
BR113: vincolo integrit campo (project,ncr) riferimento a Non-
ConformanceReport
BR114: vincolo integrit campo (project, meeting) rif. a Meeting
BR115: vincolo integrit campo enumerativo
disposition = { Return to Supplier, Use as is, Rework,
Repair, Scrap }
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, ai)
Chiavi esterne (project, ncr), (project, ai)
Business rules
BR116: vincolo integrit campo (project, ncr) riferimento a Non-
ConformanceReport
BR117: vincolo integrit campo (project, ai) rif. a ActionItem
7.1 modello concettuale 119
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, ci)
Chiavi esterne (project, ncr), (project, ci)
Business rules
BR118: vincolo integrit campo (project, ncr) riferimento a Non-
ConformanceReport
BR119: vincolo integrit campo (project, ci) riferimento a Confi-
gurationItem
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, part)
Chiavi esterne (project, ncr), (project, ci, part)
Business rules
BR120: vincolo integrit campo (project, ncr) riferimento a Non-
ConformanceReport
BR121: vincolo integrit campo (project, ci, part) riferimento a
Part
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (project, ncr, ci, part, batch, serial)
Chiavi esterne (project, ncr), (project, ci, part, batch,
serial)
Business rules
BR122: vincolo integrit campo (project, ncr) riferimento a Non-
ConformanceReport
BR123: vincolo integrit campo (project, ci, part, batch, serial)
riferimento a ManufacturedPart
120 modello dei dati
Entit PhoneNumber
Entit EmailAddress
Chiavi (uid)
Attributi email_address
Business rules
BR127: (asserzione) validazione campo email_address formato4 <lo-
calname>@<FQDN>
Entit Address
Chiavi (uid)
Attributi address_line1, address_line2, city,
state_province_region, zip_postalcode, country
Business rules
BR128: (asserzione) validazione campo enumerativo country = { na-
zioni }
Entit CustomField
Chiavi (uid)
Attributi type, name, value
Business rules
BR129: vincolo dominio campo enumerativo
type = {string, integer, date, time, timestamp, double
...}
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (company, employee, phone)
Chiavi esterne (company, employee), phone
Businees rules
BR130: vincolo integrit campo (company,employee) rif. a Employee
BR131: vincolo integrit campo phone riferimento a PhoneNumber
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (company, employee, email)
Chiavi esterne (company, employee), email
Businees rules
BR132: vincolo integrit campo (company,employee) rif. a Employee
BR133: vincolo integrit campo email riferimento a EmailAddress
Cardinalit 1:N
Partecipazione non obbligatoria
Chiave primaria (company, employee, customfield)
Chiavi esterne (company, employee), customfield
Businees rules
BR134: vincolo integrit campo (company,employee) rif. a Employee
BR135: vincolo integrit campo customfield riferimento a Custom-
Field
7.2 normalizzazione modello concettuale 123
emits_bidder_code, :::::::
LR1. Company(uid, ::::::::::::::::::: vat_id, acronym, name,
type, description, website, logo, address)
LR17. Meeting_Attendant(project,meeting,company,attendee)
LR18. Meeting_ActionItem(project,meeting,actionitem)
LR20. Document_Author(document,author)
5 Legenda: chiave primaria, :::::
chiave:::::::::
candidata, chiave esterna, .campo
. . . . . . . .derivato
.........
7.3 mappatura da modello concettuale a modello logico relazionale 125
LR21. Document_Revisor(document,revisor,remarks)
LR23. ConfigurationItem_Responsible(configurationitem,responsible)
LR24. ConfigurationItem_Attachment(configurationitem,attachment)
LR26. Part_Attachment(project,ci_code,part_number,attachment)
LR28. Part_Material(project,ci_code,part_number,material)
LR30. Part_Finishing(project,ci_code,part_number,finishing)
LR32. Part_Process(project,ci_code,part_number,process)
LR34. Part_Property(project,ci_code,part_number,property,value)
LR36. Facility(project,uid,address)
LR38. InspectionReport_ActionItem(project,irpt,actionitem)
LR40. NCR_Facility(project,ncr,facility)
LR41. NCR_Witness(project,ncr,witness)
LR42. NCR_ReviewBoardMeeting(project,ncr,meeting,disposition)
LR43. NCR_ActionItem(project,ncr,actionitem)
LR44. NCR_ConfigurationItem(project,ncr,configurationitem)
LR45. NCR_Part(project,ncr,ci,part)
LR46. NCR_ManufacturedPart(project,ncr,ci,part,manufactured)
Hubbles sharpest view of the Orion Nebula
Credit NASA, ESA, M. Robberto (Space Telescope Science Institute/ESA) and the Hubble Space Telescope Orion Treasury Project Team
Hubbles sharpest view of the Orion Nebula
Release date 11 January 2006, 16:00
This dramatic image offers a peek inside a cavern of roiling dust and gas where thousands of stars are forming. The image, taken by the Advanced
Camera for Surveys (ACS) aboard NASA/ESA Hubble Space Telescope, represents the sharpest view ever taken of this region, called the Orion
Nebula. More than 3,000 stars of various sizes appear in this image. Some of them have never been seen in visible light. These stars reside in a
dramatic dust-and-gas landscape of plateaus, mountains, and valleys that are reminiscent of the Grand Canyon.
The Orion Nebula is a picture book of star formation, from the massive, young stars that are shaping the nebula to the pillars of dense gas that may
be the homes of budding stars. The bright central region is the home of the four heftiest stars in the nebula. The stars are called the Trapezium
because they are arranged in a trapezoid pattern. Ultraviolet light unleashed by these stars is carving a cavity in the nebula and disrupting the
growth of hundreds of smaller stars. Located near the Trapezium stars are stars still young enough to have disks of material encircling them. These
disks are called protoplanetary disks or proplyds and are too small to see clearly in this image. The disks are the building blocks of solar systems.
The bright glow at upper left is from M43, a small region being shaped by a massive, young stars ultraviolet light. Astronomers call the region a
miniature Orion Nebula because only one star is sculpting the landscape. The Orion Nebula has four such stars. Next to M43 are dense, dark pillars
of dust and gas that point toward the Trapezium. These pillars are resisting erosion from the Trapeziums intense ultraviolet light. The glowing
region on the right reveals arcs and bubbles formed when stellar winds - streams of charged particles ejected from the Trapezium stars - collide
with material.
The faint red stars near the bottom are the myriad brown dwarfs that Hubble spied for the first time in the nebula in visible light. Sometimes called
failed stars, brown dwarfs are cool objects that are too small to be ordinary stars because they cannot sustain nuclear fusion in their cores the
way our Sun does. The dark red column, below, left, shows an illuminated edge of the cavity wall.
The Orion Nebula is 1,500 light-years away, the nearest star-forming region to Earth. Astronomers used 520 Hubble images, taken in five colours,
to make this picture. They also added ground-based photos to fill out the nebula. The ACS mosaic covers approximately the apparent angular size
of the full moon.
The Orion observations were taken between 2004 and 2005.
Source
http://www.spacetelescope.org/news/heic0601/
8 ARCHITETTURA SOFTWARE
No keyboard detected
Press F1 to resume
Messaggio di un vecchio BIOS per PC
Cronologia revisioni
Iterazione Descrizione
E.1 Analisi architetturale
129
130 architettura software
Source
http://www.spacetelescope.org/news/heic1007/
9 M O D E L LO D I I M P L E M E N TA Z I O N E
Sono convinto che linformatica abbia molto in comune con la fisica. Entrambe si
occupano di come funziona il mondo a un livello abbastanza fondamentale.
La differenza, naturalmente, che mentre in fisica devi capire
come fatto il mondo, in informatica sei tu a crearlo.
Rivoluzionario per caso
Linus Torvalds
Cronologia revisioni
Iterazione Descrizione
E.2 Elaborazione modello logico relazionale dei dati
133
134 modello di implementazione
20 logo BLOB,
21 address INTEGER,
22 FOREIGN KEY(address)
23 REFERENCES Address(uid),
24 CONSTRAINT CHK_company_type
25 CHECK (VALUE IN("prime", "subcontractor", "customer", -
, "supplier", "partner"))
26 );
27
28 CREATE TABLE Employee(
29 company INTEGER,
30 uid INTEGER,
31 name VARCHAR(64),
32 surname VARCHAR(64) NOT NULL,
33 middlename VARCHAR(64),
34 photo BLOB,
35 employee_number VARCHAR(16),
36 description VARCHAR(256),
37 PRIMARY KEY (company, uid),
38 FOREIGN KEY (company) REFERENCES Company(uid)
39 );
40
41 CREATE TABLE Account(
42 username VARCHAR(64) PRIMARY KEY,
43 company INTEGER,
44 employee INTEGER,
45 type VARCHAR(8),
46 password VARCHAR(32) NOT NULL,
47 FOREIGN KEY (company)
48 REFERENCES Company(uid),
49 FOREIGN KEY (company, employee)
50 REFERENCES Employee(company,uid),
51 CONSTRAINT CHK_account_type
52 CHECK (VALUE IN("user", "manager", "admin", "partner", -
, "customer"))
53 );
54
55 CREATE TABLE EmailAddress(
56 uid INTEGER PRIMARY KEY,
57 email_address VARCHAR(256) NOT NULL
58 );
59
60 CREATE TABLE Employee_EmailAddress(
61 company INTEGER,
62 employee INTEGER,
63 email INTEGER,
64 PRIMARY KEY (company, employee, email)
65 FOREIGN KEY (company, employee)
66 REFERENCES Employee(company,uid),
67 FOREIGN KEY (email)
68 REFERENCES EmailAddress(uid)
69 );
70
9.1 schema relazionale sql 135
118 );
119
120 CREATE TABLE Repository(
121 project INTEGER,
122 uid INTEGER,
123 type VARCHAR(16),
124 uri VARCHAR(2048),
125 PRIMARY KEY(project, uid),
126 FOREIGN KEY(project)
127 REFERENCES Project(uid),
128 CONSTRAIT repository_type
129 CHECK (VALUE IN("file system", "network share", "ftp", -
, "sftp")
130 );
131
132 CREATE TABLE ReferenceTemplate(
133 project INTEGER,
134 uid INTEGER,
135 template VARCHAR(256) NOT NULL,
136 PRIMARY KEY(project, uid),
137 FOREIGN KEY(project)
138 REFERENCES Project(uid)
139 );
140
141 CREATE TABLE Role(
142 project INTEGER,
143 company INTEGER,
144 employee INTEGER,
145 type VARCHAR(32),
146 PRIMARY KEY(project, company, employee),
147 FOREIGN KEY(project)
148 REFERENCES Project(uid),
149 FOREIGN KEY(company, employee)
150 REFERENCES Employee(company, uid),
151 CONSTRAINT CHK_role_type
152 CHECK (VALUE IN("Project Manager", "Deputy Manager", -
, "Configuration Manager", "AIT Manager", "QA -
, Manager", "AIT Engineer", "QA Engineer", "System -
, Engineer", "Mechanical Engineer", "Thermal -
, Engineer", "Testing Engineer", "Electronic -
, Engineer", "Support", "Customer")),
153 );
154
155 CREATE TABLE ActionItem(
156 project INTEGER,
157 uid INTEGER,
158 assigner_company INTEGER,
159 assigner INTEGER,
160 _
assignee company INTEGER,
161 assignee INTEGER,
162 status VARCHAR(16),
163 priority VARCHAR(8),
164 title VARCHAR(256),
9.1 schema relazionale sql 137
369 );
370
371 CREATE TABLE Part_Material(
372 project INTEGER,
373 _
ci code VARCHAR(32),
374 part_number VARCHAR(32),
375 material INTEGER,
376 PRIMARY KEY(project, ci_code, part_number, material),
377 FOREIGN KEY(project, parent_ci, part_number)
378 REFERENCES Part(project, ci_code, part_number),
379 FOREIGN KEY(material)
380 REFERENCES Material(uid)
381 );
382
383 CREATE TABLE Finishing(
384 uid INTEGER PRIMARY KEY,
385 type VARCHAR(64),
386 name VARCHAR(256),
387 description VARCHAR(256)
388 );
389
390 CREATE TABLE Part_Finishing(
391 project INTEGER,
392 ci_code VARCHAR(32),
393 part_number VARCHAR(32),
394 finishing INTEGER,
395 PRIMARY KEY(project, ci_code, part_number, finishing),
396 FOREIGN KEY(project, parent_ci, part_number)
397 REFERENCES Part(project, ci_code, part_number),
398 FOREIGN KEY(finishing)
399 REFERENCES Finishing(uid)
400 );
401
402 CREATE TABLE Process(
403 uid INTEGER PRIMARY KEY,
404 type VARCHAR(64),
405 name VARCHAR(256),
406 description VARCHAR(256)
407 );
408
409 CREATE TABLE Part_Process(
410 project INTEGER,
411 ci_code VARCHAR(32),
412 part_number VARCHAR(32),
413 process INTEGER,
414 PRIMARY KEY(project, ci_code, part_number, process),
415 FOREIGN KEY(project, parent_ci, part_number)
416 REFERENCES Part(project, ci_code, part_number),
417 FOREIGN KEY(process)
418 REFERENCES Process(uid)
419 );
420
421 CREATE TABLE Property(
142 modello di implementazione
, serial_number)
624 REFERENCES ManufacturedPart(project, ci_code, -
, part_number, batch_number, serial_number)
625 );
10 PIANO DI SVILUPPO DEL
SOFTWARE
Cronologia revisioni
Iterazione Descrizione
I.1 Piano della prima iterazione di elaborazione
E.1 Pianificazione degli elaborati nelle fasi e iterazioni
147
Parte II
APPENDICI
ESA Space Engineering A
(c) Examining every detail Released 29/06/2016 2:06 pm (d) ATV-4 docking system test Released 12/10/2012
Copyright STFCS. Kill The ESARAL Advanced Man- 12:22 pm Copyright ESA/CNES/Arianespace/Optique
ufacturing Laboratory on Harwell Campus, UK, assesses Video du CSG Engineers test ATV Albert Einsteins
new material processes, joining techniques and 3D print- docking system in Kourou, French Guiana. By using
ing technologies for application in space. The Scanning a plate that reproduces the passive part on the In-
Electron Microscope allows microstructural observation ternational Space Station the complete capture and
of internal porosity, cracks, defects and grain morphology docking sequence can be tested mechanically on Earth.
as well as compositional analysis using Energy Dispersive Each spacecraft can deliver up to 7 tonnes of cargo to
X-ray Spectroscopy. the International Space Station including supplies and
equipment, water, air, nitrogen, oxygen and fuel.
Philaes instruments
Released 20/12/2013 4:37 pm
Description Rosetta will deploy the Philae lander to the surface of comet 67P/Churyumov-Gerasimenko for in situ
analysis with its 10 instruments:
APXS Alpha Proton X-ray Spectrometer (studying the chemical composition of the landing site and its potential
alteration during the comets approach to the Sun)
CIVA Comet Nucleus Infrared and Visible Analyser (six cameras to take panoramic pictures of the comet
surface)
CONSERT COmet Nucleus Sounding Experiment by Radiowave Transmission (studying the internal structure of the
comet nucleus with Rosetta orbiter)
COSAC The COmetary SAmpling and Composition experiment (detecting and identifying complex organic
molecules)
PTOLEMY Using MODULUS protocol (Methods Of Determining and Understanding Light elements from Unequivocal
Stable isotope compositions) to understand the geochemistry of light elements, such as hydrogen, carbon,
nitrogen and oxygen.
MUPUS MUlti-PUrpose Sensors for Surface and Sub-Surface Science (studying the properties of the comet surface
and immediate sub-surface)
ROLIS Rosetta Lander Imaging System (providing the first close-up images of the landing site)
ROMAP Rosetta Lander Magnetometer and Plasma Monitor (studying the magnetic field and plasma environment
of the comet)
SD2 Sampling, drilling and distribution subsystem (drilling up to 23 cm depth and delivering material to onboard
instruments for analysis)
SESAME Surface Electric Sounding and Acoustic Monitoring Experiment (probing the mechanical and electrical
parameters of the comet)
Schiapparelli
Released 28 October 2015
Description Because Schiaparelli is primarily demonstrating technologies needed for landing, it does not have a long
scientific mission lifetime: it is intended to survive on the surface for just a few days by using the excess energy capacity
of its batteries. However, a set of engineering and scientific sensors will analyse the local environment during descent
and after landing.
This artists impression shows the interior of the Schiaparelli entry, descent and landing demonstrator module. Schiaparelli,
part of the ExoMars 2016 mission, was launched together with the Trace Gas Orbiter on 14 March 2016 and will arrive
at the Red Planet in October.
Schiaparelli carries a small science payload, called DREAMS (Dust Characterisation, Risk Assessment, and Environment
Analyser on the Martian Surface), to study the environment.
DREAMS consists of a suite of sensors to measure the local wind speed and direction (MetWind), humidity (DREAMS-H),
pressure (DREAMS-P), atmospheric temperature close to the surface (MarsTem), the transparency of the atmosphere
(Solar Irradiance Sensor, SIS), and atmospheric electric fields (Atmospheric Radiation and Electricity Sensor; MicroARES)
at Mars. The payload will operate on the surface of Mars for 28 sols.
In addition, there is an investigation known as AMELIA, for entry and descent science data collection using the spacecraft
engineering sensors. A separate instrumentation package, COMARS+, will monitor the heat flux on the back cover of
Schiaparelli as it passes through the atmosphere.
A compact array of laser retroreflectors, INRRI, is attached to the zenith-facing surface of Schiaparelli. This can be used
as a target for Mars orbiters to laser-locate the module.
A UHF antenna is used for communicating with the Trace Gas Orbiter.
155
BIBLIOGRAFIA
157
158 Bibliografia
standard ecss
[] ECSS Abbreviated terms. ECSS. url: http : / / ecss .
nl/home/ecss-glossary-abbreviations/.
risorse online
[12] What is the CDF? ESA. 31 Lug. 2012. url: http://
www.esa.int/Our_Activities/Space_Engineering_
Technology/CDF/What_is_the_CDF.
[Tan13] Till Tantau. The TikZ and PGF Packages. Manual for
version 3.0.0. 20 Dic. 2013. url: http://sourceforge.
net/projects/pgf/.
LIBERATORIA ALLA CONSULTAZIONE
DELLA TESI DI LAUREA
DI CUI ALLART.4 DEL REGOLAMENTO DI ATENEO
PER LA CONSULTAZIONE DELLE TESI DI LAUREA
(D.R. n. 479 del 14/11/2016)
autorizza
Marco Vanada