CS 415: Software Engineering [100 POINTS]

FINAL PROJECT (Friday, 20th October 2023)

Instructions
You are supposed to submit your work (i.e., documentation – technical report, and software
system) by 11:55pm on Friday 15th December 2023. You have eight (8) weeks to complete
this project. Form teams of four members. Project milestones should be submitted to the
provided deadlines but in the same document (i.e., an IEEE format).
Honour Code applies! Do not use any assistance from human or AI agent.

FINAL PROJECT DESCRIPTION

- IEEE conference paper format (MS Word, Latex, Overleaf): IEEE - Manuscript Templates
for Conference Proceedings
- Typical research paper structure: Abstract, Introduction, Related Work, System
Requirements, System Design, System Implementation, System Results (Testing),
Conclusion and Future Work. Also, refer to Section D.

A. [5 points] Project Details

Section - ABSTRACT
Milestone (20/10/2023 to 24/10/2023)
Choose a project that you can justify. Prepare a project description document section which should
include [1 point] the project title, team name, team members, a [2 points] brief description of the
project, and [2 points] justify your software engineering methodology (i.e., plan-driven - waterfall,
incremental - agile-driven, integration and configuration - reuse-oriented, hybrid).
Complete this form by 6:00p.m. Friday 20/10/2023: To Be Disclosed

IEEE SCIENTIFIC (CSIS) RESEARCH PAPER

B. [15 points] Justification/Motivation Milestone (25/10/2023 to 31/10/2023)
Section – INTRODUCTION & RELATED WORK
The aim behind the project should be highlighted and justified. To justify your project, you must:
- [8 points] identify at least five related works (i.e., at least three research papers published
in IEEE or ACM, and at least two notable software system),
- [5 points] you may need to conduct user needs assessment where you design data
collection instruments like surveys or interview question to better understand what your
users and stakeholders need in this project, and
- [2 points] discuss the challenges of the chosen related work.
Scientific Writing:
- Provide the state-of-the-art context/domain of the project, challenges of current solutions,
and then your informed idea of a solution.
 - NB: When referring to scientific publications (i.e., IEEE, ACM), look at how the research
papers are structured and worded, and present your technical report in a similar manner.
Be reminded that technical reports are very different from reflective report. (Refer to IEEE
publications shared with you on CANVAS or WhatsApp group).
- Use good Computer Science referencing practices. You are expected to use ACM referencing
style.

C. [70 points*] Software Engineering Cycle Milestone (01/11/2023 to 15/12/2023)

This part of the project should illustrate the different software processes used during the project.
Note that this should be as concise and intuitive as possible. The following processes should guide
you.
i. [15 points] Requirement Specifications Milestone (01/11/2023 to 07/11/2023)
Section – SYSTEM REQUIREMENTS
This involves a requirements elicitation process that requires talking to stakeholders to better
understand the expectations of the software system. We expect that you showcase this process by
talking about your [8 points] research insights (from research, related systems, user needs:
interviews and surveys) and the [7 points] decisions you made as a group with regards to the user
stories, functional and non-functional requirements (including constraints).
CAPSTONE STANDARD: Uses an appropriate procedure for requirements gathering. Clearly
outlines the procedure for requirements gathering and analysis. Clearly identifies users. Describes
appropriate use cases. Clearly enumerates detailed requirements. Clearly specifies the set of
requirements that would be addressed in this project. Requirements analysis is complete and of
high quality.

ii. [15 points] Analysis and Design Milestone (08/11/2023 to 18/10/2023)

Section – SYSTEM DESIGN
A high-level representation of your solution should be designed. Utilize Figma and UML diagrams
(i.e., Use Case, Sequence, Activity, Object/Class, Architectural Design, etc.) to give prospective users
and stakeholders an overview of what the system does. You can illustrate this using at least [12
points] twelve design diagrams. Here, each team member should design at least three diagrams.
Description of analysis and design [3 point].
CAPSTONE STANDARD: - Presents high level systems overview and architecture. Identifies key
modules and layers in the implementation. Documents each module's design. Clear mapping of
design to requirements analysis. Schematics as needed.

iii. [25 points*] Implementation Milestone (19/11/2023 to 12/12/2023)

Section – SYSTEM IMPLEMENTATION

This involves your implementation of the application where you will want to show the most
important parts of your application, i.e., functionalities that give value to your application. Make
sure you highlight the technologies used during the development process and justify your choices.
Your project can be a desktop application (i.e., Java, Python, etc.), web application (i.e., Bootstrap,
HTML5, JavaScript, PHP, etc.), mobile application (i.e., Android Studio – Java, Flutter, etc.),
embedded systems (i.e., IoT with microprocessors), etc.
Software function: [15 points]
Comments: [2 points]
Technology & Justification: [8 points]
NB: Use GitHub repository for your project development. You need to submit the link to your
project.
CAPSTONE STANDARD: Provides high level description of implementation including tools,
libraries, frameworks, APIs, components, etc.- Description shows understanding of all components
utilized. Describe implementation techniques. Provide evidence of implementation (e.g.,
screenshots of implemented software interfaces, chip layouts, photos of assembled hardware
system, etc.). Has a well-implemented, high quality, working prototype.

iv. [5 points] Verification and Validation (Milestone: 15/12/2022)

Section – SYSTEM VERIFICATION AND VALIDATION

Here, you must show how robust your application is, especially how it handles errors and bad
inputs from users. This illustrates your testing process [5 points] and how your requirements meet
your client’s expectations of the software system. Here, a clear set of test cases should be provided
and assessed/justified as to whether the tests were successful or not. For example, use JUnit for
Java-based project and Selenium for web-based projects. If these two testing tools do not apply to
your project, identify, and apply any relevant testing tools for your project.
CAPSTONE STANDARD: Describes appropriate type of testing to verify satisfaction of functional
requirements. Presents test results. As needed: Describes and provides results of component
testing, Describes, and provides results of component testing, Describes, and provides results of
system-level testing, Describes and provides results of user testing, and Analysis of test results
(including explanation of things that are not working).

v. [5 points] Product Installation/Deployment (Milestone: 15/12/2023)

Section – SYSTEM INSTALLATION AND DEPLOYMENT

This stage involves the setting up of the completed software system for the intended users. For
web-based systems, the software will have to be deployed or hosted on a web server [5 points].

vi. [5 points] Evolution/Future Work (Milestone: 15/12/2023)

Section – FUTURE WORK

Indicate what you tend to do next as a group with regards to the project. This could be based on
the [2 point] challenges of your current system, or potential feature extensions. It could be [3
point] new functionalities that will solve different problems.
 D. [Final Submission Document] IEEE Scientific Writing Milestone (20/10/2023 -
15/12/2023)
Page limit: Seven to ten pages
Structure:
Abstract: Motivate your research by highlighting the state-of-the-art of your research area, identify
research gaps (or problems), propose a solution and highlight key technologies or approaches, and
briefly present relevant results of testing.
Introduction: Research Motivation and Literature review (Related Work), proposed solution
Methodology: Approach to requirements elicitation and results, SDLC approach with justification
System Architecture and Implementation: Scenarios/User stories, UML diagrams and
implementation technologies
System Validation: Testing (Unit to Acceptance).
Conclusion and Future Work: Summarize your research and identify areas that need
improvements. Add new features that can be considered to evolve your research.
References
Appendix
NB: When referring to scientific publications (i.e., IEEE, ACM), look at how the research papers are
structured and worded, and present your final technical report in a similar manner. Be reminded
that technical reports are very different from reflective reports. (Refer to IEEE publications on
CANVAS)
IEEE Conference Paper Template:
https://www.ieee.org/conferences/publishing/templates.html
1. Microsoft Word →A4 →(Doc 30KB)
2. LaTeX Template Instructions
3. Overleaf
CAPSTONE STANDARD:

CONCLUSIONS AND RECOMMENDATIONS (Section 6)

Summary of degree to which project meets functional requirements
Points out limitations of the work or possible flaws in its design
Suggests directions for future development
Logical conclusion
APPENDICES
Provides a well-structured project-management Gantt chart
Provides a well-structured API documentation and/or a system or
user manual, if needed (optional)
Provides further low-level details of requirements analysis, design,
implementation, etc. where needed
Has results of further testing as needed
PROFESSIONAL ETHOS AND COMMUNICATION SKILLS
Follows manuscript design specifications
Is well-organized, concise, adequately developed, and clear
 Is well-edited without errors in grammar or spelling
Shows strong "ethos"-gives readers a favorable impression of the
writer's professionalism and communication skills,

E. [10 points] Presentation/Demonstration Milestone (17&18/12/2023)

Prepare a presentation for Monday 17 and Tuesday 18 December (8:00 a.m./9:30 a.m. –
th th

11:15 a.m./12:45 p.m.). Structure your presentation in line with the section provided above (i.e.,
from Section D). Take note that the shared set of requirements for individual team members
should guide the presentations or demonstrations. The order of presentation or demonstration
will be provided by/on 15th December 2023.
NB: The presentation/demonstration will be organised in-person and on the course’s ZOOM (CSIS
invitation link) during the mentioned days and times. Each group will have 12 minutes for your
presentation and demonstration, so each member will have at least 10 minutes to talk about their
contributions. ‘Questions and Answers’ will be 2 minutes for each team. Hence, each team will
have 12 minutes for presentation and Q&A.

All the best!