Studio 7

i say no more...

Studio 5

oh this is fun... i'm working up to lots and lots of point.

we have done the structure chart and the database design. more to come later when they put more stuff on muso for me to copy from.

Studio 4: quote!

"must go do count of chairs" - jake

Studio 4: Part 2

i'm so wikid

Studio 4: Part 1

1. What event turns on the telephone? switch to on
   

2. What states does the telephone go into when it is turned on? quiet
   
3. What are the three ways that the telephone can be turned off? low warning, uncharged, switch off
   
4. Identify what must be true for each case. low warning: low ammount of battery, uncharged: no battery, switch off: button pushed to switch off
   
5. Can the telephone turn off in the middle of the Active (Talking) state. not directly it must be hung up first.
   
6. How can the telephone get to the Active (Talking) state? from quiet, to dialing, to connecting or quiet to ringing.
   
7. Can the telephone be plugged in while someone is talking? no, because they are both in the top half of the diagram
   
8. Can the telephone change battery states while someone is talking? yes, because the top half of the diagram and the bottom half can occur at the same time.
9. Explain which movement is allowed, and which is not allowed. One can only go from one state to another using the arrows, if they aren't connected you can't change to that state directly. The action must also be true.
   
10. What states are concurrent with what other states? Make a two-column table showing the concurrent states.

Plugged in	Charged
Plugged in	Low warning
Plugged in	Uncharged
Quiet	Charged
Quiet	Low warning
Quiet	Uncharged
Dialling	Charged
Dialling	Low warning
Dialling	Uncharged
Connecting	Charged
Connecting	Low warning
Connecting	Uncharged
…	…

i'm not going to do all of them that's pointless.

hello to: 1 value point, 1 design point, 1 individual point!
:)

Studio 3

well well well, i'm sick of doing all the work for my group so now i have to be head slave driver, that's how u get 10 group points!

every1 in my team should be reading my blog and the email i sent them about this task. we did all the sequence diagrams for 1 use case, and i'm currently developing a design class diagram in visio because B block computers don't have VP for UML and i can't get in to K labs anymore since IE took them all over, i love how full they are too, makes me feel so good that the IE students are fully using the faculty's resources. anywho.... yeah i'll put up a pretty image from visio here so that my blog is more colourful.

you can download the visio file here, it's been updated since this diagram to include some methods, i'm still not sure what methods i'm meant to include...


more to come later...

Studio 2: Part 2

Do you have a good team? Why?
I believe we have a good team, we have a good range of skills and we can work co-operatively in team together as we have been a team before and we often work together in our studies.

What makes a good team, what will you have to do as a group to be effective?
A good team has members that are good at seperate things. In our group we have two members that are more from the programming side of IT and two that are more inclided to the more theory and written enlgish type tasks

How will the team make decisions?
The team will make decisions by democracy where possible, when there is a draw, i will make the decision because i am the best. just kidding, it will be decided by who is loudest, nooo, if we have a problem that we can't agree on a solution for we will seek guidance from our wonderful tutor Jake.

How will you work together, how will you communicate?
We will meet every week in studios, outside of tutorials we will communicate using email and face to face because we do alot of the same units together, and where needed we will organise a team meeting outside the normal studio hours.

more to come....