Close Button
Signup/Login
Back All services Close Button

World's Leading Assignment Library

Continued assistance through writing and revision till final submission by the professional and experienced writers.

  • 10 subjects

  • 2,10,1000
    solved Questions

  • 500 Solved Questions
    Added Everyday

  • Download Solution
    in Seconds

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 p

Question Preview:

 

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:

  1. Practical Evidence View complete question »

Question Preview:

 

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:

  1. 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 Project project(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 not currently doing Team Project, you must propose an individual software development project in lieu of a Team Project project and get it approved.  This may be a programming project from another module or a project of your own.  It must be approved by the Software Engineering module leader and, if it is a programming project from another module, it must also be approved by the other module’s leader.

  1. 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.

  1. 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 university generally 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 this portfolio, including the essay component, as you 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.

 

 

View less »

Solution preview

Physical Evidence
Naming Conventions
Java follows camel case naming for its classes, packages and variables(Principles of Programming). In java, package name should be in small case, should begin with “com.” and should have no separating character. We have named the package “com.teamproject5.univent” adhering to the naming conventions for java package.

Get solution

java assignment help

© Livewebtutors. All Rights Reserved 2018

Livewebtutors
Rated 4.9/5 based on 2480 reviews
Arrow up