Дисертації з теми "Software development/design"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 дисертацій для дослідження на тему "Software development/design".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
Izguden, Mustafa. "Design Software Development For Induction Motors." Master's thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613229/index.pdf.
Повний текст джерела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.
Повний текст джерелаCataloged 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
Moore, Freeman Leroy. "Quantifying Design Principles in Reusable Software Components." Thesis, University of North Texas, 1995. https://digital.library.unt.edu/ark:/67531/metadc278795/.
Повний текст джерелаVan, Der Merwe Ruan. "Development of tailorable mechanical design support software." Thesis, Stellenbosch : Stellenbosch University, 2013. http://hdl.handle.net/10019.1/85664.
Повний текст джерела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.
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.
Повний текст джерелаTä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
Hu, Wei 1972. "Managing embedded software development in China." Thesis, Massachusetts Institute of Technology, 2003. http://hdl.handle.net/1721.1/30053.
Повний текст джерела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.
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.
Повний текст джерелаLove, Randall James. "Predictive software design measures." Thesis, This resource online, 1994. http://scholar.lib.vt.edu/theses/available/etd-06112009-063248/.
Повний текст джерела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.
Повний текст джерела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).
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.
Повний текст джерела"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.
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.
Повний текст джерела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.
Rais, Aziz. "Interface-Based Software Development." Doctoral thesis, Vysoká škola ekonomická v Praze, 2017. http://www.nusl.cz/ntk/nusl-264730.
Повний текст джерелаNg, Andrew Eng Jwee. "Switched-current filtering systems : design, synthesis and software development." Thesis, University of Glasgow, 1999. http://theses.gla.ac.uk/5040/.
Повний текст джерела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/.
Повний текст джерелаBarratt, Dean M. "An analysis of system development tools." Virtual Press, 1990. http://liblink.bsu.edu/uhtbin/catkey/722786.
Повний текст джерелаDepartment of Computer Science
Adhyapak, Sriram. "ASDN : Automated Software Design Notebook tool." FIU Digital Commons, 1990. http://digitalcommons.fiu.edu/etd/1087.
Повний текст джерела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.
Повний текст джерелаDemise Observation Capsule
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.
Повний текст джерелаSeth, Deepak. "A platform based approach for embedded systems software development." Thesis, Massachusetts Institute of Technology, 2006. http://hdl.handle.net/1721.1/35092.
Повний текст джерела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.
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.
Повний текст джерелаLee, Jason Chong. "Integrating scenario-based usability engineering and agile software development." Diss., Virginia Tech, 2010. http://hdl.handle.net/10919/26729.
Повний текст джерелаPh. D.
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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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/.
Повний текст джерелаChapman, William James. "The development, design, and theory of educational interactive multimedia software." CSUSB ScholarWorks, 2002. https://scholarworks.lib.csusb.edu/etd-project/2330.
Повний текст джерелаPipkin, Jeffrey A. "Applying design metrics to large-scale telecommunications software." Virtual Press, 1996. http://liblink.bsu.edu/uhtbin/catkey/1036178.
Повний текст джерелаDepartment of Computer Science
Stuurman, Christian Phillip. "The development of software for a faxmoden card." Thesis, Cape Technikon, 1995. http://hdl.handle.net/20.500.11838/1068.
Повний текст джерелаThis 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.
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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
Wilburn, Cathy A. "Using the Design Metrics Analyzer to improve software quality." Virtual Press, 1994. http://liblink.bsu.edu/uhtbin/catkey/902489.
Повний текст джерелаDepartment of Computer Science
Moghim, Mohammad Reza. "Incorporating design patterns into object-oriented development methods." Thesis, University of Salford, 1999. http://usir.salford.ac.uk/26820/.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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
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.
Повний текст джерелаPh. D.
incomplete_metadata
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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерелаGibbon, Cleveland Augustine. "Heuristics for object-oriented design." Thesis, University of Nottingham, 1997. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.388318.
Повний текст джерела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.
Повний текст джерела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.
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.
Повний текст джерела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.
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.
Повний текст джерела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.
Повний текст джерела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.
Повний текст джерела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.
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.
Повний текст джерела