Добірка наукової літератури з теми "Software development/design"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "Software development/design".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Статті в журналах з теми "Software development/design"
Comer, James R., Herb C. Conn, and Kurt A. Schember. "Software design and development." ACM SIGCSE Bulletin 17, no. 1 (March 1985): 335–41. http://dx.doi.org/10.1145/323275.323403.
Повний текст джерелаYoshikawa, Hidekazu, and Takashi Nakagawa. "ICONE23-1312 SOFTWARE SYSTEM DEVELOPMENT OF NPP PLANT DID RISK MONITOR : BASIC DESIGN OF SOFTWARE CONFIGURATION." Proceedings of the International Conference on Nuclear Engineering (ICONE) 2015.23 (2015): _ICONE23–1—_ICONE23–1. http://dx.doi.org/10.1299/jsmeicone.2015.23._icone23-1_147.
Повний текст джерелаShirazi, Abolfazl, and Mehran Mirshams. "Software Development for Satellite Thermal Design." Applied Mechanics and Materials 390 (August 2013): 703–7. http://dx.doi.org/10.4028/www.scientific.net/amm.390.703.
Повний текст джерелаKearsley, Greg. "Microcomputer Software: Design and Development Principles." Journal of Educational Computing Research 1, no. 2 (May 1985): 209–20. http://dx.doi.org/10.2190/gvb4-72kl-aj34-8trp.
Повний текст джерелаLin, C. Y., and R. R. Levary. "Computer-aided software development process design." IEEE Transactions on Software Engineering 15, no. 9 (1989): 1025–37. http://dx.doi.org/10.1109/32.31362.
Повний текст джерелаSmith, Douglas R. "Design ware: Software Development by Refinement." Electronic Notes in Theoretical Computer Science 29 (1999): 275–87. http://dx.doi.org/10.1016/s1571-0661(05)80320-2.
Повний текст джерелаCui, Xin. "Structure design of knowledge base of software enterprise based on project development." Functional materials 24, no. 2 (June 22, 2017): 005–284. http://dx.doi.org/10.15407/fm24.02.278.
Повний текст джерелаSievi-Korte, Outi, Ita Richardson, and Sarah Beecham. "Software architecture design in global software development: An empirical study." Journal of Systems and Software 158 (December 2019): 110400. http://dx.doi.org/10.1016/j.jss.2019.110400.
Повний текст джерелаKim, Sungchul, and Bongchoon Jang. "Development of Bellows Design Software using MATLAB." Indian Journal of Science and Technology 8, S8 (April 1, 2015): 201. http://dx.doi.org/10.17485/ijst/2015/v8is8/70619.
Повний текст джерелаSu, Qiao Mei, Jian Min Wang, and Jiao Jiao Guo. "Earthwork Actuarial Software System Design and Development." Advanced Materials Research 267 (June 2011): 578–83. http://dx.doi.org/10.4028/www.scientific.net/amr.267.578.
Повний текст джерелаДисертації з теми "Software development/design"
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.
Книги з теми "Software development/design"
Software design. 2nd ed. Harlow, England: Addison-Wesley, 2003.
Знайти повний текст джерелаBudgen, D. Software design. Wokingham, England: Addison-Wesley Pub. Co., 1994.
Знайти повний текст джерелаAyer, Steve J. Software development design documentation. Sunnyvale, CA: Technical Communications Associates, 1986.
Знайти повний текст джерелаCharles, Thies, ed. Secure software design. Burlington, Mass: Jones & Bartlett Learning, 2013.
Знайти повний текст джерелаDooley, John F. Software Development, Design and Coding. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1.
Повний текст джерелаTerry, Winograd, ed. Bringing design to software. New York, N.Y: ACM Press, 1996.
Знайти повний текст джерелаTog on software design. Reading, Mass: Addison-Wesley Pub. Co., 1996.
Знайти повний текст джерелаM, Jonkers H. B., and Middelburg Cornelis A, eds. Notations for software design. London: Springer-Verlag, 1994.
Знайти повний текст джерелаMunson, John C. Software Specification and Design. London: Taylor and Francis, 2005.
Знайти повний текст джерела1953-, Ammar Hany Hussein, ed. Pattern oriented analysis and design: Composing patterns to design software systems. Boston, MA: Addison-Wesley, 2004.
Знайти повний текст джерелаЧастини книг з теми "Software development/design"
Budgen, David. "Incremental Design in Agile Software Development." In Software Design, 237–60. Third edition. | Boca Raton : CRC Press, 2021. | Series: Chapman & Hall/CRC innovations in software engineering: Chapman and Hall/CRC, 2020. http://dx.doi.org/10.1201/b21883-18.
Повний текст джерелаLunn, Ken. "Design." In Software Development with UML, 225–62. London: Macmillan Education UK, 2003. http://dx.doi.org/10.1007/978-0-230-80419-7_13.
Повний текст джерелаLunn, Ken. "Database Design." In Software Development with UML, 263–82. London: Macmillan Education UK, 2003. http://dx.doi.org/10.1007/978-0-230-80419-7_14.
Повний текст джерелаWendorff, Peter. "Process Design." In Politics in Software Development, 39–52. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-7380-7_5.
Повний текст джерелаO’Regan, Gerard. "Software Design and Development." In Undergraduate Topics in Computer Science, 61–74. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-57750-0_4.
Повний текст джерелаO’Regan, Gerard. "Software Design and Development." In Undergraduate Topics in Computer Science, 101–15. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-07816-3_6.
Повний текст джерелаDooley, John F. "Software Architecture." In Software Development, Design and Coding, 53–63. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1_5.
Повний текст джерелаBeningo, Jacob. "Testing, Verification, and Test-Driven Development." In Embedded Software Design, 197–218. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8279-3_8.
Повний текст джерелаO’Regan, Gerard. "Requirements, Design and Development." In Introduction to Software Quality, 77–88. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-06106-1_4.
Повний текст джерелаÜnsalan, Cem, Hüseyin Deniz Gürhan, and Mehmet Erkin Yücel. "Software Development Platforms." In Embedded System Design with ARM Cortex-M Microcontrollers, 27–52. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-88439-0_3.
Повний текст джерелаТези доповідей конференцій з теми "Software development/design"
Comer, James R., Herb C. Conn, and Kurt A. Schember. "Software design and development." In the sixteenth SIGCSE technical symposium. New York, New York, USA: ACM Press, 1985. http://dx.doi.org/10.1145/323287.323403.
Повний текст джерелаMu, Huaxin, and Shuai Jiang. "Design patterns in software development." In 2011 IEEE 2nd International Conference on Software Engineering and Service Science (ICSESS). IEEE, 2011. http://dx.doi.org/10.1109/icsess.2011.5982228.
Повний текст джерелаZyubin, Vladimir. "Software Psychology of Control Software Design and Development." In 2021 International Symposium on Knowledge, Ontology, and Theory (KNOTH). IEEE, 2021. http://dx.doi.org/10.1109/knoth54462.2021.9685023.
Повний текст джерелаSandberg, L. "Electronic and software design reliability." In IET Professional Development Course on Electric Traction Systems. IEE, 2008. http://dx.doi.org/10.1049/ic:20080513.
Повний текст джерелаSullivan, Kevin J. "Software design." In Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96). New York, New York, USA: ACM Press, 1996. http://dx.doi.org/10.1145/243327.243338.
Повний текст джерелаSandberg, L. "Electronic and software design reliability." In 9th IET Professional Development Course on Electric Traction Systems. IEE, 2006. http://dx.doi.org/10.1049/ic:20060209.
Повний текст джерелаCurta, Razvan Traian, and Mihai Steopan. "New feature based design software development." In 2012 IEEE International Conference on Automation, Quality and Testing, Robotics (AQTR 2012). IEEE, 2012. http://dx.doi.org/10.1109/aqtr.2012.6237780.
Повний текст джерелаLumpkin, Everett, and Michael Gabrick. "Hardware/Software Design and Development Process." In SAE 2006 World Congress & Exhibition. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2006. http://dx.doi.org/10.4271/2006-01-0170.
Повний текст джерелаLöwgren, Jonas. "Applying design methodology to software development." In the conference. New York, New York, USA: ACM Press, 1995. http://dx.doi.org/10.1145/225434.225444.
Повний текст джерелаZeng, Fuping, and Shunkun Yang. "Design Criteria Development for Software Reliability." In 2012 Second International Conference on Intelligent System Design and Engineering Application (ISDEA). IEEE, 2012. http://dx.doi.org/10.1109/isdea.2012.528.
Повний текст джерелаЗвіти організацій з теми "Software development/design"
Hakel, Peter. Design-by-contract and test-driven software development. Office of Scientific and Technical Information (OSTI), July 2019. http://dx.doi.org/10.2172/1545734.
Повний текст джерелаOkawa, Soshi, Haruo Ishikawa, and Yoon-Eui Nahm. Development of Computer Software Tool for Set-Based Design. Warrendale, PA: SAE International, May 2005. http://dx.doi.org/10.4271/2005-08-0123.
Повний текст джерелаMöllenkamp, Andreas. Paradigms of Music Software Development. Staatliches Institut für Musikforschung, December 2014. http://dx.doi.org/10.25366/2022.99.
Повний текст джерелаMyatt, R. L., and P. G. Marston. DC CICC retrofit magnet preliminary design, software development and analysis report. Office of Scientific and Technical Information (OSTI), May 1992. http://dx.doi.org/10.2172/5236309.
Повний текст джерелаMyatt, R. L., and P. G. Marston. DC CICC retrofit magnet preliminary design, software development and analysis report. Office of Scientific and Technical Information (OSTI), February 1992. http://dx.doi.org/10.2172/5708011.
Повний текст джерелаSchultz, J. H., P. G. Marston, J. R. Hale, and A. M. Dawson. DC CICC retrofit magnet preliminary design, protection analysis and software development. Office of Scientific and Technical Information (OSTI), November 1991. http://dx.doi.org/10.2172/5808920.
Повний текст джерелаDechev, Damian. Effective software design and development for the new graph architecture HPC machines. Office of Scientific and Technical Information (OSTI), March 2012. http://dx.doi.org/10.2172/1039407.
Повний текст джерелаHolcomb, Greg D. Design and Software Development of Automated Data Acquisition System for Load Cell Calibration. Fort Belvoir, VA: Defense Technical Information Center, July 1998. http://dx.doi.org/10.21236/ada370991.
Повний текст джерелаMarston, P. G. DC CICC retrofit magnet preliminary design, protection analysis, and software development. Final report. Office of Scientific and Technical Information (OSTI), April 1994. http://dx.doi.org/10.2172/10175503.
Повний текст джерелаSyrovatskyi, Oleksandr V., Serhiy O. Semerikov, Yevhenii O. Modlo, Yuliia V. Yechkalo, and Snizhana O. Zelinska. Augmented reality software design for educational purposes. [б. в.], December 2018. http://dx.doi.org/10.31812/123456789/2895.
Повний текст джерела