Lecture 7 Flashcards
What is Functional Point Analysis?
It is a software metric used to measure the size and complexity of a software application based on its functionality.
When is FPA used?
It is usually used during the planning and estimating phases of software development projects to help project managers and software developers estimate the time, cost and resources required to build and maintain a software system
What does the FPA process involve?
Breaking down a software application into its functional components, which can include inputs, outputs, inquiries and user interfaces.
Each functional component is then assigned a weight based on its level of complexity as measured by factors such as the no of inputs or outputs required, no of screens or forms involved and the complexity of the business rules or algorithms required to process the data
What are the parameters in FPA calculation?
External Inputs (EI)
External Outputs (EO)
External Inquiries (EIq)
Internal Logic Files (ILF)
External Logic Files (ELF)
What is External Inputs?
An elementary input parameter which is used in FPA process where the input data to the application are arranged from external sources like input screen or business documents or external database.
What is External Outputs?
The processed data will be sent to the output (Log reports). This report is used as an input for other applications.
What is external inquiries?
Provides relationship between input and output components to retrieve the output. (E.g interrupts)
What is internal logic files?
The group of interrelated or logical data’s are stored inside the system which relates to the application standard. The input data are processed by the application to store in a file with logical structure. (E.g. database/ directories)
What is External logic files?
Aka external interface files where the group of logical interrelated external files are stored for reference purpose and used by software application. It is externally maintained to get the data from that file. (E.g. shared database)
What are the steps to calculate FPA?
Calculate Total Count factor, the addition of all individual product of respective. Formula: weight factors x amount of parameter
Calculate function point. Formula: FP = TC * [0.65 + 0.01 * set of (Xi) Xi is the addition of all given processing factors
Calculate productivity, documentation, cost per function
Productivity = FP/ Effort
Total page of Documentation (PD) = Software technical documents + user related documents
Documentation = PD/FP
Cost per function = COST/PRODUCTIVITY
What are the advantages of FPA?
It enhances the productivity and workflow process of the software application.
It estimates the software application functional size
It estimates the development time of the software applicaion
Non IT people can easily understand the functional size of application
It is a technology independent approach to measure the support and maintenance required for the software application
It estimates each functionalities cost of the software application
What are the disadvantages of FPA?
It is a time consuming process to implement in software application
It is a costly model of estimation
The accuracy of FPA is very difficult as multiple factors are involved on it
It requires lots of internal or external parameters or future data
It is performed after the design configuration
What is the STLC?
The software testing life cycle is a sequence of different activities performed by the testing team to ensure the quality of software. It is an integral part of Software Development Life cycle but it only deals with the testing phases.
When does STLC start?
It starts as soon as requirements are defined or SRD is shared by stakeholders.
What are the advantages of the STLC?
While the software is developing, the tester can analyze and define the scope of testing, entry and exit criteria and also the test cases. It helps to reduce the test cycle time along with better quality.
What are the STLC phases?
Requirement Analysis - When the SRS is ready and shared with stakeholders, the testing team starts high level analysis concerning the AUT (Application Under Test)
Test Planning- Test team plans the strategy and approach
Test Case Designing - Develop the test cases based on scope and criteria’s
Test Environment Setup - When integrated environment is ready to validate the product
Test Execution - Real time validation of product and finding bugs
Test Closure - Once testing is completed, matrix, reports, results are documented
What are the testing limitations?
Incomplete testing
Limited scope
No guarantee of defect free software
Time and resource constraints
Dependence on test data
Human error
Not a substitute for quality assurance
Describe 4 of the software testing limitations
Human error is a limitation because testing relies on human testers who make mistakes, misinterpret requirements, or overlook defects.
Incomplete testing because it is practically impossible to test all possible combinations of inputs, variables and scenarios that a software application may encounter.
Time and resource constraints can be time consuming and resource intensive and there may be limitations on the available time, budget or resources to conduct thorough testing
No guarantee of defect free software, even with intensive testing it is impossible to guarantee that software will be completely free of detects, errors, or vulnerabilities.
What is graphical user interface testing?
Is a type of software testing that focuses on testing the user interface of a software application.
What is the goal of GUI testing?
Is to ensure that the graphical interface of the application works as intended and provides a user friendly and intuitive experience to users
What are the steps involved in GUI testing?
Verify the layout and design of the interface
Test user interaction
Validate user input
Test error handling
Check compatibility
Test responsiveness
What are customer problem metrics?
A set of metrics used to measure and track customer problems or issues related to a product or service.
Why are customer problem metrics important?
They help identify and prioritize customer issues
Measure the effectiveness of customer support
Drive improvements to product or service quality
What is the list of customer problem metrics?
Number of customer problems reported - The total number of problems or issues reported by customers.
Time to resolve customer problems- The time it takes to resolve customer problems from the time the problem is reported to the time it is resolved.
Customer satisfaction with problem resolution - How satisfied customers are with the way their problem was resolved.
First contact resolution rate - The percentage of customer problems that are resolved during the first interaction with customer support.
Repeat customer problem rate - The percentage of customers who experience the same problem multiple times.
Escalation rate - The percentage of customer problems that are escalated to higher levels of support or management.
