How to Create an Entity Relationship Diagram

Entity-relationship diagrams are used to plan and design a database for normalization purposes.
The entity-relationship model starts with the entities, data normalization starts with the attributes, and the two tools tend to verify each other. The entity-relationship model’s entities, attributes, and relationships map smoothly to a physical database.
ERD gives a clear, high-level logical view of the data in a system. It is an excellent starting point for modeling the system.
Before creating an entity-relationship diagram, the analyst must have at least a preliminary sense of the system’s logical entities, attributes, and data structures. The necessary information is obtained during the information gathering and problem definition stage Entity-relationship diagrams are important tools in the structured requirements methodology and in database design.An entity is an object (a person, group, place, thing, or activity) about which data are stored. A relationship links two entities and is shown by drawing a line between them.
Logically, a relationship can be stated in the form of a sentence with a verb linking the two entities.  However, the entity being displayed as reference are only example of an entity name or a table in your database.  Remember that you still need to add data fields for your table.  Moreover, you have to connect some entities as necessary especially if there is a foreign key within your table.

 

Guide in Conducting Interview

Conducting Interview

1. Occasionally check the tape recorder (if used) is working.
2. Ask one question at a time.
3. Attempt to remain as neutral as possible. That is, don't show strong emotional reactions to their responses. Patton suggests to act as if "you've heard it all before."
4. Try to Encourage responses with occasional nods of the head, "uh huh"s, etc.
5. Be careful about the appearance when note taking. That is, if you jump to take a note, it may appear as if you're surprised or very pleased about an answer, which may influence answers to future questions.
6. Provide transition between major topics, e.g., "we've been talking about (some topic) and now I'd like to move on to (another topic)."
7. Don't lose control of the interview. This can occur when respondents stray to another topic, take so long to answer a question that times begins to run out, or even begin asking questions to the interviewer.

What to Do After Interview

1. Make sure if the tape recorder, if used, worked throughout the interview.
2. Insert any notes e.g., to clarify any scratchings, ensure pages are numbered, fill out any notes that don't make senses, etc.
3. Write down any observations made during the interview. For example, where did the interview occur and when, was the respondent particularly nervous at any time? Were there any surprises during the interview? Did the tape recorder break?

How to Interview with the Client in Systems Project

First of all you need to understand "why" you are meeting with the client! What is the purpose of this meeting?

For example:

• Is the purpose of this meeting to discuss the Vision of the document?
• Does the Vision, Business Case, and Project Charger exist and you are now ready to elicit requirements?

You also need to understand the "state" of the project!

For example:

• Are you adding creating a brand new system to support existing business processes? If so, are these processes already documented?
• Are you replacing an existing system? If so, any documentation exist for the existing system (requirements, functional specifications, user guides, etc.)?
• Are you modifying an existing system? Again, are there any existing artifacts which describe the existing system?

You need to understand the "methodology" used on your project and in your organization!

For example:

• Are you operating in an Agile process where you will have direct access to the stakeholders during the development process? if so, you might not need to capture/elicit too much upfront as many of the details will come up via subsequent iterations.
• Are you in an environment where requirements must be all documented upfront in details, using a specific type of artifact, and signed in blood by the C-Level Executives?
• Somewhere in between?

In general, as long as you are somewhat prepared for the meeting (and you say you are) you'll be OK. Just make sure you have some high-level open ended questions that you can ask and then be prepared to be quiet and listen.

The Key to Effective Project Resource Allocation

What Do We Need to Implement the Plan?

1. Determine quickly what resource you will need
Always remember that every resource is the person working and involved in the project.

2. Determine who the best people are in the project
They are the one who are commited and focused and can deliver quality standard

3. Approach and check on their availabiliy
Assuming they are available put their name down against the relevant tasks in your project plan