Relevant bibliographies by topics / Software Project Management Life Cycle

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software Project Management Life Cycle'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software Project Management Life Cycle.'

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.

Journal articles on the topic "Software Project Management Life Cycle"

1

Cha, Jonghyuk, and Eunice Maytorena-Sanchez. "Prioritising project management competences across the software project life cycle." International Journal of Managing Projects in Business 12, no. 4 (December 2, 2019): 961–78. http://dx.doi.org/10.1108/ijmpb-11-2017-0145.

Full text
Abstract:
Purpose The purpose of this paper is to investigate the relative importance of project management (PM) competences across the different stages of a software project life cycle to identify competence development gaps and opportunities. Design/methodology/approach A deductive and quantitative approach was adopted to address the research questions with a web-based survey for data collection. Findings After reviewing the context of competences and PM competences, the importance of the PM competences overall and for specific stages in the project life cycle was analysed. The result highlights that functional and meta-competences are perceived to be the most important competence dimensions for software project practitioners. Originality/value This study makes three contributions. First, it consolidates PM competences into a set of 20 within four competence dimensions. Second, it prioritises these competences across the software project life cycle. Third, it identifies the significance of the inter-relationship between PM competences and project life cycle to reveal PM competence development gaps and opportunities.
APA, Harvard, Vancouver, ISO, and other styles
2

Altunel, Haluk. "Agile Project Management in Product Life Cycle." International Journal of Information Technology Project Management 8, no. 2 (April 2017): 50–63. http://dx.doi.org/10.4018/ijitpm.2017040104.

Full text
Abstract:
Agile project management methodologies are becoming more popular day by day. They provide flexibility and adaptability to customers and project teams in terms of planning and competition. Due to these benefits, the share of the agile managed projects has been increasing. Most of the agile projects are executed on products. On the other hand, every product has a life cycle. Just as living beings, it is born, it grows/changes, matures, loses ground and completes its life and dies. The stages that define the product life in this way were put forth in The Product Life Cycle Theory. One or generally more projects and various operational works accompany the product throughout the product life. In this study, the effects of applying agile project management principles on product's life cycle are analyzed. In order to receive effective results from the agile project that accompany the product, project is suggested to be divided into phases and these phases are proposed to be differentiated according to the stage of the product. Furthermore, Product Life-time Project concept is introduced with agile methodologies. It reserves a project and its team to a specific product during its whole life. Product Life-time Project is applied to software development and automotive industries and the results are presented and compared with the traditional approach.
APA, Harvard, Vancouver, ISO, and other styles
3

Favaro, J. "Guest Editor's Introduction: Renewing the Software Project Management Life Cycle." IEEE Software 27, no. 1 (January 2010): 17–19. http://dx.doi.org/10.1109/ms.2010.9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Guntamukkala, Vamsidhar, H. Joseph Wen, and J. Michael Tarn. "An empirical study of selecting software development life cycle models." Human Systems Management 25, no. 4 (November 8, 2006): 265–78. http://dx.doi.org/10.3233/hsm-2006-25405.

Full text
Abstract:
This article discussed the problem that is commonly faced by project managers in selecting an appropriate software development model. A good number of models and the ongoing debate between the advocates of agile and traditional models make the selection of a right one uneasy and complicated. The purpose of this study is to propose a new alternative view in selecting development models from the perspective of degree of flexibility in different project situations. The results of a survey conducted to 74 project managers and software developers indicate that there are three naturally occurring development model groups, including heavyweight (Waterfall and V models), middleweight (Incremental and Spiral models), and lightweight (Extreme Programming and SCRUM). A canonical function is identified to help project managers select an appropriate software development model for each potential or planned project.
APA, Harvard, Vancouver, ISO, and other styles
5

Misra, Subhas C., and Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model." International Journal of Quality & Reliability Management 32, no. 3 (March 2, 2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.

Full text
Abstract:
Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).
APA, Harvard, Vancouver, ISO, and other styles
6

Iatrellis, Omiros, and Panos Fitsilis. "A Review on Software Project Management Ontologies." International Journal of Information Technology Project Management 9, no. 4 (October 2018): 54–72. http://dx.doi.org/10.4018/ijitpm.2018100104.

Full text
Abstract:
This article aims to provide the reader with a comprehensive background for understanding current knowledge and research works on ontologies for software project management (SPM). It constitutes a systematic literature review behind key objectives of the potential adoption of ontologies in PM. Ontology development and engineering could facilitate substantially the software development process and improve knowledge management, software and artifacts reusability, internal consistency within project management processes of various phases of software life cycle. The authors examined the literature focusing on software project management ontologies and analyzed the findings of these published papers and categorized them accordingly. They used qualitative methods to evaluate and interpret findings of the collected studies. The literature review, among others, has highlighted lack of standardization in terminology and concepts, lack of systematic domain modeling and use of ontologies mainly in prototype ontology systems that address rather limited aspects of software project management processes.
APA, Harvard, Vancouver, ISO, and other styles
7

Vavilenkova, Anastasiia. "ANALYSIS OF FLEXIBLE METHODOLOGIES OF SOFTWARE DEVELOPMENT FOR IMPLEMENTATION IN TEAM PROJECTS." Bulletin of the National Technical University «KhPI» Series: New solutions in modern technologies, no. 1(7) (April 23, 2021): 39–46. http://dx.doi.org/10.20998/2413-4295.2021.01.06.

Full text
Abstract:
The materials of the article analyze the main models of the software life cycle, which underlie the flexible methodologies of software development to identify the features of its application during the implementation of team projects. It was found that the use of classical life cycle models, in particular, cascade, spiral, incremental, V-shaped and iterative, is not effective in implementing all modern aspects of software development based on the use of new information technologies. It was conducted the comparative analysis of the most popular flexible methodologies of software development Agile, Scrum, Kanban, RUP, DSDM, RAD on such indicators as life cycle model, number of iterations, purpose of project creation and types of projects for implementation, priorities, possibility of interaction with the customer, adaptation to change. The advantages and disadvantages of flexible software development methodologies made it possible to single out the MSF methodology, which is based on the harmonization of cascading, spiral and iterative models of the software development lifecycle and allows you to choose the Scrum template as the most successful for implementing and demonstrating work in team development projects. MSF uses an approach that involves the gradual creation of a working product with some functionality that reflects the requirements for the final product at this stage. It is proposed to use Microsoft solutions based on Visual Studio and Team Foundation Server for centralized management of team project elements, use of visual architecture modeling tools, code quality management capabilities and obtaining all project team members up-to-date information on project status. This is because the MSF model combines five following main models: team model; process model (sequence of actions required to build a team project); discipline of project management (provides comprehensive planning of all stages of the team project, budget management, resources, costs, scheduling); risk management disciplines and readiness management disciplines (assessment of team project members' knowledge for further distribution of team roles). The article demonstrates an example of creating a training team project based on the use of the Scrum flexible methodology template in Visual Studio based on Team Foundation Server.
APA, Harvard, Vancouver, ISO, and other styles
8

Vogel, David A. "Software Safety for Every Phase of Software Development." Biomedical Instrumentation & Technology 40, no. 4 (July 1, 2006): 309–14. http://dx.doi.org/10.2345/i0899-8205-40-4-309.1.

Full text
Abstract:
Abstract Where does risk management belong, at the beginning of a project or at the end? Many managers choose one or the other, or both. The correct answer is that risk management needs to be considered throughout the software development life cycle. When the risks include the safety of patients or the users of the software, the methods need to be more formal. This article will explain why, and then will provide the how and the how much.
APA, Harvard, Vancouver, ISO, and other styles
9

Penha, Renato, Wagner Solivan Ferreira, Luciano Ferreira da Da Silva, Flavio Santino Bizarrias, and Cláudia Terezinha Kniess. "The Contribution of a Model to Estimate Activities in Software Projects Based on Lessons Learned." Future Studies Research Journal: Trends and Strategies 13, no. 1 (January 1, 2021): 73–93. http://dx.doi.org/10.24023/futurejournal/2175-5825/2021.v13i1.541.

Full text
Abstract:
Purpose – The main objective of this article is to propose the use of a model developed by Matturo and Silva (2010) to capture knowledge in software projects based on the lessons learned.Design/methodology/approach – We carried out a qualitative research from a descriptive perspective through a single case study applied to an Enterprise Information Technology company. The company is a leader in market solutions to support customer experience management. For the data collection process, we used systematic literature review, document analysis and semi-structured interviews.Findings – The results supported project managers to better understand the storage and use of information from lessons learned in dimensioning the use of human resources and to support the estimation of new project activities. In addition, the results showed the organization's disregard for not giving due importance to the information and knowledge generated during the life cycle of a project.Research, Practical & Social implications – The model allows companies to obtain new knowledge or consult existing knowledge throughout the life cycle of projects and to support project managers in the process of estimating activities and preparing budgets with greater precision, using the information from lessons learned as a support. acquired in the completed projects.Originality/value – The lack of information in the initial scope of the project and in the definition of activities in the human resource allocation process hinder the duration of the project's development activities, directly resulting in inaccurate estimates. As a result, this scenario contributes to the increased risk of deviations in terms and / or costs of software projects.
APA, Harvard, Vancouver, ISO, and other styles
10

Alsaber, Leanah, Ebtesam Al Elsheikh, Sarah Aljumah, and Nor Shahida Mohd Jamail. "Perspectives on the adherance to scrum rules in software project management." Indonesian Journal of Electrical Engineering and Computer Science 21, no. 1 (January 1, 2021): 360. http://dx.doi.org/10.11591/ijeecs.v21.i1.pp360-366.

Full text
Abstract:
Adapting users need to fulfill their requirements and delivering products to be on time within the planned cost, is critical matter that all software project managers (SPM) put the highest priority for it while considering the users satisfaction at the same time. Agile methodology is one of the solutions provided by software engineers (SE), to get the customers involved in the system development life cycle (SDLC) to avoid the risk nonconformance cost. Yet SPM’s still facing the nonconformance costs and the dynamic changes, and the root cause of the issue is not pointed on to find a solution for it. This undertaking research aimed at determining whether software developers understand scrum rules. In addition, how does this knowledge gab affect the software projects success from the project management perspective. Furthermore, the engagement studied the impact of lack of enough knowledge on the topic to project delivery. The collected data from the qualitative and quantitative methods, which was conducted with scrum teams who worked in the <span>health information system</span> (HIS), Educational solutions, and Governmental solutions has showed deviations in organizational practices and team conflicting, competition, and pressure as well as declined product quality.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software Project Management Life Cycle"

1

Montanaro, Elsa. "Modelli e applicazioni per la valutazione della complessità dei progetti. Il caso Crif spa." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2017. http://amslaurea.unibo.it/12970/.

Full text
Abstract:
L'elaborato ha lo scopo di approfondire un tema sul quale si sta dibattendo molto negli ultimi anni: la complessità dei progetti. Ad oggi, sono stati effettuati molti studi il cui obiettivo è quello di ricercare e definire le cause di complessità dei progetti. Vista la varietà del tema, è risultato e risulta difficoltoso trovare una definizione univoca di complessità, che valga per ogni tipologia di settore industriale e per ogni tipologia di progetto. Nonostante questo, però, i progressi effettuati da parte degli studiosi sono stati notevoli e, pertanto, vengono riportati nella prima parte dell'elaborato. Oltre a queste considerazioni di stampo teorico, la difficoltà nel trattare la complessità dei progetti si esplica anche negli aspetti pratici della gestione di un'organizzazione, a livello proprio di valutazione della complessità. Questo aspetto si rivela essere molto critico per le aziende, soprattutto considerando i benefici che esse potrebbero trarre da una sua corretta valorizzazione, in termini di gestione delle risorse, applicazione di strumenti di project management adeguati, etc. Essendo questo aspetto pratico di notevole importanza, si è scelto di riportare nell'elaborato alcuni strumenti e modelli che, se correttamente implementati, possano essere di aiuto alle organizzazioni nella gestione del loro portfolio di progetti. La forza di questi modelli risiede nella loro estrema versatilità, la quale permette loro un'applicazione su larga scala. In particolar modo, nell'ultima parte della trattazione viene descritto un esempio reale che mostra proprio l'adattamento di un modello di valutazione, nato e sviluppato per un'azienda della grande distribuzione, ad una realtà aziendale differente, quella della Crif S.p.A. Nelle conclusioni sono riportati alcuni commenti dai quali si evince come l'applicazione del modello sia risultata adeguata al caso in questione.
APA, Harvard, Vancouver, ISO, and other styles
2

Kuo, Yi-Chiun. "Multi-database support in the recursive multi-threaded software process management tool." CSUSB ScholarWorks, 2002. https://scholarworks.lib.csusb.edu/etd-project/2266.

Full text
Abstract:
The Recursive Multi-Threaded (RMT) software process management tool gives software developers the following capabilities: break a large project into a sequence of prototypes (or threads) track these threads individually, and estimate the progress and completion date of the project from these individual threads. The goal of this project is to provide the RMT Tool with an ability to support multi-database for collaborative software development. As a demonstration, actual data is used from several previous algorithma projects.
APA, Harvard, Vancouver, ISO, and other styles
3

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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
4

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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
5

Švehla, Michal. "Řízení projektů pomocí specializovaných softwarů." Master's thesis, Vysoké učení technické v Brně. Fakulta stavební, 2012. http://www.nusl.cz/ntk/nusl-225700.

Full text
Abstract:
This diploma thesis deals with management of projects with specialized software. It contains principles of project management in general and in construction projects. For this purpose, it’s primarily devoted to MS Project (general), BUILDpower and CONTEC (construction projects). Thesis also offers a look at the possibilities of combining the advantages of both approaches. For practical examples, there is representative construction project in pre-investment phase. This project or its parts is elaborated in mentioned software.
APA, Harvard, Vancouver, ISO, and other styles
6

Simon, Scott James. "The recursive multi-threaded software life-cycle." CSUSB ScholarWorks, 1997. https://scholarworks.lib.csusb.edu/etd-project/1306.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pretorius, Suzaan. "The Effect of Project Types and Project Life Cycle Phases on Leadership Style." Thesis, University of Pretoria, 2019. http://hdl.handle.net/2263/72418.

Full text
Abstract:
With the current trend towards empowered teams, hierarchical company structures are increasingly being replaced by team-based ones. As a result, a shift in the classic understanding of leadership is needed and research on leadership in project management is increasing. Two major concepts have developed in recent years: shared and vertical leadership styles. This thesis reports on the development of a new Model of leadership styles that considers the effect of project types and the project life cycle phases on leadership style (vertical versus shared leadership), and how an appropriate balance between the two styles influences the likelihood of project management success. A web-based questionnaire yielded 313 complete responses and the data was analysed using hypothesis testing. Based on this empirical work and relevant literature, a novel Model is proposed. The Model explains how project types and life cycle phases influence the appropriateness of different leadership styles, and it guides the practitioner to selecting appropriate leadership styles for specific situations. Recommendations for furthering the model are discussed.
Thesis (PhD)--University of Pretoria, 2019.
NRF
Graduate School of Technology Management (GSTM)
PhD (Project Management)
Unrestricted
APA, Harvard, Vancouver, ISO, and other styles
8

Baloyi, Gidion. "The effectiveness of the project management life cycle in Eskom Limpopo Operating Unit." Thesis, University of Limpopo, 2015. http://hdl.handle.net/10386/2589.

Full text
Abstract:
Thesis (MBA.) -- University of Limpopo, 2018
South Africa is a developing state; the roles of the state owned entities in encouraging economic growth and contributing to the mitigation of unemployment and poverty eradication are unavoidable. Project management from an engineering development perspective and as an industrial discipline has been investigated and published throughout the past period. It could be said that the subject is mature, as recent publications on project management fail to bring new knowledge to light particularly in Eskom. This mini dissertation studies the most significant serious success factors in the effective project management in different departmental conditions within Eskom. Projects are being used daily in Eskom to achieve the company goal. In recent years researchers have become increasingly interested in factors that may have an impact on project management effectiveness and the success of projects. However, there is little research that shows how effectively projects are managed in a business organisational context like Eskom. My Study aims to partly fill this gap by presenting results from a case study and surveys of Eskom as an organisation practising project management. It also aims to investigate the effectiveness of project management in terms of Eskom Divisional structures, technical competency, Eskom Project leadership ability and the characteristics of an effective project manager. In managing projects, it is significant to know how to handle both the tools and the people and to achieve a balance between the two. Experience, especially in the management of change was perceived to be a significant factor in project success
APA, Harvard, Vancouver, ISO, and other styles
9

Labuschagne, Carin. "Sustainable project life cycle management : criteria for the South African process industry." Pretoria : [s.n.], 2002. http://upetd.up.ac.za/thesis/available/etd-10112005-083255.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Palmer, Erika. "Developing and Integrating Life Cycle Management Methods in Project Management Systems : Case: Faveo Prosjektledelse AS." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for energi- og prosessteknikk, 2013. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-24796.

Full text
Abstract:
The goal of this master thesis was to develop life cycle management tools and methods for use in project management. The research questions concerned the practical integration of these tools in a system dynamics perspective and the contribution this can have in creating value. First an introduction of the research area is given, followed by the methods employed, an exploration of the theoretical foundation, a theoretical analysis of how life cycle management in project management can be used, an explanation of the tool that was developed, an explanation of the application of the tool on a project and how it contributes to value creation, and finally a discussion is given followed by a conclusion. The Sustainable Project Life Cycle Management (SPLCM) Guide is the tangible result of this thesis, and it is an easy to use tool that project managers at Faveo (and in other companies) can use in their projects to mitigate the environmental and social impacts of their projects. Using this guide will change the Faveo system (illustrated in the specialization project) and allows the project managers to have a direct relationship with the community and the environment in the life cycle of their projects. The SPLCM Guide not only has the potential to reduce the impact the projects at Faveo have on society and the environment, but it can also create value for the project owners and for Faveo itself. Sustainable value creation meets the needs of stakeholders while creating value for the company, and the SPLCM Guide (in conjunction with other initiatives) can realize this for Faveo.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software Project Management Life Cycle"

1

Hoffman, Mark. Application development: Managing the project life cycle. Carlsbad, CA: Midrange Computing, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Haug, Michael, Eric W. Olsen, Gilles Vallet, and Olivier Bécart, eds. Software Management Approaches: Project Management, Estimation, and Life Cycle Support. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Babcock, Ray. Industry best practices for the software development life cycle: Final report. [Helena, Mont.]: Montana Dept. of Transportation, 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kuhrmann, Marco. Software life cycle: Management und Entwicklung. Frankfurt, M: Entwickler.press, 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Program management: A life cycle approach. Boca Raton, FL: CRC Press, 2013.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

The management of construction: A project life cycle approach. Boston, MA: Butterworth-Heinemann, 2003.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Kovalenko, Vladimir. Design of information systems. ru: INFRA-M Academic Publishing LLC., 2020. http://dx.doi.org/10.12737/987869.

Full text
Abstract:
The tutorial discusses the design features of information systems (is) involved in the implementation of CALS technologies: MRP/MRPII/ERP systems, e-Commerce systems (B2B), supply chain management (SCM), customer relationship management (CRM), and decision support systems (OLAP). The issues of choosing the design technology, software tools for project development, building functional and information models in the environment of Business Studio, MS Visio, Elma, AllFusion Modeling Suite and Oracle Designer 10g, as well as the development of technical and operational documentation are highlighted. The characteristics of CASE technologies and their implementation in the Oracle Designer 10g environment are considered. A comparative analysis of the standards of the organization of the life cycle of creating and using IP, practical recommendations for the development of standard profiles, examples of the development of an IP project based on a cascading model of the life cycle, including using a process approach in the management and automation of processes. The models of the client — server architecture and the structure of cloud computing are considered. Modern approaches to the selection of ready-made is and their implementation in automated enterprises are studied in detail. Meets the requirements of the Federal state educational standards of higher education of the latest generation. It is intended for students (bachelors and specialists) and masters of higher educational institutions studying in the direction of "Applied Informatics". It is also recommended for teachers and specialists working in the field of information technology.
APA, Harvard, Vancouver, ISO, and other styles
8

United States. Dept. of the Interior. Office of the Secretary. A Project manager's guide to application systems life cycle management. [Washington, D.C.]: The Department, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Managing the system life cycle. 2nd ed. Englewood Cliffs, N.J: Yourdon Press, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Stein, R. Timothy. The computer system risk management and validation life cycle. Chico, CA: Paton Press, 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software Project Management Life Cycle"

1

Haug, M., and E. W. Olsen. "The EUREX Project." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 17–24. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Haug, Michael, Eric W. Olsen, Gilles Vallet, and Olivier Bécart. "Software Process Improvement A European View." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 3–15. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Haug, Michael, Eric W. Olsen, Gilles Vallet, and Olivier Bécart. "Summaries of PIE Reports." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 145–216. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Haug, M., and E. W. Olsen. "The EUREX Taxonomy." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 25–30. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Vallet, G. "Perspectives." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 33–54. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bécart, O. "Resources for Practitioners." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 55–75. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Bécart, O. "Experience Reports." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 77–112. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Bécart, O. "Lessons from the EUREX Workshops." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 113–31. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Vallet, G. "Significant Results." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 133–39. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Haug, Michael, Eric W. Olsen, Gilles Vallet, and Olivier Bécart. "Table of PIEs." In Software Management Approaches: Project Management, Estimation, and Life Cycle Support, 143–44. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56616-5_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software Project Management Life Cycle"

1

"The NASA information system life-cycle transition management within the software project." In Digital Avionics Systems Conference. Reston, Virigina: American Institute of Aeronautics and Astronautics, 1988. http://dx.doi.org/10.2514/6.1988-3947.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

MILLIGAN, JAMES. "Software Life Cycle Support Environment (SLCSE) - Project ManagementSystem (SPMS): Not just another project management tool." In 8th Computing in Aerospace Conference. Reston, Virigina: American Institute of Aeronautics and Astronautics, 1991. http://dx.doi.org/10.2514/6.1991-3942.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gayraud, Stéphane, and Riti Singh. "A Techno-Economic Computational Tool for Power Generation Project Assessments and Life Cycle Risk Management." In ASME 1997 Turbo Asia Conference. American Society of Mechanical Engineers, 1997. http://dx.doi.org/10.1115/97-aa-130.

Full text
Abstract:
The growing desire for sponsors of power generation projects to share risk with the lenders has promoted the use of computational tools, simulating and evaluating from a techno-economic viewpoint long-term, high-risk projects. Such models need to include reliable engine diagnostics, life-cycle costing and risk analysis technique. This paper presents a Decision Support System (DSS) for the assessment of power generation projects using industrial gas turbines. The software, programmed in Visual Basic in Excel, runs the object-oriented software Pythia which has been developed by the Department of Propulsion, Power and Automotive Engineering at Cranfield University and which can perform gas turbine performance calculations, including off-design conditions, with or without degradation effects providing thus very reliable engine diagnostics. Moreover, a life cycle cost, assessed using manufacturer methodology for instance, can be integrated into the economic model. The degree of uncertainty relating to technical and economic factors is assessed using a normal distribution and the level of risk can then be evaluated using a risk analysis technique based upon the Monte Carlo Method. The DSS therefore provides charts and result tables to support the decision making, allowing the user to achieve a good level of confidence using new techniques of risk management.
APA, Harvard, Vancouver, ISO, and other styles
4

Tubaishat, Abdallah. "IT Systems Development: An IS Curricula Course that Combines Best Practices of Project Management and Software Engineering." In InSITE 2009: Informing Science + IT Education Conference. Informing Science Institute, 2009. http://dx.doi.org/10.28945/3315.

Full text
Abstract:
Most computing programs still devote little time to software life cycle development, software processes, quality issues, team skills, and other areas of software engineering essential to effective commercial software development. A teaching project was developed and implemented by accommodating knowledge and practices that are applicable to most projects in the area of project management and in the area of software development to Information Systems (IS) students. This approach is relevant to IS model curricula and is in accordance with IS2002.10 project management and practice course guidelines. The rationale behind this approach is to overcome the relative lack of experience of IS students in many aspects of project management and software development by introducing them how to plan, organize, and control software development projects, and to help students strengthen good software engineering practices prior to entering IT industry and become more efficient. We present results of a case study based on a survey conducted in an IT Systems Development course. Survey results show that including topics on project management and Software Engineering best practices lab into an IT Systems Development course helped students (a) deal with non-technical issues of software projects, (b) develop their ability to communicate clearly with team members, and (c) overcome their lack of experience in many aspects of project management and software development.
APA, Harvard, Vancouver, ISO, and other styles
5

Hai¨k, P., K. Fessart, E. Remy, and J. Lonchampt. "Overview of EDF Life Cycle Management and Nuclear Asset Management Methodology and Tools." In 16th International Conference on Nuclear Engineering. ASMEDC, 2008. http://dx.doi.org/10.1115/icone16-48911.

Full text
Abstract:
The long term management of a production asset raises several major issues among which rank the technical management of the plant, its economics and the fleet level perspective one has to adopt. Decision makers are therefore faced with the need to define long term policies (up to the end of asset operation) which take into account multiple criteria including safety (which is paramount) and performance. In this context, EDF “PWR Durability I & II” research projects have consecutively been launched, since 2001, at EDF - Research & Development in order to develop methods and tools for EDF fleet. The aim of this paper is to summarize and analyze the research work that has been performed by EDF - R&D (in the field of decision making for nuclear power plant maintenance and operation) during the past seven year, in order to characterize the issues that have been or could be addressed with the developed methodology and tools. As a result, in this paper, we first remind the reader of the EDF overall methodology for asset management and its adaptations to plant-level life cycle management and to fleet-level component major replacement or capital investment management. We then focus on the three software tools that implement this methodology in order to allow decision makers, in several different contexts (life-cycle management, plant level operation and maintenance optimization, major component replacement ...) to define, evaluate and analyze long term plant operation and maintenance policies, major component replacement policies and capital investment strategies. We also show how the methodology and the software tools were used, from 2003 to 2007, on several pilot case studies. Examples of technical and economic results obtained for two pilot case studies (one at the plant level, the other at the fleet level) are described as well as the kinds of conclusions one can draw from them in order to help decision makers evaluate and analyze long term asset management strategies or compare different plants. We also analyze the added value of probabilistic evaluations and of our “rolling-up” process that allows to take into account interactions between the components of the plant or between the plants. Finally, we propose a classification of issues that can be addressed with our methodology and tools and introduce some perspectives for our future work.
APA, Harvard, Vancouver, ISO, and other styles
6

Narasimhan, Lakshmi, Di Wu, and Narinder Gill. "Meta-Analysis of Clinical Cardiovascular Data towards Evidential Reasoning for Cardiovascular Life Cycle Management." In InSITE 2007: Informing Science + IT Education Conference. Informing Science Institute, 2007. http://dx.doi.org/10.28945/3147.

Full text
Abstract:
The cardiovascular disease is one of the serious and life-threatening diseases in the developed world. One aspect of medical treatment is using drugs with blood pressure reducing or cholesterol lowering functions. Importantly, such treatment needs to be individually tailored and is significantly correlated to the particular conditions of individual patients. However, such pathologies and mechanisms are still only under investigation. Several novel and unique computational methods, called meta-analyses techniques, for formatting and analyzing a wide variety of cardiac datasets are discussed in this paper with the aim to building cardiovascular database and related patient life-cycle management services. In this paper we also present an overview of a second order inference engine underlying the meta-analyses, which yields evidenced-based reasoning that is more likely to better assist decision-making on the effectiveness of cardiovascular treatment than what is available currently. Furthermore, the software architecture and other details of such a medical informatics system tailored to cardiovascular disease are also described. Research and development work on this project yields itself to application to many other areas, such as disease control and prevention in Epidemiology, and dietics. The system can therefore make a profound impact to medical informatics.
APA, Harvard, Vancouver, ISO, and other styles
7

Rivero, Luis, Italo Silva, Pedro Cutrim, Anselmo Paiva, Milton Oliveira, Erika Alves, Geraldo Braz Junior, and Domingos Dias. "Implementando o Gitflow para Gerencia de Configuração em um Projeto de Desenvolvimento de Software Ágil: Um Relato de Experiência." In Computer on the Beach. São José: Universidade do Vale do Itajaí, 2021. http://dx.doi.org/10.14210/cotb.v12.p178-185.

Full text
Abstract:
In software engineering, Software Configuration Management is a set of support activities that allows for the orderly absorption of changes inherent to software development. For that, organization models for code versioning like Gitflow have been proposed. In Gitflow, two fixed branches (master and develop) are used to store the project history and be the starting point for changes. Despite the popularity of Gitflow for being considered a simple workflow, there are few: (a) reports of its use in practice and / or (b) documentation on how to deploy it in a real environment. This paper presents the process of adapting Gitflow and creating rules for its application in a real software development project. This adaptation took into account the opinions of managers and developers of a team of approximately 30 people within an agile Scrum life cycle. As a result, definitions and documents were generated to keep track of development, in addition to defining the necessary steps for its application considering the development process adopted by the team.
APA, Harvard, Vancouver, ISO, and other styles
8

Marinina, Oksana. "COST MANAGEMENT OF MINING PROJECT LIFE CYCLE." In 17th International Multidisciplinary Scientific GeoConference SGEM2017. Stef92 Technology, 2017. http://dx.doi.org/10.5593/sgem2017/13/s03.023.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Willar, Debby, Estrellita V. Y. Waney, Daisy D. G. Pangemanan, Rudolf E. Mait, and Jemmy J. Rangan. "Quality Management of Infrastructure Project Life-Cycle." In 2018 International Conference on Applied Science and Technology (iCAST). IEEE, 2018. http://dx.doi.org/10.1109/icast1.2018.8751555.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Gritskevich, Olga. "Special Aspects Of Innovative Project Life Cycle Management." In Trends and Innovations in Economic Studies, Science on Baikal Session. European Publisher, 2020. http://dx.doi.org/10.15405/epsbs.2020.12.38.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software Project Management Life Cycle"

1

Radhakrishnan, N., Bobby Hughey, and Warren Bennett. Study on the Availability of Commercial Software for the Corps' Life Cycle Project Management (LCPM). Fort Belvoir, VA: Defense Technical Information Center, April 1989. http://dx.doi.org/10.21236/ada208254.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Anderson, William, Ed Morris, Dennis Smith, and Mary C. Ward. COTS and Reusable Software Management Planning: A Template for Life-Cycle Management. Fort Belvoir, VA: Defense Technical Information Center, October 2007. http://dx.doi.org/10.21236/ada473976.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Piercy, Candice, Safra Altman, Todd Swannack, Carra Carrillo, Emily Russ, and John Winkelman. Expert elicitation workshop for planning wetland and reef natural and nature-based features (NNBF) futures. Engineer Research and Development Center (U.S.), August 2021. http://dx.doi.org/10.21079/11681/41665.

Full text
Abstract:
This special report discusses the outcomes of a September 2019 workshop intended to identify barriers to the consideration and implementation of natural and nature-based features (NNBF) in US Army Corps of Engineers (USACE) civil works projects. A total of 23 participants representing seven USACE districts, the US Army Engineer Research and Development Center (ERDC), and the University of California–Santa Cruz met at USACE’s South Atlantic Division Headquarters in Atlanta, Georgia, to discuss how to facilitate the implementation of NNBF into USACE project planning for wetlands and reefs using six categories: (1) site characterization, (2) engineering and design analysis, (3) life-cycle analysis, (4) economic analysis, (5) construction analysis, (6) and operation and maintenance (and monitoring). The workshop identified seven future directions in wetland and reef NNBF research and development: • Synthesize existing literature and analysis of existing projects to better define failure modes. • Determine trigger points that lead to loss of feature function. • Identify performance factors with respect to coastal storm risk management (CSRM) performance as well as ecological performance. • Focus additional research into cobenefits of NNBF. • Quantify the economic life-cycle costs of a project. • Improve technology transfer with regards to NNBF research and topics.
APA, Harvard, Vancouver, ISO, and other styles
4

Melby, Jeffrey, Thomas Massey, Fatima Diop, Himangshu Das, Norberto Nadal-Caraballo, Victor Gonzalez, Mary Bryant, et al. Coastal Texas Protection and Restoration Feasibility Study : Coastal Texas flood risk assessment : hydrodynamic response and beach morphology. Engineer Research and Development Center (U.S.), July 2021. http://dx.doi.org/10.21079/11681/41051.

Full text
Abstract:
The US Army Corps of Engineers, Galveston District, is executing the Coastal Texas Protection and Restoration Feasibility Study coastal storm risk management (CSRM) project for the region. The project is currently in the feasibility phase. The primary goal is to develop CSRM measures that maximize national net economic development benefits. This report documents the coastal storm water level and wave hazard, including sea level rise, for a variety of flood risk management alternatives. Four beach restoration alternatives for Galveston Island and Bolivar peninsula were evaluated. Suites of synthetic tropical and historical non-tropical storms were developed and modeled. The CSTORM coupled surge-and-wave modeling system was used to accurately characterize storm circulation, water level, and wave hazards using new model meshes developed from high-resolution land and sub-aqueous surveys for with- and without-project scenarios. Beach morphology stochastic response was modeled with a Monte Carlo life-cycle simulation approach using the CSHORE morphological evolution numerical model embedded in the StormSim stochastic modeling system. Morphological and hydrodynamic response were primarily characterized with probability distributions of the number of rehabilitations and overflow.
APA, Harvard, Vancouver, ISO, and other styles
5

Berkowitz, Jacob, Nathan Beane, Kevin Philley, Nia Hurst, and Jacob Jung. An assessment of long-term, multipurpose ecosystem functions and engineering benefits derived from historical dredged sediment beneficial use projects. Engineer Research and Development Center (U.S.), August 2021. http://dx.doi.org/10.21079/11681/41382.

Full text
Abstract:
The beneficial use of dredged materials improves environmental outcomes while maximizing navigation benefits and minimizing costs, in accordance with the principles of the Engineering With Nature® (EWN) initiative. Yet, few studies document the long-term benefits of innovative dredged material management strategies or conduct comprehensive life-cycle analysis because of a combination of (1) short monitoring time frames and (2) the paucity of constructed projects that have reached ecological maturity. In response, we conducted an ecological functional and engineering benefit assessment of six historic (>40 years old) dredged material–supported habitat improvement projects where initial postconstruction beneficial use monitoring data was available. Conditions at natural reference locations were also documented to facilitate a comparison between natural and engineered landscape features. Results indicate the projects examined provide valuable habitat for a variety of species in addition to yielding a number of engineering (for example, shoreline protection) and other (for example, carbon storage) benefits. Our findings also suggest establishment of ecological success criteria should not overemphasize replicating reference conditions but remain focused on achieving specific ecological functions (that is, habitat and biogeochemical cycling) and engineering benefits (that is, storm surge reduction, navigation channel maintenance) achievable through project design and operational management.
APA, Harvard, Vancouver, ISO, and other styles
6

Innovative Solutions to Human-Wildlife Conflicts: National Wildlife Research Center Accomplishments, 2014. U.S. Department of Agriculture, Animal and Plant Health Inspection Service, June 2015. http://dx.doi.org/10.32747/2015.7206799.aphis.

Full text
Abstract:
The National Wildlife Research Center (NWRC) is the research arm of Wildlife Services (WS), a program within the U.S. Department of Agriculture’s (USDA) Animal and Plant Health Inspection Service (APHIS). NWRC’s researchers are dedicated to finding biologically sound, practical, and effective solutions to resolving wildlife damage management issues. They seek these solutions using a multiyear, multidisciplinary project management system. NWRC identifies and prioritizes projects based on feedback from WS program leaders, managers, and stakeholders concerning their most pressing wildlife damage management needs. During 2014, five research projects reached the end of their 5-year life cycle. At the final project reviews, project leaders and their staff presented and discussed each project’s accomplishments, challenges, and findings.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software Project Management Life Cycle' for particular source types:
Journal articles Dissertations / Theses Books
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!

To the bibliography