MITG2102讲解、辅导Python编程、讲解c/c++，Java程序语言、辅导Mobile Computing 辅导Database|讲解S
- 首页 >> 其他 College of International Education (CIE)
Associate Degree Programme
Project on Mobile Applications Development
Course : MITG2102 Mobile Computing (Section 51)
Year/Term : 2018-19, Semester 2
Deadline : 2 May, 2019 (Thu) 17:30 onto Moodle
Credit : 50% of total assessment
Objective
To apply the techniques and skills of mobile applications development learned in this course to complete a practical project.
Description
The project should be accomplished individually. Students are required to develop a mobile application to be run on the Android 8.1 (API 27) platform, with screen size of 1080 x 1920 (420dpi).
Theme
The theme of the mobile application is mobile Commerce (M-Commerce), i.e. promote business product or service sales through mobile platform. The main target users are potential customers and clients. However, whenever appropriate, the application administration staff may also use the application for information input, update…etc. Functions provided in the application are not limited. Possible examples include company and products/services information, promotional news, member services, online shopping and ordering functions…etc. You should conduct a research about the functions of similar mobile applications available in the market for more ideas.
Project Progress
Each individual needs to submit a working progress report which should include the following content, by 7 April (end of Week 10):
1.Research and comparison with similar mobile apps available in the market: functions, user interface design…etc.
2.List of planned functions, with brief descriptions
3.Preliminary or draft user interface design: sketches or screen captures
4.Development method to be used: App Inventor 2, Android Studio, or others.
The overall project progress will contribute to 10% of the project mark.
Submission of Project Work
Students should submit the following materials to the lecturer:
(a)Final product of the mobile application in .apk file format and the corresponding zipped development files (e.g. downloaded App Inventor 2 project .aia file, Android Studio project files).
(b)A project report which includes the following items:
-Name of the mobile application
-Function descriptions
-User interface design
-Detail descriptions of the skills and techniques applied to develop the application.
Grading
Your grade will be based upon your inclusion of all the elements listed above and on how well you meet the application theme and requirements. The overall assessment criteria are shown as follows:
1) Project progress 10%
2) Functional Design 20%
3) Creativity 10%
4) User Interface Design 10%
5) Technical Skills Applied 40%
6) Robustness 10%
Total : 100%
Resources: Online References for Android Development
Students may visit the following web sites and any other sources, for the Android development tutorials, library and API reference.
(1) Android Developers: http://developer.android.com
(2) MIT App Inventor: http://appinventor.mit.edu
Assessment Rubrics
Criteria Capstone
(Exemplary) Milestone
(Competent) Milestone
(Basic) Benchmark
(Emerging) Fail
Project progress Thoroughly research and compare similar mobile applications in the market.
The work progress of functional and user interface design is strictly kept as planned during the whole project period. Research on similar mobile applications in the market has been done, without comparison among them.
The work progress of functional and user interface design is still kept as planned, with short delay in some tasks. Research on similar mobile applications in the market is too brief.
The work progress of functional and user interface design cannot follow the plan, with serious delay. Do not research on similar mobile applications in the market.
There is no planning or evidence for the working progress during the project period. PLAGARISM or NON SUBMISSION
Functional Design A complete set of functions is designed, which is fully suitable for the theme and users’ needs of the application. A limited set of functions is designed, which is still suitable for the theme and users’ needs of the application. Only basic functions are designed to suit for the theme and users’ needs of the application. The designed functions are simple and not suitable for the theme and users’ needs of the application.
Creativity Uses the unexpected to full advantage; very original, clever, innovative, and creative approach that captures users’ attention. Some originality apparent; clever at times; good variety and blending of materials/media. Little or no variation; a few original touches but for the most part material presented with little originality or interpretation. Bland, predictable, and lacked attractiveness. Repetitive with little or no variety; little creative energy used.
User Interface Design The user interface is clear, user friendly, attractive and totally appropriate for the functions designed. The user interface is clear, user friendly, but only partially appropriate for the functions designed. The user interface is unclear, difficult to use, and only partially appropriate for the functions designed. The user interface is irrelevant or inappropriate to the functions designed.
Technical Skills Applied Advanced and basic skills and techniques have been applied in the application.
All the skills and techniques applied are appropriately used for the emphasis of ideas. All the basic skills and techniques have been applied in the application.
Some of the skills and techniques applied are appropriately used for emphasis of ideas. Only some of the basic skills and techniques have been applied in the application.
Skills and techniques applied are inappropriately used for emphasis of ideas, but are still relevant to the theme. No basic skills or techniques have been applied in the application.
Skills and techniques applied are totally irrelevant to the theme.
Robustness The application is completely robust, which is totally error-free and checks for all the input or control validities. The application is partially robust, which is error-free, but does not check for input or control validities. The application is not robust, which contains some errors or bugs, and does not check for input or control validities. The application is not functioned properly, which contains a great amount of errors and bugs.
- END -
Associate Degree Programme
Project on Mobile Applications Development
Course : MITG2102 Mobile Computing (Section 51)
Year/Term : 2018-19, Semester 2
Deadline : 2 May, 2019 (Thu) 17:30 onto Moodle
Credit : 50% of total assessment
Objective
To apply the techniques and skills of mobile applications development learned in this course to complete a practical project.
Description
The project should be accomplished individually. Students are required to develop a mobile application to be run on the Android 8.1 (API 27) platform, with screen size of 1080 x 1920 (420dpi).
Theme
The theme of the mobile application is mobile Commerce (M-Commerce), i.e. promote business product or service sales through mobile platform. The main target users are potential customers and clients. However, whenever appropriate, the application administration staff may also use the application for information input, update…etc. Functions provided in the application are not limited. Possible examples include company and products/services information, promotional news, member services, online shopping and ordering functions…etc. You should conduct a research about the functions of similar mobile applications available in the market for more ideas.
Project Progress
Each individual needs to submit a working progress report which should include the following content, by 7 April (end of Week 10):
1.Research and comparison with similar mobile apps available in the market: functions, user interface design…etc.
2.List of planned functions, with brief descriptions
3.Preliminary or draft user interface design: sketches or screen captures
4.Development method to be used: App Inventor 2, Android Studio, or others.
The overall project progress will contribute to 10% of the project mark.
Submission of Project Work
Students should submit the following materials to the lecturer:
(a)Final product of the mobile application in .apk file format and the corresponding zipped development files (e.g. downloaded App Inventor 2 project .aia file, Android Studio project files).
(b)A project report which includes the following items:
-Name of the mobile application
-Function descriptions
-User interface design
-Detail descriptions of the skills and techniques applied to develop the application.
Grading
Your grade will be based upon your inclusion of all the elements listed above and on how well you meet the application theme and requirements. The overall assessment criteria are shown as follows:
1) Project progress 10%
2) Functional Design 20%
3) Creativity 10%
4) User Interface Design 10%
5) Technical Skills Applied 40%
6) Robustness 10%
Total : 100%
Resources: Online References for Android Development
Students may visit the following web sites and any other sources, for the Android development tutorials, library and API reference.
(1) Android Developers: http://developer.android.com
(2) MIT App Inventor: http://appinventor.mit.edu
Assessment Rubrics
Criteria Capstone
(Exemplary) Milestone
(Competent) Milestone
(Basic) Benchmark
(Emerging) Fail
Project progress Thoroughly research and compare similar mobile applications in the market.
The work progress of functional and user interface design is strictly kept as planned during the whole project period. Research on similar mobile applications in the market has been done, without comparison among them.
The work progress of functional and user interface design is still kept as planned, with short delay in some tasks. Research on similar mobile applications in the market is too brief.
The work progress of functional and user interface design cannot follow the plan, with serious delay. Do not research on similar mobile applications in the market.
There is no planning or evidence for the working progress during the project period. PLAGARISM or NON SUBMISSION
Functional Design A complete set of functions is designed, which is fully suitable for the theme and users’ needs of the application. A limited set of functions is designed, which is still suitable for the theme and users’ needs of the application. Only basic functions are designed to suit for the theme and users’ needs of the application. The designed functions are simple and not suitable for the theme and users’ needs of the application.
Creativity Uses the unexpected to full advantage; very original, clever, innovative, and creative approach that captures users’ attention. Some originality apparent; clever at times; good variety and blending of materials/media. Little or no variation; a few original touches but for the most part material presented with little originality or interpretation. Bland, predictable, and lacked attractiveness. Repetitive with little or no variety; little creative energy used.
User Interface Design The user interface is clear, user friendly, attractive and totally appropriate for the functions designed. The user interface is clear, user friendly, but only partially appropriate for the functions designed. The user interface is unclear, difficult to use, and only partially appropriate for the functions designed. The user interface is irrelevant or inappropriate to the functions designed.
Technical Skills Applied Advanced and basic skills and techniques have been applied in the application.
All the skills and techniques applied are appropriately used for the emphasis of ideas. All the basic skills and techniques have been applied in the application.
Some of the skills and techniques applied are appropriately used for emphasis of ideas. Only some of the basic skills and techniques have been applied in the application.
Skills and techniques applied are inappropriately used for emphasis of ideas, but are still relevant to the theme. No basic skills or techniques have been applied in the application.
Skills and techniques applied are totally irrelevant to the theme.
Robustness The application is completely robust, which is totally error-free and checks for all the input or control validities. The application is partially robust, which is error-free, but does not check for input or control validities. The application is not robust, which contains some errors or bugs, and does not check for input or control validities. The application is not functioned properly, which contains a great amount of errors and bugs.
- END -