Stratergies to prepare for the exam?

[MJRomeo81]

Seems fine to me. But don't stress over the algorithms. VCAA present really clear pseudocode, unlike this example question.

[Yendall]

Just reading over a practice exam I did way back in Term 3.
Question 1:What are the key tasks associated with the planning of software projects?
Determining the scope of the software solution, also taking into considerations user requirements (non-functional and function) and constraints
My teacher said: "The scope of the solution is more in the design brief"  is it?

[billyjackson768]

Hmm... I'm pretty sure planning comes under the design stage of PSM (page 5 of Adrian Janson's textbook) and encompass thing such as writing up all your pseudocdoe, creating data dictionaries, IPO charts and doing all that other design stuff where you work out how the system will function.

What your teacher is probably meaning by the scope being in the design brief is it being with all the information you are given once the analysis stage is completed including your SRS and all that jazz.

[Yendall]

Ah okay, I hope that question doesn't come up haha

So I would talk about the planning of software projects as more of a Design phase?

[billyjackson768]

Ah okay, I hope that question doesn't come up haha

So I would talk about the planning of software projects as more of a Design phase?

Definatly and a design brief is actualy the first bit of information your given before analysis and the SRS even starts. So I guess that's something like a problem a teacher would give you in class that includes all the information on what a client is looking for you to do.

[Yendall]

Ah okay. I'm feeling alright for this exam!

[Lasercookie]

Hmm... I'm pretty sure planning comes under the design stage of PSM (page 5 of Adrian Janson's textbook) and encompass thing such as writing up all your pseudocdoe, creating data dictionaries, IPO charts and doing all that other design stuff where you work out how the system will function.

I disagree. I believe the question

Question 1:What are the key tasks associated with the planning of software projects?

is referring to this study design dot point: "key tasks associated with planning software projects, including identifying, scheduling and monitoring tasks, resources, people and time"

I think there's a difference between designing/planning what the actual outcome of the project will look like (which is what is done in the design phase of the PSM) and planning the software project.

Planning the software project involves organising who does that tasks, when they do it, working on deadlines. This study design dot point was more fleshed out in the previous study design, with the GANTT and PERT charts. All that project management stuff. I'm not sure if that fits explicitly into the PSM. I would be inclined to say that following and carrying out the PSM is working on the software project.

You'd definitely do some of that stuff early on, at the start. It might fit somewhere into analysis, but I think even doing analysis would require some project management (figuring out what tasks must be done, what data to be gathered, who will gather the data). That project management stuff would be something ongoing throughout the whole time - you'd be always checking if you're up to speed with the deadlines etc.

[billyjackson768]

Ok. That's sounds like much more appropriate answer. I hope my advice hasn't done any harm. As I understand it there still are elements of planning going on in the design stage though. But with the things I described that's probably moreso specific planning on how the solution will be made. Rather than the general "planning of software projects" which laseredd is right on top of.

[Yendall]

I think I know what my teacher meant know. Pages 33 - 41 outline everything that is involved in planning a software project. It can include:

• The Design Brief
• Specific Project Management skills (breaking down the project into a series of key tasks)
• The Solution Requirements (Functional and Non-Functional)
• Data Collection [Quantitative and Qualitative] (observation, interviews, surveys, questionnaires, examining)
• Constraints
• SRS

That's a pretty massive list, but it's basically everything involved in "Analysis" I believe?

[billyjackson768]

I'm not sure the chapter is called from "planning to analysis" so it sounds like the transition to me. I think there may be somewhere to draw a line there. To be safe I would probably try and talk about that kind of project managment stuff mentioned rather than focusing on stuff that is largely central to the analysis phase. Perhaps you may be able to call this planning preanalysis? Or am I making a distinction between the two that isn't there? Anyway's lets just hope VCAA are nice to us today. A couple of hard question would be good, only so long as they don't start getting all vague again.

Good luck everyone!

[Yendall]

They probably won't ask a question like that. But i'm sure they'll accept a range of answers, planning is quite vague.

Good luck!

[billyjackson768]

Yeah, they will hopefully be specific when asking questions like that, hopefully.

So how's everyones last minute cramming coming along. I just finished skim reading the book. Now I'm going to go over my lists and go through the 2011 exam again so I can make sure I'm ready to answer similar questions and actually am detailed enough in my responses. After clicking through it last night I think I was a little to light on some of my marking. I better make sure all my responses are right up to scratch.

[Yendall]

Yeah I skim read the book and some notes. Went over the 2011 paper, realised that i needed to be a little more specific. Now just reading over a document i made the other night that covers everything. Still unsure what full marks on the OSI model + relationship with TCP/IP would encompass. I'm thinking something along the lines of;

The Physical Layer of the OSI model is used to transfer bits along cables and determine physical destinations between devices. The Physical Layer is the foundation of the OSI model and is responsible and essential for functionality on the sequential layers. Similar to the OSI model is the TCP/IP protocol stack/model, it follows a similar design to the OSI model being that it has a foundation layer called the Network Interface Layer, which is similar to the Physical Layer and Data Link Layer of the OSI in the sense that it determines destinations and routes data between determined devices. Without the Network Interface Layer the 3 sequential layers of the TCP/IP stack wouldn't be able to function.

Maybe. It's still a little sketchy, thoughts?

[billyjackson768]

I'm not sure you need to go into so much detail about TCP/IP,layers. I don't think that's something that's a focus of the course. Just describing each, explaining the distinction between the two and the relation the OSI model (layer 1)has at the foundation I think should be enough.

[Yendall]

Study Design; Page 41:

"Purposes and Functions of the Physical Layer (Layer 1) of the OSI and the relationship of the physical layer to the Transmission Control Protocol/Internet Protocol Model"
I'd say you'd need to know what the layers do and how they are similar. But to what extent? Do you need to talk about devices that operate at the layers or how the data is routed etc.? "Purposes and Functions is fairly broad if you think about it.