software engineering -test 1-(part 3)
Project planning involves 4 steps:
1. Perform estimation of
• The work effort
• The schedule
• The needed resources
2. Clearly define and establish measurable “goals” (realistic and measurable goals) for the project
(deliverables).
3. Determine the project resource allocations of
• People
• Process
• Tools and Facilities
4. Identify and analyze the project risks.
RISK MANAGEMENT
1.RISK IDENTIFICATION
2.RISK PRIORITIZATION
3. RISK MITIGATION
ORGANIZING
Once a project plan has been formulated or even before it has been completed, the organizing activities
must be initiated. For example, as soon as we have the estimated resources planned, hiring and
placement may begin
MONITORING
Once the project is organized and set into motion, there still needs to be regular tracking to
ensure that it is headed in the right direction. (Projects cannot be left to successful completion
by itself)
Three main components of project monitoring:
1. Collection of project information (Status)
2. Analysis and evaluation of collected information
3. Presentation and communication of the project status
Trend Analysis
Trend Analysis is the process of monitoring and identifying trends in project data.
Regression Analysis
Regression analysis can help identify which independent variables significantly impact the
dependent variable. For example, it can determine which marketing channels or advertising
strategies influence sales most, allowing businesses to allocate resources more effectively.
ADJUSTING
It is highly unlikely that a software project progresses with no problem.
• If the monitoring process indicates any need for adjustment, then the project management team must take timely actions.
• As soon as the project status suggests potential problem, we must not be afraid to make changes.
• Three main areas of adjustments are (or are combinations of):
• Resources
• Schedule
• Project content
SOME PROJECT MANAGEMENT TECHNIQUES
1) Project Effort Estimation (PO)
2) Work Breakdown Structure (PO)
3) Project Status Tracking With Earned Value (MA)
4) Developing Measurements And Metrics (PM).
COCOMO ESTIMATION MODELS (Cont.)
Organic Project
Semidetached Project
Embedded Project (Difficult)
Organic Project
Small & simple software projects handled by a small team with good domain
knowledge and few rigid requirements.
Example: Small data processing or Inventory management system.
Semidetached Project
Intermediate (in terms of complexity) project, where the team having mixed
experience (both experience & inexperience resources) to deals with rigid/nonrigid requirements.
Example: Database design or OS development.
Semidetached Project
Intermediate (in terms of complexity) project, where the team having mixed
experience (both experience & inexperience resources) to deals with rigid/nonrigid requirements.
Example: Database design or OS development.
Embedded Project (Difficult)
This project having a high level of complexity with a large team size by
considering all sets of parameters (software, hardware and operational).
Example: Banking software or Traffic light control software.