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.
Wednesday, March 28, 2007
Wednesday, March 21, 2007
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
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
Thursday, March 15, 2007
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.
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.
Wednesday, March 7, 2007
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.
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.
Subscribe to:
Posts (Atom)
