DSW02B1 Project Description
Lecturer: Mr. KR Mabokela
School of Consumer Intelligence and Information Systems, Department of Applied Information System, University of Johannesburg.
Semester: July – December 2019
Total Marks: 100
Due Date: 30.10.2019
Group Project – Mobile Application Development Project Project Details
The team project (Must strictly be 5–6 students per team) for this course involves conceptualizing, Analysis, designing, and Implementation of a mobile application running on either Windows platform – Xamarin, HTML5, Ionic, Android or iOS SDK. Your need choice one platform that you are comfortable with and use it to develop you’re Mobile Application. The application should meet a set of functional and non-functional requirements as per the description below. The teams should follow a well-managed development process that results in user-friendly, well-designed and well-documented Mobile software.
High-Level Requirements
Duringourlecturesessionwementionedthatthemostusersthesedaysprefertouse mobiledevicemore than desktop computers. Mobile devices serves as three things which is to serves as your gateway to everything else; your daily entertainer and lastly, it represents you. Thus, the Mobile App that you conceptualize must be represent your team values, must represent you, and most importantly be unique to you.
In addition, the Mobile App must meet the following requirements: – Must uniquely meet a clear need and solution;
– Must be well-designed and user-friendly,
– Must have a creative user interface
– Must be innovative addressing a specific problem,
– Must have at least three domain objects,
– Must have data that persists throughout multiple user sessions,
– Must have be able to store and retrieve information to the database; – Must have the ability to work offline;
– Must be compatible to the recent mobile devices,
– Must use at least one Internet-based service (e.g., YouTube, Twitter, Facebook, Firebase, or Geolocations services, Google Maps);
– Must use at least one device sensor (e.g., Camera, GPS, accelerometer, or light sensor).
Page 1 of 4
Big Note: All groups or teams must design an original distinct Mobile Apps. There should NOT be multiple groups or team Mobile Apps that meet the same needs or similar problem. I expect that each group designs and develops an original Mobile App that is distinct from Mobile Apps that are already available on the market as well as other groups. Since the project entails designing and implementing an Innovative Mobile App that represents you, use this opportunity to showcase your innovative ideas, creativity in your mobile app design. In addition, your mobile app may be a game that meets the above requirements and originality considerations.
Evaluation Criterion
Criterion (1): Environment Setup and Running Mobile App
Evaluation Criteria: The mobile app executes via the platform emulator (i.e, Android, Xamarin, Ionic, iOS, or mobile device).
Criterion (2): Mobile App Requirements and Design Document
This Criteria entails envisioning and designing a mobile app that meets the requirements specified in
the High-Level Requirements section.
Submit: A SINGLE design document using Latex writing system that shows:
– Write details of your app conception, specifically:
◦ Narratives (one or two paragraphs describing how someone uses your app and why
your mobile app is necessary to achieve certain goals);
◦ A UML class diagram of your mobile app’s domain model designed following the object- oriented approach discussed in the lecture session;
◦ A categorized list of use-cases describing users’ interactions with the app (for example categories can include “Account MANAGEMENT,” “Mapping,” and so on);
◦ Your mobile app’s relational model that describes tables and relations in your relational database schema (you need to include the relational model in your document, not just an ER diagram);
◦ Sketches (drawings of people using the mobile app as you envision, how the app connects to external services, and so on);
◦ Screen layout mockups; and
◦ Screen flows showing how clicking different User Interface elements navigates the user among mocked-up screen layouts.
Note: Your screen layout mockups OR screenshots, screen flows, and sketches may be drawn by hand, but they MUST be legible.
Showcase: Your mobile app design document with the information above. You should explain your app to the grader during your group’s meeting with him/her.
Evaluation Criteria: Clear evidence of the object-oriented design process.
Criterion (3): Installing, Debugging, Profiling, App Lifecycle Management
This checkpoint involves demonstrating your ability to do the following: – Installing your app on a mobile device;
– Debugging (e.g., stepping through source code and setting breakpoints on your app);
– Profiling your app using one or more profilers (e.g., Visual, Android Studio’s CPU, GPU, or memory profilers or Instruments for iOS);
Page 2 of 4
– The mobile app lifecycle and logging. Here you must implement a simple part of your mobile app and demonstrate using the log file that you can trigger the app’s lifecycle methods in Activities (e.g., onPause( ) and onResume( )) and Fragments (e.g., onCreateView()).
Submit:
– A screenshot of at least one type of profiler (e.g., CPU or memory footprint in Android Studio, Visual Studio or Xcode);
– Screenshots of the mobile app’s lifecycle methods being triggered;
– Screenshots of debugging your app in Android Studio, Visual Studio or Xcode (specifically, setting a breakpoint, viewing variables’ states, and stepping through code).
Evaluation Criteria:
Criterion (4): Database Integration Requirements
You need to show evidence of apps ability to perform CRUD components.
Submit:
– Screenshots of your mobile app’s data storage schema
– Screenshots of your mobile app’s class organization;
– Screenshots of a version control repository for your mobile app’s source code.
Showcase:
– Your app’s data storage schema;
– Your app’s ability to perform creation, retrieval, updates, and deletions (CRUD) with your data store (an on-device relational database or an external service such as Firebase);
– The version control repository for your app and layout of your mobile app’s classes.
Evaluation Criteria:
– Students demonstrate implementation of their mobile app’s data storage schema (using a relational or any SQL databases);
– Students demonstrate that their mobile app can perform CRUD operations on stored data; – Students demonstrate use of a version control system; and
Criterion (5): Functional Demonstration of Your Mobile App
For this checkpoint, you have to demonstrate a functioning mobile app. The app should work from end to end. Do not worry about the performance of the following; network connectivity, GPS signal reception, and so on.
Submit:
– A list of use cases
– Screenshots of your app running.
Showcase: Your mobile app working on a mobile device. (If it works only on an emulator, you will
only receive partial marks.)
Evaluation Criteria: Check working use-cases
Criterion (6): Demonstration of Your Mobile App’s Non-Functional Requirements
This checkpoint entails showing your app’s non-functional capabilities such as usability, performance, availability, maintainability, modifiability, and scalability. The app should work from beginning to end,
– Students demonstrate understanding of IDE use;
– Students demonstrate comprehension of the Android/iOS/Windows app/Platform of your
choice’s lifecycle.
Page 3 of 4
must be robust enough to work under failures (such as loss of network connectivity and GPS signal reception, screen rotation, and termination by the OS).
Submit:
– List of use cases and NON-functional requirements met
– Screenshots of the app
Showcase: The working app on a device demonstrated to work under failures (network connectivity, GPS, screen rotation) or app can work-offline.
Evaluation Criteria: Number and quality of working use cases and non-functional requirements met.
Submission
Due: Wednesday, 30 October 2019
App Session Demo
Time: To be determined
Report Expectations
– References: You are responsible for citing any third-party intellectual property you use in the project.
– Clear Writing: Your writing should be simple, concise, and easy to understand; if not, revise it! Your writing should demonstrate a logical sequence of thought; spelling and grammar errors should be absent. Most word processing tools (including online ones such as Google Docs) have built-in spelling and grammar checkers; please use them and also note that Prospective employers and graduate schools expect clear writing. In addition, Latex writing is preferred.
– Figures: You are welcome to include figures in your report. Please cite them as “Figure 1. Hand-drawn figures are not allowed in the document, please draw them with software such as MS Visio, eDraw, OmniGraffle, etc.
Page 4 of 4
Reviews
There are no reviews yet.