Prototypage logiciel

Le prototypage logiciel (ou « software prototyping » en anglais) désigne l'ensemble des activités de création de prototypes pour les logiciels, c'est-à-dire des versions incomplètes du programme en cours de développement. Cette activité est donc assez proche de la création et la validation de prototypes, telle qu'on la pratique dans l'industrie. Ainsi, un prototype permet d'explorer de façon interactive des scénarios d'utilisation du produit pour en valider les orientations. Il ne simule toutefois que quelques aspects du logiciel et peut être très différent du produit final. Intérêts De même que les industriels commencent toujours par procéder à un prototypage avant de construire de coûteuses usines afin de mettre en évidence les défauts qui n'avaient pas été imaginés, il est conseillé au concepteur de logiciels de réaliser une maquette, ou un prototype (ou les deux) pour tester la validité de sa conception, et recevoir les remarques des utilisateurs (il est en effet b

À propos de ce résultat

Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.

Publications associées (36)

Publications associées

Chargement

Personnes associées (1)

Personnes associées

Chargement

Unités associées (2)

Unités associées

Chargement

Concepts associés (4)

Concepts associés

Chargement

Cours associés (17)

Cours associés

Chargement

Séances de cours associées (34)

Séances de cours associées

Chargement

Improving the Interoperation between Generics Translations

Romain Michel Beguet, Martin Odersky, Milos Stojanovic, Nicolas Alexander Stucki, Vlad Ureche

Generics on the Java platform are compiled using the erasure transformation, which only supports by-reference values. This causes slowdowns when generics operate on primitive types, such as integers, as they have to be transformed into reference-based objects. Project Valhalla is an effort to remedy this problem by specializing classes at load-time so they can efficiently handle primitive values. In its current early prototype, the Valhalla compilation scheme limits the interaction between specialized and erased generics, thus preventing certain useful code patterns from being expressed. Scala has been using compile-time specialization for 6 years and has three generics compilation schemes working side by side. In Scala, programmers are allowed to write code that freely exercises the interaction between the different compilation schemes, at the expense of introducing subtle performance issues. Similar performance issues can affect Valhalla-enabled bytecode, whether the code was written in Java or translated from other JVM languages. In this context we explain how we help programmers avoid these performance regressions in the miniboxing transformation: (1) by issuing actionable performance advisories that steer programmers away from performance regressions and (2) by providing alternatives to the standard library constructs that use the miniboxing encoding, thus avoiding the conversion overhead.

ACM2015

Chargement

ScalaDyno: Making Name Resolution and Type Checking Fault-tolerant

Cédric Bastin, Martin Odersky, Vlad Ureche

The ScalaDyno compiler plugin allows fast prototyping with the Scala programming language, in a way that combines the benefits of both statically and dynamically typed languages. Static name resolution and type checking prevent partially-correct code from being compiled and executed. Yet, allowing programmers to test critical paths in a program without worrying about the consistency of the entire code base is crucial to fast prototyping and agile development. This is where ScalaDyno comes in: it allows partially-correct programs to be compiled and executed, while shifting compile-time errors to program runtime. The key insight in ScalaDyno is that name and type errors affect limited areas of the code, which can be replaced by instructions to output the respective errors at runtime. This allows byte code generation and execution for partially correct programs, thus allowing Python or JavaScript-like fast prototyping in Scala. This is all done without sacrificing name resolution, full type checking and optimizations for the correct parts of the code -- they are still performed, but without getting in the way of agile development. Finally, for release code or sensitive refactoring, runtime errors can be disabled, thus allowing full static name resolution and type checking typical of the Scala compiler.

ACM2014

Chargement

Experience Catalysts And Architecture Towards a New Tradition

Jens Badura, Jeffrey Huang, Selena Savic, Andrew James Sempere

This paper describes two research projects in the field of interactive architecture, both examples of experience catalysts; Settings which allow new insights in the aesthetic constitution and perception of environments. This term can be thought of as somewhat synonymous with artistic intervention, but is used instead to recognize that the participants might not self-identify as artists. We are working with architectural notions of space and place, but are interested in the experience of place more than its formal structure. We wish to emphasize the dynamic and are interested in transitions not as the pauses between states but as destinations worth exploring. Quadricone by Selena Savic is an actual experience catalyst: a physical manifestation of a digital “material” (in this case network traffic.) The goal is less data visualization and more an attempt to understand what it means to physically experience something normally invisible. Inter-Actor by Andrew Sempere casts architecture as an ongoing event which might benefit from the flexibility of the digital. The idea is to create a combination of software and hardware that allows for “rapid prototyping” of interactive space. Inter-Actor is not an experience catalyst but a toolkit for creating them.

Porto: FAUP Publicações2013

Chargement

Développement rapide d'applications

La méthode de développement rapide d'applications, dite méthode RAD (acronyme de l'anglais rapid-application development), est la première méthode de développement de logiciels où le cycle de dévelo

Software development process

In software engineering, a software development process is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, o

Prototype

vignette|Photographie d'un prototype BMW : la BMW Nazca C2 Dans le domaine de l'industrie et plus généralement de la recherche et développement (R&D), un prototype est selon la définition de l'OCDE ,

MGT-409: D. Thinking: real problems, human-focused solutions

This course aims to engage students into multidisciplinary collaboration to tackle real world problems with a human centered approach. It will also provide knowledge about the role of design in innovation.

CS-486: Interaction design

This course focuses on goal-directed design and interaction design, two subjects treated in depth in the Cooper book (see reference below). To practice these two methods, we propose a design challenge, which is further divided into mini-projects evenly spaced throughout the semester.

MICRO-406: Products design & systems engineering

This course will cover all the aspects of product design and system engineering from learning relevant methods to the actual implementation in a hands-on practice of product development.