← Indietro
EsameEsame completoTesto d’esame

10 01 18

Esame completo di Software Engineering 2 per il corso di Computer Engineering presso Politecnico di Milano. Materiale proveniente dall’archivio storico Studwiz e classificato per la consultazione online.

Software Engineering 2Esame completo

Informazioni sul documento

Cosa trovi in questo materiale

Esame completo di Software Engineering 2 per il corso di Computer Engineering presso Politecnico di Milano. Materiale proveniente dall’archivio storico Studwiz e classificato per la consultazione online.

Qualità dell’importazione: il testo è stato estratto direttamente dal documento originale.

Contenuti estratti dal documento

Passaggi rappresentativi riconosciuti nelle diverse parti del materiale. Il testo completo resta presente nella pagina per la ricerca, mentre l’anteprima compatta rende più semplice la lettura.

Pagina 1

Dipartimento di Elettronica e Informazione Politecnico di Milano prof. Carlo Ghezzi e Elisabetta Di Nitto 20133 Milano (Italia) Piazza Leonardo da Vinci, 32 Tel. (39) 02-2399.3400 Fax (39) 02-2399.3411 Software Engineering II Part I 10 January 2008 Last name First name Identification number (Matricola) Section (specify the professor you are associated with, either Prof. Ghezzi or Prof. Di Nitto) Notes 1. Missing identification data invalidate the exam. 2. Return only these pages. Extra sheets will be ignored. You may use a pencil. 3. The exam is in 2 parts. For part 1 you will not be allowed to use books or class notes. For part 2 you will be allowed to use books and class notes. The first part must be in 30 min., the second part in 55 min. The final result is the sum of the scores obtained in both parts. 4. Any use of electronic devices (computers, calculators, cell phones, …) is forbidden. 5. You cannot keep a copy of the exam when you leave the room. 2 Question 1 – Software development process (2 points) What is a software prototype? It is an intermediate, partial implementation of a system developed to assess some property of the system before starting the final development, to reduce project risks. This practice is common in other fields. For example, airplane wings are evaluated in a wind tunnel before moving to production. How can you classify prototypes? Throw-away prototypes are only used for assessment (like the airplane wing above). Evolutionary prototypes may be evolved progressively into the final product. Both are possible in software. For example, a component that simulates the external environment in a plant control software can be viewed as throw-away. When and why can it be useful? Typically, when requirements are not fully understood. For example,…

Anteprima

Prima pagina del documento.

Prima pagina: 10 01 18