BT3103 - Mid-Term Project Guidelines
Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit
BT3103 - Mid-Term Project Guidelines:
Weightage: 25%
Project:
Identify a problem, gather requirements, and design an application.
Depending on your group’s interest, you can identify a problem from any domain (Finance, Healthcare, Retail, Project Management, etc.).
The application need not be an invention, but it should be able to solve a business problem. Profitable or nonprofitable, any will do. However, the focus should be on the Requirements and Design. Of course, you can take external references to motivate your idea but DO NOT copy from the internet.
You will be tested on the Problem Statement, Requirement Analysis, and Design.
Steps for the project:
1. Brainstorm within your team on several ideas and select the best idea.
2. For the best idea, document:
a. The problem statement
b. The goal of the project - User Benefits
c. Requirements:
i. Functional
ii. Non-Functional
3. Develop a prototype. You can use any tool. However, if you develop using HTML/CSS/JS, you can use the prototype for final project development.
Please note that the final project will be the ‘implementation’ of the mid-term project, so choose your project accordingly.
Since, ultimately, your team only has to develop this application going forward, I suggest picking an application/domain where all the group members are comfortable working instead of asking me, the TAs, or others.
Submission:
One pdf file only. NO word doc / No ppt / No Video
Attach screenshots of the prototype in the pdf file. NOT more than 25 pages, including everything.
Font = Times New Roman / Arial | Font size = 12 Margin = 1”
Deadline:
27th Feb 23:59.
Few additional points on the mid-term project.
1. The application can be from any domain (profit or non-profit); however, it should solve a problem.
2. You and your group have to develop this application further, so I am not the right person to comment if the application (finance, retail, or any other) is good or bad. Please discuss this within the group. Our focus is on the methodology of development and not on the complexity of the application.
3. Ultimately, you must use HTML+CSS+Vue +Firebase for the final project. You can use external libraries to make your work easier, like bootstrap, Vuetify, or others.
4. The complexity of the application depends on your selection. Assume you are thinking of developing a rocket science application with numerous features, but I know you can't develop all the features until week 13, and that's okay. Focus only on features that can be developed within this course period. I will see your efforts on how much work you have done and your quality.
5. For mid-terms. The grading is based on the quality of the problem statement, requirements, and designs. For example, if you have fewer requirements but are greatly written, you will get higher marks compared to more poorly written requirements. Ensure you have gone through the basics of Lectures 1 and 2 and write your requirements accordingly.
6. Although UI design can be very subjective, it doesn't mean you don't dig deep and use good CSS properties. A great-looking Interface with a good color selection and design match is always preferred over a random color selection. Also, a design should match the requirements. Remember that the design is made to fulfill the requirements.
7. The number of requirements entirely depends on your application and what problem you are trying to solve.
8. You can use fake/mock data in the absence of real data. Please mention that in the report. Also, make sure you don't download or use data that is not public and free to use.
Mid-term Rubrics:
S.N |
Criteria |
Rubric |
1 |
Problem Statement (5%) |
The report describes the problem statement precisely. It should highlight the need for the application and the necessary research done. User benefits are explained in detail. The report contains an executive summary with information on the project. |
2 |
User Requirements (10%) |
Students have understood the project, which is reflected in the Functional and Non-functional requirements. The requirements are written clearly and should be complete and unambiguous. Each requirement is to pass through the criteria of a reasonable requirement ( discussed in class). Limitations have been discussed. User groups are identified. |
3 |
Design (10%) |
The proposed design is as per the requirements. The components/modules are fulfilling all the requirements. The design is mapped to the requirements. Data flow diagrams, and other linkages ( if any) are clearly mentioned. The UI is neat and follows a color scheme and not random colors. The screenshots in the report are clear. |
2023-02-21