The Australian National Health Priority Areas (NHPA) highlight areas where primary health care is essential for improving health outcomes in the future. This information needs to find its way to those who need it most and the general population as a whole. This information can be presented as an educational activity by the nurse. For this assessment you will plan and develop an educational activity based around the NHPA of diabetes mellitus. You are NOT required to present your educational activity for this assessment. This activity needs to reflect the nursing process and in particular, the Clinical Reasoning Cycle. The information needs to be evidence based and directed to your target audience. There is a link to the Clinical Reasoning Cycle on the Moodle site. Once you have researched the topic, you will need to outline how this educational session will be delivered including information such about why, how, where, what and when. You should also consider and include aspects such as: How will you organise your audience to be present? Do you need to think about any additional resources to deliver the activity? How will this activity be funded? Does it require funding? REMEMBER: This is a PRIMARY HEALTH educational activity. Keep it relevant to your target audience. Please note the following details: • Word limit is 1500 words (+/- 10%). Appendices are not included in the word count. • Text should be word processed, with appropriate formatting, size 12 font, double line spacing and layout - please refer to the marking criteria for more detail. • You may use headings if preferred. • You must write in academic style, be mindful of casual language, grammar and punctuation and sentence structure. • You can choose to add diagrams although, these are not required. • If you choose to add a diagram, please add it as an appendix and ensure it is appropriately referenced. This will not be included in your word count. • Save and upload your file as a Word document so it can be marked. • You must reference your assessment as per the APA referencing style guidelines. Brief They will involve the use of web based development tools such as Python / Django and HTML / database technologies to develop a simple software system utilising a web based interface. Phase 1 involves the development of a structured English description of the major components of a software system from short textual information pieces alongside the creation of UML and similar diagrams of the system structure. Phase 2 involves the implementation of this design within a suitable web based language and deployment to an appropriate web-server technology. Phase 3 is an analysis of the completed development work with specific reference to software engineering principles and a critical review of the software engineering process and the benefits of object orientated design for this kind of system modelling. Phase 1 Deliverables: • A design portfolio for the indicated (or similar) system typically including: o Structured English description of the system to be produced o Requirements specification o Use cases and use case models o Sequence / interaction models o Class diagrams (optional stub code for review) o Design rationale for the application of design patterns to the system Phase 2 Deliverables: • Implemented code for the project analysed for phase 1 in an appropriate web based language (e.g. Python 3.x, MySQL, HTML5) • Documented testing strategy and results • Screencast / demonstration of the software functionality Phase 3 Deliverables: • An initial critical self appraisal of with regard to your development skills • An analysis of how you have applied the software engineering principles to the software developed in phase 2 • A critical review of the project development What you are expected to submit: • Phase 1: o Appropriately formatted text document containing all relevant information. Submission must be in a PDF (.pdf) or Word (.doc, .docx) file format. • Phase 2: o A zip file containing the fully functional web application prototype o An appropriately formatted text document containing:  A link to the website if appropriate  The testing documentation o Screencast demonstrating functionality • Phase 3: o An appropriately formatted text document containing all relevant information. PDF or Word file preferred. The work should be no more than 2000 words in total, with a preferred length of around 500 words for each of the assessed sections in the work. There is no penalty for exceeding the word limit. Problem Scenario As a developer Software Ltd (DSL) you have been asked to produce a prototype web application for a group promoting sports - Local Sports Clubs (LSC). The sports club has submitted a short written proposal for their project and a statement as to the intent / aims of the project. You have been given the task of producing a design and development plan for this application and implementing a simple prototype of the work before further work is carried out. Contextual Information: The Organiser for Local Sports Clubs “We are looking to roll out software for multiple local sports clubs over the following year to allow them to organise leagues and tournaments so that we can encourage people to take part in healthy exercise routines and simply to get out there and play sports. Overall we are looking for a clean and simple set of tools, a web page or an app maybe, which can be used by a local co-ordinator to enrol people onto the system, track their attendance, injury, and play statistics as well as maybe tracking other things like fitness goals. We want to be able to get people to join into teams for friendly and competitive leagues and tournaments and track their team and individual competitiveness ratings. If possible we would like the software to provide a sign-up page for individuals joining teams and for teams to be able to advertise their available spots. The individual sport for the prototype doesn’t really matter. We know this is a bit fuzzy but we also need to be able to keep notes on people and teams for things like fouls, injuries and penalties so we need some kind of admin system, and ideally the regional co-ordinator should be able to manage multiple locations and cross data between them.” Proposal Requirements: • Web or mobile app • Track teams within a league and / or tournament structure (Swiss or Single elimination, ideally both) • Track team and individual skill ratings using something like an ELO ranking • Allow records to be kept on individuals • Allow records to be kept on teams • Registration for users and administrators • Additional support for news and articles within the web page or results pages Guidelines: Criteria Description Phase 1 The work will be evaluated on the analysis and design work performed by the student. 15% - Analysis of the problem solution and implementation of a set of criteria related to the project. 15% - Design of the analysed system developed by the student. Marks awarded in this section are based on the design coherence to the analysis performed and the appropriate use of design techniques. At higher mark ranges a wider number and type of techniques should be implemented as appropriate. Phase 2 The work in this section will be based on the design implemented by the student in phase 1. 15% - Functional implementation of features indicated in the design plan 10% - Appropriate use of design patterns and object orientated programming techniques 5% - Documentation and testing of the system, provision of an appropriate screen cast demonstrating the functionality implemented. Phase 3 The work in this section is based on the student’s evaluation of their own work as well as their evaluation of the use of design patterns within the work they have used. 15% - Critical reflection on the work implemented and the capabilities that the student has learned 15% - Critical reflection on the use of design patterns within the project and the wider software industry. 10% - Critical review and reflection on the use of software engineering techniques within the software community. • The prototype you are asked to produce should: • A single or multi-site solution to the problem (multi-site / multiple levels of administrators being graded more highly) • A web or application interface which displays news / events, and has login capabilities • A web or application interface which allows an administrator to: o Add people to the system o Add teams to the system o Add people to teams o Add details of attendance at events, current injuries, and track their play statistics (goals / points / ranking etc.) as determined by you o Add events to the system (league or tournament, adding both and variants being graded more highly) o Add matches to events o Add games to matches o Allow results entry / automatically calculate event results at each stage / at the end (automation being graded more highly) • Optionally: A web or application interface which allows a user to: o Register on the system o Add themselves to teams that have open slots o Find teams that have open slots o Report injuries • Optionally: Administration system that allows for the update of existing information You are given free reign with the design aspects, the practical is looking to get you to make justifiable decisions within the context of your own knowledge base and to carry those design and analysis elements through to documentation and testing of the prototype. You should find appropriate sources or justifications for your decisions and write about the choices that you made in phase 3 when you carry out your critical reflection on the process. In regards to specific questions: 1. For which sport, we will develop site? 1. The client doesn’t have a preference, select a sport of your choice. 2. It has mentioned in a document that we will create a site for "multiple local sports club". Can you please give brief idea? 1. The idea is that the website should not be heavily influenced by a single site, if you want to carry out extensive theming or similar these should be customisable within the application itself, multiple sites will use the system so it will need to either be stand alone at each site, or interconnected if you choose to allow a regional coordinator role. 3. How many types of user can login into the system? (For ex. Admin, co-ordinator, etc...) 1. As a default 2, the administrator and the user, though you may choose to add the regional coordinator or any other roles that you wish to add such as team captain, authorised editor etc. 4. We will provide registration functionality for co-ordinator, but should we provide registration functionality for People or co-ordinator will register people from his login? 1. A default coordinator account will need to be provided to create sub coordinator accounts, the choice is yours to allow people to self register, be added by the coordinator, or self register with approval – the client has no preference. 5. Co-ordinator will track attendance, injury, and play statistics as well as maybe tracking other things like fitness goals of People. Can you please give some brief idea? 1. Attendance should be a mapping of events that the players team is assigned to to their attendance on the day. 2. Injury should likely be open text field, with perhaps some common injury types or descriptions if needed. The idea being that attendance while injured is not required, this can be implemented as a simple toggle, a range of dates, multiple ranges of dates, or any other system that you can suggest and justify. 3. Play statistics should track for example goals scored, interceptions, or similar sports specific issues that you would like to represent. The choice is open to you to demonstrate the kind of functionality that could be presented here. 6. Who will create Team? How should we assign people into Team 1. The choice is yours, teams could be registered by players (possibly creating a team-captain role / login?), or by the coordinator. The client has no specific preference. 7. "Teams to be able to advertise their available sports". Can you please explain? 1. A team may play in multiple different types of sports, for example 5 a-side football and 5 a-side rugby, and 7 a-side football. A team could then be entered in multiple different leagues / tournaments of the appropriate type. The choice of complexity is yours with the default being 1 team:1 sport 8. "Individual sport for the prototype". Can you please explain? 1. You are asked to implement the solution for only a single sport e.g. badminton and to have the matches / games / tournament / league structure for only that type of game. If you wish to add more you may do so. The choice of sport is left to you as the client has no specific preference. 9. "We also need to be able to keep notes on people and teams for things like fouls, injuries and penalties so we need some kind of admin system". Which type of information should we store and how admin will store above information for people and teams? 1. The choice of database structure is up to you – the client is only concerned that the information is accessible and that they can view it. The choices of data will depend on the sports that you choose to implement as different sports have different types of fouls, penalties and similar. This could be for example a negative points score on their tournament score, or a game loss, or a match loss. As this is a prototype the implementation choice is yours. 10. "Co-ordinator should be able to manage multiple locations and cross data between them". Can you please explain? 1. The default assumption for this is that you will deploy the software as a stand alone to a single site. If you choose to include a regional coordinator account then additional functionality such as cross-area teams, multiple coordinator accounts, regions etc. are suggested as additional possible areas of exploration. PHASE 3: 1. Give brief idea of how much details do you require in all 3 following points: 1. "An initial critical self-appraisal of with regard to your development skills"? 1. What were your initial skills entering this programme, what experience level did you have, what have you learned on the course and through this work, what gaps in your skills or knowledge have you identified, what do you need to improve upon etc. 2. "An analysis of how you have applied the software engineering principles to the software developed in phase 2"? 1. How did you apply the principles of software engineering to the development work that you were asked to carry out, what software engineering techniques did you utilise and how did they assist / detract from the implementation. What tools should you have used and why. 3. "A critical review of the project development"? 1. Review of your own work, what was successful, what wasn’t. How was your time management, how did you spend your time, did you apply yourself to the project. Were your initial analysis questions correct, did you carry through the assumptions to the other phases, could you justify your decisions, could you justify your decisions objectively. There are no right or wrong answers in phase 3, and phase 2 is based off of your analysis work carried out in phase 1 so again there are strictly no right or wrong implementations – you need to justify and validate your choices such that a reasonable client and external observer would agree with you.