how to become good software house

7
ASSIGNMENT NO 1 HOW TO IMPROVE SOFTWARE QUALITYASSURANCE IN DEVELOPING COUNTRIES MAY 29, 2016 ABDUL RAFAY (BSCS F12 0110 Submitted to: SIR ASAD UR REHMAN

Upload: abdul-rafay

Post on 12-Apr-2017

33 views

Category:

Software


0 download

TRANSCRIPT

Page 1: How to become good software house

ASSIGNMENT NO 1

HOW TO IMPROVE SOFTWARE QUALITYASSURANCE IN DEVELOPING

COUNTRIES

MAY 29, 2016 ABDUL RAFAY (BSCS F12 0110

Submitted to: SIR ASAD UR REHMAN

Page 2: How to become good software house

ASSIGNMENT NO 1

1. Main points of this SQA research paper

Software Quality is an important factor because it gives satisfaction to

the customer as well as the stakeholders that they have made something

good. Software quality is important in both developed and under

developing countries.

To give your competitors in IT market company should make high

quality products because once the software is delivered then it all

depends on customer how they will give you the feedback, if the

software has errors the reputation is in danger.

IT organizations should follow some standards, procedures, method and

practices that make them away from errors.

The standards and procedures include CMMI (Capability Maturity

Model Integration) and ISO (International Standard Organization) but it

is difficult and costly for small Software Development Organizations to

follow the standards.

Management plays a huge role in the SQA. So it is the prime

responsibility of the team managers

i. To facilitate the team members

ii. Provide them the good working environment and

iii. Arrange some formal training courses.

Quality plan:

is the most important in any quality improvement activity. SQA team

managers

are responsible and accountable to develop quality plan and also

implement the plan. They are also responsible for quality

measurement, quality improvement and configuration management.

Quality Plan includes the inspection of the problems. The methodology

used for inspection was dividing and conquer. It was time consuming

task, but ensures problems detection

Inspection at the end of the project but it can be done at any phase of the

project and reveal the errors from the code.

Page 3: How to become good software house

ASSIGNMENT NO 1

Peer review and user involvement is also an important phase which help

in getting feedback of the code.

**Peer review is a type of software review in which a work

product (document, code, or other) is examined by its author and

one or more colleagues, in order to evaluate its technical content

and quality. **

PARNAS MODEL:

i. No formal need for the training of inspection.

o No investment by company

o Less budget consumed

ii. Helps in finding the errors in the code as well as ambiguities in

development phase.

DAVID MODEL:

i. Quality of this free software is high because of the open

development models used in the development process.

Surveys

Page 4: How to become good software house

ASSIGNMENT NO 1

MAIN ISSUES ADDRESSED

Time

Budget

Less use of quality standards

Lack of specialists

Project durations

Compromise on quality due to less profit

Developer’s attitude

Team formation for requirements gathering

Politics

CRITICAL ISSUES:

i. 23% Telecom companies

ii. 37% Software consultant companies

iii. 40 % Software development companies

Are affected by the above mentioned issues

LACK OF SPECIALIST:

o Developer is also fulfilling the responsibilities of tester which is

one of the main reasons of lack of software quality.

o Reduce quality and maintainability.

o Just testing the functionality reduces the quality of software.

LACK OF CONFORMANCE TO STANDARDS:

o Small organizations just develop following any standards to save

the cost but that can lead to failures which can cost even more

than that.

DEVELOPER’S ATTITUDE:

i. Developers mostly do not show cooperating behaviour-SQA

EMPLOYERS

ii. Developer does not show interest in the problem areas mentioned by the

SQA

UNREALISTIC DEADLINES:

Page 5: How to become good software house

ASSIGNMENT NO 1

i. QA team has very tight schedule to deliver the project. Half of the total

time is mostly spent on domain understanding and functional

requirements

ii. Lack in domain knowledge then it will affect quality quite badly.

iii. 60% projects fail due to unrealistic deadlines

TEAM FORMATION AND COMPROMISE ON QUALITY:

i. No SQA representor in the requirements team.

ii. QA team leads also compromise on quality of local projects because

they consider Pakistani clients technically less strong as compared to

foreign clients and consider that local clients mostly does not go for

third party testing but foreign clients hire a third party to evaluate the

quality of the projects.

iii. Mangers give less time to the testing and QA activities of the local

projects.

POLITICS:

i. Leg pulling

ii. team leads with better Public Relations get highly paid projects which

affect the experience and the benefits for their team members.

RESOLVING ISSUES

DEPLOYING CMMI MODEL:

i. Surely improves the quality of software products as well as

reputation

ii. improves the reputation of the software organizations because mostly

customers inquire about CMMI certification and CMMI level.

90%

92%

94%

96%

98%

Time Budget Professionals Environment

Project Completion Success Rate

Page 6: How to become good software house

ASSIGNMENT NO 1

iii. Highly recommended to follow CMMI standards.

CERTIFIED AND SPECIALLIZED SQA TEAM

i. Proper SQA team or at least full time tester because only a tester can

find the errors and can match the specifications with the user demands.

ii. SQA team is to make sure that all the procedures

iii. Develop professionalism through training and mentoring in employees

Developers Attitude:

i. Managers should make sure to develop a good relationship between

development team and SQA team.

ii. Workshops regarding to improve their abilities and approach towards

the different team members.

iii. Monthly meetings

NO COMPROMISE ON QUALITY

i. Team leads should make sure to give proper time to every project

regardless of the profit margin

ii. You can’t handle the quality issue created because of profit issues.

AVOID INTERNAL POLITICS

i. it is the responsibility of the managers to make sure that politics should

not affect the quality of the software

1. What their research shows?

o Effects of Non Specialists on Project Completion Rate

808 non-specialist

99% Specialist (know exactly how to tackle different problems

in the project life cycle)

o Effects of Certified Team on Project Completion Rate

98% certified team (Certifications give more exposure to the

employees towards new technologies)

85 % Non-certified

o Effects of Domain Knowledge and Politics on Project Completion

Rate:

97% Domain Knowledge and no Politics

Page 7: How to become good software house

ASSIGNMENT NO 1

85% No Domain Knowledge and Politics

2. LEARNINGS:

o Specialist, certified teams and group who have domain knowledge

will lead Software house to a respectable position in IT department.

o CMMI OR ISO standards, better developers’ attitude, no internal

politics will lead you on the top if u maintain them through out every

software project

o By following different rules to manage all the issues we can manage a

software house more handsomely and in an effective manner.

o SQA deals planning, strategy, testing execution and tools and should

know how to to establish time tables and agree on a Quality Assurance

Plan for the various applications implementation.