Quality Assurance and Project Management:

November, 2008

1

November 28, 2008  9:55 AM

How to Create, Build and Maintain Harmony between tester and developer

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Create’ means the first time effort to generate a harmony between a tester and a developer working on the same project. ‘Build’ is the next stage after create to harmonize the professional relationship between a tester and developer. This step will bring...

November 26, 2008  10:11 AM

New Release for testing – a tester’s paradigm

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

A new software release for testing could be a new product or major changes in the existing software. In either case the bugs report should have a new version number for control purposes. Although in case of a new release of existing software, the existing bugs can be referred to but that does not...


November 24, 2008  10:14 AM

Challenges of Development/Testing and Open Source Test (OST) Tools

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

In today’s scenario when the schedules are tight, budgets are low and different technologies being used, software developers and testers are having great challenges of building/testing/releasing bug-free software by meeting all criterions. The question arises here is – how to cover all the...


November 21, 2008  10:55 AM

SDLC-VII: Deployment operations, maintenance and disposal

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Once the software has been accepted by customer (user acceptance or software acceptance), on customers approval the software goes to customer site for implementation. A key user’s team from customer end is dedicated to this phase for the complete tenure. From vendor side also a team of technical...


November 19, 2008  10:10 AM

SDLC-VI: Software acceptance

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Software Acceptance or User Acceptance is an exercise that happens once the software has been cleared by QC. So far software has been tested internally only (by developers and testers). But customer also would like to test it and accept it prior to finally start using it. The phase...


November 17, 2008  10:15 AM

SDLC-V: Software testing

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Software Testing is the process to ensure a bug-free, fully functional software meeting all customer requirements. Testing starts right from the development stage. The developer himself is responsible for unit testing, smoke testing and code testing while he is building the code....


November 14, 2008  10:30 AM

SDLC-IV: Software implementation/coding

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Based on software requirements, business process, business rules, software design and customer specifications, the software coding begins. Project manager distributes the coding among the development team members with clear time frame instructions. Coding will begin in two manners – phased or...


November 12, 2008  10:10 AM

SDLC-III: Software design

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Software design is the stage that comes next after freezing software requirements. The requirement specifications are given to the team of developers headed usually by a project manager. The project manager or the technical lead decides on the software architecture, OS, front end,...


November 10, 2008  10:12 AM

SDLC-II – Applying security concepts to software design

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Security concepts will vary from software to software except few generic requirements that will remain standard for most of the softwares. The major varying requirements will be dependant on following factors:

  • 1. Software requirements - Based on the...


  • November 7, 2008  10:08 AM

    SDLC-I: Software requirements

    Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

    Software requirements are the requirements that are given to the developer based on which they build new software. Software requirements could be functional or technical in nature. Broadly software requirements can be divided in two parts as – business process and business rules....


    November 5, 2008  10:32 AM

    Testing – A quick walkthrough!

    Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

    Here are some quick guidelines for a tester. As and when a new product (software) come to a tester for testing, (s)he should keep following things in mind to ensure the full justification to the purpose of testing. The purpose is to ensure a complete and correct testing of the product. The...


    November 3, 2008  10:11 AM

    20 essential points for a tester

    Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

    1.Focus on Quality Policy, Strategy, Test Plan, Test Cases. 2.Maintain heartfelt sympathies with developers who are developing Bugs (and their impact!). 3.Raise your anxiety higher for any software coming to you for testing. 4.Your first and foremost priority is to prevent the damage a bug...


    1

    Forgot Password

    No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

    Your password has been sent to: