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

Week 5

Busy times are happening at the moment and I just feel like time is slipping away. But lets do something different for a change. lets start with the studio

Well I didnt mind this week. It was very difficualt and challenging. First exercise was to create an event table using the example of a lift. It seemed easy when told but found it extremly difficualt to doccument it and what goes on. the whole class and even tutor found it extremely difficualt but have found it usefull and gave me experience in which i can then learn in the future to really sit down and think about it properly. then the class diagrams of an universtity wasn't too bad, i actually found it extremely easy but maybe due to doing it in programming.

ok now the lecture. learnt about the traditional or structured apporach where we talked about event tables, DFD, Decision talbes, Dicision tree and process dependency diagram. i had learnt in the past about dfd but i never really understood dfd and the abstraction it can have. there is first the context diagram and then level 0 and so on but they then can link to each other. i thought there was only 1 level and it shows everything which this way is much easier. it makes sense.

Mid semester break comming up, cant wait but its goign to be a short break with all the assignments comming up.

Week 4

Hello world, back again for an exciting day. Well its been a very busy week and am starting to feel the pressure again for assignments. Not doing too bad with it but feel time is getting away from me.

Well lets start where we always do at the lecture. It was a dark and rainy morning but lecture was interesting. Spoke of different ways to model in analysis such as mathematical, descriptive and graphical and how we will be doing it all the time. There really is no right answer and doing it at one time and doing it again is not going to be the same model. The first model is also not going to be the final one because you find other better ways in going about it and more ideas into the system as well. There are different types of events such as internal, temporal and state. can be difficault in identifying these events and also can be done in the design phase. some types of graphical are Eventables, ERD, class diagram and UML. Also spoke of relationships such as 1:1, 1:many and many:many. this week was better cause there was not so much confussion and loads of content which then i could diegest.

the tut was difficualt cause asking the questions i had was difficault in explaining what i was meaning. difficualt to give an example but i suppose if i gave some type of diagram then maybe it would have helped the situation. also in the groups, each of the members kind of gave the opinion in the answering which made it difficault cause in the real worl you would only have people that would know what was wanted and how it worked instead of the students telling me how they would do it and not what the client wants. that again maybe confusing but its diffcualt to right it down, instead i need to speak it out. looking forward to really starting the assignment as its going to a good challenge.

till next week

Week 3

Well im a day later then a normally am but still cracking to do these blogs. Being very busy yesterday just gave me no time what so ever.

so lets start shall we. lecture was very interesting but i fell very sick with the flu and got worse as the lecture went on so i found it difficualt to concertrate. but im well again after 2 days of not much action. so the lecture was about requirement gathering. learnt about all the techniques such as analysis, information gathering, meetings, bpr, discussions with users, activity diagrams, questionnaires and so on in which helps in anaylising what the system may require. building prototypes of the system was a good way in asking the user if that is exactly what is needed, with no function, just an interface gives the user a feel and can then discuss about changes or things they liked. there is again just so much in this lecture but i feel better this week with the amount of information that was given this lecture compared to last week.

Tut was good and bad. listen to audio from a member from basecamp project. it was interesting in getting another persons perspective but he made me feel like that everyone should follow his steps such as no diagrams, make errors. i think that this maybe true for such a small project in the way of the staff but not so much in larger cause if a new person came in, he or she would have no clue to what was going on and how it works. it was good on the way that if you stay positive, the project kept running. also liked the idea of their billing system where they made it after launch cause they used the time wisely. i felt it really wouldnt help me so much now but only in the future.

Week 2

2nd week is down but it feels like 5 or 6 weeks allready. Very successful week and and i feel that i am really getting into the thinking of looking at a system and then trying to figure the steps invloved in the system. also my thinking is becoming more broad which i did not think was really possible.

anyway lets start with the lecture. lecture had alot of information whih really made the it float in my head and not sink in so i needed to read back into the lecture to just soak all the information. learnt about System development lifev cycles which had learnt before in past subjects but was good to reenforce it. also learnt different types such as the waterfall approach and the rapid application development. each steps were explained in depth but like i said just too much to learn in a 2 hour lecture.

Tute was good where the exercise was to figure the pocesses within a fruit and veggies from the farmers to the consumers. the subsytem my group did was the consumer side which was difficualt suprisingly because we chose it beause it sounded easy. i thought there was really only one process but really thinking and discussing about it, found that there were alot more then expected such as qulaity check, making complaints, interacting with the other subsytems such as retailer such as in the way of pricing and complaints. the presentation was very successful and extremely happy with my progression in this subject.

Week 1

Well its the first week back and im here. Well lets start with the first lecture. I was surprised that i had not fallen asleep, na only jokes. The lecture was really good, not too boring, gave a great overview of what im in for for the rest of the semester. Seemed scared but now cant wait to really get into it.
Now for the first Tute. First created an account for blogger in which im taking now to the world. Then we moved on to the first case study which was about water management and water constraints that melbourne has. My group did the processes in which disposal of water was occuring within the system. at first it was difficualt to get into it, trying to figure what the questions meant but its due to the large rush of being 50mins late so its understandable. also it was difficualt with people in the group as they really had no idea what the questions were asking and found it difficault to research the case study but it all came together which was good. i suppose that the main problem was not all students were first language speaking english so it doesnt help. great experience and i suppose that this is always going to happen in the feild when i do go to get a job and its a learning thing. so it all went well, no dramas but it was a good exercise to get started.