@article{hemacasa:2003:icpc-final2001-almejas,
  author = {{{\'{A}}ngel} Herranz and Julio Mari{\~{n}}o and Manuel Carro and Pablo
                  Sanchez},
  title = {Almejas gigantes e interfaces de usuario (soluci{\'{o}}n del
                  programa E)},
  journal = {Novatica},
  year = {2003},
  volume = {1},
  number = {161},
  pages = {70},
  month = jan,
  note = {Secci{\'{o}}n ``Programar es crear''},
  url = {http://www.ati.es/novatica/2003/161/161-70.pdf}
}
@unpublished{rey:2003:katana,
  author = {Jos{\'{e}} Mar{\'{i}}a Rey},
  title = {Demand Analysis via the Dynamic Generation of Finite
                  Domains},
  note = {Available at http://babel.ls.fi.upm.es/publications},
  optkey = {},
  optmonth = {},
  year = {2003},
  annote = {In Spanish}
}
@inproceedings{hemo:2003:fahme,
  author = {{{\'{A}}ngel} Herranz and Juan Jos{\'{e}} {Moreno-Navarro}},
  title = {Formal Agility.  How Much of Each?},
  booktitle = {Taller de Metodolog{\'{i}}as {\'{A}}giles en el Desarrollo del
                  Software. VIII Jornadas de Ingenier{\'{i}}a del Software y Bases
                  de Datos, JISBD 2003},
  pages = {47-51},
  year = {2003},
  month = nov,
  organization = {Grupo ISSI},
  address = {Alicante, Espa{\~{n}}a},
  abstract = { Agile Processes and Formal Methods (FM), water and oil,
                  impossible mixture?  Yes at first sight.  Nevertheless,
                  being formal methods weight processes and being agile
                  processes informal approaches to software development, it is
                  worth to study how much formal can be an agile process like
                  Extreme Programming (XP) and how much agile can be a formal
                  method.  On our view, some XP practices are suitable for a
                  formal approach.  },
  postscript = {http://babel.ls.fi.upm.es/~angel/papers/finalcopy-jisbd2003.ps.gz}
}
@inproceedings{hemamo:2003:fesj,
  author = {{{\'{A}}ngel} Herranz and Noelia Maya and Juan Jos{\'{e}}
                  {Moreno-Navarro}},
  title = {From Executable Specifications to Java},
  booktitle = {III Jornadas sobre Programaci{\'{o}}n y Lenguajes, PROLE 2003},
  pages = {33-44},
  year = {2003},
  editor = {Juan Jos{\'{e}} {Moreno-Navarro} and Manuel Palomar},
  address = {Alicante, Espa{\~{n}}a},
  month = nov,
  organization = {Departamento de Lenguajes y Sistemas Inform{\'{a}}ticos,
                  Universidad de Alicante},
  note = {Dep{\'{o}}sito Legal MU-2299-2003},
  abstract = { In this paper the authors study a pair of constructs in a
                  formal specification language that can be directly
                  translated into readable and relatively efficient code.
                  Those constructs are \emph{algebraic types} and (an extended
                  concept of logical) \emph{quantification}.  The translation
                  is guided by object oriented design patterns that makes the
                  synthesised code easily understandable by ordinary
                  developers.  Efficiency can be achieved thanks to the effort
                  of the user during the specification refinement process,
                  specification transformations and implementation issues of
                  the the design patterns.  },
  postscript = {http://babel.ls.fi.upm.es/~angel/papers/finalcopy-prole2003.ps.gz}
}
@inproceedings{hemo:2003:slam-rad,
  author = {{{\'{A}}ngel} Herranz and Juan Jos{\'{e}} {Moreno-Navarro}},
  title = {Rapid Prototyping and Incremental Evolution Using {SLAM}},
  booktitle = {14th IEEE International Workshop on Rapid System
                  Prototyping, RSP 2003},
  pages = {},
  year = {2003},
  month = jun,
  address = {San Diego, California, USA},
  abstract = { The paper shows the outlines of the SLAM system, that
                  allows for an effective use of Formal Methods (FM) in Rapid
                  Application Development (RAD) and other prototyping
                  processes.  The SLAM system, includes an expressive object
                  oriented specification language and a development
                  environment that, among other features, is able to generate
                  \emph{efficient} and \emph{readable} code in a high level
                  object oriented language (Java, C++, ...).  SLAM is able to
                  generate prototypes that can be used to validate the
                  requirements with the user.  The additional advantage is
                  that the prototype is not throw-away because most part of
                  the generated code can be directly used and the other part
                  can be optimised with the additional help of assertions
                  automatically included.  },
  postscript = {http://babel.ls.fi.upm.es/~angel/papers/finalcopy-rsp2003.ps.gz}
}
@inproceedings{hemo:2003:slam-xp,
  author = {{{\'{A}}ngel} Herranz and Juan Jos{\'{e}} {Moreno-Navarro}},
  title = {Formal Extreme (and Extremely Formal) Programming},
  booktitle = {4th International Conference on Extreme Programming and
                  Agile Processes in Software Engineering, XP 2003},
  pages = {88-96},
  year = {2003},
  editor = {Michele Marchesi and Giancarlo Succi},
  series = {LNCS},
  number = {2675},
  month = may,
  address = {Genova, Italy},
  abstract = { This paper is an exploratory work were the authors study
                  how the technology of Formal Methods (FM) can interact with
                  agile process in general and with Extreme Programming (XP)
                  in particular.  Our thesis is that most of XP practices
                  (\emph{pair programming}, \emph{daily build}, \emph{the
                  simplest design} or \emph{the metaphor}) are technology
                  independent and therefore can be used in FM based
                  developments. Additionally, other essential pieces like
                  \emph{test first}, \emph{incremental development} and
                  \emph{refactoring} can be improved by using FM.  In the
                  paper we explore in a certain detail those pieces: when you
                  write a formal specification you are saying \emph{what} your
                  code must do, when you write a test you are doing the same
                  so the idea is to use formal specifications as tests.
                  Incremental development is quite similar to the refinement
                  process in FM: specifications evolve to code maintaining
                  previous functionality.  Finally FM can help to remove
                  redundancy, eliminate unused functionality and transform
                  obsolete designs into new ones, and this is refactoring.  },
  pdf = {http://babel.ls.fi.upm.es/~angel/papers/finalcopy-xp03.pdf}
}
@phdthesis{susana:thesis,
  author = {Mu{\~{n}}oz-Hern{\'{a}}ndez, Susana},
  title = {A Negation System for {P}rolog},
  school = {Facultad de Inform{\'{a}}tica, Universidad Polit{\'{e}}cnica de Madrid},
  year = {2003}
}
@inproceedings{Susana_intneg_WFLP03,
  author = {Mu{\~{n}}oz-Hern{\'{a}}ndez, Susana and J. Mari{\~n}o and Moreno-Navarro, Juan Jos{\'e}},
  title = {Constructive Intensional Negation: a practical
                  implementation},
  booktitle = {Workshop on Functional and (Constraint) Logic Programming (WFLP)'03},
  optbooktitle = {WFLP'03},
  year = {2003}
}
@article{carro:herranz:marinno:sanchez:2003:novatica,
  author = {\'{A}ngel Herranz and Manuel Carro and Julio Mari{\~{n}}o and
                  Pablo {S{\'{a}}nchez Torralba}},
  title = {Almejas gigantes e interfaces de usuario},
  journal = {Nov{\'{a}}tica},
  year = 2003,
  volume = {1},
  number = 161,
  month = feb,
  pages = {70--73},
  note = {Contribuci{\'{o}}n a la columna "Programar es Crear"}
}

This file was generated by bibtex2html 1.98.