Reference no: EM133773069
SOFTWARE ENGINEERING
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:
Automated Software Engineering
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
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.
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 of Report (30 points)
Logical and well-structured report (10 marks)
Effective and engaging points (10 marks)
Clear and concise discussion (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)
Assignment 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 employed to develop a fashion e-commerce platform.
A fashion e-commerce platform must cater to a diverse clientele while providing a seamless shopping experience. To achieve this, the platform should incorporate a broad spectrum of features, from basic product browsing and purchasing to advanced functionalities like personalized recommendations and social integration. The platform's interface should be visually appealing and intuitive, encouraging customer engagement.
Beyond the customer-centric aspects, the platform should also provide tools for sellers and brands. Efficient product management, inventory control, and sales analytics are crucial for business success. The integration of payment gateways, shipping carriers, and inventory management systems is another critical component.
To ensure the platform's success, it must address non-functional requirements such as security, performance, and scalability. Protecting sensitive customer data is paramount, while the platform must be able to handle fluctuations in traffic and product offerings.
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 (20 marks)
CASE STUDY - Fashion e-commerce platform
You and your team have been employed to develop a fashion e-commerce platform.
A fashion e-commerce platform must cater to a diverse clientele while providing a seamless shopping experience. To achieve this, the platform should incorporate a broad spectrum of features, from basic product browsing and purchasing to advanced functionalities like personalized recommendations and social integration. The platform's interface should be visually appealing and intuitive, encouraging customer engagement.
Beyond the customer-centric aspects, the platform should also provide tools for sellers and brands. Efficient product management, inventory control, and sales analytics are crucial for business success. The integration of payment gateways, shipping carriers, and inventory management systems is another critical component.
To ensure the platform's success, it must address non-functional requirements such as security, performance, and scalability. Protecting sensitive customer data is paramount, while the platform must be able to handle fluctuations in traffic and product offerings.
Workplan / Work breakdown Agreement
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:
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)
Task 4: System Demonstrations
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.