Scribd
Upload
95 views9 pages

Software Project Management & Quality Assurance

The document discusses software project management and quality assurance. It contains questions and answers related to topics like team organization models, software configuration management, software development life cycles, Gantt charts, and risk management activities.

Uploaded by

evryones_scribd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
95 views9 pages

Software Project Management & Quality Assurance

The document discusses software project management and quality assurance. It contains questions and answers related to topics like team organization models, software configuration management, software development life cycles, Gantt charts, and risk management activities.

Uploaded by

evryones_scribd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 9

ASSIGNMENT

-------------------------------------------------------------------------------------------------Software Project Management & Quality Assurance


( BC0054 )
.................
Qn1.) Explain Centralized-Control and Decentralized-Control Team Organization
Ans:The organizing function of management deals with devising roles for individuals and
assigning responsibility for accomplishing project goals. The aim of an organization is to
facilitate cooperation towards a common goal.
Centralized-Control Team organization.
It is a standard management technique in well understood disciplines.In this mode of
organization, several workers report to a supervisor who directly controls their tasks and
is responsible for their performance.centralized control is based on a hierarchical
organizational structure in which number of supervisor report to a "second-level"
manager and so on up the chain, to the president of the enterprise.
In general, centralized control works well with tasks which are simple enough that the
one person responsible for control of the project can grasp the problem and it's solution.
One way to centralize the control of a software development team is through chiefprogrammer team. In this kind of organization,one engineer, known as the chiefprogrammer is responsible for the design and all the technical details of the project.
Chief manager
specialist
Librarian

programmer
Fig: chief programmer team:

The success of the chief programmer team clearly depends on the skill,ability
of the chief programmer, the size and complexity of the problem.

Decentralized-Control Team Organization

In a decentralized-control team organization, decisions are made by


consensus, and all work is considered group.Team members review each
other's work and are responsible as a group for what every member
produces.
Fig shows the patterns of control and communication among team members
in a decentralized-control organization.

fig (a) Management structure.


Fig(b) Patterns of communication.
The ring like management structure is intended to show the lack of hierarchy
and that all team members are at same level.
The decentralized-control organization is more suited for long-term projects,
because the amount of intra-group communication that it encourages leads
to a longer development time, presumably accompanied by lower life cycle
costs.
The proponents of this kind of team organization claim that it is more
appropriate foe less understood and more complicated problems, since a
group can invent better solutions than a single individual can.

******************************************

Qn2.)
What is Software Configuration Management? Explain its Goals.
Ans:-

Software configuration management (SCM) is an important element of software quality


assurance.Its primary responsibility is the control of change.SCM is a set of activities to
control change by identifying the products that are likely to change,establish relationships
among them,defining mechanisms for managing different versions of these work
products,controlling the changes imposed and auditing and reporting on the changes
made.
In short, SCM is a methodology to control and manage a software development project.
Goals of Software configuration management (SCM)
Configuration identification - What code are we working with?
Configuration control - Controlling the release of a product and the
changes.
Status accounting - Recording and reporting the status of components.
Review-Ensuring completeness and consistency among components.
Build management- managing the process and tools used for builds.
Process management-Ensuring adherence to the organization's
development process.
Environment management-Managing the software and hardware that
host our system.
Teamwork - Facilitate team interactions related to the process.
Defect tracking- making sure every defect has traceability back to the
source.
The configuration is organized in a manner that enables orderly control of
change.The software configuration is composed of a set of interrelated
objects and also software configuration items that are produced as a result of
some engineering activity. Software configuration management is an
umbrella activity that is applied throughout the software process. Because
change can occur at any time,SCM activities are developed to identify
change,control change,ensure that change is being properly implemented
and report changes to other who may interested.SCM is responsible for the
identification identification of individual SCIs and various versions of the
software,the auditing of the software configuration to ensure that it has been
properly developed, and the reporting of all changes applied to the
configuration.

******************************************
Qn3.)
Explain Waterfall life cycle model.
Ans:-

The "waterfall model", documented in 1970 by Royce was the first publicly documented
life cycle model. The model was developed to help cope with the increasing complexity
of aerospace products. The waterfall model followed a documentation driven paradigm.
This is the least flexible and most obsolete of the life cycle models.well suited
to projects that have low risk in the areas of user interface and performance
requirements, but high risk in budget and schedule predictability and
control.This model is the base model for all the other models.
This model involves the following phases:

Analysis or requirements

Design

Implementation

Testing or verification

Maintenance
The waterfall model is one time model. It is not evolutionary model.
To follow the waterfall model, one proceeds from one phase to the next in a
purely sequential manner.
For example, one first completes "requirements specification"- they set in
store
the requirements of the software. When the requirements are fully
completed,one proceeds to design. The software in question is designed and
a "blueprint" is drawn for implementer( coder) to follow-this design should be
plan for implementing the requirements given.

When the design is fully completed, an implementation of that design is


made by coders. Towards the later stages of this implementation phase,
disparate software components produced by the different teams are

integrated.
After the implementation and integration phases are complete, the software
product is tested and debugged,any faults introduced in earlier phases are
removed here. Then the product is installed, and later maintained to
introduce new functionality and remove bugs.
Thus the waterfall model maintains that one should move to the new phase
only when the preceding phase is completed and perfected. Phase of
development in the waterfall model are thus discrete, and there is no
jumping back and forth or overlap between them.

******************************************

Qn4.)
What is Gantt Chart? What are its advantages?
Ans:-

Project planning is a part of project management, which relates to the use of schedules
such as Gantt charts to plan and subsequently report progress within the project
environment. Project planning is the key to completing project successfully. Creating a
project plan is the first thing we need to do when undertaking any kind of project.
What is Gantt chart:
Gantt chart is project planning technique used for several purposes, including
scheduling,Budgeting,Resource planning. It was initially developed by
Henry Laurence Gantt, A.B., M.E ( 1861-23 November 1919). He was a mechanical
engineer and management consultant. These Gantt charts were employed on major
infrastructure projects including the Hoover Dam and interstate highway system and still
are an important tool in project management.
Advantages of Gantt chart:

Graphical representation of a schedule.


Clear and easy communication.
Resource allocation.
Tracking of the schedule.
Providing a history of the project.
Plan staffing
It can illustrate the relationship between work activities.

Once a Gantt schedule has been established for a project, progress should be periodically
plotted against the baseline schedule. If different functional areas are involved in a
project,each area may need it's own detailed schedules to support the project master
schedule. In such cases it is important that working schedules be linked to a common
master schedule in a way that they can be easily updated. Gantt chart is derived
automatically from the PERT chart.
Gantt chart helps in planning the utilization of resources,while the PERT chart is better
for monitoring the timely progress of activities.
******************************************

Qn5.)
List the various activities under the risk management.
Ans:-

Risk is the possibility of the loss. Software Risk management is a software engineering
practice with processes, and tools for managing risks in a project.
It provides a disciplined environment for pro-active decision making ti assess
continuously what can go wrong, determine what risks are important to deal with and
implement actions to deal with those risks.
Various activities under the risk management: Planing how risk management will be held in the particular project. Plan should
include risk management tasks,responsibilities,activities and budget.
Assigning a risk officer- a team member other than a project manager who is
responsible for foreseeing potential project problems. Typical characteristic of risk
officer is a healthy skepticism.
Maintaining live project risk database. Each risk should have these attributes,opening
date,title,short description,probability and importance. Optionally a risk have an
assigned person responsible for its resolution and a date by which the risk must be
resolved.
Creating anonymous risk reporting channel. Each team member should have
possibility to report risk that he foresees in the project.
Preparing mitigation plans for risks that are chosen to be mitigated. The purpose of
the mitigation plan is to describe how is this particular risk will be handledwhat,when,by who and how will it be done to avoid it or minimize consequences if it
becomes a liability.
Summarizing planned and faced risks, effectiveness of mitigation activities and effort
spent for the risk management.
There are two stages in the process of Project Risk Management, Risk Assessment and
Risk control. Risk assessment may be the most important step in the risk management
process, and may also be the most difficult and prone to error. Once risks have been
identified and assessed, the steps to properly deal with them are much more
systematically.
******************************************

Qn6.)
Define
a) Software assurance

(b) Software Engineering.

(c) Software Management (d) Software reviews


(e) Code Reviews
Ans:Software assurance :Software assurance is the planned and systematic set of activities that ensures that
software processes and products conform to requirements,standards and procedures.
From the above definition,"processes" includes all of the activities involved in
designing,developing,enhancing and maintaining software. " products" include the
software,associated data,it's documentation and all supporting and reporting paperwork.
Software Engineering :Software engineering is the set of activities that analyzes requirements, develops
designs,writes code, and structures database.
In other words, software Engineering is an engineering discipline whose focus is the costeffective development of high-quality software systems. It is a discipline that integrates,
methods and tools for the development of computer software.
Software Management :Software management is the set of activities involved in planning,controlling and
directing the software project. These all activities are involved in the software life cycle.
Software Reviews :Software reviews are one of the most important SQA activities.
Reviews serve as filters throughout all software engineering activities, removing errors
while they are relatively inexpensive to find and correct.

Code Reviews :Code reviews involve two or more developers reading code independently and then
meeting the author to discuss any findings. Again, this relies heavily on the experience of
the reviewer knowing what to look in a review.

Software assurance forms part of the triad of these all activities, along with software
management and software engineering that taken together, can provide a successful
software development,enhancement or maintenance activity.

******************************************
------------------------------------------------- END

You might also like