Tesi di laurea Tesi di laurea Pubblica la tua tesi Guide per tesi e cv Come scrivere una tesi. Ricerca avanzata. Metti nel carrello. Lista dei desideri. Scegli il punto di consegna e ritira quando vuoi Scopri come. This is a detailed summary of research on design rationale providing researchers in software engineering with an excellent overview of the subject.
Professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle. Software engineering is still primarily a human-based activity and rationale management is concerned with making design and development decisions explicit to all stakeholders involved. Recensioni degli utenti Scrivi una nuova recensione su Rationale Management in Software Engineering e condividi la tua opinione con altri utenti.
- VHDL: Programming By Example.
- Download Rationale Management In Software Engineering ;
- Features & Highlights.
- The Judgment of Caesar: A Novel of Ancient Rome (St. Martins Minotaur Mystery).
Prodotti correlati. Requirements-Engineering und -Management. Software Design Decoded. While argumentation formats can be traced back to Stephen Toulmin 's work in the s  datums, claims, warrants, backings and rebuttals, the origin of design rationale can be traced back to W. Several variants on IBIS have since been proposed. Not all successful DR approaches involve structured argumentation. For example, Carroll and Rosson's Scenario-Claims Analysis approach  captures rationale in scenarios that describe how the system is used and how well the system features support the user goals.
Rationale Management in Software Engineering | SpringerLink
Carroll and Rosson's approach to design rationale is intended to help designers of computer software and hardware identify underlying design tradeoffs and make inferences about the impact of potential design interventions. There are a number of ways to characterize DR approaches. Some key distinguishing features are how it is captured, how it is represented, and how it can be used. Rationale capture is the process of acquiring rationale information to a rationale management.
The choice of design rationale representation is very important to make sure that the rationales we capture is what we desire and we can use efficiently. According to the degree of formality, the approaches that are used to represent design rationale can be divided into three main categories: informal, semiformal, or formal. However, these descriptions make it hard for automatic interpretation or other computer-based supports.
Rationale Management in Software Engineering
In the formal representation, the rationale must be collected under a strict format so that the rationale can be interpreted and understood by computers. However, due to the strict format of rationale defined by formal representations, the contents can hardly be understood by human being and the process of capturing design rationale will require more efforts to finish, and therefore becomes more intrusive.
Semiformal representations try to combine the advantages of informal and formal representations. On one hand, the information captured should be able to be processed by computers so that more computer based support can be provided. On the other hand, the procedure and method used to capture information of design rationale should not be very intrusive.
In the system with a semiformal representation, the information expected is suggested and the users can capture rationale by following the instructions to either fill out the attributes according to some templates or just type into natural language descriptions. Design rationale has the potential to be used in many different ways. One set of uses, defined by Burge and Brown ,  are:. DR is used by research communities in software engineering, mechanical design, artificial intelligence, civil engineering, and human-computer interaction research. In software engineering, it could be used to support the designers ideas during requirement analysis, capturing and documenting design meetings and predicting possible issues due to new design approach.
It also help the designers to understand and respect each other's ideas and resolve any possible issues. The DR can also be used by the project managers to maintain their project plan and the project status up to date. Also, the project team members who missed a design meeting can refer back the DR to learn what was discussed on a particular topic.
The unresolved issues captured in DR could be used to organize further meetings on those topics. Design rationale helps the designers to avoid the same mistakes made in the previous design. This can also be helpful to avoid duplication of work.
There are several books and articles that provide excellent surveys of rationale approaches applied to HCI,  Engineering Design  and Software Engineering. From Wikipedia, the free encyclopedia. The Uses of Argument. Cambridge: Cambridge University Press.