These are my notes, but it's no where near as detailed as the book, sorry
EDIT: the titles are bolded but i cba to format it on here sozzers!
Decision tables
• Provide simple way of displaying the actions to be taken when certain conditions occur.
• There are the following sections:
- Conditions stub: situations or events which need testing. Cause of the actions which need to be taken. A condition might be “is the person over 18?”
- Actions stub: these are the actions depending on the combination general conditions in the conditions stub that apply. For instance: “may be served alcoholic drink” could be an action.
- Conditions entries: these give an indication of which of the conditions apply. This is done by placing Y or N next to each condition depending on whether the condition applies or not.
- Action entries. – These are the conditions which apply. A cross is marked in the decision table to show which actions should be taken.
Advantages of decision tables:
• You can make sure that all the combinations of conditions have been considered.
• They are easy to understand since the information is held on one table.
• There is a standard layout so everyone uses the same format.
• Programmers may use them to write programs and they are useful for working out logic conditions in excel, database etc.
• They show cause and effect and are therefore understood by most people.
Data flow diagrams
• They look at inputs, processes and the outputs of a system.
• External source of data
- Oval box which is used to describe where outside the system the data comes to. I.e. customer.
• Data flow
- Shown by an arrow pointing in the direction of the flow, usually it is advisable to put a description of the flow on top of the arrow to aid understanding.
• Data store
- Data store is anywhere where data can be stored such as a filing cabinet etc.
- Symbol will have a number to give it reference when describing it.
- M is used for manual C is used for computer.
• Levels of DFD
- You have to draw DFD’s at different levels:
- Level 0 is an overview of the whole system. It is called a context diagram as it shows the main flows and orders.
- Level 1shows the main processes in the system and presents a more detailed view of the data flows.
- Breaks down the process boxes in level one and presents an even more detailed version of the processes.
• Using DFD’s
- During system investigation to record current system findings.
- During system design to illustrate how a proposed system will work
- When outlining the specifications of the new system.
Entity relationship diagrams
• Look at any components important to the system and the relationship between them
• Entity – anything about which data is recorded. Includes people, places, objects, customers, sales, payments etc.
• Attributes – Each entity has its own attributes. It is the detail about an entity, for example, customer name, postcode, amount owing etc. Etc.
• Relationships – ways in which entities in a system are related to another. It could be a one to one relationship, one to many, many to many.
• Deciding the type of relationship – looking at the relationship from both ends, a student could take more than one course. A single course can be taken by many students. Therefore it is many to many.
• Another example might be – one tutor has many pupils, many pupils have one tutor – therefore it is one to many.
• Many to many relationships cannot be implemented and so you have to create a new entity that would link the 2 together. For example, with many students to many course, a new entity called enrolment could be entered which attaches the 2 entities together.
Using keys
• Primary key – one or several attributes that can uniquely define a particular entity. For example, customer entity could be uniquely defined by a customer number.
• Foreign key – when one of the attributes that is a primary key in one entity also appears in another entity, there is a relationship between the entities. Because the attribute is not unique, the key entered is called a foreign key. For example, if there was an employee ID as a primary key in the employee table, there might be an employee ID again in the payroll table. Therefore, the foreign key will take the place of the employee ID.
Data dictionary: ADD IN AN EXAMPLE.