To see the other types of publications on this topic, follow the link: Software project.
Dissertations / Theses on the topic 'Software project'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Software project.'
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
Kanik, Yusuf. "Software Project Scheduling, Software Project Performance Measurement And Control." Master's thesis, METU, 2005. http://etd.lib.metu.edu.tr/upload/12606362/index.pdf.
Full textAbstract:
This thesis is about software project scheduling and use of earned value method on software projects.
As a result of the study, a solution for software project scheduling problems is proposed. A mathematical formulation, developed using integer programming method, is at the heart of the solution. Objective of the formulation is to minimize the development costs consisting of direct labor cost, indirect costs and probable penalty costs. The formulation takes the capability and compatibility variances among resources into account whereas contemporary approaches mostly focus on resource availability. Formulation is of type discrete time and takes the time span to be searched as input. Therefore a heuristic approach has been developed for providing time span input to the models developed using the formulation. The heuristic approach has been proven to be calculating a time span that does not hinder achieving the absolute optimum schedule and shortens the solution time of the integer programs. The heuristic approach and problem formulation have been incorporated into a computer program that generates integer programs and heuristic solutions.
This thesis also describes a method for preparing an earned value plan, based on the scheduling solution defined. The method aims to help project managers in determining the status of their projects and deciding whether any corrective action is required or not. Besides the method, approaches for incorporating indirect costs and penalty costs, which are not explicitly discussed in literature, into final cost estimation have been described.
2
Farlik, John T. "Project success in agile development software projects." Thesis, Capella University, 2016. http://pqdtopen.proquest.com/#viewpdf?dispub=10108921.
Full textAbstract:
Project success has multiple definitions in the scholarly literature. Research has shown that some scholars and practitioners define project success as the completion of a project within schedule and within budget. Others consider a successful project as one in which the customer is satisfied with the product. This quantitative study was conducted to test the relationship between communications of agile teams and project success. The research also tested the relationship between software process improvement and project success. The researcher presented three different characterizations of project success (time, budget and customer satisfaction). Through correlation testing, the study examined the results of the relationship between communications, software process improvement, and project success. The customer satisfaction definition of project success was more closely correlated with projects in which communications was effective. Projects characterized as having a formal software process improvement process in place were more closely correlated with the cost and schedule definitions of project success. Implications of the study include conducting further research with ordinal data in the regression testing of the independent and dependent variables. Future work should concentrate upon risk and change management in an agile project management project environment. This work furthers the ideas contained in the Project Management Second Order (PM-2) framework.
3
Habarta, Lukáš. "Softwarová podpora projektového řízení." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2019. http://www.nusl.cz/ntk/nusl-403821.
Full textAbstract:
The topic of this thesis is project management and description of software solution for project management support. This software solution was also implemented within the thesis. The first part contains a description of the terminology used in project management. There is described project management as well. The second part contains a description of technical analysis and implementation of the web application for project management.
4
Annavajjala, Karuna. "Java challenge software project." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=893.
Full textAbstract:
Thesis (M.S.)--West Virginia University, 1999.Title from document title page. Document formatted into pages; contains viii, 107 p. : ill. (some col.) Vita. Includes abstract. Includes bibliographical references (p. 79-80).
5
Ljungquist, Andreas, and Björn Rosander. "Software Project Planning : The Relationship between Project Planning and Project Success." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3309.
Full textAbstract:
Software engineering is the computer science discipline concerned with developing computer software. However, software engineering does not only include the technical perspective of producing software. It also involves management issues, such as planning, controlling, and monitoring a software project. A project typically embraces a structured set of activities, which are performed in a pre-determined sequence. The initial activity is generally the process of planning the project, which according to some is one of the most important and crucial efforts in order to achieve pre-defined objectives. Other states the opposite and claim that too much planning may obstruct development creativity. Current thesis explores the planning paradigm and the significance of planning efforts in the Swedish software industry. Contemporary literatures on software project planning are reviewed and presented. Moreover, the result of an empirical study, examining the relationship between project planning and project success, is presented.
6
Nimmakayala, Akhilesh, and Venkata Sai Anurudh Gudivada. "The significance of Software Engineering Management in Software projects : A study on Project Management success factors, an ideal Project Manager and the current state of Project Management Education." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17247.
Full textAbstract:
Background. Management is an essential factor in any organization let alone its kind and size. Project management is the art and science of planning and implementing a project to achieve the desired outcome. Project Management (PM) plays a crucial role in businesses which are bound to function in a team-based environment regardless of the type of business. Although a variety of project management practices are employed in different kinds of industries, it is well understood that the style and level of employment of these project management practices have a significant impact on the project success. The software engineering industry has its own project management practices and the employment of these practices depends on the project manager who thus plays a key role in project management. Project manager has been a ubiquitous feature of traditional software projects. Project managers are a merger of personal characteristics and areas of competency that act together to integrate the various components of a project. In this study, the author discusses about the concept of software engineering management, various characteristics and key competencies of a project manager and also the factors influencing the overall success of a project. The authors also discuss about the current state and importance of PM education and its influence in the real time industry. Objectives. This research study is to analyze and make conclusions about the ideal features of a project manager and therefore attempt to understand its association with critical factors of PM for a project’s success in terms of delivering the product as scheduled and also understand various non-PM factors that are critical for project success. The study also attempts to show the significance of studying PM specifically in the context of Software Engineering as different from other contexts and the importance of PM education in academics and teaching PM in the industry. Methods. To achieve the objectives of this research, we attempt to study project management in the context of Software Engineering by conducting a literature review followed with a descriptive Survey as our research methods for this study to show how far literature complies to the present-day views and overall form a common opinion on this subject by comparing both the findings. Results. The results yielded by conducting a literature review conclude that Project Management or Software Engineering Management plays a vital role in software projects. Various factors that contribute towards successful project management were identified. Also, relevant literature was reviewed to identify the characteristics and competencies of an effective project manager and the status of project management education in academics and in the software engineering industry. The results obtained from the literature review were used in designing a survey and were further used to compare with and validate the results of this survey. A thorough analysis of these results yielded in capturing the current status and views with a snapshot of the situation in the present Software Engineering industry. A clear view on the subject area and results from a sample population of 73 software engineering professionals consisting of up to 41 experienced managers were analyzed, commented and documented. Conclusions. Various conclusions were drawn including discussions on the compliances and contradictions between present literature and software professionals in the present industry have been made. It was found that the majority of software professionals believe that project management in software engineering is unique from project management in other disciplines. It was found that professionals believe project management to be highly to very highly crucial for the overall success of software projects and that the most important key factors for successful project management were team motivation, communication and risk management. It was found that ‘Ability to foresee a problem’, ‘Decision making’ and ‘Inspires a shared vision’ were among the top three characteristics and ‘Team management’, ‘Leadership’ and ‘Ability to work under pressure’ were among the top three competencies of an effective project manager. It was found that managers feel the need to be taught about project management standards and that the ‘PMBoK’ and ‘ISO 9001’ were the most popular standards implemented. It was found that there are very contrasting views among companies on training project managers before promoting them to managerial positions whereas managers expect to be trained. Keywords: Software Engineering Management, Software Project Management, Project Manager, Project Success, Project Management Education, Software Engineering.
7
Crosby, Dave. "Project risk management in smaller software teams." Click here to access this resource online, 2007. http://hdl.handle.net/10292/378.
Full textAbstract:
This thesis investigates project risk management issues in smaller software teams. Certain gaps in the literature are identified. There is limited literature on what risk management techniques software practitioners use. The studies that are published tend to focus on large software teams. This thesis investigates what risks these smaller teams consider to be important. It also investigates what techniques are perceived to address these risks and how effective those techniques are considered to be. One of those risks is found to be of primary importance, yet this risk is not suggested by the project management literature. This thesis goes on to conduct a more in-depth exploration of that specific risk in the context of these smaller teams Interviews were selected as the most appropriate method to achieve the objectives of the thesis. Nineteen interviews in eight software organisations are conducted to collect data for this thesis. Three different perspectives on project risk were investigated. Those were the perspectives of the; service managers, project managers and developers. Hence a large store of rich information is collated. The results are analysed and a rich set of information is presented in this thesis. As a result of this research it is suggested that smaller software teams may find it useful to consider the 16 risks discussed in this research and how applicable those risks are to their individual organisation. Service managers may need to do more to raise the awareness of the importance of risks associated with ‘customer relationship issues’ within their own organisations. Three risks stood out as areas where future research might be most fruitful. They were; customer relationship issues, introduction of new technology and unrealistic schedules and budgets. Risks related to customer relationship issues were of particular significance and have tended to be over looked in the project management literature. It is submitted that research into standard project risk management approaches may need to be combined with business risk management approaches to gain a full understanding of the risks faced and addressed by these smaller teams.
8
Ren, J. "Search based software project management." Thesis, University College London (University of London), 2013. http://discovery.ucl.ac.uk/1398915/.
Full textAbstract:
This thesis investigates the application of Search Based Software Engineering (SBSE) approach in the field of Software Project Management (SPM). With SBSE approaches, a pool of candidate solutions to an SPM problem is automatically generated and gradually evolved to be increasingly more desirable. The thesis is motivated by the observation from industrial practice that it is much more helpful to the project manager to provide insightful knowledge than exact solutions. We investigate whether SBSE approaches can aid the project managers in decision making by not only providing them with desirable solutions, but also illustrating insightful “what-if” scenarios during the phases of project initiation, planning and enactment. SBSE techniques can automatically “evolve” solutions to software requirement elicitation, project staffing and scheduling problems. However, the current state-of- the-art computer-aided software project management tools remain limited in several aspects. First, software requirement engineering is plagued by problems associated with unreliable estimates. The estimations made early are assumed to be accurate, but the projects are estimated and executed in an environment filled with uncertainties that may lead to delay or disruptions. Second, software project scheduling and staffing are two closely related problems that have been studied separately by most published research in the field of computer aided software project management, but software project managers are usually confronted with the complex trade-off and correlations of scheduling and staffing. Last, full attendance of required staff is usually assumed after the staff have been assigned to the project, but the execution of a project is subject to staff absences because of sickness and turnover, for example. This thesis makes the following main contributions: (1) Introducing an automated SBSE approach to Sensitivity Analysis for requirement elicitation, which helps to achieve more accurate estimations by directing extra estimation effort towards those error-sensitive requirements and budgets. (2) Demonstrating that Co-evolutionary approaches can simultaneously co-evolve solutions for both work package sequencing and project team sizing. The proposed approach to these two interrelated problems yields better results than random and single-population evolutionary algorithms. (3) Presenting co-evolutionary approaches that can guide the project manager to anticipate and ameliorate the impact of staff absence. (4) The investigations of seven sets of real world data on software requirement and software project plans reveal general insights as well as exceptions of our approach in practise. (5) The establishment of a tool that implements the above concepts. These contributions support the thesis that automated SBSE tools can be beneficial to solution generation, and most importantly, insightful knowledge for decision making in the practise of software project management.
9
Fontoura, Lisandra Manzoni. "PRiMA : project risk management approach." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2006. http://hdl.handle.net/10183/6947.
Full textAbstract:
Esta tese propõe uma abordagem sistemática para gerenciar riscos em projetos de software, por meio da adaptação de processos. O objetivo da abordagem é permitir a elaboração de um processo específico para um dado projeto, visando minimizar a exposição do projeto aos riscos, identificados de acordo com o contexto do projeto. As atividades, possíveis de serem executadas em processos de projetos de uma organização, são estruturadas em um framework de processo (PRiMA-F), que inclui também os padrões de processo e organizacionais usados para descrever ações preventivas e corretivas aos riscos. A estruturação do framework básico, construído pela organização, poderá permitir distintas instanciações, como por exemplo, processos de acordo com o paradigma ágil ou planejado, ou em conformidade com normas de qualidade, como CMM e outras; além dos padrões organizacionais e de processo para gestão de riscos de projeto. PRiMA-F define o escopo maior do processo de software da organização e este é adaptado de acordo com os riscos identificados para o projeto e suas necessidades específicas, dando origem ao processo a ser usado no projeto. adaptação. Os guias descrevem como adaptar elementos de processo de acordo com o tamanho e o formalismo do projeto. Configurações de processo são modelos prédefinidos, visando atender projetos típicos ou modelos de qualidade. Prima-F pode ser estendida para novos riscos, padrões e processos, de acordo com as necessidades da organização. Utilizando o paradigma Goal/Question/Metric, no framework de processo (PRiMAF), são definidas métricas do processo de software, associadas aos riscos, para serem usadas para acompanhar o progresso dos fatores de risco, possibilitando ao gerente de projeto tomar ações corretivas, quando necessário e no momento adequado. As ações corretivas são descritas usando padrões organizacionais e de processo. Uma ferramenta de apoio à sistemática proposta (PRiMA-Tool) foi desenvolvida. Estudos de caso foram elaborados para validar a sistemática proposta
10
MARANHÃO, Robson Godoi de Albuquerque. "An approach to innovative software project management in software factories." Universidade Federal de Pernambuco, 2016. https://repositorio.ufpe.br/handle/123456789/18619.
Full textAbstract:
Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-04-24T14:13:59Z
No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
An Approach to Innovative Software Project Management - Final.pdf: 4765797 bytes, checksum: 1279ab985bdeaf01b2453e5ba5ace612 (MD5)Made available in DSpace on 2017-04-24T14:13:59Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) An Approach to Innovative Software Project Management - Final.pdf: 4765797 bytes, checksum: 1279ab985bdeaf01b2453e5ba5ace612 (MD5) Previous issue date: 2016-09-05
CNPQ
Innovation has been recognized as an essential condition for gaining competitive advantage, but also for survival in the software industry. The participation of everyone is essential both in idea generation and innovation implementation. Besides the innovation concern, project-oriented software factories are adopting models like CMMI and MPS.Br to achieve an advantage regarding quality. However, the engagement of everyone is sometimes overlooked, so that innovative ideas (incremental innovations) or opportunities for improvement are not perceived. The aim of this study is to build an approach to manage innovative software project (ISPM), guiding project managers and team members in managing innovation in project-oriented software factories. Thus, this approach can be a determining factor in fostering innovation and avoiding it to be stifled by stimulating engagement and participation. A mixed method was used to analyze the phenomenon of fostering innovation in project-oriented software factories, composed of a systematic literature review (SLR) and an action research (AR) in a real organization. The SRL analyzed 17 primary studies, from an initial set of 2,827 articles, where impact factors in ISPM were identified, resulting in the initial approach. The action research was conducted in a large international organization of software development, with units throughout Brazil. The final model of the ISPM approach confirmed the positive influence of engagement and participation of everyone on idea generation and innovative behavior project-oriented software factories. Demonstrating that it is possible to innovate in this context and keep following the procedures defined for the organization. In particular, the findings showed that the creation of a motivating and open environment for creativity made feasible the innovation development. The study results provided explanatory power to promote innovation, as well as showed the importance to study such phenomena in the software industry, specifically in project-oriented software factories. Moreover, the approach provided several strategies and recommendations for professionals to foster innovation and avoid it to be stifled.
Inovação tem sido reconhecida como uma condição essencial para se ganhar vantagem competitiva e sobreviver na indústria de software. A participação de todos é primordial, tanto na geração de ideias quanto na implementação da inovação. Além da preocupação em inovar, as fábricas de software orientadas a projetos vêm adotando modelos como CMMI e MPS.Br para conseguir um diferencial em termos de qualidade. Porém, o engajamento de todos por vezes é negligenciado, fazendo com que ideias inovadoras (inovações incrementais) ou oportunidades de melhoria não sejam percebidas. O objetivo deste estudo é construir uma abordagem para o gerenciamento de projetos inovadores de software (ISPM), orientando os gerentes de projeto e membros da equipe na gestão da inovação, em fábricas de software orientadas a projetos. Desta forma, esta abordagem pode ser um fator determinante para fomentar a inovação e evitar que ela seja sufocada, ao estimular o engajamento e participação de todos. Um método misto foi utilizado para analisar o fenômeno do fomento à inovação em fábricas de software orientadas a projetos, sendo composto por uma revisão sistemática da literatura (SLR) e uma pesquisa-ação (AR) em organização real. A SRL analisou 17 estudos primários, de um conjunto inicial de 2.827 artigos, onde foram identificados os fatores de impacto para o ISPM, resultando na elaboração de uma abordagem inicial. A pesquisa ação foi realizada em uma grande organização internacional de desenvolvimento de software, com unidades espalhadas pelo Brasil. O modelo final da abordagem para ISPM confirmou a influência positiva do engajamento e da participação de todos na geração de ideias e no comportamento inovador em fábricas de software orientadas a projetos. Demonstrando que é possível inovar neste contexto, sem abdicar de seguir os processos definidos para a organização. Em particular, os achados mostraram que a criação de um ambiente motivador e aberto à criatividade viabilizaram o fomento da inovação. O resultado do estudo proporcionou poder explanatório ao fomento da inovação, assim como mostrou a importância de se estudar o fenômeno na indústria de software, especificamente em fábricas de software orientadas a projetos. Além disso, a abordagem proporcionou diversas estratégias e recomendações aos profissionais da área para fomentar a inovação e evitar que ela seja sufocada.
11
Magnusson, Evelina, and Moa Westlund. "Measuring Performance in Large Scale Agile Software Development Projects." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-300388.
Full textAbstract:
The increased usage and need for software as part of products has challenged traditional project management, nevertheless for hardware heavy organisations that are used to rely on the linear prediction and tracking of project outcomes. The developments in projects with embedded systems have countless dependencies and almost impossible to predict. Literature shows that software development projects have problems meeting the initial goals of budget, time, and scope. This is discovered too late due to insufficient methods of tracking progress. The purpose of this thesis was to investigate how large agile software development projects can continuously be followed to evaluate their performance and meet initial customer agreements fixed in time, budget, and scope. The thesis was conducted at Saab, active in the defense and security industry. This qualitative exploratory study was conducted with semistructured interviews and focus group discussions at the case company Saab, benchmark interviews with two additional companies, and an extensive literature study. The issues with the existing tracking approach were explored to determine how progress tracking may be created to continuously measure progress and indicate if project goals will be accomplished or not. The more general challenges in software development were also investigated to provide knowledge about areas in need of additional metrics which could indicate the problem and mitigate it. One industry-specific challenge is the security aspect that is unavoidable and requires a lot of documentation that holds up the development activities. Other detected challenges were difficulties in understanding requirements that lead to faulty estimations and work in the wrong direction, undiscovered dependencies that lead to a lot of rework and waiting for additional parts, insufficient testing environments that lead to late feedback, and holds up the development. It was also visible that the projects were conducted with different management approaches and no best-proven practice existed for tracking performance. From an analysis of the empirical data and existing literature, a suggestion of method tracking design was developed for large agile software projects with fixed contracts. The models were proposed to allow flexibility, enable control, and provide a holistic view. As Saab intends to introduce Earned Value Management in their software projects, this method was complemented with COMOD, TRL, IRL, and SRL to provide these three characteristics. Transparency and visibility of both products and processes are also found to be key to project success, thus additional metrics to increase visibility in projects are suggested to enable efficient project leading.Den ökade användningen och behovet av mjukvara har utmanat traditionell projektledning, speciellt för hårdvaruorganisationer som är vana att kunna förlita sig på den linjära utvecklingen av ett projek. Utvecklingen av projekt som inkluderar inbyggda system med otaliga beroenden är nästan omöjliga att förutsäga. Litteratur visar att mjukvaruutvecklingsprojekt har problem att nå de ursprungliga målen för budget, tid och omfattning. Detta upptäcks för sent på grund av otillräckliga metoder för att mäta framsteg i projekt. Detta examensarbete genomfördes som en fallstudie på Saab, aktiv inom försvar- och säkerhetssektorn. Syftet med denna avhandling har varit att utvärdera hur projektledning för stora agila mjukvaruutvecklingsprojekt kontinuerligt kan följa utvecklingen för att möta de ursprungliga kundavtalen som är fastställda i tid, budget och omfattning. Denna kvalitativa undersökningsstudie genomfördes med semistrukturerade intervjuer och fokusgrupp intervjuer på företaget Saab, benchmarking intervjuer med ytterligare två företag och en omfattande litteraturstudie. För att utvärdera hur en metod för utvärdering av projektstatus ska utformas för att i tid ange om projektmålen inte kommer att uppnås, undersöktes utmaningarna med mjukvaruutveckling och därifrån har möjliga mätvärden och metoder för att mildra eller upptäcka dessa problem utvärderats. Några av de upptäckta problemen verkar överlappa flera industrier medan andra verkar vara mer specifika för just militär- och försvarsindustrin. En branschspecifik utmaning är säkerhetsaspekten som är oundviklig och kräver mycket dokumentation som stannar upp utvecklingsaktiviteterna. Andra upptäckta utmaningar var svårigheter att förstå krav som leder till felaktiga uppskattningar och arbete i fel riktning, oupptäckta beroenden som leder till mycket omarbetning och väntande på ytterligare delar, otillräckliga testmiljöer som leder till sen feedback och håller upp utvecklingen. Stora skillnader i de metoder som idag tillämpas från projektledning i dessa projekt var synligt under projektet, vilket indikerar på att det idag inte finns någon accepteras bästa metod i uppföjlning. Från analys av samlad empirisk data samt befintlig litteratur utvecklades ett förslag på hur en metod för uppföljning av stora agila mjukvaruprojekt skulle kunna se ut. Design på föreslagen modell skulle möjliggöra flexibilitet och kontroll samt förmedla ett helhetsperpektiv. Eftersom Saab avser att introducera Earned Value Management i sina mjukvaruprojekt kompletterades denna metod med COMOD, TRL, IRL och SRL för att få dessa tre egenskaper. Öppenhet och synlighet för både produkt och process visar sig också vara nyckeln till framgång i projektutveckling, vilket är möjligt med ytterligare mått för att öka synligheten i projektet.
12
Czibor, František. "Softwarová podpora projektového řízení." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2009. http://www.nusl.cz/ntk/nusl-236760.
Full textAbstract:
This thesis deals with project management and how software can support it. In first part the problems and characteristics of project management is stressed as well as theoretical basics with focus on software development projects. Comparison of the available tools as project management aid is also touched. Objective of this thesis is to create such a project management aid tool by detailed analysis, design and implementation. The system has been implemented in programming language C#, the database layer is Microsoft SQL. End the end of the thesis the summary of the achieved results and possible future extensions of the project management tool can be found.
13
Arwe, John E. (John Elliott) 1964. "Reducing system software project risk through choice of project architecture." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/9744.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 1999.Includes bibliographical references (leaves 83-86).
The choice of project architecture - the structure of and interrelationships between product, processes, and organization - alters the project's risk profile. While most analyses take project scope as an input, I propose the examination of multiple project decompositions take place as part of project planning and project monitoring. The subprojects created by each decomposition will have unique risk profiles, suggesting different process and organizational adaptations that lower overall project risk. By selecting project decompositions that partition risk and then adapting the structure of each sub-project to mitigate its particular risks, the probability of risk occurrence is reduced and the severity of consequences may be reduced. Case studies of four IBM mainframe system software projects illustrate lessons regarding project architecture, some general and some project- or process-specific. These projects employ both waterfall and iterative process models, managed using varying degrees of functional, lightweight, and heavyweight organizations.
by John E. Arwe.
S.M.
14
Tuzmen, Metin. "Project Manager 2007 /." Connect to title online, 2007. http://minds.wisconsin.edu/handle/1793/34210.
Full text
15
Liberto, Samuel Matthew. "Computer software project management : an introduction." Thesis, Monterey, California. Naval Postgraduate School, 1991. http://hdl.handle.net/10945/26427.
Full textAbstract:
This thesis addresses the general principles of computer software project management. The main objective is to aid perspective software project managers in dealing with the development and management of software projects. The definition of the classical software development life cycle is given. The components include system engineering, analysis, design, coding, testing, and maintenance. The thesis contains a description of the reasons why many software projects have cost overruns and late schedules. The variability of requirements and software complexity are two factors. Proper project management is one remedy to project cost overruns and late schedules. The components of software project management are planning, organizing, directing, and controlling. Many tables of comparisons and techniques for aiding software project management are given. State of the art software development techniques are discussed. Finally, a checklist to aid software managers when developing software is provided
16
Demir, Kadir Alpaslan. "Measurement of software project management effectiveness." Monterey, Calif. : Naval Postgraduate School, 2008. http://edocs.nps.edu/npspubs/scholarly/dissert/2008/Dec/08Dec%5FDemir.pdf.
Full textAbstract:
Dissertation (PhD. in Software Engineering)--Naval Postgraduate School, December 2008.Dissertation Advisor(s): Michael, James Bret ; Osmundson, John. "December 2008." Description based on title screen as viewed on January 29, 2009. Includes bibliographical references (p. 385-400). Also available in print.
17
Heidrich, Jens. "Goal-oriented quantitative software project control." Stuttgart Fraunhofer-IRB-Verl, 2008. http://d-nb.info/993138713/04.
Full text
18
Zych, David M. (David Michael Robert) 1980. "Software redesign of the Haystack project." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/86747.
Full text
19
Lipkin, Ilya. "Testing Software Development Project Productivity Model." University of Toledo / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=toledo1321593577.
Full text
20
Björklund, Anna. "NoSQL Database for Software Project Data." Thesis, Umeå universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-43838.
Full textAbstract:
The field of databases have exploded in the last couple of years. New architectures try to meet the need to store more and more data and new kinds of data. The old relational model is no longer the only way and the NoSQL movement is not a trend but a new way of making the database fit the data, not the other way around.This master thesis report aims to find an efficient and well designed solution for storing and retrieving huge amounts of software project data at Tieto. It starts by looking at different architectures and trying three to see if any of them can solve the problem. The three databases selected are the relational database PostgreSQL, the graph database Neo4j and the key value store Berkeley DB. These are all implemented as a Web service and time is measured to find out which, if any, can handle the data at Tieto. In the end it is clear that the best database for Tieto is Berkeley DB. Even if Neo4j is almost as fast, it is still new and not as mature as Berkeley DB.
21
Henry, Troy Steven. "Architecture-Centric Project Estimation." Thesis, Virginia Tech, 2007. http://hdl.handle.net/10919/32756.
Full textAbstract:
In recent years studies have been conducted which suggest that
taking an architecture first approach to managing large software
projects can reduce a significant amount of the uncertainty present
in project estimates. As the project progresses, more concrete
information is known about the planned system and less risk is
present. However, the rate at which risk is alleviated varies
across the life-cycle. Research suggests that there exists a
significant drop off in risk when the architecture is developed.
Software risk assessment techniques have been developed which
attempt to quantify the amount of risk that varying uncertainties
convey to a software project. These techniques can be applied to
architecture specific issues to show that in many cases, conducting
an architecture centric approach to development will remove more
risk than the cost of developing the architecture. By committing to
developing the architecture prior to the formal estimation process,
specific risks can be more tightly bounded, or even removed from the
project.
The premise presented here is that through the process of
architecture-centric management, it is possible to remove
substantial risk from the project. This decrease in risk exceeds
that at other phases of the life-cycle, especially in comparison of
the effort involved. Notably, at architecture, a sufficient amount
knowledge is gained by which effort estimations may be tightly
bounded, yet the project is early enough in the life-cycle for
proper planning and scheduling. Thus, risk is mitigated through the
increase in knowledge and the ability to maintain options at an
early point. Further, architecture development and evaluation has
been shown to incorporate quality factors normally insufficiently
considered in the system design.
The approach taken here is to consider specific knowledge gained
through the architecting process and how this is reflected in
parametric effort estimation models. This added knowledge is
directly reflected in risk reduction. Drawing on experience of
architecture researchers as well as project managers employing this
approach, this thesis considers what benefits to the software
development process are gained by taking this approach. Noting a
strong reluctance of owners to incorporate solid software
engineering practices, the thesis concludes with an outline for an
experiment which goes about proving the reduction in risk at
architecture exceeds the cost of that development.Master of Science
22
Hendrich, Michal. "Řízení projektů v kompetenčním centru SQA." Master's thesis, Vysoká škola ekonomická v Praze, 2013. http://www.nusl.cz/ntk/nusl-192562.
Full textAbstract:
This thesis deals with project management competence center in Software Quality Assurance, which operates the University of Economics in Prague. The first part of this thesis is focused on basic terminology management projects and projects aimed at testing. The second part focuses on project management competence center in Software Quality Assurance, which describes a modified project life cycle according to the PMBOK and project life cycle testing. All phases of the lifecycle contain sub-activities and the person responsible for the activity. The last part of this thesis is focused on management competency center Software Quality Assurance tool available for cooperation IBM Connections, which is available for students and staff of the University of Economics in Prague. The thesis is a complex material intended primarily for manager competency center, its teams and includes guides on how to manage the very center and its projects.
23
Middleton, Nigel Peter Jon. "Managing software quality." Thesis, Imperial College London, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.286299.
Full text
24
Söderlund, Joakim. "Managing Free Software Projects." Thesis, Linnéuniversitetet, Institutionen för datavetenskap, fysik och matematik, DFM, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-22106.
Full textAbstract:
Developing as free software is a powerful and popular way to create software. Many successful projects such as Apache, GNU/Linux and Mozilla Firefox were created as free software. In this degree project we will take a close look at how to manage free software projects. A free software project named Shaskel will also be set up as a practical example.
25
Ahmedshareef, Zana. "Controlling schedule duration during software project execution." Thesis, University of Brighton, 2015. https://research.brighton.ac.uk/en/studentTheses/819fb81b-e3c1-40ce-bad9-f44308fdbc79.
Full textAbstract:
This thesis describes a method of identifying the influences on schedule delays in projects that develop large software systems. Controlling schedule duration is a fundamental aspect of managing projects because of the financial losses associated with late projects. While challenges with controlling software projects have been investigated, there still seemed to be more to be learned about the interplay of a range of factors during project execution and that affect project duration when developing and integrating software systems within enterprise architecture environment.
26
Tsao, Heng-Jui. "Personal Software Process (PSP) Scriber." CSUSB ScholarWorks, 2002. https://scholarworks.lib.csusb.edu/etd-project/2140.
Full textAbstract:
Personal Software Process (PSP) Scriber is a Web-based software engineering tool designed to implement an automatic system for performing PSP. The basis of this strategy is a set of tools to facilitate collection and analysis of development data. By analyzing the collected data, the developer can make informed, accurate decisions about their individual development effort.
27
Foley, Katherine Marie. "Software pilferage in government agencies." CSUSB ScholarWorks, 1992. https://scholarworks.lib.csusb.edu/etd-project/755.
Full text
28
Katiyar, Kirti. "CARES - Computer Aided Rehabilitation Software." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2857.
Full textAbstract:
This project was done with the vision that it would simplify and improve outpatient treatment of substance abusers through a rehabilitation software program with 24-7 access availability. By developing an easy-to-use interface for out-patient substance abuse patients, they along with their counselors, administrators and insurance agencies, will be able to facilitate continuous communication during the course of a patient's treatment.
29
Jaber, Khaled M. "Supporting Project Tasks, Resources, Documents, and Defects Analysis in Software Project Management." Ohio University / OhioLINK, 2016. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1461609929.
Full text
30
Gigler, Thomas Russell III. "Moops: A web implementation of the Personal Software Process reporting system." CSUSB ScholarWorks, 2008. https://scholarworks.lib.csusb.edu/etd-project/3382.
Full textAbstract:
The purpose of Moops is to bridge the gap between PSP Scriber, geared very specifically to the CSCI655 class, and other available PSP implications which are so general they are difficult to use immediately without valuable time spent learning the software. Moops is a PHP/MySQL based web application designed to provide the students taking the CSCI655 graduate software engineering course at CSUSB with an intuitive, easy to use tool to implement the Personal Software Process (PSP). Moops eliminates the possibility of errors in calculations by completing all calculations for the user.
31
Rahim, Faizul Azli Mohd. "Factors contributing to information technology software project risk : perceptions of software practitioners." Thesis, University of Liverpool, 2011. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.548788.
Full textAbstract:
The majority of software development projects normally connected with the application of new or advanced technologies. The use of advanced and, in most cases, unproven technology on software development projects could leads to a large number of risks. Every aspect of a software development project could be influenced by risks that could cause project failure. Generally, the success of a software development project is directly connected with the involved risk, i.e. project risks should be successfully mitigated in order to finish a software development project within the budget allocated. One of the early researches on risk of software projects was conducted by Boehm (1991) where the research identified top 10 risk factors for software project. Boehm research had been the starting point of research in risk of software projects. For the past 10-15 years, many researches had been conducted with the introduction of frameworks and guidelines. However, still software development project failures had been reported in the academic literatures. Researchers and practitioners in this area have long been concerned with the difficulties of managing the risks relating to the development and implementation of IT software projects. This research is concerned specifically with the risk of failure of IT software projects, and how related risk constructs are framed. Extant research highlights the need for further research into how a theoretically coherent risk construct can be combined with an empirical validation of the links between risk likelihood, risk impact on cost overrun, and evidence of strategic responses in terms of risk mitigation The proposal within this research is to address this aspect of the debate by seeking to clarify the role of a project life cycle as a frame of reference that contracting parties might agree upon and which should act as the basis for the project risk construct. The focus on the project life cycle as a risk frame of reference potentially leads to a common, practical view of the (multi) dimensionality setting of risk within which risk factors may be identified and which believe to be grounded across a wide range of projects and, specifically in this research, for IT software projects. The research surveyed and examine the opinions of professionals in IT and software companies. We assess which risk factors are most likely to occur in IT software projects; evaluate risk impact by assessing which risk factors IT professionals specifically think are likely to give rise to the possibility of cost overruns; and we empirically link which risk mitigation strategies are most likely to be employed in practice as a response to the risks and impacts identified. The data obtained were processed, analysed and ranked. By using the EXCEL and SPSS for factor analysis, all the risk factors were reduced and groups into clusters and components for further correlation analysis. The analysis was able to evidence opinion on risk likelihood, the impact of the risk of cost overrun, and the strategic responses that are likely to be effective in mitigating the risks that emerge in IT software projects. The analysis indicates that it is possible to identify a grouping of risk that is reflective of the different stages of the project life cycle which suggest three identifiable groups when viewing risk from the likelihood of occurrence and three identifiable groups from a cost overrun perspective. The evidence relating to the cost overrun view of risk provided a stronger view of which components of risk were important compared with risk likelihood. The research account for this difference by suggesting that a more coherent framework, or risk construct, offered by viewing risk within the context of a project life cycle allows those involved in IT software projects to have a clearer view of the relationships between risk factors. It also allows the various risk components and the associated emergent clusters to be more readily identifiable. The research on strategic response indicated different strategies as being effective between risk likelihood versus cost overrun. The study was able to verify the effective mitigation strategies that are correlated to the risk components. In this way, the actions or consequences conditioned can be observed on identification of risk likelihood and risk impact on cost overrun. However, the focus of attention on technical issues and the degree to which they attract strategic response is a new finding in addition to the usual reports concerning the importance of non-technical aspects of IT software projects. The research also developed a fuzzy theory based model to assist software practitioners in the software development life cycle. This model could help the practitioners in the decision making of dealing with risks in the software project. The contribution of the research relates to the assessment of risk within a construct that is defined in the context of a fairly broadly accepted view of the life cycle of projects. The software risk construct based on the project management framework proposed in this research could facilitates a focus on roles and responsibilities, and allows for the coordination and integration of activities for regular monitoring and aligning with the project goals. This contribution would better enable management to identify and manage risk as they emerge with project stages and more closely reflect project activity and processes and facilitate the risk management strategies exercise. Keywords: risk management, project planning, IT implementation, project life cycle
32
MARINHO, Marcelo Luiz Monteiro. "Uncertainty management in software projects." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/15977.
Full textAbstract:
Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-03-15T15:42:08Z
No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Uncertanty Management in Software Projects - Marcelo Marinho.pdf: 6691446 bytes, checksum: c11ad7bca6e24d387867ffea22b8e5ed (MD5)Made available in DSpace on 2016-03-15T15:42:08Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Uncertanty Management in Software Projects - Marcelo Marinho.pdf: 6691446 bytes, checksum: c11ad7bca6e24d387867ffea22b8e5ed (MD5) Previous issue date: 2015-11-11
Various projects types are proposed with different objectives; it is necessary to manage strategically, according to organizational goals. Successful projects increase sales, reduce costs, improve quality, customer satisfaction, the work environment; among other benefits. An increasing number of companies use project management as a key strategy for maintaining competitiveness, increasing the value possibility to their business. However, many projects with all the ingredients for success fail. One reason for this is related to failure in assessing the uncertainties by executives, managers and project team. In a typical software development environment it is not different. Thus, the aim of this work is to propose an approach to manage uncertainties in software projects to contribute to their better performance and influence their success. The research method used in this work is based on the principles of Evidence-Based Software Engineering. During the guide conception stage an exploratory literature research on managing uncertainty in software projects and a systematic literature review on the state of the art theme in a more structured way along with an action research conducted in a software development project were conducted. In addition, semi-structured interviews with software industry experts and researchers in the field were carried out in order to obtain improvement to the approach. In the evaluation phase a focus group was conducted to evaluate the proposed approach. The results showed that an exploratory literature review helped to characterize the difference between risk and uncertainty and mapped the uncertainty sources. The systematic literature review found 5 ways to manage uncertainties in projects; 18 practices for project management focusing on reducing uncertainties; a confirmation of the uncertainty sources mapped in primary studies and the relationship between uncertainty and innovative projects was assessed. In the action research there was an application of techniques and strategies in projects and investigation on whether those contributed to uncertainty; in semi-structured interviews the addition of the practical point of view for the approach was evaluated and added. Finally, the focus group was performed to assess the elaborated approach. The results of this research contribute to software project management by defining an approach to uncertainty management, as well as describing strategies and guidelines for team members.
Vários tipos de projetos são propostos, com diferentes objetivos, em que é preciso gerenciálos estrategicamente de acordo com metas organizacionais. Projetos bem sucedidos aumentam as vendas, reduzem os custos, melhoram a qualidade, a satisfação do cliente, o ambiente de trabalho, entre outros benefícios. Assim, um número crescente de empresas utilizam o gerenciamento de projetos como uma estratégia fundamental para manter a competitividade, aumentando a possibilidade de valor aos seus negócios. No entanto, muitos projetos com todos os ingredientes para o sucesso, falham. Um dos motivos porque isso acontece relaciona-se com a não avaliação das incertezas pelos executivos, gerentes e equipe do projeto. Em um ambiente de desenvolvimento de software típico não é diferente. Baseado nisso, o objetivo geral deste trabalho é propor uma abordagem para gerenciar as incertezas em projetos de software, contribuindo assim para um melhor desempenho dos projetos de software e influenciando no seu sucesso. O método de pesquisa adotado neste trabalho está fundamentado nos princípios da Engenharia de Software baseado em evidências. Foi realizada uma pesquisa exploratória da literatura sobre gerenciamento das incertezas em projetos de software. Em seguida, de forma mais estruturada, foi realizada uma revisão sistemática da literatura sobre o estado da arte do tema juntamente com uma pesquisa-ação, conduzida em um projeto de desenvolvimento de software. Além disso, entrevistas semi-estruturadas foram realizadas com especialistas da indústria de software e pesquisadores na área a fim de avaliar as evidências encontradas e adicionar insumos para a abordagem. Na fase de avaliação foi realizado um grupo focal com especialistas que avaliaram a abordagem proposta. Os resultados da revisão da literatura exploratória serviu para caracterizar a diferença entre riscos e incertezas e foram mapeadas as fontes de incertezas. Da revisão sistemática da literatura encontramos 5 formas de gerenciar as incertezas nos projetos e 18 práticas para o gerenciamento de projetos focando na redução das incertezas. Foi realizada uma confirmação das fontes de incertezas mapeadas nos estudos primários e avaliada a relação entre incertezas e projetos inovadores. Na pesquisa-ação pôde-se aplicar técnicas e estratégias em projetos e investigar se essas contribuíram para gestão da incerteza. Nas entrevistas semiestruturadas foi avaliado e adicionado o ponto de vista prático para a abordagem. Finalmente, um grupo focal foi realizado para avaliar a abordagem elaborada. Os resultados desta pesquisa contribuem para a gestão de projetos de software por definir uma abordagem para o gerenciamento de incerteza, bem como descrevendo as estratégias e orientações para os membros da equipe.
33
Braz, Miguel Joaquim Quinta. "Gestão de projetos : as práticas de uma empresa de software." Master's thesis, FEUC, 2015. http://hdl.handle.net/10316/29690.
Full textAbstract:
Relatório de estágio do mestrado em Gestão, apresentado à Faculdade de Economia da Universidade de Coimbra, sob a orientação de Pedro Godinho e Benjamin Cardoso.Os projetos são uma realidade cada vez mais em voga nas organizações atuais, tornando-se imperativo que estas pratiquem uma gestão criteriosa ao longo de todas as fases de um projeto. A Critical Software, SA identificou na gestão de projetos a metodologia chave para apoiar o desenvolvimento dos seus projetos críticos de segurança, missão e negócio. No decorrer do meu estágio na Critical Software, SA, entre o mês de fevereiro e junho de 2015, fui tendo contacto direto com várias práticas de gestão em diferentes tipos de projetos. Motivado por esta aproximação, decidi optar por este tema para o relatório, o qual resulta do estágio curricular do Mestrado em Gestão da Faculdade de Economia da Universidade de Coimbra. Neste relatório começo por fazer uma apresentação da Critical Software, SA e depois sucede-se a revisão da literatura sobre a gestão de projetos. Sendo este um tema bastante abrangente, decidi focar-me nos conceitos e aspetos que considero fundamentais a esta área e com os quais me fui deparando ao longo do estágio. Seguidamente, abordo as práticas que esta considera basilares para realizar com sucesso a gestão dos projetos, tendo por referência o que a literatura nos diz. Após esta experiência no contexto prático, concluo que a gestão de projetos é uma atividade crucial e deve ser encarada com extrema minúcia, tendo o gestor de projeto e o departamento afeto à gestão de projetos um papel preponderante e de extrema responsabilidade, uma vez que a sustentabilidade financeira da empresa está intimamente ligada à gestão individual de cada projeto executado na organização.
34
Nichols, Kenneth Nolan. "Technical-legal aspects of software patents." CSUSB ScholarWorks, 1996. https://scholarworks.lib.csusb.edu/etd-project/1249.
Full text
35
Lee, Thomas Seward. "Software-based gradient nonlinearity distortion correction." CSUSB ScholarWorks, 2006. https://scholarworks.lib.csusb.edu/etd-project/3180.
Full textAbstract:
The primary purpose of the thesis is to discuss the use of Magnetic Resonance Imaging (MRI) in functional proton radiosurgery. The methods presented in this thesis were specifically designed to correct gradient nonlinearity distortion, the single greatest hurdle that limits the deployment of MRI-based functional proton radiosurgery systems. The new system central in the thesis fully utilized MRI to provide localization of anatomical targets with submillimeter accuracy. The thesis provides analysis and solutions to the problems related to gradient nonlinearity distortion. The characteristics of proton radiosurgery are introduced, in addition to a discussion of its advantages over other current methods of radiation oncology. A historical background for proton radiosurgery is also presented, along with a description of its implementation at Loma Linda University Medical Center (LLUMC), where a new system for functional proton radiosurgery has been proposed and is currently under development.
36
Dale, Anthony James Eric. "A Framework for Linking Projects and Project Management Methods." Thesis, University of Canterbury. Computer Science and Software Engineering, 2006. http://hdl.handle.net/10092/1182.
Full textAbstract:
Software development processes such as the Waterfall process and Extreme Programming are Project Management Methods (PMMs) which are well known and widely used. However, conventional Project Management (PM) lacks the process concepts expressed in PMMs, and the connection between PMMs and PM is not much explored in the literature. Our research problem is to make this connection. We present data models for PM and PMM, in a framework that can articulate the PM-to-PMM relationship, illustrating with simple examples. Tools and visualizations created in terms of our framework can make use of the familiarity, history and context of project management tools, and the prescriptiveness and reactivity of PMMs, and we believe these may assist the management of complicated projects, such as IT projects. Project Mentor, a prototype Java/XML implementation of the framework semantics, can create and then revise a PMM-aware project, conforming to a specified PMM. The PM-to-PMM connection is persistent in project data, and we describe a visualization of the footsteps of a PMM in project data that does not rely on the state of a PMM process. The visualization can also be used by Project Mentor, to indicate the state of a PMM. We test for possible applications of our framework with a case study and survey of some existing project data, and conclude with a description of further work.
37
Xia, Shujiang. "An improved software process management tool: ReMoTe (recursively estimating multi-threaded observation tool enterprise)." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2871.
Full textAbstract:
The principal purpose of the project is to enable ReMoTe support for multi-databases. ReMoTe stands for the Recursively Estimating Multi-Threaded Observation Technology Enterprise, which is a web-based computer aided software engineering tool for monitoring software development process. Development of ReMoTe is based on the RMT (Recursive Multi-Threaded) software life cycle developed by Scott Simon, a CSUSB alum, in his master's thesis in 1997. ReMoTe enables the monitoring of projects that use different databases in various locations. Central management can view the progress information of each project using a web browser no matter where the database or project team is located. In this project, three database software were supported, namely MySQL, Oracle, and Microsoft Access, and employed contemporary technologies such as JavaScript, PHP, and Open Database Connectivity (ODBC). Source codes are included.
38
Rainer, Austen William. "An empirical investigation of software project schedule behaviour." Thesis, Bournemouth University, 1999. http://eprints.bournemouth.ac.uk/388/.
Full textAbstract:
Two intensive, longitudinal case studies were conducted at IBM Hursley Park. There were several objectives to these case studies: first, to investigate the actual behaviour of the two projects in depth; second, to develop conceptual structures relating the lower-level processes of each project to the higher-level processes; third, to relate the lower-level and higher-level processes to project duration; fourth, to test a conjecture forwarded by Bradac et al i. e. that waiting is more prevalent during the end of a project than during the middle of a project. A large volume of qualitative and quantitative evidence was collected and analysed for each project. This evidence included minutes of status meetings, interviews, project schedules, and information from feedback workshops (which were conducted several months after the completion of the projects). The analysis generated three models and numerous insights into software project behaviour. The models concerned software project schedule behaviour, capability and an integration of schedule behaviour and capability. The insights concerned characteristics of a project (i. e. the actual progress of phases and milestones, the amount of workload on the project, the degree of capability of the project, tactics of management, and the sociotechnical aspects of a project) and characteristics of process areas within a project (i. e. waiting, poor progress and outstanding work). Support for the models and the insights was sought, with some success, from previous research. Despite the approach taken in this investigation (i. e. the collection of a large volume of evidence and the analyses of a wide variety of factors using a very broad perspective), this investigation has been unable to pinpoint definite causes to explain why a project will or will not complete according to its original plan. One `hint' of an explanation are the differences between the socio-technical contexts of the two projects and, related to this, the fact that tactics of management may be constrained by a project's socio-technical context. Furthermore, while the concept of a project as a distinct entity seems reasonable, the actual boundaries of a project in an organisation's `space-time' are ambiguous and very difficult to properly define. Therefore, it may be that those things that make a project difficult to distinguish from its surrounding organisation are interwoven with the socio-technical contexts of a project, and may be precisely those things that explain the progress of that project. Recommendations, based on the models, the insights and the conclusions, are provided for industry and research.
39
Radlinski, Lukasz. "Improved Software Project Risk Assessment Using Bayesian Nets." Thesis, Queen Mary, University of London, 2008. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.509672.
Full text
40
Vajre, Chetan D. "Modeling Dynamic Interactions in a Software Development Project." [Tampa, Fla. : s.n.], 2003. http://purl.fcla.edu/fcla/etd/SFE0000096.
Full text
41
Daniel, Sherae Lee. "Absorptive capacity and open source software project performance." College Park, Md.: University of Maryland, 2007. http://hdl.handle.net/1903/7730.
Full textAbstract:
Thesis (Ph. D.) -- University of Maryland, College Park, 2007.Thesis research directed by: Robert H. Smith School of Business. Dept. of Decision and Information Technologies. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.
42
Tian, Yuan Umphress David A. "Adapting eXtreme programming for global software development project." Auburn, Ala, 2009. http://hdl.handle.net/10415/1657.
Full text
43
Manasseh, Christian G. (Christian Georges) 1976. "Project man agrement of geographically distributed software teams." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/80158.
Full textAbstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 1999.Includes bibliographical references (leaves [102]-106).
by Christian G. Manasseh.
M.Eng.
44
Damasiotis, Vyron. "Modelling software project management complexity : an assessment model." Thesis, Staffordshire University, 2018. http://eprints.staffs.ac.uk/4834/.
Full textAbstract:
During the last years, more and more business use projectised organisation as an organisation structure to tackle complex problems needed for the implementation of their strategic objectives. A significant number of these projects were/are challenged or even failed to meet their initial requirements in terms of cost, time and quality. This phenomenon is more intense in software projects due their special characteristics sourcing from the dynamic and continuous changing environment they operate and the nature of the software itself. Most of these failures were attributed to complexity that exists in various forms and levels at all projects. Many studies attempted to identify the sources of project complexity and define an appropriate complexity typology for capturing it. However, most of these studies are theoretical and only a limited number is proposing models capable to evaluate or measure project complexity. This research, acknowledges the endogenous character of complexity in projects but instead of trying to identify complexity dimensions of this complexity in projects, focuses on the complexity in the interfaces between project processes, project management processes and project managers, which consists of the critical point for successful project execution. The proposed framework can be used in order to highlight the most significant complexity areas either organisation specific or project specific, providing in that way the necessary awareness for better, efficient and effective project management. The approach followed in framework design, identifies the variation of perception of complexity between different organisations. Allow organisations to evaluate complexity of projects and provide them with an important information that will assist project selection process. Identifies the significance of peoples’ knowledge and experience and generally the maturity/capabilities of an organisation in management in order to handle complexity, as this was revealed through the findings of this research. Furthermore, considers complexity as variable that can be measured and propose a model for it. To implement this framework, an extended literature review was initially performed, for identifying the complexity factors sourcing from project management aspects. Subsequently, statistical methods for processing and refining the identified factors were used, resulting to the final set of measures used in the framework. Finally, the proposed model was validated through the appliance of case study methodology.
45
Conrad, Paul Jefferson. "Analysis of PSP-like processes for software engineering." CSUSB ScholarWorks, 2006. https://scholarworks.lib.csusb.edu/etd-project/2962.
Full textAbstract:
The purpose of this thesis is to provide the California State University, San Bernardino, Department of Computer Science with an analysis and recommended solution to improving the software development process.
46
Ferrer, Conill Raul. "Motivation in Virtual Project Management : On the Challenges of Engaging Virtual Teams and the Features of Project Software." Thesis, Karlstads universitet, Avdelningen för informatik och projektledning, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-27432.
Full textAbstract:
As global markets transcend nationalities in search for key advantages in cost,quality and flexibility, the once unbridgeable limit of geographical location isovercome by faster Internet speed lines, online services and tools that allowindividuals and businesses to interact regardless of space and time. This thesis studies the transition from traditional project management to virtualenvironments and the impact that this new paradigm has over dispersed teamsand their interactions among themselves and the project manager. The focus of the study lays on the concept of motivation within virtual projectmanagement and the role of the project manager to overcome the specificchallenges of this new working scenario. Additionally, parallels are drawn on themotivation features that virtual project management systems offer to projectmanagers as well as team members. This study shows the importance of bridging the difficulties of motivatingdispersed teams and how traditional techniques of motivation have a muchlesser impact on team members. The idea of progress and self accomplishmentare brought forth as the strongest motivators for dispersed teams. Finally, this study exposes the shortcomings of current projectware as a tool tomotivate teams and explores the idea of applying gamification techniques tothese software packages to lift the motivation responsibilities off the shoulders ofproject managers.
47
Barkley, Cynthia Vanderwilt. "Math lessons for Fontana High School software." CSUSB ScholarWorks, 1994. https://scholarworks.lib.csusb.edu/etd-project/935.
Full text
48
Montgomery, Susan Renee. "Computers and composition: Theory and corresponding software." CSUSB ScholarWorks, 1993. https://scholarworks.lib.csusb.edu/etd-project/651.
Full text
49
Simon, Scott James. "The recursive multi-threaded software life-cycle." CSUSB ScholarWorks, 1997. https://scholarworks.lib.csusb.edu/etd-project/1306.
Full text
50
Magwali, Silibaziso Nobukhosi. "Application of project management software and its influence on project success : a case of NPOs in the Western Cape." Thesis, Cape Peninsula University of Technology, 2018. http://hdl.handle.net/20.500.11838/2871.
Full textAbstract:
Thesis (MTech (Business Administration in Project Management))--Cape Peninsula University of Technology, 2018.Though strides have been taken to ensure the availability and application of technology, there still exists some disparity between the envisaged use compared to the actual one (Ross, Romich & Pena, 2016:48). The application of technology, such as project management software (PMS), could be the answer to unlocking success in projects especially where a large scope and high degree of complexity can sometimes prove to be very challenging. The research explored how the application of PMS influences project success. A case of NPOs in the Western Cape Province, South Africa was used. The research objectives were to (1) establish if PMS is applied in the NPO’s work, (2) determine employees’ interactions with PMS relative to project success, and (3) identify the limitations of current PMS being used. A non-experimental and quantitative approach was taken to conduct the research. Out of a potential 200 units of analysis, a sample group consisting of 132 project-implementing NPOs in the Western Cape was used. Ninety-four responses were received setting the response rate at 71%. The research instruments used were questionnaires, which were administered physically and online. The data was analysed using the Statistical Package for Social Sciences (SPSS) software. There is high project success rate among NPO projects in the Western Cape at 77%. The research revealed that PMS is utilised in a significant number of organisations with the most popular ones used being Microsoft Project, Project Manager and Jira. Most project offices utilise PMS on a weekly or monthly basis especially during the project planning and execution stages. The limitations of the software include that it can over-complicate issues, be time-consuming, and costly. In light of the above, respondents revealed that they believe PMS does have a positive influence on project success. Furthermore, based on the findings and conclusions derived from this study, the researcher made a few recommendations. For example, persons in academia need to widen the scope of the study to different geographical locations and use a different research approach. Another is that software engineers/developers must consider localised support for PMS as well as improve on scalability issues. To NPOs, recommendations were made on potential training sessions to capacitate the sector to be more adept to information and communication technology (ICT) and eventually make more use of PMS.