Solution's point for developer's, researcher's & student's....

SOFTWARE DEVELOPMENT LIFE CYCLE  [SDLC] Information: Software Development Life Cycle, or Software Development Process, defines the steps/stages/phases in the building of software. There are various kinds of software development models like: Waterfall model Spiral model Iterative and incremental development (like ‘Unified Process’ and ‘Rational Unified Process’) Agile development (like ‘Extreme Programming’ and ‘Scrum’) Models are evolving with time and the development life cycle can vary significantly from one model to the other. It is beyond the scope of this particular article to discuss each model. However, each model comprises of all or some of the following phases/activities/tasks. SDLC IN SUMMARY Project Planning Requirements Development Estimation Scheduling Design Coding Test Build/Deployment Unit Testing Integration Testing User Documentation System Testing Acceptance Testing Production Build/Deployment Release Maintenance SDLC IN DETAIL ...

Software Testing Life Cycle (STLC)  defines the steps/stages/phases in testing of software. However, there is no fixed standard of STLC in the world and it basically varies as per the following: Software Development Life Cycle Whims of the Management Nevertheless, Software Testing Life Cycle, in general, comprises of the following phases: Phase Activity Deliverables Necessity Requirements/Design Review You review the software requirements/design (Well, if they exist.) Review Defect Reports Curiosity Test Planning Once you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests. Test Plan Test Estimation Test Schedule Farsightedness Test Designing You design/detail your tests on the basis of detailed requirements/design of the software (sometimes, on the basis of your imagination). Test Cases /  Test Scripts /Test Data Requirements Traceability Matrix Creativity Test Environment Setup You setup the test environment (server/c...

Hi Friends :  iOS changed the mobility game, no doubt about it. It paved the way for the ‘mobile era’ by offering amazing functionality with a simple user experience.  However when it comes to testing and monitoring, working with the  iPhone /iPad mobile application can be anything but simple… As the iOS app market continues to produce record growth, challenges and complexities surrounding iOS  application testing  also continue to interfere with development. A key challenge of iOS testing is that, unlike the open-source  Android OS , Apple iOS is a closed operating system. Added complexity during the development and testing stages arises with a closed system, since users can’t extract necessary data from low level objects, which are essential for test automation. So, what’s the best approach for getting the necessary level of access to the  iOS device  – rooting (jailbreaking) or compile-time source instrumentation? Should you base your tes...

Reference: http://stackoverflow.com/questions/2137769/where-do-i-get-a-thread-safe-collectionview The following is an improvement on the implementation found by Jonathan. Firstly it runs each event handler on the dispatcher associated with it rather than assuming that they are all on the same (UI) dispatcher. Secondly it uses BeginInvoke to allow processing to continue while we wait for the dispatcher to become available. This makes the solution much faster in situations where the background thread is doing lots of updates with processing between each one. Perhaps more importantly it overcomes problems caused by blocking while waiting for the Invoke (deadlocks can occur for example when using WCF with ConcurrencyMode.Single).   using System; using System.Collections.Generic; using System.Collections.ObjectModel; using System.Collections.Specialized; using System.Linq; using System.Text; using System.Windows.Threading;   namespace ...