Task You will produce an electronic portfolio (i.e., an organised collection of digital files) to illustrate what you believe – based on research and experience – to be “good” software engineering practice. It will consist of a table of contents, plus the following two major sections and bibliography: Practical Evidence This section will consist of samples of annotated and commented source code – plus other project-related documentation – that you have personally developed for your Team Projectproject(s), which demonstrates your application of what you believe to be “good” software engineering practice, or which demonstrates violation of what you believe to be “good” software engineering practice. Where appropriate, use citations to back up what you consider to be “good” software engineering practices. You should organise your practical evidence in a sensible manner that makes it easy to read. For example, you might divide it into subsections, where the subsection headings are based on (but not necessarily limited to) the weekly lecture topic areas. Note 1: Source code included in this section of your portfolio should have clear and explicit identification of how it demonstrates “good” software engineering practices or how it violates “good” software engineering practices. Do not force the reader to guess. You may include examples of other team members’ code, but you must identify them as such and you must provide a critique of them. Note 2: If you are notcurrently doing Team Project, you mustpropose an individual software development project in lieu of a Team Projectproject and get it approved. This may be a programming project from another module or a project of your own. It mustbe approved by the Software Engineeringmodule leader and, if it is a programming project from another module, it must also be approved by the other module’s leader. Essay A properly referenced, critical essay that (a) describes and strongly defends your definition of “good software engineering practices”, and (b) describes and critiques how you have applied this definition to the development of your project(s). In particular, part (b) should be a critical summary of your collected practical evidence (above), plus discussion and critique of other activities (e.g., pair programming, feature-driven development) that do not necessarily result in code or documentation but may be directly related to software engineering. The word count should be approximately 2,000 to 3,500 words. Bibliography Each citation in your practical evidence and essay should refer to an entry in your bibliography. You are encouraged to use Harvard referencing style because the universitygenerally prefers it, but this is not a requirement as long as you use a recognised and consistent style of citing and referencing. You are expected to construct thisportfolio, including the essay component, asyou develop your Team Project (or other approved) project(s). Do not leave it to the end. The Monday workshop sessions can be used to provide formative feedback on your portfolio as you go along.
The post Task You will produce an electronic portfolio (i.e., an organised collection of digital files) to illustrate what you believe – based on research and experience appeared first on Homework Aider.
What Students Are Saying About Us
.......... Customer ID: 12*** | Rating: ⭐⭐⭐⭐⭐"Honestly, I was afraid to send my paper to you, but you proved you are a trustworthy service. My essay was done in less than a day, and I received a brilliant piece. I didn’t even believe it was my essay at first 🙂 Great job, thank you!"
.......... Customer ID: 11***| Rating: ⭐⭐⭐⭐⭐
"This company is the best there is. They saved me so many times, I cannot even keep count. Now I recommend it to all my friends, and none of them have complained about it. The writers here are excellent."
"Order a custom Paper on Similar Assignment at essayfount.com! No Plagiarism! Enjoy 20% Discount!"
