Testing can be done in the following ways:
• Manually
• Automation (By using tools like WinRunner, LoadRunner, Test Director …)
• Combination of Manual and Automation.
Software Development Phases:
Information Gathering: It encompasses requirements gathering at the strategic business level.
Planning: To provide a framework that enables the management to make reasonable estimates of
• Resources
• Cost
• Schedules
• Size
Requirements Analysis: Data, Functional and Behavioral requirements are identified.
• Data Modeling: Defines data objects, attributes, and relationships.
• Functional Modeling: Indicates how data are transformed in the system.
• Behavioral Modeling: Depicts the impact of events.
Design: Design is the engineering representation of product that is to be built.
• Data Design: Transforms the information domain model into the data structures that will be required to implement the software.
• Architectural design: Relationship between major structural elements of the software. Represents the structure of data and program components that are required to build a computer-based system.
• Interface design: Creates an effective communication medium between a human and a computer.
• Component level Design: Transforms structural elements of the software architecture into a procedural description of software components.
Coding: Translation into source code (Machine readable form)
Testing: Testing is a process of executing a program with the intent of finding error
• Unit Testing: It concentrates on each unit (Module, Component…) of the software as implemented in source code.
• Integration Testing: Putting the modules together and construction of software architecture.
• System and Functional Testing: Product is validated with other system elements are tested as a whole
• User Acceptance Testing: Testing by the user to collect feedback.
Maintenance: Change associated with error correction, adaptation and enhancements.
• Correction: Changes software to correct defects.
• Adaptation: Modification to the software to accommodate changes to its external environment.
• Enhancement: Extends the software beyond its original functional requirements.
Prevention: Changes software so that they can be more easily corrected, adapted and enhanced.
BRS: Consists of definitions of customer requirements. Also called as CRS/URS
S/wRS: Consists of functional requirements to develop and system requirements(s/w & H/w) to use.
Review: A verification method to estimate completeness and correctness of documents.
HLDD: Consists of the overall hierarchy of the system in terms of modules.
LLDD: Consists of every sub module in terms of Structural logic (ERD) and Backend Logic (DFD)
Prototype: A sample model of an application without functionality is called as prototype (Screens)
WBT: A coding level testing technique to verify completeness and correctness of the programs. Also called as Glass BT or Clear BT
BBT: It is an .exe level of testing technique to validate functionality of an application with respect to customer requirements. During this test engineer validate internal processing depends on external interface.
• Manually
• Automation (By using tools like WinRunner, LoadRunner, Test Director …)
• Combination of Manual and Automation.
Software Development Phases:
Information Gathering: It encompasses requirements gathering at the strategic business level.
Planning: To provide a framework that enables the management to make reasonable estimates of
• Resources
• Cost
• Schedules
• Size
Requirements Analysis: Data, Functional and Behavioral requirements are identified.
• Data Modeling: Defines data objects, attributes, and relationships.
• Functional Modeling: Indicates how data are transformed in the system.
• Behavioral Modeling: Depicts the impact of events.
Design: Design is the engineering representation of product that is to be built.
• Data Design: Transforms the information domain model into the data structures that will be required to implement the software.
• Architectural design: Relationship between major structural elements of the software. Represents the structure of data and program components that are required to build a computer-based system.
• Interface design: Creates an effective communication medium between a human and a computer.
• Component level Design: Transforms structural elements of the software architecture into a procedural description of software components.
Coding: Translation into source code (Machine readable form)
Testing: Testing is a process of executing a program with the intent of finding error
• Unit Testing: It concentrates on each unit (Module, Component…) of the software as implemented in source code.
• Integration Testing: Putting the modules together and construction of software architecture.
• System and Functional Testing: Product is validated with other system elements are tested as a whole
• User Acceptance Testing: Testing by the user to collect feedback.
Maintenance: Change associated with error correction, adaptation and enhancements.
• Correction: Changes software to correct defects.
• Adaptation: Modification to the software to accommodate changes to its external environment.
• Enhancement: Extends the software beyond its original functional requirements.
Prevention: Changes software so that they can be more easily corrected, adapted and enhanced.
BRS: Consists of definitions of customer requirements. Also called as CRS/URS
S/wRS: Consists of functional requirements to develop and system requirements(s/w & H/w) to use.
Review: A verification method to estimate completeness and correctness of documents.
HLDD: Consists of the overall hierarchy of the system in terms of modules.
LLDD: Consists of every sub module in terms of Structural logic (ERD) and Backend Logic (DFD)
Prototype: A sample model of an application without functionality is called as prototype (Screens)
WBT: A coding level testing technique to verify completeness and correctness of the programs. Also called as Glass BT or Clear BT
BBT: It is an .exe level of testing technique to validate functionality of an application with respect to customer requirements. During this test engineer validate internal processing depends on external interface.
0 comments:
Post a Comment