ICT602 Software Engineering Assignment Help

ICT602 Software Engineering Assessment Help

 

Assessment Overview

Assessment tasksLearning Outcome Mapping
Assessment IDAssessment ItemWhen dueWeightingULO#CLO# for MITSCLO# for GDITS

 

1

ResearchReport (Individual)

 

Session 4

 

20%

 

1, 2

  

 

 

2

 

SoftwareRequirements Specification Report (Group) (1,500 words)

 

 

Session 6

 

 

30%

 

 

1, 2

 

 

1, 2

 

 

1, 2

 Part A - Software     
 Design     
 Specification ReportPart A - Session10Part A - 30%   
3*Part B – TestPlan Part C –Part B – Session11 Part C - Session 12

 

 

Part B – 10% Part C - 10%

3, 4, 51, 2, 3, 4

1, 2, 3,

4

 Presentation(Group)     


 

Referencing guides

You must reference all the sources of information you have used in your assessments. Please use the IEEE referencing style when referencing in your assessments in this unit. Refer to the library’s referencing guides for more information.

 

  • https://elearning.vit.edu.au/pluginfile.php/473840/block_html/content/VIT%20Library%20Refer encing%20-%20IEEE%20-%2007042020.pdf

 

Academic misconduct

VIT enforces that the integrity of its students’ academic studies follows an acceptable level of excellence. VIT will adhere to its VIT Policies, Procedures and Forms where it explains the importance of staff and student honesty in relation to academic work. It outlines the kinds of behaviours that are "academic misconduct", including plagiarism.

 

Late submissions

In cases where there are no accepted mitigating circumstances as determined through VIT Policies, Procedures and Forms, late submission of assessments will lead automatically to the imposition of a penalty. Penalties will be applied as soon as the deadline is reached.

 

Short extensions and special consideration Special Consideration is a request for:

 

  • Extensions of the due date for an assessment, other than an examination (e.g. assignment extension).
  • Special Consideration (Special Consideration in relation to a Completed assessment, including an end-of-unit Examination).

Students wishing to request Special Consideration in relation to an assessment the due date of which has not yet passed must engage in written emails to the teaching team to Request for Special Consideration as early as possible and prior to start time of the assessment due date, along with any accompanying documents, such as medical certificates.

For more information, visit VIT Policies, Procedures and Forms.

 

Inclusive and equitable assessment

Reasonable adjustment in assessment methods will be made to accommodate students with a documented disability or impairment. Contact the unit teaching team for more information.

 

Contract Cheating

Contract cheating usually involves the purchase of an assignment or piece of research from another party. This may be facilitated by a fellow student, friend or purchased on a website. Other forms of contract cheating include paying another person to sit an exam in the student's place.

 

 

Contract cheating warning:

 

  • By paying someone else to complete your academic work, you don’t learn as much as you could have if you did the work yourself.
  • You are not prepared for the demands of your future employment.
  • You could be found guilty of academic misconduct.
  • Many of for pay contract cheating companies recycle assignments despite guarantees of “original, plagiarism-free work” so similarity is easily detected by TurnitIn.
  • Penalties for academic misconduct include suspension and exclusion.
  • Students in some disciplines are required to disclose any findings of guilt for academic misconduct before being accepted into certain professions (e.g., law).
  • You might disclose your personal and financial information in an unsafe way, leaving yourself open to many risks including possible identity theft.
  • You also leave yourself open to blackmail - if you pay someone else to do an assignment for you, they know you have engaged in fraudulent behaviour and can always blackmail you.

 

Grades

We determine your grades to the following Grading Scheme:

 

 

 

GradePercentage
A80% – 100%
B70% – 79%
C60% – 69%
D50% – 59%
F0% – 49%

 

 

Assessment Details for Assessment Item 1:

Overview

 

 

AssessmenttasksLearning
Assessmen  t IDAssessment ItemWhen dueWeightingULO#

 

1

Research Report (Individual)

 

Session 4

 

20%

 

1, 2

 

 

ASSESSMENT ITEM 1:

 

This assessment requires you to research and prepare a report on contemporary software development processes used.

 

Assignment 1

This assignment will be completed individually.

Marks: 20% of your total marks/grades. Due Date: Session 4

Submission: The report must be submitted through the Moodle submission link provided under the assessments on Unit page before the deadline.

Lateness: A late penalty of 20% per day after the due date, including the weekends.

 

Authorship: This assignment is an individual assignment, and the final submission must be identifiable as an individual’s own work. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in disciplinary action. Refer to the Academic Integrity Section below for more details.

Extensions: No extensions will be given in normal circumstances. An extension may be granted in special circumstances as per the VIT policy.

Student Statement: A completed electronic student statement is required to be accepted with the submission. It is created automatically when you press a Submit button (or confirm your submission) for your assignment via Moodle submission system.

ACADEMIC INTEGRITY & PLAGIARISM (STANDARD WARNING):

 

Academic integrity is about the honest presentation of your academic work. It means acknowledging the work of others while developing your own insights, knowledge and ideas. You should take extreme care that you have:

  • Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,
  • Provide a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate references, as if they were your own.

 

INSTRUCTIONS:

 

In this assessment you are required to write report on a recent academic paper on a topic related to Software Engineering or related Software Engineering field (e.g., methodologies, analysis, design, testing, quality, etc.). Some possible research areas are included but were not limited to:

  • Mining Software Repositories
  • Search-based Software Engineering
  • Quantum Software Engineering
  • Project Management methodologies
  • Test Driven Methodologies
  • Advanced human Interfaces
  • Artificial Neural Networks (applied to software engineering)
  • Cloud Computing (in relation to software engineering)
  • Agent Oriented Software Engineering

 

  • Automated Software Engineering

 

 

The selected paper must be directly relevant to one of the above topics or another topic that is related to Software Engineering. The paper can be from Scopus Level Q1, Q2 and Q3 academic conferences or other relevant Journal or online sources such as ProQuest, Google Scholar, Academic department repositories, or a significant commercial company involved in research such as IBM etc. All students must select a different paper and send it for approval (or discuss with) to the tutor/lecturer by end second week. Thus, the paper must be approved by your lecturer before proceeding. In case two student select same paper, the first come first serve policy will be applied. Note that popular magazine or web-site articles are not academic papers. Some suggested periodicals for this assessment are as follows.

 

 

 

 

  
 

 

The mark for Assessment 1 is 20% of the overall Unit’s marks. The marks include both your report content and the report structure. A marking guide/scheme for your presentation is attached herewith.

Marking Criteria/Rubric

You will be assessed on the following marking criteria/Rubric:

 

Selection of the Topic (5 Marks)

 

  • The relevant topic was chosen (5 marks)

 

Content (50 marks)

 

  • The overview of the paper discussed and intent Quality and clarity of the research problem statement and research question(s) (10 marks)
  • Significance and originality of the research contribution (10 marks)

 

  • Adequacy and coherence of the research methodology (10 marks)

 

  • Appropriateness and relevance of the literature review (10 marks)

 

  • Soundness and completeness of the research findings and conclusions (10 marks)

 

Organization and Delivery (10 points)

 

  • Logical and well-structured report (10 marks)

 

References (15 points)

 

  • The references and citations are provided (5 Marks)

 

  • The references and citations are correct (5 Marks)

 

  • The references and citations are appropriate (5 Marks)

 

Assessment Details for Assessment Item 2:

 

Assessment tasksLearning OutcomeMapping
Assessment IDAssessment ItemWhen dueWeightingULO#CLO# for MITSCLO# for GDITS

 

 

 

2

Software Requirements Specification Report (Group) (1,500 words)

 

 

 

Session 6

 

 

 

30%

 

 

 

1, 2

 

 

 

1, 2

 

 

 

1, 2


 

Assignment 2

This assignment will be completed in groups. Marks: 30% of your total marks/grades.

Due Date: Session 6

 

Submission: The report of not excessing 1500 words must be submitted in the PDF format through the Moodle submission link for assignment 2. We shall check your report for plagiarism or similarly through Turnitin. No DRAFT submissions will be marked.

 

Lateness: A late penalty of 20% per day after the due date, including the weekends.

 

Authorship: This assignment is a group assignment; students are required to form a group of 4 for this assessment. The final submission must be identifiable as a group’s own work. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in disciplinary action. Refer to the Academic Integrity Section below for more details.

 

Extensions: No extensions will be given in normal circumstances. An extension may be granted in special circumstances as per the VIT policy.

 

Student Statement: A completed electronic student statement is required to be accepted with the submission. It is created automatically when you press when you upload the document (or confirm your submission) for your assignment via Moodle submission system.

 

ACADEMIC INTEGRITY & PLAGIARISM (STANDARD WARNING):

Academic integrity is about the honest presentation of your academic work. It means acknowledging the work of others while developing your own insights, knowledge and ideas. You should take extreme care that you have:

 

Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,

Provide a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate references, as if they were your own.

 

INSTRUCTIONS:

In this assessment the students will work in groups assigned to submit a software specification document. The document must contain the following headings:

 

  1. Title Page
  2. Table of Contents
  3. Introduction
  4. System Overview
  5. Requirement Specifications
    1. Functional Requirements
    2. Non-functional Requirements
    3. Others
  6. User Interfaces
  7. System Interfaces
  8. Assumptions / Constraints
  9. References
  10. Contributions/WBA

 

Workplan / Work breakdown Agreement (WBA)

You are expected to work as a group on this assignment and contribute very closely to approximately an equal amount of work (unless the special consideration policy outlined applies). In your workplan you must provide details about the contributions and how the work is organised and managed. In most cases, if this is followed, students will receive equal marks on those aspects to their teammates. The Workplan section must include the following information:

 

Student Name:

 

Contribution Description:

 

%age of Contribution:

 

I [NAME OF THE STUDENT] hereby accept the Work breakdown/contribution as agreed. [DATE]

 

CASE STUDY – E-retail platform

You and your team have been tasked with developing a comprehensive e-retail platform. This platform must cater to a wide range of customers while delivering a seamless and engaging shopping experience. To achieve this, the platform should incorporate a variety of features, from basic product browsing and purchasing to advanced functionalities like personalized recommendations, dynamic pricing, and social media integration. The platform's interface should be visually appealing, user-friendly, and optimized for both desktop and mobile devices to maximize customer engagement.

 

In addition to customer-facing features, the platform must also provide robust tools for sellers and retailers. Efficient product management, real-time inventory tracking, and detailed sales analytics are essential for business success. The platform should seamlessly integrate with payment gateways, shipping carriers, and inventory management systems to ensure smooth operations.

To ensure the platform’s success, it must address non-functional requirements such as security, performance, scalability, and reliability. Protecting sensitive customer data (e.g., payment information and personal details) is critical, while the platform must be capable of handling high traffic volumes, especially during peak shopping seasons like holidays or sales events. Additionally, the platform should be scalable to accommodate future growth in product offerings and user base.

NOTE: As a developer your team should conduct client interviews to discuss the specifications in more detail. Utilise the consultation time for this task.

 

MARKING SCHEME / GUIDE

 

Please note that the Assessment will contribute towards 30of the final grade.

 

NOTE that no marks will be granted for wrong or incorrect submission of files

 

NOTE that one person in the group should submit the document. Group members are required to submit participation form. No participation form no mark.

Report Layout and Formatting:

 

  • Report should be of correct layout as mentioned ABOVE, containing unit code, unit name and student ids etc (4 marks)
  • Report should have VIT logo. (1 marks)
  • The document follows the correct formatting (5 Marks) Total Marks: 10 Marks

 

Report Content:

 

  • Report should have clear introduction. (5 marks)
  • Clear introduction of system descriptions and software development lifecycle with proper justifications (10 marks)
  • Clear depiction of requirement specifications (functional, non-functional etc) (25 marks)
  • Assumptions or Constraints are appropriate and makes sense (10 marks)
  • Software analysis and modelling using use case diagrams. The diagram should be syntactically and semantically correct (20 marks) Total Marks: 70 Marks

Grammar:

 

  • All use of spellings, punctuations and grammars should be correct. Total Marks: 5 marks

Word limit:

 

  • Word limit followed.

 

Total marks: 5 marks

 

 

References:

 

  • References should be valid, reliable and from credible sources.
  • References follows the correct format i.e. IEEE format.

 

Total Marks: 10 marks


 

Assessment Details for Assessment Item 3:

Overview

 

AssessmenttasksLearnin
Assessment IDAssessment ItemWhen dueWeightingULO#
 

 

 

Part A - Software Design Specification Report

 

 

 

 

 

 

Part B – Test Plan

Part C – Presentation (Group)

 

 

Part A - Session10

  
  Part A - 30% 
 Part B – SessionPart B – 10% 
 11  
3*Part C - Session12 3, 4, 5
  Part C - 10% 


 

Assignment 3 PART A - Software Design Specification Report

 

This assignment will be completed in groups.

Marks: 30of your total marks/grades. Due Date: Session 10

Submission: This assignment requires submitting the report and video demonstration as a separate submission through the Moodle submission link for assignment 3. No DRAFT submissions will be marked.

Lateness: A late penalty of 20% per day after the due date, including the weekends.

 

Authorship: This assignment is a group assignment, and the final submission must be identifiable as a group’s own work. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in disciplinary action. Refer to the Academic Integrity Section below for more details.

Extensions: No extensions will be given in normal circumstances. An extension may be granted in special circumstances as per the VIT policy.

Student Statement: A completed electronic student statement is required to be accepted with the submission. It is created automatically when you press when you upload the document (or confirm your submission) for your assignment via Moodle submission system.

ACADEMIC INTEGRITY & PLAGIARISM (STANDARD WARNING):

Academic integrity is about the honest presentation of your academic work. It means acknowledging the work of others while developing your own insights, knowledge and ideas. You should take extreme care that you have:

  • Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,
  • Provide a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate references, as if they were your own.

INSTRUCTIONS:

This assignment is an extension of assignment 2, that is the team is working on the same case study as in assignment 2, and creating the software design specification.


 

  • Based on the updated requirements draw a conceptual class diagram of the whole system showing all classes and relationships. You can add attributes and methods where necessary but it's optional, and you do not need to show all attributes and methods.

Hint: Show methods where inheritence or any solid principles are applied.

 

The diagram should adhere to all object-oriented principles and patterns covered in this unit and appropriate for the case study under discussion.

  • Define and discuss what architectural pattern should be used to design the fashion e-retail platform.
  • Students should discuss within the team and get confirmation from the staff member about the complex module they are implementing. Use Java programming language to develop it. You can use GIT or any other distributed version control system to track changes and access files remotely. However, it is optional and not accessed but recommended. Also, write instruction to run and deploy code on machines so that the teaching team can run it on their local machines.

Note: It is not mandatory to use GUI, a simple stand alone command line application is also acceptable as long as it shows the required functionalities.


 

Assignment 3 PART B - Software Testing Report

 

Marks: 10of your total marks/grades. Due Date: Session 11

Submission: This assignment requires submitting the report and video demonstration as a separate submission through the Moodle submission link for assignment 3. No DRAFT submissions will be marked.

Lateness: A late penalty of 20% per day after the due date, including the weekends.

 

Authorship: This assignment is a group assignment, and the final submission must be identifiable as a group’s own work. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in disciplinary action. Refer to the Academic Integrity Section below for more details.

Extensions: No extensions will be given in normal circumstances. An extension may be granted in special circumstances as per the VIT policy.

Student Statement: A completed electronic student statement is required to be accepted with the submission. It is created automatically when you press when you upload the document (or confirm your submission) for your assignment via Moodle submission system.

ACADEMIC INTEGRITY & PLAGIARISM (STANDARD WARNING):

Academic integrity is about the honest presentation of your academic work. It means acknowledging the work of others while developing your own insights, knowledge and ideas. You should take extreme care that you have:

  • Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,
  • Provide a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate references, as if they were your own.

Instruction

 

A test plan is a comprehensive document that outlines the strategy, objectives, resources, schedule, and scope of testing activities for the e-retail platform. The goal of the test plan is to ensure that the platform meets all functional and non-functional requirements, delivers a seamless


 

user experience, and is free of critical defects before deployment. Below is the format need to be followed:

  1. Objective
  2. Scope
  3. Test Type
  4. Test Environment
  5. Test Schedule
  6. Roles and Responsibilities
  7. Test Deliverables
  8. Risk and Mitigation

 

Important: Simply showing correct outputs will grant no marks.


 

Assignment 3 PART C - Presentation

Marks: 10of your total marks/grades. Due Date: Session 12

Submission: This assignment requires submitting the report and video demonstration as a separate submission through the Moodle submission link for assignment 3. No DRAFT submissions will be marked.

Lateness: A late penalty of 20% per day after the due date, including the weekends.

 

Authorship: This assignment is a group assignment, and the final submission must be identifiable as a group’s own work. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in disciplinary action. Refer to the Academic Integrity Section below for more details.

Extensions: No extensions will be given in normal circumstances. An extension may be granted in special circumstances as per the VIT policy.

Student Statement: A completed electronic student statement is required to be accepted with the submission. It is created automatically when you press when you upload the document (or confirm your submission) for your assignment via Moodle submission system.

ACADEMIC INTEGRITY & PLAGIARISM (STANDARD WARNING):

Academic integrity is about the honest presentation of your academic work. It means acknowledging the work of others while developing your own insights, knowledge and ideas. You should take extreme care that you have:

  • Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,
  • Provide a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate references, as if they were your own.

Instruction

 

  • The whole group should demonstrate the design and working of the application including the contribution. The video demonstration must follow the following protocols:
    • The whole group will be present in the video with face visible (Camera on). The whole group must introduce themselves and present their contributions. Then the team should discuss design, architecture and demonstrate the running of the system (VIT Eats Application).


 

  • The video must not exceed more than 10 minutes
  
 


 

 

 

Workplan / Work breakdown Agreement (WBA)

You are expected to work as a group on this assignment and contribute very closely to approximately an equal amount of work (unless the special consideration policy outlined applies). In your workplan you must provide details about the contributions and how the work is organised and managed. In most cases, if this is followed, students will receive equal marks on those aspects to their teammates. The Workplan section must include the following information:

Student Name:

 

Contribution Description:

 

%age of Contribution:

 

I [NAME OF THE STUDENT] hereby accept the Work breakdown/contribution as agreed. [DATE]

NOTE: We will take into account your WBA while marking your assessments and the marks will be adjusted based on the WBA.


 

MARKING SCHEME / GUIDE

 

The assessment will be marked on the following criteria

 

For part A

Task 1: Class Diagram (30 Marks)

 

  • Classes are well-chosen.

 

  • Important domain concepts are modelled.

 

  • Elements that are outside the scope of the specification are not modelled.

 

  • All elements that are shown are within the scope of the specification.

 

  • All relevant associations are shown.

 

  • Inheritance is used appropriately.

 

  • Aggregation/composition are used correctly (if at all).

 

  • All obvious associations and dependencies between classes are shown.

 

  • Navigability arrows on associations and dependencies make sense (if shown).

 

  • Syntax is correct

 

Task2: Architecture (10 Marks)

  • Appropriate Architectural Pattern is applied in design and the code.

 

  • Architectural Pattern is correctly justified.

 

Task3: Implementation (15 Marks)

  • Design in the code matches the design in the class diagram.

 

  • Coding standards. Applies to any code that has been touched by human hands (e.g. meaningful variable and method names, commenting, layout) -- note that this applies to both human-written code and machine-generated code that has been hand-edited. We will look for meaningful identifier names (variable, classes, methods), inline comments, method header comments, class/module comments, layout.
  • Functional Completeness (any complex module including login)

 

Part B

Task 1: Test Plan (10 marks)

-           The test plan is comprehensive, well-structured, and covers all critical aspects.


 

For part C

Task 1: System Demonstrations / Presentation (10 Marks)

  • Please start the video by discussing the contribution of each team member (i.e., which team member was responsible for which component in the system). Students should demonstrate a working system (the complex module) including the design, architecture and any other parts (if required).
  • Students demonstrate understanding of the system, the relationship between the code and the design documents, the design and the architecture of the system. Students should point out where in their code the constructs shown in their design documents are implemented.

“Achieve top grades with Punjab Assignment Help – expert guidance, plagiarism-free solutions, and on-time delivery for all your academic needs!”

Example invalid form file feedback

Join our 150К of happy users

Get original papers written according to your instructions and save time for what matters most.