Overview of Software Engineering (MN507Assignment-2) Assignment Help
Assessment Details and Submission Guidelines
Trimester
T2 2024
Unit Code
MN507
Unit Title
Overview of Software Engineering
Assessment Type
Assignment 2-Group Report
Assessment Title
Group Assignment – Design and development of MIT’s Alumni portal
Purpose of the assessment (with ULO Mapping)
This assignment assesses the basic concepts of professional ethics in IT and maps with the following ULOs:
• Understand software engineering principles and design software processes for business requirements.
• Understand agile software development practices and analysis, design, implementation and testing in the context of an agile framework • Compare and contrast different Software Engineering process models: waterfall, evolutionary, spiral, prototyping and others.
• Analyze business problems and elicit user requirements using software engineering methodologies.
• Use appropriate modeling techniques to model business requirements and data requirements.
• Capable of developing architectural designs for software systems and understanding the different architectural design patterns.
• Capable of designing and construction of user interfaces. • Software Engineering, specifically related to object-oriented software engineering.
• Produce a software system plan and framework including implementation, deployment, testing, maintenance, and evolution
Weight
20%
Total Marks
100 Marks
Word limit
2,000-2,500 Words or above
Due Date
Friday, 27/09/2024 (Week 11)
Submission
Guidelines
• Generative AI (GenAI) tools may be used with prior permission Students may use GenAI for this formative assessment with prior approval for understanding, learning and research purposes only. Using these tools to write assignments will be considered as academic misconduct and be penalized. If students are using any of the information from GenAI, then he/she must cite the use of Gen AI in their assessment.
More information of using GenAI can be found via the following link:
• All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page.
• The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2.54 cm margins on all four sides of your page with
appropriate section headings.
• Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using IEEE referencing style.
Extension
• If an extension of time to submit work is required, a Special Consideration Application must be submitted directly on AMS. You must submit this application three working days prior to the due date of the assignment. Further information is available at:
Academic
Misconduct
• Academic Misconduct is a serious offense. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: For further information, please refer to the Academic Integrity Section in your Unit Description.
Assignment Description
This group assignment is the continuation of Assessment 1 case scenarios, MIT’s Alumni portal project. Students should form groups of three or four members for this assignment. The purpose of this assignment is to analyze, design and implement (coding, building, and testing) the project.
MIT would like your group writing up a report, which contains the following activities for designing and developing the Alumni portal:
1. Product Roadmap to outline a general timeframe (e.g., Gantt Chart) for when your group will design, develop, and release identified requirements from Assessment 1.
2. The SRS document (a sample template in Moodle) which contains the following design elements (using UML notations):
Identify and draw a use case diagram(s) for MIT’s Alumni portal
ER diagram with all possible entities and attributes
State chart diagram(s)
Sequence diagram(s)
Class diagram for the entire system with all the attributes, methods, and associations.
3. The design document must include layered architecture and implement using the tools and platform of your choice, a software application with a front-end GUI, middle layer implementing the business logic and backend database.
4. Your group also requires designing a test specification (test cases) based on the project requirements and implementing (verification) them with evidence.
The report contents should include the following headings:
a. Cover page and your group details
b. Executive Summary (state system overview, system users, and system usability) c. Table of Contents
d. Introduction
e. Discussions (expand and explain your group’s supportive arguments)
f. Conclusion and recommendations
g. References and appendices
References
Must consider at least eight references (with at least five current references – not earlier than 2020). Must follow the IEEE referencing style.
Assignment Instructions:
• Do not use Wikipedia as a source or a reference.
• Make sure you properly reference.
Marking Guide for Assignment 1
Description
Weight
Introduction
8
Product roadmap (Gantt Chart)
10
Use Case Diagram (at least 8 use cases)
8
ER diagram
8
State chart diagram(s)
8
Sequence Diagram
8
Class Diagram
8
System Architecture (Layered based)
8
GUI Portal
10
Requirement Verification and Validation
15
Conclusion & Recommendation
4
References and Appendices
5
Total
100