All language subtitles for sgki-080

Hello, everyone. Can you hear me?

All right. Yeah. He's a cerveza. Yep.

Yeah, I can hear you clearly. I can hear you.

Okay. All right. Good to see you.

Only have 22 people, and it's being recorded.

So, um. It's so good. Okay, let me see what's going on here.

Okay. So we are going to, um, start talking about the final report.

Um, we spend, um, this term, you know, next few weeks, uh, exploring, uh, different aspects of the proposal.

Okay, so we have, um, in the in the previous term, um, we focussed on more, um, is someone saying anything, uh, who would become one of us?

Okay. So, uh, if you could, uh, mute yourself, that would be good, because I see a little bit some background.

So. Okay. Okay. So, um, the last time we looked at some, you know, broader topics like project management, conceptual thinking, strategic thinking.

And also I gave you some learning, um, activities, uh, involving, uh, technical writing and, and some recordings on that.

So, uh, today we are going to build on that and integrate that into the final report.

Okay. So let me, um, share my screen.

Okay. So, um. If you get the report.

Okay. So, anyway, um.

Seems like everything is progressing well, and, uh, uh, we, uh, you know, following your, your weekly, uh, journals.

And then we have, uh, check in sessions for independent projects and, uh, the, uh, had a, uh, uh, mental evaluation.

The first one, uh, last week. And, and we are collating that information as well.

So everything is, is on track.

And I hope your projects, uh, in general, you know, doing well with the industry mentors, um, and everything is on track from your side as well.

So today, then we will look at the final report.

So what I'm going to do today is to talk about the, uh.

The. Final report template.

And then so it's here under the impression that I wrote a good template.

And also I'm going to talk about, um.

Final report. Harvey Harvey, mock the final report and also the presentation.

Okay. Those are the two objectives for today's discussion.

Okay. So, um, so what we have here is that if you go to template and pull out a final report template and um, okay, here it is.

So that's the um, project template.

And uh, if you look at the um. Trading.

Um, so we are going to look at the grading criteria.

So it is different to the way the proposal is, but it's much more, uh, more, um, high level, uh, in terms of uh, uh, just to one single grade.

Yeah. Okay. I'm going to come to that as well.

And then also I'm going to talk about the presentation marking, which is much more, um, straightforward in the sense that we have,

you know, different items that the, uh, presentation quality of the presentation will be judged.

So we'll go one by one. Okay. Um, so, uh, final report.

So those who downloaded this before, um, you may want to download this again.

Um, I did, with some minor tweaks, very minor cosmetic changes, but it would still be good to, uh, download the, um,

this template and some wording, some I added some extra clarifications in some places, but this is still a minor, very minor change.

But you know, make sure that you get the this one, the current one from the.

Okay. Um, okay. Before we start, do does anyone have any comments or, uh, any burning questions?

Okay. No worries. So even, uh, uh, if you if you if you have questions during the presentation, during this lecture, you can stop me and ask any time.

Okay. And I can see the in this presentation I can see the chat.

So, um, you can just, uh, you know, give me a buzz and then, uh, ask your question.

Okay. Um, so the final project in many ways is similar to the proposal.

So in that sense, you would see that it's a kind of seamless, uh, extension and expansion of the proposal.

So that's a good news, right? Um, and the the main, um, difference would be that you have real results and outcomes to present.

So that's a new addition. So, um, uh, we'll, um, go with the in the go with, um, each item and each page.

And then from next week I would take different sections and talk about those, uh, in terms of how you can, you know,

think about those different segments that help you to I will want to help you to write those sections in the best possible way.

Okay. So one of the things okay, the very the final report is going to be judged or marked is that we, uh, we have uh, so-called sessions, panel,

uh, sessions for the presentations, we will have 7 or 8 pedal pedal sessions in the second week of, um, in the second week of exams.

Okay. And, um. So each session would have two judges and two staff members from computing, and they would also mark the report.

So, no. So you have two judges marking your report and the same two judges attending your presentation and, uh, evaluating that.

So we get the average of those two looks like for the presentation and the report.

One of the things that, um, we find, uh, we also found that in the proposal and also in the previous years,

the judges find it very difficult to understand,

not just this doesn't apply to all proposals, but, um, in general for a lot of, uh,

proposals and reports of this issue that the judges find it difficult to follow what you are doing.

Right. From what you explained, they cannot get a good picture of what you are doing or what you have done in the case of Final Report.

So, uh, so there has been a big issue because the,

the items of the different sections are not really connected in the way you present your information in the way you talk about it.

So there has been a serious concern.

And also in some cases some projects are totally, um, uh, totally difficult to penetrate.

It's almost like a big block, right? Um, the it's not explained well enough, especially when the topic is quite, um, um, uncommon.

You could be, uh, designing a dissertation engine.

Um, you know, that, like the verification of different, um, the signature items or something.

And that's all very common. And then the technology of the jargon is very uncommon.

And the judges haven't done these things before because there are 200 projects here.

And, you know, nobody has done all those projects. So some projects are so, so difficult to even, but just we would start to understand.

Okay. So for that reason we had to be extremely careful about how you go about it.

So that's why I will go over the template today and then have another, uh,

few lectures on how to go about about different items here so that you can I hope you have expanded, uh, all great understanding of, uh, what to do.

So starting with the, the, um, first page, it's very similar to the proposal.

You write your title. Um, so make sure that there is a title.

Sometimes people forget to write the title. Okay.

So put your title and also highlight what, um, your project is about industry dependent or research project.

So delete the ones. Yeah I have you have some instructions here.

Choose the one that applies to your project and delete the other parts.

Okay. Same here. Uh, this is written for uh, um, the, the industry with a mentor and so on.

And if they, you know, if they don't apply to you, remove them and and just do what's necessary again.

So those are the instructions. So the refer to the instructions.

Now here's a new item. Okay. Executive summary.

When you have completed the project, it's it's customary to give a kind of summary.

Summary of the overall project. So the one thing to remember is that everything is in the past tense.

Like if this is this, this is reporting the work that has been done.

So sometimes, uh, sometimes right, as in the proposal, I will do this.

So I will do that this way. Uh, it's all in the future tense.

So that's not that. This is not about future tense. It's about past everything has.

So everything must be put to the past. Okay?

So avoid using future tense in this.

Right? Right. Okay. The first item is the executive summary.

Then you have a table of content. Then we have a glossary and acronym.

Those three are new then background.

Uh we use this. We had this before requirements and goals.

You had this before. Metadata was before. And um results and outcomes.

You had this before, but no, the, the slightly different, uh, requirements, uh, in terms of evidence and providing evidence.

Then, um, the reflections will be new, you know, uh, reflections on the work you completed and then the references, um, as before.

And the other new thing is the appendices. Yeah.

So appendices is where you put, um, um, at the end of your report, um,

any material that it's useful to show, but it doesn't have to be, uh, in the main text.

Okay. So all these things, it could be code, it could be screenshots, it would be tables, you know, it could be graphs.

Um, all those things can be, uh, put in an appendix at the end of the report, right into the report.

So, um, that's what the appendix is. So that's pretty much the, um, report template in terms of headings.

And you, you see 2 or 3 new items. No.

Okay. Let's um, um, let's go um, through these items.

Um, now, um, remember, I will also emphasise this, uh, post to uh, note as well report.

The report must be 15 to 20 pages.

So we you have to stick to that limit.

It's so important. Um, the proposal or the we said five pages.

Uh, some proposals were like 20 pages. Um, so we didn't really, um, didn't really, um, uh, do anything about it.

We mentioned that it was too long.

However, this in this, um, um, report, we will look into that mainly because we have, um, to go through 200 reports.

And then we had to have the, um, the presentations within a week.

And also then we had to send them a soon after.

So it's a very, very tight time frame. Okay.

So we had to stick to 15 to 20 page time.

Um the the page limit. It's a strict requirement.

Strict condition. Okay. I'll make a post on that as well.

No. Um, if you have if you have done any, read any literature, like a conference paper or research article or book and some books also had it.

They have a summary. Uh, sometimes a book has a summary of the whole book, and sometimes each chapters have a chapters.

Um, can have a summary of what the chapter contains.

So it's a very, very brief summary of everything that document is about.

So here we are going to use the headings below.

They have three headings uh for headings to give a short very brief summary of the project giving an overview of the problem address.

So he has a problem. And just what is the problem. So again when you write think about your audience.

Your audience in this case um uh will be two judges,

academic staff members who don't know anything about your project in terms of really, you know, what you are doing.

So, um, it's totally new to them, and they are reading about it for the first time.

So you have to keep that in mind if you're totally new people.

So they are looking at it with fresh eyes, right?

They would not in your checking, um, meetings. Uh, they haven't evaluated any of your work before you.

They haven't seen your proposal. Nothing. Okay, so write it.

Um, write for a totally new, fresh audience, right?

Okay, so you the the problem.

Address the goal. And the methods employed and the outcomes in terms of the product process developed.

Describing his purpose, features and testing, as well as its strengths and limitations.

Limitations. But this is generally the case in any kind of research project, any kind of project.

You talk about basically saying what you know, why did you do it, what was the problem you addressed?

And then with the problem, you develop some, you know, you always set a goal, right?

This is my goal. And they you omitted it.

You would design a method to achieve both. And then at the end you talked about, uh, what the outcome is like in terms of its purpose,

the features and testing and the strengths and limitations.

So important thing is that each it should be 150 words.

It's very small. It's not like a less than half a page okay.

Maybe got a page. So so when you do something this is about your whole project.

And when you do something like this, like condensing a whole or 14 weeks of project into 150 words,

and then the, uh, you know, with these specific sections.

So you had very careful about what's the most important information under each section.

Okay. So you have to do it in order to get it down to 150 words.

And you might say, you know, I'll go over it in detail.

So next week, uh, you might say, I just, you know, I had just this problem in this particular company,

they have this problem in the where it's not efficient. And the goal was to develop an improved web system with, with X, Y, z, you know, features.

And then you develop the you use these methods of flask and MongoDB, um, for the, you know, database and so on.

Uh, so very, very to the point, very brief, to the point, uh, but still connected, like very clear to the chat.

And then at the end, you could say, then, um, I achieved this website, uh, with these features.

Um, it's functioning well. It was tested and its strength is that, you know, it's not, um, scalable or whatever, you know, um,

whatever the strength and the strength is that it's it's much more improved and it's efficient.

But the limitation would be whatever that limitation is.

So generally the projects, uh, when they were achieve the hundred percent, um, like a future proof, uh, everything, you know, perfect kind of system.

There's always some sort of a limitation or something that can be improved.

So that's that. So the point, the takeaway, uh, the take, um, the, uh, uh, whole point is that it has to be very succinct, very, very to the point.

Then you can only cover a couple of sentences under each section or even one sentence in some place, 2 to 3 sentences in other place, but 150 words.

So sometimes people write more than that. It's not also restricted to the, the, the word limit, um, in the executive summary.

Okay. So um, remember that way to the point.

Very succinct and most crucial information should go there.

No table of contents. You must have seen this many, many times in textbooks and many other documents.

Um, so table of contents is a very useful, uh, item, uh, specially for, for the, the readers.

So, uh, you would say these are my headings.

And then under each heading you will have subheadings and you get to put the page number where each um heading.

Also pages can be found. So if someone wants to look at a particular item then they know which page they have to go to.

So um, that's the table of contents and the glossary acronym.

And this is also quite useful because um, there are we are looking at 200 different projects and many,

many, many different, um, acronyms, uh, being used.

Um, so all these uncommon acronyms, um, that the um, you may have used in your project, you have to list and define any non-typical,

uh, technical terms and any terms related to the application domain of the project and expand the acronyms.

So sometimes, uh, the particular domain will have its own, uh, acronyms that you probably will use quite readily.

But the judge may not have any idea what those acronyms mean.

So, um, other than very basic, uh, acronyms that everybody can understand or any computer person understand, uh, list.

Um, so the list, everything, um, that your project uses, um, the value of this is that like the table of content?

If the judge, um, you know, by reading it and come across, um, one acronym, but they forgot the overall meaning of it.

Um, um, so instead of finding the exactly in which section that was, um,

explained, they could easily go to the glossary and find out the meaning of that.

So the reader will find it very helpful to have a glossary, um, and the acronyms expanded acronyms.

Okay. So that's a very important one. Now we are going to the more familiar territory, uh, because you have done this and thought about this before.

Um, the background. And uh, again, I want to emphasise, um, couple of points here.

Um, when some, when a section asks about a particular, uh, information, just give that information and not any other information.

For example, sometimes in the background, some some of you will write about the company, the goal and the methods and even sometimes the outcomes.

We don't need that, especially when you have to stick to a particular type, particular um, page.

It's also crucial that you don't, but in general it's not done that way.

All right. So the why we have different headings is because that heading has a meaning.

Each heading has a meaning and you have to give meaning to that heading with the information you provide under it.

Under it. Right. So background means background not the problem, not the solution, not the right.

So it's the background. So in that way you simplify your thinking.

Uh, you only have to write particular information in a particular block, not other information.

Right. So that means you look at what exact information is being asked for each section.

This the most important thing. What is being asked and right only that.

Okay. So that's a important message. Take home message here.

So in the interview overview, if your project is with a company or you know or another organisation,

provide a brief description of the company organisation and their business.

Why do we have this background. Again the church you know totally new person.

Uh, you if you start like, okay, I'm, uh, I might some people start immediately.

The my aim was to develop a website for this company.

Okay. Which company? What this company is about, you know, it's it's not clear.

So it's not about what you're going to do. Just a simple example information about.

Okay, my, uh, you know, my project, um, uh, you know, this x x, y is a company and it's located in Oakland.

Um, its purpose, their business is, you know, whatever they, they do it services to businesses or whatever they do.

And it's a very large organisation or very small organisation, large,

meaning it may have 200 people or small, maybe, you know, 1 or 2 people, maybe maybe ten people.

So just to give a context. So yeah, to your project where what is the background to that.

You know the, to the, your project in terms of the, the, the the project first.

Right. So um, so it's a basically about what is what if you're doing an industry project, what these companies are about, what are they doing.

You know, give us a little bit of a description so immediately that, you know okay.

All right. I see no plan or size of company. Okay.

This is first. And then they will kind of place you and your project in that context, in them in mind.

It will help them also then understand what you are going to talk about in the in the subsequent sections.

Right. So if you are doing a research project, uh, you can provide, of course, you're going to have a company to talk about.

Uh, but if you are doing a research project, for example, with egg research, then you can talk about egg research.

You know, my project is with the egg research. Research is located here, uh, and their business, the you know, the purpose is this.

And, you know, they may have different branches in different, um, different, uh, cities and, uh, and so.

So if you are doing an independent project, you can talk about my, um, the uh uh um, uh, you know, I'm working, um, with a hypothetical company.

Again, you can, uh, give some sort of a description of this company.

Yeah, it could be located anywhere.

You know, you just you made it up, but at least you know, you the a description of what these companies are about, what they're doing.

And, um, just a general overview. If it's a large company, small company and so on.

So, um, so it's not, uh, the, uh, it's a, it's a when you write something also, it's easier if you start with some sort of simple information.

So these, uh, background is very easy to sort of getting into the, into the project from a judges perspective.

Okay. Once you have said that, um, this is the, uh, background to the company,

then you can say the next the next question, judge who's asking, is that okay?

They might say, okay. Yeah, okay. This is a company. I can understand that. So what's the problem now?

So then you say, okay, describe the problem you are solving in your project and why it is a problem to be solved.

So, you know, like I said before, then you know, focus your focus now is a problem.

So you can say this particular company, you know, has this issue with their, uh, business analysis, you know, system.

Uh, it's it's inefficient to what, whatever.

So why it is important to be sold is that they are losing customers.

Maybe they're losing businesses. Maybe, you know, um, what that, uh, you know, problem, why it needs to be solved.

So then the judge, from a judges perspective, they would have you have added some additional information.

Right. So this is a very significant because the problem is what defines your project okay.

So it has to be clearly stated. Again it's not quality is not the the quantity doesn't mean quality.

So you can, you know, write the clearly succinctly uh, but meaningfully okay.

So describe the problem. And then you can talk about the project team, um, you know what was involved in it.

And they could be technical people, industry people, academics.

So other stakeholders, other parties relevant to your project.

Right. So your team will be anybody or the people who will perform some role in your project.

Okay. If you're doing if you're if you have created the hypothetical company with the, um,

chief technical officer or chief financial officer, don't put them as your project team because actually they are hypothetical.

So you don't have real people like that.

So in this project team, would they hire people who who will be working with you if you are the only person then to,

um, the sole, um, uh, team, right.

Uh, of the team member I don't have any other if you plan to, uh, have some,

uh, survey is done, then you can you have some stakeholders that you used,

but make them be them, you know, make sure that they are actual, real people and then they have a role to play in your project.

Okay. So that's, uh, um, uh, repeat from background from the proposal.

But now that you have already done some, you know, done the work and you will don't copy from the proposal,

but try to, you know, make sure that it actually flows, flows well with the rest of the document.

Okay. You may want to improve some aspects. So now you can see that now the from the judges perspective they know the company.

They you know the problem. They know the team. You know. So they have you are providing some sort of a clarity to the project.

And now the but once the problem is described, uh, it's a more general right.

You describe the problem in general terms. Again, when you describe the problem, don't say, um, I'm going to solve this using the x, y, z method.

Uh, and so on. So don't put them into it.

Don't put the out of the just to specify the problem is simple layperson terms, because we are not using a lot of technological jargon here.

It's still a vague background, right. That does it. So in layperson terms you describe it.

Now the problem is described in the chat to see how you kind of converted that problem into a specific goal or goals that you wanted to achieve.

Uh, and then what were the requirements. Right.

So any project would have certain requirement that means certain, um, uh,

certain levels of achievement in certain aspects, uh, or certain quality aspects, right, or functional aspects and so on.

So, um. So when you start, it's important to give an overall goal of your project.

Okay, so overall goal is the highest, highest, uh, perspective right.

Highest view of your project. So if it's a website, you might see my overall goal of my project was to develop a website that is, uh, um,

far more, um, advanced or, uh, far more efficient, uh, than the current system or something like that.

So it has to be an overarching statement. It's not about writing a report or produce documentation, all those things.

They are secondary elements that provide an overall goal of the project and then the requirements.

So, uh, you might say that the, the, the requirement was that it has to um.

It has to, uh, accommodate, um, certain important, you know, aspects.

Not very detailed.

Well, you don't have to put hundreds of details here, but in terms of overall system, you may have set, you know, few requirements associated with it.

Uh, and those requirements would actually, uh, define the your success.

So if the requirements are met, then it's a, uh, project is successful.

So you may um, most of the time the overall goal can be really big.

So you may have some sub goals like needed to achieve that overall goal.

Right. So in the, in the in in terms of web development, it could be that, you know,

the front end or the back end of the database and any other, um, user manuals that you have to, um, develop.

Oh um, yeah. So things like that.

So you can think about how. So it's also when you subgoals are quite useful because it allows you to, to kind of uh, um, divide, you know,

your project into, into sections and then it helps you plan and it helps you do the work, it helps you integrate and so on.

So, um, so most of you have sub goals as well.

Um, and also including the section how you know if the requirements and goals have been met.

So the value of this is that you are telling the judge okay here, what's my problem.

And to uh, just this problem. So this is the overall goal and the it has these requirements.

It will be the efficiency will be the how it looks or, um, user engagement or user experience, whatever.

Those are the requirements. And then, uh, to achieve this goal I have divided into set goals.

And if the project is successful, uh, these these these things will be the metrics of success.

Right. So now you have kind of wrapped everything up in a whole project into a very nice,

um, overview, very important overview, um, of the project and what to be done.

Right. Okay. No. Then you have the if you are doing the research project, you would have a must.

Uh, this is a must literature review. Um, because in research projects, research is based on what has happened in the past.

So your standard, your platform is past research.

So you cannot never, ever do a research project without referring to what has been done in that particular domain before.

So it's really it's extremely rare that you get you say, okay, there's nothing to be done on this topic, okay.

But it will be for the first time. Anything is done to never happens because we have to research is we are talking

about thousands or hundreds of years of research in all sorts of areas.

So when you do this research, therefore you all you have some literature.

Okay. So this literature can be um, the um, um, conference papers, the books, uh, journal articles,

equipment, you know, databases, you know, it could be to be any many, many things.

So if you are doing a research project, provide a review of literature most relevant to your projects.

So you had picked the, the most relevant, uh, papers, uh, to your project.

Right. So when you do literature, you so many papers come up and, and I'm sure you your whoever your mentor is, uh, they will also help you with that.

Um, but anyway, it's, it's very to the point that it's very, um, relevant to the your project.

The review must summarise the important thing.

Also look at when you when you look at the instructions and see what are the main points here that, that that's being um asked.

Right. So review of literature most relevant to a project review must summarise the current state of research on that topic.

With just one second, I had to. I hope to turn the.

Hello? Sorry. Um. You have to mute so that I don't get disturbed again.

All right. Okay, so, um, summarise the current state of research and you might say, okay,

current state of the reasons I doing this project, nobody has done it before.

There's no current state, but you kind of look it's not the way to go about it cuz he you look at in basic terms.

For example, if you guys, uh, system for um, um mapping say um, pasture farms,

nobody probably has done this particular topic before, but there may be other people who have done similar work,

either using just to map some other farms or, or some, um, uh, some other techniques or map of the farm,

so whatever, you know, um, so it's still there will be some sort of a current state about that topic.

And then you summarise the current state of the research on the topic in a way

that it shows the relevance of your chosen problem and why it needs to be solved.

Again, you know, you can say that current state of the research is this.

And accordingly, uh, this particular issue has not been addressed before.

So therefore and why it is significant. Uh, you have to also so when you do a research project, you have to say, okay,

it's not it's not enough to say that my objective is to do this and so on.

But why is it important? And I should also mention the heels of why it's a problem to be solved.

But you can emphasise here that with the, with, um, evidence that, um, this problem has not been addressed before and it is for this.

It's an explosive reasons. It is important to be so.

Okay. So you can see how the information is organised and it's very meaningfully presented.

Okay. Um, uh, okay.

Now then, now that, um, this is all kind of, uh, uh, done, now you can sort of go into the kind of detail aspects of the book, right?

First of all, is a method. No easiest way to look at the methods is to look at your goal and subgoals, right?

So in your first you have an overview of the method.

Describe how you structured your approach to the project,

including any project management approach used, any specific techniques, tools and only technology.

So this is more like this is this is more like your overall goal, right?

It is a summary statement. But here here the summary statement is about the methods technologies tools you used.

I like it like a a full glance full view of code project.

Right. In terms of um, the method. So this would be the, the everything related to the overall goal.

Um, and and then you are asking you to again you have done this before diagram and described.

So it's very very helpful for you as well as to judge if you drew a diagram like even if you do a research project you still can do a diagram, right.

So if you have three components like a, um, the front end, the back end,

the database and so on, you can still draw a diagram and show how things are connected.

Okay. So how are they come from a design and how do they interact with each other.

So once you draw that diagram you can talk about okay, this is my overall system and the components I design the frontend using x, y, z and a.

And then frontend interacts with the backend and so on.

Um, so if you use API all these things can be nicely integrated.

So you have what, what expectation is um, for you to give a complete, integrated, uh, view of your whole system, whole approach.

Um, so in that thing, if your project is a software project, this should.

So various software components, if it is a human focussed project or business or something, you know,

it should show the different aspects of the project that needed to be brought together and in which stage,

you know, um, sometimes you have to do certain things first and then bring the other one something that you had to do.

So the differently. Okay, maybe you know, a few things at a time together or, you know, different, you know, each is very problem specific.

So if it's a research project, it should provide a, um, the specific methods and processes of each aspect.

Right. Uh, so research will be your methodology.

Maybe you have data, um, a data collection or data cleaning or data pre-processing.

And then you may have modelling, have you done model and then you have results analysis of results.

And then you have some sort of a summary, you know. Summarisation of that, he says.

So anyway, it all will have some sort of a, um, the process.

Uh, also these each aspect, uh, copy a solution and they have to work together.

Right. So it's important that you look at the whole thing in, in holistic integrated with everything flowing to each other or, you know,

things flow to flow some, some place and then information and something happens and then information flow to another place and so on.

So here then the idea is that you have a picture and then also you describe the picture.

In terms of what's inside or how it works and so on.

So these two together. So if you look at the these different components would be the components.

These components could refer to some bolts maybe. You know sometimes it can be your components.

I exactly use of both and the overview exactly.

Refer to your overall go by. To achieve this I need a use this approach.

And these these these these tools and and the tools that you talk about.

The specific tools will be their separate entity component in the design section.

Right. So that's also um we have done this before.

And then, uh, risks and challenges. Now, you we have done this also in the proposal.

Um, now you are looking back so early, when you read the proposal, you were kind of guessing, you know, this could go wrong.

This could go wrong. This would be very challenging. This could be too time consuming.

I may not be able to do this due to whatever. Right? Uh, but now you, uh, you are looking back, right?

So you can say more definitively, what were the risks, risks and what were the challenges and how you overcame them.

Right. And how they impacted, um, your project.

Right. So, um, no, it's definitely it's more straightforward.

And then the implementation, this is something that a lot of, uh, students had some difficulty.

So what what what is the expectation if you look at from a judges.

So imagine you are a judge of this project. Okay.

Or someone else's project. You are a judge. So what do you want to see okay.

Overview of the project okay I understand okay I know the overall goal okay.

They have a good kind of a, um, you know, tools and, you know, a number of tools.

This makes sense. And then you look at the picture okay.

That makes sense. And each has each component has submitted logic and so on that also fine.

And then okay so that and the implementation will be slightly different.

Implementation would be how you kind of carry out these things because so far everything is more like a list of things.

Right. List of things. Uh, how would you go about doing it.

So you might say, uh, it's more like a kind of like a timeline, you know, the way how you went about doing it.

Right? You might you may have done, um, first, you may be of a, you know, a, um, data, data collection.

And then then, um, then you kind of worked on two different aspects, you know,

at the same time or one aspect, and then you worked on the other aspect and so on.

It's a more like a plan, like how did you implement it? More like it has a kind of timestamped, uh, associated with it.

So, you know, vitamins, you, you live to give life to these items you talked about?

Yes. A list of, you know, kind of arbitrary things. Um, you know, yeah, it's more connected.

Everything is everything you presented here is more connected in a logical way.

In the way, uh, in terms of, uh, how they were implemented again.

Um, so here you are giving how you did that.

How did you how did you go on doing, you know, how did you go, um, completing this project, that kind of question you are asking.

And then you said the end. Uh, what of the about the artefacts?

Okay, so, um. Again.

Um, a lot of times people don't know.

There's a bit of a level confusion when you discuss your defects.

Um, uh. Let's see. It could be you might say, okay, I, you might give a list of the, my report,

the documentation code, etc., but your main artefact is whatever the system.

So reflect of the overall goal and that will give you the main artefact.

It could be a web system. It could be new.

Um, the, um the data visualisation platform, or it could be a new business analysis um, framework or business analysis system, whatever.

Think about the main item, the bulky item, the most, your highest it.

You know, when you look at it, look at your project from um, from outside to what was the highest outcome.

Right. That that will be your, uh, main artefact.

Right. And then a you can have code, uh, report, etc.

The code, you are not looking at the code as the main knowledge, but the main artefact, the system that the code.

Works on all the food souls. All right. So think about that.

So when you talk about this way, it also gives the impression to the church that you work.

Um, you have a handle on the project. You are you are, you are not keeping your eye off of the of the gold or are you of the board, right?

That means you are looking at you. You are keeping your overall goal in mind and you are carrying.

Everything is discussed based on your main board. Even the parts are described in relation to the main goal, right?

So make sure that you are at that level and describing aspects related to the main goal.

Okay, so so you have a system. And with this system you may have quartz reports minerals.

Um, exactly. Yeah. Okay. Now you go to the results and outcomes.

Here. Now that you said this, then you look in the system and it has these these aspects.

Um, I James is 30 fixed. So you can then show what evidence you have for how did you meet your goal and requirements.

So you can say, yes, it was successful. And here is evidence.

Uh, so you had to provide evidence. First of all, you can say it's a verb system.

Um, it is a you wanted a highly efficient system and now it is you have highly efficient system.

And here is the the evidence. Maybe you show it or if it's more like, uh, um, more appealing, um, user interface.

And you can say, here it is before and now he here's the new one.

That kind of evidence. Right. So it's up to you and depends on the project design.

Include the beginning documentation, screenshots of diagrams, the code, the results of user feedback and so on.

Okay, so you decide, however, you have to think about what is again, there are levels of information that you can present when you see evidence.

You have to think about what is the main, most useful,

most crucial information that I can show as evidence that it that system is at the level it meets the requirements.

And at this, you know, high a little low level, right.

Um, so we knew for sure that.

You might then have. Okay. It's important. Also, I feel like, you know, it's good to show some secondary information, which is also important.

If you feel that then you can put that those parts in in an appendix.

Thank you. A lot of doctors talk about that as well.

Somebody inputting a dissection must provide comprehensive evidence that your system functions according to the requirements.

Additional items can be in that context. Can I just mention that?

Okay. Now one, to show that again you have to think about the how to provide the crucial information that you are not really missing anything.

At the same time, you had to have. You had to be succinct, right?

You don't have to go overboard with it. Providing pages and pages and pages of code or pages and pages of screenshots.

It just makes sense. So you have to just be very clear about about what you want to show.

And then also be clear and clarify what this means.

Okay. This this, uh, this figure, uh, figure one shows a the previous page of user interface and the current user interface.

Okay. And it shows the current one is much more appealing.

So it gives the reader not just two screenshots.

Just explain why you are putting it and what what what you want the reader to see in those figures or in those items.

So it's important that you see it. So um, and then once you finish all that, um, so initial, you can say, okay, list,

list items that you want to show evidence for and then show evidence for those items.

And then the important thing is testing and validation.

You have done this before as well in the proposal and these puzzles that you did in 69 as well.

So how you did the test? What sort of tests you did, what were the results you found?

And then again, show evidence for that. Okay.

Uh, and then you have reflections. So this is this is a new board, right?

We haven't had this in the proposal. So reflections will be you look back and and look at your, your everything that,

um, that had that happened during the time in terms of, um, achieving your goals.

So you might say okay, did you achieve like you said, okay.

Or did it go the way you expected? If not, why?

What new learning did you complete to achieve the goal?

Have you, um, how have you grown? Both personally, technically, through completing the project?

Okay. Here you would say, you know what? Were you new?

What did you learn here? Right. Um.

What are you learning? Remember, this project has a level nine of the qualification framework.

And to one requirement is that you learn new things and you apply them into a industry standard.

So industry standard project. All right. So so you reflect on you know what happened.

You know did it go you know everything explained or anything.

And did you achieve everything or did you have to change the goals or, you know, solely change the course and so on.

And then you conclude saying, what are the strengths and limitation of your projects?

So, um, like I said before, every project has strengths and weaknesses.

You will not achieve everything you wanted. Oh, you may see some other, you know, get so the the weaknesses of the system okay.

And then what. But how what are your suggestions for the future?

If you know what can be done in the future, maybe company you can it could be a recommendation to the company.

Uh, yeah. Or it could be your own thinking of how we can be, you know, uh, enhance to expand it.

Expand. It will change in the future. And again, you ask what you do differently if you did the project again.

So it's again reflective kind of statement. Um, sometimes you do things.

And then I did say, oh, I wish I had done it this way, or I could have done this better.

Or if you had done this way, it would be much more efficient.

And so. So all these things, um, can happen in a project.

So you can, you can talk about it and then you come to the references, you provide a list of reference references.

And uh, again, you know, this was in the proposal as well.

This can be company literature, the brochure document software documentation, publish books, you know,

make communication, uh, you know, professional websites, conferences, um, compass papers or articles.

Um, this is the style we recommend. So you can look at, um, you get the these reference, uh, you will see many different examples,

um, for any, any type of um, reference that you have used.

Okay. And the last item is the, um.

Appendages again. Um, it's, uh, it's still kind of in a part of the report, but it's it's, uh, secondary and, uh, um,

you know, an appendix is usually it's secondary is if it's primary, it will be in the main text.

Secondary, it's appendix. Uh, and it's not totally irrelevant.

You know, that's why it's they, they've been read, um, like many journal papers have,

have an appendix and sometimes they refer to it and it's optional that the reader

goes then and habit have look it's just enough to sometimes enough to say,

um, you know this um, some of the outcomes, um, what was x, y, z.

And you'd seen that in a figure it gave or something like that.

And then the reader can choose whether to go there or not at all.

They can just, you know, keep going, keep reading them.

So but it's good to there, because then the reader knows itself fills a particular gap in the text.

Uh, but but um, they whether they look at it or not, they in their minds, you feel a particular gap and they can go on reading the document.

Right. So that's, uh, uh, that's a useful way of looking at it.

So, um. We can look into these things in the next couple of weeks.

So what I'm going to, um. Okay.

About that bend is, is it's not enough that you do you throw items into, um, you know, a few pages outside, like after the references,

you can put some stuff in the appendix, but you have to refer to, um, in the text,

you have to refer, for example, you could be testing results with testing, right?

You might say, I did this. I use this x, y, z regression testing, integration, um, testing and and so on.

And then put some evidence for that.

And then you can say some other, um, some details or something, you know, some of the evidence is in the appendix B,

um, um, the figure b1, b2 um, so that way they know directly where in the appendix that your item is.

It's not enough to say it's in the appendix. You have to say it's in that bin and also say what that figure is about.

Right. You can say, uh, the detailed results of that section or um, the integration testing, um,

results are in the appendix in that in the particular graph or particular table and which shows that the testing was successful.

Okay. So you have to kind of integrate that, uh, into the document in a, in a, in a word or sentence.

Um, but more importantly, you have to refer um, to that appendix or items properly in the text so that the reader can quickly understand.

Okay. So that's the um, main, um, the template.

And uh, like I said, next time next week, uh, we'll probably take maybe 2 or 3 items at a time, okay.

And then we'll see how we can structure this.

Um, because a lot of, um, it's, although it looks simple and straightforward, um, quite a number of students struggle with proper communication.

Like sometimes you have, for example, the aim and the method and results in each and every section.

Right? Every section has everything in it. Sometimes, you know, so that's redundant information.

And also it's really, um, you know, it's not that interesting to the reader, uh, when you say you put everything in every section.

So, um, when you give only the required information is very interesting, then the reader would think, okay, how would they go?

Okay. How would the method okay, how about their results data.

So it's a kind of and we're adding some sort of curiosity and interest also uh, in the minds of the reader.

Okay. So that's that.

And uh, so yeah, so next week we'll take a few items and then week after week with a few other, you know, some more items.

Um, and I will check work week.

You like take an example research project for example uh independent project and example industry project and see how we can structure,

uh, these different items so that you can feel more comfortable, uh, or you so you don't feel that you are left alone in writing it.

Thank you. So, um, any comments on that before I look at the grading aspect of it?

Okay, so, uh, if not, then we can look at the, uh.

Grading, which you be interested to find out. Okay, so this is more like a we are reading, uh.

Um, reading it more like a, uh, thesis.

If you if you know what I mean.

Usually in your master's project, you have a, uh, at the end of the end of the end of the, uh, term, like you, in your case, it's a one year project.

At the end of the one year, there's a there is a capstone project.

There's two papers with it. So, um, you have some, you know, report this is considered as, uh, more like a mini thesis.

Uh, bigger thesis will be a two year research project.

We have two year master's. It'll be like a proper master's research project.

Uh, with this one is more like a dissertation.

Even dissertation in a normally in the university dissertation has a good chunk of literature review and references and so on.

So it's also not a equivalent to a dissertation, but we are treated more like a mini dissertation.

Okay. And um, marking for this kind of thesis is, um, a dissertation is given oral grade.

Okay. So examiners are expected to assign only a grade to the report that could be related to the overall global assessment of the report.

The midpoint of the grade range will be taken as the month for the proposal.

For the purposes of overall group calculation. That means, you know it is 90 and above, so a plus will be higher.

90 for it would be 85 to 89. The midpoint will be 87.5.

That kind of mark okay. To assist in determining series of formula or criteria have been developed.

Uh um okay. So these are the criteria. So criteria the suitability uh for use.

Opt or deployment and then the university ranking.

Right. So just to give you a couple of items. So all criteria are met and significantly exceeded outstanding excellence.

So that's the requirement to get an A-plus. All criteria met this criteria.

Uh the what you mentioned in the overall goals section.

This is my criteria. Uh, and they met and significantly exceeded outstanding.

And the project, uh, is of production quality and is suitable for use by external parties that we have completed.

And it can be used, uh, as,

as expected that if you said that this is whatever your achievement goal it is at that level and then, uh, all play to met.

Excellent. Uh, standard of work then project is a very high standard and could be used with little or no modification.

So it's it's pretty multi student also up there. And then the criteria are actually made by people content.

So I mean inadequacies uh means project is able to use but requires further work to be of a suitable quality.

So there's uh some quality judgement here.

And then the criteria have been made, but report contains errors or significant inadequacies in one more, one or more of the matters.

Disputable conclusions or reflections. But so, um, so that means it requires additional work to be of suitable quality and meet the requirements.

So it goes to be minus rate and so on. So you can read this other parts.

Um, so there's a bit of a graded response. Right. So in terms of criteria um the one.

The cry to one you. The students I expected demonstrate independent application and know highly specialised knowledge

and skills in research or annual advance policy within the discipline of professional practice.

So demonstrate independent application and specialised knowledge.

That's why we say you need to learn something new and you do it independently, right?

Uh, student has succeeded in this. When they can demonstrate to the examiners that they have designed and implemented a project with

clear aims and objectives that exchange their learning and scholarship from their current bases,

such that they demonstrate specialised knowledge, some of which is at the forefront of knowledge.

This is done through a thorough report. Um.

Um, uh, this is done through a thorough report with extensive presentations that demonstrate the solution is,

is is being or is able to be used in professional practice.

So that's the kind of, uh, you know, criteria and one for this, this, this go here.

Um. Again. You can. This is done.

Look at this part. Think this is done through a thorough report with excellence of presentation that demonstrate the solution.

Okay. Okay. The content of the report should be presented as as a coherent body of work, including clear motivation, aids and objectivity.

Sufficient explanation of methods.

An approach used if someone is undertaking a similar project, would follow the same method and then achieve the same outcome,

right, so someone can follow your work and report it, then it's a will.

The centre document diagrams tables should be used to investigate the work and should be well presented, accurate and concise.

Yeah. Cogent the tree. The report should demonstrate an objective measure of success,

both in terms of functional completeness and correctness and meeting the aims and objectives.

Yeah. So objective measures of such as it could be the accuracy of something or passing certain tests or meeting the aims and objectives.

The creative full will be the reporter demonstrate critical self reflection in terms of development of new skills and areas for continued development.

We have self reflection as part. There is a cultural pride that people should be clear, clear, accurate, cogent and concise.

Okay, um, so it should be free of typographical errors, errors of spelling and errors of language instruction.

And uh, it should be your own work.

We talk about that in the next lecture next week.

Okay. The work should be suitably documented and citations correct in every detail.

The method adopted should be uniform throughout. And that means responsive site should be throughout and aligned with the link.

And usually current practices outlined by library teaching and learning.

If so, if necessary, the report examines will not give equal weight to each of the criteria specified of a

greater significance will be given to the appropriateness and quality of the work done.

The method used and the students ability to demonstrate originality, critical insight and reflection, and capacity to carry out independent work.

So you can see fair bit of, um, high level stuff we are looking at.

So, um, it's not about going into detail about how you have gone about in level strategies.

Like I said, that's why the conceptual thinking, strategic thinking is, is so important for when you come to this kind of knowledge.

So the presentation aspect will be of secondary importance through although the poor aspect will result in lower paid.

Okay. Okay. Although it will do secondary to this aspect because obviously it's a work in the project.

It's a primary um, the quality uh, presentation is also important in that for specs, will we support presentation which is in the lower grade okay.

So. That's the report grading criteria.

Do you have any comments, um, on any of these two documents?

Okay. If not, I will just. Actually, we'll go through this and finish, and then we'll pick up, uh, same things, um, next time in some detail.

Right. So this today is more like a global view of what the project and presentation and record.

Study report and presentation will be like, no, um, in the presentation evaluation.

You have 30 minutes and ten minutes for the presentation and 20 minutes for Q&A.

So, um, Samantha will organise the presentations and she will let you know in advance, and then you can pick your start.

Um, but, uh, so this happened in the second week of the exams.

Um, like. Yeah, I think I have this here.

So, um, this is the calendar and it's in this week.

Yeah. This whole week we will have, um, your presentations.

And, um. Okay, so going back to the US.

So we are lucky there are a number of, um, items that we are looking at.

And first of all, when you have ten minutes to present, you have to think about what you want to how you want to go about it.

Okay. Um, so you had to go only very briefly view a background to the background in the sense background to the whole project.

Right. So you can see the, um, the overall company, you know, that background you had in the, in the, in the report goals?

Uh, if you have a review, you can talk a little bit about it. Methods, results, conclusion and reflection.

So it has to be extremely brief. Okay. And because you have to also present your your work your system and how it works within ten minutes.

So you cannot give more than three four minutes to all these, you know, interact to pass.

You know, the other parts other than the how the system works.

However, without these part, you nobody, you know, people cannot understand the, um, the what you are going to what you are presenting.

Um, but the good thing is that the the when the, when the judges come to the presentation, they will have read your report already.

They only need some sort of, uh, um, you know, short, you know, jog their memory, uh, because they have read it.

So you need the most, most important information for all these aspects, right?

Not not a whole lot of, um, detail. So it's more like a three, four minutes to this and then, um, five, six minutes demonstrating your your work.

The demonstration is the most crucial part. Show that your system works.

You can show, uh, if this if there are moving parts, you can show the results.

You can show it. If there's a code, you can show it. You decide what you want to show.

And also you will upload your material into GitHub or some folders.

We will let you know as well. So in terms of what they will be looking at is, are you giving an overall view of your project out of five?

Everything is out by the clarity of content.

Is it clear when you listen, when somebody listens through the whole presentation, then they are going to ask any questions until you finish.

So they might say, is it clear that this content is clear to me?

Uh, it is just the information flow, uh, coherently connected, or is it kind of said that here and there?

Okay. Uh, very difficult to understand or is very smooth and easy to understand.

The flow of information is quite logical. And then you look at how were the timing?

Did you go all the time? Sometimes, you know, you don't have time to it for the demo because you spend so much time on various aspects that play me.

Um, are you joking? Really? You know, you clear about the, um, the whole thing you project or you are until that, you know,

and then that also leads to how your confidence and attitude in presenting your work.

So judges can immediately see whether you are fidgety or uncertain or anxious.

Anxious is okay, but sometimes it happens in a presentation.

But if you have done the work, you know you will have a kind of a aura of confidence about the work you have done.

Then the quality of the slides, visual aids, how clear, how nice.

So you just done something very quickly, you know, something, you know, with without any thought about that.

I so understanding the project topic. So this comes from the Q&A part.

Do you understand the topic clearly. Understand the problem clearly.

Uh, how were the technical skill levels attained? I said quite acceptable or you know they will nine would be some new skills.

Um, and then soundness of the methodology and design.

Is it a well-thought through design or not?

And then the quality of the final product. So it is functional that the three achieves all the objectives and research requirements

and then the produced outcomes engendered and tested and validated as a proof of success.

And then finally answering questions, are you quite confident and clear and correct in answering the questions or anything you know,

from totally uncertain or somewhere in between?

Okay, so it's out of find this, uh, whole presentation.

Uh, so you judge will, uh, mock the presentation.

We get the average of the two. So that's basically, um, what we want to I wanted to call it today.

Um, okay. We are I 32 people are here.

Um, so do you have any any.

Um. Overall. Uh, question about it.

Yeah, yeah, yeah. Can I ask can I ask one question? Um, yeah.

Yeah.

During this, uh, presentation, uh, like we did in the studio project, we will not be having a demo, just a presentation or with the slides that's on.

Yeah. It just, uh, you know, you have a demo. That's a main part.

So, like I said, here in this ten minute presentation.

Right. Ten minutes. So you, you will have to take about maybe I'm just guessing, but it's up to you.

You can choose, um, maybe three, four minutes in here on that and then leave the rest of the time for your team.

So demo is the crucial part. You can go through these three minutes maybe, and then seven minutes for the demo,

but remember to leave a good amount of time out of these ten minutes, you know, uh, Jemmy Blow to the demo.

It is a crucial. So this is also needed to get, you know, the, you know, provide the context.

And also when you talk about these things in the in this part that I'm highlighting, it kind of builds,

you know, kind of a builds everything brings everything together in the presentation.

Right? Without it, it just uh, it's, you know, it's missing, right.

You see that button music. So if you connect those items into one sort of a overall perspective, you know, about the project.

So do it very quickly. Uh, I would say 3 to 7 minutes.

So for, you know, 4 to 6 depending on how you, what you have to show.

But remember you must have some time for the demo.

And also we stick to the time very, very strictly because everything is timed and uh, you know, there's no time.

Yes. There's no yeah. There's no listening time.

Uh, okay. Thank you. Okay. Any other comments?

So, um, Professor Blue, because, uh, Q8, I have some questions.

Yes. Okay. What do you want to ask?

Um, can I. Can I go ahead? Emma? Yeah. Isn't it? Yeah, yeah.

Okay. Go ahead. Shall I start? Uh, okay.

Who who who wants to go first? Emma. I think I heard, uh, uh, female voice first.

Um. Okay. Who who is that? Divya.

Emma. Emma. Okay. I don't know.

Okay, this is my my question. My question is pretty simple.

So it's like if we have the same the sentence of the older structure or the, uh,

the information we might have, like the highest rate in our the final report.

So how much the percentage or should baseline. Uh, I didn't get that.

Uh, can you repeat that question? Uh, the question is like, uh, we have the same a structure, the sentence from the, uh, final report.

So we have checking for the same word or the similar words from the other.

Um. Uh, checking. Oh.

Oh. It's okay. You can use anything you like. If you provide any wording that you use in Checkins, you can use it to sort of open.

Oh, okay. So it doesn't matter how many percentage away I say inner voice.

Uh, purist. No, it just means a your work.

Right? Still checking is still your work, right? Yeah.

Chicken. You are talking about the independent project chickens, right? Yeah.

Yeah, yeah. So they are still your work. If you if you have you work in the chickens.

It's okay. But if you borrowed some from, you know, words from here and there without really being attention because we are not looking at,

you know, the editing or anything in the at that level chicken level.

Um, so you need to know that whatever you write in your report is your own writing because the, the, uh.

So sorry for that. Are it just, uh, because we have the example, we have all the same example.

That's the main reason. What do you mean by the same example, the example of the final report where we'll have the same words on the,

uh, final example, like the name, uh, class.

Something like that. Oh, this um, some certain things will be similar.

I mean, that we use the template. Um, so, uh, but your project is unique.

You are the only one doing your project, so all these things will be quite different, right?

So, um. Yeah. So if you have some, you know, borrow, borrow some, you know, what are you using the checking.

That's fine. But make sure that it is not, um, what you call plagiarised because we will use Turnitin and I school.

Um, no, I school is part of the journey to report.

So we will be looking at, um, high school and again like in the proposal I school and then 30% will not be marked um,

because we don't know you know, we the, we would, you know, log the machine, the log, the human right.

So, um, we'll talk some more about it. But important thing is that you your writing is your own, but the projects are different.

So we we won't see identical reports. So very similar.

But if you if you find very similar reports, we might be thinking, you know, what's going on in here and so on.

So usually, you know, the projects are quite different.

Okay? Okay. Thank you. You're welcome. Yeah. Uh, who is the gin?

Um. With a change. Who has had a question before?

Okay. Um, after, uh. Devi. Uh uh. Yeah.

Do you. Okay. Yeah. Okay. Divya, you have a question? Yeah.

I had a question, uh, regarding, um, like, if I had a machine learning project, like, if I'm using Jupyter notebook, like, to complete my project.

Um, I don't know if I have to upload my entire project in GitHub, uh, for showing as evidence.

Or do I just have to, uh, put the snippets like you suggested in the, um, report in the final report?

So I think you have to you have to upload your work, um, the most popular GitHub and, uh, view the, you know, get back to you soon on that.

Um, and snippets also, uh, should be there because just, just it's not just enough to say it's in the code there,

but, you know, show some sort of a crucial information from your coding or from your work.

So that report also has a kind of a look of completeness.

And it's all easier for the, for the reader.

Um, the, the, the program, uh, that you upload or the files you upload will be to get more detailed information.

You know what I mean? Yeah yeah yeah yeah.

So it's good. It a test. It has to be both.

So the the report must be complete in the sense of having enough information to see what you have done, the results you have achieved and so on.

And, and detail will be in the report, in the appendices or the or the, um, in the, the files or the, uh, your what you upload on GitHub and so on.

All right. Yeah. So you will come.

So, um, I okay, let me, uh, go.

Uh, so one from the chat and then come back to Jin.

Okay. Uh, it says the, uh, could you kindly confirm the expected word limit for the final report?

Um, we are looking at, like, 15 to, um, sorry, 15, 20 pages of write the 1.1 and half.

Um, you know, because, um, lots of space.

You know, the lines, a space. Um, I haven't thought about the word limit.

Um, for, for for now, think of 15 to 20 pages of, um, with line spacing.

One and a half. Okay. Um, that kind of, uh.

Yeah. Is that?

Would that be enough for now? Marshall. Thank you bro.

I'll that's you know. Yeah. Okay. All right. So Imma, uh, you know, I think that, uh, you ask the same question as before.

If you had the same sentence. Yeah. Mean very similar to that one.

And no we are not. Um I don't know if you feel a chicken is actually part of a, it would be part of.

Um, turnitin because you are checking, uh, reports were.

Only the proposal is in the system. So, um, I don't think your chickens were there, right?

So if there are similarities to the proposal, uh, it might say.

But again, you know, um, we we know whether it's a proposal or, uh, the, uh, the other things.

Right. Chen. What's your question? Thank you.

So I got a three questions at the moment.

The first one is that, uh, for the project plan, uh, you know, we have some similar, um, information should be also covered in final report.

Is that okay? We just a copy paste all we have to paraphrase this information.

You mean the what do you have in the proposal?

Uh, for example, in the proposal, we probably have the executive summary or like the first proposal, the cabinet secretary's office.

Oh, well, for example, we have the like the testing model, something similar.

Yeah, yeah. Uh, you might, um, obviously, you know, you things might have changed a little bit.

And you will, you will. I think it's good to kind of, uh, um, instead of just blindly copying it, you know, it, you know, from one to the other.

Let's see whether it still reflects the, um, the current situation, um, which is that you have completed the work.

Right? You might want to adjust, you know, some of the wordings,

because it's so different when you first wrote it because you didn't have, you know, you was so, so, uh, in so, um,

almost introductory and kind of basic and it's also futuristic right at the end, you really have some more reflections and,

and perhaps you would, um, you would want to, um, you know, uh, rewrite or, or paraphrase or whatever, you know, might happen.

But, you know, certain things have to be exactly the same, you know, that.

That's also understandable. Okay. Thank you.

So the second question, the second question is that I am currently working on the industry, uh,

product, but uh, project about actually it's not kind of like, uh, building a web website.

So it's it's just like a business analyst.

The report analyst. So there's no demo in my final presentation.

Is that okay? The more we use the term demo in, in, uh, in a very broad way.

You know, if you know, you still have some results, right?

Some outcome, it could be Excel sheet, you know, you could we just want to expose it showing all these different business aspects,

maybe a pie charts or some other charts or whatever.

So there must be important thing you that you demonstrate. Imagine somebody sitting and they have never seen your work, never seen they have seen you.

But maybe, maybe they haven't seen you. That if we have 16, 16 staff members, you know, um, you know, in the judging.

So I'm, I'm sure some of them haven't seen you.

So is a new person doing new project and they're they may not be 100% familiar with that with the project or your topic.

And then you have to show here's, here's what I want to do.

And here's, you know, the results. So you need to decide what results I want to show as evidence of my achievement.

Right. And there must be something, whether it's a business analysis web page or, um, data visualisation platform or GIS project to map, you know, um,

pumps or whatever,

all these things need to be clearly shown that there is no doubt in the mind of the judge that you have achieved it and you have achieved it.

It. So you choose then what to show. But there must be something to show.

Okay. Okay. Thank you. So so so my last question will be you say you you mentioned that the final report will be 15 to 20 pages.

Uh, does this number include appendix? Without the appendix O.

Without appendix. Okay. Okay. There's no page limit for that thing.

Okay. Thank you. That's why the appendix would be just glanced.

They won't be read. Know? It's not something they read, but, you know, word by word.

It will be just glanced. You know, if you briefly go over the appendix.

That's the difference in the text and the appendix, usually. Okay. Okay, cool.

Thank you. All right. So in the in the from the church, there's a question.

Uh, we ran for an individual project. The timeline extends beyond 14 weeks due to the project's ongoing nature.

Even after the project release, it takes additional time, uh, to determine whether the problem has been addressed.

Could you provide some guidance on how to write a program? Intersection.

Uh, I think in the for that, uh, idea was that you choose a project that can be completed in the time frame.

And, um, so I would suggest that you kind of, uh, uh, contain the, the problem so that you can, um, show that, you know,

you can perhaps re, you know, re revise the goal, for example, to show that, uh, to show the achievements within the 14 weeks.

And if there's anything else that need to be done, you could put them as your future, future recommendation to complete this other aspect.

But at least some aspects must be completed that, you know, if the project that you want to complete that project.

But there may be other things that can be done later on. So make sure that you contain it to like within the 14 weeks.

You know, you can curtail the if it's a big one, you can sort of curtail it to the what you want, but make it a more like a rounded project, right?

So the standalone project, uh, you can say, okay, I have this, but without the other part that need to be done in future,

I cannot show anything because this need that, but which is not acceptable.

So you have to show some sort of evidence of some sort of item or system or process that's kind of standalone.

And it has, you know, stand, um, uh, on its own.

Okay. So the other question is due to it doesn't make sense.

Okay. Oh, yes. Yes. Okay.

Uh, due to the need of the solution, I for several technical challenges, after conducting a self-study and research, I was able to resolve.

These issues should be included in the problem. No, no, not in the problem address.

Problem address is is not your challenges. Problem is actually the topic.

Right? Problem address could be that, um, so the business process, uh, this um,

suppose there is a company and they need a more advanced business analytics system.

That's the problem. Or they need the more improved website or use it because, you know, more appealing website or um,

they need to, uh, system to, um, visualise the data and make meaning of data.

These are much more high level items, right. Problem is the highest level statement of your project.

And uh, this problem could be in the reflections.

Any issues you have, you know, you could put it in the reflections and you could say that.

Yeah, you know, I have these these problems. Therefore I had to change the, you know, original topic that you repeat or the objectives are you.

But those things can go in the, in the um, um, the reflection that reminds me renew in your goals, um, you know, new learning.

You know, they are not the goals. Goals refer to the technical topic, technical project that you're working on.

You know, um, the like, uh, how to learn, how to learn certain the certain, uh, skill.

And they are not your objective, although they are required. I mean, you and they would these, uh, they would need it.

The objectives, overall goal, all these things. Problem refers to the actual particular work.

Um, uh, the project was about.

So it's a technical aspect of the project. Okay.

Yeah. And then there are dependencies, including the total paid.

Okay. Yeah. And so that it's not so appendix can be um, but still don't write 200 pages okay.

So that can be make it short as well. Right.

So then uh, you have a question or two.

Oh. Hello, professor. Yes I have one question.

Mhm. So for the final report, uh, does it also has that uh eternity percentage limited.

Because when we do the. Yeah. Yeah 5%. 5%.

Yeah. 5%. 5%. Yeah.

So but um, uh, for the, uh, students who are doing the research, you most of, uh, uh, that, uh, community is coming from the reference.

Um, so how can we, uh. How do we like, uh.

Uh, re resolve this. Yeah. Yeah.

Yeah, yeah. But but, uh, when we see that, when we see references, because we can see the report.

Um, so, uh, it gives a percentage, right?

Uh, yeah. See, you see what? That's. Okay.

So, um, so it's exactly like the, the, like the, um, the proposal because sometimes you cannot, you cannot avoid the, uh, because.

Yeah. Like references one and some technical terms could be another one there.

So we say 5% and it could be like 5 to 10 would be more like, uh, you know, depending on, you know, how common the some of the terms are.

So, um, but if we do the research one, there will be a little bit higher, but we can we can resolve that.

No issue there. Okay. Uh oh, I get it.

Thank you. But but make sure that apart from the reference as it's about 5%.

Right? Yeah. Yeah, yeah. Okay. Okay.

So, uh, we have, uh. Okay.

Jeanne's asking, do you still have online class today?

Yeah, we are already having it. So we are meeting next week.

Would that be useful to meet up again next week and go over these different items?

Would that be useful? Can you make some noise for that?

That would be great. Prof. Thank you. Okay. All right. Yes. Okay. Okay.

All right. It's because it's a bit sad sometimes.

You do really good projects and it's not communicated. And then you get kind of it.

Unexpected results and you see what's going on.

I have done so much work and so and so, um.

I think, uh. I like you to do the best you can in the report as well.

Uh, sometimes you have the idea that, okay, what's the big deal?

You know, we have we have programmers, severe modellers, you know, who was writing it.

So it's not the case.

In fact, um, a lot of, uh, students will finish his PhD, and he's himself a software person, and he's currently developing a software platform.

And his wife, who is the, um, the designer.

And we had dinner the other day, um, with them, and she was saying, um, how important the reports,

uh, because she didn't pay much attention, but she realised how important it is,

the because when they see the reports as a graphic design, it's so important that, uh, when she communicates with other people,

the reports are real written and reports she get from other team where she would get information.

For her part, it's so important how the other people communicate those ideas to her, uh,

as well as how she communicates ideas to the other people in the team so that the whole thing works properly.

So there is no, no, um, going around.

You have to you have to really do it and do it in the best possible way.

And also, if you have a good report, you can show you got an interview, you can show it and say, here it my project.

And when they see the nice document with nice executive summary,

nice program described in a very interesting, you know methodology and it will go very clearly stated.

So both clearly stated and the methods very clearly explained and specified with this diagram and so on.

And the results, everything you know, sometimes, you know, the judge will immediately know even when you before you when you say in the next section,

they will have a really good idea of what you are going to say next.

If everything is kind of lining up properly and everything is clear, and that's where the judge or the marker gets very satisfied,

you know that also has a kind of positive influence on you own your own reports and also maybe something a good bias,

uh, outlook, uh, on your project as well.

If everything flows with people, be happier reading about it, reading the report.

So, uh, there's a lot of positives about writing, clearly,

and it's more important that you become a clear communicator because you have to write succinctly.

It clearly, coherently, coherently meaning you track the one thing flows to the other, then it flows to another.

And it's a very clear expression of, of of what you have done.

And it's not easy. It's a skill that needs to be developed, but the value, especially if you become a leader,

if you go into leadership positions, it's even it's so crucial,

is paramount that you know how to communicate, you know, in written and in in oral form as well,

that you clearly communicate your ideas and you know what to what level without level confusion.

You know what's important, what's high level, what's detail level, all these things.

Uh, that's where if you have not going through those videos, um, conceptual thinking, strategic thinking,

I encourage you to have a look at because this whole project is about it, like a strategist thinking, talking about their work.

So it has to come as a strategy, a conceptual thinker talking about their work.

And also when you go to the outside, you're doing become a leader or part of the team.

It's again, you know, all these issues, all these concepts, um, quite important in your workplace.

So you have you've got a leader to to guide the team.

You need to have a huge, a very, very broad overview of your topic, uh, when to go to the, to the, to the detail and so on.

So all these things, uh, reflected in the report.

Okay. So. What? You know, the, uh.

Johann, you have a question? Uh, yeah.

Hi. Uh, I just have a technical question that I cannot access the chatting the interface here, so.

Uh, okay. I'm not sure what happened.

I don't know, uh. Uh, you mean on this team today, right?

Yeah, yeah. I have no idea. But I see a lot of thought of, uh, questions on the chat.

So, uh. I am the, um.

Okay, but do you have a question? Um.

Not now. Just for this year. Okay. All right. I don't know why.

Uh. It's unusual. Uh. Okay.

And there's also a Q&A section. Uh, I don't know whether you can access that or not.

Lot of people writing in the Q&A section. There's a Q&A section, and that's where I see all the questions.

And in the chat I don't yeah, there's nothing there on the chat.

Um. And you other. Comments or questions.

Okay. Seems like we are done. What the J.

So today was an overview of the template. The grading of the report and rating of the presentation.

And next week at the same time we will go over the executive summary and the background and the goals.

Those three and the week after will go through the methods.

And he says, right. Yeah.

And then? If you don't finish it, then we go to the next week after.

We'll talk about the last bus and appendixes and things like that, or any other questions you may have.

Okay, so I also encourage you to, if you haven't done looked at those, um, um, um, okay.

Let me um, maybe I'll share. Stop sharing. And um.

Uh, we, uh. If you go to the resources.

They study resources. Uh, and you can see, uh, some of the, uh, uh.

I think I also suggested this last time giving an oral presentation how to communicate effectively.

Uh, these are all learned skills. You know, it's not that if you know you have it, you know, immediately you need to kind of,

uh, first learn about it and look how other people do it and get some tips and so on.

So here's a tips. Well excellent presentation. You know, you can you know this is a Ted talk and how to, um, make that how to make, uh,

technical presentation that speak to magic ingredients of amazing, um, presentations and also three, three minutes.

Um example. These are very I think these are really good examples of how people in three minutes talk about highly,

you know, high level of content and in a very clear manner.

So you can be right that you can be that in a move the, you know, more you kind of put effort into it, the better your, your, your quality would be.

And then, um, last time I said this, uh, introduction of taking a writing, it's also, um, the good, um, the introduction.

And then we had the, um, uh, five years ago, I conducted a workshop with Atila Cameron in at Lincoln Teaching and Library.

And this is her slides. Um, it's it's, um, we go through maybe next time on this as well.

And also we have a, um, I told you, where is the, um.

Uh, yeah. He he has a report writing workshop that I conducted with, you know, with the students about, you know, aspects of technical writing.

So then I also mentioned this last time, uh, you can look into that and then, um, yeah,

I think clearly and concisely this is about how to kind of, uh, um, and I clearly, concisely this is a monash University tutorial.

Uh, you can all these things uh, quite have will be quite useful.

And also you can book the workshops in appointment and I, I will from now on.

I think I already, um, posted some workshops and some of you attended them and I'll keep,

um, like, you know, the, the there will be two people from Lincoln teaching and learning.

Uh, I have, um, you know, um, uh, uh, um, to support you.

So they will be available, uh, for personal, individual appointments,

or they can you can send me writing to them and get some advice as to where their issues can be, and they can also support you.

So there are two people I will, um, one is Katrina Cameron, and then the other person is Tui.

And I'll put those names also very soon. Okay. So they are they are dedicated, you know, to, to support you and this class and the way that I put the,

um, the workshops here is where you, you make those bookings.

So, um, so these are, you know, very useful things for the final and everything.

The important thing will be when you learn from different places and different things and over time,

like you had book 14 weeks and you were doing different things every week, certain learning activities.

And if you did them over time, then you will have a kind of expanded skill base in terms of written and,

you know, uh, oral communication and all these ways.

Sure. Then you stop, you know,

submit the report or when the judges read the report and when you send in front of your judges and you you make a presentation,

all these kids will converge. And you would be surprised, you know, how will those, uh, those things have come to support you?

Okay. So, um, I think with that, we have covered everything, uh, in this, um, uh, you know, list of resources over time.

Right? So I hope you have done it. And definitely these are very, um, helpful resources.

So that's for today. And next week we will then, um, take, take the template at that.

And. See what questions.

I think this will probably help you get yourself organised.

Like. Yeah. Hopefully they they'll be superb projects.

Synodic post this time. Uh, no. Just will go like this thinking oh, I did this project about.

I had no idea from that. So we don't want that to happen. Okay.

So, uh. Right. I think we are done.

Are there any last minute questions? Okay.

If not. Download the new template.

It's not new. Minor tweaks were there. Download that file from the gun page and start thinking about it.

Put some idea you don't have to write one time. Sit down and write you know, paragraphs as into the new thing.

You just jot down some ideas under different sections you want and it's a very nice also technique.

Very helpful. You just start writing the whole thing.

You just put some ideas under different sections and you can revise or shift some the ideas.

And you know, it's easier in here just with the phrases.

Sometimes it's easier to reorganise all those things.

Then once the idea is through correctly or clearly with those little phrases, then you can expand your your use.

Right? So there are different ways of uh, getting, you know, uh, doing, attacking it.

So anyway, I think I would say good bye for now and see you next time and I'll add to your blog, okay.

Next Monday. Thank you. Prof. Thank you, thank you, thank you, thank you, thank you.

Okay. Bye bye bye.

Thank you. But.