Business Interview Questions

I would explain to the stakeholder that the purpose of the Business Requirements elicitation meeting was designed to identify the business need not to design the solution.

Great answer and exactly right!

nice!!

1. Review documentation/ release notes. 2. List/ Review the steps in the upgrade. 3. Get the other parties involved to set aside time. 4. Then I would look at the media, and take any backups if needed. 5. I would set up a time which i would communicate to the users asking them to stay out of the system. 6. Complete the upgrade 7. Communicate with the users that it is ok to log back in to the system.

A functional requirement is the what; a system requirement is the how.

A functional requirement is what the system should do. It is what function is wanted. Non functional is how that is achieved. It specifies how that system should work.

A functional requirement describes the observable behavior of a system. It describes how the work should be done. A system requirement describes the needs of the system (computer) to be able to use the software or hardware. Some examples of functional requirement are “user must be able to login to their account” “user must be able retrieve password”. Some examples of system requirements are “the system must be able to operate in windows and Mac operating systems”

Helping my staff to maximise their potential

An average in which each quantity to be averaged is assigned a weight. These weightings determine the relative importance of each quantity on the average. Weightings are the equivalent of having that many like items with the same value involved in the average.

Cisco is already touching the SMB and consumer segment, esp. with its managed services. Public TelePresence at a low enough price would be extremely attractive to consumers in less developed areas. With Cisco's experience in using games to promote its products, offering game hosting as a managed service is not such a big leap.

The interviewer was interested in breath of experience rather than specific technical skill. Unix work with scheduling and XML skills are necessary, but not heavy (the same procedures are done over and over again). Emphasis was on selling yourself through experience.