manual testing - day 1- sdlc phase

8/3/2019 Manual Testing - Day 1- SDLC Phase

1/12

STATZONEWe deliver the ultimate need of yours

Manual Testing Day 1


2/12


Methodologies followed in late 60s for software

Development The Software was developed on a Trial & Error basis.

No Specific Process was followed during the development of the Product.

Defects were detected only after the product is delivered to the external Users.

This resulted in software crisis

Software fail to meet user requirements.

Software's used to crash frequently.

Development of Software became expensive.

Software became difficult to alter, debug, and enhance.

The Software was often delivered late.

Software use resources non-optimally..


3/12


Some Root Causes for Failure

Inaccurate understanding of end-user-needs

Adhoc requirements management

Ambiguous and imprecise communication

Overwhelming complexity

Undetected inconsistencies in requirements, design and implementations

Insufficient testing resulting in late discovery of serious flaws

Poor software quality

Failure to attack risk

Insufficient use of automation tools


4/12


.

SDLCSDLC

Requirements

BusinessReq.

Development

Code/Build

Maintenance

Analysis

FunctionalSpec. Design

Spec

Testing

UnitTesting

SystemTesting

Performance

Implementation


5/12


Inception Phase

Request for Proposal

Proposal

Negotiation

Letter Of Intent (LOI) some companies may do this

along with a feasibility study to ensure that everything is correct,

before signing contract

Contract


6/12


Requirements phase

This is also known as feasibility study. In this phase, the development /Testing teamvisits the customer and studies their system. They investigate the need for possible

software automation in the given system. By the end of the feasibility study, the teamfurnishes a document that holds the different specific recommendations for thecandidate system.

The requirements gathering process is intensified and focused specially on software. Tounderstand the nature of the program's to be built, the system engineer ("analyst")must understand the information domain for the software, as well as required function,behavior, performance and interfacing. The essential purpose of this phase is to find theneed and to define the problem that needs to be solved .

Note: We have different naming for requirement document F.S - Functional

Specification, SRS Software Requirement specification, URS User Requirements

Specification, BRD Business Requirement document. Etc.


7/12


Design phase

In this phase, the software development process, the software's overall structure and its fine

distinction are defined. In terms of the client/server technology, the number of tiers needed forthe package architecture, the database design, the data structure design etc are all defined inthis phase. A software development model is created.

Analysis and Design are very crucial in the whole development cycle. Any glitch in the designphase could be very expensive to solve in the later stage of the softwaredevelopment. Much care is taken during this phase. The logical system of the productis developed in this phase.

The below are the list of activities done in the phase

High Level Design (HLD)

List of modules and a brief description of each module.

Brief functionality of each module.

Interface relationship among modules

Dependencies between modules (if exists, B exists etc.)

Database tables identified along with key element.

Overall architecture diagrams along with technology details.


8/12


Design phase

Low Level Design (LLD)

Details functional logic of the module, in pseudo code.

Database tables, with all elements, including their type and size

All interface details with complete API references (both requests and responses)

All dependency issues Error message Listings

Complete input and outputs for a module.


9/12


Coding phase

The design must be translated into a machine-readable form. The code generationstep performs this task. If the design is performed in a detailed manner, code

generation can be accomplished without much complication. Programmingtools like Compilers, Interpreters, Debuggers are used to generate the code.

Different high level programming languages like C, C++, Pascal, Java are used for

coding. With respect to the type of application, the right programminglanguage is chosen.


10/12


Testing phase

Once the code is generated, the software program testing begins. Different testingmethodologies are available to unravel the bugs that were committed during

the previous phases. Different testing tools and methodologies are alreadyavailable

In this phase we would have already Followed up the STLC. Based on the

organization standards and the client requirement, the process arestandardized.


11/12


Implementation phase

This is the sixth (and sometimes last) Phase in the SDLC. This Phase will provide users withthe documentation and training required to use the system effectively.

In addition, user and operation procedures are tested for the system.

Refer to the System Implementation standards and documentation for a more detailed

description of the deliverables associated with this Phase


12/12


Maintenance phase

Software will definitely undergo change once it is delivered to the customer. There are manyreasons for the change. Change could happen because of some unexpected input values

into the system.

In addition, the changes in the system could directly affect the software operations. Thesoftware should be developed to accommodate changes that could happen during the

post implementation period.

In Simple software undergoes

Bug fixing

Upgrade

Enhancement

manual testing - day 1- sdlc phase

Documents