FIT 2001 Week 7

Lecture

Today I found the material very general and not specific in any case regarding design.

Design phase activities and key questions table looks very important.

1. Design and Integrate the Network
2. Design the Application Architecture
3. Design the User Interfaces
4. Design the System Interfaces
5. Design and Integrate the Databases
6. Prototype for Design Details
7. Design and Integrate the System controls

The 7 above I would summarize as, Integrate into network design, Application design, User interface Design, System Interface or how sub systems interact with each other design, Database integration design, prototype before implementation and Integration of system controls.

I guess a story probably is more interesting then the above though.


A company releases a tender for an upgrade of their system. Now after all the analysis has been done, then the design work can begin. Some key notes is whether the current company has a network and can we actually use it? If we can then it solves a lot of key design issues, if not then we may need to reconstruct a network system that can integrate with the current network for our new system.

Whoever gets the tender has to come out with a proposal and this can be describe in the application architecture and demonstration of the application can be done using user interface mock ups if its a software system. The system interfaces requires integration of communication between the company's system and the new system being developed. The database also has to be updated to link up with the new system. A prototype is developed and tested and then we integrate the entire system controls into the new system.

And then we come into the topic of networks....Ah networks, reminds me of the FIT 2008 course....ahh memories.....Networks are like a whole entire field on its own. Integration into one requires a lot of planning and even the bandwidth can bring down a good system. A system that takes up too much bandwidth will compromise the companies current systems that are still being used. So networks are very important because of communication.

Client - Server, 2 layer, 3 layer, just seems to be cascading or buffering load by using seperate servers to handle different sets of data.

Single tier, Multi Tier Computers, Clusters.....describes the systems of computer interfaces

• Internet – Global collection of networks that use TCP/IP networking protocols
• Intranets– Private networks using same TCP/IP protocol as the Internet
– Limited to internal users
• Extranets – Intranet that has been extended outside the organization

Tute
Today's tute was about thoughts on design. My thoughts is that design is a very messy business. In order to actually be a good designer, one must have a lot of references and knowledge on the particular design before one can design for it. Going in without a plan in design wastes a lot of time. I remember how hard it was to make a inertia powered model without a plan.

Anyway looking at websites showed me the multiple use of architectures and then you have competitions between cloud computing and the traditional server client architectures. I see the usefullness of the cloud but sounds like more of a power company sort of service. Imagine then in  world fully on to cloud computing, one only needs to use a word processor by renting a service for word processing from a cloud. Then we would be charged based on the rental time or usage from that cloud. It would keep our computers neater and backups are handled by databases but privacy and security may be an issue.

I think I am confuse now regarding this topic, must find out why are we learning about network architectures...So I asked Sutti and I finally understand. Before we can design a web system, we need information on how much load the system can take. The benefits and risks of different architectures. ....

Anyway can't spend anymore time, in conflict with other subject assignments and exams, such a busy weekend

FIt 2024 Funny crash

 

GCC crash




after GCC Crash , under projects -> freeze...then on run looks like the above....

FIT 2001 Week 6

Lecture

Use case diagrams...ah....long live the actors who made our lives so enjoyable.

Users are known as actors well in this role playing game anyway. Games seem to come to my mind when I think of Use Case diagrams. Developing games require a lot of objects interaction within the system as well as User interaction so definately there must be Use Cases to test whether a certain functionality is required, desired or even if its worth implementing.

Lets say an Ogre wielding a club.Most likely whack the player for some damage . The player also can interact with the Ogre thus whacking the Ogre for some damage as well. This would be called an includes relationship. Well obviously 1 whack won't do so hence we then have the repeating message to associate that it will take a couple of twacks before either the Ogre or the Player gets knocked out.

Domain models are static models but use case models are dynamic. I believe the meaning is that domain models are subject to iteration but they are highly fixed to the requirements but the dynamic models require more user interaction and thus requirements change every time on the whim of users also iteratively.

Drawing use cases involves a stick figure defining the role. This role is highly dependent on who the system being developed is catered for. Thinking of roles reminds me of my time playing Neverwinter Nights, following D&D roles. Roles determine who and how will that role affect the usage of the system.

CRUD, create ,read/report ,update, delete....Use cases should cover all the above because then the system can be integrated fully. Like the Ogre above which has to be created by someone, able to report and be read, update its status or on KO be deleted in the system.

Tute

Tute gave some practice on domain modelling and use case diagram...To do a full domain class diagram seems to be quite tedious because of the interpretive nature of the cardinalities.

One thing tht I asked my tutor was regarding the System Sequence Diagram. Can the system actually send messages to the user? I didn't thought about it because the arrow denotes message sending and the dashed line arrow represented return message so I was informed that it is on the perspective on the user not of the system.


For example, System displays a prompt asking for user to click okay or cancel. Wouldn't this be a system sending a message to user. Yes in some way but note that before the system can actually display this mesage the user must first see the message and thus it would look more like , User sends a message to the system I want to do something because I saw this message, system responds by sending the appropiate message back and then the user sends the message in respond to the return message of the system.

Got to start on my assignment 2....