please make sure you reach the requirements and watch out the deadlines.
thank you
Module Learning Outcomes Assessed:
1.Critically evaluate different technology design and implementation options for developing mobile apps with rationale and recommendations.
2.Apply the appropriate platform and technologies to produce a mobile app that delivers innovative user experience within specified time constraints and quality requirements, including risk management.
3.Design and implement a mobile app following the process of building native or hybrid apps.
4.Demonstrate an ability to maintain ease of data access and usability across platforms.
5.Evaluate mobile app development resources and apply appropriate tools, apps editors or the Integrated Development Environments (IDEs) for developing cross platform apps.
Task Overview:
You will be assigned a topic for this module and given access to detailed customer requirements. The topic you have been assigned can be found in the Topic List document whilst details of each are in the Assignment Descriptors document (see the Useful Resources section below).
There are four required outputs.
1.The first task is to produce a presentation for the management team outlining the different development choices and making a justified recommendation.
2.The next task is to design, build and deploy a secure cloud-based data management API complete with online documentation. The API must be built inside the supplied Codio box, using the Dart language and be deployed to the cloud. The changes must be pushed to GitHub every day you work on the project.
3.The company will be taking on a small team of developers to build and maintain the app. Assuming the chosen platform is Flutter, you will produce a detailed onboarding guide that will be given to all team members. This will describe the different tools that can be used to develop the app, giving pros and cons as well as instructions on how to set up their workstation, navigate and use the preferred IDE as well as how to generate a website and a native app. Everything in this guide including screenshots must be related to your specific topic.
4.The final step is to design and implement a Flutter app to satisfy the customer requirements. You may develop your code on your local computer however this must be committed and pushed to GitHub every day you spend on developing it.
Submission:
You are required to submit several documents. Each should be of the specified length and in a specific format.
Mobile Technology (ILO 1):
A presentation consisting of up to six (6 slides). This should be uploaded in PDF format and called TECHNOLOGY.PDF.
UI and Functionality (ILO2 and ILO3):
A 5 minute screencast in 720P resolution or higher, encoded as MP4. The file should be called APP.MP4. The screencast should demonstrate the functionality as listed in the topic descriptor.
API Design (ILO 4):
A 5 minute screencast in 720p resolution or higher encoded as MP4. The file should be called API.MP4. The screencast should show the Postman API t
3/15/22, 8:38 PM feature 3 now includes the old feature 4 · agile/projects@f264d8c · GitHub
https://github.coventry.ac.uk/agile/projects/commit/f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99 1/2
agile / projects
Code Issues 1 Pull requests Projects 1 Security Insights
feature 3 now includes the old feature 4
New feature 4 task is to display stats.
master
aa7401 committed on Dec 18, 20211 parent 4545e22 commit f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99
Showing 1 changed file with 17 additions and 5 deletions.
Browse files
Unified Split
19 Survey.md
30 30
31 31
32 32
33
33
34 34
35 35
36 36
47 47
48 48
49 49
50
50
51
52
51 53
52 54
53 55
57 59
58 60
59 61
62
22
The home screen should be visible without needing to log in. If logged in the user should
see a **New survey** link or button that takes them to the _New Survey_ screen. Here they
can create a new survey by completing the form and supplying the following data:
1. The survey name.
– 2. A multiline description of the survey that accepts _markdown_ formatting.
+ 2. A multiline description of the survey.
Although not part of the form, the following data should be inserted into the database:
2. The date it was created (but not the time).
3. The number of questions in the survey (see below).
– Next to each there should be an **Add question** link or button. This takes them to a
screen where they can add a new question. Each question includes the following data:
+ Next to each there should be an **Edit** link or button. This takes them to a screen
where they can add and remove survey questions.
+
+ On this screen there should be an **Add question** link or button that allows for a new
question to be added. This will prompt for the following data:
1. The question title.
2. A multiline description of the question that accepts _markdown_ formatting.
1. The id of the survey the question should be added to.
2. The date and time the question was created.
+ As each question is added, its title should be displayed on the screen together with a
https://github.coventry.ac.uk/agile
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/agile/projects/issues
https://github.coventry.ac.uk/agile/projects/pulls
https://github.coventry.ac.uk/agile/projects/projects
https://github.coventry.ac.uk/agile/projects/security
https://github.coventry.ac.uk/agile/projects/pulse
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/agile/projects/commits?author=aa7401
https://github.coventry.ac.uk/agile/projects/commit/4545e225922df1f69511bb2c6effcca18e3a905a
https://github.coventry.ac.uk/agile/projects/tree/f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99
https://github.coventry.ac.uk/agile/projects/commit/f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99?branch=f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99&diff=unified
https://github.coventry.ac.uk/a
3/15/22, 8:36 PM projects/19 Survey.md at master · agile/projects · GitHub
https://github.coventry.ac.uk/agile/projects/blob/master/19 Survey.md 1/5
agile / projects
15 stars 60 forks
Code Issues 1 Pull requests Projects 1 Security Insights
projects / 19 Survey.md
aa7401 feature 3 now includes the old feature 4 … History
1 contributor
Star Notifications
master
Survey Tool
A tool that can be used to carry out surveys. All questions use the same scale that is used
by the University Module Surveys. All surveys and results should be stored in a database.
For the purposes of this project there should be at least 5 sensible questions.
1. Strongly Disagree (1 point)
2. Disagree (2 points)
3. Neither agree nor disagree (3 points)
4. Agree (4 points)
5. Strongly agree (5 points)
Testing
You are required to create the following accounts to allow the system to be tested. All
accounts should have the password p455w0rd :
116 lines (68 sloc) 5.39 KB
https://github.coventry.ac.uk/agile
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/agile/projects/stargazers
https://github.coventry.ac.uk/agile/projects/network/members
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/agile/projects/issues
https://github.coventry.ac.uk/agile/projects/pulls
https://github.coventry.ac.uk/agile/projects/projects
https://github.coventry.ac.uk/agile/projects/security
https://github.coventry.ac.uk/agile/projects/pulse
https://github.coventry.ac.uk/agile/projects
https://github.coventry.ac.uk/aa7401
https://github.coventry.ac.uk/aa7401
https://github.coventry.ac.uk/agile/projects/commit/f264d8c92b6d97e1c58d7eb531cdd1eb537b1c99
https://github.coventry.ac.uk/agile/projects/commits/master/19%20Survey.md
https://github.coventry.ac.uk/login?return_to=%2Fagile%2Fprojects
https://github.coventry.ac.uk/login?return_to=%2Fagile%2Fprojects
3/15/22, 8:36 PM projects/19 Survey.md at master · agile/projects · GitHub
https://github.coventry.ac.uk/agile/projects/blob/master/19 Survey.md 2/5
1. student1
2. student2
3. student3
4. student4
5. admin (this is only needed if you attempted the stage 3 functionality).
Students 1-3 should have completed the survey(s) but user 4 should have not attempted
any of them.
Feature 1
The home screen should be visible without needing to log in. If logged in the user should
see a New survey link or button that takes them to the New Survey screen. Here they can
create a new survey by completing the form and supplying the following data:
1. The survey name.
2. A multiline description of the survey.
Although not part of the form, the following data should be inserted into the database:
1. The username of the currently logged-in user.
2. The date and time the survey was created.
To demonstrate this feature and to prove that the form works correctly you will need
to show that the data is being persisted correctly, either by running a database query
Why Choose Us
- 100% non-plagiarized Papers
- 24/7 /365 Service Available
- Affordable Prices
- Any Paper, Urgency, and Subject
- Will complete your papers in 6 hours
- On-time Delivery
- Money-back and Privacy guarantees
- Unlimited Amendments upon request
- Satisfaction guarantee
How it Works
- Click on the “Place Order” tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
- Fill in your paper’s requirements in the "PAPER DETAILS" section.
- Fill in your paper’s academic level, deadline, and the required number of pages from the drop-down menus.
- Click “CREATE ACCOUNT & SIGN IN” to enter your registration details and get an account with us for record-keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
- From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.