Assignment

No:-4

CAP-412
Software
Project
Management
Submitted to: Submitted by:
Respected Ankur Singh
Sandeep Sharma Sir Roll no:-
Re3801a29

CAP 412: SOFTWARE PROJECT MANAGEMENT

HOMEWORK - 4
Part A
Q 1: Elaborate some visualizing ways of
presenting the collected data for the completion
of projects?
Ans
Studying a problem through the use of statistical data analysis usually involves four basic
steps.

1. Defining the problem

2. Collecting the data
3. Analyzing the data
4. Reporting the results

Designing ways to collect data is an important job in statistical data analysis.

Two important aspects of a statistical study are:

Statistical inference is refer to extending your knowledge obtain from a random

sample from a population to the whole population. This is known in mathematics
as an Inductive Reasoning. That is, knowledge of whole from a particular. Its
main application is in hypotheses testing about a given population.
The purpose of statistical inference is to obtain information about a population
form information contained in a sample. It is just not feasible to test the entire
population, so a sample is the only realistic way to obtain data because of the
time and cost constraints. Data can be either quantitative or qualitative.
Qualitative data are labels or names used to identify an attribute of each
element. Quantitative data are always numeric and indicate either how much or
how many.
Data can be collected from existing sources or obtained through observation and
experimental studies designed to obtain new data. In an experimental study, the
variable of interest is identified. Then one or more factors in the study are
controlled so that data can be obtained about how the factors influence the
variables. In observational studies, no attempt is made to control or influence
the variables of interest. A survey is perhaps the most common type of
observational study.

Q 2: Elaborate the areas where the following

terms are implemented:-
(a)Cost monitoring
During the execution of a project, procedures for project control and record
keeping become indispensable tools to managers and other participants in the
construction process. These tools serve the dual purpose of recording the
financial transactions that occur as well as giving managers an indication of the
progress and problems associated with a project. The problems of project control
are aptly summed up in an old definition of a project as "any collection of
vaguely related activities that are ninety percent complete, over budget and
late. The task of project control systems is to give a fair indication of the
existence and the extent of such problems.

(b)Change control
Change control is a systematic approach to managing all changes made to a
product or system. The purpose is to ensure that no unnecessary changes are
made, that all changes are documented, that services are not unnecessarily
disrupted and that resources are used efficiently. Within information technology
(IT), change control is a component of change management.

Q 3: How would the project manager measures

the quality of the project?
Ans3
This helps us determine if we are going to meet our goal. Perhaps there are other indicators
that we should be measuring that might suggest that the schedule is at risk. Components that
make up the schedule are:
 • Work estimates
• External dependencies (such as equipment orders)
• Speed of risk and issue resolution

Metrics to address the components include:

• Accuracy of work effort estimates for tasks completed

• Mean time to resolving issues
• Mean time of open issues
• Longest current open issue

Some practices we rely on to address quality:

• Automated integration tests.

• Unit Tests.
• Acceptance tests for every story (we use user stories for requirements)
• Feature Level Tests (testing groups of stories)
• Code reviews (all our code is reviewed using a tool)
• Risk tracking
• Manual testing for each story, immediately after it is implemented.
• Automated performance tests.

Part B
Q 1: Compare and contrast the product and
process quality management?
Ans
Product Controls
Quality systems that focus on sorting and isolating defective product are
generally called product controls. Because the process generates defective
product, efforts are made to identify, sort, and segregate the defective product.
Often, the defects are made throughout the process but only culled at the end.
For example, a manufacturer sells a sterile original equipment manufacturer
(OEM) part. The part is made from a metal press, where it is etched with a lot
number, cleaned, packaged, and steam sterilized. Prior to shipment, samples of
the sealed product are inspected. If the metal press caused hairline cracks to
form in the part, then this may be detected only at the very end of the process.
All of the cleaning, labelling, packaging, and sterilization are wasted on
essentially defective product. Because defective product is definitely present,
product controls require 100% inspection or multiple 100% inspections to
guarantee product quality. Statistical sampling plans are not useful because they
presume an acceptable defect level of a few percent, which is generally not
acceptable for Food and Drug Administration (FDA) regulated products.

Process Controls
Process controls are quality systems based on preventing defects by controlling
and monitoring manufacturing processes. Because no defective product is
produced, these processes can achieve much higher quality levels than a system
based on product controls. Processes must be rigorously characterized,
understood, and controlled for this system to be effective. For example, a
pharmaceutical manufacturer typically combines a number of drug components
into a heated batch reactor, mixes them thoroughly, dries them in a granulator,
and compresses them into tablets. Process controls for this operation would
include specifications on batch size, mixing speed, drying temperature, mixing
temperature, drying time, mixing time, and speed at which pellets are
compressed. These are distinct from product specifications in that they will be
different depending on the equipment used.

Q2: Suppose you are the project manager ,

write the steps how you implement Software
quality plan.
Ans
The objective of the Software Quality Program Plan is to ensure
that developing software is evaluated to determine that the
desired quality has been achieved. This is performed by creating
a process to provide independent assessment of whether the
desired quality has been achieved.

The plan shall be applicable for all software products and

processes declared for use on a specific software development
project.

• SOFTWARE QUALITY PROGRAM PLAN FOR THE name of project.;

• Document identifier including issue;
• Date the document was formally approved;
• The organization responsible for 'preparing' the document;
• The organization requiring the document preparation;
• A distribution statement;
 • Total number of pages comprising the document;
• Any classification distribution requirements necessary.

SQP procedures, tools, and records.

Procedures used by SQP are as follows:

• product reviews (internal, end-of-phase)

• in-process reviews (peer reviews)
• management review
• process audits (internal)
• Code walkthrough
• Static code analysis (Risk Class 1)
• FEMA (Risk Class 1)
• etc.

Tools to be used in the SQP are:

• Name, the identification number, version, and development status of the

tools necessary to complete the Software Quality Program.