Dissertations / Theses on the topic 'Software development/design'
To see the other types of publications on this topic, follow the link: Software development/design.
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 'Software development/design.'
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
Izguden, Mustafa. "Design Software Development For Induction Motors." Master's thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613229/index.pdf.
Full textAbstract:
The purpose of this thesis has been to convert two softwares called TPCAD (Three Phase Induction Machine Computer Aided Desing) and SPCAD (Single Phase Induction Machine Computer Aided Design) developed earlier for the design and analysis of three and single phase induction machines to meet the needs of motor manufacturing industry so that they can be run in windows environment. Furthermore, it was aimed to include features such as double cage motor analysis and design, to provide a facility designed motor lamination can be drawn for the user to see and facilitate sharing the designed lamination with other professional programs such as finite element analysis or thermal analysis etc.
As a result of this study, a user friendly design tool facilitating the design process of induction motors has been upgraded by using C++ Microsoft Visual Studio .Net programming language. TPCAD and SPCAD are tested with different commercial motors. The results show that the full load performance calculations are within the range of 5% error for both programs. However, starting performance calculation errors are within 10% for TPCAD, and 8% for SPCAD.
2
Ke, Yuqing S. M. Massachusetts Institute of Technology. "Assessing various software development methodologies and matching software development methodologies with projects." Thesis, Massachusetts Institute of Technology, 2019. https://hdl.handle.net/1721.1/122438.
Full textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019Cataloged from PDF version of thesis.
Includes bibliographical references (pages 157-158).
As the software industry evolves, various software development methodologies have become widely used in the industry. Most commonly used methodologies are Waterfall and Agile, along with less known alternatives, such as spiral and hybrid methodologies. When deciding on the methodologies, program managers tend to choose one based on the team preference or historical pattern. However, each software project is unique in its own way and has characteristics that are distinct from the previous projects the team has worked on. For each project, it is crucial to adopt a suitable methodology that help teams to produce the software that meets customer needs within schedule and budget constraints. Therefore, a practical question for every program manager is "How to find a suitable methodology for a specific project?" This thesis is aimed to help program managers answer this question.
We first explore how to evaluate each software development methodology based on the two-level decomposition of software development methodology, then analyze the project characteristics based on the situational inputs in three categories: scope, schedule and budget. Thereafter, the thesis proposes a framework to match software development methodology with a specific project. This thesis extends West's work in [1] by introducing a systems approach to assess a software project and a framework to determine the degree of compatibility between a methodology and a software project. The benefits of leveraging the systems approach are: ** The decomposition of methodologies highlights which elements in a methodology play key roles of providing the advantageous ilities over other methodologies. ** The decomposition of a project enables a program manager to evaluate the input elements of a project and gain a systems view on the project characteristics.
The framework allows program managers to compare several candidate methodologies and choose the most compatible one using the mismatch scores, weighted summations that indicate the incompatibilities between the candidate methodologies and the project based on the ilities ranking decided by the program managers. To demonstrate how to use this framework for a real world project, an example project is given. The detailed steps of calculating the mismatch scores between three methodologies and the project are shown. The proposed framework can be used as a guideline for program managers to find methodologies for different projects with the information gathered from project stakeholders. This framework has some limitations. A major one is that, since the framework is quantitative based, induvial experience is used to evaluate the elements of methodologies and factors of projects.
Further work can be done to improve the objectivity of the evaluation through the surveys of industrial experts and members of teams adopting this framework.
by Yuqing Ke.
S.M. in Engineering and Management
S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program
3
Moore, Freeman Leroy. "Quantifying Design Principles in Reusable Software Components." Thesis, University of North Texas, 1995. https://digital.library.unt.edu/ark:/67531/metadc278795/.
Full textAbstract:
Software reuse can occur in various places during the software development cycle. Reuse of existing source code is the most commonly practiced form of software reuse. One of the key requirements for software reuse is readability, thus the interest in the use of data abstraction, inheritance, modularity, and aspects of the visible portion of module specifications. This research analyzed the contents of software reuse libraries to answer the basic question of what makes a good reusable software component. The approach taken was to measure and analyze various software metrics as mapped to design characteristics. A related research question investigated the change in the design principles over time. This was measured by comparing sets of Ada reuse libraries categorized into two time periods. It was discovered that recently developed Ada reuse components scored better on readability than earlier developed components. A benefit of this research has been the development of a set of "design for reuse" guidelines. These guidelines address coding practices as well as design principles for an Ada implementation. C++ software reuse libraries were also analyzed to determine if design principles can be applied in a language independent fashion. This research used cyclomatic complexity metrics, software science metrics, and traditional static code metrics to measure design features. This research provides at least three original contributions. First it collects empirical data about existing reuse libraries. Second, it develops a readability measure for software libraries which can aid in comparing libraries. And third, this research developed a set of coding and design guidelines for developers of reusable software. Future research can investigate how design principles for C++ change over time. Another topic for research is the investigation of systems employing reused components to determine which libraries are more successfully used than others.
4
Van, Der Merwe Ruan. "Development of tailorable mechanical design support software." Thesis, Stellenbosch : Stellenbosch University, 2013. http://hdl.handle.net/10019.1/85664.
Full textAbstract:
Thesis (MScEng)-- Stellenbosch University, 2013.ENGLISH ABSTRACT: A wide variety of design methodologies exist in literature and the methodologies employed may differ among companies and even among design teams. Therefore a software tool, called DiDeas II, is being developed for the early phases of mechanical engineering design. DiDeas II is customisable to accommodate various design methodologies. An approach for customisability which allows the user interface and data structure to be customised without changing the source code has been implemented in previous developments via an approach combining ontology and conceptual graphs. This approach is expanded in this thesis to allow for the implementation of various design methodologies through the use of tables for the display of information with inheritance of data among these tables. During groupwork, communication is both asynchronous and synchronous. DiDeas II has been developed in this thesis to facilitate and capture both asynchronous and synchronous communication between team members. Capturing such communications has the potential to provide insight into design decisions. The communication functionality was assessed in case studies in an academic environment. DiDeas II proved to be effective at recording “soft” information during design and placing the information into context for future reference. The degree to which DiDeas II could be customised to suit the design process at different companies was assessed through discussions with engineers in industry. These discussions showed that it was possible to customise DiDeas II according to the design processes followed by the participants.
AFRIKAANSE OPSOMMING: „n Wye verskeidenheid ontwerpsmetodologieë bestaan in die literatuur en die metodologieë wat gebruik word kan tussen maatskappye en selfs tussen ontwerpspanne verskil. Daarom word „n sagteware-hulpmiddel, genaamd DiDeas II, ontwikkel vir die vroeë fases van meganiese ingenieursontwerp. DiDeas II is pasbaar om voorsiening te maak vir verskeie ontwerpsmetodologieë. „n Benadering vir pasbaarheid wat toelaat dat die gebruikerskoppelvlak en datastruktuur aangepas kan word sonder om veranderings aan die bron-kode te maak, is geïmplementeer in vorige ontwikkelings deur „n benadering wat ontologie en konseptuele grafieke kombineer. Hierdie benadering is in hierdie tesis uitgebrei om voorsiening te maak vir die implementering van verskeie ontwerpsmetodologieë d.m.v. tabelle vir die vertoon van informasie, met data wat “oorgeërf” word tussen hierdie tabelle. Kommunikasie is beide asinkroon en sinkroon tydens groepwerk. DiDeas II is in hierdie tesis verder ontwikkel om beide asinkrone en sinkrone kommunikasie metodes te bemiddel en daarvan rekord te hou. Die rekordhouding van sulke kommunikasie het die potensiaal om insig te bied aangaande ontwerpbesluite. Die kommunikasie funksionaliteit is geassesseer in gevallestudies in „n akademiese omgewing. DiDeas II was effektief in die rekordhouding van “sagte” informasie tydens ontwerp, sowel as om sulke informasie binne konteks te plaas vir latere verwysing. Die mate waartoe DiDeas II aangepas kan word om voorsiening te maak vir die ontwerpsprosesse van verskillende maatskappye, is geassesseer deur gesprekke met ingenieurs in industrie. Hierdie gesprekke het getoon dat dit moontlik is om DiDeas II aan te pas volgens die ontwerpsprosesse wat die deelnemers gebruik.
5
Haapala, O. (Olli). "Application software development via model based design." Master's thesis, University of Oulu, 2015. http://urn.fi/URN:NBN:fi:oulu-201504021268.
Full textAbstract:
This thesis was set to study the utilization of the MathWorks’ Simulink® program in model based application software development and its compatibility with the Vacon 100 inverter. The target was to identify all the problems related to everyday usage of this method and create a white paper of how to execute a model based design to create a Vacon 100 compatible system software. Before this thesis was started, there was very little knowledge of the compatibility of this method. However during the practical experiments, it became quite quickly clear that this method is very compatible with the Vacon 100. Majority of the problems expected before this thesis was started proved to be wrong. The only permanent problem that came up during this thesis was that Vacon 100 supports only the 32-bit floating-point precision while Simulink uses the 64-bit floating-point precision by default. Even though this data type incompatibility prevents usage of some of the Simulink’s blocks, it is by no means a limiting factor that restricts usage of this method. During the practical research no problems were found that completely prevent the usage of this method with the Vacon 100 inverter. The Simulink PLC Coder was in the spotlight during the practical research work. Even though the code generator worked better than was expected, the biggest problems limiting the usage of model based design relates to the PLC Coder. All in all based on this study, it is easy to say that model based design is a very usable tool for everyday design work. The method does not necessarily show its advantages in a small scale design work and the implementation phase can take some time before the company has collected the support model library needed. However in the future, the software requirements will increase, which grows the importance of model based design. A well-executed model based design can have a significant improving effect on financial, time and quality aspectsTämän lopputyön tarkoituksena oli tutkia MathWorks:n Simulink®-ohjelmiston käyttöä mallipohjaisessa ohjelmistotuotannossa ja sen soveltuvuutta Vacon 100 -taajusmuuntajan ohjelmointiin. Tavoitteena oli identifioida kaikki ongelmakohdat, jotka vaikuttavat menetelmän jokapäiväisessä hyödyntämisessä, sekä luoda raportti, miten menetelmän avulla voidaan tehdä Vacon 100 yhteensopiva ohjelmisto. Ennen työn aloittamista menetelmän soveltuvuudesta ei ollut tarkkaa tietoa. Työn aikana suoritetut käytännönläheiset ohjelmistotuotantoesimerkit kuitenkin osoittivat nopeasti menetelmän toimivuuden. Ongelmakohdat, joita ajateltiin ennen työn aloittamista, osoittautuivat pääosin vääriksi. Ainoa pysyvä ongelmakohta, joka työn aikana tuli esille, on Vacon 100:n tuki vain 32-bit reaaliluvuille, kun taas Simulink käyttää oletuksena 64-bit reaalilukua. Vaikka datatyypistä aiheutuva ongelma estääkin muutaman Simulink-lohkon käytön, se ei kuitenkaan ole menetelmän käyttöä rajoittava ongelma. Työssä ei tullut vastaan yhtään ongelmaa, joka olisi estänyt mallipohjaisen suunnittelun käytön Vacon 100 -laitteen kanssa. Simulink:n koodigenerointityökalu eli Simulink PLC Coderon tärkeässä osassa työn tutkimuksen kannalta. Kaiken kaikkiaan koodigeneraattori toimi yli odotusten, mutta suurimmat ongelmat, jotka rajoittavat mallipohjaisen suunnittelun käyttöä, liittyvät kuitenkin PLC Coder:n toimintaan. Yhteenvetona työn perusteella voidaan todeta, että mallipohjainen ohjelmistotuotanto on nykyaikana erittäin käyttökelpoinen menetelmä. Tosin menetelmän tuomat hyödyt eivät välttämättä tule esille pienessä mittakaavassa ja ennen kuin yritykselle on muodostunut omaan tuotteeseen liittyvien mallien ja lohkojen tietokanta. Tulevaisuudessa kuitenkin suunnittelutyön vaatimusten kasvaessa, mallipohjaisen ohjelmistotuotannon merkitys tulee kasvamaan. Hyvin toteutettuna menetelmä parantaa huomattavasti suunnittelutyön tulosta niin taloudellisesti, ajallisesti kuin laadullisestikin
6
Hu, Wei 1972. "Managing embedded software development in China." Thesis, Massachusetts Institute of Technology, 2003. http://hdl.handle.net/1721.1/30053.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, February 2004.Includes bibliographical references.
As microprocessors have become smaller and cheaper, they are embedded in more and more non-computing products, such as washing machines, elevators, MP3 players and printers. It has been estimated that these products consumed 99% of the worldwide production of microprocessors. I In general, "Embedded system" means a computer system sitting inside a product other than a computer to make the product more flexible and controllable. For example, a modem washing machine has a control software system to execute different "washing programs" for different types of clothes. Embedded systems usually have strict requirements on response time, and the response must be generated within a finite and specified period, though depending on the situation, the time could be within a few milliseconds or a few seconds. Because of the special requirement on response time, embedded systems are sometimes called real-time systems. Embedded systems can be divided into two categories: hard and soft, according to the degree of required "timeliness" 2 . A hard embedded system is stringent on that the response must occur within a specified timeline. Typical examples are flight-control systems and missile control systems. A soft embedded system is less strict: response time is important but the system still can function properly given occasionally missed deadline. Examples are mobile phones, printers, and medical devices. This paper is only concerned with development of the soft-embedded systems, and hence the term "embedded systems" in the paper means "soft embedded systems".
by Wei Hu.
S.M.
7
Morgan, Thane (Thane J. ). 1962. "Lean manufacturing techniques applied to software development." Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/9575.
Full text
8
Love, Randall James. "Predictive software design measures." Thesis, This resource online, 1994. http://scholar.lib.vt.edu/theses/available/etd-06112009-063248/.
Full text
9
Yacoub, Sherif M. "Pattern-oriented analysis and design (POAD) a methodology for software development /." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1026.
Full textAbstract:
Thesis (Ph. D.)--West Virginia University, 1999.Title from document title page. Document formatted into pages; contains xx, 343 p. : ill. (some col.). Vita. Includes abstract. Includes bibliographical references (p. 324-337).
10
Murray, Collin (Collin J. ). "Lean and agile software development : a case study." Thesis, Massachusetts Institute of Technology, 2008. http://hdl.handle.net/1721.1/43176.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2008."February 2008."
Includes bibliographical references (p. 89-90).
This paper looks at agile and lean development transitions for organizations that formerly used the waterfall style of development. There has been lots written about the positive aspects of agile software development and the anticipated benefits are widely touted. Through my research I became aware of significant obstacles that organizations can encounter when adopting an agile development method. The obstacles seem to be more applicable to organizations that use the waterfall development method and are compounded when legacy products exist. The intent of this thesis is to identify positive and challenging aspects for organizations that undertake a transition from waterfall development to agile development.
by Collin Murray.
S.M.
11
Pepin, Ronald (Ronald Raymond) 1961. "Application of critical chain to staged software development." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/9750.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 1999.Includes bibliographical references (leaves 58-59).
One in three IT projects are canceled before they are completed. Of the projects that are completed, over 75% are late, over budget or are released with reduced functionality. Average cost overruns are 189%; average schedule overruns are 222% (The Standish Group). The software development process and the project management techniques are critical components in completing a development project on time and on budget. Critical Chain Project Management techniques and a Staged Development process were designed to address issues that contribute to the large number of schedule and cost overruns. Critical Chain is based on Theory of Constraint principles developed by Eliyahu Go ldratt. Critical Chain offers practical methods for planning, scheduling, tracking and mitigating schedule risk in a development program. Staged Development, a form of an incremental product development lifecycle, is considered to be a software development best practice. Staged Development promises faster development schedules, increase progress visibility and higher quality. In this study the author researches, applies and analyzes the Critical Chain and Staged Development methodologies. The combination of the two methodologies created a process that served to increase likelihood of project success.
by Ronald Pepin.
S.M.
12
Rais, Aziz. "Interface-Based Software Development." Doctoral thesis, Vysoká škola ekonomická v Praze, 2017. http://www.nusl.cz/ntk/nusl-264730.
Full textAbstract:
Even though there are many software development and project management methodologies available, research and practice both show that IT software development projects still fail, and that the quality of software products does not always meet customers' expectations. There might be multiple causes for such failures, but some of these reasons can be seen to influence or create others. Therefore, the larger the project is, the higher its risk of failure, especially if the teams involved work remotely (distributed and outsourced). This increase in project complexity is considered the motivation for this paper. Similarly, there are other factors that can result in a project's failure and customers' dissatisfaction regarding software quality. All such factors identified by research conducted by organizations specializing in this area are analyzed in order to identify a common root of IT project failures. Once the root causes of these failures have been identified and analyzed, the goal of the Interface based software development methodology is to solve them. The solution offered by an Interface based software development methodology is to improve understanding of software requirements and to describe these requirements with interfaces in an object-oriented way. Interface based software development will support and drive development towards service-oriented architecture (SOA) and component-based development (CBD). The goal of interface based software development is to increase software testability and maintainability and to make it more easily feasible to execute various software development processes in parallel.
13
Ng, Andrew Eng Jwee. "Switched-current filtering systems : design, synthesis and software development." Thesis, University of Glasgow, 1999. http://theses.gla.ac.uk/5040/.
Full textAbstract:
Allpass filters are commonly employed in many applications to perform group delay equalisation in the passband. They are non-minimum phase by definition and are characterised by poles and zeros in mirror-image symmetry. SI allpass filters of both cascade biquad and bilinear-LDI ladder types have been in existence. These were implemented using Euler based integrators. Cascade biquads are known to have highly sensitive amplitude responses and Euler integrators suffer from excess phase. The equalisers that are proposed here are based on bilinear integrators instead of Euler ones. Derivation of these equalisers can proceed from either the s-domain, or directly from the z-domain, where a prototype is synthesised using the respective continued-fractions expansions, and simulated using standard matrix methods. The amplitude response of the bilinear allpass filter is shown to be completely insensitive to deviations in the reactive ladder section. Simulations of sensitivities and non-ideal responses reveal the advantages and disadvantages of the various structures. Existing DI multirate filters have to date been implemented as direct-form FIR and IIR polyphase structures, or as simple cascade biquad or ladder structures with non-optimum settling times. FIR structures require a large number of impulse coefficients to realise highly selective responses. Even in the case of linear phase response with symmetric impulse coefficients, when the number of coefficients can be halved, significant overheads can be incurred by additional multiplexing circuitry. Direct-form IIR structures are simple but are known to be sensitive to coefficient deviations and structures with non-optimum settling times operate entirely at the higher clock frequency. The novel SI decimators and interpolators proposed are based on low sensitivity ladder structures coupled with FIR polyphase networks. They operate entirely at the lower clock frequency which maximises the time available for the memory cells to settle. Two different coupling architectures with different advantages and disadvantages are studied.
14
Stiebritz, Martin Tillmann. "Development and experimental validation of a protein design software." kostenfrei, 2008. http://www.opus.ub.uni-erlangen.de/opus/volltexte/2008/1060/.
Full text
15
Barratt, Dean M. "An analysis of system development tools." Virtual Press, 1990. http://liblink.bsu.edu/uhtbin/catkey/722786.
Full textAbstract:
The development of a software package is a complex and time consuming process. Computer Assisted Software Engineering (CASE) tools, such as Excelerator, DesignAid and SA Tools have offered an alternative to the traditional methods of system design. While the use of these design tools can lessen the burden of project management, there currently exists no systematic method for describing or evaluating existing products.This study identifies criteria for software development tools by examining three products used in a PC-based computing environment. The three software development tools studied are DesignAid version 4.0 by Nastec Corporation, SA Tools by Tekcase Corporation, and Excelerator version 1.7 by Index Technology Corporation. In order to give the "look and feel" of the products, the same design project is implemented on each of the tools. Then each product is evaluated with respect to a given set of criteria.Department of Computer Science
16
Adhyapak, Sriram. "ASDN : Automated Software Design Notebook tool." FIU Digital Commons, 1990. http://digitalcommons.fiu.edu/etd/1087.
Full textAbstract:
Software Engineering is one of the most widely researched areas of Computer Science. The ability to reuse software, much like reuse of hardware components is one of the key issues in software development. The object-oriented programming methodology is revolutionary in that it promotes software reusability.
This thesis describes the development of a tool that helps programmers to design and implement software from within the Smalltalk Environment (an Object- Oriented programming environment). The ASDN tool is part of the PEREAM (Programming Environment for the Reuse and Evolution of Abstract Models) system, which advocates incremental development of software.
The Asdn tool along with the PEREAM system seeks to enhance the Smalltalk programming environment by providing facilities for structured development of abstractions (concepts). It produces a document that describes the abstractions that are developed using this tool. The features of the ASDN tool are illustrated by an example.
17
Zamouril, Jakub. "Flight Software Development for Demise Observation Capsule." Thesis, Luleå tekniska universitet, Rymdteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-64420.
Full textAbstract:
This work describes the process of the design of a flight software for a space-qualified device, outlines the development and testing of the SW, and provides a description of the final product. The flight software described in this work has been developed for the project Demise Observation Capsule (DOC). DOC is a device planned to be attached to an upper stage of a launch vehicle and observe its demise during atmospheric re-entry at the end of its mission. Due to constraint on communication time during the mission and the need to maximize the amount of transferred data, a custom communication protocol has been developed.Demise Observation Capsule
18
Mkpong-Ruffin, Idongesit Okon Umphress David A. Hamilton John A. "Quantitative risk assessment model for software security in the design phase of software development." Auburn, Ala., 2009. http://hdl.handle.net/10415/1584.
Full text
19
Seth, Deepak. "A platform based approach for embedded systems software development." Thesis, Massachusetts Institute of Technology, 2006. http://hdl.handle.net/1721.1/35092.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2006.Includes bibliographical references (leaves 94-96).
A platform based approach for product development allows companies to eliminate redundancies, efficiently utilize its resources and provide products for a wider market. The basic idea is to develop and share key components and to introduce new technologies in as many products as possible. The automobile industry has for long used the concept of product platforms and has successfully achieved savings in development costs and seen a growth in sales and market share. By creating a common software platform, this concept can be applied to software development for embedded systems where software modules and applications can be shared across products within a product family. This provides better code reuse and increases standardizations across products. This thesis will examine how the concept of platforms can be applied to software development from the viewpoint of the telecommunications industry. By using the power of a common software platform, telecommunication equipment makers can accelerate product delivery and introduce new technologies to a wider range of customers. With the right strategy, they can also make their products into platforms that serve as a foundation on which other companies can develop products and offer their services.
by Deepak Seth.
S.M.
20
Ramsay, Craig Douglas. "Seeking improvements in detailed design support for software development projects." Thesis, University of Dundee, 2012. https://discovery.dundee.ac.uk/en/studentTheses/643486ad-50ee-4d7d-8546-2d8fadcab2c7.
Full textAbstract:
Evidence from literature indicates prevailing issues in relation to the documentation of software systems. Documentation requires significant effort to create and maintain and this can often reduce the inclination to produce it in a timely manner and to ensure that it remains up to date with the program which code it corresponds to. As a result, documentation is not entirely trusted as a source of consultation during software maintenance tasks. Existing tool support neglects important aspects of detailed design documentation for software systems. This work proposes a design for a novel research tool which provides improved support for the detailed design and documentation of software systems and which addresses the prevailing issues identified. At the core of this tool is a ‘dynamic synchronization’ feature which automates the process of detecting and synchronizing changes between program code and documentation at the level of detailed algorithms in code; preventing them from getting out of date. An evaluation experiment was designed and conducted wherein the research tool was used to complete a series of programming and documentation tasks representing typical software development and code maintenance scenarios. The results show that software developers using the dynamic synchronization feature had a significant 66 percent reduction in the time required to keep their documentation up to date during a code maintenance task (p < 0.01), and a significant 31 percent reduction in the time to complete the maintenance task (p < 0.01). In a questionnaire, they expressed a significant 20 percent higher confidence level that their documentation was an accurate reflection of their code than software developers using non-synchronized forms of documentation (subjective measure, p = 0.03). Further areas of research and development are proposed.
21
Lee, Jason Chong. "Integrating scenario-based usability engineering and agile software development." Diss., Virginia Tech, 2010. http://hdl.handle.net/10919/26729.
Full textAbstract:
Agile development methodologies are becoming increasingly popular because they address many risks of software development through things such as quick delivery of working software and responsiveness to change. As agile organizations have begun to develop more user interface-intensive systems, they understand the value and need to design more usable systems. The fields of usability engineering and human-computer interaction are focused on exploring how people interact with computer systems. However, much of this work is inaccessible to agile practitioners because it does not align with core agile values and because there has not been adequate transfer of knowledge between practice and academia.
This motivated my creation of the eXtreme Scenario-Based Design (XSBD) process, an integrated agile usability approach. XSBD provides key usability benefits of the scenario-based design (SBD) approach (an established usability engineering process) and is compatible with an agile development framework modeled on leading agile processes like XP and Scrum. XSBD was designed for use in projects in which a large part of the overall system quality is determined by system usability. This requires close communication and coordination of the disparate usability and agile development work practices. A core aspect of XSBD is the central design record (CDR), which is the shared design representation that guides usability design. It tightly couples usability evaluation results to design features and high level project goals, allowing the usability engineer to leverage key benefits of traditional SBD while working in an agile framework.
I began developing XSBD at Virginia Tech, evaluating it through several student-led development efforts. To improve and demonstrate the applicability of XSBD in practice, I partnered with Meridium, Inc., a software and services company. Using an action research case study method, I worked with several development teams there who used XSBD to develop products. This directly linked usability and HCI research to practice, allowing me to demonstrate XSBDâ s utility in practice while evaluating it from a theoretical perspective. The results of this work suggest several avenues for further work both to increase its adoption in practice and to link to existing HCI research efforts such as design rationale and knowledge reuse.Ph. D.
22
Heerjee, K. B. "An interactive, graphical, program design and development environment." Thesis, University of Abertay Dundee, 1988. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.382796.
Full textAbstract:
New software development methodologies are being produced with increasing frequency. The latest techniques claim to produce software of unprecedented reliability and productivity, yet are seldom substantiated by empirical evidence. Researchers in the field of human-computer interactions have long held the view that well designed interactive systems increase performance levels over conventional techniques. Intuitively this seems logical, but very little work has been done to substantiate this claim empirically. This thesis aims to show that well designed structured programming environments provide productivity gains and increase performance levels over conventional techniques. An Animated Programming Environment (APE), has been developed which is an interactive, graphical, program design and development system that embodies structured programming and top-down design. The system supports the development of programs for a variety of block structured languages whilst working conceptually at the level of Jackson diagrams. Formal methods were applied to validate and verify the APE system. The immediate benefits are an increased understanding of the system and the detection of some errors in the implementation. By interrogating the implementation and documentation, axiomatic specifications were written and a prototype of the APE system developed in Standard ML. The principal benefit of constructing a formal model is the development of a framework to aid communication between personnel involved with system maintenance. The model can also be used to investigate future changes, and since this framework provides relevant abstraction of user and system behaviour it should facilitate improved documentation and user learning. Evaluation of the system was carried out during the design and implementation stages of the development life-cycle. The evaluation was based on responses to a questionnaire and a comparison with conventional means of generating code. The questionnaire evaluation elicited users' general impressions about the system and its interface, and their detailed views on more specific aspects of the system. The comparative evaluation showed no difference in the median quality of the solution to a programming problem, but a significantly reduced time and variance in quality compared to conventional methods.
23
Anderfelt, Victor. "From Mob Programming to Mob Development : User-Centred Design in Collaborative Software Development." Thesis, Uppsala universitet, Institutionen för informatik och media, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-414221.
Full textAbstract:
Mob programming is a collaborative software development method that has gained increasing attention in both industry and research. While the focus of mob programming is on the benefits of teams programming together, there are also potential benefits for other aspects of the software development process. However, there is a lack of research on the use of the method outside the domain of programming. This study explores user-centred design (UCD) in mob programming through a case study of three software development teams at Sveriges Television, a Swedish public broadcasting company. Results show that the teams use the method for a variety of tasks in their daily work, calling for a rebranding of the method to mob development to encompass the broader scope. The integration of UCD is analysed through the principles of user-centred agile software development. The results indicate that a revision of these principles is needed to include the cross-functional and social factors that mob development adds to the software development process.
24
Eralp, Ozgur. "Design And Implementation Of A Software Development Process Measurement System." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12604771/index.pdf.
Full textAbstract:
This thesis study presents a software measurement program. The literature on software measurement is reviewed. Conditions for an effective implementation are investigated. A specific measurement system is designed and implemented in ASELSAN, Inc. This has involved organizational as well as technical work. A software tool has been developed to assist in aggregating measurements obtained from various CASE tools in use. Results of the implementation have started to be achieved. Lots of useful feedbacks have been returned to the organization as a result of analyzing of the measurement data.
25
Naidu, I. Ajit. "Design and development of SINK, a software INteractions knowledge system." Master's thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-12232009-020100/.
Full text
26
Chapman, William James. "The development, design, and theory of educational interactive multimedia software." CSUSB ScholarWorks, 2002. https://scholarworks.lib.csusb.edu/etd-project/2330.
Full textAbstract:
This project provides teachers and students with background information regarding software design. Specifically it will focus on design theory including content, interface, graphics, animation, navigation, and audio issues which may arise during the design and construction of educational multimedia software. The design issues represented here are demonstrated in the software "You can make a difference ... Human Rights".
27
Pipkin, Jeffrey A. "Applying design metrics to large-scale telecommunications software." Virtual Press, 1996. http://liblink.bsu.edu/uhtbin/catkey/1036178.
Full textAbstract:
The design metrics developed by the Design Metrics team at Ball State University are a suite of metrics that can be applied during the design phase of software development. The benefit of the metrics lies in the fact that the metrics can be applied early in the software development cycle. The suite includes the external design metric De,the internal design metric D27 D(G), the design balance metric DB, and the design connectivity metric DC.The suite of design metrics have been applied to large-scale industrial software as well as student projects. Bell Communications Research of New Jersey has made available a software system that can be used to apply design metrics to large-scale telecommunications software. This thesis presents the suite of design metrics and attempts to determine if the characteristics of telecommunications software are accurately reflected in the conventions used to compute the metrics.Department of Computer Science
28
Stuurman, Christian Phillip. "The development of software for a faxmoden card." Thesis, Cape Technikon, 1995. http://hdl.handle.net/20.500.11838/1068.
Full textAbstract:
Thesis (M.Tech (Electrical Engineering))--Cape Technikon, 1995This thesis describes the design and development ofsoftware for a FAXMODEM card for a personal computer. The software was developed to enable the designed FAXMODEM card to transmit and receive facsimiles independent of the host personal computer.
29
Elberg, Edwin 1970. "A system dynamics approach to the software development business problem." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/88326.
Full text
30
Farebo, Samuel. "User-Centered Design in Agile software development for in-house enterprise tools." Thesis, Umeå universitet, Institutionen för tillämpad fysik och elektronik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-110752.
Full textAbstract:
The Agile software development model is driven by "learning by doing" and rejects Big Design Up Front (BDUF) for that reason. User-Centered Design (UCD) on the other hand requires a more holistic view to be able to create a usable user interface and in the end create a good user experience. Finding a balance between the incremental development and the need for a more comprehensive view of the user interface is therefore the key to usability in Agile software development. The objective of this master thesis was to construct a framework on how to combine UCD and Agile development in general, and specifically for the web based tool, called Alo, at the IS/IT department of Com Hem AB, Sweden. The results of this thesis was that the process of integrating User-Centered Design in Agile software development first of all needs a familiar starting point for both usability experts and developers. This can be achieved with what Desirée Sy describes as “Cycle Zero”, to let usability experts perform initial research ahead of implementation. Designing one sprint ahead should later converge to a more synchronized process where requirements and sketches of the interface are put together, with the help of developers, just in time for the implementation. This does not only prevents waste in the form of documentation and miscommunication associated with hand-offs, but also makes the implementation more purposeful and fun for developers.Secondly, build prototypes early in the process to create a holistic vision of the finished product and to test concepts in usability tests early. Thirdly, create shared understanding (within the development team as well as with outside stakeholders) of user needs by involving the entire team in usability testing. Critical to the success of all the above is that all outside stakeholders understands the Agile process and respects that the team is a self-organizing unit that solves problems within a set of given boundaries, rather than a code factory that feeds on specification documents.
31
Carlstedt-Duke, Edward, and Erik Elfström. "Towards guidelines for development of energy conscious software." Thesis, Linköping University, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-17444.
Full textAbstract:
In recent years, the drive for ever increasing energy efficiency has intensified. The main driving forces behind this development are the increased innovation and adoption of mobile battery powered devices, increasing energy costs, environmental concerns, and strive for denser systems.
This work is meant to serve as a foundation for exploration of energy conscious software. We present an overview of previous work and a background to energy concerns from a software perspective. In addition, we describe and test a few methods for decreasing energy consumption with emphasis on using software parallelism. The experiments are conducted using both a simulation environment and real hardware. Finally, a method for measuring energy consumption on a hardware platform is described.
We conclude that energy conscious software is very dependent on what hardware energy saving features, such as frequency scaling and power management, are available. If the software has a lot of unnecessary, or overcomplicated, work, the energy consumption can be lowered to some extent by optimizing the software and reducing the overhead. If the hardware provides software-controllable energy features, the energy consumption can be lowered dramatically.
For suitable workloads, using parallelism and multi-core technologies seem very promising for producing low power software. Realizing this potential requires a very flexible hardware platform. Most important is to have fine grained control over power management, and voltage and frequency scaling, preferably on a per core basis.
32
Wilburn, Cathy A. "Using the Design Metrics Analyzer to improve software quality." Virtual Press, 1994. http://liblink.bsu.edu/uhtbin/catkey/902489.
Full textAbstract:
Effective software engineering techniques are needed to increase the reliability of software systems, to increase the productivity of development teams, and to reduce the costs of software development. Companies search for an effective software engineering process as they strive to reach higher process maturity levels and produce better software. To aid in this quest for better methods of software engineering. the Design Metrics Research Team at Ball State University has analyzed university and industry software to be able to detect error-prone modules. The research team has developed, tested and validated their design metrics and found them to be highly successful. These metrics were typically collected and calculated by hand. So that these metrics can be collected more consistently, more accurately and faster, the Design Metrics Analyzer for Ada (DMA) was created. The DMA collects metrics from the files submitted based on a subprogram level. The metrics results are then analyzed to yield a list of stress points, which are modules that are considered to be error-prone or difficult for developers. This thesis describes the Design Metrics Analyzer, explains its output and how it functions. Also, ways that the DMA can be used in the software development life cycle are discussed.Department of Computer Science
33
Moghim, Mohammad Reza. "Incorporating design patterns into object-oriented development methods." Thesis, University of Salford, 1999. http://usir.salford.ac.uk/26820/.
Full textAbstract:
Object-oriented methods and design patterns provide valuable design guidance for object-oriented system development. However, they are not competitors, and in fact complement each other in many ways. The research reported in this thesis studied how to apply design patterns and object-oriented methods together to guide system development. It addresses issues such as, how methods need to be changed to accommodate the application of design patterns; how design patterns need to be adapted to fit within methods; and how the heuristics of design patterns may be brought to bear on improving methods. The thesis reports the experience of accommodating six design patterns ( Adapter, Composite, Facade, Mediator, Observer and Strategy ) from the book entitled "Design Patterns Elements of Reusable Object-Oriented Software" by E.Gamma, R. Helm, R.Johnson and J.Vlissides into certain object-oriented methods namely (Responsibility-Driven Design, Object-Oriented Software Engineering and Unified Modelling Language). This experience has been used in the work to generate a general approach for accommodating design patterns into methods. It also shows how the properties of the object-oriented methods and design patterns interact.�
34
Hwang, Yves. "An automated software design synthesis framework." University of Western Australia. School of Electrical, Electronic and Computer Engineering, 2009. http://theses.library.uwa.edu.au/adt-WU2009.0157.
Full textAbstract:
This thesis presents an automated software design synthesis framework known as Project Calliope. This framework aligns with Harel's automated software development process as it addresses the aspect of automating design and implementation. Project Calliope is based on a Statecharts synthesis approach in the literature. The main goal of Project Calliope is to automatically generate testable Unified Modeling Language (UML) Statecharts that are deterministic, visually manageable and UML compliant. In order to minimise design errors in the generated UML Statecharts, Project Calliope supports model checking through Statecharts execution. In addition, executable code is automatically generated based on the synthesised UML Statecharts. This framework seeks to provide a pragmatic design framework that can be readily incorporated into software development methodologies that leverage UML. In this thesis, Project Calliope is applied to three simple applications from Whittle and Schumann's examples and a case study based on a commercial application. They are automatic teller machine, coffee dispenser, an agent application, and a groupware application respectively.
35
Quezada, Gomez Juan Manuel. "Model-based guidelines for automotive electronic systems software development." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100383.
Full textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.Cataloged from PDF version of thesis.
Includes bibliographical references (pages 96-98).
The automobile innovation transformed the human life style ever since its introduction to the public, and for over the last one hundred years incumbent technologies have been adopted to improve its performance characteristics. Yet, we need a holistic approach to understand that automobiles shifted from being a mere assembly of mechanical parts to a multidisciplinary system that form the modern automobile. Thanks to the increased use of electronics and software in automobiles, consumers benefit from better gas mileage, more amenities and features, such as comfort, driving assistance, and entertainment. At the same time, stability and performance of automobiles as systems have been facing deterioration, and eventually vehicle owners are finding that features and functions become inoperative over time, causing frustration, loss of time and money. Reports of problems experienced by vehicle owners have stem from casual factors of system defects that model-based systems engineering can reduce or eliminate. This research presents a model-based systems engineering approach to an automobile electronic system design. The work is founded on a comprehensive OPM model and engineering guidelines for electronic control module software design. The purpose of the framework developed in this study is to support development of complex vehicle software that allows flexibility for changing features and creating new ones, and enables software developers to pinpoint systemic faults quicker and at earlier lifecycle phases, reducing rework, increasing safety, and providing for more effective resolution of such problems.
by Juan Manuel Quezada Gomez.
S.M. in Engineering and Management
36
Webster, David D. "Hardware, software, firmware allocation of functions in systems development." Diss., Virginia Polytechnic Institute and State University, 1987. http://hdl.handle.net/10919/49907.
Full textAbstract:
The top-down development methodology is, for the most part, a well defined subject. There is, however, one area of top-down development that lacks structure and definition. The undefined topic is the hardware, software, and firmware allocation of functions. This research addresses this deficiency in top-down system development. The key objective is the restructuring of the hardware, software, and firmware process from a subjective, qualitative decision process to a structured, quantitative one.
Factors that affect the hardware, software, and firmware allocation process are identified. Qualitative data on the influence of the factors on the allocation process are systematized into quantitative information. This information is used to develop a model to provide a recommendation for implementing a function in hardware, software, or firmware. The model applies three analytical methods: 1) the analytic hierarchy process, 2) the general linear model, and 3) the second order regression technique. These three methods are applied to the quantified information of the hardware, software, firmware allocation process. A computer-based software tool is developed by this research to aid in the evaluation of the hardware, software, and firmware allocation process. The software support tool assists in data collection. Future application of the support tool will enable the capture and documentation of expert knowledge on the hardware, software, and firmware allocation process. The improved knowledge base can be used to improve the model which in tum will improve the system development process, and resulting system.Ph. D.
incomplete_metadata
37
Deanda, Felix. "Development and application of software tools for computer-assisted drug design /." Digital version accessible at:, 1999. http://wwwlib.umi.com/cr/utexas/main.
Full text
38
Udupi, Gopalakrishna. "Design and development of a software module for minimizing transportation costs." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/GUdupi2006.pdf.
Full text
39
Al-Shamma, Omran. "Development of interactive aircraft design software for use in problem based learning." Thesis, University of Hertfordshire, 2013. http://hdl.handle.net/2299/12108.
Full textAbstract:
In the last ten years or so, many interactive aircraft design software packages have been released into the market. One drawback of these packages is that they assume prior knowledge in the field of aircraft design. Also, their main purpose being the preliminary aircraft design in a commercial environment, and are not intended for instructional use. Aircraft Design is an iterative process, and the students in the formative years of training must realise that one year of study is not enough to embrace all the necessary underlying concepts in this field. Most universities present the aircraft design as a classical Problem-Based Learning scenario, where students work in groups, with the group size varying between 5 and 8 students., each with a designated role, to carry out a specific task. The students work through the classical process of preliminary design based largely on textbook methods. Therefore, the need for a preliminary design tool (software) that helps the students to understand, analyse, and evaluate their aircraft design process exists. The developed software does everything that is needed in the preliminary design environment. Students are interactively guided through the design process, in a manner that facilitates lifelong learning. Comprehensive output is provided to highlight the “what if scenarios”. The software consists of many modules such as input (user interface), weight estimation, flight performance, cost estimation, take-off analysis, parametric studies, optimisation, and dynamic stability. Due to the large number of input design variables, a full interactive Graphical-User-Interface (GUI) is developed to enable students to evaluate their designs quickly. Object-Oriented-Programming (OOP) is used to create the GUI environment. The stability and control derivatives computed in this work are largely based on analytical techniques. However, a facility is provided in the software to create the data input file required to run a software package produced by USAF, called DATCOM, that enables computation of the dynamic stability and control derivatives that can be ultimately used in flight simulation work. Amongst all the variables used in aircraft design, aircraft weight is the most significant. A new weight estimation module has been developed to increase the accuracy of estimation to better than 5%. Its output results agree very favourably with the published data of current commercial aircraft such as Airbus and Boeing. Also, a new formula is proposed to estimate the engine weight based on its thrust in the absence of the data available with high degree of accuracy. In order to evaluate the effectiveness of the design under consideration, a comprehensive methodology has been developed that can predict the aircraft price as a function of aircraft weight. The Direct Operating Cost (DOC) is also calculated using methods proposed by ATA, NASA, and AEA. Finally, a walk-through of two case studies are presented, one for large transport aircraft and other for small business jet, to show how typical undergraduate students will proceed with the design and to demonstrate the effectiveness of the developed software.
40
Lockhart, Jonathan A. "Software Development Process and Reliability Quantification for Safety Critical Embedded Systems Design." University of Cincinnati / OhioLINK, 2019. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1562673285477425.
Full text
41
Davies, C. G. "An investigation into computer assisted program and system design." Thesis, University of Manchester, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.382928.
Full text
42
Coskun, Cagdas. "Software Development For Multi Level Petri Net Based Design Inference Network." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12605278/index.pdf.
Full textAbstract:
This thesis presents the computer implementation of a multi resolutional concurrent, design inference network, whose nodes are refined by PNDN (Petri Net Based Design Inference Network) modules. The extended design network is named as N-PNDN and consists of several embedded PNDN modules which models the information flow on a functional basis to facilitate the design automation at the conceptual design phase of an engineering design. Information flow in N-PNDN occurs between parent and child PNDN modules in a hierarchical structure and is provided by the token flow between the modules. In this study, computer implementation of the design network construction and token flow algorithms for the N-PNDN structure is restored and therefore the previous DNS (Design Network Simulator) is adapted for the multi layer design and decomposition of mechatronic products. The related algorithms are developed by using an object oriented, visual programming environment. The graphical user interface is also modified. The further developed DNS has been used for the application of the N-PNDN structure in the conceptual design of 5 mechatronic systems. In the guidance of this study, it has been understood that the further developed DNS is a powerful tool for designers coming from different engineering disciplines in order to interchange their ideas.
43
Gigler, Thomas Russell III. "Moops: A web implementation of the Personal Software Process reporting system." CSUSB ScholarWorks, 2008. https://scholarworks.lib.csusb.edu/etd-project/3382.
Full textAbstract:
The purpose of Moops is to bridge the gap between PSP Scriber, geared very specifically to the CSCI655 class, and other available PSP implications which are so general they are difficult to use immediately without valuable time spent learning the software. Moops is a PHP/MySQL based web application designed to provide the students taking the CSCI655 graduate software engineering course at CSUSB with an intuitive, easy to use tool to implement the Personal Software Process (PSP). Moops eliminates the possibility of errors in calculations by completing all calculations for the user.
44
Gibbon, Cleveland Augustine. "Heuristics for object-oriented design." Thesis, University of Nottingham, 1997. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.388318.
Full text
45
Russell, Gregory B. (Gregory Brian). "A systems analysis of complex software product development dynamics and methods." Thesis, Massachusetts Institute of Technology, 2007. http://hdl.handle.net/1721.1/42371.
Full textAbstract:
Includes bibliographical references (p. 64-65).Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2007.
Software development projects and products have long shouldered a reputation for missed deadlines, blown budgets, and low quality. Unfortunately, this negative reputation appears to be supported by more than just anecdotal evidence; quoting an industry study', respected software development expert and author Steve McConnell reports in his book Professional Software Development" that "Roughly 25 percent of all projects fail outright, and the typical project is 100 percent over budget at the point it's canceled." What's more, notes McConnell, "Fifty percent of projects are delivered late, over-budget, or with less functionality than desired." Exactly why software development projects and products have historically performed so poorly and with arguably little if any improvement over the past 40 years, however, is a subject on which there is less agreement. While blame often aligns along functional (product marketing and sales) versus technical (software development) lines, the increasing popularity of different and often contradictory software development methodologies seems to suggest that no real consensus exists within the software development community itself. The goal of this thesis is twofold: 1. To describe a set of key factors to consider when analyzing software processes 2. To outline an organizational framework that is optimized for implementing and managing software development practices
by Gregory B. Russell.
S.M.
46
Curhan, Lisa A. 1961. "Software defect tracking during new product development of a computer system." Thesis, Massachusetts Institute of Technology, 2005. http://hdl.handle.net/1721.1/34824.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, 2005.Includes bibliographical references (p. 74-75).
Software defects (colloquially known as "bugs") have a major impact on the market acceptance and profitability of computer systems. Sun Microsystems markets both hardware and software for a wide variety of customer needs. The integration of hardware and software is a key core capability for Sun. Minimizing the quantity and impact of software defects on this integration during new product development is essential to execution of a timely and high-quality product. To analyze the effect of software defects on the product development cycle for a midrange computer system, I have used a particular computer platform, the Productl server, as a case study. The objective of this work was to use Sun's extensive database of software defects as a source for data-mining in order to draw conclusions about the types of software defects that tend to occur during new product development and early production ramp. I also interviewed key players on the Productl development team for more insight into the causes and impacts of software defects for this platform. Some of the major themes that resulted from this study include: The impact of defects is not necessarily proportional to their quantity. Some types of defects have a much higher cost to fix due to customer impact, time needed to fix, or the wide distribution of the software in which they are embedded. Software Requirements need to be vetted extensively before production of new code. This is especially critical for platform-specific requirements. The confluence of new features, new software structure and new hardware can lead to a greater density of software defects. The higher number of defects associated with the new System Controller code supports this conclusion. Current Limitations of Defect Data Mining: Automated extraction
(cont.) of information is most efficient when it can be applied to numbers and short text strings. However, the evaluation of software defects for root cause cannot be easily summarized in a few words or numbers. Therefore, an intelligent classification methodology for root causes of software defects, to be included in Sun's defect database, would be extremely useful to increase the utility of the database for institutional learning. Software Defect Data Mining seems to be underutilized at Sun. I have barely touched the surface of the information that can be extracted from our "BugDB" defect database. This data resource is rich with history. We should extract and analyze this type of data frequently.
by Lisa A. Curhan.
S.M.
47
Goynuk, Yilmaz. "Development Of An Electrical Machines Analysis And Optimum Design Software Package." Master's thesis, METU, 2008. http://etd.lib.metu.edu.tr/upload/12609788/index.pdf.
Full textAbstract:
In this study, three different programs are developed for the analysis of the
three-phase induction motor, single-phase capacitor type induction motor
and switched reluctance motor. The programs are developed by using Pascal
and C++ programming languages. In the performance calculations of motors,
analytical methods are used and these methods are tested for accuracy.
These programs have also capabilities to design an optimum motor, which
meets a set of performance, material and manufacturing constraints while
minimizing the weight or any other defined objective function.
In addition, in this study, an optimization tool is used to obtain an appropriate
optimization method for the design of different types of motors.
The software is tested over different commercial motors. The results illustrates
that the performance calculations and optimization approach of the
programs lead to good results.
48
Ingram, Claire. "Using requirements and design information to predict volatility in software development." Thesis, University of Newcastle Upon Tyne, 2011. http://hdl.handle.net/10443/1832.
Full textAbstract:
We hypothesise that data about the requirements and design stages of a software development project can be used to make predictions about the subsequent number of development changes that software components will experience. This would allow managers to concentrate time-consuming efforts (such as traceability and staff training) to a few at-risk, cost-effective areas, and may also allow predictions to be made at an earlier stage than is possible using traditional metrics, such as lines of code. Previous researchers have studied links between change-proneness and metrics such as measures of inheritance, size and code coupling. We extend these studies by including measures of requirements and design activity as well. Firstly we develop structures to model the requirements and design processes, and then propose some new metrics based on these models. The structures are populated using data from a case study project and analysed alongside existing complexity metrics to ascertain whether change-proneness can be predicted. Finally we examine whether combining these metrics with existing metrics improves our ability to make predictions about change-proneness. First results show that our metrics can be linked to the quantity of change experienced by components in a software development project (potentially allowing predictions to take place earlier than before) but that best results are obtained by combining existing complexity metrics such as size, or combining existing metrics with our newer metrics.
49
Eng, Mindy. "Exploring property driven design fabrication through materials testing and software development." Thesis, Massachusetts Institute of Technology, 2010. http://hdl.handle.net/1721.1/65176.
Full textAbstract:
Thesis (S.B.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering, 2010.This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student submitted PDF version of thesis. Vita.
Includes bibliographical references (p. 33).
Since its introduction in the late 1980s, layered manufacturing has become an increasingly efficient and common means to delivering functional and visually representative prototypes in relatively short amounts of time from previously prepared Computer-Aided Design files. However, most layered manufacturing technologies today produce only single material, constant property prototypes from a limited array of materials. In this project, we explore a different approach to layer manufacturing, namely, a layered manufacturing product that, while using a single material, produces an entity of varying material properties. Materials testing of PMC®-724 demonstrate the material's capacity to possess a range of Shore A Hardness over a range of elasticity, illustrating the potential for printing with variable property materials. Moreover, we will also explore a new approach to fabrication that challenges the concept of Computer- Aided Manufacturing (CAM) by introducing a software application that, rather than providing a means of digitizing the geometry of a completed design, allows engineers and designers to create and design structures that are defined at various points by their material behavior as opposed to their geometry. As a proof of concept demonstration, a mono-material, variable property shoe sole will be printed using property-mapped polyurethane elastomer PMC®-724 with the new software.
by Mindy Eng.
S.B.
50
Hermelin, Leidefors Madelen. "In-Place Translation in Software Development : A Design Science Research Approach." Thesis, Uppsala universitet, Institutionen för informatik och media, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-294704.
Full textAbstract:
Computers have been used for natural language translation sincethe 1940s. The role for computers to support translation work has expandedsince the commercialisation of the Internet in the early 1990s.As an implication of ’crowd sourcing’, translation is now supportedby users through community translation, meaning that people - usersof web sites - actively translate web sites into different languages. Inthis thesis we will present Babbler - a novel concept for communitytranslation. Following a design science research approach, a softwarewas designed and implemented in an information systems developmentproject. We present our conceptual design and its software implementation,and evaluate it using different techniques, including log analysis,interviews with translators, and an informed argument contrastingour design to other community translation approaches. The evaluationaddresses various qualities of the design, including effectiveness, efficiency,reliability, workflow, implementability and performance. Basedon our results, we reflect about translations to different target groups(based on demographics such as gender, age and culture), informedby an explorative analysis of translation results in the empirical context.We also show further implications for future design of communitytranslation artefacts, and future research in the area.