ACS130 Introduction to Systems Engineering and Software ACS130-002 Craig Bacon ([email protected], Room A10, AJB) Tara Baldacchino ([email protected], Room D13, AJB) Assignment Weighting: 15% flowchart + 25% for robot software + 10% individual contribution = 50% Assignment Released: Friday 13th November (week 7) Assignment Deadlines: See below. Please also refer to the ACS130RobotSpecification.pdf and other resources found on Blackboard in ‘Arduino Robot Project’. How and what to submit 1. The flowchart must be submitted to the ACS130 Blackboard> Arduino Robot Project>Flowchart. You must upload your diagram as Groupx (where x is your group number) which you have created for this assignment to the above drop box. Please submit a PDF so that I can access your flowchart. Only one group member needs to submit. Deadline is 11.59pm Monday 30th November (week 10)- one submission per group. 2. The robot software needs to be implemented and available in the Tinkercad class assigned to you. Please follow the instructions for working collaboratively on the project. The deadline is and your final version needs to be called GroupXFINAL where X is your group number. Deadline is 11.59pm Sunday 14th February (week 2)- one submission per group. Marking will involve your group demonstrating your project- details to be confirmed in semester 2. 3. Additionally, you need to copy your code and paste it to a word document and submit it to Turnitin via ACS130 Blackboard>Arduino Robot Project>Robot Software. Failure to upload your code to Turnitin will result in a 10 mark penalty. In this document you also need to answer the research question provided below. Deadline is 11.59pm Sunday 14th February (week 2). 4. Individual contribution needs to be submitted in ACS130 Blackboard>Arduino Robot Project>Individual Contribution. Deadline is 11.59pm Monday 15th February (week 2). 5. Peer assessment which will be used to influence the group mark to form an individual mark. This is found in ACS130 Blackboard>Arduino Robot Project>Peer Assessment. Deadline is 11.59pm Monday 15th February (week 2). To work collaboratively on the project, please 1. Go to https://www.tinkercad.com/joinclass 2. Enter the class code: For ACSE students ARD6-GISX-64LH, and for Aero students FJFQ-RISZ-GAU1 3. Click ‘Join with Nickname’ 4. Enter the Nickname I gave to your group Assignment Briefing You need to draw the flowchart, build the circuit and write the software, as well as answer a research question, for a robot tracking a beacon whilst avoiding obstacles. The software should control the robot to behave as follows: Startup with a three second delay during which the LEDs must flash. The robot will scan the room, by turning on the spot, to locate an emergency beacon, once detected the robot shall track and proceed towards the beacon whilst avoiding obstacles. You must design (by drawing a flowchart), implement and test software which will run on the ‘hardware’ you create in Tinkercad. The programming language used in this assignment is Arduino C. This project follows a V-model (figure below) approach where you are required to design the software of the system, then implement that logic followed by testing your solution. 1. Flowchart (15%) due 11.59pm Monday 30th November (week 10) The flowchart needs to be detailed enough that it shows loops and decisions to show how you would attempt to implement this project to get the robot to do what we’ve asked for in the assignment briefing. I also want a description which provides some insight into what the flowchart is doing which is crucial to the steps asked for in the assignment briefing (eg explaining what the various loops are doing, explaining points in the flowchart where the robot detects an object etc). This will help me better understand what your flowchart is doing as well as indicating that you have achieved all of the objectives of the brief. I also want details of what parts you could potentially put into functions, including details of input parameters as well as return variables. The flowchart can be hand drawn, but please make sure it is legible so that I can mark it fairly. You can then take a photo of it so that you have it digitally. You can also use freely available software, eg, https://www.lucidchart.com/pages/. I am not necessarily expecting your flowchart to be correct, in terms of the logic- so no marks are for correctness, but rather have you attempted to solve the problem given to you and have you given sufficient detail? I am interested in your thought process for solving the problem at hand. This stage is an important step when designing systems because it helps to break down the problem. Flowchart: effort made to solve the problem based on the specification /3 Description /4 Functions: ideas about what can be put into a function, including input variables and return parameters. /4 Details: loops, reading from sensors etc. /4 Overall Mark /15 Flowchart Marking Criterion Marks 2. Robot Hardware & Software (25%) due 11.59pm Sunday 14th February (week 2) The software code and research question need to be submitted to Turnitin in ACS130 Blackboard. During the ‘lab’ session we will mark your working code via Tinkercad class. 4. Individual Contribution (10%) due 11.59pm Monday 15th February (week 2) Individually submit a paragraph to ACS130 Blackboard>Robot Arduino Project>Individual contribution which tackles the following points. If from your description it is obvious that you have not contributed to the group work, then marks will be deducted from the robot project mark. You are allowed 100-150 words per point (so 450 words max). 5. Peer Assessment due 11.59pm Monday 15th February (week 2) Since this is a group project, you will have the opportunity to submit an evaluation of the contribution of the individual members of the group. If everyone in your group contributed equally then you do not need to fill in a form because the marks won’t change. Otherwise, please fill in the form found on Blackboard>Robot Arduino Project> Peer Assessment. The deadline to submit this is 11.59pm Monday 15th February (week 2). This form will be used to evaluate the contribution of individuals in a group, and I will use it to raise or lower the mark for individuals based on the information and evidence provided in the form. How the marking will be done Robot Hardware and Software Marking Criterion Marks Does the robot do what is asked for in this assignment briefing? Start-up flashing of LEDs, scanning for beacon, tracking beacon (correct motors moving depending on which beacon sensor is activated), avoid obstacles sensibly (motors need to be moving in sensible directions to avoid the obstacles). /10 Clarity of the information printed to the screen- is it obvious what the robot is doing from the text provided on the serial monitor? /3 Software readability (use of header comment, comments, indentation, meaningful variable names) /3 Use of user defined functions /4 3. Research question: Can your group provide an explanation of an alternative method that can be used to move away from the obstacles (once they have been detected)? You are currently using delays to move away from the obstacles. What else could be used? How does it work? Is your proposed method more or less accurate than the current method? This will be marked via Turnitin. /5 Overall Mark Individual mark depends on ‘attendance’ to marking session (-5). /25 Individual Contribution Marking Criterion Marks Describe what involvement you had in designing, implementing and testing the software for the system, using the V-model as a reference. /4 Analyse and describe how you thought the team worked on this project, including a reflection on how teamwork within the group could have been improved. /3 Reflect and describe the skills (both academic and professional) that you have acquired or improved as a result of working on this project. /3 Overall Mark /10 The flowchart will be marked via Turnitin and marks will be available to you via Blackboard. I will go over a potential flowchart
to the robot project in the week 11 synchronous online session before the robot software deadline. This will give you the opportunity to review how you are tackling the solution to the robot project. The hardware and software will be marked during the timetabled ACS130 lab sessions in week 2 of semester 2: exact times and dates will be confirmed closer to the time. The marking will involve demonstrating the robot software and discussing the code. You need to submit your code, and research question by end of day 14th February. The module leader will review the code and moderate all marks after the lab session. This marking session is compulsory and all members of the group must be present. Failure to attend will result in a 5 mark penalty. The individual contribution will be marked via Turnitin and marks will be available to you via Blackboard. The assignment briefing also shows the marking criteria for the various components of the robot project. How you should work This assignment is to be done in groups of two students, and it must be wholly the work of the group. All individuals in the group must contribute equally to the work. The work will be done in the timetabled ACS130 labs, as well as outside the lab sessions since you will be able to work on the project in your own time. The software used is Tinkercad which you have experienced in the practice sessions. Learning Outcomes By the end of this assignment, students will be able to: • Design, implement and test software, following the V-model, to control hardware, creating an integrated software/hardware system. • Work effectively in a team, hence improving team working skills. Additional Information Penalties for late submission Late submissions will not be allowed for this assignment. The software will be marked as is, at the marking session detailed on the first page. Unfair means Your group is not permitted to submit the partial or full work of other groups or material from any other source as your own work. Any suspicions of the use of unfair means will be investigated and may lead to penalties. See http://www.shef.ac.uk/ssid/exams/plagiarism for more information. Extenuating Circumstances If you have medical or serious personal circumstances which cause you to be unable to submit this assignment on time or which may have affected your performance, please inform me ([email protected]), and complete and submit an extenuating circumstances form along with documentary evidence of the circumstances. See http://www.sheffield.ac.uk/ssid/forms/circs. Help This assignment briefing, the lectures, the practice sessions and resources on the ACS130 Blackboard course and the training in the ACS130 laboratories provide all the information that is required to complete this assignment. If you need clarifications on the assignment, then please ask a GTA or staff member during the lab sessions, or post a question on the ACS130 Blackboard discussion board. 欢迎咨询51作业君
