FIT2001 Week 8: design

Well, the main thing I’m working on this week is the Assignment 1b Functional Specification Report. I’m glad the things I learned in ENH1260 Introduction to Professional Writing and FIT2043 Technical Documentation for Software Engineers are coming back to me, so I’m pretty happy that I can format my report and make it look business-y. Unfortunately I last took FIT2010 Databases FIT2008 Networks in 2007, so I’m going to need to brush up on the Diagrams for the Assignment and Terminology for the Design lecture! I’m still struggling with converting my event table into a Use Case diagram, so I just have to do the other diagrams and then ask lots of questions in the next tutorial. It just feels bad and wrong every time I attempt it, so I’m a bit discouraged there. Anyway, on with this week’s topic.


Good design involves creativity. While you can just put in tech solutions with the goal of meeting the Acceptance Test document, that isn’t really design. Design is a creative process where the designer (perhaps the Information Architect) makes IT solve problems in really efficient and useful ways, to inspire the business to use IT to add value, not just as a problem solver.

So let’s think “Blue Prints” so the designer can tell the programmer (either another person or their own future-self) how to build the system. Design works at both high-level and low-level. Of course, while Analysis works out what the system should do, Design looks at how the system should do it. There are three big areas that System Design focuses on: Network, Software and Database, which are inter-related.

The main points of the lecture were: Networking (enough to talk to the networking specialist) Application Architecture, User Interface (muck it up and the users will hate your system), System to System Interfaces. Database is a big deal, because a system is basically a Database with a graphical front end.

Security: besides passwords and encryption, also include Audit trail and logs.

Client Server Architecture is important. Having multiple servers lets us separate the different components of the system out.

3 Tier Architecture

Middleware is the glue that holds the layers together and lets the different software objects in the layers talk to each other.

The Quiz
This week I didn’t do well on the quiz: showing there is some specific knowledge to pick up here, rather than apply existing knowledge to new problems.

I managed to guess the answers involving stuff I already knew, such as LAN, distributed architecture, cluster, intranet, extranet, database relating to the Data Layer as well as the questions about the Analysis phase.

However, this is the stuff that I missed:

These were all Free form answer questions, and I think I could have improved my score by reading the question more carefully, or if I had been asked to define each of these rather than guess the word that matches the definition.

The Tutorial
The most memorable thing from the Tutorial? “What is the internet?”
“A Box.”

April 30, 2010 | |



Comments RSS

2 Responses to “FIT2001 Week 8: design”

  1. Alison on April 30th, 2010 6:08 am

    hooray! I’ve finished my Use Case Diagram!

  2. Matt on May 6th, 2010 12:16 am

    IT Crowd – Presenting… The Internet!

Leave a Reply