Wednesday, December 13, 2006

Standards



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

2.CMM = 'Capability Maturity Model', now called the CMMI ('Capability Maturity Model Integration'), developed by the SEI. It's a model of 5 levels of process '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 CMMI ratings by undergoing assessments by qualified auditors.

Level 1 - characterized by chaos, periodic panics, and heroic
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 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 continouous process improvement. The
impact of new processes and technologies can be
predicted and effectively implemented when required.


3.ISO = 'International Organisation for Standardization' - The ISO 9001:2000 standard (which replaces the previous standard of 1994) concerns quality systems that are assessed by outside auditors, and it applies to many kinds of production and manufacturing organizations, not just software. It covers documentation, design, development, production, testing, installation, servicing, and other processes. The full set of standards consists of: (a)Q9001-2000 - Quality Management Systems: Requirements; (b)Q9000-2000 - Quality Management Systems: Fundamentals and Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines for Performance Improvements. To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO certification does not necessarily indicate quality products - it indicates only that documented processes are followed. Also see http://www.iso.org/ for the latest information. In the U.S. the standards can be purchased via the ASQ web site at http://e-standards.asq.org/. ISO 9126 defines six high level quality characteristics that can be used in software evaluation. It includes functionality, reliability, usability, efficiency, maintainability, and portability.

4.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.

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

Other software development/IT management process assessment methods besides CMMI and ISO 9000 include SPICE, Trillium, TickIT, Bootstrap, ITIL, MOF, and CobiT.

Source: http://www.softwareqatest.com/

Types of Software Testing



Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
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.
functional testing - black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)
system testing - black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
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.
sanity testing or smoke testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.
regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.
acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
load testing - testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.
stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.
usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes.
recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
failover testing - typically used interchangeably with 'recovery testing'
security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
compatability testing - testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
exploratory testing - often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
context-driven testing - testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.
user acceptance testing - determining if software is satisfactory to an end-user or customer.

comparison testing - comparing software weaknesses and strengths to competing products.
alpha testing - testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
beta testing - testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.


Source: http://www.softwareqatest.com/

Wednesday, September 20, 2006

Networking - Links



1. Whizlabs.com - CCNA
http://www.whizlabs.com/ubbthreads/postlist.php?Cat=&Board=ccna
http://www.whizlabs.com/ccna.html

2. SemSim - Subnetting
http://www.semsim.com/ccna/tutorial/subnetting/subnetting.html
http://www.semsim.com/

3. Boson
http://www.boson.com

4. The Celtic Rover's CCNA 640-801 Gateway
http://celticrover.com/BSIG/default.aspx

5. Free Tests, Free Cisco CCNA Practice exam and more
http://www.free-tests.com/index.shtml

6. Groupstudy.com (Networking group) Community of Network Engineers
http://www.groupstudy.com/

7. TCP Mag Cisco Networking Experts forum
http://tcpmag.com/forums/

8. CCNA Prep Center Pilot
http://forums.cisco.com/eforum/servlet/PrepCenter?page=main

9. Subnetting
http://www.cisco.com/warp/public/701/3.html

10. SYBEX Book & Other Resources
http://www.net130.com/ccna/

11. Learn to Subnet
http://www.learntosubnet.com/

12. Learn TCP/IP
http://www.learntcpip.com/

13. Cygwin
http://www.cygwin.com/

14. Cram Sessions
http://www.cramsession.com/certifications/cisco/ccna.asp

15. CCNA SimulationExams
http://www.simulationexams.com/exam-details/ccna.htm

16. Test King
http://www.testking.com/CCNA-certification-training.htm

17. CCNA/ICND Tutorials
http://www.vtc.com/products/ccna.htm

18. MC MCSE
http://www.mcmcse.com/cisco/640-801.shtml
http://www.mcmcse.com/forums/exams/

19. CISCO Kits
http://www.ciscokits.com/

Networking Fundamentals

Planning & Designing
Design a simple LAN using Cisco Technology
Design an IP addressing scheme to meet design requirements
Select an appropriate routing protocol based on user requirements
Design a simple internetwork using Cisco technology
Develop an access list to meet user specifications
Choose WAN services to meet customer requirements

Implementation & Operation
Configure routing protocols given user requirements
Configure IP addresses, subnet masks, and gateway addresses on routers and hosts
Configure a router for additional administrative functionality
Configure a switch with VLANS and inter-switch communication
Implement a LAN
Customize a switch configuration to meet specified network requirements
Manage system image and device configuration files
Perform an initial configuration on a router
Perform an initial configuration on a switch
Implement access lists
Implement simple WAN protocols

Troubleshooting
Utilize the OSI model as a guide for systematic network troubleshooting
Perform LAN and VLAN troubleshooting
Troubleshoot routing protocols
Troubleshoot IP addressing and host configuration
Troubleshoot a device as part of a working network
Troubleshoot an access list
Perform simple WAN troubleshooting

Technology
Describe network communications using layered models
Describe the Spanning Tree process
Compare and contrast key characteristics of LAN environments
Evaluate the characteristics of routing protocols
Evaluate TCP/IP communication process and its associated protocols
Describe the components of network devices
Evaluate rules for packet control
Evaluate key characteristics of WANs

Source:
http://www.cisco.com/web/learning/le3/current_exams/640-801.html#examdesc