Thursday, April 26, 2007
Week 8: The nature of good design
CSA:
Client-Server divides programs into two types
• Server – manages information system resources or provides
well defined services for client
• Client – communicates with server to request resources or
services
• Advantage – Deployment flexibility
– Location, scalability, maintainability
• Disadvantage – Potential performance, security, and
reliability issues from network communication
Summary:
• Systems design is process of organizing and structuring
components of system to allow construction
(programming) of new system
• Design phase of project consists of activities that relate to
design of components of new system
– Application architecture, user interfaces, system interfaces,
database, network diagram, system controls
– Prototyping may be required to specify any part or all of the
design
• Inputs to design activities are diagrams, or models, built
during analysis
• Outputs of design are also set of diagrams, or models, to
describe architecture of new system and detailed logic of
programming components
• Inputs, design activities, and outputs are different
depending on whether a structured approach or an
object-oriented approach is used
• Architectural design adapts to development environment
and decomposes design into layers
Thursday, April 19, 2007
Week 7
Ok so the assignment has been started finally, i think i should still have enough time to get through it without stressing myself out. Although there are other assignments due during this time... ow well we will get thourgh :). Was looking through the sample assignment again after starting, and i must say that i am so happy that we were given this because it would have been very hard otherwise to understand how these things are supposed to be set out and what is exactly required in each section.
Again i am battling against Visual Paradigm and loosing. Peter mentioned that there are some people that can just sit at case tools and work straight from there; i have found that i AM NOT one of these people. I like pen and paper, so i suspect the program will be the last stop when completing the assignment.
I like the idea of Partial Matrix's, although their objectiveness can be biased by the user and their desired outcome if done correctly it defiantly shows the pros and cons of the different options.
Till next we meet,
Paul
Thursday, April 05, 2007
Week 6
These posts are getting smaller and smaller, hmm i kind of knew this would happen! OK so week 6, MORE AND MORE AND MORE of the UML, i don’t see the point in use case models.. they look and seem stupid but hopefully ill understand what the hell they are good for after the assignment. Started using visual-paradigm today, ok for one it would be nice to be taught how to use it! you know instead of just going 'here use'. It was basically trial and error which is so not professional. Meh my rant and obligation post has been completed.
Thursday, March 29, 2007
Week 5
Thursday, March 22, 2007
Week 4:
Begining analysis (but does not reference the chapter of the same name in the book, really means chapter 5):
The starting point of analysis is is attempting to model an event. An even being an occurrence at a specific time and place that triggers a system process. There are three types of events:
External
- Outside the system
- Initiated by external agent or actor
Temporal
- Occurs as result of reaching a point in time
- based on system deadlines
State
- Something inside system triggers processing need
The rest of the lecture was basically about all the different modelling diagrams contained in the UML. It may become confusing when differentiating them because a lot of them are structured the same way and include the same information. We have already looked at Class diagrams in java and ERD/DSD in database so I’m not too worried, but intend to go back and look over the differences.
My father is a member of a private golf club that has such a system in place, so I’m aware of most of the extra information need to operate. This helped immensely when interviewing the mock client because i could already foresee the answers to the questions i had and was merely clarifying what i already knew.
Tuesday, March 20, 2007
Thursday, March 15, 2007
Week 3
We all know about the different techiniques for information gathering 'reviewing existing documents, interviews, observation ect...' and what each strength and weeknesses assocated with these are. This week we looked at how a system analyist would go about aquiring the information needed to create the system from its users.
We identified that users dont always work the way the organisation created system works so the correct way and acctual way of doing something has to be identified during this process.
There are two types of requirements functional (activities systems must proform) and non-functional (such as useability, reliability, and security requirements).
PODCASTS: I cant help but think that this topic was brought up in the tutes as a way of infulencing more individuals to sign up for the unit podcast.. *casts a disparaging look*
Amusing facts: Tutor has left the room twice to take calls :P
Thursday, March 08, 2007
Week 2
There was a lot of information to take in in the lecture! We covered the SD methodology and the different approachs (waterfall, overlap, itteration) to SD.
The tute was a repeat of the last one, which was just inforcing the skills we learnt in the first one.
Update: oops i just made this post in the last two minutes of the tute and was going to come back to it. So now here i am :P
Yeah ok as i was saying there was a lot of information! But its basically information we have covered either in earilier units or VCE. So im not too worried about how much we had to absobe but i have gone over it again just to make sure i know the majority of the imformation.
Till next we meet,
Paul
I LEFT HOME EARLY!
Sitting I’m my tute wondering what is the appropriate amount of time I should stay if the tutor hasn’t turned up… You would think what half an hour? (24 minutes and counting :P). Im going to try and battle on by myself.
Paul
Thursday, March 01, 2007
Tute one
Good start to the unit paul, 10 minutes late to the first tute! Grr over an hour with the traffic! (Yet still arrive before it begins)
Ok so the tute has started off a bit slow, first we discussed what a system is and what the role of a systems analysis is. I think it was very important that we did this because everyone was still a little iffy about what these were in relation to the unit, people were getting confused with an information system rather than just a system.
The exercise was to divide into groups and select a subsystem of the water supply system. We selected the distribution system, and had a bit of a hard time identifying the stages in which the water must go through to reach the end consumers. None of the websites that were linked as extra resources provided a clear outline of the processors that take place (or rather we couldn’t find the relative material on the resources provided). We sat down and logically thought about how the system worked and then created, what would probably be very simplistic in relation to real life, staged process.
Overall i believe it served its purpose, a simplistic introduction to how a systems analyst tackles a problem that wasn’t overloaded with information we will never remember, nor need.
Week one over and only twelve more to go!
Till next we meet,
Paul
Wednesday, February 28, 2007
Exciting News!
So far week one has gotten off to a good start, we were introduced to POD (Peter O'Donnell) who can best be described as a character. His enthusiasm and quirky attitude has been unanimously deemed as a plus, and i personally believe it will make covering the material seem a lot less like a chore (well thats enough ego rubbing i think, my hands are getting tired).
We have been told that the first assignment will be presented in an mp3 format. This has me a little worried simply because i hate ambiguity, its far easier when you have a clear direction. But i can definitely see the positive aspects of this option, in a real life situation we would be relying heavily on notes that we have taken and because we will be allowed a follow up (speaking to the tute in a mock interview) for clarification im less worried about the apprehensions i currently feel.
My first tute is tomorrow so ill try and complain some more then.
Till next we meet,
Paul