I need 1700 words in web app relating to car garage structure

roposal document on a web app relating to a car garage a structure that has the following sections:

Section 1: Introduction 400 words

Section 2 Research methodology and plan 200 words

Section 3: Describe the resources and skills required 200 words

Section 4: Project plan including a Gantt chart. 300words

Section 5: Risks that you may encounter during the implementation of the project 200 words

Section 6: Legal, Social, Ethical and Professional (LSEP) issues that you may encounter during the implementation of the project. 400 words

A presentation on topic will be given and report structure( attached )  

these are supporting documents 

project proposal on a web application on car garge .docx

Webapp.pptx

question.docx

................................................................................................................................................................................................

Attachment 1:

1.0 Introduction (about 400 words) 

Your introduction should include (in paragraphs, but not necessarily in bullet points. The bullet points are given here for you, to make them easy to read):

Aim of your proposed project, and what it intends to achieve. Propose a project that deals with one or more computer science domain problems devising realistic solutions. A suggested starting line would be “This project aims to design and develop a ……”

1.1 The Problem Statement  

A more detailed description of the problem that the project will solve (called Problem Statement). Describe the problem from the business, or organizational, or the intended audience point of view. This is also an opportunity to give a project background, about the industry specifics, or the issues faced by the target audience, and how this project aims to solve these issues.

1.2 Functional Requirements

A descriptive list of functional requirements of your intended artefact. Comment on which functionalities should be considered “advanced” from the project implementation point of view. Many of you would ask, “where do I get the functional requirements”. The functional and non-functional requirements are normally obtained from the client who is sponsoring the project. However, you may not have a sponsor. In that case, your “sponsor” is your audience, the users. You need to undertake research for the project background above. This research will help you to understand what the audience want and need. You need to put yourself in their shoes and try to understand what functionalities would be useful to have. So, if you don’t have a client, then you have a problem, and you can visualize a client, or audience that will use your artefact.

The project requirements must be divided into Functional Requirements (Core and Advanced) and Non-functional Requirements.

1.3 Project Objectives

A list of Project Objectives that will help you to plan and manage the project. These objectives must fulfil the SMART criteria (no need to mention the word SMART in your proposal. That is for us to judge if they are SMART or not). By now, you understand what the project objectives are. You have a list of functional requirements that you need to research, design, implement (your artefact), and test. So, how are you going to organize the work now? You have a final goal, now devise some objectives, with a deadline for each objective, that will help you to deliver the project on time. Please, look at the materials provided under Units for more guidance with Project Objectives.

(Up to 400 words) 20% 

(From the word Aim, in the first paragraph, I have written here about 330 words. So you have room for about 70-90 more words here, to complete this section (Introduction)

Please pay attention to the numbering system I have used, and follow that in every other assignment. However, remember that the word count is not set in stone, and it is provided as guidance, as help for you to know how much you roughly have to write.)

2.0 Research Methodology (about 200 words) 

Research methodology and plan. In this section, you should identify areas of research that you need to undertake, which will help you with the design and implementation of the project. The types of research will include secondary research (Literature Review), and they may or may not include primary research (involving even human participants). The literature review can be on the current state of the art in the area of your proposed project. This section should contain a preliminary list of secondary sources that you will use (referenced and relevant to your project. Not too many. About three will do). The evaluation of this section will also include an evaluation of the list of references in the end of your report. Note: You are NOT going to undertake the research at this stage. You are only outlining the research to be undertaken later. The Literature Review will be completed in the next coursework assignment, whereas the primary research will be undertaken as part of the project.

What would be a good research topic? Don’t confuse it with the project title. If you are developing, let’s say, a mobile app, such as a fitness tracker, you have questions and dilemmas to answer. For example, why would I want to use your app? What would make it attractive to me as part of the audience? You can undertake research into the most wanted functionalities in a fitness tracker, and if you want to do it for gym goers, or outside runners, bikers, or whatever. You get the gist now. The secondary research will answer some questions you have, and will inform the design stage. So, choose a good topic, do some preliminary research on some sources, put those sources here, and job done for the secondary research part. For primary research, think about the need for it.

(About 200-250 words) 10%

3.0 Resources and Skills (about 200 words) 

Describe the resources and skills required for the implementation of the project.

It goes without saying that “do not start a project, if you do not have all the resources to complete it.” So, evaluate what you have, and plan for what you need, even in the form of preparing yourself before the project implementation to have knowledge and skill in a programming language that you need. This is part of the project plan. This will also include the hardware and software resources.

You can organise it in a table, or any suitable format. However, it should include the HW/SW resources, and your skills (what you have and what you need).

(About 200-250 words) 10%

4.0 Project Plan 

Now, we come to the project plan itself, which will result in the end, and it will include a Gantt chart (or another type of chart, such as Burndown chart. Up to you.)

In this section, using the project objectives from Section 1 (Introduction), you will plan your project through the development of a project schedule and a Gantt chart.

4.1 Task list and schedule 

You will demonstrate your project planning skills in this section, by first dividing the project into a number of tasks, then you will allocate time to each task, finishing the planning work with a Gantt chart.

How do you get the tasks? Use the functionalities and the project objectives to get a list of tasks that are needed to complete, to get the project done. The project schedule and the Gantt chart will be done in Excel format and then copied in the appendix part of this proposal. In this section you will describe the planning work, illustrated by some partial screenshots of your work.  

4.2 Gantt chart 

Remember the order of work – first you come up with a task list, then use the deadlines from the project objectives to allocate time to each task and you will have a project schedule. Then, use the schedule to create a Gantt chart or a Burndown chart, depending on your project. If you don’t know what they are, undertake some research and you will see that it is not difficult. The order or the timescale for each task in the Gantt chart may be different from the schedule, because you can make changes. Visualisation from the Gantt chart helps you to see things better and make changes.

(About 300-350 words, excluding the word count inside tables). 30%

5.0 Risks  

Risks that you may encounter during the implementation of the project. This section should include factors that can prohibit your project from being successful, including your skillset and scope creep.

Note: Time is not a risk factor, because the timescale is appropriate for project implementation work. Time management skills that you possess can be a positive factor, or a risk factor. Disasters, such as loss of data, can be risk factors. How do you plan for this risk? Of course, regular backups on a separate storage area.

What about illness, or any unpredicted events? If you dedicate as much time as you can, when you have the time, it will help you to have some leeway, when things happen and you have less time available. Talk about real risks, and not theoretical risks from materials you read.

If you have a real client to work for, like your employer, and then suddenly you find yourself in another job, it can be a risk, but it may not. You don’t actually need a client, so if you are still able to complete the project and present it to us, then there is no risk. However, if you have to use client resources to do the project, then the risk is real, and you need to have a plan.

Anyway, time for you to think about your risks.

 (About 200 words) 10%

6.0 Legal, Social, Ethical and Professional (LSEP) issues 

Legal, Social, Ethical and Professional (LSEP) issues that you may encounter during the implementation of the project. Consider LSEP issues individually for each of the Legal, Social, Ethical and Professional categories. If you don’t encounter any of the LSEP categories provide a brief description on why that is the case. In terms of Legal Issues there are a number of areas of legislation that relate to computing, including the Computer Misuse Act, the Data Protection Act, the Equality Act 2010 and Copyright. Social Issues refer to the social impact of the artefact you will be developing.

See, for example, the relevance of social issues in ubiquitous computing environments. In terms of Ethical issues, consider whether or not your project will require primary research involving human subjects at any point. In this section, you can discuss the wider ethical implications of your project but you must also demonstrate knowledge of University regulations in this regard.  

Note: When considering the above issues, your main focus will be on the project implementation period. Issues beyond the project implementation period can only be discussed if the intended usage poses moral or ethical issues, or if you are advising the project sponsor on the legal and professional usage of the artefact. Note also the organization of the section in paragraphs, and not just one big chunk of text, which is difficult to read. 

Divide this section into subsections:

6.1 Legal Issues

6.2 Professional and Social Issues 

6.3 Ethical Issues (These issues relate to the use of human participants for primary research) 

(Up to 400 words) 20% 

Note: Up to this point, my instructions amount to about 1600 words, so this can be a very good guidance on how much you need to write in each section. Don’t be afraid of overdoing it. There is always the appendix to take everything that is valuable. 

7. Proposal Summary (about 250 words, but not included in the word count) 

8. References at least 20 

Here, in Harvard format, you list your sources of reference, that you have used in the report.

9.0 Appendices 

9.1 Appendix A Project Schedule

Make sure that every picture, screenshot, table, or graph/chart that you include in your report are accompanied by explanatory text. Otherwise, it is a headache for the reader to try and understand what you had in mind when you put it there. And it does not matter where it is, in the main sections, or here in the appendices, it is the same – explain it. How much explanation, then it depends on the context.

9.2 Gantt chart  

9.3 Maybe some background research on the project can be included here, or anything that you think will add value to the project, but you cannot include it in the main sections, due to the word count. No need to ask questions. If you think is valuable, put it here, you can only get marks for it, but no mark deduction, if it is not required. 

**********************************************************

Attachment 2:

Detailed description of the task:

You have to produce a written document (1600-1700 words maximum) proposing a project with a structure that has the following sections (apart from the title page, contents page, references page, and the appendices):

Section 1: Introduction 

• Aim of your proposed project, and what it intends to achieve. Propose a project that deals with one or more computer science domain problems devising realistic solutions.

• A more detailed description of the problem that the problem will solve (called Problem Statement). Describe the problem from the business, or organizational, or the intended audience point of view.

• A descriptive list of functional requirements of your intended artefact. Comment on which functionalities should be considered “advanced” from the project implementation point of view.

• A list of Project Objectives that will help you to plan and manage the project. These objectives must fulfil the SMART criteria (no need to mention the word SMART in your proposal).

 (Up to 400 words) 20%

 
Section 2: Research methodology and plan. In this section, you should identify areas of research that you need to undertake, which will help you with the design and implementation of the project. The types of research will include secondary research (Literature Review), and they may or may not include primary research (involving even human participants). The literature review can be on the current state of the art in the area of your proposed project. This section should contain a preliminary list of secondary sources that you will use (referenced and relevant to your project). The evaluation of this section will also include an evaluation of the list of references in the end of your report. Note: You are NOT going to undertake the research at this stage. You are only outlining the research to be undertaken later. The Literature Review will be completed in the next coursework assignment, whereas the primary research will be undertaken as part of the project. (Up to 200 words) 10% 

Section 3: Describe the resources and skills required for the implementation of the project. (Up to 200 words) 10% 

Section 4: Project plan including a Gantt chart. In this section, using the project objectives from Section 1 (Introduction), you will plan your project through the development of a project schedule and a Gantt chart. You will demonstrate your project planning skills in this section, by first dividing the project into a number of tasks, then you will allocate time to each task, finishing the planning work with a Gantt chart. The project schedule and the Gantt chart will be done in Excel format and then copied in the appendix part of this proposal. In this section you will describe the planning work, illustrated by some partial screenshots of your work. (Up to 300 words, excluding the word count inside tables). 30% 

Section 5: Risks that you may encounter during the implementation of the project. This section should include factors that can prohibit your project from being successful, including your skillset and scope creep. Note: Time is not a risk factor, because the timescale is appropriate for project implementation work (Up to 200 words) 10% 

Section 6: Legal, Social, Ethical and Professional (LSEP) issues that you may encounter during the implementation of the project. Consider LSEP issues individually for each of the Legal, Social, Ethical and Professional categories. If you don’t encounter any of the LSEP categories provide a brief description on why that is the case. In terms of Legal Issues there are a number of areas of legislation that relate to computing, including the Computer Misuse Act, the Data Protection Act, the Equality Act 2010 and Copyright. Social Issues refer to the social impact of the artefact you will be developing. See, for example, the relevance of social issues in ubiquitous computing environments. In terms of Ethical issues, consider whether or not your project will require primary research involving human subjects at any point. In this section, you can discuss the wider ethical implications of your project but you must also demonstrate knowledge of University regulations in this regard. Professional issues can be discussed in relation to the BCS Code of Conduct. There is also the ACM Code of Ethics and Professional Conduct. Note: When considering the above issues, your main focus will be on the project implementation period. Issues beyond the project implementation period can only be discussed if the intended usage poses moral or ethical issues, or if you are advising the project sponsor on the legal and professional usage of the artefact. (Up to 400 words) 20% 

Additional guidance notes  

Please ensure that:  

• you include the word count after each section;

• your report clearly contains the six sections listed above;

...........................................................................................................................................................................................