Friday, 13 May 2011

FIT 2001 Week 9

Lecture

I didn't realise I made it to blog of the week until today...Shows how much time I invest into this subject reading other peep's blogs.

Hmm....Request For Proposals(RFP)....I remember doing something about this in FIT 2008 for Networks. What was I doing....ah right I remember now....Good to have an archive of it... we were playing vendors for RFP's and had to work a Project requirement Brief based on the Scope of Work and Objectives of the RFP.

An RFP goes out and vendors will ussually, in some way, bid for it via offers. Then the client with all these offers will ussually choose the solutions based on the multitude of alternatives available unless the client is already decided on developing in-house and thus only has one solution already in mind. Ussually client's will use a matrix with weights on it. Engineering disciplines use a similar table to check alternatives for alternative solutions. The way we do it is just weighing requirements and checking how well the system being develop is meeting this requirements.

It is better to have alternatives, just like a backup plan in case anything goes wrong, but if you only have 1 plan, don't spend too much effort thinkingof another plan of action. Just follow through and iteratively remodel the plan and if a new plan does come out and then you can iterate again and examine. In other words iterate in the small, don't commit too far into the plan....Divide and conquer...Explore opportunities as they arise..You can get stuck in planning stage for a long time.

Tutorial

Converting class diagrams to relationships

1. Create a table (or entity) for each class
2. Choose a primary key for each table (invent one if needed)
3. Add foreign keys to represent one-to-many associations
4. Create new tables to represent many-to-many associations
5. Represent classification hierarchies
6. Define referential integrity constraints
7. Evaluate schema quality and make adjustments
8. Choose appropriate data types and value restrictions for each field.

Seems like a tedious amount of steps....

I think all it means is just converting class diagrams into ERD diagrams....Why are the lines in the solution dashed....I thought ERD was solid lines....hmm.....I am going to assume it is suppose to be solid...

Blogger was down yesterday and yes this post is long overdue....I will upload Week 10 very soon

No comments:

Post a Comment