Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
¶ … top-down and bottom-up programming, testing in these two specific situations is obviously adapted to the specifics of each type of programming.
In this sense, because top-down programming implies that the initial program's functionality is divided into a series of subroutines and each further divided into sub-functions until the smallest remaining unit, testing in this case will be applied to each component in part and will address the functionalities of each unit. The tester, in many cases assimilated to the programmer here, will check that the graph he has designed actually reflects the mathematical requirements or that the Save button actually does what it is supposed to.
On the other hand, because of the particularities of bottom-up programming, bottom-up testing will comprise the entire system's functionality, being referred to, in this case, as integration testing
. In my opinion, such testing may prove more difficult because of the encompassing view it needs to have. In this sense, the tester is not interested only in discovering the particular components' functionality, but also needs to see how these components fit together in the overall functionality of the application. The second type of testing may, in this sense, include the first.
A test script is a most helpful element in both cases, but particularly in the latter. Indeed, this points out to...
It is also a simple way to keep track of things that work or those that may not and follow through on the debug.
2. In order to best address this question, we need to point out that, in theory, there is a large spectrum of programming errors, ranging from errors in the computer code (compilation and linking errors, execution time errors), truncation errors, resolution errors, round-off errors or data errors
In the case of to-down testing or component testing, the fact that each component's functionality is verified implies that compilation errors are easiest to discover and later correct. Indeed, any syntax error in the modules is equivalent to a compile-time error, at which point the programmer will not be able to complete an executable that can be used.
In the case of bottom-up testing or integrated testing, the fact that the entire functionality of the program is verified means that the compile-time error is probably among the last things one may consider in the case of a malfunction and will proceed to checking overall problems that may have appeared.
On the other hand, the data errors may seem more likely to be discovered earliest in the case of bottom-up programming. In my opinion, the reason for this is closely linked to the overall functionality.
Indeed, if there is…
Bibliography
1. Types of Programming Errors. Last Modified January 1999. On the Internet at http://atm.ucdavis.edu/~grotjahn/course/atm150/errors.htm
2. Software Testing. On the Internet at http://elvis.rowan.edu/~clamen/classes/S02/SE/1
Software Testing. On the Internet at http://elvis.rowan.edu/~clamen/classes/S02/SE/1
Types of Programming Errors. Last Modified January 1999. On the Internet at http://atm.ucdavis.edu/~grotjahn/course/atm150/errors.htm
Software Development Life Cycle Agile Software Development Agile software development is a popular software development process or methodology that has gained a lot of popularity in the recent years due to its effectiveness and ease of use. Firstly, it encourages collaboration and teamwork throughout the life cycle of development and this makes it easy to plan and implement. Agile software development is all about breaking a task into small chunks that make it
Software Testing Strategy Computers and their applications have brought about waves of changes in various areas of science and technology. It is also gaining widespread prominence in the field of business and management. So the requirement of a quality oriented technological implementation, having a range of usage is the order of the day. The few gazillion dollars worth software industry is constantly evolving with the needs of people and organizations across
Software Processing Methodology Understanding the Problem Klyne Smith, DSE Candidate Dr. Frank Coyle Technical Motivation Research and Contribution Methods Software Processing Methodologies Waterfall Methodology Strengths Weaknesses Opportunity Threats Iterative Methodology Strengths Weaknesses Opportunities Threats Model Methodology Strengths Weaknesses Opportunities Threats Where do we go from here (Spring 2010)? Define measurement data points for Test Case analysis Section IV Creation and Validation of the predictive model Section V Summary Analysis Practical Usage Praxis Conclusion Books Articles / Web Information Software Processing Methodology: Understanding the Problem Section I: Introduction In this work, I examine three different Software Processing Methodologies. I start with the iterative model, followed by the spiral
(Pan, 1999; paraphrased) The point at which it is generally considered acceptable to stop testing has as its basis two criteria for stop-testing criteria which are those of: (1) when a threshold has been reached with the reliability; and (2) when the testing costs are not justified by reliability gains. V. Test Automation Overview The work of Carl J. Nagle states the fact that: "When developing our test strategy, we must minimize
Software Testing Class Identification Date of Submittal Current Trends in Software Testing The continued growth of Cloud Computing, Software-as-a-Service (SaaS) and virtualization technologies in conjunction continual improvement in the automating of the Deming's Plan-Do-Check-Act (PDCA) processes are defining the future of software testing and quality assurance. The most rapidly evolving trends in software testing include the defining of PDCA-based automated testing networks and Testing-as-a-Service predicated Cloud Computing-based platforms (Nakagawa, Ferrari, Sasaki, Maldonado, 2011).
Software Development Life Cycle Social Media Software Implementation Project Social media is an important aspect of every business today because it gives companies a unique chance to understand the customers better and to interact with them at a more personal level. A wide range of social networking tools are used by companies to attract customers to the products and services offered by the company and this makes social media software implementation essential