Software project management unit 2 notes

Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Software Engineering. More related articles in Software Engineering. We use cookies to ensure you have the best browsing experience on our website. Start Your Coding Journey Now! WorkFlows of the process: Software process workflows, Inter trans workflows. Iterative Process Planning: Work breakdown structures, planning guidelines, cost and schedule estimating, Interaction planning process, Pragmatic planning.

Project Control and Process instrumentation: The server care Metrics, Management indicators, quality indicators, life cycle expectations pragmatic Software Metrics, Metrics automation.

Tailoring the Process: Process discriminants, Example. Follow us on Facebook and Support us with your Like. How useful was this post? Average rating 4. It is there for the software production but involves no concrete activity that has any direction connection with software production; rather it is a set of multiple processes, which facilitates software production.

Project planning may include the following:. It defines the scope of project; this includes all the activities, process need to be done in order to make a deliverable software product. Scope management is essential because it creates boundaries of the project by clearly defining what would be done in the project and what would not be done.

This makes project to contain limited and quantifiable tasks, which can easily be documented and in turn avoids cost and time overrun. For an effective management accurate estimation of various measures is a must. With correct estimation managers can manage and control the project more efficiently and effectively.

Lines of code depend upon coding practices and Function points vary according to the user or software requirement. The managers estimate efforts in terms of personnel requirement and man-hour required to produce the software. For effort estimation software size should be known.

Once size and efforts are estimated, the time required to produce the software can be estimated. Efforts required is segregated into sub categories as per the requirement specifications and interdependency of various components of software. The tasks are scheduled on day-to-day basis or in calendar months. The sum of time required to complete all tasks in hours or days is the total time invested to complete the project. This might be considered as the most difficult of all because it depends on more elements than any of the previous ones.

For estimating project cost, it is required to consider -. We discussed various parameters involving project estimation such as size, effort, time and cost. This technique uses empirically derived formulae to make estimation. This model is made by Lawrence H.

Putnam model maps time and efforts required with software size. It divides the software product into three categories of software: organic, semi-detached and embedded. Project Scheduling in a project refers to roadmap of all activities to be done with specified order and within time slot allotted to each activity. Project managers tend to define various tasks, and project milestones and arrange them keeping various factors in mind. They look for tasks lie in critical path in the schedule, which are necessary to complete in specific manner because of task interdependency and strictly within the time allocated.

Arrangement of tasks which lies out of critical path are less likely to impact over all schedule of the project. For scheduling a project, it is necessary to -. All elements used to develop a software product may be assumed as resource for that project. This may include human resource, productive tools and software libraries. The resources are available in limited quantity and stay in the organization as a pool of assets.

The shortage of resources hampers the development of project and it can lag behind the schedule. Allocating extra resources increases development cost in the end. It is therefore necessary to estimate and allocate adequate resources for the project.

Risk management involves all activities pertaining to identification, analyzing and making provision for predictable and non-predictable risks in the project.

Risk may include the following:. Execution needs monitoring in order to check whether everything is going according to the plan.