Explore topic-wise InterviewSolutions in .

Pareto PRINCIPLE is also known as 80/20 principle. It is a management TOOL to track problem tracking effectively. This principle says that 20% of the problems lead to 80% of other problems. Hence, in order to concentrating on solving 80% of the problems rather, one can CONCENTRATE to solve 20 % of the problems which saves lot of troubles. The ANALYSIS and concentration is done for only 20% of the vital problems. In a PROJECT the vital problems are the first 10% and the last 10% .

Pareto Principle is also known as 80/20 principle. It is a management tool to track problem tracking effectively. This principle says that 20% of the problems lead to 80% of other problems. Hence, in order to concentrating on solving 80% of the problems rather, one can concentrate to solve 20 % of the problems which saves lot of troubles. The analysis and concentration is done for only 20% of the vital problems. In a project the vital problems are the first 10% and the last 10% .

It is one way of tackling PROBLEM in management. It says 20% of the PROBLEMS lead to other 80% of the problems. According to this PRINCIPLE, we should focus on 20% of the problem. In any software project FIRST 10% and last 10% from the vital part of the project.

It is one way of tackling problem in management. It says 20% of the problems lead to other 80% of the problems. According to this principle, we should focus on 20% of the problem. In any software project first 10% and last 10% from the vital part of the project.

Casual Analysis and Resolution is the PROCESS of analyzing

• DEFECTS, problems and good practices/positive triggers in a project.
• ROOT cause of the same.
• Identity the respective corrective and preventive actions.
• Tracking these tasks to closure.

The IDENTIFICATION of the root causes scientifically and carrying out their corrective and preventive actions is the advantage of CAR. At the initial stage, all phase and at the end stage of the project, the CAR is needed to be performed on a monthly basis. CAR can be done by using ‘fishbone’ diagram.

Casual Analysis and Resolution is the process of analyzing

The identification of the root causes scientifically and carrying out their corrective and preventive actions is the advantage of CAR. At the initial stage, all phase and at the end stage of the project, the CAR is needed to be performed on a monthly basis. CAR can be done by using ‘fishbone’ diagram.

To analyze possible DECISIONS by using a formal evaluation process which identifies the alternatives against established criteria is DONE by the DAR. For example a project is to use a third party tools and will not depend on only one TOOL but evaluate by using three to four tools. In this process certain alternatives are AVAILABLE in case of problems.

To analyze possible decisions by using a formal evaluation process which identifies the alternatives against established criteria is done by the DAR. For example a project is to use a third party tools and will not depend on only one tool but evaluate by using three to four tools. In this process certain alternatives are available in case of problems.

CAR – Casual analysis and RESOLUTION:

CAR identifies problem and perform a root cause analysis of the same. CAR NEEDS to be performed at every project phase. FISHBONE diagram is one of the WAYS to perform CAR.

DAR- Decision Analysis and Resolution:

This is to analyze possible decisions using a FORMAL evaluation process that identifies alternatives against current resources.

CAR – Casual analysis and resolution:

CAR identifies problem and perform a root cause analysis of the same. CAR needs to be performed at every project phase. Fishbone diagram is one of the ways to perform CAR.

DAR- Decision Analysis and Resolution:

This is to analyze possible decisions using a formal evaluation process that identifies alternatives against current resources.

Waterfall Model: The waterfall model is a software development process which follows a sequential APPROACH. This approach steadily flows downwards like a waterfall which INCLUDES the phases of conception, initiation, analysis, design, construction, testing and maintenance.

Spiral Model: The spiral model is one of the software development processes which combines the design and PROTOTYPING -in -stages together to gain the advantage of top-down and bottom-up approaches.

Build and Fix model: This model is one of the worst model for project development. The project is built without specifications and lacks design steps. Essentially, the project is developed, tested, modified as many times as possible. This process continues until the client’s satisfaction is attained. The cost is greater compared to other models. The software engineers are discouraged to use this model.

Rapid prototyping Model: To determine and identify the design flaws and obtaining FEEDBACK during design process is done by using rapid prototyping model. Product designers and engineers are allowed to view their designs look and function in real WORLD situations by using Rapid Prototyping Model.

Incremental Model: The evolution of waterfall model is incremental model. The integration testing, product design and development is done as a series of incremental builds. A popular software evolution model used by many software companies. Incremental model is suitable and applicable where software requirements are well defined, but their implementation may be delayed; and the basic software functionality are required early.

Waterfall Model: The waterfall model is a software development process which follows a sequential approach. This approach steadily flows downwards like a waterfall which includes the phases of conception, initiation, analysis, design, construction, testing and maintenance.

Spiral Model: The spiral model is one of the software development processes which combines the design and prototyping -in -stages together to gain the advantage of top-down and bottom-up approaches.

Build and Fix model: This model is one of the worst model for project development. The project is built without specifications and lacks design steps. Essentially, the project is developed, tested, modified as many times as possible. This process continues until the client’s satisfaction is attained. The cost is greater compared to other models. The software engineers are discouraged to use this model.

Rapid prototyping Model: To determine and identify the design flaws and obtaining feedback during design process is done by using rapid prototyping model. Product designers and engineers are allowed to view their designs look and function in real world situations by using Rapid Prototyping Model.

Incremental Model: The evolution of waterfall model is incremental model. The integration testing, product design and development is done as a series of incremental builds. A popular software evolution model used by many software companies. Incremental model is suitable and applicable where software requirements are well defined, but their implementation may be delayed; and the basic software functionality are required early.

Waterfall model:

This is the oldest model. It represents sequence of stages; output of one stage becomes input of others.

SPIRAL Model:

This is improved VERSION of waterfall model. Here we have scope to reiterate and go BACK to the earlier stages number of times as project progresses.

Build and fix model:

This is a risky and most unorganized model. In this, developers KEEP writing code until the customer is happy.

Rapid Prototype Model:

In this model, we develop prototype which acts like a final PRODUCT. Once prototype is approved, then the actual development starts.

Incremental Model:

In this model, the product is divided into sections and each section of the product are created and tested separately.

Waterfall model:

This is the oldest model. It represents sequence of stages; output of one stage becomes input of others.

Spiral Model:

This is improved version of waterfall model. Here we have scope to reiterate and go back to the earlier stages number of times as project progresses.

Build and fix model:

This is a risky and most unorganized model. In this, developers keep writing code until the customer is happy.

Rapid Prototype Model:

In this model, we develop prototype which acts like a final product. Once prototype is approved, then the actual development starts.

Incremental Model:

In this model, the product is divided into sections and each section of the product are created and tested separately.

The DIFFERENT phases of software projects are follows:

Initiation:

Preparing scope document, requirement DOCUMENTS, Estimation chart, project PLAN and proposal documents.

Planning:

Designing test plan and coding STANDARDS.

Execution:

Writing code.

Controlling:

Testing and establishing change management procedure.

Closure:

CLOSING project and move it to maintenance mode.

The different phases of software projects are follows:

Initiation:

Preparing scope document, requirement documents, Estimation chart, project plan and proposal documents.

Planning:

Designing test plan and coding standards.

Execution:

Writing code.

Controlling:

Testing and establishing change management procedure.

Closure:

Closing project and move it to maintenance mode.

SDLC - STANDS for Software Development Life Cycle.

It can be divided in to 7 PHASES they are:

1. Preliminary INVESTIGATION (Feasibility Study).
2. Requirement ANALYSIS (Analysis).
3. Design of the SYSTEM.
4. Software Construction.
5. System Testing.
6. System Implementation.
7. System Maintenance.

SDLC - stands for Software Development Life Cycle.

It can be divided in to 7 phases they are:

PROJECT MANAGEMENT INSTITUTE (PMI).

Project Management Institute (PMI).

The DUAL Vee Model, like the V-Model is a SYSTEMS DEVELOPMENT model designed to simplify the understanding of the complexity associated with developing systems. In systems engineering it is used to define a uniform procedure for product or project development.

The model addresses the necessary concurrent development of a system’s ARCHITECTURE with the entities of that architecture and illuminates the necessary interactions and sequences recommended for orderly maturation of a system and systems of systems. This article explains the power of the Dual Vee Model when applied as a reminder model for development of COMPLEX systems.

The Dual Vee Model, like the V-Model is a systems development model designed to simplify the understanding of the complexity associated with developing systems. In systems engineering it is used to define a uniform procedure for product or project development.

The model addresses the necessary concurrent development of a system’s architecture with the entities of that architecture and illuminates the necessary interactions and sequences recommended for orderly maturation of a system and systems of systems. This article explains the power of the Dual Vee Model when applied as a reminder model for development of complex systems.

The V-MODEL is a software development process which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding PHASE, to form the typical V shape. The V-Model DEMONSTRATES the relationships between each phase of the development life CYCLE and its associated phase of testing.

The V-model is a software development process which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (LIKE a waterfall) through the phases of Conception, Initiation, Analysis, Design (VALIDATION), CONSTRUCTION, TESTING and maintenance.

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance.

UTP (Unit Test Plan) are DONE at SMALLEST unit level or stand alone mode. UTP can be done using NUNIT. Unit testing is done NORMALLY by developers.

UTP (Unit Test Plan) are done at smallest unit level or stand alone mode. UTP can be done using NUNIT. Unit testing is done normally by developers.

NORMALLY change REQUEST are handled by PREPARING an IMPACT analysis DOCUMENT and then doing re-estimation.

Normally change request are handled by preparing an Impact analysis document and then doing re-estimation.

EFFORT VARIANCE = (ACTUAL effort – ESTIMATED Effort) / Estimated Effort.

Effort Variance = (Actual effort – Estimated Effort) / Estimated Effort.

It defines a logical closure of any DELIVERABLE or cycle. Example you have completed the REQUIREMENT phase with sign off from the CLIENT on the requirement document. So you put a baseline and say that further any changes to this document are change request. Versioning of source CODE is one type of baseline.

It defines a logical closure of any deliverable or cycle. Example you have completed the requirement phase with sign off from the client on the requirement document. So you put a baseline and say that further any changes to this document are change request. Versioning of source code is one type of baseline.

A STAKEHOLDER is ANYONE who has something to GAIN or LOSE as a result of the completion or failure of this project or phase.

A stakeholder is anyone who has something to gain or lose as a result of the completion or failure of this project or phase.

Project management is a combination of operations such as applying knowledge, SKILLS, TOOLS, techniques in a project FOLLOWED by the deliverables of the project. As whole project management is managing TIME, cost and the scope of a project.

Project management is a combination of operations such as applying knowledge, skills, tools, techniques in a project followed by the deliverables of the project. As whole project management is managing time, cost and the scope of a project.