FIT 2024 Week 2

Sorry for the delay, fellow readers. My laptop board level failed on me and I had to get a new lap top. So I should be back on track writing another blog-pisode.

FIT 2001 Lecture

Actually lecture was interesting this time, since it was domain modelling. A model drawn with as little implementation information as possible to describe a system to be implemented.

To describe things in a system, that is modelling. Modelling is very important to create a plan or roadmap to imagine the end system. It fits all the requirements into understandable blocks so that there is an organized plan to build the system. 

Well if you fail to plan then you plan to fail.

In an object orientated approach, the things are objects with their classes governing the objects blue print.

Class : Type of Thing

Object: The Thing

Method: Behavior of the Thing

Attributes : Descriptive values of the thing

A method I picked up is identifying the nouns and verbs. Nouns for things and verbs for functions of those things. These help make the domain model tangible.

Cardinality / Multiplicity describes the relationship between objects with each other. An example would be a single hospital to multiple departments would have a cardinality of 1 at hospital and 0..* at departments. The '*' character represents many.

Unified Modelling Language is a tool used to model systems. In an object orientated approach, classes, attributes and methods fill most of the domain modelling.Still new to this way of modelling and hence lacking a bit of the rules.

FIT 2001 Tute

A sub-class and a super-class share the amount of attributes of their objects. This is due to inheritance. This is a form of generalization. 

Describing multiplicities, describes associations. The way objects relate to each other, that was how I interpret it. This description helps the developer, understand the relationships between the classes and their neighbouring classes.

Aggregation or whole-part relationships are relationships that relate objects to its parts. Like a car has an engine and multiple other components.

There was one question with the problem of creating a student, teacher , professor system. The question was why would the Human Resource Committee be omitted from the system. I found that it was not the main point of the system problem being described but maybe it was due more to the description of the human resource committee was incomplete and thus with not enough information, you do not go include into the system an unclear object. An unclear object increases the complexity and the requirements may not be met and hence wasted money and time. 

Visual Paradigm is an interesting tool. I was fussing with it since it doesn't work like an ordinary drawing tool where you can just draw lines all over the place. Instead the links are quite specific with generalization lines and aggregation lines to link the classes together. Compared to other visual tools though, I felt like the tool was a bit complex. One thing I do like about the tool though is that it works by projects so I can have multiple diagrams all in a single file instead of image files every where around my computer.

Until my next blog

FIT 2001 Expectations and Reflection Week 1

Expectations

This unit I foresee that I would be seeing a lot of analysis going on. I have read a Software Engineering book before attempting this course and there are some similarities like the waterfall model. System analyst means Business analyst as well as Information Systems Development. It is analyzing the aspects, outcomes and risks associated with the need to implement system solutions to a business problem.

My beginning expectation is that I predict I will be interested in what tools are available because I do have a system that needs some re-development for my friends back home.

Lecture 1

Today I was a bit bored because the content may just be because it was the introduction since I have read about agile development, waterfall models and such. Although the content was boring, the thing that I got out of it was that I like the Agile Modeling Paradigm especially Extreme Programming methodology. Changes are something that I believe that must be embraced because it is a natural order of life. If I don't change then I cannot improve.

The methodologies all seem similar with changes here and there, so I guess System's methodology is more of a personal taste then an actual algorithm that if you follow rigidly you will obtain a specific result.

Two methods of System analysis Traditional and Object Orientated. I guess object orientated involves object in world of interaction whereas the traditional method is more of step wise, linear, sequential procedures.

Note : Dr Yen Cheung is my lecturer.

Tute 1

The tute was pretty fast because NetBeans IDE allowed me to create a database on a server and update it instantly. That's pretty cool as looking at the java code, at the number of lines that I would have to write, it makes my world a whole lot easier. The NetBeans IDE creates the code based on database of already written code, this is my impression. Maybe patterns can be used instead.

I have used Eclipse IDE before and it does help abstract a layer above the actual digital logic layer. Assembly layer is fun. The downside I suppose is that it is very predictive which may apply unneeded code or comments.

Productivity should be the same for a similar type of system no matter the size. The development of models should be the same if the system is similar but it is still highly dependent on the type of system and its environment.

5 Assignments, choose 2...gosh....all interesting....so planning to do all....

Note: Suttisak.jantavongso is my tutor.