undefined | unit 6 software quality project monitoring and control

UNIT 6

Software Quality & Project Monitoring and Control

Q1) What is Project Monitoring and Control?

A1)

Monitoring and Controlling are processes needed to track, review, and regulate the progress and performance of the project. It also identifies any areas where changes to the project management method are required and initiates the required changes.

The Monitoring & Controlling process group includes eleven processes, which areMonitor and control project work: The generic step under which all other monitoring and controlling activities fall under.

Perform integrated change control: The functions involved in making changes to the project plan. When changes to the schedule, cost, or any other area of the project management plan are necessary, the program is changed and re-approved by the project sponsor.

Validate scope: The activities involved with gaining approval of the project's deliverables.

Control scope: Ensuring that the scope of the project does not change and that unauthorized activities are not performed as part of the plan (scope creep).

Control schedule: The functions involved with ensuring the project work is performed according to the schedule, and that project deadlines are met.

Control costs: The tasks involved with ensuring the project costs stay within the approved budget.

Control quality: Ensuring that the quality of the project?s deliverables is to the standard defined in the project management plan.

Control communications: Providing for the communication needs of each project stakeholder.

Control Risks: Safeguarding the project from unexpected events that negatively impact the project's budget, schedule, stakeholder needs, or any other project success criteria.

Control procurements: Ensuring the project's subcontractors and vendors meet the project goals.

Control stakeholder engagement: The tasks involved with ensuring that all of the project's stakeholders are left satisfied with the project work.

Q2) What do you understand by Software Quality Management System?

A2)

Software Quality Management System is a quality management system is the principal methods used by organizations to provide that the products they develop have the desired quality.

A quality system subsists of the following:

Managerial Structure and Individual Responsibilities: A quality system is the responsibility of the organization as a whole. However, every organization has a sever quality department to perform various quality system activities. The quality system of an arrangement should have the support of the top management. Without help for the quality system at a high level in a company, some members of staff will take the quality system seriously.

Quality System Activities: The quality system activities encompass the following:

Auditing of projects

Review of the quality system

Development of standards, methods, and guidelines, etc.

Production of documents for the top management summarizing the effectiveness of the quality system in the organization.

Q3) ExplainSix Sigma model?

A3)

Statistical Quality Control: Six Sigma is derived from the Greek Letter σ (Sigma) from the Greek alphabet, which is used to denote Standard Deviation in statistics. Standard Deviation is used to measure variance, which is an essential tool for measuring non-conformance as far as the quality of output is concerned.

Methodical Approach: The Six Sigma is not a merely quality improvement strategy in theory, as it features a well defined systematic approach of application in DMAIC and DMADV which can be used to improve the quality of production. DMAIC is an acronym for Design-Measure- Analyze-Improve-Control. The alternative method DMADV stands for Design-Measure- Analyze-Design-Verify.

Fact and Data-Based Approach: The statistical and methodical aspect of Six Sigma shows the scientific basis of the technique. This accentuates essential elements of the Six Sigma that is a fact and data-based.

Project and Objective-Based Focus: The Six Sigma process is implemented for an organization's project tailored to its specification and requirements. The process is flexed to suits the requirements and conditions in which the projects are operating to get the best results.

Customer Focus: The customer focus is fundamental to the Six Sigma approach. The quality improvement and control standards are based on specific customer requirements.

Teamwork Approach to Quality Management: The Six Sigma process requires organizations to get organized when it comes to controlling and improving quality. Six Sigma involving a lot of training depending on the role of an individual in the Quality Management team.

Q4) Explain about project management?

A4)

A project manager is a character who has the overall responsibility for the planning, design, execution, monitoring, controlling and closure of a project. A project manager represents an essential role in the achievement of the projects.

A project manager is a character who is responsible for giving decisions, both large and small projects. The project manager is used to manage the risk and minimize uncertainty. Every decision the project manager makes must directly profit their project.

Role of a Project Manager:

1. Leader

A project manager must lead his team and should provide them direction to make them understand what is expected from all of them.

2. Medium:

The Project manager is a medium between his clients and his team. He must coordinate and transfer all the appropriate information from the clients to his team and report to the senior management.

3. Mentor:

He should be there to guide his team at each step and make sure that the team has an attachment. He provides a recommendation to his team and points them in the right direction.

Responsibilities of a Project Manager:

Managing risks and issues.

Create the project team and assigns tasks to several team members.

Activity planning and sequencing.

Monitoring and reporting progress.

Modifies the project plan to deal with the situation.

Q5) Explain Project management and planning activities?

A5)

1. Project Planning: It is a set of multiple processes, or we can say that it a task that performed before the construction of the product starts.

2. Scope Management: It describes the scope of the project. Scope management is important because it clearly defines what would do and what would not. Scope Management create the project to contain restricted and quantitative tasks, which may merely be documented and successively avoids price and time overrun.

3. Estimation management: Apart from cost estimation because whenever we start to develop software, but we also figure out their size(line of code), efforts, time as well as cost.

For size, then Line of code depends upon user or software requirement.

Foreffort, if size of the software is estimated,based on the size one can estimate how big team required to produce the software.

For time, when size and efforts are estimated, the time required to develop the software can easily determine.

Cost estimation includes all the elements such as:

Size of software

Quality

Hardware

Communication

Training

Additional Software and tools

Skilled manpower

4. Scheduling Management: Scheduling Management in software refers to all the activities to complete in the specified order and within time slotted to each activity. Project managers define multiple tasks and arrange them keeping various factors in mind.

For scheduling, it is compulsory -

Find out multiple tasks and correlate them.

Divide time into units.

Assign the respective number of work-units for every job.

Calculate the total time from start to finish.

Break down the project into modules.

5. Project Resource Management: In software Development, all the elements are referred to as resources for the project. It can be a human resource, productive tools, and libraries.

Resource management includes:

Create a project team and assign responsibilities to every team member

Developing a resource plan is derived from the project plan.

Adjustment of resources.

6. Project Risk Management: Risk management consists of all the activities like identification, analyzing and preparing the plan for predictable and unpredictable risk in the project.

Several points show the risks in the project:

The Experienced team leaves the project, and the new team joins it.

Changes in requirement.

Change in technologies and the environment.

Market competition.

7. Project Communication Management: Communication is an essential factor in the success of the project. It is a bridge between client, organization, team members and as well as other stakeholders of the project such as hardware suppliers.

From the planning to closure, communication plays a vital role. In all the phases, communication must be clear and understood. Miscommunication can create a big blunder in the project.

8. Project Configuration Management: Configuration management is about to control the changes in software like requirements, design, and development of the product.

Q6) Write short note on ISO certification ?

A6)

Process of ISO certification

Application: Once an organization decided to go for ISO certification, it applies to the registrar for registration.

Pre-Assessment: During this stage, the registrar makes a rough assessment of the organization.

Document review and Adequacy of Audit: During this stage, the registrar reviews the document submitted by the organization and suggest an improvement.

Compliance Audit: During this stage, the registrar checks whether the organization has compiled the suggestion made by it during the review or not.

Registration: The Registrar awards the ISO certification after the successful completion of all the phases.

Continued Inspection: The registrar continued to monitor the organization time by time.

Q7) Define Defect Prevention?

A7)

Solution:Defect Prevention is much more efficient and effective in reducing the number of defects and also is very cost effective to fix the defects found during the early stage of the software process. Most of the organizations conduct Defect Discovery, Defect Removal and then Process Improvement which is collectively known as a Defect Management Process.

The Defect Management Process should be followed during the overall software development process and not only for specific testing or development activities.

If a defect found in the testing phase then a question can be raised that if the defect is caught in this phase then what about the other defects that are alive in the system which may cause system failure if it occurs and is not yet discovered.

So all processes like review process, static testing, inspection, etc., need to strengthen and everyone in the project should be serious about the process and contribute wherever necessary. Senior management in the organization should also understand and support the defect management process.

Testing approaches, review process etc., should choose based on the project objective or organizational process.

Defect management life cycle

Defect Life Cycle Flowchart

Q8) What Is Defect Analysis?

A8)

In the software development process, a bug or defect has a life cycle. The defect needs to go through the life cycle in order to be fixed and closed.

The name of the defect status may vary depending on the tools that are used (QC, JIRA, etc.) and the process followed in the organisation. A defect can be defined as the abnormal behaviour of the software. The life cycle analysis starts when the defect is found and ends when the defect is closed after ensuring it is not reproduced.

The goal of a defect analysis is to determine the root cause of the defect. The root cause can be defined as the causal or contributing factors that, if corrected, would prevent the recurrence of the identified problem. The ‘factor’ that caused the defect should be permanently eliminated through process improvement. To do this, a standard defect analysis process is followed.

Standard Defect Analysis Process

Identifying the problem,

Containing and analysing the problem,

Defining the root cause,

Defining and implementing the actions required to eliminate the root cause, andValidating that the corrective action prevented recurrence of the problem.

A defect analysis can save time and money. some of the benefits of defect analysis are:

Problems are not repeated, thereby reducing rework, retesting, re-inspections, and costs that are incurred due to poor quality software,

Problems are prevented in other areas,

Communication improves between groups,

Process cycle times improve (because there are fewer rework loops), and

Secure long-term company performance and profitability.

Incremental Software Improvements

Defect analysis is a cooperative effort between the different consultants involved in a project. Their knowledge about the processes is put to use to help in defect analysis and can be considered as part of the model for experience-driven incremental software process improvement.

Sign Up