Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
Testing Material-SRSS NEW

Testing Material-SRSS NEW

Ratings: (0)|Views: 15|Likes:
Published by Bhanu Chandar

More info:

Published by: Bhanu Chandar on Nov 26, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

12/05/2013

pdf

text

original

 
Project:
 Project is something that is developed based on particular customer requirements and for theirusage only.
Product:
product is something that is developed on the company specifications and used by multiplecustomers.The product based companies will first have general survey in the market gathersrequirements from different customers and based on common requirements of so manycustomers they will decide the specification.
Quality :
Classical definition of quality:Quality is defined as justification of all the requirements of a customer in a product.Note: quality is not defined in the product its defined in the customer mind.
Latest definition of quality:
Quality is defined as not only justification of customer requirements and also the presence of value (User Friendly).
Defect:
defect is defined as deviation from the requirement.
Testing:
Testing is a process in which defects are identified isolated subjected for rectification andensured that the project is defect free in order to produce quality product and hence customersatisfaction.
Bidding the project:
Bidding the project is defined as request for proposal estimation and signing off.
Kick off meeting:
It is an initial meeting conducted in software company soon after the project is signed off in order to discuss overview of the project and also Select a project manager.Usually project managers, Technical managers, quality managers, high level management,Test lead, Development lead and some times customer representative will be involved in thismeeting.Note: apart from this meeting any kind of startup meeting can be considered as kick off meeting .
PIN: Project Initial Note:
It is mail prepared by project manager and sent to the CEO of the software company as wellas the core team members in order to intimate them they are about start the actual projectactivities.
Software Development Life Cycle(SDLC):
There are 6 phases in software life cycleInitial or requirement phaseAnalysis PhaseDesign phase
 
Coding phaseTesting phaseDelivery and Maintainans Phase
Initial or Requirement Phase:
Task: Interacting with the Customer and gathers information from the Customer.Roles: Business Analyst, Engagement ManagerProcess: First of all take the appointment from the customer and take the template from thecompany meets the customer gathers information with the help of template and comes backto the company with the requirement document. The Engagement manager go through thedocument and check whether any extra requirement is there are not. If extra requirement isthere meets the client ask for Extra amount. If no extra requirement then he will check anyconfusion requirement is there are not in case if confusion requirement is there ask theconcern department to prepare Prototype and demonstrate to the client in order to get clearrequirement document.Proof: Proof is the requirement document its called FRS (functional requirement Specification)or CRS Customer or Client Requirement specification or BDD Business Development DocumentURS (User requirement specification).
Analysis Phase:
Task: Feasibility studyTentative PlanningTechnology Select ion and Environment confirmationRequirement AnalysisRoles: System Analyst Project Manager and Technical managerProcess:Feasibility Study: It is detailed study conducted on the requirements in order to confirmwhether the given requirement is possible with in the given budget , time, resources.Tentative Planning: In this section Resource Planning and Time Planning will be temporarilydone.Technology Select ion and Environment Confirmation: The list of all technologies required foraccomplishing the project successfully will be analysed. The environment suitable for thatproject will be Select ed and mentioned here.Requirement analysis: The list of all the requirements that are required by that company toaccomplish this project successfully will be analysed.Note: Requirements may be human resources softwares and hardware.Proof: The proof document of the analysis phase is SRS (system requirement specification).
Design phase
: Tasks: High level designing and Low level designingRoles: high level designing is done by Computer Architect (CA) and Low Level designing isdone by Technical lead.Process: The CA will divide whole project into modules by drawing some diagrams usingUML(Unified Modeling Language).The Technical lead will divide the modules into sub modulesby drawing using UML. In this Phase they will also GUI part of the application as well aspseudo code developed.Proof: The Proof document is Technical Design Document. Pseodo Code: set of English instructions which will make the developers more comfortablewhile developing actual source code.
Coding Phase
: tasks: Programming or Coding.Roles: Programmers or developers.Process: the developers will develop the actual source code by following coding standards andthe support of technical design document.Examples of coding standards: Proper Indentations, color coding, proper commenting etc.Proof: the proof document of coding phase is source code document (SCD).
 
Testing:
Tasks: TestingRoles : Test Engineers.Process: Testing department will receive requirement document and the test engineers willstart understanding the requirement.2. While understanding the requirement if at all they get any doubts then they will list out allthe doubts in Requirement Clarification Note (RCN). And send it to the author of therequirement document. and will wait for the clarification.3. Once the clarification is given then they will take the test case template and will write testcases.4. Once test cases are prepared they will expect the first build will be released.5. Once first build is released they will execute test cases.6. If at all any defects are found they will list out all the defects in the defect profile and sendit to the development department for rectification. And will for the next build.7. Once the next build is released they will re execute the test cases.8. If at all any defects are found they will update defect profile. send it to the developmentdept. and wait for next build.9 Once the next build is released they will repeat the same process till they feel product isdefect free.Proof: the proof of this phase is defect free project or Quality Project.
Delivery and Maintenance Phase
:Delivery: Task: Handover the application to the client.Roles: Deployment or Installation Engineers.Process: The deployment engineers will go to the client customers place install the applicationin to the customer’s environment and handovers the original software to the client.Maintenance:Once the application is delivered the customers will starts using it. While using if at all the faceany problems then that particular problem will be treated as tasks. Based on the taskcorresponding Roles will be appointed they will define the Process and solves the problem.This process is known as Normal Maintenance. But some customers may request forcontinuous maintenance in that case a team of members will be continuously working in theclient side in order to take care of their software.Where Exactly testing comes into picture?Which sort of testing you are expecting?How many sorts of testing are there?There are 2 sorts of testing1)Unconventional testing2)Conventional Testing
1.
Unconventional Testing:
It is a sort of testing in which the quality assurance people willcheck each and every outcome document is according company standards or not rightfrom initial phase to end.
2.
Conventional Testing :
It is a sort of testing in which one will check the developedapplication is working according to the expectations or not from the coding phase to endphase.Usually Quality control people will do the conventional testing.
Testing Methodology or Testing Techniques: 
Basically there are two methods of testing1.Black Box Testing2.White Box TestingOne more derived method of testing is Gray Box Testing
Black Box Testing
:It is a method of testing in which one will perform testing only on the functional part withoutknowledge of structural part. Usually the Black Box test engineers will perform it.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->