I recommend that as part of your project you start a glossary of terms - use the ones currently in use in the company. Get agreement on the terms from the project team members so that you are all talking the same language. The definitions on Joe's blog are very good and if I needed to set definitions up I would start with these and adapt them to the company I was at.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
It is never late to tailor SDLC and come up with new and meaningful terms in testing. Terms are used variably in IT but I hope your new company will appreciate your intiative to use appropriate terms during testing. Glossary provided by Lynee is good1. Rock your team with new initiatives.
While exact definitions of terms used at various places may vary and this is sometimes acceptable, there's a certain limit to how far they should deviate from typical industry use. It sounds like your current company has it backwards. I'd research how these terms are most commonly used and try to influence some change to less confusing terminology. Even if this project is almost over, surely there will be another one coming up or further maintenance on it. Almost everywhere I've been uses something similar to this:
Integration: Testing the connection of two modules, sometimes at a unit-testing level.
System: Connecting two or more components or applications together and testing at the use-case level. Can also be end-to-end testing.
<font size="2" face="Verdana, Arial, Helvetica">deepa18, don't spam the forums with your advertising infested site that has no relavance to anything discussed here.. you posted links for it twice today.