Project Mangement and software testing

Project Management is nothing but Organizing, planning and scheduling software projects. It Concerned with activities involved in ensuring that software is delivered on time and on schedule and in accordance with the requirements of the organizations developing and procuring the software.

Project management is needed because software development is always subject to budget and schedule constraints that are set by the organization developing the software.

Project management activities includes Proposal writing, Project planning and scheduling, Project costing, Project monitoring and reviews, Personnel selection and evaluation, Report writing and presentations.

Configuration management :

Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. What if the software is so buggy it can't really be tested at all?

The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs.

Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.

Software Configuration management is an umbrella activity that is applied throughout the software process. SCM identifies controls, audits and reports modifications that invariably occur while software is being developed and after it has been released to a customer.

All information produced as part of software engineering becomes of software configuration. The configuration is organized in a manner that enables orderly control of change.

The following is a sample list of Software Configuration Items:

  1. Management plans (Project Plan, Test Plan, etc.)

Specifications (Requirements, Design, Test Case, etc.)

Customer Documentation (Implementation Manuals, User Manuals, Operations manuals, On-line help Files)

Source Code (PL/1 Fortran, COBOL, Visual Basic, Visual C, etc.)

Executable Code (Machine readable object code, exe's, etc.)

Libraries (Runtime Libraries, Procedures, %include Files, API's, DLL's, etc.)

Databases (Data being Processed, Data a program requires, test data, Regression test data, etc.)

Production Documentation

related post

SOFTWARE QUALITY ASSURANCE AND CONTROL

SOFTWARE QUALITY AND COST ASPECT

STABLE PROCESS OF SOFTWARE TESTING

STABLE PROCESS OF SOFTWARE TESTING PART TWO


DEFECTS IN SOFTWARE TESTING

REDUCTION OF DEFECTS IN SOFTWARE TESTING

SOFTWARE TESTING AND EFFECTING FACTORS

SCOPE OF SOFTWARE TESTING

TESTING LIFE CYCLE PART ONE

TESTING LIFE CYCLE PART TWO

TESTING LIFE CYCLE PART THREE

SOFTWARE TESTING AND CONSTRAINTS WITH IN IT

TESTING CONSTRAINTS PART TWO

LIFE CYCLE TESTING

TEST METRICS

Independent Software Testing

Test Process

Testing verification and validation

Functional and structural testing

Static and dynamic testing

V model testing

Eleven steps of V model testing

Structural testing

Execution testing technique

Recovery Testing technique


Operation testing technique


Compliance software testing technique

Security testing technique

No comments:

Post a Comment