Faculty of Science and Engineering Unit Managing Software Development Unit codeISYS3001 Due Date24 September XXXXXXXXXX:00 PM Learning Outcomes5, 6 Weight20% of overall unit assessment Assignment...

I WANT HD ,MY FINAL ASSIGNMNET SO HAS TO BE BEST


Faculty of Science and Engineering Unit Managing Software Development Unit codeISYS3001 Due Date24 September 2021 11:00 PM Learning Outcomes5, 6 Weight20% of overall unit assessment Assignment 2 Description The assignment has component that is a C# source code, but the majority are written responses. The responses and the C# code should be submitted through the submission link in the unit site. Please do not leave the assignment to the last minute as you can start working on the assignment straight away. If you do require an extension for submission, you must request this before the due date. Unless an extension is agreed, a late penalty will be applied. Please be aware that any extensions might mean that you won’t receive your grade before the final assessment. Each day late submission will apply a 5% penalty with a maximum of five days late. Submissions after four days will not be awarded any credit. Please note that a timestamp of 11:01 on the due date is considered one day late. This assignment covers the agile development and automatic document generation topics in this unit. Important: You must submit your own solution with reasoning, however, we are perfectly happy for you to chat and discuss with previous students of this unit and your current classmates. The last bit is particularly important. What we are looking for is the thought process behind your designs and solutions as well as the actual solutions. Reports which do not give satisfactory reasons for their designs and solutions will be penalised. Part 1 - Agile processes (15 marks) Mountain Top Development (MTD) is a company involved with Internet of Things (IoT) products. The founders of MTD recognised a larger need for small and ‘smart’ software products than centralised large systems. To maintain its competitive advantages, MTD has to adapt itself to the market. Sizes of their development projects will become smaller, while multiple projects of many varieties may be undertaken in parallel. The Waterfall process model is not appropriate for many of their future projects. MTD is investigating the adoption of Agile methodologies and practices. You are required to write a report on the adoption of Scrum and XP methodologies (including identifying individual practices and processes suitable) for Mountain Top Development. Your report should provide: 1. An overview of the Agile mindset (3.5 marks). 2. Comparison of the Agile mindset and the Waterfall process (3.5 marks). 3. Description of the Scrum process and XP methodology (3.5 marks). 4. Guidelines for choosing Scrum or XP according to types of projects (3.5 marks). 5. Another well-known process as candidate of adoption of new process for the second stage (1 mark). The other well-known process can be any process you know. This will require independent research and your illustration of understanding Agile concepts in software development. The contents of the report should be organised logically, and the report should have a title, an executive summary, a table of content, an introduction, a conclusion, and reference list. The briefing should be a maximum of 1500 words. This is a briefing to an employer/client. You will be penalised for going over the limit, as it may indicate your writing is not precise and you have not thought about your responses enough. Part 2 - Automatic document generation (5 marks) Your clients have requested a demonstration on the value of automatic document generation to be presented to their new junior programmers that have just begun working at the company. Attached is a C# program for a simple game that you are required to use to demonstrate this. You must replace the current inadequate comments with the C# XML comments. Your XML comments should contain examples of each of the following tags at the very least: 1.

and (1.5 marks) 2. and (1.5 marks) 3.

(1 mark) 4. (1 mark) Note that your code does not have to compile but you could implement it in Visual Studio to iron out problems. Please note that you need to explain each of your C# XML comments. Comments without a good explanation will result in loss of marks and may not be marked entirely. namespace Assign2 { // // This program is for ISYS3001 Assignment 2 (2021) // // It calls some functions that need commenting // class Program { // // Mainline function // static void Main(string[] args) { int num1 = ReadNumber(); int num2 = ReadNumber(); FormatBinary(num1, "+", num2, Add(num1, num2)); Console.ReadLine(); } // // Read a single integer // public static int ReadNumber() { Console.Write("Number: "); try { return Convert.ToInt32(Console.ReadLine()); } catch (FormatException) { Console.WriteLine("illegal number format"); return 0; } } // // Formatted operation output // public static void FormatBinary(int n1, string op, int n2, int result) { Console.WriteLine("{0} {1} {2} = {3}", n1, op, n2, result); } // // Add two integers // public static int Add(int n1, int n2) { return n1 + n2; } } } Mark deductions (after): Demerit areas Marks Not writing Report Title, Student Name, Student Number, etc. on the first page 1% Not writing the Executive Summary (Abstract) 1% Not using a table of content and/or page numbers 1% Not writing the Introduction and Conclusion sections 1% Incorrect referencing and/or reference list not on a separate page 1% Exceeding the maximum word-limit (+/- 10%) 2% Late submission penalty 5% per day Further Notes: · Word-limit: The maximum word-limit will be strictly applied. The marker can deduct marks for writing over this word-limit. So, make sure your report is completed within the given word-limit. There is no maximum word-limit applicable for Title, Executive Summary, Reference List, and appendices. · Start early and submit on-time: Avoid any pitfalls that may arise due to late start. Thus, start your assignment as soon as possible to submit on-time. For late submissions, the standard assessment submission policy will be applied (see the unit profile). · Appendix: You may add appendices to document any additional material you wish to include such as tables, diagrams, figures, or other supplementary material. Appendices do not contribute to the word count of the document. · Reference: You should add a reference section and include any references, including publications (literature, books, etc.), which you want to refer to, to support your report. · Late Submission: This assignment will be due on Monday, 19th April, at 11:00pm. A penalty of 5% of the available mark will be deducted from the actual mark for each day of late submission up to five days. · Consultation: You will have the opportunity to show your assignment draft to your tutors/unit assessor for feedback. · Contact: Please contact the unit assessor/lecturer/tutors if you have any issues or confusions. ISYS3001 – Managing Software Development 2 SOUTHERN CROSS UNIVERSITY ASSIGNMENT COVER SHEET For use with online submission of assignments Please complete all of the following details and then make this sheet the first page of each file of your assignment – do not send it as a separate document. Your assignments MUST be submitted as either Word documents, text documents with .rtf extension or as .pdf documents. Student Name: Student ID No.: Unit Name: Unit Code: Tutor’s name: Assignment No.: Assignment 2 Assignment Title: Due date: Date submitted: Declaration: I have read and understand the Rules Relating to Awards s18 as contained in the SCU Policy Library. I understand the penalties that apply for plagiarism and agree to be bound by these rules. The work I am submitting electronically is entirely my own work. Signed: (please type your name) Date: End ISYS3001 Assignment 2 ReportPage 2 8/12/2021 ISYS3001-2021-2 Managing Software Development https://learn.scu.edu.au/webapps/rubric/do/course/manageRubrics?dispatch=view&context=course&rubricId=_10486_1&course_id=_145827_1 1/3 Assignment 2   Levels of Achievement Criteria Excellent Good Partially Satisfactory Unsatisfactory Part 1-1 Provided an overview of Agile mindset 3.5 Points Provided both a comprehensive and succinct overview. 2.5 Points Provided an overview but with some missing information. 1.75 Points Some elements of an Agile overview attempted. 0 Points No genuine attempt made. Part 1-2 Comparison of the Agile mindset and the Waterfall process 3.5 Points Provided a comprehensive comparison of the Agile mindset and the Waterfall process 2.5 Points Provided a comparison of the Agile mindset and the Waterfall process but with some missing information. 1.75 Points Made a genuine attempt to provide a comparison of the Agile mindset and the Waterfall process but has signi�cant information missing. 0 Points No genuine attempt made. Part 1-3 Description of Scrum process and XP methodology 3.5 Points Provided comprehensive descriptions of Scrum process and XP methodology 2.5 Points Provided some descriptions of Scrum process and XP methodology but is missing information and/or evidence of research. 1.75 Points Made an attempt to present descriptions of Scrum process and XP methodology. 0 Points No genuine attempt made. Name Description Rubric Detail  H el p 8/12/2021 ISYS3001-2021-2 Managing Software Development https://learn.scu.edu.au/webapps/rubric/do/course/manageRubrics?dispatch=view&context=course&rubricId=_10486_1&course_id=_145827_1 2/3   Levels of Achievement Criteria Excellent Good Partially Satisfactory Unsatisfactory Part 1-4 Guidelines for choosing Scrum or XP according to types of projects 3.5 Points Clearly identi�ed guidelines appropriate for choosing Scrum or XP according to types of projects. 2.5 Points Identi�ed some guidelines appropriate for choosing Scrum or XP according to types of projects but with missing information or lack of research. 1.75 Points Made a genuine attempt but with signi�cant amounts of information missing. 0 Points No genuine attempt made. Part 1-5 Another well-known process as candidate of adoption of new process for the second stage 1 Points A detailed explanation of another well- known process as candidate of adoption across the organisation. Clearly explained and justi�ed why. 0.75 Points An explanation of another well-known process as candidate of adoption across the organisation. Did not clearly explain and justify why. 0.5 Points Made an attempt but with signi�cant information missing. 0 Points No genuine attempt made. Part 2 XML 5 Points Used (or justi�ed editing) ALL tags required and provided an explanation for the comments. 3.75 Points Used all tags but with missing information and/or did not provide an explanation on the comments. 2.5 Points Made an attempt to use the tags required but