Formalizing the software development process
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 s...
Guardado en:
| Autores principales: | , , |
|---|---|
| Formato: | Objeto de conferencia |
| Lenguaje: | Inglés |
| Publicado: |
2001
|
| Materias: | |
| Acceso en línea: | http://sedici.unlp.edu.ar/handle/10915/21725 |
| Aporte de: |
| id |
I19-R120-10915-21725 |
|---|---|
| record_format |
dspace |
| institution |
Universidad Nacional de La Plata |
| institution_str |
I-19 |
| repository_str |
R-120 |
| collection |
SEDICI (UNLP) |
| language |
Inglés |
| topic |
Ciencias Informáticas SOFTWARE ENGINEERING Software development Formalizing Software Development Process |
| spellingShingle |
Ciencias Informáticas SOFTWARE ENGINEERING Software development Formalizing Software Development Process Pons, Claudia Giandini, Roxana Silvia Baum, Gabriel Alfredo Formalizing the software development process |
| topic_facet |
Ciencias Informáticas SOFTWARE ENGINEERING Software development Formalizing Software Development Process |
| 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.
Modern 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.
For instance, a use case (in the use-case model) can be traced to a collaboration (in the design model) representing its realization. |
| format |
Objeto de conferencia Objeto de conferencia |
| author |
Pons, Claudia Giandini, Roxana Silvia Baum, Gabriel Alfredo |
| author_facet |
Pons, Claudia Giandini, Roxana Silvia Baum, Gabriel Alfredo |
| author_sort |
Pons, Claudia |
| title |
Formalizing the software development process |
| title_short |
Formalizing the software development process |
| title_full |
Formalizing the software development process |
| title_fullStr |
Formalizing the software development process |
| title_full_unstemmed |
Formalizing the software development process |
| title_sort |
formalizing the software development process |
| publishDate |
2001 |
| url |
http://sedici.unlp.edu.ar/handle/10915/21725 |
| work_keys_str_mv |
AT ponsclaudia formalizingthesoftwaredevelopmentprocess AT giandiniroxanasilvia formalizingthesoftwaredevelopmentprocess AT baumgabrielalfredo formalizingthesoftwaredevelopmentprocess |
| bdutipo_str |
Repositorios |
| _version_ |
1764820464844144640 |