Register now or log in to join your professional community.
IN General ,should have over all knowledge of the work,IN which you r working.
Quality analysis is the procedure/special mode of carrying out projects specification and deliverable's within a time bound specific
QA is the tool of quality check build material
A QA mechanical piping engineer must be able to
both quality product and process control
Not to let down team quality
QA Engineer must be detail-oriented and can solve problems. They must be efficient when examining products and know how to implement practical changes to improve the quality of the products they oversee.
As a good QA professional you should know first what is your company quality objectives.
QA is different from QC, Therefore the skill sets that you must have to QA is different from the approach that you may have to QC.
QA must have the following skill sets in order to become efficient and effective.
1.) He must be knowledgeable enough to know the codes and standards applicable to the project.
2.)He should be acquainted and familiar with the project specification,contracts and detailed drawings,so that he may be able know the project requirements for testing by drafting an ITP, material requirements for materials approval,and etc.
3.)Familiarity with the authorities submission, approval and inspection
4.)Experience enough to know the correct method of works on the project so that he may be able to draft a proper and appropriate sequence of work.
5.)Should have an in-depth knowledge on each ISO documentation on the project and may be able to equate and inculcate that knowledge effectively to his project team
6.)He should have a good leadership skills , matured, good communication skills, organize and a team player
7.)Should know the procedure and processes involved in the project in terms of seeking approval ,seeking of information and closing out of site memos.
8.)Should and must have an excellent operational planning skills.
9.)Reporting and presentation skills
.)Must be updated on the daily progress on site
.)Must understand what are the procedural, documentation and processes involved during the pre, during and post handover requirements of the project
.)Should have a proper gauge/KPI for every work for continuous improvement and development.
1) Communication, 2) Team building, 3) Knowledge of work procedures, 4) Problem detection, 5) Feedback analysis
A good QA can readily identify requirements and scope out relevant negative/positive scenarios at every stage of the process. It’s your ability to envision the unanticipated curveballs that make you a great QA. Your creative approach to devising the niche-but-possible scenarios capable of undermining even the best developed systems will set you apart from the herd. Test outside the boundaries, help create better products.
As software consultant Dave Whalen puts it, the QA’s job is to tell developers and product managers their baby is ugly. Getting there early in the process is important, but so is the way you deliver the news: tread softly. As Whalen advises, building a good rapport with development teams is vital.
Finding fault is all well and good; delivering clear, actionable insight takes skill. Good QAs recognise the importance of detailed, specific information into the precise nature of a flaw, including details on how it can be reproduced. More really is more here – rather over deliver than leave senior QAs or developers continually coming back with questions. Never assume that developers or product managers will be familiar with the terms and phrases you use to describe issues – spell it out, be clear or have a frustrating work life.
QAs have input into the entire software development process. Verifying software is just one aspect of the role – but most end users aren’t interested in code, they’re interested in what any application can do for them. Your ability to offer objective insight into the validity of any features/changes/application is just as important as your ability to verify code.
Of course, picking usability holes the week before a product launches is more likely to result in arguments than any changes being implemented, so validation should take place early in the development process. Equally, your objectivity means being able to let go of minor imperfections or features you don’t personally like if they don’t have a significant negative impact. Be able to verify and validate and you’ll bring real value to your team.
Tools will come and go; sophisticated automated QA testing procedures for highly complex software mean career-minded QAs should have command of popular developer languages like Java and C#. Your ability to write automation scripts using Perl, Python, Ruby or similar will also set you on the path to QA promotion.
Software Quality Assurance engineers don’t always get the recognition they deserve, but increasing awareness of what happens when you ship bad software mean most tech companies are placing increasing value on QAs. Another reason to keep smiling.
