principles of software engineering

profileSuperClass
 (Not rated)
 (Not rated)
Chat

This is a Template please make a copy before using.

 

Please note that file name and page numbers are automatically printed in the footer please do not alter in anyway.

 

ITECH3501-6501 – Individual Assignment.

Principles of Software Engineering

School of Science, Information Technology and Engineering (SITE)

 

Objective: 

The purpose of this assignment is to enable students to demonstrate their ability to interpret a set of laws that are part of the principles of software engineering, to evaluate principles of software engineering aspects within an industry in relation to the various elements covered, to apply them to a cases drawn from technical and academic literature and to communicate the key issues through a written academic report.

Individual Assignment

Weighting and Due Date: Refer to Course Description on Moodle

Description of assignment:

The Laws of Software Engineering.

Consider the following four laws given in the prescribed text:

Curtis

Good design requires deep application domain knowledge. (L5)

Simon

Hierarchical structures reduce complexity. (L6)

Denert

Separation of concerns leads to standard architectures. (L9)

DeRemer

What applies to small systems does not apply to large ones. (LI6)

 

 

 

 

 

  1. Describe each law in your own words. Define the terms in each law and explain the law clearly and thoroughly.  Illustrate your explanation with practical examples – with at least one example for each law from software engineering.

 

  1. The following diagram is from the text. Cleary and thoroughly explain the relationship between observations, laws and theories.  Illustrate your answer with examples – with at least one from software engineering.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  1. ITECH6501 Additional Item

 

 

The following diagram appears in the text.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In your own words clearly and thoroughly explain the relationship between Laws, Methods and Tools. Illustrate your answer with examples – at least one of which is from software engineering.

 

 

 

Your support material must be compiled from reliable sources such as the academic resources in Federation University library which might include, but not limited to: the main library collection, library databases and the BONUS+ collection as well as any reputable online resources (you should confirm this with your tutor).

Plagiarism

It is important to learn from the work of others and you are encouraged to explore the library, World Wide Web resources and have discussions with other students.  However, work for the assessment must be entirely your own work.

*Important*

Plagiarism is the presentation of the expressed thought or work of another person as though it is one's own without properly acknowledging that person.

You must not allow other students to copy your work and must take care to safeguard against this happening.  In cases of copying, normally all students involved will be penalised equally; an exception will be if you can demonstrate the work is your own and you took reasonable care to safeguard against copying.

Plagiarism is a serious offence.  As set out in the University Regulation 6.1.1. students who are caught plagiarising will, for a first offence, be given a zero mark for that task.  A second offence will result in a failing grade for the course involved and any subsequent offence will be referred to the Student Discipline Committee.

Federation University General Guide to Referencing:

 

The University has published a style guide to help students correctly reference and cite information they use in assignments. A copy of the University’s citation guides can be found on the university’s web site. It is imperative that students cite all sources of information.  The General Guide to Referencing can be purchased from the University bookshop or accessed online at:

http://federation.edu.au/__data/assets/pdf_file/0015/164121/FedUni-General-Guide-to-Referencing-2014.pdf

Submission requirements

You will be required to submit your report via Turnitin prior to submitting a final version on Moodle.

It is important that there are no issues with Turnitin before you submit your final report on Moodle – you must provide evidence of this.

Refer to the preventing plagiarism page on the University website:

http://federation.edu.au/students/assistance-support-and-services/academic-support/learning-and-study/preventing-plagiarism

For more information about Turnitin:

http://federation.edu.au/students/assistance-support-and-services/academic-support/learning-and-study/preventing-plagiarism/about-turnitin


Marking Guide

ITECH350-6501     Principles of Software Engineering

Item

Essential Points to Cover

Mark

 

1.    Cover Page

 

 

Course Name & Number, Student Name, Student ID, Tutor’s Name

5

 

2.    Abstract

 

Not more than 250 words.

10

3.    Curtis

Good design requires deep application domain knowledge. (L5)

What is good design? What is deep application knowledge?

10

4.    Simon

Hierarchical structures reduce complexity. (L6)

What is complexity? How is it measured?

10

5.    Denert

Separation of concerns leads to standard architectures. (L9)

What are concerns? How are concerns separated? What is a standard architecture?

10

6.    DeRemer

What applies to small systems does not apply to large ones. (LI6)

What is meant by small? What is a large system? Other than size, in what ways are they different?

10

7.    Observations, Laws & Theories

What is a law?

10

 

8.    References

Both inline and full references. (APA)

10

9.    Presentation of report

Spelling, Grammar and Layout

10

TOTAL

/80

ITECH6501 Additional Item

What is a method? What are some tools in software engineering?

/20

TOTAL

/100

FINAL MARK

/10

    

 

 

    • 8 years ago
    principles of software engineering A+ Tutorial use as Guide
    NOT RATED

    Purchase the answer to view it

    blurred-text
    • attachment
      principles_of_software_engineering.docx