Dissertations / Theses on the topic 'Design rationale'
To see the other types of publications on this topic, follow the link: Design rationale.
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Design rationale.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Vadhavkar, Sanjeev Sureshchandra. "Augementing design patterns with design rationale." Thesis, Massachusetts Institute of Technology, 1997. http://hdl.handle.net/1721.1/43291.
Full textAbstract:
Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 1997.Includes bibliographical references (leaves 100-103).
by Sanjeev Sureshchandra Vadhavkar.
M.S.
2
Burge, Janet E. "Software Engineering Using design RATionale." Link to electronic thesis, 2005. http://www.wpi.edu/Pubs/ETD/Available/etd-050205-085625/.
Full textAbstract:
Dissertation (Ph.D.) -- Worcester Polytechnic Institute.Keywords: software engineering; inference; knowledge representation; software maintenance; design rationale. Includes bibliographical references (p. 202-211).
3
Remakrishnam, Sailesh. "Design rationale representation and testing." Thesis, This resource online, 1995. http://scholar.lib.vt.edu/theses/available/etd-01312009-063423/.
Full text
4
Malloy, John William. "DOCUMENTING DESIGN RATIONALE TO PROMOTE LEARNING." Miami University / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=miami1398945540.
Full text
5
Shum, Simon J. "A cognitive analysis of design rationale representation." Thesis, University of York, 1991. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.306290.
Full text
6
Fuller, Charles E. Russell Douglas V. "A design rationale capture using REMAP/MM /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1994. http://handle.dtic.mil/100.2/ADA283534.
Full text
7
Fuller, Charles E., and Douglas V. Russell. "A design rationale capture using REMAP/MM." Thesis, Monterey, California. Naval Postgraduate School, 1994. http://hdl.handle.net/10945/30937.
Full textAbstract:
Every year the Department of Defense (DoD) spends between 24 and 32 billion dollars on software alone, with maintenance costs comprising the majority of this figure. Recent studies have indicated that an effective solution to help curtail the large maintenance cost is by capturing the rationale which was used to create the systems requirements and designs, and using this information throughout the life cycle. This thesis explores the use of the REMAP/MM model for the purposes of capturing these rationale, and presents a detailed example of how REMAP/MM utilizes multimedia artifacts as tools in various systems development activities.
8
Kim, NaJung. "Rationale design of polymeric siRNA delivery systems." Diss., University of Iowa, 2011. https://ir.uiowa.edu/etd/1237.
Full textAbstract:
Regulation of gene expression using small interfering RNA (siRNA) is a promising strategy for research and treatment of numerous diseases. However, siRNA cannot easily cross the cell membrane due to its inherent instability, large molecular weight and anionic nature. For this reason, a carrier that protects, delivers and unloads siRNA is required for successful gene silencing. The goal of this research was to develop a potential siRNA delivery system for in vitro and in vivo applications using cationic polymers, chitosan and polyethylenimine (PEI), poly(ethylene glycol) (PEG), mannose, and poly(D,L-lactic-co-glycolic acid) (PLGA). Furthermore, the delivery system was constructed in two different ways to explore the effect of mannose location in the structure. In the first approach, mannose and PEG were directly conjugated to the chitosan/PEI backbone, while mannose was connected to the chitosan/PEI backbone through PEG spacer in the second approach. First, the ability of modified chitosan polymers to complex and deliver siRNA for gene silencing was investigated. Despite the modified chitosan polymers successfully formed nanoplexes with siRNA, entered target cells and reduced cytotoxicity of unmodified chitosan, they showed limited gene silencing efficiency. For this reason, modified PEIs were examined to improve in vitro gene knockdown. The modified PEI polymers also complexed with siRNA and facilitated endocytosis of the nanoplexes. In addition, the modifications reduced inherent cytotoxicity of unmodified PEI without compromising the gene silencing efficiency on both mRNA and protein levels. Interestingly, we found that complexation of siRNA with PEI-PEG-mannose resulted in higher cell uptake and gene silencing than complexes made with mannose-PEI-PEG. Finally, the effect of sustained release of the mannosylated pegylated PEI/siRNA nanoplexes on gene silencing was tested by encapsulating the nanoplexes within PLGA microparticles. The modified PEIs enhanced the entrapment efficiency of siRNA into the particles and resulted in reduced initial burst followed by sustained release. Incorporating the modified PEIs increased cellular uptake of siRNA, whereas it did not enhance in vitro gene knockdown efficiency due to the sustained release properties. The modified PEIs reduced the in vitro cytotoxicity and in vivo hepatotoxicity of the PLGA microparticles. In addition, encapsulating the nanoplexes into PLGA microparticles further reduced the cytotoxicity of PEI. Throughout the study, the second structure was proven more efficacious than the first structure in cellular uptake, gene silencing, siRNA encapsulation, and sustained release. We have developed novel polymeric siRNA delivery systems that enhance delivery efficiency and cellular uptake of siRNA. They have great potential for utility as a long-acting siRNA delivery system in biomedical research.
9
af, Malmborg Solith. "Designing dialogue : Using design rationale to advise public participation." Thesis, Linköpings universitet, Malmstens Linköpings universitet, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-176370.
Full textAbstract:
This thesis takes an interdisciplinary approach to research how design rationale may improve practices for participatory design in urban planning. Knowledge on sustainable development, participatory planning in public sector, design rationale and innovation are brought together to form a cohesive understanding for the matter of citizen dialogue and participation. To further gain knowledge on the subject a case study is done following the planning of a consultation at the urban planning office in Norrköping by participatory observations. Furthermore, semi-structured interviews are conducted with civil servants from Norrköping and Norrtälje, discussing the theme of citizen dialogue and municipal capacity and competence for its performance. The knowledge contributions addresses the specific case study at first hand, but are also applicable in some general sense. The study shows that design rationale can be of use and inspiration to address issues of culture and mental models in public sector, as these as believed to stand in the way of forming a more innovative and adaptive public sector that can design better practices for dialogue and participation. Design thinking and attitude can bring openness and human centred perspectives, among other things, to public organisations. For the case study in question it is suggested that the urban planning office would benefit from implementing and trying out ways of working that are more in line with design thinking and attitude. It is also suggested that they might benefit from employing an experienced designer to be part of planning procedures, as expert designers can adapt methods and tools for participation to design case specific activities. To employ a more case specific and local approach to participatory practices is proposed to bring better results, both in terms of its democratic breakthrough as well as its impact on social sustainability. Overall, this thesis offers contributions to design knowledge, knowledge that in turn can be important for the area of sustainable development at large.
10
Lara, Silvana Maria Affonso de. "Um suporte à captura informal de design rationale." Universidade de São Paulo, 2005. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-08112006-134155/.
Full textAbstract:
Durante o processo de desenvolvimento de software, uma grande quantidade de documentos é gerada com o propósito de registrar as experiências e as decisões relacionadas ao projeto de software. Apesar do esforço empregado na documentação de tais informações, muitas vezes esses documentos não contêm informações suficientes e necessárias para o completo entendimento do software, para a reutilização das experiências adquiridas e a recuperação do processo de tomada de decisão. De maneira geral, apenas as decisões finais a respeito do projeto são documentadas. O Design Rationale (DR) consiste das informações adicionais aos documentos padrões em um processo de desenvolvimento de software, facilitando sua compreensão, manutenção e reuso. Na literatura, muitas pesquisas referem-se aos problemas relacionados à atividade de captura de DR, principalmente no que diz respeito à sobrecarga de trabalho durante o momento de design. O desenvolvimento de mecanismos que facilitem a captura de Design Rationale durante a elaboração de artefatos de software é ainda um desafio. No contexto de ferramentas CASE (Computer Aided Software Engineering), cuja utilização enfrenta grande resistência por parte de seus usuários (desenvolvedores), torna-se imprescindível a aplicação de técnicas para garantir a máxima usabilidade dessas ferramentas, de forma a minimizar a resistência à sua utilização. O paradigma da computação ubíqua trouxe grandes mudanças ao desenvolvimento de aplicações da Ciência da Computação, visto que estas aplicações são transparentes, apresentam um comportamento contínuo e ciente de contexto, e visam tornar a interação com o usuário a mais natural possível. Diante desse contexto, a adoção de mecanismos de computação ubíqua na atividade de captura de DR torna-se uma abordagem de interesse científico. O uso de mecanismos de computação ubíqua faz com que a captura das informações e decisões relacionadas ao projeto de software seja realizada de forma mais natural, reduzindo a sobrecarga do uso de uma ferramenta que necessite de tempo adicional para o armazenamento do DR, seja durante o processo de tomada de decisões ou depois do mesmo. Assim sendo, o trabalho realizado neste projeto de mestrado consistiu na reengenharia de uma ferramenta de suporte a DR e à sua integração com um editor gráfico que permite a escrita manual e oferece um serviço de reconhecimento de escrita, de modo a prover uma maneira mais flexí?vel para a entrada de dados e que pode ser utilizada em dispositivos com diferentes tamanhos e características, tais como Tablet PCs e lousas eletrônicasDuring the process of software development, a great amount of documents is generated with the purpose of registering experiences and decisions related to software project. Despite the effort made aiming at documenting of such information, in general, these documents do not contain enough and necessary information for the complete understanding of the software, for the reuse of the acquired experiences and the recovery of the process of decision making. In general, only the final decisions regarding the project are registered. The Design Rationale (DR) consists of the additional information to standards documents in a process of software development, aiming to facilitate its understanding, maintenance and reuse. In literature, many researches reveal the problems related to the activity of DR capture, especially related to the work overload during the moment of design. The development of mechanisms to facilitate the Design Rationale capture, during the elaboration of software artifacts, is still a challenge. In the context of CASE (Computer Aided Engineering Software) tools usage, users (developers) present great resistance, so the application of techniques to achieve the maximum usability in the tools becomes essential, aiming to minimize the resistance to their adoption. The paradigm of ubiquitous computing brought great innovations to the development of applications, since the applications are transparent; they present a continuous and aware context behavior, and aim the user-computer interaction become the most natural as possible. For that reason, the adoption of ubiquitous computing mechanisms in the activity of DR capture becomes an approach of scientific interest. The use of the ubiquitous computing makes the capture of the information and decisions related to software project be carried out on a more natural way, reducing the overload of using a tool that needs additional time for the DR storage, either during the process of making decisions or just after. This master project consisted of re-engineering of a DR tool and its integration with a graphical editor. The editor allows handwriting and offers a service of writing recognition in order to provide a more flexible way for the data entry and can be used in devices of different sizes and characteristics, such as Tablet PCs and electronic blackboards.
11
Tang, Antony Shui Sum, and n/a. "A rationale-based model for architecture design reasoning." Swinburne University of Technology, 2007. http://adt.lib.swin.edu.au./public/adt-VSWT20070319.100952.
Full textAbstract:
Large systems often have a long life-span and their system and software architecture design comprise many intricately related elements. The verification and maintenance of these architecture designs require an understanding of how and why the system are constructed. Design rationale is the reasoning behind a design and it provides an explanation of the design. However, the reasoning is often undocumented or unstructured in practice. This causes difficulties in the understanding of the original design, and makes it hard to detect inconsistencies, omissions and conflicts without any explanations to the intricacies of the design. Research into design rationale in the past has focused on argumentation-based design deliberations. Argumentation-based design rationale models provide an explicit representation of design rationale. However, these methods are ineffective in communicating design reasoning in practice because they do not support tracing to design elements and requirements in an effective manner.
In this thesis, we firstly report a survey of practising architects to understand their
perception of the value of design rationale and how they use and document this knowledge.
From the survey, we have discovered that practitioners recognize the importance of documenting design rationale and frequently use them to reason about their design choices. However, they have indicated certain barriers to the use and documentation of design rationale. The results have indicated that there is no systematic approach to using and capturing design rationale in current architecture design practice. Using these findings, we address the issues of representing and applying architecture design rationale.
We have constructed a rationale-based architecture model to represent design rationale,
design objects and their relationships, which we call Architecture Rationale and
Element Linkage (AREL). AREL captures both qualitative and quantitative rationale for
architecture design. Quantitative rationale uses costs, benefits and risks to justify architecture
decisions. Qualitative rationale documents the issues, arguments, alternatives and
tradeoffs of a design decision. With the quantitative and qualitative rationale, the AREL
model provides reasoning support to explain why architecture elements exist and what
assumptions and constraints they depend on. Using a causal relationship in the AREL
model, architecture decisions and architecture elements are linked together to explain the reasoning of the architecture design. Architecture Rationalisation Method (ARM) is a
methodology that makes use of AREL to facilitate architecture design. ARM uses cost,
benefit and risk as fundamental elements to rank and compare alternative solutions in the decision making process.
Using the AREL model, we have proposed traceability and probabilistic techniques
based on Bayesian Belief Networks (BBN) to support architecture understanding and
maintenance. These techniques can help to carry out change impact analysis and rootcause analysis. The traceability techniques comprise of forward, backward and evolution tracings. Architects can trace the architecture design to discover the change impacts by analysing the qualitative reasons and the relationships in the architecture design. We have integrated BBN to AREL to provide an additional method where probability is used to evaluate and reason about the change impacts in the architecture design. This integration provides quantifiable support to AREL to perform predictive, diagnostic and combined reasoning.
In order to align closely with industry practices, we have chosen to represent the
rationale-based architecture model in UML. In a case study, the AREL model is applied
retrospectively to a real-life bank payment systems to demonstrate its features and applications.
Practising architects who are experts in the electronic payment system domain
have been invited to evaluate the case study. They have found that AREL is useful in
helping them understand the system architecture when they compared AREL with traditional design specifications. They have commented that AREL can be useful to support the verification and maintenance of the architecture because architects do not need to reconstruct or second-guess the design reasoning.
We have implemented an AREL tool-set that is comprised of commercially available
and custom-developed programs. It enables the capture of architecture design and its
design rationale using a commercially available UML tool. It checks the well-formedness
of an AREL model. It integrates a commercially available BBN tool to reason about the
architecture design and to estimate its change impacts.
12
Tang, Antony Shui Sum. "A rationale-based model for architecture design reasoning." Australasian Digital Thesis Program, 2007. http://adt.lib.swin.edu.au/public/adt-VSWT20070319.100952/index.html.
Full textAbstract:
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2007.A thesis submitted in total fulfillment of the requirements of for the degree of Doctor of Philosophy, Faculty of ICT, Swinburne University of Technology, 2007. Typescript. Bibliography p. 214-226.
13
Haynes, Steven R. "Explanation in information systems : a design rationale approach." Thesis, London School of Economics and Political Science (University of London), 2002. http://etheses.lse.ac.uk/2652/.
Full textAbstract:
This dissertation investigates the relationship between the information systems (IS) development context, and the context in which such systems are used. Misunderstandings and ambiguities emerge in the space between these contexts and often result in construction of systems that fail to meet the requirements and expectations of their intended users. This study explores this problem using an approach derived from three largely separate and distinct fields: explanation facilities in information systems, theories of explanation, and design rationale. Explanation facilities are typically included in knowledge-based information systems, where their purpose is to provide system users with the underlying reasons for why the system reaches a particular conclusion or makes a particular recommendation. Prior research suggests that the presence of an explanation facility leads to increased acceptance of these conclusions and recommendations, therefore enhancing system usability. Theory of explanation is a field of study in which philosophers attempt to describe the unique nature of explanation and to identify criteria for explanation evaluation. Design rationale research is concerned with the capture, representation, and use of the deep domain and artefact knowledge that emerges from the design process. The design rationale approach goes beyond specification and suggests that to understand a system requires knowledge of the arguments that led to its realisation. This study proposes a model of IS explanation structure and content derived from formal theories of explanation with a method for obtaining this content based on design rationale. The study has four goals: to derive a theory of explanation specific to the domain of information systems; to examine this definition empirically through a study involving IS development and management professionals; to investigate in a case study whether the information needed to populate the explanation model can be captured using design rationale techniques; and construction of prototype software to deliver explanations per the proposed framework.
14
BERARDI, RITA CRISTINA GALARRAGA. "DESIGN RATIONALE IN THE TRIPLIFICATION OF RELATIONAL DATABASES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2015. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=27082@1.
Full textAbstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIROCOORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO
PROGRAMA DE EXCELENCIA ACADEMICA
DOUTORADO SANDUÍCHE NO EXTERIOR
Uma das estratégias mais populares para publicar dados estruturados na Web é expor bases de dados relacionais (BDR) em formato RDF. Esse processo é chamado BDR-para-RDF ou triplificação. Além disto, princípios de Linked Data oferecem vários guias para dar suporte a este processo. Existem duas principais abordagens para mapear bases de dados relacionais para RDF: (1) a abordagem de mapeamento direto, onde o esquema das bases de dados é diretamente mapeado para um esquema RDF, e (2) a abordagem de mapeamento customizado, onde o esquema RDF pode ser significativamente diferente do esquema original da base de dados relacional. Em ambas abordagens, existem vários desafios relacionados tanto com a publicação quanto com o uso de dados em RDF originados de bases de dados relacionais. Esta tese propõe a coleta de design rationale como uma valiosa fonte de informação para minimizar os desafios do processo de triplificação. Essencialmente, a coleta de design rationale melhora a consciência sobre as ações feitas no mapeamento da base de dados relacional para um conjunto de dados no formato RDF. As principais contribuições da tese são: (1) um modelo de design rationale (DR) adequado para o processo de BDR-para- RDF, independente da abordagem utilizada (direta ou customizada); (2) a integração de um modelo de DR para um processo que segue a abordagem direta de BDR-para-RDF e para um processo que segue a abordagem customizada usando a linguagem R2RML; (3) o uso do DR coletado para melhorar recomendações de reuso de vocabulários existentes através de algoritmos de Ontology Matching.
One of the most popular strategies to publish structured data on the Web is to expose relational databases (RDB) in the RDF format. This process is called in RDB-to-RDF or triplification. Furthermore, the Linked Data principles offer useful guidelines for this process. Broadly stated, there are two main approaches to map relational databases into RDF: (1) the direct mapping approach, where the database schema is directly mapped to an RDF schema; and (2) the customized mapping approach, where the RDF schema may significantly differ from the original database schema. In both approaches, there are challenges related to the publication and to the consumption of the published data. This thesis proposes the capture of design rationale as a valuable source of information to minimize the challenges in RDB-to-RDF processes. Essentially, the capture of design rationale increases the awareness about the actions taken over the relational database to map it as an RDF dataset. The main contributions of this thesis are: (1) a design rationale (DR) model adequate to RDB-to-RDF processes, independently of the approach (direct or customized) followed; (2) the integration of a DR model in an RDB-to-RDF direct mapping process and in an RDB-to-RDF customized mapping process using the R2RML language; (3) the use of the DR captured to improve the recommendations for vocabularies to reuse.
15
SANTOS, DANIELE REIS GONZAGA. "SUPPORT FOR RECORDING AND USING DESIGN RATIONALE FOR WEB APPLICATION DESIGN." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2007. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=10714@1.
Full textAbstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIROTodo projetista realiza, ao projetar algum artefato, uma seqüência de raciocínio e de tomadas de decisão de projeto que resultam neste artefato. A captura do raciocínio utilizado pelo projetista durante a modelagem de uma aplicação raramente é realizada. Tal raciocínio é denominado na literatura como Design Rationale, e a dificuldade de sua captura e uso é atribuída em grande parte à falta de ferramentas adequadas a este fim. Tais ferramentas devem ser integradas ao processo de design, interrompendo minimamente o raciocínio do projetista/desenvolvedor que está construindo a aplicação. Estas ferramentas devem também permitir o reuso de soluções, auxiliando o projetista/desenvolvedor a melhorar a qualidade de design de seus artefatos. O objetivo do trabalho realizado é integrar a captura e uso de design rationale a um ambiente de prototipação de aplicações hipermídia, além de permitir o reuso de designs registrados. Como resultado, é apresentado o ambiente integrado HyperDE+DR, baseado no ambiente HyperDE para prototipação de aplicações hipermídia e na abordagem Kuaba para representação e uso de design rationale. O ambiente integrado HyperDE+DR desenvolvido e implementado gera e registra automaticamente decisões de design tomadas durante a construção dos artefatos pelo projetista/desenvolvedor. Questões e idéias são geradas e respondidas também automaticamente pelo ambiente, de acordo com os métodos de design usados pelo ambiente - OOHDM e SHDM -, o que facilita o processo de captura do design rationale. Adicionalmente, o ambiente possibilita o reuso de design rationales, permitindo a integração ou reutilização de designs para a construção de novas aplicações, podendo torná-las mais completas, consistentes e reduzir o esforço de desenvolvimento.
Every designer follows some line of reasoning, and makes several decisions when designing an artifact, which is the final result of this decision process. This design reasoning and decision structure, commonly called Design Rationale, is rarely captured and recorded. The reasons for this seem to be due to the lack of appropriate tools, which should capture the Design Rationale in an unobtrusive way, allowing the designer to focus on the design itself. Such tools should also allow reusing previous design solutions, helping the designer/developer to improve the quality of the solution. The goal of this dissertation is to provide means to capture, record and use Design rationale within a prototyping environment for hypermedia applications. As result, we present the HyperDE+DR environment, which combines the HyperDE environment with the Kuaba approach for recording Design Rationale. The HyperDE+DR environment automatically generates and records design decisions made by the designer during the development process. Questions and ideas are automatically generated and tentatively answered, to be reviewed later by the designer by following the OOHDM and SHDM design methods that underlie the original HyperDE environment. In addition, HyperDE+DR supports Design Rationale use, by allowing integration of previous design rationales into a design being developed. This allows improving the completeness and consistency of the resulting design, also lowering development costs.
16
Van, Schaik Jeroen Robbert. "A framework for design rationale capture and use during geometry design." Thesis, University of Southampton, 2014. https://eprints.soton.ac.uk/371822/.
Full textAbstract:
Despite broad agreement on the utility of design rationale use and capture, a review of the relevant literature shows that industrial usage remains limited, especially during geometry design. An initial field study confirmed low design rationale capture during the geometry design stage. The lack of linking between design rationale and geometry models is identified as a factor holding back design rationale capture. A toolset is presented to link entities in geometry models to design rationale, allowing the creation of design rationale referring to a specific geometry design decision. Using the design rationale links it is possible to create graphs of the structure of geometry models and attached rationale. Furthermore the presence and quantity of design rationale can be displayed as a coloured overlay on the geometry. The toolset has been tested by 7 groups of student-designers, and although the uptake of the design rationale linking tool by the users was low, results show that groups using the tool captured relatively more design rationale during geometry design, although reservations have to be made regarding to self-selection bias. The study shows that the availability of design rationale linking tools is not by itself enough to improve design rationale capture during geometry design.
17
Haghighatkhah, A. (Alireza). "An argumentation-based design rationale approach to reflective design of persuasive systems." Master's thesis, University of Oulu, 2014. http://urn.fi/URN:NBN:fi:oulu-201401141004.
Full textAbstract:
Technology has significantly influenced human lifestyle, industrial sector, businesses and the way people interact with each other. Evidently, information technology is no longer a neutral tool. Intentionally or otherwise, system designers and developers influence our attitudes and/or behaviors for varying motives including promotion of socially valued activities. However, promoting moral values using technologies raises several ethical concerns. For example, what might be ethical for one person could be completely unethical from the other. Moral justification of persuasive systems requires involving all stakeholders in a rationale and open argumentation process. The moral issues are difficult to perceive and comprehend and more importantly, the entire process involves different stakeholders with conflicting viewpoints. Therefore, it is challenging to find an optimal solution to satisfy all stakeholders and argumentation process encompasses both cognitive and social complexities.
In an attempt to address the problem; this study outlines an argumentation-based design rationale application. The proposed solution is to mitigate social and cognitive complexities pertaining to moral justification process. The main aim of this thesis is to study construction and evaluation of the said solution in order to facilitate reflective design and evaluation of persuasive information systems. This study follows formal problem-centric approach and was conducted by applying Design Science Research (DSR) methodology. We carried out an experiment to examine socio-technical aspects of the designed artifact focusing on system usefulness and its effect on the problem context. System usefulness of the artifact was studied by analyzing perceived usefulness and usability of the solution from participants’ opinions.
The intended implication of this study was to examine that argumentation-based design rationale could potentially decrease complexity of argumentation process. Likewise, it could lead to improved communication and reasoning between stakeholders. These aspects do not guarantee design and development of information systems that are morally justifiable by all standards. However, it is suggested that there are certain prerequisites that are needed for moral justification of persuasive information systems. From a practical perspective, we developed and evaluated a discourse-supported application that effectively establishes rationale and autonomous communication process. Theoretically, we acknowledge that three major aspects of argumentation-based design rationale applications including communication, reasoning and problem comprehension capabilities have a significant influence on mitigating social and cognitive complexities of ethical reflection relating to persuasive information systems.
18
Sagoo, Jeevan. "Design rationale for the regulatory approval of medical devices." Thesis, Cranfield University, 2012. http://dspace.lib.cranfield.ac.uk/handle/1826/8014.
Full textAbstract:
Design rationale is a methodology aimed at capturing and representing design decisions according to a designated structure. Additionally, these design decisions and their underlying arguments can be made available for examination at a later date. The literature review identified that there is currently a lack of information describing the use of design rationale methods and computational support tools with the medical device domain. Furthermore, the review of literature has also recognised that there are no existing guidelines available for medical device manufacturers and regulatory authorities to follow in order to capture and represent the design decisions in the case of medical devices. Medical devices are instruments which are used for diagnosis, screening, monitoring, or the treating of patients suffering from disease, injury, or disability. Medical devices are products that require rigorous regulation before they can be placed onto the market. If problems are encountered with a device once it has been placed onto the market, the device is recalled by the relevant regulatory authority. Device recalls can often result in the device manufacturers having to evaluate the design decisions that were made during the product development stages in order to address the reported problems and implement a solution. As a result, medical device manufacturers can incur unexpected rework and/or redesign costs, and in even more severe circumstances, incur high litigation costs. This research; reviews the state-of-the-art in design rationale and identifies its key capabilities, analyses design rationale’s feasibility for use with the medical device domain, identifies the regulatory approval processes for medical devices and compares them, analyses the possibilities of utilising design rationale with the regulatory approval of medical devices, and develops a set of guidelines. The guidelines detail the necessary steps that are required to capture and represent the design decisions for medical devices. The utility of this contribution has been verified through the process of validation with experts and researchers.
19
Ryskamp, Jordan David. "Developing Intelligent Engineering Collaboration Tools Through the use of Design Rationale." BYU ScholarsArchive, 2010. https://scholarsarchive.byu.edu/etd/2428.
Full textAbstract:
This thesis presents a new method that improves upon the existing approaches to developing collaborative tools. The new method uses automatically inferred and manually recorded design rationale to intelligently filter the information that is shared by a collaborative tool. This represents an improvement upon the existing state of the art in collaborative engineering tools. To demonstrate the viability of the method three collaborative tools were created. The first is a multi-user collaborative design environment tool named SimulPart and built upon the NX CAD package. SimulPart uses the new method to limit the amount of communication required to keep every user in synch during a multi-user co-design session. The second implementation is a visual history tool named VisiHistory that allows designers to watch time lapse videos of the creation of a design that are automatically generated using the new method. The final tool is an intelligent user directory named SmartHelp that uses the new method to allow designers to identify which of their peers have expertise in certain CAD operations. Validation was performed for each of these tools by benchmarking the tool against the leading commercial solution or industry process. The results of the validation showed that the new method does in fact offer a superior collaborative solution as it outperforms the existing tools and methods in several key collaborative metrics. As a result of this work future efforts are encouraged into both improving upon the quality of the inferred design rationale and increasing the functionality of the three tools created using the new method.
20
Guzzetta, Fabrizio. "Rationale Design of Up-Converting Nanoparticles Towards Advanced Optical Applications." Doctoral thesis, Universitat Jaume I, 2018. http://hdl.handle.net/10803/662815.
Full textAbstract:
The thesis aims to shed some light on the massive production of up-converting nanocrystals through solvothermal conditions. Solvothermal route allows to prepare larger quantities of these nanomaterials, as compared to normal glassware-based routes, and increase yield of nanomaterials per synthesis. The synthetic route was optimized through thorough analysis of several parameters
Then, the produced nanomaterials were used to propose new optical applications in both biological (encapsulation of the nanomaterials within vesicles based on glicolypids under different pH conditions) and technological fields (the solids were entrapped within a soft-matter matrix that, under a critical temperature, underwent a sol-gel transition and permitted in a low-temperature range (below water boiling point) the modulation of matrix emissions).
Lastly a microwave - assisted synthesis was studied, as alternative to solvothermal route, to understand the formation of up-converting nanocrystals, which allowed a versatile post-synthetic coating for further applications of the crystals.La tesis abarca un problema general de producción a gran escala de los nanomateriales. Condiciones solvotermales permiten optimizar el rendimiento de producción de materiales, y por lo tanto esta ruta de síntesis ha sido elegida para su producción masiva. El proceso ha sido optimizado a través el analísis de diferentes parametros de reacción. Se han producido también aplicaciones ópticas avanzadas tanto en ámbito biológico (atrapando los sólidos en vesiculas preparadas por medio de glicolípidos a diferente pH) cuanto en ámbito tecnologico (los solidos venián atrapados en sistemas fibrilares que a raíz de una temperatura critica en la transición sol-gel permitía modulación de las emisiones de la matríz órganica). En fin se ha estudiado y analizado la formación de sistemas cristalinos por medio de la sintesis a microondas, como sistema alternativo al solvotermal, que ha resultado en la formación de nanorods con posibilidad de recubrimiento post-síntesis.
21
Scott, Quincy R. (Quincy Roy) 1978. "SSPARCy : a software integration support and design rationale capture system." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/86851.
Full textAbstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.Includes bibliographical references (leaves 117-119).
by Quincy R. Scott.
M.Eng.
22
Borges, Vanessa dos Anjos [UNESP]. "Apoio à gerência de requisitos de software utilizando Design Rationale." Universidade Estadual Paulista (UNESP), 2014. http://hdl.handle.net/11449/122158.
Full textAbstract:
Made available in DSpace on 2015-04-09T12:28:25Z (GMT). No. of bitstreams: 0
Previous issue date: 2014-02-27Bitstream added on 2015-04-09T12:47:36Z : No. of bitstreams: 1
000811283.pdf: 807592 bytes, checksum: 20071fc52e344400d2ef0f3dbc06d166 (MD5)Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
As necessidades dos usuários e partes interessadas no desenvolvimento de um software, denominadas requisitos, mudam constantemente, seja por falta de informações ou por mudanças organizacionais ou ambientais. A gerência desses requisitos gera um grande volume de informações que podem ser reutilizadas para consolidar o conhecimento dos envolvidos no projeto. Diversas são as técnicas para formalização desse conhecimento, destacando-se a técnica de Design Rationale que trata da organização da lógica de raciocínio utilizada para projetar artefatos. Neste contexto, este trabalho apresenta um estudo sobre a utilização de Design Rationale na Gerência de Requisitos de software, integrando essa técnica a um sistema web de apoio à Engenharia de Requisitos de Software, denominado Ferramenta de Suporte à Engenharia de Requisitos - FSER. Para avaliação dessa integração, foi realizado um Experimento Controlado, com a participação de alunos de graduação em Ciência da Computação e profissionais da área de Tecnologia da Informação, constatando sua contribuição no que concerne a disseminação do conhecimento e com a formação de uma base de dados que apóie o desenvolvimento de projetos futuros
The users and stakeholders needs identified during software development, called requirements often change, either for lack of information or due to organizational or environmental changes. The management of these requirements generates a large volume of information that can be re-used to consolidate the knowledge between users and stakeholders of project. There are several techniques to formalize this knowledge, emphasizing Design Rationale technique which dealing with the logical reasoning organization used to design artifacts. In this context, this study presents the application of Design Rationale in Software Requirements Management, integrating this technique to a web support system for Software Requirements Engineering, called Requirements Engineering Support Tool - REST. For assessment this integration, it was performed a Controlled Experiment, involving Computer Science undergraduate students and Information Technology professionals, recognizing its contribution regarding knowledge dissemination and a database creation supporting the development of future projects
23
Camponogara, Marcos. "QOC *:utilizando Design Rationale como ferramenta para gestão do conhecimento." Pontifícia Universidade Católica do Rio Grande do Sul, 2008. http://hdl.handle.net/10923/1489.
Full textAbstract:
Made available in DSpace on 2013-08-07T18:42:28Z (GMT). No. of bitstreams: 1
000402763-Texto+Completo-0.pdf: 556574 bytes, checksum: 655afda9c78f443615939500b7d640fd (MD5)
Previous issue date: 2008In general, the decision making process in a software development project depends on the people involved in this process and their knowledge of the project. Also, the option analysis process which results in a decision, produces a kind of knowledge that is very important for the project and its future, since this knowledge is about key decisions and their rationale. Thus, understanding the rationale behind a decision provides a powerful way to better understand how a project works in detail and why some decisions were taken. Considering this perspective, it is necessary to find an approach to organize and maintain knowledge about the decision making process from software development projects, and then use this knowledge to help people involved in these projects. Another possibility is to reuse the generated knowledge in other projects, as learned lessons, considering in this case, similar scenarios from past projects. Taking in account what has been stated above, this research proposes an approach to document and organize the rationale regarding the decision making process in software development projects, using for this purpose a simple and objective representation that encourages reasoning in order to define the best solutions for problems faced in software development projects.
Durante o processo de desenvolvimento de um sistema de software, uma grande quantidade de conhecimento é utilizada e produzida como resultado das opções analisadas e das decisões tomadas ao longo do desenvolvimento do projeto. Este conhecimento é valioso, pois reflete as razões que estão por trás das decisões, o que facilita o entendimento dos rumos do projeto e proporciona uma visão global do mesmo. Desta forma, existe a necessidade de se encontrar alternativas para organizar e manter este tipo de conhecimento e então torná-lo um recurso que possa facilitar a continuidade de projetos de software ou então a manutenção de sistemas desenvolvidos. Outra possibilidade ainda é a reutilização deste conhecimento em outros projetos, considerando-se neste caso a existência de cenários semelhantes aos cenários vivenciados em projetos anteriores. Neste sentido, o presente trabalho aborda o desenvolvimento de uma pesquisa baseada em Gestão do Conhecimento e Design Rationale, e propõe uma maneira de representar e manter as razões que motivaram a tomada de determinadas decisões em projetos de software, considerando, para isso, uma forma de representação simples e objetiva que instiga o questionamento e a discussão a respeito das melhores opções para atender questões que surgem durante o desenvolvimento de um projeto.
24
Borges, Vanessa dos Anjos. "Apoio à gerência de requisitos de software utilizando Design Rationale /." São José do Rio Preto, 2014. http://hdl.handle.net/11449/122158.
Full textAbstract:
Orientador: Rogéria Cristiane Gratão de SouzaBanca: Maria Istela Cagnin Machado
Banca: Leandro Alves Neves
Resumo: As necessidades dos usuários e partes interessadas no desenvolvimento de um software, denominadas requisitos, mudam constantemente, seja por falta de informações ou por mudanças organizacionais ou ambientais. A gerência desses requisitos gera um grande volume de informações que podem ser reutilizadas para consolidar o conhecimento dos envolvidos no projeto. Diversas são as técnicas para formalização desse conhecimento, destacando-se a técnica de Design Rationale que trata da organização da lógica de raciocínio utilizada para projetar artefatos. Neste contexto, este trabalho apresenta um estudo sobre a utilização de Design Rationale na Gerência de Requisitos de software, integrando essa técnica a um sistema web de apoio à Engenharia de Requisitos de Software, denominado Ferramenta de Suporte à Engenharia de Requisitos - FSER. Para avaliação dessa integração, foi realizado um Experimento Controlado, com a participação de alunos de graduação em Ciência da Computação e profissionais da área de Tecnologia da Informação, constatando sua contribuição no que concerne a disseminação do conhecimento e com a formação de uma base de dados que apóie o desenvolvimento de projetos futuros
Abstract: The users and stakeholders needs identified during software development, called requirements often change, either for lack of information or due to organizational or environmental changes. The management of these requirements generates a large volume of information that can be re-used to consolidate the knowledge between users and stakeholders of project. There are several techniques to formalize this knowledge, emphasizing Design Rationale technique which dealing with the logical reasoning organization used to design artifacts. In this context, this study presents the application of Design Rationale in Software Requirements Management, integrating this technique to a web support system for Software Requirements Engineering, called Requirements Engineering Support Tool - REST. For assessment this integration, it was performed a Controlled Experiment, involving Computer Science undergraduate students and Information Technology professionals, recognizing its contribution regarding knowledge dissemination and a database creation supporting the development of future projects
Mestre
25
Poorkiany, Morteza. "Managing design rationale in the development of product families and related design automation systems." Doctoral thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH, Produktutveckling, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-38033.
Full textAbstract:
As the markets’ needs change rapidly, developing a variety of products that meet customers’ diverse needs is a competitive factor for many manufacturing companies. Development of highly customized products requires following an engineer-to-order business process to allow the products to be modified or adapted to new customers’ specifications, which brings more value to the customer and profit to the company. The design of a new product variant involves a large amount of repetitive and time-consuming tasks but also information handling activities that are sometimes beyond human capabilities. Such work that does not rely so much on creativity can be carried out more efficiently by applying design automation systems. Design automation stands out as an effective means of cutting costs and lead time for a range of well-defined design activities and is mainly considered as a computer-based tool that processes and manipulates the design information. Variant design usually concern generating a new variant of a basic design, that has been developed and proved previously, according to new customer’s demands. To efficiently generate a new variant, a deep understanding of the intention and fundamentals of the design is essential and can be achieved through access to design rationale—the explanation of the reasons and justifications behind the design. The maintenance of product families and their corresponding design automation systems is essential to retaining their usefulness over time and adapting them to new circumstances. Examples of new circumstances can include the introduction of new variants of existing products, changes in design rules to meet new standards or legislations, or changes in technology. To maintain a design automation system, updating the design knowledge (e.g. design rules) is required. The use of design rationale will normally become a necessity for allowing a better understanding of the knowledge. Consequently, there is a need for principles and methods that enable the capture and structure of the design rationale and sharing them with the users. This study presents methods and tools for modeling design knowledge and managing design rationale in order to support the utilization and maintenance of design automation systems. Managing design rationale concerns enabling the capturing, structuring, and sharing of design rationale. The results have been evaluated through design automation systems in two case companies.Att kunna erbjuda kundanpassade produkter har blivit allt viktigare för många tillverkande företag. Utformningen av en ny produktvariant involverar en stor mängd repetitiva och tidskrävande uppgifter men även informationshanteringsaktiviteter som ibland är bortom mänskliga möjligheter. Sådant arbete som inte förlitar sig så mycket på kreativitet kan genomföras mer effektivt genom att använda designautomatiseringssystem. Designautomatisering framstår som ett effektivt sätt att minska kostnader och ledtid för en rad väldefinierade designaktiviteter och betraktas huvudsakligen som ett datorbaserat verktyg som analyserar och syntetiserar designinformationen. Variantdesign handlar vanligtvis om att skapa en ny variant av en grundläggande design, som har utvecklats och bevisats tidigare enligt nya kunders krav. För att effektivt skapa en ny variant är en djup förståelse för designens avsikt och grundläggande uppbyggnad avgörande och kan uppnås genom tillgång till ”design rationale”- förklaringen av skälen och motiveringarna bakom designen. Underhållet av produktfamiljer och deras motsvarande designautomatiseringssystem är viktigt för att behålla användbarheten över tid och anpassa dem till nya omständigheter. Exempel på nya omständigheter kan innefatta införande av nya varianter av befintliga produkter, ändringar av designregler för att uppfylla nya standarder, lagstiftningar eller tekniska ändringar. För att upprätthålla ett designautomatiseringssystem krävs uppdatering av designkunskapen (t ex designregler). Användningen av design rationale kommer normalt att bli en nödvändighet för att ge en bättre förståelse av kunskapen. Följaktligen finns det ett behov av principer och metoder som möjliggör fångande och strukturering av design rationale och dela dem med användarna. Denna studie presenterar metoder och verktyg för modellering av designkunskap och hantering av design rationale för att stödja utnyttjande och underhåll av designautomatiseringssystem. Vid hantering av design rationale gäller det att göra det möjligt att fånga, strukturera och dela med sig av design rationale. Resultaten har utvärderats genom att undersöka effekterna av dem i designautomationssystem i två företag.
26
FILHO, JOSÉ EURICO DE VASCONCELOS. "A DESIGN MODEL BASED ON RATIONALE: RELATING PROBLEM SPACE TO SOLUTION SPACE OF DESIGN." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2010. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=16991@1.
Full textAbstract:
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICOO design de sistemas interativos é um processo complexo, iterativo e colaborativo, que requer diferentes conhecimentos para sua realização, e composto por diferentes atividades que se inter-relacionam na composição de um produto final. As informações produzidas durante cada atividade são de extrema relevância para a continuidade do processo e para a compreensão, explicação e manutenção do produto produzido. Estas informações devem estar relacionadas e integradas em um discurso claro e coerente, permitindo sua rastreabilidade e contemplando a proveniência e o contexto em que foram produzidas. Observa-se, entretanto, que as propostas de captura e modelagem do processo de design em IHC provêem uma visão fragmentada e/ou incompleta deste processo. Por esta razão, propõe-se aqui um modelo epistêmico, baseado em Design Rationale (DR), adequado ao registro e modelagem do design de sistemas interativos. Com base na revisão e análise das principais visões e propostas do processo de design, seus requisitos, modelos, notações, linguagens de suporte foi proposto o modelo epistêmico Ideia. O modelo tem como principal objetivo registrar e comunicar as atividades de design de forma coesa, oferecendo subsídios para a reflexão da equipe de design sobre as atividades do processo de design, bem como informações de proveniência para a rastreabilidade das informações. Para isso, o modelo propõe a integração dos insumos e produtos (e.g., requisitos, modelos, artefatos) das atividades de design, oferecendo uma ponte entre as atividades de análise (espaço de problema) e de design conceitual (espaço de solução) por meio do DR. O modelo foi implementado no protótipo Deprost e adotado no design de parte de um sistema colaborativo, o sistema WikiMapps, possibilitando avaliar a proposta através de um estudo de caso sobre seu desempenho quanto ao que é proposto.
The design of interactive systems is a complex, iterative and collaborative process, composed of different activities that are interrelated in the composition of a final product and requires different expertise to perform it. The information produced during each activity is very important for the continuity of the process and to understand, explain and maintain the product produced. This information must be related and integrated in a clear and coherent speech, allowing traceability and addressing the origin and the context in which they were produced. It is noted, however, that the proposed process catch and modeling in HCI design provide a fragmented and/or incomplete view of this process. For this reason, we propose an epistemic model, based on Design Rationale (DR), suitable for the recording and modeling of the design of interactive systems. Based on the review and analysis of the key views and proposals of the design process, their requirements, models, notations and support languages, the epistemic model Ideia has been proposed. The model has as its main goal to register and report design activities in a cohesive manner, offering support for the reflection of the design team about the activities of the design process as well as information sources for the traceability of information. For this, the model proposes the integration of inputs and outputs (e.g., requirements, models, artifacts) of the activities of analysis (problem space) and the conceptual design (solution space) DR. The model was implemented in the Deprost prototype and adopted in the design of part of the WikiMapps project, allowing us to evaluate the proposal in a real case study.
27
Mix, Kenneth John. "Integrating Engineering and Communication Tools for the Automation of Design Rationale Capture." BYU ScholarsArchive, 2010. https://scholarsarchive.byu.edu/etd/2078.
Full textAbstract:
Product development is continually becoming more challenging as global competition requires more efficient design methods. The reuse of company knowledge, specifically the design rationale that occurs during projects is essential to success. This thesis presents a method for integrating engineering and communication tools for purposes of automating the capture of communication-based design rationale. The method is based on four basic principles: to integrate, to make data retrievable, to minimize user interaction, and to store as much DR as possible. The core method consists of two primary operations, the first being to capture the design rationale, and the second being to provide for effective retrieval. An implementation of this method that uses NX as the engineering tool and Skype VoIP software as the communication tool was created for the purpose of testing integration as a means of DR capture. The implementation was evaluated using four separate tests, which focus on efficiency of capture and retrieval, cost analysis, and user satisfaction. These results show that the tool provides improvement in each of the tested categories. From this testing I conclude that integrating communication and engineering tools is an excellent way to capture communication-based design rationale. The tool presented is more efficient than traditional methods in the test cases and provides a user-friendly solution to DR capture. This tool also has various other important applications, such as global collaboration and expectation management. It also provides an excellent framework for upcoming multi-user CAx tools.
28
Bramwell, Christopher John. "Formal development methods for interactive systems : combining interactors and design rationale." Thesis, University of York, 1995. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.296395.
Full text
29
Fumagalli, Lisandra Cazassa. "Um mecanismo de recuperação de design rationale em documentos na web." Universidade de São Paulo, 2005. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-02122014-164017/.
Full textAbstract:
Design Rationale (DR) consiste em um conjunto de informações relacionadas ao processo de desenvolvimento e de tomada de decisão de um projeto. Nos projetos, em especial, adquirir e disponibilizar tais informações são práticas importantes para a melhoria das atividades de desenvolvimento e consequentemente da qualidade do produto desenvolvido. Por meio da atividade de documentação, os artefatos produzidos durante o projeto constituem a base para que ligações possam ser inseridas e expressem as relações com o DR correspondente. Um documento XML se apresenta como mecanismo apropriado para essa atividade pois além das informações, é possível acrescentar significado a essas informações. No entanto, a utilização efetiva das informações nesse documento XML só é possível se elas forem encontradas e exploradas de maneira a auxiliar os membros das equipes de projeto na realização de suas atividades. A ferramenta DocRationale foi desenvolvida para permitir o armazenamento e recuperação de informações de projeto de software, e respectivo DR. No entanto, para a exploração do DR armazenado, somente a navegação simples foi prevista inicialmente. Assim, a busca por informações de DR torna-se bastante custosa. Neste trabalho é apresentado um mecanismo para busca de DR, com o propósito de melhorar a exploração dessas informações.Design Rationale (DR) consists of a set of information related to the development and decision process of a project. In projects, acquiring and making such information available are important practices for the improvement of development process. Consequently the product has higher quality. With the documents produced during the software development is possible to create links with their corresponding DR. In that context, an XML document may be considered an appropriate mechanism for the documentation activity because information in those documents have a meaning. However, the effective use of information contained in this XML document is only possible if these information are searched and explored according to the needs of project teams. The DocRationale tool was developed to storage and recovery information related to software projects and their respective DR. However, as only the simple navigation was foreseen initially, searching for DR information is very onerous. In this work it is presented a mechanism for DR searching as a way to improve the exploration of these information.
30
Camponogara, Marcos. "QOC *: utilizando Design Rationale como ferramenta para gest?o do conhecimento." Pontif?cia Universidade Cat?lica do Rio Grande do Sul, 2008. http://tede2.pucrs.br/tede2/handle/tede/5022.
Full textAbstract:
Made available in DSpace on 2015-04-14T14:49:00Z (GMT). No. of bitstreams: 1
402763.pdf: 556574 bytes, checksum: 655afda9c78f443615939500b7d640fd (MD5)
Previous issue date: 2008-01-09Durante o processo de desenvolvimento de um sistema de software, uma grande quantidade de conhecimento ? utilizada e produzida como resultado das op??es analisadas e das decis?es tomadas ao longo do desenvolvimento do projeto. Este conhecimento ? valioso, pois reflete as raz?es que est?o por tr?s das decis?es, o que facilita o entendimento dos rumos do projeto e proporciona uma vis?o global do mesmo. Desta forma, existe a necessidade de se encontrar alternativas para organizar e manter este tipo de conhecimento e ent?o torn?-lo um recurso que possa facilitar a continuidade de projetos de software ou ent?o a manuten??o de sistemas desenvolvidos. Outra possibilidade ainda ? a reutiliza??o deste conhecimento em outros projetos, considerando-se neste caso a exist?ncia de cen?rios semelhantes aos cen?rios vivenciados em projetos anteriores. Neste sentido, o presente trabalho aborda o desenvolvimento de uma pesquisa baseada em Gest?o do Conhecimento e Design Rationale, e prop?e uma maneira de representar e manter as raz?es que motivaram a tomada de determinadas decis?es em projetos de software, considerando, para isso, uma forma de representa??o simples e objetiva que instiga o questionamento e a discuss?o a respeito das melhores op??es para atender quest?es que surgem durante o desenvolvimento de um projeto.
31
Poorkiany, Morteza. "Support Maintenance of Design Automation Systems - A Framework to Capture, Structure and Access Design Rationale." Licentiate thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Produktutveckling - Datorstödd konstruktion, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-28172.
Full textAbstract:
The ability to innovate and launch customized products that are well matched to customer demands is a competitive factor for many manufacturing companies. Development of highly customized products requires following an engineer-to-order business process to allow the products to be modified or adapted to new customers’ specifications, which brings more value to the customer and profit to the company. Design of a new product variant involves a large amount of repetitive and time consuming tasks but also information handling activities that are sometimes beyond human capabilities. Such work that does not rely so much on creativity can be carried out more efficiently by applying design automation systems. Design automation stands out as an effective means of cutting costs and lead time for a range of well-defined design activities and is mainly considered as a computer-based tool that processes and manipulates the design information. Adaptation and variant design usually concern generating a new variant of a basic design, which has been developed and proved previously, according to new customer’s demands. In order to efficiently generate a new variant, a deep understanding of the previous design is essential. Such understanding can be achieved by access to the design rationale explaining the reasons and justifications behind the design. Maintenance of design automation systems is essential to retain their usefulness over time and adapt them to new circumstances. New circumstances are, for example, introduction of new variants of existing products, changes in design rules in order to meet new standards or legislations, or changes in technology. To maintain a design automation system, updating the design knowledge (e.g. design rules) is required. Use of design rationale will normally become a necessity to allow a better understanding of the knowledge. Consequently, there is a need of principles and methods to enable capture, structure, and access design rationale. In this study, a framework for modeling design knowledge and managing design rationale in order to support maintenance of design automation systems is presented. Managing of design rationale concerns enabling capture, structure, and access to design rationale. In order to evaluate the applicability of the framework, the findings are tested through design automation systems in two case companies.Impact
Adapt
32
MEDEIROS, ADRIANA PEREIRA DE. "KUABA: AN APPROACH FOR REPRESENTATION OF DESIGN RATIONALE FOR THE REUSE OF MODEL BASED DESIGNS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2006. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=8935@1.
Full textAbstract:
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICOEste trabalho apresenta um modelo de representação de conhecimento e a arquitetura conceitual de um ambiente de design integrado para apoiar a representação de design rationale e seu uso no design de artefatos de software. Em nossa abordagem de representação propomos o uso da semântica formal dos artefatos, fornecida pelos métodos de design, para representar design rationale usando o vocabulário definido na ontologia Kuaba. Este vocabulário, descrito em uma linguagem formal para especificação de ontologias, permite definir um conjunto de regras e operações computáveis que apóiam o reuso de designs na produção de novos artefatos de software. Esta abordagem de representação possibilita um novo tipo de reuso de design de software em um nível mais alto de abstração, onde rationales podem ser integrados e re- empregados no design de um novo artefato.
This work presents a knowledge representation model and the conceptual architecture of an integrated design environment to support recording design rationale, as well as use of design rationale, during design of software artifacts. In our representation approach, we propose the use of the formal semantics of artifacts provided by design methods to represent design rationale using the vocabulary defined in the Kuaba ontology. This vocabulary described in a formal ontologies specification language allows defining a set of rules and computable operations that support the reuse of designs in the production of new software artifacts. This representation approach enables a type of software design reuse at the highest abstraction level, where rationales can be integrated and re-employed in designing a new artifact.
33
Wang, Hongwei. "The retrieval and reuse of engineering knowledge from records of design rationale." Thesis, University of Cambridge, 2012. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.610290.
Full text
34
Neto, Americo Talarico. "Uma abordagem para projeto de aplicações com interação multimodal da Web." Universidade de São Paulo, 2011. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-07062011-091441/.
Full textAbstract:
O principal objetivo do desenvolvimento de aplicações multimodais é possibilitar uma maneira mais natural dos seres humanos se comunicarem com as máquinas, por meio de interfaces mais eficientes, intuitivas, fáceis de usar e, de certa forma, mais inteligentes. No entanto, a literatura da área mostra que a reutilização, tanto de conhecimento como de código fonte, ainda apresenta problemas, dados a complexidade do código em sistemas multimodais, a falta de mecanismos eficientes de testes de usabilidade e a dificuldade em se gerenciar a captura, o armazenamento e a recuperação de conhecimento de projeto. Nesta tese argumenta-se que a utilização de uma abordagem sistemática, centrada no usuário, apoiada por uma ferramenta computacional e com um modelo bem definido que permita o desenvolvimento de interfaces multimodais com a reutilização de Design Rationale, aumenta e melhora os níveis de usabilidade, promove a identificação e utilização de padrões de projeto e o reúso de componentes. Para demonstrar esta tese, apresenta-se neste texto a abordagem para o desenvolvimento de interfaces multimodais Web, MMWA, e o seu ambiente de autoria, o MMWA-ae, ambos compostos por atividades que auxiliam a equipe de projeto durante as fases de projeto, desenvolvimento e avaliações de usabilidade. São discutidos também os resultados obtidos com a execução de três estudos de caso, realizados no ambiente acadêmico, nos quais se buscou determinar a viabilidade da abordagem e os benefícios que podem ser alcançados com a combinação de diferentes técnicas, a saber: design rationale, padrões de projeto, modelagem de tarefas, componentes de software, princípios de usabilidade, avaliações heurísticas, testes com usuários, regras de associação, entre outras. Os resultados evidenciam que a abordagem e seu ambiente de autoria podem proporcionar diferentes benefícios para organizações que desenvolvem sistemas multimodais, incluindo o aumento da usabilidade e consequentemente da qualidade do produto, bem como a diminuição de custos e da complexidade do desenvolvimento com a reutilização de código e de conhecimento capturado em projetos anterioresThe main goal of developing multimodal applications is to enable a more natural way of communication between human beings and machines through interfaces that are more efficient, intuitive, easier to use and, in a certain way, more intelligent. However, the literature shows that the reuse of both knowledge and source code still presents problems, given the complexity of the code in multimodal systems, the lack of efficient mechanisms to test the usability and the difficulty in managing the capture, the storage and the recovery of design knowledge. In this thesis it is discussed that the use of a systematic approach, usercentered, supported by a computer tool and with a well defined model that allows the development of multimodal interfaces with the reuse of DR, increases and improves the usability levels, promotes the identification and the use of design patterns and the reuse of components. To demonstrate this thesis, it is shown in this text an approach to develop Web multimodal interfaces (MMWA) and its authoring environment (MMWA-ae), both composed of activities that help the design team during the different project phases: design, development and usability evaluation. We also discuss in this thesis the results obtained with the execution of three case studies, executed in the academic environment, which aimed to determine the feasibility of the approach and the benefits that can be achieved with the combination of different techniques, such as: design rationale, design patterns, tasks model, software components, usability principles, heuristic evaluations, user testing, association rules, among others. The results show clearly that the approach and its author environment can provide different benefits to organizations that develop multimodal systems, including the usability improvement and, consequently, the quality of the product, as well as the decrease of costs and complexity since it encompasses the development with reused code and design knowledge captured in previous projects
35
Morris, Debra A. Paco Tina M. "Towards an information model and mechanisms for design rationale capture and use /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1993. http://handle.dtic.mil/100.2/ADA275060.
Full text
36
Morris, Debra A., and Tina M. Paco. "Towards an information model and mechanisms for design rationale capture and use." Thesis, Monterey, California. Naval Postgraduate School, 1993. http://hdl.handle.net/10945/39983.
Full textAbstract:
Approved for public release; distribution is unlimited.Every year the Department of Defense's (DoD) expenditures on software alone amount to almost ten billion dollars, with maintenance costs comprising the majority of this figure. Recent studies have indicated that an effective solution to help curtail the large maintenance cost is by capturing the rationale which was used to create the systems requirements and designs, and using this information throughout the life cycle. However, various models proposed by current research for capture of design rationale address only some specific aspects of the design process rather than the entire design process. This thesis identifies the important components of a comprehensive design rationale information model, proposes mechanisms to facilitate their capture, and identifies the generic functionalities of a design rationale management tool to use the rationale in various systems development activities.
37
Phillips, Sophie E. C. "Structuring multimedia data to capture design rationale and to support product development." Thesis, University College London (University of London), 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.399013.
Full text
38
Francisco, Simone Domingues. "DocRationale: uma ferramenta para suporte a design rationale de artefatos de software." Universidade de São Paulo, 2004. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-20082015-102820/.
Full textAbstract:
Uma grande quantidade e variedade de artefatos é gerada durante o processo de desenvolvimento de um software. A documentação por meio dos diversos artefatos de tal processo é importante para proporcionar um bom conhecimento do software, além de tornar menos complicada a sua manutenção e reuso. Tais documentos, em geral, não registram informações adicionais relativas às alternativas, escolhas e decisões - Design Rationale (DR) - feitas durante a elaboração de cada artefato. O\" armazenamento e recuperação de DR dos artefatos de software tornaria mais simples a sua manutenção e facilitaria seu reuso, já que possibilita que o software torne-se mais completo de informações. O presente trabalho apresenta a ferramenta DocRationale que captura, armazena e recupera DR de artefatos de software. A DocRationale enfatiza a colaboração entre os desenvolvedores e a anotação estruturada por meio de uma simplificação de um modelo de representação de DR.During the software development process a large number of different artefacts is generated. Documentation is an essential activity, since it promotes a better software understanding and eases its maintenance and reuse. In general, the documents do not record additional information related to the alternative options, choices and decisions - in order words the Design Rationale (DR) - evaluated during the design of an artefact. The storage and retrieval of DR software artefacts would further improve its maintenance and reuse potential since the software would be easier to understand. This work presents a tool - DocRationale - to capture, store and retrieve design rationale of software artefacts. This tool promotes collaboration between software developers and uses structured annotation to simplify the DR conceptual model.
39
Kraus, Sarah. "The Rationale, Design and Implementation of the African Cardiomyopathy and Myocarditis Registry." Doctoral thesis, Faculty of Health Sciences, 2019. http://hdl.handle.net/11427/30799.
Full textAbstract:
Background. Causes of heart failure in Africa are largely non-ischaemic: hypertension, rheumatic heart disease and cardiomyopathy. Cardiomyopathies pose a great challenge because of poor prognosis and high prevalence in low- and middle-income countries with limited access to specialised care. Little is known about aetiology or outcomes of cardiomyopathy in Africa. Method. The African Cardiomyopathy and Myocarditis Registry Program (IMHOTEP) is a pan-African multi-centre, hospital-based cohort study. It aims to describe the clinical characteristics, aetiology, genetics, management and outcome of cardiomyopathies in children and adults. Index patients were recruited as either incident (new) or prevalent (existing) cases, and family screening was conducted in selected cases. Several sub-studies were conducted at the initiating centre, including; outcome studies on prevalent cases incorporated into IMHOTEP, a cardiovascular magnetic resonance (CMR) study on incident cases, and a clinical genetics study on families. Results. The pilot phase was commenced in Cape Town (February 2015), followed by staggered initiation at 6 further sites. Over 600 index patients have been recruited to the registry to date. Preliminary data on the first 99 incident adult cases recruited at the initiating site, showed that dilated cardiomyopathy (DCM; n=67) was commonest, followed by hypertrophic (HCM; n=13), left ventricular noncompaction (LVNC; n=11), restrictive (RCM; n=4) and arrhythmogenic right ventricular (ARVC; n=4) cardiomyopathies. Cardiomyopathy occurred predominantly in mixed race (46%) and black (41%) Africans, and more frequently in females (54%). Mean age of presentation was 36.8 ±12.5 years. CMR performed in incident cases (67/99, 68%) proved diagnostically useful, however, acute myocarditis was only reported in one individual. In addition, prevalent cases with ARVC and DCM were enrolled from two existing studies at the initiating centre. Except for fewer (24%) genotype positive (PKP2 20%, CDH2 4%) individuals with ARVC (n=70), the baseline characteristics and diagnostic criteria were similar to what has been reported internationally. Transplant-free survival probability at 1-year, 5-years and 10-years was 98.5%, 90.7%, and 80.8% respectively in ARVC (median survival time 9.0 years) and there were no significant differences in survival between those with and without implantable cardioverter defibrillators [p=0.27]. In the prevalent DCM cohort (n=133), transplant-free survival probability was 93.4%, 82.2% and 73.1% at 1-year, 5-years and 10-years respectively, with a median survival time of 5.3 years. The age of onset (34.8 ±11.0 years) and death (41.5 ±9.6 years) were significantly younger in our DCM patients compared to European cohorts. Thirty-five families were recruited (16 genotype positive, 19 genotype unknown) with autosomal dominant inheritance observed in 94.3% families. Conclusion. IMHOTEP is the first multi-centre registry for cardiomyopathy in Africa. Preliminary data suggests an earlier age of onset compared to European cohorts and that DCM is the most common form of cardiomyopathy in South Africa. Molecular genetic analysis will provide vital and novel data on the genetic causes of cardiomyopathy in Africans.
40
Poorkiany, Morteza. "Enabling traceability of design rationale using the concept of product family description (PFD)." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH, Maskinteknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-16421.
Full textAbstract:
This thesis work is based on the previous researches in design automation at Sandvik Coromant. The concept of product family description (PFD) has been introduced to the company to improve documentation of knowledge in engineering design process. Current documentation at the company for engineering design covers mostly the design definition part of the knowledge. PFD is constituted by design definition and completed by design rationale. This kind of documentation improves reusing, revising and expanding the knowledge at the company. On the other side, PFD is an input for design programming and a good engineering design description for a product provides more efficiency in design programming. The project is started by a survey for several principles and applications for knowledge modelling. Product variant master (PVM) and Semantic MediaWiki are selected by the results of the survey. To show the concept of PVM, modelling of a test product is done in product model manager (PMM) software. The main part of the project is setting up product family description (PFD) by capturing design rationale for the test product, implementing in Semantic MediaWiki. Since the design rationale is not documented, it was recorded during several meetings with the designer of the test product. The description is completed by including the argumentations about the rules, figures, dimensions and etc. Also in the project has been tried to improve and revise the description to make it more simple and efficient. Another objective of the project is to show Semantic MediaWiki as a candidate application for modelling knowledge at the company. In this step the applicability and functionality of both PFD and Semantic MediaWiki is seen. In the next stage the project findings and company documentation are evaluated. In this step has been tried to show the pros and cons of the project. The emphasis of the evaluation is on PFD and the alternative application. In the end a conclusion of the whole methods and findings of the project comes with discussion with people who were involved in this work.
41
Kawamoto, Sandra. "Proposta de um modelo de representação de Design Rationale para projetos de sistemas ERP." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-07082007-121610/.
Full textAbstract:
Atenção especial tem sido dada às atividades de documentação e suporte a projetos em Engenharia de Software, principalmente quando estão relacionadas a sistemas complexos e equipes distribuídas. Geralmente apenas se registram as informações relativas às decisões finais de determinada fase. Não são documentadas as razões de cada decisão e nem as alternativas que foram consideradas e descartadas. A captura e recuperação, de maneira eficiente, deste tipo de informação é a finalidade do estudo do Design Rationale. O registro destas informações pode facilitar a manutenção, o reuso e também a própria fase de elaboração do projeto, na medida em que possibilita um melhor entendimento do sistema, por meio da disseminação de conhecimento, comunicação e integração entre a equipe de projeto. A questão é quando e como capturar estas informações sem muita interferência junto às atividades usuais dos projetistas, a fim de que os benefícios possam superar os custos envolvidos nesta tarefa. O presente trabalho tem como objetivo mostrar com razões plausíveis a grande utilidade da aplicação da técnica de Design Rationale em projetos de sistemas ERP, propondo um novo modelo de representação das decisões de projeto para estes sistemas.Special attention has been given to documentation and support activities in Software Engineering design, mainly when they are related to complex systems and distributed teams. Usually, information related to the final decisions of each phase is registered. However, the reasons of each decision and the alternatives that were considered and discarded are not documented. Capture and recovery of this type of information, in an efficient way, are the purposes of the Design Rationale study. Recording this information can facilitates maintenance, reuse and even the design phase, providing a better understanding of the system, by knowledge spread, communication and integration among the project team. The main concern is when and how to capture this information with low interference in designers\' usual activities, so that benefits can overcome costs involved in this task. The purpose of the present work is to show with plausible reasons the great usefulness of the application of Design Rationale technique in ERP systems design, proposing a new representation model for recording design decisions in these system.
42
Bylund, Markus. "A Design Rationale for Pervasive Computing - User Experience, Contextual Change, and Technical Requirements." Doctoral thesis, Stockholm : Swedish Institute of Computer Science (SICS), Department of Computer & Systems Sciences, Stockholm University, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-259.
Full text
43
BOWERS, ROBERT SIDNEY EARL. "MANAGING CREATIVITY FOR PRODUCTIVITY: RATIONALE, DESIGN AND PROGRAMS (INNOVATION, CREATIVE, INVENTION, INNOVATE, CREATION)." Diss., The University of Arizona, 1986. http://hdl.handle.net/10150/188177.
Full textAbstract:
This study presents an operational definition of creativity within the contexts of business, school and community. A design for the strategic management of creativity is developed. Suggestions are made for programs to increase effectiveness in the use of creative skills. Creativity has been viewed in the past as something that happens rather than deliberate activity directed to specific goals. Numerous studies have failed to find a significant relationship between measurements of creative skills and intelligence as delimited by IQ tests and other measures of performance. Creativity can be distinguished as a category, process and quality of intelligence, and both can be defined in qualitative and theoretical terms. Models are constructed in the study to classify creativity. The components of the creative act can be tracked. A model sets parameters and categories for investigations to permit variation of content in a relatively stable sequence of steps. The sequence can be extracted as a method to process ideas from any discourse.
44
Paiva, Debora Maria Barroso. "Um processo envolvendo elementos de design rationale para projetos de pesquisa em software." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-14092007-104959/.
Full textAbstract:
O volume crescente de projetos de pesquisa que envolvem software motiva a realização de análises sobre os processos utilizados no desenvolvimento desses projetos, considerando-se as atividades realizadas, os resultados obtidos e a aplicação de recursos. Na área de Engenharia de Software, processos têm sido propostos nos últimos anos com o objetivo de contribuir para o desenvolvimento de projetos de pesquisa que envolvem software. Busca-se, de forma geral, auxiliar o gerenciamento dos diversos artefatos que podem ser gerados, por exemplo, modelos, código fonte, relatórios técnicos e artigos científicos. As soluções apresentadas na literatura começaram a ser propostas recentemente e, portanto, os estudos realizados nessa área apresentam-se em estágio bastante inicial. Dessa forma, o objetivo deste trabalho foi definir um processo para o desenvolvimento de projetos de pesquisa envolvendo software, que esteja de acordo com um conjunto de requisitos identificado e que possa contribuir para a evolução desses projetos. Para reforçar a continuidade dos projetos, foi estudada a abordagem de design rationale, com o objetivo de oferecer meios para que as decisões sejam capturadas e registradas em fases específicas do desenvolvimento. O processo de documentação foi enfatizado, ou seja, foi investigado como a abordagem de design rationale poderia ser utilizada para melhorar a documentação dos projetos de pesquisa. Como um resultado obtido, foi definido um modelo para representação de design rationale (DR-SACI), implementado em uma ferramenta CASE e avaliado em um experimentoThe increasing volume of research projects in the context of software is a motivation for analyzing processes which are used to develop such projects, regarding activities that are carried out, results that are gathered and application of resources. In the Software Engineering area, recently, processes have been considered with the objective to contribute for research projects development in which software is an element. Overall, the main purpose is to help management overtime of artifacts that can be produced, such as, models, code, technical reports and scientific papers. However, research developed in this direction and solutions discussed in the literature are presented in an initial stage. Therefore, the objective of this work was to define a process for development of research projects regarding a set of requirements. It is expected that such process can be useful to contribute for evolution of these projects. To reinforce the aspect of research project evolution, the design rationale approach was studied. The goal was to provide the opportunity of capturing and registering decisions in specific development phases. The documentation process was emphasized, i.e., the design rationale approach was analyzed focusing on the improvement of research projects documentation. As a result, a model for design rationale representation was defined, implemented in a CASE tool and evaluated by means of an experiment
45
Alcantara, Primo T. "Development of a computer-understandable representation of design rationale to support value engineering." Diss., Virginia Tech, 1996. http://hdl.handle.net/10919/37208.
Full textAbstract:
The life span of facilities produced by the Architecture-Engineering-Construction industry is typically 25 years or more Several distinct phases characterize the life span of a facility. Each of these phases involve numerous participants from different professional disciplines. These participants generate and use a lot of information about the facility. Current methods used by the industry to convey this information are drawings and specifications. However. these drawings and specifications reflect only a summary of the information generated and used by the project participants This summarized information only describes the product. Information about the process of generating these information becomes implicit in the drawings and specifications. Rationale is the collective term for this set of implicit process information.
The main issue addressed by this dissertation is the need to communicate design rationale information. Design rationale is a subset of the entire rationale generated for a facility Design rationale refers to information about the design process. Explicitly stating design rationale information reduces the chance of misinterpreting design drawings and specifications.
The primary objective of this dissertation is to determine a data structure capable of representing design rationale information. This data structure also allows a computer system to perform analytical tasks on the design rationale data. Examples of analytical tasks a computer system can perform on design rationale data include: generating a parameter dependency network and resolving data conflicts. This dissertation defines this data structure as two separate but complementary modules. The Knowledge Representation Module assists in gathering project-specific product information. The Rationale Storage Module assists in capturing project-specific process information. This dissertation discusses each of these two modules in detail.
The secondary objectives of this dissertation include: (1) defining a computer program architecture, (2) creating a computer program interface, and (3) verifying the appropriateness of the data structure in representing design rationale. A proof-of-concept computer program, DRIVE, applied to an actual value engineering study project accomplishes these objectives.Ph. D.
46
Kennedy, Emily Barbara. "Biomimicry in Industry: The Philosophical and Empirical Rationale for Reimagining R&D." University of Akron / OhioLINK, 2017. http://rave.ohiolink.edu/etdc/view?acc_num=akron1491505696395819.
Full text
47
Peña, Feniosky A. (Feniosky Avelhermi). "Design rationale for computer supported conflict mitigation during the design-construction process of large-scale civil engineering systems." Thesis, Massachusetts Institute of Technology, 1994. http://hdl.handle.net/1721.1/11633.
Full text
48
Hoisl, Bernhard, and Stefan Sobernig. "A Survey on Documenting and Using Design Rationale when Developing Domain-specific Modeling Languages." WU Vienna University of Economics and Business, 2016. http://epub.wu.ac.at/4920/1/report.pdf.
Full textAbstract:
This document reports on the results of a survey which is part of a long-term research project conducted at the Institute for Information Systems and New Media at the Vienna University of Economics and Business (WU Vienna) and which targeted experts on domain-pecific modeling languages (DSMLs). We define a DSML as being a specialized modeling language tailored primarily for graphical modeling tasks in a particular application domain, supporting the model-driven development (MDD) of software systems for this domain. As a special kind of domain-specific languages (DSLs), DSMLs provide end users with at least one graphical or diagrammatic concrete syntax; in contrast to textual or form/table-based DSLs, for instance. We asked DSML experts identified via dedicated scientific venues (e.g. authors of published articles, program committee members of conferences, associate editors of journals) to take part in the survey. Venues included premier outlets for researchers and practitioners in the field of MDD and DSMLs, such as, the ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MoDELS) or the International Journal on Software and Systems Modeling (SoSyM). With this survey, we collected expert opinions on different aspects of documenting and using design rationale when developing DSMLs. In the context of DSML development, design rationale is the reasoning and justification of decisions made when designing, creating, and using the core artifacts of a DSML (e.g. abstract and concrete syntax, behavior specification, metamodeling infrastructure, MDD tool chain). (authors' abstract)Series: Technical Reports / Institute for Information Systems and New Media
49
Filho, Adalberto Gonzaga da Silva. "Wikis para suporte à documentação de processo de software livre." Universidade de São Paulo, 2011. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-29072011-101723/.
Full textAbstract:
Um processo de software é definido pelas diversas atividades comumente efetuadas durante o desenvolvimento de software, considerando que tais atividades sejam realizadas sob políticas bem definidas e procedimentos bem estabelecidos. Assim, existem diversos modelos de processo de desenvolvimento de software, que visam garantir a qualidade do produto desenvolvido por meio de tal processo. Identificando a necessidade de processos de software específicos para o desenvolvimento de software livre, devido aos modelos tradicionais não considerarem as características do desenvolvimento deste tipo de software, foi proposto no contexto do Projeto QualiPSo o modelo OMM (Open Source Maturity Model). Com o intuito de contribuir com o modelo OMM e a comunidade de software livre, esse trabalho teve como um de seus objetivos a análise do emprego de wikis no processo de desenvolvimento de software. Outro objetivo dessa pesquisa foi o desenvolvimento de uma ferramenta para mensurar o quanto de documentação e registro de Design Rationale tem sido realizado em uma wikiA software process is defined by several activities commonly performed during the software development, whereas such activities are conducted under well defined policies and and well established procedures. Thus, there are various models of software development process designed to ensure the quality of the product developed through this processes. By identifying the need for software processes specific to the development of free software, due to traditional models do not consider the characteristics of this type of software, the OMM Model (Open Source Maturity Model) was proposed in the the QualiPSos project context. Aiming to contribute with the OMM model and free software community, one of this work objectives was the analysis of using wikis in the software development process. The other objective of this research was to develop a tool to measure how much documentation and registration of Design Rationale has been performed in a wiki
50
Craft, Brandan. "Why Branding Can Increase a Professional Athlete's Value: A Rationale for Designer Engagement." Columbus, Ohio : Ohio State University, 2008. http://rave.ohiolink.edu/etdc/view?acc%5Fnum=osu1212006927.
Full text