SOFTWARE PROJECT MANAGEMENT
Matter: Software metology.Professor: Javier Daza Piragauta. Students: Laura Ximena Lopez Cardenas. Carlos Julio Mape Sanabria.
Table of Contents
1. Introduction
2. What is managing
3. Differences between Planning and Managing Software
4. Software Architecture
5. The 4 P's: • Personnel • Product • Process • Project
6. Estimation of Software Projects.
7. Management, control and quality assurance of the Software.
8. Maturity Model
Introduction
In this work we will know the procedure for software project management, in order to carry out a project correctly
• What is managing
Software project management refers to the branch of project management dedicated to the planning, scheduling, resource allocation, execution, monitoring, and delivery of software and web projects.
Project management in software engineering differs from traditional project management in that software projects have a unique lifecycle process that requires several rounds of testing, updates, and customer feedback. Most IT-related projects are managed in the Agile style, to keep up with the increasingly fast pace of business and iterate based on feedback from customers and stakeholders.
• Differences between Planning and Managing Software
The main difference is that by managing you plan, while managing you put in place the planning done during the administration.
• Software Architecture
They are patterns or guidelines that help build a program (application). These patterns allow you to have a guide for developers, analysts and all related positions to achieve compliance with the requirements of the application.
Software architecture refers to the structure and relationship between the different parts of a software and its external visible properties.
In short, a software architecture is composed of more data architectures articulated with each other. This is why it encompasses so many elements and tools to be carried out.
Its main objective is to offer a certain quality to the data management system, based on its performance, time savings, its availability and usability, the ability to modify and adapt to the new needs of the system, among other quality attributes.
• The 4 P's: • Personnel • Product • Process • Project
The 4 P's
In all types of projects there is a need to acquire an adequate project management, to carry out this, you must select the right personnel, determine the best process according to the problem you want to solve, in addition to excellent planning with the aim of obtaining a product on time and quality.
• The 4 P's: • Personnel • Product • Process • Project
• Personal
Are the main authors in a project; it is made up of architects, developers, database engineers, test engineers and management staff [2]. The selection, recruitment and training of personnel should be taken into account along with the work and development of the team culture and design of the organization
• The 4 P's: • Personnel • Product • Process • Project
• Product Products are called those components that are created during the life of the project such as models, codes, executables, documentation, UML diagrams, user interface sketches, prototypes, etc. The product is a produced item, which is quantifiable and which can be a finished element.
y.
• The 4 P's: • Personnel • Product • Process • Project
• Process
A process is the set of activities that are performed to create the product (template to create the project). The process is defined in terms of workflow (set of activities), workers and artifacts are identified, and UML activity diagrams are used to describe workflows
• The 4 P's: • Personnel • Product • Process • Project
• Project
The project is an organizational element that manages the development of activities for the implementation of a product or service taking into account the limited resources available, including people, time, costs, etc., to achieve the planned objectives.
• Estimation of Software Projects.
Estimating in software projects is an extremely complex task, which requires, among other things, having detailed information on the project or projects to be estimated, carrying out a first planning of the project and knowing the available resources. Even if they have all the means and the necessary information, the estimates of software projects usually err, predicting lower results than those that finally occur.
• Management, control and quality assurance of the Software.
Software management
Software control
Software quality control system. It is the structure that organizes evaluations, inspections, audits and reviews that ensure that the assigned responsibilities are met, resources are used efficiently and the fulfillment of the objectives of the product is achieved.
Quality management through software refers to the systematic balance that is maintained between the set of planned and regulated activities, as well as the satisfaction generated in customers who place their trust in a certain product or service that meets the requirements that the market demands.
• Management, control and quality assurance of the Software.
Software Warranty
Software quality
Quality assurance is the set of tasks that serve as support to provide adequate security where each of the processes created is permanently optimized, trying to ensure that the products meet the requirements and specifications of the product or software [9], it is also necessary that they meet the ideal conditions for their use. The person in charge of comparing the quality of the product with the policies adopted and the measures established of non-conformity when an inconsistency is detected is known as quality control.
The quality of the software as it is a methodology that helps to collect evidence of the use of a product or software, to guarantee this quality guidelines are used to measure the control of the quality of this, in addition to prolonging the life of the software. The correlation between audit occupancy, quality assurance, quality control and software testing is often complicated.
• Maturity Model Maturity models are an evolution of methodologies to manage the quality of the organization. They were initially conceived for the software industry, but currently their area of application is very diverse.
Conclusions
In conclusion, we realize that there are several steps for the management of a project, therefore to be able to carry out a project we must know each step in order to carry it out.
https://www.wrike.com/es/project-management-guide/faq/que-es-la-gestion-de-proyectos-de-software/
https://www.informaticaparatunegocio.com/blog/la-diferencia-administrar-gestionar/#:~:text=La%20diferencia%20principal%20es%20que,planificaci%C3%B3n%20hecha%20durante%20la%20administraci%C3%B3n.
https://www.capterra.es/blog/695/diferencia-software-gestion-de-proyectos-y-gestion-de-tareas
https://keepcoding.io/blog/que-es-arquitectura-software/
file:///C:/Users/laura/Downloads/7608-Text%20del%20art%C3%ADculo-60873-1-10-20171105%20(1).pdf
http://scielo.sld.cu/scielo.php?script=sci_arttext&pid=S2227-18992013000300003#:~:text=La%20estimaci%C3%B3n%20en%20proyectos%20de,y%20conocer%20los%20recursos%20disponibles.
https://www.itop.es/blog/item/que-es-un-software-de-gestion-de-calidad.html#:~:text=La%20gesti%C3%B3n%20de%20calidad%20mediante,cumple%20los%20requerimientos%20que%20el
https://www.ecured.cu/Sistema_de_control_de_calidad_de_software#:~:text=Es%20la%20estructura%20que%20organiza,de%20los%20objetivos%20del%20producto.
http://scielo.sld.cu/scielo.php?script=sci_arttext&pid=S1815-59362014000200004#:~:text=Los%20modelos%20de%20madurez%20constituyen,de%20aplicaci%C3%B3n%20es%20muy%20diversa.
¡Gracias!
SOFTWARE PROJECT MANAGEMENT
Laura Ximena Lopez Cardenas
Created on August 14, 2022
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Practical Video
View
Akihabara Video
View
Essential Video
View
HALLOWEEN VIDEO MOBILE
View
Halloween Illustrated Video
View
Halloween video
View
Birthday Party Invitation
Explore all templates
Transcript
SOFTWARE PROJECT MANAGEMENT
Matter: Software metology.Professor: Javier Daza Piragauta. Students: Laura Ximena Lopez Cardenas. Carlos Julio Mape Sanabria.
Table of Contents
1. Introduction 2. What is managing 3. Differences between Planning and Managing Software 4. Software Architecture 5. The 4 P's: • Personnel • Product • Process • Project 6. Estimation of Software Projects. 7. Management, control and quality assurance of the Software. 8. Maturity Model
Introduction
In this work we will know the procedure for software project management, in order to carry out a project correctly
• What is managing
Software project management refers to the branch of project management dedicated to the planning, scheduling, resource allocation, execution, monitoring, and delivery of software and web projects. Project management in software engineering differs from traditional project management in that software projects have a unique lifecycle process that requires several rounds of testing, updates, and customer feedback. Most IT-related projects are managed in the Agile style, to keep up with the increasingly fast pace of business and iterate based on feedback from customers and stakeholders.
• Differences between Planning and Managing Software
The main difference is that by managing you plan, while managing you put in place the planning done during the administration.
• Software Architecture
They are patterns or guidelines that help build a program (application). These patterns allow you to have a guide for developers, analysts and all related positions to achieve compliance with the requirements of the application. Software architecture refers to the structure and relationship between the different parts of a software and its external visible properties. In short, a software architecture is composed of more data architectures articulated with each other. This is why it encompasses so many elements and tools to be carried out. Its main objective is to offer a certain quality to the data management system, based on its performance, time savings, its availability and usability, the ability to modify and adapt to the new needs of the system, among other quality attributes.
• The 4 P's: • Personnel • Product • Process • Project
The 4 P's In all types of projects there is a need to acquire an adequate project management, to carry out this, you must select the right personnel, determine the best process according to the problem you want to solve, in addition to excellent planning with the aim of obtaining a product on time and quality.
• The 4 P's: • Personnel • Product • Process • Project
• Personal Are the main authors in a project; it is made up of architects, developers, database engineers, test engineers and management staff [2]. The selection, recruitment and training of personnel should be taken into account along with the work and development of the team culture and design of the organization
• The 4 P's: • Personnel • Product • Process • Project
• Product Products are called those components that are created during the life of the project such as models, codes, executables, documentation, UML diagrams, user interface sketches, prototypes, etc. The product is a produced item, which is quantifiable and which can be a finished element. y.
• The 4 P's: • Personnel • Product • Process • Project
• Process A process is the set of activities that are performed to create the product (template to create the project). The process is defined in terms of workflow (set of activities), workers and artifacts are identified, and UML activity diagrams are used to describe workflows
• The 4 P's: • Personnel • Product • Process • Project
• Project The project is an organizational element that manages the development of activities for the implementation of a product or service taking into account the limited resources available, including people, time, costs, etc., to achieve the planned objectives.
• Estimation of Software Projects.
Estimating in software projects is an extremely complex task, which requires, among other things, having detailed information on the project or projects to be estimated, carrying out a first planning of the project and knowing the available resources. Even if they have all the means and the necessary information, the estimates of software projects usually err, predicting lower results than those that finally occur.
• Management, control and quality assurance of the Software.
Software management
Software control
Software quality control system. It is the structure that organizes evaluations, inspections, audits and reviews that ensure that the assigned responsibilities are met, resources are used efficiently and the fulfillment of the objectives of the product is achieved.
Quality management through software refers to the systematic balance that is maintained between the set of planned and regulated activities, as well as the satisfaction generated in customers who place their trust in a certain product or service that meets the requirements that the market demands.
• Management, control and quality assurance of the Software.
Software Warranty
Software quality
Quality assurance is the set of tasks that serve as support to provide adequate security where each of the processes created is permanently optimized, trying to ensure that the products meet the requirements and specifications of the product or software [9], it is also necessary that they meet the ideal conditions for their use. The person in charge of comparing the quality of the product with the policies adopted and the measures established of non-conformity when an inconsistency is detected is known as quality control.
The quality of the software as it is a methodology that helps to collect evidence of the use of a product or software, to guarantee this quality guidelines are used to measure the control of the quality of this, in addition to prolonging the life of the software. The correlation between audit occupancy, quality assurance, quality control and software testing is often complicated.
• Maturity Model Maturity models are an evolution of methodologies to manage the quality of the organization. They were initially conceived for the software industry, but currently their area of application is very diverse.
Conclusions In conclusion, we realize that there are several steps for the management of a project, therefore to be able to carry out a project we must know each step in order to carry it out.
https://www.wrike.com/es/project-management-guide/faq/que-es-la-gestion-de-proyectos-de-software/ https://www.informaticaparatunegocio.com/blog/la-diferencia-administrar-gestionar/#:~:text=La%20diferencia%20principal%20es%20que,planificaci%C3%B3n%20hecha%20durante%20la%20administraci%C3%B3n. https://www.capterra.es/blog/695/diferencia-software-gestion-de-proyectos-y-gestion-de-tareas https://keepcoding.io/blog/que-es-arquitectura-software/ file:///C:/Users/laura/Downloads/7608-Text%20del%20art%C3%ADculo-60873-1-10-20171105%20(1).pdf http://scielo.sld.cu/scielo.php?script=sci_arttext&pid=S2227-18992013000300003#:~:text=La%20estimaci%C3%B3n%20en%20proyectos%20de,y%20conocer%20los%20recursos%20disponibles. https://www.itop.es/blog/item/que-es-un-software-de-gestion-de-calidad.html#:~:text=La%20gesti%C3%B3n%20de%20calidad%20mediante,cumple%20los%20requerimientos%20que%20el https://www.ecured.cu/Sistema_de_control_de_calidad_de_software#:~:text=Es%20la%20estructura%20que%20organiza,de%20los%20objetivos%20del%20producto. http://scielo.sld.cu/scielo.php?script=sci_arttext&pid=S1815-59362014000200004#:~:text=Los%20modelos%20de%20madurez%20constituyen,de%20aplicaci%C3%B3n%20es%20muy%20diversa.
¡Gracias!