Specifying Queries

This is a good idea.

Your database needs to specify (i.e. plan) the queries you're going to be using. This means it needs to

• say what the query will be called
• say what fields will be used in it - and which table they will come from

e.g.

qryInvoice
Csutomer ID - from tblCstomer
BookingID - from tblBookings

etc...

Input Needs

You probably have things like

• input masks
• drop down boxes
• calendar controls
• parameter queries
• forms

Fine. I need a section which gives a brief overview of data input needs. All the evidence for this is probably already there, but this section needs to bring that all together and summarise it (bullet points are fine).

I need:

1. what data is going to be inputted
2. who is going to do the inputting (at the client)
3. where are they going to get the data from
4. how is the input going to be done - cross reference to all the screenshots of stuff you have (the list above) with page numbers

I would have a section for this, probably towards the end of the Implementation section (somewhere around security) called "Input Needs". Lots of cross referencing to the stuff you've already got is just fine.

Apple vs Flash

So, Steve Jobs says Flash is a bit rubbish and not suitable for running on Apple's uber-cool touchscreen smartphones and the like.

Good.

The less use that's made of Flash the better imo. It's hideously overused - I took a look at a Flash website today - for a lodge business. Why on earth the site was built in Flash I'll never know - ages to load, lousy scrolling and really sucky look all round.

So any disincentive to use the damned stuff on standard websites sounds like a plan to me.

Jobs explains his difficulties with Flash - which can be a great tool if it's used properly btw - in a letter. Sound points in general - the lack of openness, security problems and battery issues convince me by themselves. Worth a read.

40 uses for a floppy disk...

Fabby article from the BBC Magazine - seems like there's a lot of technical demand for them and they make handy ice scrappers as well :-)

This week, though, Sony decided it would stop making them. Part of my life just disappeared (of course, I'm old enough to remember floppy disks which were actually floppy...)

Monitoring Progress in Open Workbench

You can use Open Workbench. Yay!

But can you monitor your progress in it?

This thought occurred as a result of reading some little detail in the markscheme for the sample piece of work we have. In AO1 - Row 2 the comment explaining why the candidate didn't get 4 marks says:

Project is used to plan time, which is appropriate, but candidate has not shown that it has been used to monitor progress, so the explanation does not warrant the fourth mark

So, we need to use Open Workbench to try to monitor our progress. Hmmmm....

NB: Before you do this BACK YOUR FILE UP!

Having discussed this in class, James "The Machine" found the Status Update tab - look down on the left hand side in the Controlling group. From this you can try:

• click in the Total Actuals (hours) column and put in the amount of time some jobs actually took - look, stuff happens
• check back on the Gannt chart and look at the phases bar - look: there's a little bar showing progress on the phase!
• take some screenshots now
• now change the Started box on the far right to Completed - it goes when you click away - not yet, but later! It disappears. Take some more screenshots - this shows that you're monitoring the progress that's occured as you're going along. You can see why, in a complex project, this would be a good idea yes? Good.
• check the Gannt chart view as well - the Gannt bars will eventually start changing some colour - and might shift (if you start a task which is dependent on another one!)

Take care with this. I think you need a couple of pages of screenshots to show that you monitored it. But be aware that you will lose views and information - which is why a backup copy's a good idea because me and JTM haven't worked out how to get them back again yet!

Hannah says what are Standard Ways of Working?

Another good question Hannah. I hope you'll continue to ask questions long after you've left us.

Standard ways of working need to be proven for most portfolios. This simply means do things the way they should be done - the "industry standard" ways of doing stuff. Like:

• sensible file names, using version numbers etc... Include your documentation etc... as well as whatever you're producing
• sensible sheet names or names for queries, reports, tables etc... using standard methods (like: tblPokemonCharacters or qryYellowFruit)
• sensible file structure - using folders effectively to organise work
• backing up an using appropriate storage

For Project Management you might also include elements which show that you've used standard ways of working for group projects such as:

• use of agenda, minutes etc... to schedule meetings
• use of project management software to plan - e.g. Gannt charts and resource assignments using Open Workbench
• effective use of e-mail, letters, synchronous chat etc... to manage work
• use of collaborative documents to allow multiple people to work on the same document (for example, user guides etc...)

For the final mark in the row you'll need to be answering the question: Why did I/we do this?

It's OK to be sad - the FarmVille story

FarmVille.

Bit sad really isn't it? But not terribly dangerous if played in small doses according to this BBC article (although note: an official got sacked in Bulgaria for playing it - take care eh...).

Comments are interesting - the idea that Groups may be scams: get you to fill out a survey and, ah ha, they have personal details.

Now, do I join just to get a farm? Hmmmm....