Reference no: EM133867774

SOFTWARE ENGINEERING

Assessment:

PART A - Software Design Specification Report

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.

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:
Objective
Scope
Test Type
Test Environment
Test Schedule
Roles and Responsibilities
Test Deliverables
Risk and Mitigation

Assignment PART - Presentation

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

For part A

Task 1: Class Diagram

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
Appropriate Architectural Pattern is applied in design and the code.

Architectural Pattern is correctly justified.

Task3: Implementation
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
- The test plan is comprehensive, well-structured, and covers all critical aspects.

For part C
Task 1: System Demonstrations / Presentation
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.