1.

Record Nr.

UNISA996389285803316

Autore

Puteanus Erycius <1574-1646.>

Titolo

ErycI Puteani Suada Attica, sive Orationum selectarum syntagma [[electronic resource] ] : Item palæstra bonæ mentis, prorsus innovata

Pubbl/distr/stampa

Oxoniæ, : Excudebat Guilielmus Turner, impensis Tho : Robinson, 1640

Descrizione fisica

[16], 534, [2] p

Soggetti

Speeches, addresses, etc., Latin (Medieval and modern)

Lingua di pubblicazione

Latino

Formato

Materiale a stampa

Livello bibliografico

Monografia

Note generali

The last leaf is blank.

"ErycI Puteani Palaestra bonæ mentis" has a divisional title page; pagination and register are continuous.

Reproduction of the original in Wadham College. Library.

Sommario/riassunto

eebo-0185



2.

Record Nr.

UNINA9911007081203321

Autore

Holt Jon

Titolo

Model-based requirements engineering / / Jon Holt, Simon A. Perry and Mike Brownsword

Pubbl/distr/stampa

Stevenage, Herfordshire, U.K., : Institution of Engineering and Technology, 2012

ISBN

1-61344-642-X

1-283-37886-8

9786613378866

1-84919-488-2

Descrizione fisica

1 online resource (357 p.)

Collana

IET Professional applications of computing series ; ; 9

Altri autori (Persone)

PerrySimon A

BrownswordMike

Disciplina

620.001/171

620.001171

Soggetti

Computer software - Development

Lingua di pubblicazione

Inglese

Formato

Materiale a stampa

Livello bibliografico

Monografia

Note generali

Description based upon print version of record.

Nota di bibliografia

Includes bibliographical references and index.

Nota di contenuto

pt. 1. Introduction -- pt. 2. Concepts -- pt. 3. Realisation.

Sommario/riassunto

This book provides a hands-on introduction to model-based requirementsengineering and management by describing a set of views that form the basisfor the approach. These views take into account each individual requirement interms of its description, but then also provide each requirement with meaning byputting it into the correct 'context'. A requirement that has been put into a contextis known as a 'use case' and may be based upon either stakeholders or levelsof hierarchy in a system. Each use case must then be analysed and validated bydefining a combination of scenarios and formal mathematica