Become a Lie Detector
How to Detect Lies
Become a Lie Detector
Introduction to Detecting Lies:
The following techniques to telling if someone is lying are often used by police, and security experts. This knowledge is also useful for managers, employers, and for anyone to use in everyday situations where telling the truth from a lie can help prevent you from being a victim of fraud/scams and other deceptions.
Warning: Sometimes Ignorance is bliss; after gaining this knowledge, you may be hurt when it is obvious that someone is lying to you.
Signs of Deception:
Body Language of Lies:
• Physical expression will be limited and stiff, with few arm and hand movements. Hand, arm and leg movement are toward their own body the liar takes up less space.
• A person who is lying to you will avoid making eye contact.
• Hands touching their face, throat & mouth. Touching or scratching the nose or behind their ear. Not likely to touch his chest/heart with an open hand.
Emotional Gestures & Contradiction
• Timing and duration of emotional gestures and emotions are off a normal pace. The display of emotion is delayed, stays longer it would naturally, then stops suddenly.
• Timing is off between emotions gestures/expressions and words. Example: Someone says “I love it!” when receiving a gift, and then smile after making that statement, rather then at the same time the statement is made.
• Gestures/expressions don’t match the verbal statement, such as frowning when saying “I love you.”
• Expressions are limited to mouth movements when someone is faking emotions (like happy, surprised, sad, awe, )instead of the whole face. For example; when someone smiles naturally their whole face is involved: jaw/cheek movement, eyes and forehead push down, etc.
Interactions and Reactions
• A guilty person gets defensive. An innocent person will often go on the offensive.
• A liar is uncomfortable facing his questioner/accuser and may turn his head or body away.
• A liar might unconsciously place objects (book, coffee cup, etc.) between themselves and you.
Verbal Context and Content
• A liar will use your words to make answer a question. When asked, “Did you eat the last cookie?” The liar answers, “No, I did not eat the last cookie.”
•A statement with a contraction is more likely to be truthful: “ I didn’t do it” instead of “I did not do it”
• Liars sometimes avoid “lying” by not making direct statements. They imply answers instead of denying something directly.
• The guilty person may speak more than natural, adding unnecessary details to convince you… they are not comfortable with silence or pauses in the conversation.
• A liar may leave out pronouns and speak in a monotonous tone. When a truthful statement is made the pronoun is emphasized as much or more than the rest of the words in a statement.
• Words may be garbled and spoken softly, and syntax and grammar may be off. In other
words, his sentences will likely be muddled rather than emphasized.
Related Books:
Never be Lied to Again
Body Language
Other signs of a lie:
• If you believe someone is lying, then change subject of a conversation quickly, a liar follows along willingly and becomes more relaxed. The guilty wants the subject changed; an innocent person may be confused by the sudden change in topics and will want to back to the previous subject.
• Using humor or sarcasm to avoid a subject.
Final Notes:
Obviously, just because someone exhibits one or more of these signs does not make them a liar. The above behaviors should be compared to a persons base (normal) behavior whenever possible.
Most lie detecting experts agree that a combination of body language and other cues must be used to make an educated guess on whether someone is telling the truth or a lie.
Difference between Project and product and project scope and product scope
Project versus Product In lifecycle terms, the idea of building, creating or producing a product is conceived, then considered for funding. When approved it becomes in investment that needs be managed. While you are creating the product you are in the project lifecycle. Once the product is built then the project lifecycle ends, but the product’s life continues. This phase of the product’s life is refered to as Steady State or Operations & Maintenance. This may be 1-2 years, or 50 years. Dept of Defence refers to the entire product life, from conception to demise as a “Program.” Don’t confuse this with PMI’s definition of Program Management (a group of related projects). Project Scope versus Product Scope From the scenarion I describe above, Project Scope covers the definition and management of the project phase in hte product’s life. This includes cost, schedule, quality, etc. that PMBOK describes. Product Scope defines the specifications of the item that was created, including how it will be used, under what conditions it should provide service/function, and the cost to own and operate it. by Friar
DR. ZAKIR NAIK – PRESIDENT, IRF
|
DR. ZAKIR NAIK – PRESIDENT, IRF A medical doctor by professional training, Dr. Zakir Naik is renowed as a dynamic international orator on Islam and Comparative Religion. Dr. Zakir Naik clarifies Islamic viewpoints and clears misconceptions Dr. Zakir is popular for his critical analysis and convincing answers to challenging questions posed by audiences after his public talks. In the last 6 years (by the year 2002), Dr. Zakir Naik has delivered mo He has successfully participated in several symposia and dialogues with prominent personalities of other faiths. His public dialogue with Dr. William Campbell (of USA), on the topic, “The Qur’an and the Bible in the light of Science” held in city of Chicago, U.S.A., on April 1, 2000 was a resounding success. Sheikh Ah Dr. Zakir Naik appears regularly on many international T.V. Channels in more than 100 countries of the world. He is regularly invited for T.V. and Radio interviews. More than a hundred of his talks, dialogues, debates and symposia are available on VCDs and DVDs. He has authored books on Islam and Comparative Religion. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
BIO-DATA DR. ZAKIR ABDUL-KARIM NAIK
ISLAMIC RESEARCH FOUNDATION
|
about Islam, using the Qur’an, authentic Hadith and other religious Scriptures as a basis, in conjunction with reason, logic and scientific facts. He is 43 years old.
re than 1000 public talks in the U.S.A., Canada, U.K., Saudi Arabia, U.A.E., Kuwait, Qatar, Bahrain, Oman, South Africa, Italy, Mauritius, Australia, Malaysia, Singapore, Hongkong, Thailand, Guyana (South America), Trinidad and many other countries, in addition to numerous public talks in India.
med Deedat, the world famous orator on Islam and Comparative Religion, who had called Dr. Zakir, “Deedat plus” in 1994, presented a plaque in May 2000 awarded to Dr. Zakir Abdul-Karim Naik for his achievement in the field of Da’wah and the
Designing Data & Process Placement
To allocate the processes and data to specific system processor nodes.
The Physical Data Model and Physical Process Model, or the Object Model, identify everything that must be placed within the distributed architecture.
Define Division of Client and Server Processing
Finalize the processing to take place on the server and the client. There are various degrees of division ranging from monolithic (all processing on the server) to fully distributed.
Re-examine the processes defined to ensure that the distribution of data and processes as defined in the data and process placement strategy remains appropriate for the processes as designed.
Define Clients and Servers
The data and process placement strategy defines the approach to distribution of data and processes.
Identify the distribution of data and processes among the different client and server nodes in the network. This could be a geographic distribution, such as branches located across a region, or a distribution by business division, for example, sales and finance.
Identify all server nodes in the system and allocate server processes and interfaces to appropriate physical processor nodes. Identify all client nodes in the system and allocate client processes and interfaces to appropriate physical client nodes.
Identify data that will reside on each node. Consider the issues associated with distributed data. Check that all processes, which require access to data, map against data that exists on that node, or that the appropriate interface exists to access the required data on a server.
Identify all servers that the client nodes must access and note the data volumes and frequency that the data access will require.
Re-examine the communications network design to ensure that there are no adverse effects caused by data and process placement design decisions.
CraigBorysowich (CTT)
Requirements List Deliverable & Sample
To formally define the requirements that will be addressed by the project in a formal list of requirements statements that are feasible, testable, consistent with each other, and clearly and properly stated.
Description
Multiple page listing with each requirement separately itemized.
Sample
Sample Requirements List:
Requirements List Deliverable & Sample
Craig Borysowich (Chief Technology Tactician)
web development life cycle
Web sites can also be developed with certain methods with some changes and additions with the existing software development process. Let us see the steps involve in any web site development.
1. Analysis:
Once a customer is started discussing his requirements, the team gets into it, towards the preliminary requirement analysis. As the web site is going to be a part of a system, It needs a complete analysis as, how the web site or the web based application is going to help the present system and how the site is going to help the business. Moreover the analysis should cover all the aspects especially on how the web site is going to join the existing system. The first important thing is finding the targeted audience. Then, All the present hardware, software, people and data should be considered during the time of analysis. For example, if a company XYZ corp is in need of a web site to have its human resource details online, the analysis team may try to utilize the existing data about the employees from the present database. The analysis should be done in the way, that it may not be too time consuming or with very less informative. The team should be able to come up with the complete cost-benefit analysis and as the plan for the project will be an output of analysis, it should be realistic. To achieve this the analyst should consult the designers, developers and testers to come up with a realistic plan.
Input: Interviews with the clients, Mails and supporting docs by the client, Discussions Notes, Online chat, recorded telephone conversations,Model sites/applications etc.,
Output: 1. Work plan, 2. Cost involved, 3. Team requirements, 4. Hardware-software requirements, 5. Supporting documents and 6. the approval
2. Specification Building:
Preliminary specifications are drawn up by covering up each and every element of the requirement. For example if the product is a web site then the modules of the site including general layout, site navigation and dynamic parts of the site should be included in the spec. Larger projects will require further levels of consultation to assess additional business and technical requirements. After reviewing and approving the preliminary document, a written proposal is prepared, outlining the scope of the project including responsibilities, timelines and costs.
Input: Reports from the analysis team
Output: Complete requirement specifications to the individuals and the customer/customer’s representative
3. Design and development:
After building the specification, work on the web site is scheduled upon receipt of the signed proposal, a deposit, and any written content materials and graphics you wish to include. Here normally the layouts and navigation will be designed as a prototype.
Some customers may be interested only in a full functional prototype. In this case we may need to show them the interactivity of the application or site. But in most of the cases customer may be interested in viewing two or three design with all images and navigation.
There can be a lot of suggestions and changes from the customer side, and all the changes should be freezed before moving into the next phase. The revisions could be redisplayed via the web for the customer to view.
As needed, customer comments, feedback and approvals can be communicated by e-mail, fax and telephone.
Throughout the design phase the team should develop test plans and procedures for quality assurance. It is necessary to obtain client approval on design and project plans.
In parallel the Database team will sit and understand the requirements and develop the database with all the data structures and sample data will also be prepared.
Input: Requirement specification
Output: Site design with templates, Images and prototype
The possible steps in the process of web site engineering.
4. Content writing:
This phase is necessary mainly for the web sites. There are professional content developers who can write industry specific and relevant content for the site. Content writers to add their text can utilize the design templates. The grammatical and spelling check should be over in this phase.
Input: Designed template
Output: Site with formatted content
5. Coding:
Now its programmers turn to add his code without disturbing the design. Unlike traditional design the developer must know the interface and the code should not disturb the look and feel of the site or application. So the developer should understand the design and navigation. If the site is dynamic then the code should utilize the template. The developer may need to interact with the designer, in order to understand the design. The designer may need to develop some graphic buttons when ever the developer is in need, especially while using some form buttons. If a team of developers is working they should use a CVS to control their sources. Coding team should generate necessary testing plans as well as technical documentation. For example Java users can use JavaDoc to develop their documents to understand their code flow. The end-user documentation can also be prepared by the coding team, which can be used by a technical writer who can understand them, writes helps and manuals later.
Input: The site with forms and the requirement specification
Output: Database driven functions with the site, Coding documents
6. Testing:
Unlike software, web based applications need intensive testing, as the applications will always function as a multi-user system with bandwidth limitations. Some of the testing which should be done are, Integration testing, Stress testing, Scalablity testing, load testing, resolution testing and cross-browser compatibility testing. Both automated testing and manual testing should be done without fail. For example its needed to test fast loading graphics and to calculate their loading time, as they are very important for any web site. There are certain testing tools as well as some online testing tools which can help the testers to test their applications. For example ASP developers can use Microsoft’s Web Application Test Tool to test the ASP applications, which is a free tool available from the Microsoft site to download.
After doing all the testing a live testing is necessary for web sites and web based applications. After uploading the site there should be a complete testing(E.g.. Links test)
Input: The site, Requirement specifications, supporting documents, technical specifications and technical documents
Output: Completed application/site, testing reports, error logs, frequent interaction with the developers and designers
7. Promotion:
This phase is applicable only for web sites. Promotion needs preparation of meta tags, constant analysis and submitting the URL to the search engines and directories. There is a details article in this site on site promotion, click here to read it. The site promotion is normally an ongoing process as the strategies of search engine may change quite often. Submitting a site URLs once in 2 months can be an ideal submission policy. If the customer is willing, then paid click and paid submissions can also be done with additional cost.
Input: Site with content, Client mails mentioning the competitors
Output: Site submission with necessary meta tag preparation
8. Maintenance and Updating:
Web sites will need quite frequent updations to keep them very fresh. In that case we need to do analysis again, and all the other life cycle steps will repeat. Bug fixes can be done during the time of maintenance. Once your web site is operational, ongoing promotion, technical maintenance, content management & updating, site visit activity reports, staff training and mentoring is needed on a regular basis depend on the complexity of your web site and the needs within your organization.
Input: Site/Application, content/functions to be updated, re-Analysis reports
Output: Updated application, supporting documents to other life cycle steps and teams.
The above-mentioned steps alone are not strict to web application or web site development. Some steps may not applicable for certain tasks. Its depend on the cost and time involved and the necessity. Sometimes if it is a intranet site, then there will be no site promotion. But even if you are a small development firm, if you adopt certain planning along with this web engineering steps in mind, it will definitely reflects in the Quality of the outcome.
CHECKLIST FOR IDENTIFYING GOALS AND OBJECTIVES
Have all of the background materials been reviewed, such as the organization’s strategic business plan (which should include the organization’s mission, business strategy, and critical success factors), the Request for Proposal (if one exists), requirements documentation, and concept papers?
Has the project team met with customer executives and other stakeholders to establish a clear and unambiguous understanding of their goals and aspirations?
Is it clear how the goals and objectives of this project fit within the overall goals and objectives of the organization (i.e., the bigger picture)?
Have the critical constraints been identified (e.g., the customer’s expectations for such things as effort, duration, and cost)?
Has the business value of achieving the goals and objectives been identified?
Have the goals and objectives been documented in a clear and unambiguous way (e.g., specific not general)?
Have the goals and objectives been documented in a way that will serve to challenge and motivate the project team (e.g., sufficiently difficult but also realistic and attainable)?
Are the goals and objectives measurable, tangible, and verifiable?
Is it clear how the achievement of the goals and objectives will be measured?
Is there consensus on the goals and objectives, as defined?
CTO
Association Matrix Checklist
|
CHECKLIST FOR AN ASSOCIATION MATRIX |
|||||
| Project Name: | Project Code: | ||||
| Document Name: | Document Number: | ||||
| Reviewed By: | Reviewed Date: | ||||
|
Checklist Items |
Yes |
No |
Comments |
||
| There are no missing rows or columns (the matrix is complete). | |||||
| The rows and columns are sorted for best presentation. | |||||
| All rows have an association with at least one column. | |||||
| All columns have an association with at least one row. | |||||
| For CRUD matrices, all entities that are being managed by the application have a “create”. | |||||
| For CRUD matrices, all entities that are managed by other applications (i.e., interfaces) show as “read” only. | |||||
IT Infrastructure department
Move to take up new responsibilities in the IT Infrastructure department
- If you do not know what IT infrastructure is, then neither party in this discussion is thinking clearly. You need to approach whoever feels this is a good idea and ask them to define IT Infrastructure (which in every company I have worked for refers to a minimum of the underlying back-office hardware (and in one case software) that the enterprise runs. This includes but is not restricted to Servers (including OS installs), Phones, Network Configuration/Tuning and much-much more. If you are a Project Manager, then you know how important training is and do not hesitate to state the requirement up front and make sure it is clear a stack of manuals and work station that runs Google is not good enough! In your new role you will be responsible for making sure the machines that run the software that runs the company is running 24 x 7 and that means you will wear a pager and be its slave. Make sure you are wanting this type of life style and good luck! Some people love this type of role, but make sure it suits you and your personality.
