it's necessary to install sql server management studio on Client system for wpf applcation

If you are using SQL Server in your application, then the client computer must be able to see an instance of SQL Server in order for your app to work.
But...

You should not include SQL Server in your installation. There are a couple of reasons:
0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version.
1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version.
2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator...
3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control.
4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea!
5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.

The advantage of SQL server is almost always only in multiuser applications: if your application does not need to share it's database with other users then you should consider changing your software to use a simpler, single user database such as SQLCE, SqLite, or Access - none of which need a complicated server installation (just a couple of simple DLL files which the app installer can add as part of "normal" installation).