Registro completo de metadatos
| Campo DC | Valor | Lengua/Idioma |
|---|---|---|
| dc.provenance | Universidad de Buenos Aires. Facultad de Ciencias Económicas | - |
| dc.creator | Giandini, Roxana Silvia | - |
| dc.creator | Baum, Gabriel | - |
| dc.creator | Pons, Claudia Fabiana | - |
| dc.date | 2001-05 | - |
| dc.date.accessioned | 2019-06-19T20:37:32Z | - |
| dc.date.available | 2019-06-19T20:37:32Z | - |
| dc.date.issued | 2001-05 | - |
| dc.identifier | http://digital.cic.gba.gob.ar/handle/11746/3465 | - |
| dc.identifier | Recurso Completo | - |
| dc.identifier.uri | http://rodna.bn.gov.ar/jspui/handle/bnmm/327490 | - |
| dc.description | 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. | - |
| dc.description | Eje: Ingeniería del Software | - |
| dc.format | application/pdf | - |
| dc.format | 4 p. | - |
| dc.language | eng | - |
| dc.rights | info:eu-repo/semantics/openAccess | - |
| dc.rights | Attribution 4.0 International (BY 4.0) | - |
| dc.source | reponame:CIC Digital (CICBA) | - |
| dc.source | instname:Comisión de Investigaciones Científicas de la Provincia de Buenos Aires | - |
| dc.source | instacron:CICBA | - |
| dc.source.uri | http://digital.cic.gba.gob.ar/handle/11746/3465 | - |
| dc.source.uri | Recurso Completo | - |
| dc.subject | Ciencias de la Computación | - |
| dc.title | Formalizing the software development process | - |
| dc.type | info:eu-repo/semantics/conferenceObject | - |
| dc.type | info:eu-repo/semantics/submittedVersion | - |
| dc.type | info:ar-repo/semantics/documentoDeConferencia | - |
| Aparece en las colecciones: | Facultad de Ciencias Económicas. UBA | |
Ficheros en este ítem:
No hay ficheros asociados a este ítem.