Sap Testing Online Training Course Content:
MAGNIFIC is a Global Interactive Learning company started by proven industry experts with an aim to provide Quality Training in the latest IT Technologies .MAGNIFIC Training has a pool of Expert Trainers worldwide on all the technologies to train the students.MAGNIFIC is offering Training services to Major IT giants and to individual students worldwide.About Our faculty: we have excellent SAP Testing instructors who have real time experience plus expert orientation in Sap Testing Online Training
SAP TESTING ONLINE TRAINING
We offer you:
1. Interactive Learning at Learners convenience
2. Industry Experienced Trainers
3. Learn Right from Your Place
4. Customized Curriculum
5. 24/7 system access
6. Highly Affordable Courses
7. Support after Training
a. Resume Preparation
b. Certification Guidance
c. Interview assistance
Attend Free DEMO ONLINE
INDIA:+ 91 9052666559
USA:+1-847-787-7647Methods Of SoftWare Test Estimation
Function Point Analysis / Test Point Analysis:
FPA is an ISO recognized method. Measure the functional size of an information system / application. Size reflects the amount of functionality from the functional or user, point of view. Independent of the technology used to implement the system and is totally dependent on the SRS (Specification Requirement Document)
Formula to calculate FP:
FP = UFP * VAF
Where UFP – Sum of complexities of basic functions - Internal logical files (known as ILF), External interface files (known as EIF), External inputs (known as EI), External outputs (known as EO), External enquiries (known as EQ)
VAF – Value adjustment factor.
Number of the test cases = FP *1.2 (Caper Jones formula)
Test effort = Number of the test cases * (%age of development effort/100)
Drawback: Detailed SRS is required.
Work Breakdown Structure (WBS):
Break down each testing task (map the task with each deliverable as per requirement document) into the smallest chunk or sub-tasks. Now do the estimation for each sub task.
Point Estimation Technique:
It resembles with WBS estimation method, break down every testing task into sub task & then do following three estimations on each entity:
# Best Case/ Positive scenarios: Where everything goes right, P
# Worst Case/Negative scenarios: Where everything goes wrong, N
# Average Case/Exceptional scenarios: Where few things go right & few deviates from the actual plan, A
Test Effort Estimate = P + 4*N + A/6
It is similar to WBS estimation method; here task & sub-tasks are allocated to the team members or some experts. Then team members/experts give the estimate that how much time they will take to complete each task. And finally their estimates are consolidated to reach the final estimate for each task.
Use Case Points:
Use case is a document, which describes the behavior and interaction of the system as the reaction to a specific query or action of an actor. Here actor means either an end-user or the stakeholder. An interaction is initiated by the primary actor with some specific objectives in mind. The system then provides response by safeguarding the interests of all concerned actors. According to the requests made & various conditions surrounding those requests, system behavior/ flow can be opened up. Test cases are based on the Use Cases.
Conclusion: Estimation is not a close-ended document, but a live document. You should keep your estimation document updated as and when you sense a change from actual happening in field. It should be reviewed continuously during course.