闪电代写 -代写CS作业_CS代写_Finance代写_Economic代写_Statistics代写_代码代做_IT代写_加急帮助

Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

Module title & code

WM9A4-15 Digital Development with Python 24/25

Assessment type

Essay

Weighting of mark

70%

Assignment brief

Scenario:

You have been hired by the University of Warwick to provide consultancy on developing an interactive web application for displaying information and managing enrolment for a diverse range of online short courses. The University of Warwick offers various short summer courses in different domains such as technology, business, and sciences. They aim to enhance user engagement, streamline course management, and improve the overall user experience.

You must design and implement core features of the interactive web application. Although it is not necessary to fully realise the application, some essential features should be coded and thoroughly documented, along with plans for future functionalities.

Part One – 60% (42 marks):

Your report must:

· Explain the core objectives of the application.

· Identify and describe two key principles that will shape the design and development of the application.

· Provide a detailed description of how data will be stored, retrieved, manipulated, and managed within the application.

· Discuss a likely challenge or risk associated with developing the web application and propose how this risk can be mitigated.

Part Two – 40% (28 marks):

Your report must:

· Provide source code or pseudocode for features that you have implemented as well as discuss features planned for future development.

· Explain the approach taken in your code implementation.

· Discuss how your application adheres to best programming practices.

· Provide an overview of the testing methodologies used to ensure the quality and functionality of your code.

It is MANDATORY for all source code to be included in the appendix of the report in plain text to be considered for marking. Guidance on this can be found on Moodle, but please speak to the module tutor if you are unsure. Additionally, you can provide a link to a GitHub repository containing your source code or a link to your deployed web application if you wish, though source code in the appendix is STILL REQUIRED.

Word count	Suggested word count – 2800 words for the main body of content, not including source code, documentation, table of contents and reference list. Plus or minus 10% of the word limit is acceptable..
Module learning outcomes (numbered)	1. Analyse business needs and collaboratively design and pitch an innovative web application proposal, demonstrating project management and communication skills. 2. Critically assess and combine various programming languages to develop interactive and professional web applications. 3. Critically evaluate software development lifecycle methodologies and develop both theoretical and practical workflow models. 4. Critically evaluate the impact of programming in business to develop innovative solutions for business challenges. 5. Critically examine various issues and design structured applications in a suitable programming language to address them.
Learning outcomes assessed in this assessment (numbered)	2,3,5
Marking guidelines	See below.
Academic guidance resources	Time will be reserved during the module to review the module assignment and for students to raise questions, and students are permitted to ask the Module Leader questions about the assignment up to the submission deadline.

Where to get help:

1. Talk to your module tutor if you don’t understand the question or are unsure as to exactly what is required.

2. There are also numerous online courses provided by the University library to help in academic referencing, writing, avoiding plagiarism and a number of other useful resources. https://warwick.ac.uk/services/library/students/your-library-online/

3. If you have a problem with your wellbeing, it is important that you contact your personal tutor or wellbeing support services https://warwick.ac.uk/services/wss

Marking Guidelines:

Part 1 – 60% (42 Marks)

Criteria	80-100%	70-79%	60-69%	50-59%	40-49%	0-39%
Core Objectives (10%)	Clear, comprehensive objectives, fully aligned with user needs and project goals.	Well-defined objectives, mostly aligned with user needs and project goals.	Good objectives, generally aligned with user needs and project goals.	Clear objectives, some alignment with user needs and project goals.	Basic objectives, limited alignment with user needs and project goals.	No clear objectives or alignment with user needs and project goals.
Design Principles (30%)	Two key principles excellently articulated and highly relevant.	Two key principles well-articulated and relevant.	Two principles articulated, mostly relevant.	Two principles mentioned, some relevance.	Two principles mentioned, limited relevance.	No principles mentioned or relevance.
Data Management (30%)	Detailed, clear data management plan, highly effective.	Clear data management plan, effective.	Good data management plan, generally effective.	Clear data management plan, some effectiveness.	Basic data management plan, limited effectiveness.	No clear data management plan or effectiveness.
Challenges and Risks (20%)	Comprehensive discussion of challenges/risks, excellent mitigation strategies.	Good discussion of challenges/risks, good mitigation strategies.	Fair discussion of challenges/risks, some mitigation strategies.	Clear discussion of challenges/risks, basic mitigation strategies.	Basic discussion of challenges/risks, limited mitigation strategies.	No discussion of challenges/risks or mitigation strategies.
Structure and Visual Aids (10%)	Exemplary structure, clear consultancy role, targeted audience, precise outcomes, excellent use of visual aids.	Very good structure, clear report style, good use of visual aids.	Good structure, decent visual aids.	Clear format, some visual aids, but not fully effective.	Clear format, few or irrelevant visual aids.	No clear structure, lacks all elements.

Part 2 – 40% (28 Marks)

Criteria	80-100%	70-79%	60-69%	50-59%	40-49%	0-39%
Implemented Features (20%)	Fully functional features, exemplary code quality, clear and concise, excellent variety and integration of programming languages.	Mostly functional features, high code quality, clear and concise, good variety and integration of programming languages.	Functional features, good code quality, generally clear, fair variety and integration of programming languages.	Basic functional features, decent code quality, somewhat clear.	Limited functional features, fair code quality, somewhat unclear.	No functional features, no code quality, not clear.
Future Functionalities (10%)	Well-documented future features.	Documented future features.	Future features mentioned, mostly clear.	Basic mention of future features.	Limited mention of future features.	No future features.
Approach and Explanation (30%)	Excellent approach, thorough explanation.	Very good approach, good explanation.	Good approach, fair explanation.	Decent approach, basic explanation.	Basic approach, limited explanation.	No clear approach or explanation.
Best Practices (20%)	Exemplary adherence to best practices, highly effective.	Good adherence to best practices, effective.	Fair adherence to best practices, generally effective.	Basic adherence to best practices, somewhat effective.	Limited adherence to best practices, limited effectiveness.	No adherence to best practices or effectiveness.
Testing Methodologies (10%)	Comprehensive testing, excellent methodology.	Good testing, clear methodology.	Fair testing, decent methodology.	Basic testing, somewhat clear methodology.	Limited testing, unclear methodology.	No testing or methodology.
Structure and Visual Aids (10%)	Exemplary structure, clear and professional presentation, excellent use of visual aids.	Very good structure, clear presentation, good use of visual aids.	Good structure, decent use of visual aids.	Clear format, some visual aids, but not fully effective.	Clear format, few or irrelevant visual aids.	No clear structure, lacks all elements.