i have this structure "



Product Accountability Report Draft Final Version
This is your draft final report, building upon the initial version. This report is so far along that your instructor has the most complete impression possible of your assignment, your solution, and the process through which you arrived at that solution.

Write for the Reader
Keep in mind that the person reading your report may not be as deeply involved in the project as you are. Always put yourself in the reader's shoes and consider: what does the reader need now to understand what I want to explain? So, don't dive too deep too quickly; first, provide the context. Once that is clear, you can provide more details.

Technical & ICT Writing Center
Throughout the year, you can turn to the Technical & ICT Writing Center for individual consultations on writing your report or thesis. In these sessions with a writing instructor, you can address the issues you want to work on yourself.



The Technical & ICT Writing Center is available to students from all programs at ATIx for (almost) all writing assignments. You can turn to us at any stage of the writing process with questions about:

A more efficient writing process
A clear question and structure
Improving your writing style
"Simple" questions



Product Accountability Report
The product accountability report is the document in which you describe your internship. You do this based on the project you have conducted and the product you have created. You justify your choices and explain how you arrived at your solution.

During the execution of your project, you follow the SDLC (Software Development Life Cycle). This development line in your solution's development is also reflected in your report. You take the reader through the problem you have solved and explain the choices you made along the way. You can assume that the reader also has knowledge of IT, so you don't need to explain everything.

Guideline for Length
The guideline is that your report should contain approximately 50 pages of substantive text and images. This does not include the title page, table of contents, summary, and any attachments. So, you will need to limit what you describe.

When you find that you want to delve deeply into a topic while writing, consider describing that material in an appendix. You can then insert a summary of it into your main report.



















Goal


In your report you show two important things.

Acting methodically
First of all, you show that you have acted methodically. This means that you have worked systematically according to methods that you have learned during your training or picked up during the internship. This is, for example, dividing the internship according to the Software Development Life Cycle opens in new window, holding an interview, working with Scrum, or working under an agreed architecture. Appendix 3: Methods and Research Skills contains an incomplete list for inspiration. It is therefore important to show which methods you have used, what you have used them for and why you have chosen them. You may also have worked systematically without using a previously known method.

Accountability for choices
In addition, you show in your report that the choices you made during your internship were also made in the right way. You do this by naming these choices and then substantiating them. During your internship, there are many moments when you lack knowledge or have to make choices. This can include choices about which methods or techniques you will use during the development of your product, on which platform your application should work or with whom you will request the requirements.

Knowledge questions
We call these questions about missing knowledge and moments of choice knowledge questions. By making the knowledge questions explicit, considering alternatives and providing a substantiated answer to them, you demonstrate investigative ability. Moreover, you demonstrate the quality of your choices and thus indirectly also the quality of your end product.

Structuur



Whether you are aware of it or not, every piece of software is developed through the Software Development Life Cycle (SDLC). It is advisable to organize your report according to the various activities involved, see Figure 3. Iterative work is the norm in our sector. You will also find these steps in an iterative approach. For example, while realizing user stories, you will see that you always approach them according to the SDLC.



Acting methodically and systematically
In your document you look back on the internship and you can easily devote a chapter to each step. In every step you show that you have acted methodically. You also approach the entire project systematically. This means that the steps you take follow each other logically and are closely related. Please also include this in the report.



Knowledge questions
Knowledge questions arise during each step. For example, it may be that you do not know something about the domain in which you work, or that you have to make a choice within your architecture. You also answer these knowledge questions methodically, showing your investigative ability. This can also be seen in Figure 3, as trips to an investigation. Make concrete which knowledge questions you are going to answer, how you will do that, what the results are and what conclusion you draw from them. You can do this by weighing up different alternatives, for example by means of a multi criteria analysis. You can also substantiate your choices with authoritative sources.

You may notice that we are not talking specifically about a research phase. This is conscious. Almost all knowledge questions are related to a part of the SDLC and can be described in the activity where they occur. We therefore advise you not to think in terms of main and sub-questions beforehand, but to answer knowledge questions as soon as they arise in a phase.

Sometimes a stakeholder makes a requirement that means that you no longer have a choice, for example that you have to work with a NoSQL database. You may not completely agree with this choice, because the data is very relational, or because the literature indicates that a Graph database is more suitable. You also describe such a consideration in your report. You also provide substantiation for the final choice that has been made. If your choice conflicts with what the company had in mind, you may be able to convince the company with a good substantiation. If not, come back to this in the evaluation.

We will go into a few steps in more detail. You can read about this in this module.


Introduction

The introduction is an important part of your product accountability report. It is, of course, one of the first parts of your report that the reader reads. In the introduction you should therefore introduce your assignment in a concise and clear manner.Although of course you don't have any solutions yet and no answers to your questions, you already know something about the company that gave the order, and about the problem they experience.It also helps you if you write the introduction early on. It can also give yourself insight into the project and help you analyze the problem.






Problemanalyse


In your problem analysis you go deeper into the 'problem' of the client. In some cases, your client does not really have a problem, but your assignment does have a clear reason. This can be, for example, the desire to bring a new type of product to the market, or to improve existing products due to new developments. We also call the reason behind your assignment a problem. The problem is the reason your command exists.
The problem analysis must be read as a smoothly running story. So don't make all separate sections of this part. In your problem analysis you will address the following aspects:

1. The problem context
It is important for the reader to understand the context of the problem. For that reason, you explain who your client is, what the objectives of the company are, what products they make, what the current business process is and, if relevant, how the organization works. Limit yourself to the parts that are relevant for your reader to know. So here you only include the information with which you can make a direct link to the problem.

2.   The cause of the problem
The problem arose for a reason, for example a situation that is not running smoothly now, an obstacle they encounter, the desire to innovate something or an idea they want to bring to the market.

3. The problem
You succinctly state what the problem is. This can take various forms, such as, for example, a question or a goal.

4. Stakeholders
It is important to identify who is involved in the problem. Think of all the people who experience the problem, who benefit from solving the problem and the people who do not benefit from it. Clarify the interests of each stakeholder in relation to the problem, and explain what their role will be within your project.

Your teacher supervisor is also a stakeholder in the problem, because you also take the requirements of the program into account. You identify the stakeholders to determine how you will communicate with them. This is also a form of transmission.

Tip: it is important to get your stakeholders involved and enthusiastic; occasionally contact a stakeholder on your own initiative, for example your tutor supervisor, and proudly show him what you have already achieved.

5. Problem analysis
You explain the problem behind the problem. Why is the company running into this problem? What are the different causes? Analyze as well as possible who has the problem, where the problem occurs, how the problem arose and why it is important that this problem be solved.

6. Solution Directions
A problem often has several causes, but also several solutions. You show which solution directions are possible and you make a substantiated choice for one of the solution directions. You are probably not complete with that; Even after the problem analysis, there is still enough to figure out to arrive at the ultimate solution.

7. Project objective
In the previous steps, you researched the client's problem and thought about possible solutions. You will probably try to solve part of your client's problem using one of the solution alternatives.

You determine the objective of your project and limit exactly what you are going to do (and therefore also what you are not going to do) with a scope. Be very clear about what exactly you are going to make and under what conditions you know that you have met the goal, the so-called acceptance criteria.

Approach


In the chapter on the approach you describe in general terms how you will achieve the objective of your project. It's about the global approach to your project, you don't explain every specific technique here. For example, you explain whether and how you phase the project, how you involve stakeholders, how you obtain your requirements, but also how you ensure that the solution is of high quality. This chapter explains how to do this methodically.It is not enough to just get started. Think carefully about the risks that can occur in your project. Think about how to prevent them and incorporate this into your planning.You work out your approach in a planning with activities. Take into account the available hours, activities that you carry out for school and any holidays.Tip: a detailed planning is almost never useful, especially if you work with an Agile method, but it is time-consuming; a planning that only mentions milestones is more realistic. The purpose of the planning is to show that your approach is realistic, that the sequence of activities is clear and that it fits in with the time set for your internship.






Evaluation
When you feel you are done with your project, you can start evaluating. Evaluation is different from reflection. A reflection is about you, your skills, your behavior and your personal development. An evaluation, on the other hand, is about the process that went through, the methods used, the choices made and your end product. An evaluation is therefore always written professionally.Your evaluation can cover the entire internship period. In an evaluation you check whether the process followed, the methods used or the choices made have proved successful. Also take a critical look at the end result and its quality. If you could do the project again, you might do certain parts differently, or maybe you would do everything the same way.This is the place to describe that. Do not only draw conclusions, but also substantiate why something was successful or not. In this chapter, therefore, come back to the parts that you described earlier in your report.



Reflection
In addition to solving a problem, you want to work on your personal development and competencies during your internship. In this chapter you will take a critical look at yourself, your actions and your skills. In a reflection it is important that you describe what you think went well and what went less well, but above all that you are able to explain well why it went that way. You look critically at yourself, your role in the situation and what you could have done differently.At the start of your internship, you set different learning objectives for yourself on the basis of a PDP. In the reflection you discuss the learning objectives that you have set for yourself. Check whether you have achieved them or not, why, and what it shows. It can help to reflect according to well-known methods such as STARR or the Korthagen cycle. Try to keep the text easy to read.Using STARR does not imply that there should be a separate bullet for each letter. Your POP and reflection are always written in the I-form.


"