Formalizing the software development process
| cic.isFulltext | true | es |
| cic.isPeerReviewed | true | es |
| cic.lugarDesarrollo | Universidad Nacional de La Plata | es |
| cic.version | info:eu-repo/semantics/submittedVersion | es |
| dc.date.accessioned | 2016-08-09T13:52:57Z | |
| dc.date.available | 2016-08-09T13:52:57Z | |
| dc.identifier.uri | https://digital.cic.gba.gob.ar/handle/11746/3465 | |
| dc.title | Formalizing the software development process | en |
| dc.type | Documento de conferencia | es |
| dcterms.abstract | Object-oriented software development process, such as the Unified Process [Jacobson 99], Catalysis [D´Souza 98] and Fusion [Coleman 94] among others, is a set of activities needed to transform user’s requirements into a software system. A software development process typically consists of a set of software development artifacts together with a graph of tasks and activities. Software artifacts are the products resulting from software development, for example, a use case model, a class model or source code. Tasks are small behavioral units that usually results in a software artifact. Examples of tasks are construction of a use case model, construction of a class model and writing code. Activities (or workflows) are units that are larger than a task. Activities generally include several tasks and software artifacts. Examples of activities are requirements, analysis, design and implementation.\nModern software development processes are iterative and incremental, they repeat over a series of iterations making up the life cycle of a system. Each iteration takes place over time and it consists of one pass through the requirements, analysis, design, implementation and test activities, building a number of different artifacts. All these artifacts are not independent. They are related to each other, they are semantically overlapping and together represent the system as a whole. Elements in one artifact have trace dependencies to other artifacts.\nFor instance, a use case (in the use-case model) can be traced to a collaboration (in the design model) representing its realization. | en |
| dcterms.creator.author | Giandini, Roxana Silvia | es |
| dcterms.creator.author | Baum, Gabriel | es |
| dcterms.creator.author | Pons, Claudia Fabiana | es |
| dcterms.description | Eje: Ingeniería del Software | es |
| dcterms.extent | 4 p. | es |
| dcterms.identifier.url | Recurso Completo | es |
| dcterms.isPartOf.issue | III Workshop de Investigadores en Ciencias de la Computación | es |
| dcterms.isPartOf.series | Workshop de Investigadores en Ciencias de la Computación | es |
| dcterms.issued | 2001-05 | |
| dcterms.language | Inglés | es |
| dcterms.license | Attribution 4.0 International (BY 4.0) | es |
| dcterms.subject | Formalizing | en |
| dcterms.subject | Software Development Process | en |
| dcterms.subject | SOFTWARE ENGINEERING | en |
| dcterms.subject | Software development | en |
| dcterms.subject.materia | Ciencias de la Computación | es |
Archivos
Bloque original
1 - 1 de 1
Cargando...
- Nombre:
- Pons - Formalizing the software.pdf-PDFA.pdf
- Tamaño:
- 182.85 KB
- Formato:
- Adobe Portable Document Format
- Descripción:
- Documento completo