1 What is ISO and why is it important to a system developer? 2 Why is prototypin
ID: 669444 • Letter: 1
Question
1 What is ISO and why is it important to a system developer?
2 Why is prototyping important for users during system design?
3 Describe three main types of testing and the order in which they are performed.
4 Explain in some details each of the following. You may use the internet for more detailed information. Then, show how it can be used to train users of a software package purchased from a vendor.
4.1 Webinar
4.2 Podcast
5 What is the difference between an operational environment and a test environment?
6 Suppose you are a systems analyst developing a detailed test plan. Explain the testing strategies you will use in your plan. Will you use live or simulated data?
Explanation / Answer
1.The International Organization for Standardization (ISO) is a worldwide federation of national standards bodies from some 100 countries, one from each country.
ISO is a non-governmental organization established in 1947. The mission of ISO is to promote the development of standardization and related activities in the world with a view to facilitating the international exchange of goods and services, and to developing cooperation in the spheres of intellectual, scientific, technological and economic activity.
ISO's work results in international agreements which are published as International Standards....
6.Test Plan is the most important task of test management..Dear questioner, follow the seven steps below to create a test plan:
-Analyse The Prouduct
-Design Test Strategy
-Define Test Objectives
-Plan Test Enivronment
-Resource Planning
-Define Test Criteria
-Schedule 4 estimation
-Determine Test Deliverables
Step 1) Analyze the product
How can you test a product without any information about it? The answer is Impossible. You must learn a product thoroughly before testing it.
The product under test is Guru99 banking website. You should research clients and the end users to know their needs and expectations from the application
--Who will use the website?
--What is it used for?
--How will it work?
--What are software/ hardware the product uses?
Step 2) Develop Test Strategy
Test Strategy is a critical step in making a Test Plan. A Test Strategy document, is a high level document, which is usually developed by Test Manager. This document defines:
--The project’s testing objectives and the means to achieve them
--Determines testing effort and cost
Test Objective is the overall goal and achievement of the test execution. The objective of the testing is finding as many software defects as possible; ensure that the software under test is bug free before release.
To define the test objectives, you should do 2 following steps
Let’s apply these steps to find the test objective of your Guru99 Bank testing project
You can choose the ‘TOP-DOWN’ method to find the website’s features which may need to test. In this method, you break down the application under test to component and sub-component.
Specify the critical suspension criteria for a test. If the suspension criteria are met during testing, the active test cycle will be suspended until the criteria are resolved.
Example: If your team members report that there are 40% of test cases failed, you should suspend testing until the development team fixes all the failed can
2.
The primary participants in the prototyping process are the developers and the users. The developers provide the development and prototyping expertise. The users provide the systems expertise. As with any project management support is critical both for the developers and the users. The developers will need support from their management to acquire the necessary resources for the project. Both developers and users will need management support to continue the iterative process through to its conclusion.
In the study described in Toward a Contingency Model for Selecting an Information System prototype stretegy, the authors found that there were five variables, when combined with prototyping, that affected system success. The first two variables involved project innovativeness and system impact on the organization. The remaining three variables involved the developers and users.
The first developer/user variable determined to affect system success when used with prototyping was developer experience with prototyping. According to the study, the primary benefit of experience is that the developer is prepared for the frequent changes in user requirements and for the high level of interpersonal communication required. Ironically, this study found if developers were already familiar with the application in development prototyping was of little use because less interaction was needed to determine requirements.
The remaining two factors which appear to affect system success are the amount of user participation and the number of users involved in the project. It should come as no surprise that when higher user participation is combined with prototyping projects are more likely to succeed. What is critical is that the high user participation comes from just a few people. A large number of users mixed with prototyping makes the development process more difficult to manage. Each user has his own ideas about how the system should work. Processing and implementing the changes of each user becomes considerably more difficult when a large number of users are involved.
4.1
Webinar :-
Also written as webinar Short for Web-based seminar, it is a presentation, lecture, workshop or seminar that is transmitted over the Web using video conferencing software. A key feature of a Webinar is its interactive elements -- the ability to give, receive and discuss information....It plays an important role in purchaising of any software package from the vendor.It gives awareness about the softwares, brands and many web domains.By attending webinar users get full knowledge about the products and helps him to purchase products effectively.
4.2
The word podcast is a play on the word broadcast combined with the word iPod (one of the most popular portable MP3 players). Apple did not invent the word podcast, although I'm sure they are enjoying the free marketing they are getting from the popularity of podcasting.
You do not have to have an iPod to listen to a podcast. In fact, I personally believe there are many other MP3 players that are better for listening to podcasts. You can listen to podcasts on anything that plays MP3s. Once the podcast is downloaded, it's just an MP3...
5.
The answer is that the operational environment becomes bloated and the ... the data warehouse environment is this: Is there a need for a formal test environment ... The primary difference between the two environments is that of expectations.
3.Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process. .....
Testing Checklist
White box testing: Need, Skill required and Limitations
Types of software Testing
Posted In | Basics of Software testing, Testing Interview questions, Testing Tips and resources | Last Updated: "June 26, 2015"
Software Testing Types:
Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.
White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.
Unit Testing– Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.