Log in

Relevant bibliographies by topics / Computer software development / Dissertations / Theses

To see the other types of publications on this topic, follow the link: Computer software development.

Dissertations / Theses on the topic 'Computer software development'

Author: Grafiati

Published: 4 June 2021

Last updated: 30 July 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 dissertations / theses for your research on the topic 'Computer software development.'

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

Sherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Antia, Yezdi F. "Personal computer development system software architecture." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/104287.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Ness, Paul Edward. "Creative software development : an empirical modelling framework." Thesis, University of Warwick, 1997. http://wrap.warwick.ac.uk/3059/.

Full text

Abstract:

The commercial success of software development depends on innovation [Nar93a]. However, conventional approaches inhibit the development of innovative products that embody novel concepts. This thesis argues that this limitation of conventional software development is largely due to its use of analytical artefacts, and that other activities, notably Empirical Modelling and product design, avoid the same limitation by using creative artefacts. Analytical artefacts promote the methodical representation of familiar subjects whereas creative artefacts promote the exploratory representation of novel subjects. The subjects, constraints, environments and knowledge associated with a design activity are determined by the nature of its artefacts. The importance of artefacts was discovered by examining the representation of different kinds of lift system in respect of Empirical Modelling, product design and software development. The artefacts were examined by identifying creative properties, as characterized in the theory of creative cognition [FWS92], together with their analytical counterparts. The processes of construction were examined by identifying generative and exploratory actions. It was found that, in software development, the artefacts were analytical and the processes transformational, whereas, in Empirical Modelling and product design, the artefacts were both creative and analytical, and the processes exploratory. A creative approach to software development using both creative and analytical artefacts is proposed for the development of innovative products. This new approach would require a radical departure from the established ideas and principles of software development. The existing paradigm would be replaced by a framework based on Empirical Modelling. Empirical Modelling can be though of as a situated approach to modelling that uses the computer in exploratory ways to construct artefacts. The likelihood of the new paradigm being adopted is assessed by considering how it addresses the topical issues in software development.

APA, Harvard, Vancouver, ISO, and other styles

4

Algan, Fatih Tuğlular Tuğkan. "Test driven software development/." [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Moland, Kathryn J. "An Effective Software Development Methodology for Quality Software Development in a Scheduling Department." NSUWorks, 1997. http://nsuworks.nova.edu/gscis_etd/731.

Full text

Abstract:

The research described in this document represents work performed in the area of software development methodologies as it applied to quality software development in a scheduling department. It addressed traditional methods in software development, current trends in software development, in addition to quality and software development at various companies. The literature suggested a correlation between using a software development methodology and quality software. However, there was limited literature that measured quantitatively the correlation between the effectiveness of the software development methodology and quality software. A software development methodology was developed for the scheduling department of a government contractor company in Aiken, South Carolina based on its needs and emerging technologies. An instrument was utilized to measure the effectiveness of the developed methodology. The methodology was compared with two other methodologies: a standard methodology from the literature and the current method of software development in the scheduling department. A population of computer professionals was divided into three equal groups. Each group was asked to apply the methodology to the case study. Individuals in each group were asked to review the case study and software development methodology. Then using the instrument, the individuals were asked to evaluate the effectiveness of the software development methodology, thereby providing a means for evaluated effectiveness, without conducting years of testing. The responses of the three groups were compared to one another. The results indicated a significantly higher level of approval for those methodologies that guided the development activities, standardized the development process, and identified the development phases and deliverables. It was concluded that utilizing a software development methodology that guides, standardizes, and defines the development phases and deliverables will result in an improved software development process and software quality. Further investigation could validate the findings of this research. The results actually achieved from utilizing the methodology developed for the scheduling department compared with the results achieved from utilizing some other methodology could further validate these research findings. Additional research could examine, over an extended time period, the success of the software development process and software quality of those projects utilizing the methodology described in this dissertation.

APA, Harvard, Vancouver, ISO, and other styles

6

Knapp, Chris H. "Unlocking test-driven development." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CKnapp2006.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.

Full text

Abstract:

Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.

APA, Harvard, Vancouver, ISO, and other styles

8

Norman, Michael John. "SSDE : structured software development environment." Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.

Full text

Abstract:

Bibliography: pages 219-230.
Software engineers have identified many problem areas regarding the development of software. There is a need for improving system and program quality at design level, ensuring that design costs remain within the budget, and increasing the productivity of designers. Structured Software Development Environment (SSDE) provides the system designer with an interactive menu-driven environment, and a framework within which he can conveniently express and manipulate his proposed solution. This representation is in terms of both a conceptual model and a detailed software logic definition. Thus SSDE provides tools for both high-level (or logical) and low-level (or physical) design. It allows a user to follow his own preferred methodology rather than restricting him to one specific strategy. SSDE builds and maintains databases that record all design decisions. It provides the system designer with a mechanism whereby systems can easily be modified and new systems can evolve from similar existing systems. There are several auxiliary facilities as productivity aids. SSDE generates PASCAL code for low-level design constructs, ·full documentation of both the high- and low-level designs for inclusion in the project file, as well as a skeleton manual. The system was evaluated by a number of independent users. This exercise clearly demonstrated its success as an aid in expressing, understanding, manipulating and solving software development problems.

APA, Harvard, Vancouver, ISO, and other styles

9

Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.

Full text

Abstract:

Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.

APA, Harvard, Vancouver, ISO, and other styles

10

Mäkäräinen, Minna. "Software change management processes in the development of embedded software /." Espoo [Finland] : Technical Research Centre of Finland, 2000. http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Abuseta, Yousef M. "AutoTaSC : model driven development for autonomic software engineering." Thesis, Liverpool John Moores University, 2009. http://researchonline.ljmu.ac.uk/5927/.

Full text

Abstract:

Whilst much research progress has been achieved towards the development of autonomic software engineering tools and techniques including: policy-based management, modelbased development, service-oriented architecture and model driven architecture. They have often focused on and started from chosen object-oriented models of required software behaviour, rather than domain model including user intentions and/or software goals. Such an approach is often reported to lead to "misalignment" between business process layer and their associated computational enabling systems. This is specifically noticeable in adaptive and evolving business systems and/or processes settings. To address this long-standing problem research has over the years investigated many avenues to close the gap between business process modelling and the generation of enactment (computation) layer, which is responsive to business changes. Within this problem domain, this research sets out to study the extension of the Model Driven Development (MOD) paradigm to business/domain model, that is, how to raise the abstraction level of model-driven software development to the domain level and provide model synchronisation to trace and analyse the impact of a given model change. The main contribution of this research is the development of a MOD-based design method for autonomic systems referred to as AutoTaSC. The latter consists of a series of related models, where each of which represents the system under development at a given stage. The first and highest level model represents the abstract model referred to as the Platform Independent Model (PIM). The next model encapsulates the PIM model for the autonomic system where the autonomic capabilities and required components (such as monitor, sensor, actuator, analyser, policy, etc.) are added via some appropriate transformation rules. Targeting a specific technology involves adding, also via transformation rules, specific information related to that platform from which the Platform Specific Model (PSM) for the autonomic system is extracted. In the last stage, code can be generated for the specific platform or technology targeted in the previous stage, web services for instance. In addition, the AutoTaSC method provides a situated model synchronisation mechanism, which is designed following the autonomic systems principles. For instance, to guarantee model synchronisation each model from each AutoTaSC stage has an associated policy-based feedback control loop, which regulates its reaction to detected model change. Thus, AutaTase method model transformation approach to drive model query, view and synchronisation. The Auto'Iast? method was evaluated using a number of benchmark case-studies to test this research hypothesis including the effectiveness and generality of AutaTaSe design method.

APA, Harvard, Vancouver, ISO, and other styles

12

Baker, Wilfred G. "A software requirement development model." Master's thesis, This resource online, 1993. http://scholar.lib.vt.edu/theses/available/etd-12162009-020042/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Pullen, Andrew Mark. "Motion development for computer animation." Thesis, University of Cambridge, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.278403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Kortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.

Full text

Abstract:

Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.

APA, Harvard, Vancouver, ISO, and other styles

15

Hellström, Andreas, and Anatoly Chervyakov. "Global Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1687.

Full text

Abstract:

Global Software Development is an area that has been recently highlighted. Translation is usually an issue that people associate with adapting software for a specific country but it is much more than that. Through text representation and data formatting you can go deep into cultural aspects that affect the user interface and even the core functionality. In this thesis we will discuss just how these matters can affect development of global software. To carry out the investigation we analyzed current approaches and references and build up an extended methodology with suggestions to develop global software applications.
Utveckling av globala programvara är ett område som den senaste tiden har uppmärksammats. Översättning är vanligtvis en fråga som människor associerar med att anpassa programvaror för ett specifikt land men det är mycket mer än det. Man kan gå djupare in i kulturella aspekter som kan påverka användargränssnitt och även mjukvarans kärna. I den här uppsatsen diskuterar vi hur dessa aspekter kan påverka utveckling av global programvara. För att genomföra vårt arbete analyserades vi först befintliga metodologier och byggde upp en utökad metodologi med förslag på hur man kan utveckla global programvara.
0737 305407 0708 230374

APA, Harvard, Vancouver, ISO, and other styles

16

Ghali, Nagi. "Managing software development knowledge: A conceptually-oriented software engineering environment (COSEE)." Thesis, University of Ottawa (Canada), 1993. http://hdl.handle.net/10393/6565.

Full text

Abstract:

Software development, especially for large and complex systems, has long been recognized as a difficult and expensive process. Major software development problems (such as insufficient reuse of software, inadequate machine assistance for software developers, uncoordinated tools, excessive time spent during the maintenance phase, and poor documentation) have not yet been properly addressed. Most current software development environments do not provide satisfactory solutions for these problems. In our research, we investigated these problems and we will suggest a solution that will help to eliminate some of them. We built an environment called COSEE (Conceptually-Oriented Software Engineering Environment), on top of a knowledge management system (CODE). In COSEE, we captured three most important types of knowledge needed by software developers/maintainers: domain knowledge, design knowledge, and implementation knowledge. We dynamically linked COSEE to the programming environment (Smalltalk-80) to create a unified knowledge management system for software development. We used the object-oriented approach as our design methodology and Smalltalk-80 as our implementation language. We illustrated our approach using the ATM (Automated Teller Machine) example.

APA, Harvard, Vancouver, ISO, and other styles

17

Traino, Anthony J. "Automation of software development metrics." [Denver, Colo.] : Regis University, 2008. http://165.236.235.140/lib/ATraino2008.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

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 text

Abstract:

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).

APA, Harvard, Vancouver, ISO, and other styles

19

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

APA, Harvard, Vancouver, ISO, and other styles

20

Hart, Charles Fredrick. "Construction software using feature contexts." Diss., Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/8180.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Herrera, Acuna Raul. "Advanced computer vision-based human computer interaction for entertainment and software development." Thesis, Kingston University, 2014. http://eprints.kingston.ac.uk/29884/.

Full text

Abstract:

In this thesis we propose novel methods for 3D interaction on 3D environments. The evaluation of these methods was performed based on three interaction environments: 3D interaction using portable multi-touch devices, 3D hand gesture data manipulation using 3D database representation and 3D multi-threaded programing using hand gesture interaction. The three experiments provided qualitative and quantitative information to evaluate the features of the presented interfaces. The first experiment, based on the use on the use of portable multi-touch devices, aimed to evaluate the use of 3D movements to interact under a 3D environment. Also, the possibility of generate collaborative interaction under 3D interfacing (simulating a 3D multi-touch table top environment) was evaluated. The second experiment consisted on 3D touchless data manipulation, removing the intermediate device (portable multi-touch) and providing hand gesture data interaction using the Kinect device. Furthermore, this evaluation was conducted over a 3D cube database model, based on the concepts of multidimensional databases and graphic databases. The third experiment intended to evaluate the possibility of software generation using a 3D interaction environment, following a similar model of interaction from the second experiment, but providing a better two handed interaction. The environment aimed multi-threaded programing under a 3D interface. The three experiments provided valuable data about users’ interaction and preference, which were tested with users of different ages and levels of knowledge. The research process and results are summarized in this research work.

APA, Harvard, Vancouver, ISO, and other styles

22

Pope, Nicolas William. "Supporting the migration from construal to program : rethinking software development." Thesis, University of Warwick, 2011. http://wrap.warwick.ac.uk/46969/.

Full text

Abstract:

Creative software design, where there is no theory, no pre-computer precedent, no set of requirements or even necessarily an objective, challenges all existing software development methods. There can be no assumption that end-users know what they want. Each and every situation is unique, unpredictable and due to feedback is continually changing. Fixed solutions developed by non-domain experts are all but impossible in more unconventional systems, and increasingly there may not be domain experts at all. Allowing individuals or groups of non-professionals to program is one approach (End-User Development). However, programming requires a degree of formality, design and specification that cannot co-exist with the most informal pre-theoretical applications which need to be developed by exploratory experimentation to help with problem-solving and sense-making. Instead of programming a finished application from the beginning, there is a need to develop personal, provisional and subjective models and evolve these into public, objective and assured applications. Developing these models \on-line" through interactive experimentation is essential and it is the objective of Empirical Modelling (EM) research to enable the modelling of sense-making artefacts called construals. Whilst existing EM tools are able to support construals there is a need to see how a smooth transition from construals to applications can be made. Such a migration is not one-way as the resulting applications need to remain plastic. The aim of this thesis is to explore and develop ways of enhancing EM principles and tools to better support such migrations from construals to programs. By first identifying key characteristics of construals and associated principles and techniques, along with a critique of the existing EM tool, a new kind of environment for plastic software development is proposed. A major contribution of this thesis is the development of such a prototype environment which is illustrated using a collection of artefacts developed within it. From the prototype, called Cadence, an informal and a formal idealised account was elicited to provide a framework for this kind of development activity. The ideas explored in the thesis have the potential to impact upon the operating systems community and the everyday computer user in radical ways if taken forward. The thesis demonstrates that applications can be developed from construals without a translation step, keeping the resulting applications plastic.

APA, Harvard, Vancouver, ISO, and other styles

23

Sun, Pi-Hwa. "Distributed empirical modelling and its application to software system development." Thesis, University of Warwick, 1999. http://wrap.warwick.ac.uk/78784/.

Full text

Abstract:

Empirical Modelling (EM) is a new appro~h for software system development (SSO) that is particularly suitable for ill-defined, open systems. By regarding a software system as a computer model, EM aims to acquire and construct the knowledge associated with the intended system by situated modelling in which the modeller interacts with the computer model through continuous observations and experiments in an open-ended manner. In this way, a software system can be constructed that takes account of its context and is adaptable to the rapidly changing environment in which the system is developed and used. This thesis develops principles and tools for distributed Empirical Modelling (OEM). It proposes a framework for OEM by drawing on two crucial theories in social science: distributed cognition and ethnomethodology. This framework integrates cognitive and social processes, allowing multiple modellers to work collaboratively to explore, expand, experience and communicate their knowledge through interaction with their networked computer models. The concept of pretend play is proposed, whereby modellers as internal observers can interact with each other by acting in the role of agents within the intended system in order to shape the agency of such agents. The author has developed a tool called dtkeden to support the proposed OEM framework. Technical issues arising from the implementation dtkeden and case-studies in its use are discussed. The popular star-type logical configuration network and the client/server· communication technique are exploited to construct the network environment of this tool. A protocol has been devised and embedded into their communication mechanism to achieve synchronisation of computer models. Four interaction modes have been implemented into dtkeden to provide modellers with different forms of interpersonal interaction. In addition, using a virtual agent concept that was initially devised to allow definitions of different contexts to co-exist in a computer model, a definitive script can be interpreted as a generic observable that can serve as a reusable definitive pattern. Like experience in everyday life, this definitive pattern can be reused by particularising and adapting it to a specific context. A comparison between generic observables and abstract data types for reuse is given. The application of the framework for OEM to requirements engineering is proposed. The requirements engineering process (REP) - currently poorly understood - is reviewed. To integrate requirements engineering with SSD, this thesis suggests reengineering the REP by taking the context into account. On the basis of OEM, a framework (called SPORE) for the REP is established to guide the process of cultivating requirements in a situated manner. Examples of the use of this framework are presented, and comparisons with other approaches to RE are made.

APA, Harvard, Vancouver, ISO, and other styles

24

Lawrie, Peter Richard. "Development of computer software support for interpretive structural modelling." Master's thesis, University of Cape Town, 1995. http://hdl.handle.net/11427/15980.

Full text

Abstract:

Includes bibliographical references.
Interpretive Structural Modelling is a computer-driven method for dealing with complexity, by allowing individuals or groups to interpret the inter-relationships between different aspects or elements of a problem. In doing this interpretation, the elements are structured, and from this structuring, a graphical model is produced, allowing the modeller(s) to better understand the problem. The main contribution of this thesis was to develop a computer package for Interpretive Structural Modelling (ISM), for use at the School of Engineering Management at the University of Cape Town. The package was developed for the IBM PC.

APA, Harvard, Vancouver, ISO, and other styles

25

Fischer, Scott Edward. "Standard form 254 generation software." Thesis, Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/22386.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Crunk, John. "Examining Tuckman's Team Theory in Non-collocated Software Development Teams Utilizing Collocated Software Development Methodologies." Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10929105.

Full text

Abstract:

The purpose of this qualitative, multi-case study was to explain Tuckman’s attributes within software development when using a collocated software designed methodology in a non-collocated setting. Agile is a software development methodology that is intended for use in a collocated setting; however, organizations are using it in a non-collocated setting, which is increasing the software errors in the final software product. The New Agile Process for Distributed Projects (NAPDiP) was developed to fix these software errors that arise when using Agile in a non-collocated setting but have not been effective. This research utilized Tuckman's team theory to explore the disparity related to why these errors still occur. The research question asked is how software development programmers explain Tuckman's attributes (i.e., forming, storming, norming, performing) on software development projects. The study adopted a qualitative model using nomothetic major and minor themes in the exploration of shared expressions of sentiments from participants. The study’s population came from seven participants located in the United States and India who met the requirement of using the Agile development methodology and work for organizations on teams with a size of at least thirty individuals from various organizations. A total of seven participants reached saturation in this multi-case study supporting the research question explored. The findings of the research demonstrated that development teams do not meet all stages and attributes of Tuckman’s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman’s team development stages.

APA, Harvard, Vancouver, ISO, and other styles

27

Cornut, Francis. "The discursive constitution of software development." Thesis, London School of Economics and Political Science (University of London), 2009. http://etheses.lse.ac.uk/258/.

Full text

Abstract:

The successful development of software continues to be of central interest, both as an academic topic and in professional practice. Consequently, several software development approaches and methodologies have been developed and promoted over the past decades. However, despite the attention given to the subject and the methodical support available, software development and how it should be practiced continue to be controversial. This thesis examines how beliefs about software development come to be socially established as legitimate, and how they come to constitute software development practices in an organization. It is argued that the emergence of a dominant way of conceiving of and practicing software development is the outcome of power relations that permeate the discursive practices of organizational actors. The theoretical framework of this study is guided by Pierre Bourdieu’s theory of symbolic violence and organizational discourse theory. As a research method, ethnographic research techniques are utilized as part of a case study to gain deep insights into the standardization of software development practices. The research site is the IT division of a large financial services organization and is composed of ten units distributed across eight countries. The tumultuous development of a knowledge management programme intended to institutionalize a standard software development process across the organization’s units provides the case for this research. This thesis answers the call for studies providing detailed accounts of the sociopolitical process by which technically oriented practices are transferred and standardized within organizations. It is submitted that a discourse theoretical approach informed by Bourdieu’s thinking enables us to conceptualize this process in a more meaningful, and theoretically rigorous, manner. In providing this theoretical approach, the thesis seeks to contribute to current research on technology and innovation management, and to offer guidance on some issues concerning the management of the software development process.

APA, Harvard, Vancouver, ISO, and other styles

28

Martin, Timothy Patrick. "Flexible manufacturing system software development using simulation." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/101236.

Full text

Abstract:

This paper presents a hierarchical modeling method that can be used to simulate a Flexible Manufacturing System (FMS) at all levels of detail. The method was developed specifically to aid the software development needed for the hierarchy of computers that are present in an FMS. The method was developed by modeling an existing FMS. The models developed of the existing FMS are described in detail to provide an example of how to model other FMSs. The basic building blocks needed for designing other FMSs with this modeling method are provided. The models were written in the SIMAN simulation language. SIMAN was found to be an easy language to use for the hierarchical modeling of FMSs.
M.S.

APA, Harvard, Vancouver, ISO, and other styles

29

Ziegenhagen, Lynzi. "Evaluating configuration management tools for high assurance software development projects." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Jun%5FXiegenhagen.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Chipunza, Enciliah. "Quality management challenges in iterative software product development of a selected software development organisation in Cape Town, South Africa." Thesis, Cape Peninsula University of Technology, 2018. http://hdl.handle.net/20.500.11838/2779.

Full text

Abstract:

Thesis (MTech (Business Information Systems))--Cape Peninsula University of Technology, 2018.
Many software organisations using iterative software development approach use practices that relate to quality management. However, the quality management process has been inadequate. Despite many research studies conducted on quality management in iterative software product development none have adequately addressed the challenges and mitigation techniques to have an adequate process that leads to a quality software product. The objective of this study was to determine factors that affect the quality management process in iterative software development. The research followed a qualitative approach, a case of software organisation SasTech in Cape Town, South Africa. 22 interviews were conducted on three roles actively involved in the software product development process. These are product management, quality assurance and software developers. Themes were drawn from results and were tabulated. The duality of technology theory was used as a theoretical lens to data analysis. Several factors were identified to influence the software quality management process. These include planning, documentation, process ownership, technologies, testing, timelines and management support. Through the general proposed framework, facilities (human resources and technologies), interpretive schemes (architecture) and norms (practices) of software quality management can be institutionalised leading to adequate and effective quality management in iterative development for SasTech as well as other organisations in the same industry.

APA, Harvard, Vancouver, ISO, and other styles

31

Xiong, Jie 1974. "Addressing concurrency using UML-based software development." Thesis, McGill University, 2004. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=81457.

Full text

Abstract:

Distributed systems, systems that interact with real-time devices, responsive GUI interfaces, systems that interact with hundreds of clients simultaneously have to function correctly even in a concurrent environment. Complex concurrent activities and interactions however make the development, i.e. understanding, analyzing, designing and implementing, of such systems extremely difficult. It is important to have a systematic approach to treat the many issues when developing concurrent systems.
In this thesis, we describe an approach that addresses concurrency in all phases of object-oriented software development. We show how to identify inherent concurrency at early stages of the development, and we propose a way to systematically refine the resulting declarative specification into an object-oriented design, which controls concurrency and provides data consistency using transactions or monitors.

APA, Harvard, Vancouver, ISO, and other styles

32

Moran, Kevin Patrick. "Automating Software Development for Mobile Computing Platforms." W&M ScholarWorks, 2018. https://scholarworks.wm.edu/etd/1550153845.

Full text

Abstract:

Mobile devices such as smartphones and tablets have become ubiquitous in today's computing landscape. These devices have ushered in entirely new populations of users, and mobile operating systems are now outpacing more traditional "desktop" systems in terms of market share. The applications that run on these mobile devices (often referred to as "apps") have become a primary means of computing for millions of users and, as such, have garnered immense developer interest. These apps allow for unique, personal software experiences through touch-based UIs and a complex assortment of sensors. However, designing and implementing high quality mobile apps can be a difficult process. This is primarily due to challenges unique to mobile development including change-prone APIs and platform fragmentation, just to name a few. in this dissertation we develop techniques that aid developers in overcoming these challenges by automating and improving current software design and testing practices for mobile apps. More specifically, we first introduce a technique, called Gvt, that improves the quality of graphical user interfaces (GUIs) for mobile apps by automatically detecting instances where a GUI was not implemented to its intended specifications. Gvt does this by constructing hierarchal models of mobile GUIs from metadata associated with both graphical mock-ups (i.e., created by designers using photo-editing software) and running instances of the GUI from the corresponding implementation. Second, we develop an approach that completely automates prototyping of GUIs for mobile apps. This approach, called ReDraw, is able to transform an image of a mobile app GUI into runnable code by detecting discrete GUI-components using computer vision techniques, classifying these components into proper functional categories (e.g., button, dropdown menu) using a Convolutional Neural Network (CNN), and assembling these components into realistic code. Finally, we design a novel approach for automated testing of mobile apps, called CrashScope, that explores a given android app using systematic input generation with the intrinsic goal of triggering crashes. The GUI-based input generation engine is driven by a combination of static and dynamic analyses that create a model of an app's GUI and targets common, empirically derived root causes of crashes in android apps. We illustrate that the techniques presented in this dissertation represent significant advancements in mobile development processes through a series of empirical investigations, user studies, and industrial case studies that demonstrate the effectiveness of these approaches and the benefit they provide developers.

APA, Harvard, Vancouver, ISO, and other styles

33

Johansson, Oscar, and Max Forsman. "Shared computer systems and groupware development : Escaping the personal computer paradigm." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-75953.

Full text

Abstract:

For the majority of the computers existence, we humans have interacted with them in a similar way, usually with a strict one-to-one relationship between user and machine. This is reflected by the design of most computers, operating systems and user applications on the market today, which are typically intended to only be operated by a single user. When computers are used for teamwork and cooperation, this design philosophy can be restricting and problematic. This paper investigates the development of shared software intended for multiple users and the impact of the single user bias in this context. A prototype software system was developed in order to evaluate different development methods for shared applications and discover potential challenges and limitations with this kind of software. It was found that the development of applications for multiple users can be severely limited by the target operating system and hardware platform. The authors conclude that new platforms are required to develop shared software more efficiently. These platforms should be tailored to provide robust support for multiple concurrent users. This work was carried out together with SAAB Air Traffic Management in Växjö, Sweden and is a bachelor's thesis in computer engineering at Linnaeus University.

APA, Harvard, Vancouver, ISO, and other styles

34

Archer, Emory Scott. "Development of graphical software tools for molecular biology." Thesis, Hong Kong : University of Hong Kong, 1997. http://sunzi.lib.hku.hk/hkuto/record.jsp?B19974218.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Salvatore, Ricardo Brigatto. "Using open source software in visual simulation development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Sep%5FSalvatore.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Moo, Jason. "Applying human-computer interaction methodologies to the development of computer-aided design software." Thesis, This resource online, 1995. http://scholar.lib.vt.edu/theses/available/etd-03042009-040630/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Teo, Ching Leong. "Bistatic radar system analysis and software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Dec%5FTeo%5FChing.pdf.

Full text

Abstract:

Thesis (M.S. in Engineering Science)--Naval Postgraduate School, December 2003.
Thesis advisor(s): David C. Jenn, D. Curtis Schleher. Includes bibliographical references (p. 95-96). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

38

Lindmark, Fanny, and Hanna Kvist. "Security in software : How software companies work with security during a software development process." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.

Full text

Abstract:

This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.

APA, Harvard, Vancouver, ISO, and other styles

39

Justin, Ken. "Development of electrocardiographic image processing software." Thesis, Massachusetts Institute of Technology, 1993. http://hdl.handle.net/1721.1/72288.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Allen, Gary. "Software development methods for educational use." Thesis, University of Huddersfield, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.385922.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Myburgh, W. D. "Development of a tool to test computer protocols." Thesis, Stellenbosch : Stellenbosch University, 2003. http://hdl.handle.net/10019.1/53363.

Full text

Abstract:

Thesis (MSc) -- Stellenbosch University, 2003.
ENGLISH ABSTRACT: Software testing tools simplify and automate the menial work associated with testing. Moreover, for complex concurrent software such as computer protocols, testing tools allow testing on an abstract level that is independent of specific implementations. Standard conformance testing methodologies and a number of testing tools are commercially available, but detailed descriptions of the implementation of such testing tools are not widely available. This thesis investigates the development of a tool for automated protocol testing in the ETH Oberon development environment. The need to develop a protocol testing tool that automates the execution of specified test cases was identified in collaboration with a local company that develops protocols in the programming language Oberon. Oberon is a strongly typed secure language that supports modularisation and promotes a readable programming style. The required tool should translate specified test cases into executable test code supported by a runtime environment. A test case consists of a sequence of input actions to which the software under test is expected to respond by executing observable output actions. A number of issues are considered of which the first is concerned with the representation of test case specifications. For this, a notation was used that is basically a subset of the test specification language TTCN-3 as standardised by the European Telecommunications Standards Institute. The second issue is the format of executable test cases and a suitable runtime environment. A translator was developed that generates executable Oberon code from specified test cases. The compiled test code is supported by a runtime library, which is part of the tool. Due to the concurrent nature of a protocol environment, concurrent processes in the runtime environment are identified. Since ETH Oberon supports multitasking in a limited sense, test cases are executed as cooperating background tasks. The third issue is concerned with the interaction between an executing test case and a system under test. It is addressed by an implementation dependent interface that maps specified test interactions onto real interactions as required by the test context in which an implementation under test operates. A supporting protocol to access the service boundary of an implementation under test remotely and underlying protocol service providers are part of a test context. The ETH Oberon system provides a platform that simplifies the implementation of protocol test systems, due to its size and simple task mechanism. Operating system functionality considered as essential is pointed out in general terms since other systems could be used to support such testing tools. In conclusion, directions for future work are proposed.
AFRIKAANSE OPSOMMING: Toetsstelsels vir programmatuur vereenvoudig en outomatiseer die slaafse werk wat met toetsing assosieer word. 'n Toetsstelsel laat verder toe dat komplekse gelyklopende programmatuur, soos rekenaarprotokolle, op 'n abstrakte vlak getoets word, wat onafhanklik van spesifieke implementasies is. Daar bestaan standaard metodes vir konformeringstoetsing en 'n aantal toetsstelsels is kommersiëel beskikbaar. Uitvoerige beskrywings van die implementering van sulke stelsels is egter nie algemeen beskikbaar nie. Hierdie tesis ondersoek die ontwikkeling van 'n stelsel vir outomatiese toetsing van protokolle in die ontwikkelingsomgewing van ETH Oberon. Die behoefte om 'n protokoltoetsstelsel te ontwikkel, wat die uitvoering van gespesifiseerde toetsgevalle outomatiseer, is geïdentifiseer in oorleg met 'n plaaslike maatskappy wat protokolle ontwikkel in die Oberon programmeertaal. Oberon is 'n sterkgetipeerde taal wat modularisering ondersteun en a leesbare programmeerstyl bevorder. Die toestsstelsel moet gespesifiseerde toetsgevalle vertaal na uitvoerbare toetskode wat ondersteun word deur 'n looptydomgewing. 'n Toetsgeval bestaan uit 'n reeks van toevoeraksies waarop verwag word dat die programmatuur wat getoets word, sal reageer deur die uitvoering van afvoeraksies wat waargeneem kan word. 'n Aantal kwessies word aangeraak, waarvan die eerste te make het met die voorstelling van die spesifikasie van toetsgevalle. Hiervoor is 'n notasie gebruik wat in wese 'n subversameling van die toetsspesifikasietaal TTCN-3 is. TTCN-3 is gestandardiseer deur die European Telecommunications Standards Institute. Die tweede kwessie is die formaat van uitvoerbare toetsgevalle en 'n geskikte looptydomgewing. 'n Vertaler is ontwikkel wat uitvoerbare Oberon-kode genereer vanaf gespesifiseerde toetsgevalle. Die vertaalde toetskode word ondersteun deur 'n biblioteek van looptydfunksies, wat deel van die stelsel is. As gevolg van die eienskap dat 'n protokolomgewing uit gelyklopende prosesse bestaan, word daar verskillende tipes van gelyklopende prosesse in 'n protokoltoetsstelsel geïdentifiseer. Aangesien ETH Oberon 'n beperkte multitaakstelsel is, word toetsgevalle vertaal na eindige outomate wat uitgevoer word as samewerkende agtergrondtake. Die derde kwessie het te make met die interaksie tussen 'n toetsgeval wat uitgevoer word en die stelsel wat getoets word. Dit word aangespreek deur 'n koppelvlak wat gespesifiseerde interaksies afbeeld op werklike interaksies soos vereis deur die konteks waarin 'n implementasie onderworpe aan toetsing uitvoer. 'n Ondersteunende protokolom die dienskoppelvlak van die implementasie oor 'n afstand te bereik en ander onderliggende protokoldienste is deel van 'n toetskonteks. Die ETH Oberon-stelsel help in die vereenvoudiging van die implementasie van protokol toetsstelsels, as gevolg van die stelsel se grootte en die eenvoudige taakhanteerder . Die essensiële funksionaliteit van bedryfsstelsels word uitgelig in algemene terme omdat ander stelsels gebruik kan word om toetsstelsels te ondersteun. Ten slotte word voorstelle vir opvolgwerk gemaak.

APA, Harvard, Vancouver, ISO, and other styles

42

Demir, Kadir Alpaslan. "Analysis of TLcharts for weapon systems software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Dec%5FDemir.pdf.

Full text

Abstract:

Thesis (M.S. in Computer Science and M.S. in Software Engineering)--Naval Postgraduate School, December 2005.
Thesis Advisor(s): Doron Drusinsky, Man-Tak Shing. Includes bibliographical references (p. 87-89). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

43

Srirangarajan, Ananth Lall Pradeep Umphress David A. "The scrum process for independent programmers." Auburn, Ala, 2009. http://hdl.handle.net/10415/1617.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

King, Barbara M. "A Software Development Life-Cycle Model for Web-Based Application Development." NSUWorks, 2004. http://nsuworks.nova.edu/gscis_etd/636.

Full text

Abstract:

Software development life cycle models were believed to play a critical role in improving software quality by guiding tasks in the software development processes since being formally introduced and embraced in the 1970s. Many organizations attempted to deploy software development life cycle methodologies with the intent to improve the software development process from conception through implementation to delivery. Numerous established software development models exist, including the classic waterfall life cycle model, Spiral model, Prototyping, Evolutionary, (e.g., Staged, Phased, and Timebox models), object-oriented design (OOD) (e.g., Rational Unified Process), and agile processes (e.g., eXtreme Programming [XP]). The design and development of web-based applications introduced new problems and requirements that did not exist when traditional software development life-cycle models were being put into practice. This research presents empirical software development practice data pertaining to web-based application development. The goal of this project was to answer the question, "What is the general paradigm of an SDLC model for web-based application development?" The focus of the project was to derive an empirical SDLC model for web-based application development. Data from current practices was collected via a web-based application. Study participants used the web-based application to input data concerning the SDLC model of their web-based application development process. The empirical model was derived from the data provided by participants on current professional web-based application development practices. The results of this research showed that although web-based application development life-cycle does parallel traditional SDLCs in some phases, there were enough differences that an exact fit to an existing model does not exist. A modified version of the Classic Waterfall with some repetitiveness of the Spiral model with the addition of optional phases best met the situational requirements of web-based application development.

APA, Harvard, Vancouver, ISO, and other styles

45

Datar, Ranjani Milind. "Metrics for software reuse." Virtual Press, 1995. http://liblink.bsu.edu/uhtbin/catkey/958791.

Full text

Abstract:

A major reengineering goal is software reuse. Effective reuse of knowledge, processes and products from previous software developments can reduce costs and increase both productivity and quality in software projects.This thesis extensively tests five projects produced by the graduate software engineering class at Ball State University. Each project has the same set of requirements.Each project is also analyzed based on subjective criteria, for example documentation, use of mnemonics for variable names and ease of understanding. Based on the outcome of testing and subjective analysis, reusable parts are identified.Metrics are collected on all of these projects. This thesis compares the metrics collected on the modules identified for reuse, and the same metrics collected on the non-reusable modules, to determine if there is a statistically significant difference in those metrics between the two groups. Metrics which are good predictors of reusable modules are identified.Metrics which are found to be good predictors of reusable modules include: number of in-parameters, number of data structure manipulations and central calls.
Department of Computer Science

APA, Harvard, Vancouver, ISO, and other styles

46

Moyer, Daniel Raymond. "Software development resource estimation in the 4th generation environment." Thesis, Kansas State University, 1986. http://hdl.handle.net/2097/9956.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Flaten, Kayla. "The Progression of Agile Software Development." Scholarship @ Claremont, 2017. http://scholarship.claremont.edu/cmc_theses/1717.

Full text

Abstract:

This paper examines the use of Agile Software Development in the technology industry and how it came to be one of the leading models used in project management. By investigating the software development methods used in the late 1900s, it becomes clear where the system needed improvement in order to improve the efficiency in developing products. In investigating the Agile Manifesto, new and essential components are introduced that become vital in successfully producing a product. From this, it is easier to understand why Agile is so commonly used in the software development industry and how it became so effective.

APA, Harvard, Vancouver, ISO, and other styles

48

Minani, David Muhangwa. "Software developer competency framework." Thesis, Cape Peninsula University of Technology, 2013. http://hdl.handle.net/20.500.11838/1360.

Full text

Abstract:

Thesis submitted in fulfilment of the requirements for the degree Master of Technology: Information Technology in the Faculty of Informatics and Design at the Cape Peninsula University of Technology 2013
The application of software systems in business organizations continue to increase as the Internet technology grows. Business processes that previously required manual interventions are becoming automated using software systems. The use of software systems is fundamental to electronic processing of business transactions. More business organizations, large and small, are utilizing information technology in order to have competitive advantage in the business arena. Software is ubiquitous. Among areas where software plays core roles are e-Banking where software systems are used to process banking transactions, e-Health where software systems are used to facilitate activities in the health sector, e-Commerce where software systems are used to facilitate online business transactions, e-Government where software system are used to facilitate government activities and e-Learning where software systems are used to facilitate the teaching and learning process. Nevertheless, the large number of failing software projects and the increase in software security problems coupled with shortage of skilled software developers are still major obstacles in the software development industry. Among others, the solution can be achieved by improving the competency of software developers so that software systems developed are of good quality, safe, robust, and support business objectives. Software companies and business organizations stand a big chance to increase their return on investment (ROI), if competencies of software developers are improved. A software developer plays critical roles in software development projects. A software developer, however, requires specific skills and knowledge in order to develop software systems that solve problems and deliver solutions. This research is about competencies of software developers. The research focuses on software development activities performed by software companies and business organizations within the Western Cape Province. The unit of analysis is software developers. Data pertaining to tasks performed by software developers, tools used by software developers and skills required were collected, examined and analysed. The objective of the research is to develop a competency framework for software developers. It can be used by institutions and the industry to provide better education. Most importantly, the industry will have access to competent software developers who can perform their job well. As justified in this research, knowledge of a competency framework for software developers is extremely essential.ÿ

APA, Harvard, Vancouver, ISO, and other styles

49

Nascimento, Maria Elenita Menezes. "SMM (Software Management Model) : a multidimensional and integrative software development management model." Thesis, University of Manchester, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.386037.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Littlefair, Tim. "An investigation into the use of software code metrics in the industrial software development environment." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 2001. https://ro.ecu.edu.au/theses/1508.

Full text

Abstract:

This work describes a project that investigates the use of software metrics based on measurement of source code in industrial software development. Literature is examined relating to considerations of quality in industry; to software engineering; to emergent technologies in the software industry including the object-oriented paradigm and software patterns; to software product and process metrics; and to cultural factors affecting workplaces in the software industry. It then expounds theoretical and practical work aimed at specifying, designing and implementing a source code analyzer for use in a typical industrial project setting. There is an explanation of the design and outcomes of a questionnaire survey, conducted over the Internet, of developers with an interest in using metrics techniques to analyse source code. Finally, there is a description of a controlled experiment which attempts to detect a benefit from use of source code metrics as information to support a simple software engineering task.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!