Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due
CPT202 Software Engineering Group Project
Assignment 3 – Project Individual Report
|
Start date |
24th Feb 2025 |
|
Due date |
18th May 2025 |
|
Assignment type |
Individual assignment |
|
Percentage in final marks |
50% |
|
Late submission policy |
5% of the awarded marks shall be deducted for each working day after the submission date, up to a maximum of five working days. Late submissions for more than five working days will not be accepted. |
|
Important notes |
• Plagiarism results in the award of a ZERO mark; all submissions will be checked by Turnitin.
• The formal procedure for submitting coursework at XJTLU is strictly followed. Submission link on Learning Mall will be provided in due course. The submission timestamp on Learning Mall will be used to check late submissions.
|
Learning Outcome
- A. Work as part of a development team demonstrating effective communication and interpersonal skills to design and develop a software system.
- B. Demonstrate an understanding of the software development process including the principal methods and issues involved in deploying systems to meet business goals.
- D. Understand the role of properly written documentation in the process of software development.
- E. Recognize the legal, social, ethical, and professional issues involved in the development and deployment of a software system.
General instruction
The report must be in the format given in Individual Report Template, which is provided in the Assignment Package. It is important to note that the report must be at most 8 pages, excluding the following: (1) the cover page that has the student ID, (2) the page Table of Content, (3) references, and (4) appendixes. The appendixes may include examples of PBIs, UML, Entity-relationship diagram (ERD), screenshots of the products, and/or (part of) source code, etc.
The software solution that you have designed and implemented must be accessible from the URL pre-allocated to your team. The URL must be made clear on the cover page of the report. For verification purposes, the software from the URL must remain unchanged for 4 weeks after the submission of the presentation.The marking criteria and the weighting are based on the following factors: -
The report should be well presented, ensuring that the language used is clear, concise, and free from ambiguity. Utilize visual aids such as images, diagrams, and charts to enhance comprehension where appropriate. Ensure that all visual elements are properly labelled and referenced within the text.
The understanding of how Scrum facilitates the software development process and effective communication should be well discussed. The discussion should revolve around the parts you did (e.g., use a specific example from your own parts).
The general design and implementation of all the PBIs that you have individually developed should be presented generally. Provide a clear justification for these designs and implementations. Use UML diagrams to support your illustrations.
A detailed discussion on 2 essential PBI(s) that you have contributed should be provided in terms of the following aspects:
a. Logical flow: you could present and discuss an activity/sequence diagram.b. Database: discuss how the database design supports the PBI.c. States of the objects involved. Discuss how the state changes and affects the objects' behaviors.d. UI. Discuss how the UI design helps deliver the PBI.
4. Change Management (15%):
5. Legal, social, ethical, and professional issues (15%)
Discuss where you have considered or the project has been influenced by legal, social, ethical, and professional issues. Provide the possible solutions to these issues. The discussion should revolve around the project you do (e.g., use a specific example from your own project). If the parts you did do not involve such issues, you should consider this part from the view of the whole project.
Clearly illustrate the lessons you have learned from this project. Also, provide the improvements that can be made in the future from your perspective.