Week 13

this is the last time i will be blogging to you blogging world. its sad the SAD is finished but still have POD next semester :-D. Well this week we went through what to expect on the exam and POD gave some insight into jobs for the future. All i can say POD is that your an insperation to us all. you have made me so motivated to turning up to lectures, funny kind man, easy going and mate thank you for this semester, i can not thank you enough. I have learnt so much more then just the course which im very greatfull and you have opened my eyes to what i should be doing now. oh well, thanks for the semester everyone and thanks for reading System Anaylsis and design for Luke Pocock. Thanks

week 12

quick week this week. spoke about more interfaces but mostly system interfaces. spoke about creating databases, xml stnadards which are becoming more and more common, EDI systems such as creating inputs for another system to convert to your system, interfaces for outputs, integrity controls of the database, sercuirty controls. the reality of objects for databases is really non exestant because oracal is relational and not object oriented. thats it for this week because all we did in the tut is worked on assignments in which i got feedback for assignment1 which i can see where i went wrong and for stupid reasons. oh well, till next week

Week 11

Ok well there really is not much to tell this week, the lecture was about graphical user interfaces. well the basics are that they were designed because it made it easier for users to interact with the pc. also the importance of designing a good interface is the way the clients look at the system. if the interface is not looking the way they want, they will hate it no matter how good the program is. thats the main essense besides some story board diagramming.

tut was kinda of boring, the sites i have visited before in the past and the diagraming was pritty self explanitry. still a week behind but will be done. this is done on time which is amazing but yeah, its done

Week 10

Well week 9 is coming but week 10 will do for now. So much has been happening with assignments, training at work because i just got a promotion and alot of hassels with girlfriends work giving her shit so im finding it difficault to keep up with it all. But anyway, im doing it now.

Lecture not too bad. as pod said, every 20 mins, i had to keep telling myself keep listening and pay attention, but yeah did well. basically spoke about 2 main types of diagrams, class diagram and interaction diagrams which are sequence and collaberation diagrams. within class diagrams we talked about 3 different layers. also there are different symbols and notations for the classes. also spoke of coupling and Cohesion

Coupling – qualitative measure of how closely classes in a design class diagram are linked

Cohesion – qualitative measure of consistency of functions within a single class

also talked of subsystem packages.


tutorial went through a couple of exercises with sequence diagrams, class and subsytem packages diagrams about a dentist. its good to go through it in practice and i have to agree with you pod, not too hard to do.

Week 8

As you can see, im a little late in doing this. better not be becomming a habbit. na i have had a crazy week of assignments and have just found some time.

Lecture consisted in design, the first week on it. it covered activities that occur in the phase such as Application architecture, user interfaces, system interfaces, database, network diagram and system controls. Also discussed prototyping of systems to make sure that the client is happy with what is thought is needed. Diagraming and more diagramming is needed but also different layers of archeteture such as view layer, business logic and data level so that if a change is made, it should not effect any other layers.

Tutorial was kind of frustraiting because of a class of 10 or 15 people, it was like there was a participation of 2 people. i find that the way i learn is by finding out how the others think and expand on my thoughts. with 2 people including myself is not enough. oh well the tut consist of looking at the CFA website and discuss the purpose and problems and then solutions. also we looked at telestra and other smaller activities. i thought that maybe there could have been a bit more in the tut but with the input from others it seemed to be fine. i thought the questions could have been a bit harder but i spose its the first week. i know i have pritty much just bitched but i felt that it was necessary.

Week 7

A bit of a small week this week although stupid me, i thought we had 2 weeks holiday. dont ask why, im just plain stupid.

well the lecture started with an AFL blue slurpee from 7eleven. i thought i would give it a try and it seems to be a great refreshing start to the day. ok the leture. finishing analysis is the topic and it was not really a huge lecture. just spoke about choosing what needs to be done. inhouse development or outsourced and determining the benefits and also if the porject your about to build, is there a package that can be implemented instead. then comparing porducts from other products by giving ratings in a Partial Matrix of General Requirements.

the tutorial was just a continuation of the last tutorial and really did not learn to much more. starting to get a bit more hang of it which will be needed but deffinitly not an expert.

Week 6

Last day of Uni but wait, theres still more. well work to do over the break. as if they can call it a break and make assignments due staright after. defeats the purpose of a break really. oh well enough about that, lets get into blog for this week.

Lecture. Well lets say it didnt start too well, Peter forgot to put transitions on the slides but recovered well with the best yet. This week was about use case diagramming. it pritty much stick figures and circles that have meanings. Stick figures standing for the actors and the circles for the use cases within the system. they then can be connected to show the interacrtion. but there is also an interaction between cases which is <> . then there is use case desciptions which can have either brief, intermediate or fully developed. this descibes the step in which each use case works. also talked about Sample Sequence Diagram (SSD) and Simplified Activity Diagrams.

Tutorial. not too much to tell. just did some exercises using case tools to proactice how to draw the diagrams. also there were examples in which we had to draw the diagrams too. a little difficualt and loads of thinking but was deffinatly will help towards the assignment