You've met a nice guy and perhaps you have been dating awhile. You know you like him a lot, but you would like to now how he feels about you. What are the best signs that a guy likes you?
1. Eye contact. There are two kinds of eye contact. A guy can be to shy to have eye contact, so whenever you look hem in his eyes, he will quickly turn his head to avoid looking in your eyes. Another kind of eye contact is when he looks in to your eyes; he keeps looking a bit longer than one second. Both types of eye contact can be a sign that he likes you.
2. How does he behave around other women? Does he treat you the same as other women or do you get a 'special' treatment. If he doesn't treat you the same it could be a sign he likes you. Often when a guy likes you, he flirts with other women. He tries to make you jealous and hopes to get attentions from because of it. A nice trick is to go away, or go to the toilet, and ask a friend to look if he stops to flirt when you are no longer around.
3. Listen to what he is saying. Guys still think they have to prove their self. So when he is talking about his new car or his high paying job, he is trying to impress you.
4. See if he is showing interest in things you do or talk about. For instance, if this guy likes the same movies or the same book as you do, often that is a sign to show you how good the two of would fit together.
5. Touching. He touches you often. He puts his hand on you shoulder, when he is talking. When by accident your leg touches his, he will not move.
6. Study his body language. If he likes you, you may notice that he doesn't turn his back to you and often leans towards you.
The tips mentioned are some good signs that a guy likes you. But be careful do not rely on one sign only. See if there is more than one.
Article Source: http://EzineArticles.com/?expert=Sandy_Dons
http://ezinearticles.com/?6-Signs-That-a-Guy-Likes-You&id=2169626
Sunday, May 31, 2009
Reasons of Heart Breaks.... T.T
Following are 10 versatile sad and confused quotes for ten different situations of heart break and betrayals by friends, lovers and family.
Reason 1 Rejection at proposal: - “I know you are smiling at my shattered and dead heart, but I will weep till your smile is washed away.”
Reason 2 Betrayal by a wife: - “When you broke the first oath I was silent, when you broke the second oath I cried out in pain but this time i will speak for your silence.”
Reason3 Betrayal by a husband: - “When you cried I cried with you, when you were happy I rejoiced with you, when you could not hear I became deaf with you, but when you loved someone else what should I do?”
Reason 4:-Betrayal by a friend:-“et tu Brute then fall Caesar” Shakespeare, Julius Caesar.
Reason 5:-Betrayal by children:- “ I held your hand when you took your first step ,I took you to a doctor when in sickness, I nourished you with my blood when you were hungry, I made you look tall on my dwarf shoulders so that you can put me with people of your tender age. I have learned to live without you my son, god bless you.”
Reason 6:- A rejected child:-“My cheeks are flooded with tears, grief chokes my voice, my heart pounds your name, eyes crimson in anticipation ,my senses feel your presence. I know you are some where mother. I am crying for you.”
Reason 7:- Betrayal by a boy friend: - “We decided to live together, we decided to have children together, we decided to have a home together, we decided to die together .I am dying, where are you?”
Reason 8 :- Betrayal by a girl friend :- “ You said life is a storm I said I will face them for you, you said I am in pain I said I will suffer them for you, you said I will never leave you I said I will die for you but if you love him I can live without you.”
Reason 9:- Rejection at office :- “I toiled night and day suffering yet moving for you ,you said yes and I said yes for you ,you said no and I denied with you ,you said do and I did for you but now our ways and hearts are separate and I will strive to burry you.”
Reason 10:-Betrayal by a brother:-“Siblings of the same womb ,same blood runs through our hearts, same childhood made us young. Blinded by my love I forgot I have a heart and you have a mind which is not same in me and you
http://confused.cc/confused-sad-quotes/
Reason 1 Rejection at proposal: - “I know you are smiling at my shattered and dead heart, but I will weep till your smile is washed away.”
Reason 2 Betrayal by a wife: - “When you broke the first oath I was silent, when you broke the second oath I cried out in pain but this time i will speak for your silence.”
Reason3 Betrayal by a husband: - “When you cried I cried with you, when you were happy I rejoiced with you, when you could not hear I became deaf with you, but when you loved someone else what should I do?”
Reason 4:-Betrayal by a friend:-“et tu Brute then fall Caesar” Shakespeare, Julius Caesar.
Reason 5:-Betrayal by children:- “ I held your hand when you took your first step ,I took you to a doctor when in sickness, I nourished you with my blood when you were hungry, I made you look tall on my dwarf shoulders so that you can put me with people of your tender age. I have learned to live without you my son, god bless you.”
Reason 6:- A rejected child:-“My cheeks are flooded with tears, grief chokes my voice, my heart pounds your name, eyes crimson in anticipation ,my senses feel your presence. I know you are some where mother. I am crying for you.”
Reason 7:- Betrayal by a boy friend: - “We decided to live together, we decided to have children together, we decided to have a home together, we decided to die together .I am dying, where are you?”
Reason 8 :- Betrayal by a girl friend :- “ You said life is a storm I said I will face them for you, you said I am in pain I said I will suffer them for you, you said I will never leave you I said I will die for you but if you love him I can live without you.”
Reason 9:- Rejection at office :- “I toiled night and day suffering yet moving for you ,you said yes and I said yes for you ,you said no and I denied with you ,you said do and I did for you but now our ways and hearts are separate and I will strive to burry you.”
Reason 10:-Betrayal by a brother:-“Siblings of the same womb ,same blood runs through our hearts, same childhood made us young. Blinded by my love I forgot I have a heart and you have a mind which is not same in me and you
http://confused.cc/confused-sad-quotes/
Wednesday, May 27, 2009
On the JOB Training [Summer 09]
Excited and Happy that finally I can have my OJT now. It was really fun applying yourself to various company and find an establishment that will accommodate us, though its very hot and you should wake up early or go to school every now and them to update your files and everything, it was really cool letting yourself experience be employed. I've used the word "US" because I'm with my friends and classmates.
So as we go along, me and my pal Nicole been in Sutherland, Concentrix, Davao Doctor's Hospital, Call Box, Blue Pearl, Abratique and Creative Response. We've been hired at Sutherland HR Dept., Blue Pearl and Creative Response but as we have compared the three (3), we are more comfortable spending our OJT at Creative Response since its a Graphics Design Company locating at 8th floor, LandCo Bldg. though we are very eager to find a company that would give us any kind of allowance (food or fare) that would free us from financial crisis... hehehe... but unfortunately theirs NONE...
April 20, our first day at Creative Response, we are all very excited to start our first day at CR... hehehe... together with Ronie, Nicole, Jade and the 3 mosquiters who from somewhere in the middle of our first day just came... wahahaha... namely: Thomas, Rossini and Simon... The company will open at 11:30am and will end at 10pm... a long hours to be open... hehehe... since we are OJT's, they allow us to be in at 1pm... so everyday we will consume 9hrs... it was boring and a tiring moment since you will spend 9 hours 5 days a week.... haiz... Since CR is a new branch here at Davao, they are still changes as we pursue... So, on May 12 our schedule has changed into morning shift and will be out at 7:30pm... We will in at 9:30am and end at 7:30pm.... that schedule last for a week and the following week becomes even more worse... since the management decided to group us by 3 and 4... there will be now a morning and afternoon shift... and our consumable time everyday would be 5 hours only.... It was a bad decision and yet we have nothing to do since we are just OJT's.... the problem here is how can our group will make it before our classes begin?... we know that is very impossible... so, we have nothing to say and do with but to feel free on what we are doing and end it in the exact number of hours.
Ou enrollment is fast approaching, it was scheduled on May 29 and June 1, 09... and we all know that USEP classes will begin on June 08, 2009.... and our OJT will probably end on the 3rd week of June... It was Sad but we know we can make it....
AJA!!!!... Fighting!!!....
So as we go along, me and my pal Nicole been in Sutherland, Concentrix, Davao Doctor's Hospital, Call Box, Blue Pearl, Abratique and Creative Response. We've been hired at Sutherland HR Dept., Blue Pearl and Creative Response but as we have compared the three (3), we are more comfortable spending our OJT at Creative Response since its a Graphics Design Company locating at 8th floor, LandCo Bldg. though we are very eager to find a company that would give us any kind of allowance (food or fare) that would free us from financial crisis... hehehe... but unfortunately theirs NONE...
April 20, our first day at Creative Response, we are all very excited to start our first day at CR... hehehe... together with Ronie, Nicole, Jade and the 3 mosquiters who from somewhere in the middle of our first day just came... wahahaha... namely: Thomas, Rossini and Simon... The company will open at 11:30am and will end at 10pm... a long hours to be open... hehehe... since we are OJT's, they allow us to be in at 1pm... so everyday we will consume 9hrs... it was boring and a tiring moment since you will spend 9 hours 5 days a week.... haiz... Since CR is a new branch here at Davao, they are still changes as we pursue... So, on May 12 our schedule has changed into morning shift and will be out at 7:30pm... We will in at 9:30am and end at 7:30pm.... that schedule last for a week and the following week becomes even more worse... since the management decided to group us by 3 and 4... there will be now a morning and afternoon shift... and our consumable time everyday would be 5 hours only.... It was a bad decision and yet we have nothing to do since we are just OJT's.... the problem here is how can our group will make it before our classes begin?... we know that is very impossible... so, we have nothing to say and do with but to feel free on what we are doing and end it in the exact number of hours.
Ou enrollment is fast approaching, it was scheduled on May 29 and June 1, 09... and we all know that USEP classes will begin on June 08, 2009.... and our OJT will probably end on the 3rd week of June... It was Sad but we know we can make it....
AJA!!!!... Fighting!!!....
Wednesday, March 25, 2009
Activity5b_SE1
Prototyping allows the users to try out a working model of a system before the actual system is complete. Explain how prototyping can be counterproductive if it creates task interference during training.
Prototyping is an activity during certain software development, it is the creation of prototypes, incomplete versions of the software program being developed. A prototype typically simulates only a few aspects of the features of the eventual program, and may be completely different from the eventual implementation.
The conventional purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions.
Prototyping has several reimbursements: The software designer and implementer can obtain response from the users early in the project. The client and the contractor can compare if the software completed matches the software specification, according to which the software program is built. It also allows the software engineer some imminent into the accuracy of preliminary project estimates and whether the deadlines and milestones proposed can be successfully met.
But even prototyping can have more advantages it is also and can produce counterproductive as you go along revising your prototypes because of some new idea that comes your way as you progresses in your project it can build counterproductive during the training task since you are editing it every now and then maybe you lack some polishing it before presenting it to others. It would be a big problem in your part since it interfere while you are there presenting it. Others may say that you make projects that are not efficient and liable. But because it was just a prototypes you can revised it anytime you want.
Prototyping is an activity during certain software development, it is the creation of prototypes, incomplete versions of the software program being developed. A prototype typically simulates only a few aspects of the features of the eventual program, and may be completely different from the eventual implementation.
The conventional purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions.
Prototyping has several reimbursements: The software designer and implementer can obtain response from the users early in the project. The client and the contractor can compare if the software completed matches the software specification, according to which the software program is built. It also allows the software engineer some imminent into the accuracy of preliminary project estimates and whether the deadlines and milestones proposed can be successfully met.
But even prototyping can have more advantages it is also and can produce counterproductive as you go along revising your prototypes because of some new idea that comes your way as you progresses in your project it can build counterproductive during the training task since you are editing it every now and then maybe you lack some polishing it before presenting it to others. It would be a big problem in your part since it interfere while you are there presenting it. Others may say that you make projects that are not efficient and liable. But because it was just a prototypes you can revised it anytime you want.
Activity5a_SE1
If one person has written a component but others have revised it, who is responsible if the component fails? What are the legal and ethical implications of reusing someone else's component?
Revising means checking a piece of writing for grammar and mechanics. This kind of checking is better called proofreading. True revising involves making much more substantial changes in a piece of writing. In altering one’s work will now matter if the person who revised it has all the acquiescence in doing it so and the owner knows what that persons (who will revised his/her work) thought in revising it.
In the first place, there are levels of revising ones work. First is at its most extreme, revising means discarding a draft and starting over. In this extreme of revising, the writer rethinks the writing, changing content as well as organization and style. At this level of revising, the writer is concerned with the basic content, the concepts and fundamental imagery of the writing. Second would be a less extreme form of revising means reorganizing the draft and adding or removing sections of it. Revising at this level, the writer seeks to clarify content and style and to make the writing more accessible to the reader. At this level of revising, the writer is concerned with the overall structure of the writing, making it express the basic concept of the writing. While the third level of revising is close to proofreading. At this level, the writer mainly checks sentence and paragraph style, not so much looking for errors as seeking clear and effective writing. At this level, the writer is largely concerned with the rhythm of the writing.
In this level of revising, the individual who will revise ones toil should be educated of how to revise ones effort to avoid failures. The one revising should also continue the main point of the unusual writer of a definite subject matter and not just messing around or messing ones exertion.
Reusing is the ability to use all or the greater part of the same programming code or system design in another application. With this definition alone in no doubt we can instill into our minds how to reprocess one’s toil. You can revise it or even reuse it but never engrave the main idea of the item or one component. You can convey it in your own idea but never snatch one’s idea in it.
The legal and ethical implications of reusing else’s component is first to have a authorization from the original writer of that article. If it’s an online article and can be edited then you should have all those necessities needed in doing it so before publishing it. Secondly, you as the person revising ones theme you should be legally responsible in what you are doing and tying to imply. Liability when it comes to your capacity, knowledge and resources. It is very essential to take on consideration these things to foil failures.
Revising means checking a piece of writing for grammar and mechanics. This kind of checking is better called proofreading. True revising involves making much more substantial changes in a piece of writing. In altering one’s work will now matter if the person who revised it has all the acquiescence in doing it so and the owner knows what that persons (who will revised his/her work) thought in revising it.
In the first place, there are levels of revising ones work. First is at its most extreme, revising means discarding a draft and starting over. In this extreme of revising, the writer rethinks the writing, changing content as well as organization and style. At this level of revising, the writer is concerned with the basic content, the concepts and fundamental imagery of the writing. Second would be a less extreme form of revising means reorganizing the draft and adding or removing sections of it. Revising at this level, the writer seeks to clarify content and style and to make the writing more accessible to the reader. At this level of revising, the writer is concerned with the overall structure of the writing, making it express the basic concept of the writing. While the third level of revising is close to proofreading. At this level, the writer mainly checks sentence and paragraph style, not so much looking for errors as seeking clear and effective writing. At this level, the writer is largely concerned with the rhythm of the writing.
In this level of revising, the individual who will revise ones toil should be educated of how to revise ones effort to avoid failures. The one revising should also continue the main point of the unusual writer of a definite subject matter and not just messing around or messing ones exertion.
Reusing is the ability to use all or the greater part of the same programming code or system design in another application. With this definition alone in no doubt we can instill into our minds how to reprocess one’s toil. You can revise it or even reuse it but never engrave the main idea of the item or one component. You can convey it in your own idea but never snatch one’s idea in it.
The legal and ethical implications of reusing else’s component is first to have a authorization from the original writer of that article. If it’s an online article and can be edited then you should have all those necessities needed in doing it so before publishing it. Secondly, you as the person revising ones theme you should be legally responsible in what you are doing and tying to imply. Liability when it comes to your capacity, knowledge and resources. It is very essential to take on consideration these things to foil failures.
Thursday, February 19, 2009
Activity4b_SE1
Question:
You have been hired by a computer consulting firm to develop an income tax calculation package for an accounting firm. You have designed a system according to the customer’s requirements and presented your design at a design review. Which of the following questions might be asked at the preliminary design review? At the critical design review? At both? Explain your answers.
a) What computer will it run on?
b) What will the input screens look like?
c) What reports will be produced?
d) How many concurrent users will there be?
e) Will you use a multiuser operating system?
f) What are the details of the depreciation algorithm?
The Preliminary Design Review (PDR) is a formal inspection of the high-level architectural design of an automated system and its software, which is conducted to achieve confidence that the design satisfies the functional and nonfunctional requirements and is in conformance with CMS' enterprise architecture. Overall project status, proposed technical solutions, evolving software products, and associated documentation are reviewed at a high level to determine completeness and consistency with CMS standards, to raise and resolve any technical and/or project-related issues, and to identify and mitigate project, technical, security, and/or business risks affecting continued detailed design and subsequent development, testing, implementation, and operations & maintenance activities. http://www.cms.hhs.gov/SystemLifecycleFramework/Downloads/PDR.pdf
From the above definition PDR must be conducted to ensure that the automated system or application being designed is in conformance with CMS' enterprise architecture and design standards. It involves scientific and technical objectives of the system. A detailed information and overall system design covering all aspects (electronic, mechanical, software) of the project or even the preliminary designs (block diagrams). For the instrument being used there should be a detailed interface specification between the hardware and software. Detailed budget and project plan and most of all major areas of risk and risk mitigation plans.
All the questions above are being discussed in the PDR stage because all the questions above involves reviewing the specific plans of the project, and should be conducted before any significant acquisitions or fabrication begins, and before any finalizations are produced. Budget and project plans should be refined and agreed to.
The question above implies are for the future implementation, it implies before the system should be design. Those questions are for PDR because it expresses before the fabrication of the system.
The CDR is generally intended to evaluate the proposed final designs, sometimes including constructed prototype modules or subsystems, but prior to commitment to final production. https://safe.nrao.edu/wiki/bin/view/GBT/ProjectReviews
As what I understand from above definition, CDR is for final polishing from the PDR stage of your system. It will just evaluate the proposed final designs. It will not touch those questions being tackled at the PDR stage. CDR is for ensuring if the system achieves the requirements being discussed during their PDR stage.
You have been hired by a computer consulting firm to develop an income tax calculation package for an accounting firm. You have designed a system according to the customer’s requirements and presented your design at a design review. Which of the following questions might be asked at the preliminary design review? At the critical design review? At both? Explain your answers.
a) What computer will it run on?
b) What will the input screens look like?
c) What reports will be produced?
d) How many concurrent users will there be?
e) Will you use a multiuser operating system?
f) What are the details of the depreciation algorithm?
The Preliminary Design Review (PDR) is a formal inspection of the high-level architectural design of an automated system and its software, which is conducted to achieve confidence that the design satisfies the functional and nonfunctional requirements and is in conformance with CMS' enterprise architecture. Overall project status, proposed technical solutions, evolving software products, and associated documentation are reviewed at a high level to determine completeness and consistency with CMS standards, to raise and resolve any technical and/or project-related issues, and to identify and mitigate project, technical, security, and/or business risks affecting continued detailed design and subsequent development, testing, implementation, and operations & maintenance activities. http://www.cms.hhs.gov/SystemLifecycleFramework/Downloads/PDR.pdf
From the above definition PDR must be conducted to ensure that the automated system or application being designed is in conformance with CMS' enterprise architecture and design standards. It involves scientific and technical objectives of the system. A detailed information and overall system design covering all aspects (electronic, mechanical, software) of the project or even the preliminary designs (block diagrams). For the instrument being used there should be a detailed interface specification between the hardware and software. Detailed budget and project plan and most of all major areas of risk and risk mitigation plans.
All the questions above are being discussed in the PDR stage because all the questions above involves reviewing the specific plans of the project, and should be conducted before any significant acquisitions or fabrication begins, and before any finalizations are produced. Budget and project plans should be refined and agreed to.
The question above implies are for the future implementation, it implies before the system should be design. Those questions are for PDR because it expresses before the fabrication of the system.
The CDR is generally intended to evaluate the proposed final designs, sometimes including constructed prototype modules or subsystems, but prior to commitment to final production. https://safe.nrao.edu/wiki/bin/view/GBT/ProjectReviews
As what I understand from above definition, CDR is for final polishing from the PDR stage of your system. It will just evaluate the proposed final designs. It will not touch those questions being tackled at the PDR stage. CDR is for ensuring if the system achieves the requirements being discussed during their PDR stage.
Activity4a_SE1
Question:
Among the many nonfunctional requirements that can be included in a specification are those related to safety and reliability. How can we demonstrate that these requirements are testable? How can we demonstrate the reliability of a system that is required never to fail?
Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that specify specific behavior or functions. In general, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system. http://en.wikipedia.org/wiki/Non-functional_requirement
From the definition above, Non-functional requirements are the most critical factor in the success of your project. Without including it in your specification, your system will not be reliable enough and not secured to use.
In the question of how can we demonstrate that these requirements are testable? Is the same way of answering of how we can demonstrate the reliability of the system? The answer is to fully document both the functional and non-functional requirements. Both play different rules but of the same weight, I guess, because without the presence of one of the requirements in your system, it will definitely not work. Maybe that’s the main reason why functional and non-functional are included in developing a system because both are important in the completion of a project.
The main factor to consider in doing it is to have a better understanding of the performance your system and the usability of your system. One needs to study and have knowledge in documenting these requirements because without any knowledge of how it should be gathered or start with is useless. One needs to have a better and deep understanding about it. How can one or your group test your system without having it studied furthered?
The reliability and safety of you system depend on who develop the system. Who gathers the data needed and who list the requirements of the system. The group must have a root analysis in everything they do. It’s very important especially when you want your system to be on its peak when it will be implemented.
Among the many nonfunctional requirements that can be included in a specification are those related to safety and reliability. How can we demonstrate that these requirements are testable? How can we demonstrate the reliability of a system that is required never to fail?
Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that specify specific behavior or functions. In general, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system. http://en.wikipedia.org/wiki/Non-functional_requirement
From the definition above, Non-functional requirements are the most critical factor in the success of your project. Without including it in your specification, your system will not be reliable enough and not secured to use.
In the question of how can we demonstrate that these requirements are testable? Is the same way of answering of how we can demonstrate the reliability of the system? The answer is to fully document both the functional and non-functional requirements. Both play different rules but of the same weight, I guess, because without the presence of one of the requirements in your system, it will definitely not work. Maybe that’s the main reason why functional and non-functional are included in developing a system because both are important in the completion of a project.
The main factor to consider in doing it is to have a better understanding of the performance your system and the usability of your system. One needs to study and have knowledge in documenting these requirements because without any knowledge of how it should be gathered or start with is useless. One needs to have a better and deep understanding about it. How can one or your group test your system without having it studied furthered?
The reliability and safety of you system depend on who develop the system. Who gathers the data needed and who list the requirements of the system. The group must have a root analysis in everything they do. It’s very important especially when you want your system to be on its peak when it will be implemented.
Subscribe to:
Posts (Atom)