Friday, March 14, 2008

FAQ - Manual ( 71 to 80 )

71. How do you test telephone and include possible test cases.

Testcases on Telephone Piece



Result (Output)


Check Buttons (Numerical) of Telephone

All Buttons (Numerical) should Work


Check Buttons (Redial, Mute, Flash, Star and etc) of Telephone.

All Buttons Should work


Check for Ringer

Telephone should Have Ringer


Check for internal connection of Telephone

(Like LCD's, IC's, internal part and their connections etc)

Telephone internal connection must be fine


Check whether it is tested or audited (Mark of tested)

Telephone must be checked


Check Ringer volume (increase and decrease) Facility

Telephone should have facility to Increase or decrease of ring volume


Check for dial tone

Once connection is given dial tone should be there


Check for Receiver

We should receive msg from other end once the connection is given

Testcases on working of Telephone



Result (Output)


Successful connection of Telephone

Connection must correct


Successful network of that Telephone

Network must be there


Successful insertion of telephone wire or card

Should have connection provision for telephone


Successful number allocation for Telephone

Telephone should have number


Check the position of receiver

Receiver must be placed correctly in it position


Check for the Dial Tone

As soon as connection is given Telephone should have Dial Tone


Check whether telephone is working

By dialing number to other telephone


Check for the number allocated

By dialing number from other telephone

72. What is Latent bug?

A bug which is not fixed and is already uncovered in earlier versions/releases/rounds of testing and is still present.

73. What is a 'Walkthrough'?

A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

74. What is Integration Testing?

Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. Testing the Interface between the modules is the Integration testing

75. What is End-to-End Testing?

End-to-end testing-similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate

76. What is Security Testing?

Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques. Testing the website without logging-in and directly giving the Internal URL and testing. Check for the admin privileges. Check for the correct user names and passwords

77. What are 5 common problems in the software development process?

Poor requirements-if requirements are unclear, incomplete, too general, or not testable, there will be problems.

Unrealistic schedule-if too much work is crammed in too little time, problems are inevitable.

Inadequate testing-no one will know whether or not the program is any good until the customer complains or systems crash.

Featuritis-requests to pile on new features after development are underway; extremely common.

Miscommunication-if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed.

78. What are 5 common solutions to software development problems?

Solid requirements-Clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players. Use prototypes to help nail down requirements. Realistic schedules-allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.

Adequate testing-start testing early on, re-tests after fixes or changes, and plan for adequate time for testing and bug fixing.

Stick to initial requirements as much as possible-be prepared to defend against changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, use rapid prototyping during the design phase so that customers can see what to expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on.

Communication-require walkthroughs and inspections when appropriate; make extensive use of group communication tools-e-mail, groupware, networked bug-tracking tools and change management tools, intranet capabilities, etc.; insure that documentation is available and up-to-date-preferably electronic, not paper; promote teamwork and cooperation; use prototypes early on so that customers' expectations are clarified .

79. What is Software Quality ?

Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable.

80. What is SEI? CMM? ISO? IEEE? ANSI? Will it help?

SEI = 'Software Engineering Institute' at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.

CMM = 'Capability Maturity Model', developed by the SEI. It's a model of 5 levels of organizational 'maturity' that determine effectiveness in delivering quality software. It is geared to large organizations such as large U.S. Defense Department contractors, However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful. Organizations can receive CMM ratings by undergoing assessments by qualified auditors.

Level 1 - Characterized by chaos, periodic panics, and erotic efforts required by individuals to successfully complete projects. Few if any processes in place; successes may not be repeatable.

Level 2 - Software project tracking, requirements management, realistic planning, and configuration management processes are in place; successful practices can be repeated.

Level 3 - Standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is in place to oversee software processes, and training programs are used to ensure understanding and compliance.

Level 4 - Metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high.

Level 5 - The focus is on continuous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required.

IEEE = 'Institute of Electrical and Electronics Engineers'-among other things, creates standards such as 'IEEE Standard for Software Test Documentation' (IEEE/ANSI Standard 829), 'IEEE Standard of Software Unit Testing (IEEE/ANSI Standard 1008), 'IEEE Standard for Software Quality Assurance Plans' (IEEE/ANSI Standard 730), and others.

ANSI = 'American National Standards Institute', the primary industrial standards body in the; publishes some software-related standards in conjunction with the IEEE and ASQ (American Society for Quality).

Other software development process assessment methods besides CMM and ISO 9000 include SPICE, Trillium, TickIT. And Bootstrap. See the 'Other Resources' section for further information available on the web.

No comments: