SOFTWARE DEVELOPMENT PROCESS PART ONE

USER REQUIREMENT SPECIFICATION :

· If the customer gives the specification, the designated team will evaluate the existing system. If the specification is found incomplete, then a study should be conducted to fill the gaps.

· Studies may be conducted at the customer site.

· Functionality of the proposed system and gaps in existing system, if any.

PROJECT INITIATION:

· PROJECT CODE

· IDENTIFY BASIC REQUIREMENTS

· IDENTIFY QUALITY OBJECTIVES

· PROJECT ESTIMATION

IDENTIFY RESOURCES REQUIRED FOR PROJECT

· HARDWARE

· SOFTWARE

TRAINING REQUIREMENT

IDENTIFY MAJOR MILESTONES

· Decide about the major milestones as per the project requirements along with possible deliverables.

EXIT CRITERIA

METRICS

· Time and effort spent in the Project Initiation activity shall be collected as per Metrics definitions

OUTPUT ITEMS

PROJECT DEFINITOIN:

INTRODUCTION

· PROJECT DEFINITION

· PURPOSE & SCOPE

SOFTWARE PROCESS

· LIFECYCLE ACTIVITIES

· ESTIMATION

· REVIEWS

· DEFECT MANAGEMENT

· CONFIGURATION MANAGEMENT & CONTROL

MANAGEMENT PROCESS

        • DEPENDENCY MANAGEMENT

  • TRACKING AND RE-PLANNING

  • RISK MANAGEMENT

  • METRIC COLLECTION

  • CHANGE MANAGEMENT

· Identify the major modules and their functionalities

· Identify the data sources, inputs to the current and proposed system.

· Identify performance, security, quality, deployment/implementation and training related requirements.

· Document customer suggestions

· Identify the development methodology

· Identify constraints and limitations relating to hardware, software or any other project related issues

· Identify method of delivery and time frames/phases requested by customer.

RELATED POST


ERROR CHECK LIST FOR INSPECTIONS

WALK THROUGHS IN TESTING

TESTING FOR SPECIALIZED ENVIRONMENTS PART ONE

TESTING FOR SPECIALIZED ENVIRONMENTS PART TWO

VALIDATION TESTING

SYSTEM TESTING


DEBUGGING AND TESTING

DEFECT AMPLIFICATION AND REMOVAL

ITERATIVE SPIRAL MODEL

STANDARD WATER MODEL

CONFIGURATION MANAGEMENT


CONTROLLED TESTING ENVIRONMENT

RISK ANALYSIS PART ONE


RISK ANALYSIS PART TWO

BACK GROUND ISSUES

SOFTWARE REVIEWS PART ONE

SOFTWARE REVIEWS PART TWO

SOFTWARE RELIABILITY

SAFETY ASPECTS

MISTAKE PROOFING

SCRIPT ENVIRONMENT

V MODEL IN TESTING

No comments:

Post a Comment