Reference no: EM133852276

SOFTWARE ENGINEERING

Assessment Item 1: 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.

Selection of the Topic

The relevant topic was chosen

Content

The overview of the paper discussed and intent Quality and clarity of the research problem statement and research question(s)

Significance and originality of the research contribution

Adequacy and coherence of the research methodology

Appropriateness and relevance of the literature review

Soundness and completeness of the research findings and conclusions

Organization and Delivery

Logical and well-structured presentation

Effective and engaging oral delivery

Clear and concise slides with appropriate visuals

References

The references and citations are provided

The references and citations are correct

The references and citations are appropriate

Assessment Item 2:

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

Title Page
Table of Contents
Introduction
System Overview
Requirement Specifications
Functional Requirements
Non-functional Requirements
Others
User Interfaces
System Interfaces
Assumptions / Constraints
References
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:
CASE STUDY - Fashion e-commerce 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.

Report Layout and Formatting:

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

Report Content:

Report should have clear introduction.
Clear introduction of system descriptions and software development lifecycle with proper justifications

Clear depiction of requirement specifications (functional, non-functional etc)
Assumptions or Constraints are appropriate and makes sense
Software analysis and modelling using use case diagrams. The diagram should be syntactically and semantically correct

Assessment Item 3

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

PART B - Software Testing Report

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

PART C - Presentation

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:

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

Task 2: Architecture
Appropriate Architectural Pattern is applied in design and the code.

Architectural Pattern is correctly justified.

Task 3: 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.