UML Introduction dependencies, it’s a Vite project. If you see "next", it’s a Next.js project..pptx

If you see "react-scripts" in the dependencies, it’s likely a Create React App project.
If you see "vite" in the dependencies, it’s a Vite project.
If you see "next", it’s a Next.js project.

1. Software project management 1

2. Software project management Outlines : What is Project What is Project Management What is Software Project What is Software Project Management Project Manager Responsibilities of Project Manager 2

3. 3

4. 4

5. 5

6. 6

7. 7 Project manager is the driver of the software project management

8. Responsibilities of Project Manager Project Planning Scope Management Project Estimation Software Size Effort Time Cost estimation Resources Management Risk Management 8

9. 9

10. 10

11. Software project management View of Project Management (PM) … A software engineer manages project day-to-day activities, such as planning, monitoring and controlling technical tasks. Project managers plan, monitor, and control the work of a team of software engineers. Senior managers coordinate the interface between the business and the software professionals. 11

12. Software project management View of Project Management (PM) … Quality product The project plan is right means that deliver a high-quality product on time and within budget. However, a project manager does it right when he encourages software people to work together as an effective team, focusing their attention on customer needs and product quality. Project Management (PM) steps Understand the four P’s: People. Product. Process. Project. 12

13. Software project management People People must be organized to perform software work effectively. The software process (and every software project) is populated by players Senior managers who define the business issues that often have significant influence on the project. Project (technical) managers who must plan, motivate, organize, and control the practitioners who do software work. 13

14. Software project management People … Practitioners who deliver the technical skills that are necessary to engineer a product or application. Customers who specify the requirements for the software to be engineered and other stakeholders who have a peripheral interest in the outcome. End-users who interact with the software once it is released for production use. 14

15. Software project management People … Team Leaders Project management is a people-intensive activity. So, the team leader should has these skills: Motivation . The ability to encourage (by “push or pull”) technical people to produce to their best ability. Organization . The ability to mould existing processes (or invent new ones) that will enable the initial concept to be translated into a final product. Ideas or innovation . The ability to encourage people to create and feel creative even when they must work within bounds established for a particular software product or application. 15

16. Software project management People … The Software Team The organization of the people directly involved in a new software project is within the project manager's purview. “ Mantei ” suggests three generic team organizations: Democratic decentralized (DD). This software engineering team has no permanent leader. Decisions on problems and approach are made by group consensus. Communication among team members is horizontal. 16

17. Software project management People … The Software Team … Controlled decentralized (CD). This software engineering team has a defined leader who coordinates specific tasks and secondary leaders that have responsibility for subtasks. Problem solving remains a group activity, but implementation of solutions is partitioned among subgroups by the team leader. Communication among subgroups and individuals is horizontal. Vertical communication along the control hierarchy also occurs. Controlled Centralized (CC). Top-level problem solving and internal team coordination are managed by a team leader. Communication between the leader and team members is vertical.. 17

18. Software project management Product Communication with the customer must occur so that product scope and requirements are understood. The first software project management activity is the determination of software scope: Context . How does the software to be built fit into a larger system, product, or business context and what constraints are imposed as a result of the context? Information objectives . What customer-visible data objects are produced as output from the software? What data objects are required for input? Function and performance . What function does the software perform to transform input data into output? Are any special performance characteristics to be addressed? 18

19. Software project management Product … Problem Decomposition Sometimes called partitioning or problem elaboration, is an activity that sits at the core of software requirements analysis. Problem decomposition is applied in two major areas: (1) The functionality that must be delivered. (2) The process that will be used to deliver it. 19