Wednesday, 31 August 2016

soft develpment
1. What is software development?
Software development is the process of developing software through successive phases in an orderly way. This process includes not only the actual writing of code but also the preparation of requirements and objectives, the design of what is to be coded, and confirmation that what is developed has met objectives.

Before systems development methods came into being, the development of new systems or products was often carried out by using the experienceand intuition of management and technical personnel. However, the complexityof modern systems and computer products long ago made the need clear forsome kind of orderly development process.

Typical phases of software development:
1) Identification of required software
2) Analysis of the software requirements
3) Detailed specification of the software requirements
4) Software design
5) Programming
6) Testing
7) Maintenance

In general, the development of commercial software is usually a result of demand in the marketplace, while enterprise software developmentgenerally arises from a need or a problem within the enterprise environment.
 
Related Links:
Rafeeq Ur Rehman and Christopher Paul's Introduction to software development goes into more detail about the software development process.
 
SearchVB offers a selection of resources about design and development.

2. How is software development guided? 
The software development process is almost invariably guided bysome systematic software development method (SDM). Referred to by a numberof terms, including process models,development guidelines,and systems development life cycle models (SDLC), software development methods nevertheless generally include the same development phases:
 
  • The existing system is evaluated and its deficiencies identified, usually through interviewing system users and support personnel.
  • The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.
  • The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.
  • The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.
  • The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, andthe old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.
  • Once the new system is up and running for awhile, it should be exhaustively evaluated. Maintenance must be kept up rigorously at all times.Users of the system should be kept up-to-date concerning the latest modificationsand procedures.
The systems development life cycle model was developed as a structured approach to information system development that guides all the processesinvolved from an initial feasibility study through to maintenance of thefinished application. SDLC models take a variety of approaches to development.

 
Systems development life cycle models include:
 
· The waterfall model: This is the classic SDLC model, with a linear and sequential method that has goals for each developmentphase. The waterfall model simplifies task scheduling, because there areno iterative or overlapping steps. One drawback of the waterfall is thatit does not allow for much revision.
 
· Rapid application development (RAD): This modelis based on the concept that better products can be developed more quicklyby: using workshops or focus groups to gather system requirements; prototyping and reiterative testing of designs; rigid adherence to schedule; and less formality of team communications such as reviews.
 
· Joint application development (JAD): This modelinvolves the client or end user in the design and development of an application,through a series of collaborative workshops calledJAD sessions.
 
· The prototyping model: In this model, a prototype (an early approximation of a final system or product) is built, tested,and then reworked as necessary until an acceptable prototype is finallyachieved from which the complete system or product can now be developed.
 
· Synchronize-and-stabilize: This model involves teams working in parallel on individual application modules, frequently synchronizing their code with that of other teams and stabilizing code frequently throughout the development process.
 
· The spiral model: This model of development combines the features of the prototyping model and the waterfall model. The spiral model is favored for large, expensive, and complicated projects.
 
Related Links:
Peter H. Gregory's SearchNetworking article explores "Security in the software development life cycle."
 
The CTG also offers a white paper on the "Systems Development Process Model."
 
Bender RBT provides their document on "Systems Development Life Cycle Objectives and Requirements."
 
 

3. How has the open source development process influenced software development in general?
Open source software is developed collaboratively; source code is freely available for use and modification. The open source movement arose because some developers came to believe that competition amongst vendors leads to inferior products and that the best approach to development isa collaborative one.

The OSI (Open Source Initiative) is an industry body that certifies products as open source if they conform to a number of rules:
 
· The software being distributed must be redistributed to anyone else without any restriction
 
· The source code must be made available (so that the receiving party will be able to improve or modify it)
 
· The license can require improved versions of the software to carry a different name or version from the original software
 
Despite its emphasis on the collaborative process, the biggest influence that open source has had on software development in general may be through competition: by competing with proprietary software products, open source products force vendors to work that much harder to hold their market share in the face of viable open source alternatives.
 
Related Links:
The OSI has a Web site.
Margie Semilof's SearchWin2000 article is called "Battening down the Windows: Open source vs. commercial tools."
Jan Stafford's SearchEnterpriseLinux article is called "Perens: IT pros must lobby for open source."
 

4. What are some generally accepted best practices common to all or most development models?
Here's a collection of some of the top tips from a variety of industry sources:
 
· Make sure that you've chosen a systems development life cycle model that suits your project, because every one of the processesinvolved depends on the model. That said, however, implementing any modelis better than none -- much of the success of a project depends upon howscrupulously the model is adhered to.
 
· Reuse software components when it's appropriate, but don't use code that doesn't work perfectly for its intended purpose just because you have it on hand.
 
· Be very thorough in gathering requirements, ensuring that all parties agree on what they are -- and make sure you document them.
 
· Don't promise the moon, if you can't deliver it. Avoidletting someone who isn't fully informed negotiate with the client.
 
· Make sure that the architecture you've chosen is appropriate for the application you're building. To retain perspective, you might want to look at the smaller picture and plan the architecture incrementally.
 
· Change is part of life, including software development. You have to accept that various things -- requirements, for example -- are likely to change throughout the life of the project. Keep control of them, but not too rigidly.
 
· Set up peer review processes for every element of the project.
 
· Design thoroughly and with care, but remember the KISSprinciple: Keep it simple.
 
· In your project plan, split big projects into manageable chunks, with concrete milestones and deadlines.
 
· Ensure accountability: make sure that deadlines are clear and that people have to report on whether they made them, and explain why not if they don't.
 
· Implement quality control procedures throughout the project.
 
· Test exhaustively -- there's no point in doing a cursory run through only to have an application fail when you run it for the client.
 
· After the project is completed, conduct a thorough post-mortem, with everyone involved. You'll see what worked well and what should havebeen differently, and your future projects will benefit.
 
Related Links:
The IBM Web site offers Mike Perk's article, "Best Practices for Software Development Projects."
IEEE Software promotes the "Daily Build and Smoke Test" as a development best practice.
The Standish group provides a "Recipe for Success."
W. Edwards Deming offers more advice in his list, 14 Points for Software Development.
Johanna Rothman advises developers to write out goals inplain English to help managers, team members and stakeholders find consensusin this Software Development Magazine article. (requires free registration)
 
 

5. What are some common mistakes in software development?
According to a Standish Group report, corporations in the United States spend over $275 billion every year on software development projects, many of which are doomed to failure. Research by the group found that over 80% of projects fail for various reasons, and that fully 30% of projectswere cancelled prior to completion because of poor execution.
 
David B. Stewart, at the University of Maryland, set out to document the 10 most common mistakes of software development. He found, however,that the sheer number of errors that were commonly practiced made it impossible to keep the number to ten. He ended up calling his article "Twenty-FiveMost Common Mistakes with Real-Time Software Development." Even so, afterthe title had been established, he found another five errors so common thathe felt compelled to add them.
 
According to Dr. Michael Stovsky, of Stovsky and Associates, the most common project problems are due to failure to manage project elements successfully:
 
· Requirements are not clearly and accurately defined, and agreed upon by all concerned.
 
· Resources are not adequately planned and allocated.
 
· Threats to project success are not clearly detected, identified, and protected against.
 
· Critical path analysis is omitted, or poorly executed.
 
· The project's progress is not tracked adequately.
 
· Quality management is not carried out well enough throughout the life of the project.
 
· Too little data is collected, or data is ignored or poorly understood.
 
Correcting flaws identified during software security audits is expensive and time consuming. Worse, vast resources are spent on containing and recovering from exploits. Fortunately, providing development staff with the knowledge and tools to avoid many of these pitfalls is easy and inexpensive.
 


Related Links:
In this paper, Dr. Michael P. Stovsky explores Common Mistakes in Software Project Management.

6. Given a particular process model, is there a set of tools(a development environment) to support it?
In general, a process model usually begins as a philosophy of "who does what development when" rather than a rigid methodology complete with tools. For example, rapid application development (RAD) is an approach that can make use of existing development tools. In general, tools for supporting all or part of a process model tend to arrive later, if at all.

Historically, development tools have focused on the code-building, code archive management, documentation, testing, and packaging parts ofthe process, sometimes offered as a suite. Such a suite is generally knownas an integrated development environment (IDE).

A set of tools for managing or supporting a development project is generally known as a computer-assisted software environment (CASE). A number of companies offer products that support early stages of development such as requirements gathering, design prototyping, and data modeling. A number of these provide tools that support data modeling with the Unified Modeling Language. Overall, there is a trend toward providing all or most of the tools for a development project in a single product or related set of products.

Today, the main code-building development environments or program suites come from Microsoft with its Visual Studio and Visual Studio .NET, providing support for Visual Basic, Visual C#, Visual C++, and Visual J#; Sun Microsystems with its Java 2 Enterprise Environment; and numerous software vendors such as Borland who repackage these environments with some value-added features. Recently, almost all providers of software development environments have added features that enable the software to be used on the Web.
 
Related Links:
Microsoft provides a case study of a company that created an accounting system with its VisualBasic .NET product and additional products from PDSA.

The Caldera OpenLinux Workstation describes several different integrated development environments it provides for Linux and Unix systems.

Knowledgestorm lists many products that describe themselves as integrated development environment products.

Carnegie-Mellon Software Engineering Institute answers the question "What is a CASE Environment?"
 
 

7. How do you choose the "right" programming language for your project?

For most projects, the right language is easy to choose. Your company may have standardized on a particular development environment and language (and you may have been hired because you were already familiar with the language). Or you may be updating or enhancing an existing program; it's almost always best to use the same language the existing program is written in. In some cases, however, someone will need to select the best (or, since the best may be somewhat arguable, at least an appropriate language). In somecases, you or your team of developers may need to know several languages fordifferent purposes.

General truisms about programming languages are that:
 
  • Perl or a similar script language is most suitable for small tasks and sometimes acting as a program that goes between other, largerprograms.
  • Visual Basic is most suitable for relatively novice programmers and relatively simple programs.
  • Java, C++, or comparable languages like Python and Tcl aremost suitable for larger applications using object orientation as a designmodel.
  • C is most suitable for programs where efficiency and performance are the primary concern.
  • The appropriate assembler language is most suitable where the program is relatively short and high performance is critical.
Where constraints permit, some programmers may favor one object-oriented language over another (for example, Java, C++, Python, or Tcl). A programmer with skills in C is likely to prefer C++, which combines the proceduraland other concepts and syntax of C with object-oriented concepts.
 
Related Links:
Outback Software compares three object-oriented languages: C++, Smalltalk, and Java.

Kuro5hin compares three Visual Studio languages: C#, C++, and Java.

Jason Voegele's table compares 21 features of nine pure or hybrid object-oriented languages, including Perl and Basic.

The Open Directory Project offers a list of links relating to programming language comparisons.
 


 
8. What are some trends regarding the future of software development? 
Blogs  - A growing number of big-name softwaredevelopers are finding they can make better software applications if theyshare information with potential customers from the start and incorporate customer feedback into development decisions. While developers of gamessoftware have used this method for years, business software makers are nowalso catching on and using blogs (Web logs) as an important part of the development process.
Big-name support for independent software vendors (ISVs) -  Big players like Microsoft, IBM, and Sun have recognized that they cannot fill every niche industry's software demands, so they have begun to activelyseek partnerships with small ISVs, in hopes that by encouraging ISVs to focuson nichy vertical industry applications, everyone will benefit.
 
Component-based development - In this approach, softwareis developed in modules that are linked dynamically to construct a completeapplication. Charles Simonyi (creator of the WYSIWYG editor) believes thateventually, software development will become so modular that  even lay-peoplewill be able to assemble  components effectively to create customizedsoftware applications.
 
Continued improvements in refactoring tools - Eric Raymond,a leading philosopher about program development, maintains that the conceptof refactoring is consistent with the idea of get-something-working-now-and-perfect-it-laterapproach long familiar to Unix and open source programmers. The idea is alsoembodied in the approach known as Extreme Programming. As software applicationsbecome larger, better refactoring tools will be required to maintain codebases and diagnose bugs.
 
Outsourcing - Using this approach, software companies hire employees around the world to take advantage of time zone and labor/cost differences.Proponents say that in effect, software development teams now have a 24-hourwork day, and are able to provide fast turn-around. Detractors say that outsourcingparts of a project leads to sloppy coding and only works if there is a highdegree of coordination regarding modularized tasks, and above-average communicationwithin the team.
Related Links:

Rormer CNET developers Dan Seewer and Kevin Cobb discuss the future of software development.


Charles Simonyi, creator of the WYSIWYG, is in the process of designing programming tools for the future that are so simple that even laypeople can use them.
 
Developers are using blogs to get closer to their users.
IBM DeveloperWorks is one of many free resources available for developers

 


 
10. Software Development Words-to-Go Glossary:

Browse through instant messaging vocabulary in a handy printable glossary.
 

11. Self-assessment:

After you've looked at the glossary, quiz yourself to see what you've learned about software development terms.


 
This was last updated in April 2010

Monday, 29 August 2016

 SECREEN CAPTURE ON PC

 SECREEN CAPTURE ON PC

Hi friends,
      Tody i will tell u about how to take secreen capture on pc.For this parpus presswindows and prntscr togather.

plese like and comment before leave
Use VLC As A Screen Recording Tool

Use VLC As A Screen Recording Tool

Hi friends,
VLC player is touted as the Swiss Army Knife of all media players, and not without reason. While it practically plays every media file that you throw at it, what’s amazing about VLC is that it does so much more beyond that.
One of VLC’s potential use-cases can be using it as a screen capture/recording tool. Sure, there are other free apps out there that are better equipped for this particular task, but there might be situations when you need to do some quick screen recording, and don’t have a recorder app to work with.
Screen capturing with VLC is fairly simple, and requires just a few steps –
  • Open VLC player, and click on View –> Advanced Controls. A few more buttons will appear on the interface.
  • Now, press Ctrl + C (or, go to Media –> Open Capture Device…).
  • In the new window, set Capture Device to “Desktop”, and the Desired frame rate to “10 fps” (frames per second). You can set a higher value if you want, but 10-12 fps will make just fine screencasts.
  • Click on the Play button, and VLC will start showing your desktop. Make sure VLC isn’t maximized, else all you’ll see is an endless stream of VLC-inside-VLC windows!
  • Click on the Record button to start recording. You should preferably minimize the VLC window so that it doesn’t show up in your screencast.
  • Do whatever you need to show in your screencast, then restore the VLC window and click on the Record button again to stop recording.
  • VLC will automatically save an AVI file in your Videos folder, which you can then share or do whatever you want with it.
  • Before you get all excited about this VLC feature, here are some pretty serious limitations you should keep in mind.
    • There is no way to use your voice in your screencast. You’ll have to record your voice separately and stream that audio file along with the desktop recording. Clicking on the recording button will then save the audio along with the screencast.
    • You can only record your entire desktop in RAW format. There is no way to record a part of the desktop. This leads to enormous sized videos (like in GBs!) even for relatively short screencasts. For smaller videos, you’ll have to compress your video using H.264 or WebM.
    • As I said before, VLC shouldn’t be your go-to screen recording app, but it is certainly a useful feature to have nevertheless.
Run Android apps on your Windows PC

Run Android apps on your Windows PC

     

         ARC
Android’s application ecosystem has proven to be versatile and very developer-friendly, after a bit of a slow start. You are free to develop an app for Android and publish it to the Play Store with minimal restrictions. This has led to a plethora of really cool Android apps, some of which aren’t available on iOS or other platforms. Running Android apps usually requires an Android smartphone or tablet — obviously! — but what if you currently use iOS or another mobile OS, and want to try out Android without actually getting an Android device?
Well, fortunately, with a little leg work, you can run Android apps on a regular old Windows PC. There are a few different ways to go about it, each with their own strengths and weaknesses.

ARC Welder for Chrome

Probably the easiest way to get Android apps running on your Windows PC is to use Google’s ARC Welder Chrome extension (ARC stands for App Runtime for Chrome). Since this is a Chrome extension, it’s not only restricted to Windows PCs — you could also use this method on a Chromebook or Mac. The process is much the same no matter which platform you’re using Chrome on. Simply head to the Chrome Web Store and grab theARC Welder extension to get everything you need installed.
ARC Welder is a beta tool, and it’s mainly directed at developers. Still, the process of loading an app is quite simple. You’ll need an APK to load into ARC Welder (known as sideloading), which you can get from backing up an app on your physical Android device, or you can download an APK from any number of places on the internet. We don’t recommend you download paid apps and games from shady websites, though. There are a few sites that archive legitimate free APKs, like APK Mirror.
ARC 2
When you’ve got your APK ready to go, you can open ARC Welder from the Chrome app list and point it at the file. Then you just have to choose how you want the app to render — landscape/portrait, tablet/phone, and whether you want it to have clipboard access. Not every app will run, and some of those that do will be missing components. ARC Welder doesn’t currently have native support for Google Play Services (unless you’re the app developer and have access to the app’s code), so Google’s apps and some third-party ones will refuse to run.
Apps and games that work tend to run very well in ARC. You should get almost full functionality from apps like Evernote, Instagram, and even Flappy Bird. You can only have one app installed in Chrome via ARC Welder at a time, so you need to go back to the install dialog whenever you want to change to a different one.
The sideloading requirement along with the limit of one app at a time makes ARC Welder less than ideal for running Android apps on Windows on a daily basis. However, if you just want to get one up and running for testing or just to play around, this should be your first stop.
Android Emulator

The Android emulator

The next most straightforward way to get Android apps running on a PC is to go through the Android emulator released by Google as part of the official SDK. The emulator can be used to create virtual devices running any version of Android you want with different resolutions and hardware configurations. The first downside of this process is the somewhat complicated setup process.
You’ll need to grab the SDK package from Google’s site and use the included SDK Manager program to download the platforms you want — probably whatever the most recent version of Android happens to be at the time (5.1 at the time of publishing). The AVD manager is where you can create and manage your virtual devices. Google makes some pre-configured options available in the menu for Nexus devices, but you can set the parameters manually too. Once you’ve booted your virtual device, you’ll need to get apps installed, but the emulator is the bone stock open source version of Android — no Google apps included.
Since there’s no Play Store, you’ll need to do some file management. Take the APK you want to install (be it Google’s app package or something else) and drop the file into the tools folder in your SDK directory. Then use the command prompt while your AVD is running to enter (in that directory) adb install filename.apk. The app should be added to the app list of your virtual device.
The big upside here is that the emulator is unmodified Android right from the source. The way apps render in the emulator will be the same as they render on devices, and almost everything should run. It’s great for testing app builds before loading them onto test devices. The biggest problem is that the emulator is sluggish enough that you won’t want to make a habit of running apps in it. Games are really out of the question as well.
androidx86

Android PC ports

If you don’t mind a little extra hassle, you can have a more fluid Android app experience by installing a modified version of the OS on your PC. There are a few ports of Android that will run on desktop PCs, but support is somewhat limited because of the extensive hardware configuration options for PCs. The two leading choices for a full Android installation on PC are Android on Intel Architecture (UEFI-equipped devices) and the Android-x86 Project (pictured above).
Neither one is in a perfect state, and you’ll need a supported piece of hardware, like the Dell XPS 12 for Intel’s version or the Lenovo ThinkPad x61 Tablet for Android-x86. You could install them over top of Windows, but that’s not the best idea. The smarter way would be to create a separate hard drive partition and install Android there.
If your hardware isn’t supported by either of these projects, you can also try installing them in VirtualBox, which should be a little faster than the official Android emulator. It probably still won’t be good enough for games, but most apps should install and run correctly. Also, you’ll have to install the apps you want manually, as there’s no Google Play integration here either.

BlueStacks App Player

If you’re looking to get multiple apps and games up and running on your computer with the minimum of effort, BlueStacks is your friend. The BlueStacks App Player presents itself as just a way to get apps working, but it actually runs a full (heavily modified) version of Android behind the scenes. Not only that, but it has the Play Store built-in, so you have instant access to all of your purchased content. It actually adds an entry to your Google Play device list, masquerading as a Galaxy Note II.
The BlueStacks client will load up in a desktop window with different app categories like games, social, and so on. Clicking on an app or searching does something unexpected — it brings up the full Play Store client as rendered on tablets. You can actually navigate around in this interface just as you would on a real Android device, which makes it clear there’s a lot more to BlueStacks than the “App Player” front end. In fact, you can install a third-party launcher like Nova or Apex from the Play Store and set it as the default. The main screen in BlueStacks with the app categories is just a custom home screen, so replacing it makes BlueStacks feel almost like a regular Android device.
Bluestacks
BlueStacks App Player, in the Play Store
Having full Play Store access means you won’t be messing around with sideloading apps, and BlueStacks manages to run everything impressively. Most games are playable, but keep in mind you’ll have trouble operating many of them with a mouse. If your PC has a touch screen, you can still use apps and games that rely on more than one touch input. BlueStacks can essentially make a Windows 8 tablet PC into a part-time Android tablet. BlueStacks calls the technology that makes this possible “LayerCake” because Android apps run in a layer on top of Windows.
The only real issue with BlueStacks is that it’s not running a standard Android build. All the alterations the company made to get apps working on a PC can cause issues — some apps simply fail to run or crash unexpectedly. This customized environment is also of little value as a development tool because there’s no guarantee things will render the same on BlueStacks as they might on a real Android device without all the back-end modifications. It’s also a freemium service with a $2 pro subscription, or you can install a few sponsored apps.

So what’s the best way?

If you need to test something with the intention of putting it on other Android devices, the emulator is still the best way to give builds a quick once-over on a PC before loading them on to Android phones or tablets. It’s slow, but standardized, and you’ll be able to see how things will work on the real deal. The Android PC ports are definitely fun to play with, and performance is solid when you get apps running, but they can be finicky.
If you’re interested in getting more than a handful of apps running on your PC so you can actually use and enjoy them, BlueStacks App Player is the best solution. It’s fast, has Play Store access, and works on multitouch Windows devices. ARC Welder is also something to keep in mind if you only need to use one app at a time. The setup is easy and it’s completely free.
   HOW TO WITH DRAW MONEY FROM PYAZA BENK IN PAKISTAN

   HOW TO WITH DRAW MONEY FROM PYAZA BENK IN PAKISTAN

Hi friends,
    Payza which was formerly known as Alertpay is like an online international bank covering more than 190 countries. If you work online then you easily receive money from a person of any country into your Payza account. Not only you can receive money online, you can also send money online. You can trust Payza service as it is an international company and millions of people are already using it.
Formerly Payza provided the service to withdraw money using credit card or check. But then in the beginning of 2012 Payza introduced its prepaid debit card. After that it closed all others ways of withdrawing money except bank wire and the debit card. If you want to withdraw money using the bank wire than your account must be verified. But then again to verify your account you cannot use credit card or check option. The only option that you are left with is to use your local bank account to verify your Payza account. Only after that you will be able to withdraw money using the bank wire service. The other option is to use the prepaid debit card to make a withdrawal.
To deposit money using your local bank account you need to login into your account. After that click deposit money and enter the amount of money that you wish to deposit. Now click the next button. After that in the next payment your bank name and address will be shown. You will have to pay 20 dollars for this transaction and it will take 4 to 5 working days before the transaction is complete. In this way your account will be verified and you will be able to use the bank wire service.
There is another way to verify your account which much easier and free too. You can verify your account using some authentic documents. For example you can use your CNIC card and a utility bill to verify your account. The name and address on both the documents should be same and don’t forget to scan both the sides of your CNIC. After scanning your authentic documents you can start the account verification process. Start by uploading your documents on the Payza support page. After that click my account support and then check for my account verification inquiry. You need to be patient because it will take four to five working days before the transaction is complete.
The best and the easiest way to withdraw money from your Payza account is to use Payza prepaid debit card. For this purpose firstly be sure that there are $20 in your account. After that open your account and click the link for ordering the debit card. You will need a photo ID and one other document to verify your address. When prompted to upload a photo ID use your CNIC card provided by the government and when prompted to verify your address upload a scan of one of your utility bills. This is all you need for your Payza debit card. It can take 30 to 60 days before you can receive your debit card in Pakistan. So be patient in this case.

USE YOUR ATM DEBIT CARD TO WITHDRAW PAYZA MONEY IN PAKISTAN

When you open a Bank account in Pakistan with Standard Chartered or UBL (United Bank), they give you an ATM Card for withdrawing your money using your card. That card also works for online transactions same as Visa Debit Card. So if you have an account at UBL or SCB then just call the help line and activate your card for online usage. Now come back to your Payza Account >> Verification page and verify your ATM Visa Debit Card, when it is verified, Payza will deduct $3 or $4 from your card just for checking purpose. So you must have some rupees in your Bank account. That amount will be yours in your Payza account. So this way, Payza will verify your Debit Card and then you’ll be able to transfer your Payza funds to your ATM Visa Debit Card. This is something really easy which can be done by anyone having a Bank account in Pakistan.
Let us know your thoughts and questions  in the comment section. Stay Tuned!
How to Control an Android Device From Your PC

How to Control an Android Device From Your PC


Look ma, no hands! With a simple VNC  (Virtual Network Computing) app on your Android phone, tablet or mini PC, you can control your mobile device from a browser window on your Windows computer. Though the performance of this remote login is too slow for serious work or play, there are a few reasons that you might want to control an Android device from your PC.
When you're entering complex settings such as your email server name and password, it's sometimes easier to enter a lot of text with your computer's physical keyboard, which is available under VNC. With VNC, you can control an Android  device on the other side of your house, setting an alarm on the phone that's charging in your bedroom while you sit in the livingroom. Best of all, if you want to turn your Android mini PC into a server, you can control the stick from your laptop, without even having to plug it into a TV. 
Here's how you can control an Android device from a Windows PC.
1. Install VMLite VNC Server ($7.99) on your Android device (phone, tablet mini PC). If your device is rooted, you can try a free alternative such as Droid VNC Server, but if not, VMLite is your only real choice.
3. Enable USB debugging on your phone. You can find the USB debugging setting under Developer Options in the Android settings menu
Note: If your phone doesn't have a Developer Options submenu under Settings, you can make one appear by navigating to Settings -> About Device and tapping on the Build Number five times. Many newer phones such as the Galaxy S4 come with their developer menus hidden by default.
4. Attach your phone to your PC. Your computer will attempt to install ADB (Android Developer Bridge) drivers for your phone. If it fails to find them, you may need to download the appropriate drivers from the manufacturer.
5. Install and launch the  VMLite Android App Controller on your PC. You can download it from vmlite.com.
6. Click the Start VMLite VNC Viewer button  in the App Controller program. If your phone is rooted, you can simply launch the VMLite VNC Server on your phone and hit the Start button in it.
The VMLite VNC Server app will launch on your phone with its server started. If the server does not start, you may need to try again and make sure you have the right ADB driver.
7. Establish a connection between your PC and Device in one of two ways:
A. Click USB Connect and OK when the app controller prompts you for port numbers if you plan to keep your Android device plugged into your PC. 
B. Unplug your Android device and connect it to the same Wi-Fi network as your PC in order to establish a wireless connection.

8. Navigate to the VNC server's address in your browser. If you are connected via USB,navigate to http://localhost:5801 or, if you are connected via Wi-Fi, enter the IP address displayed under "Browser:" on your Android device.
If you prefer a standalone application, you can install a free VNC client such as VNC Viewerand use the address under "VNC viewer" to connect. 
9. Click Start HTML VNC Viewer or Start Java Applet VNC Viewer on the web page which appears in your browser. The HTML VNC Viewer runs in a tab while the Java applet VNC viewer opens in its own window and requires the Java plugin to be installed. In our tests, both performed similarly.
Once you launch either viewer, you will be able to control your Android device from a window on your desktop. You can navigate through the entire operating system and use any apps you want with a click of your mouse and enter text with your PC keyboard or swipe gestures.

Unfortunately, performance is extremely sluggish so don't expect to do any gaming or video viewing. 

VMCLITE VNC SERVER SETTINGS TWEAKS

You can tweak a few settings to in the VMLite VNC Server app, by entering the menu and selecting Settings.
If your device is rooted and you want to start VMLite VNC Server every time it boots, check Start server at boot.
If the screen image is too large to fit in your PC browser without forcing you to scroll, select Screen scaling and switch from 1.0 to 0.5.