This project will allow you to apply your knowledge and skill in Swift and iOS development. You will need to read and analyse the information provided and extract the vital pieces of the requirements that will facilitate your design and implementation of the project. For the purposes of this project you will need to leverage the major components, features techniques and procedures that you learned in this course in order to deliver your product afafagf this project and leverage the facilities of the Xcode development environment to create a working iPhone app. You will need to create user interface and user experience flows, prepare diagrams, write the code, create unit tests, and make sure the app lays out properly in both portrait and landscape modes without any errors or missing links as part of your final solution. OBJECTIVES The main objectives of this project are to: Interpret specifications and analysis performed Design a solution based on the requirements and specifications Design the logic required for a complete program design solution Write the code for the program logic. Copyright 2020 3 CA-IOSWT v1-0 Project 2020-0309 Use localization techniques for all user interface labels and messages. Debug and test your program and make sure it is working properly. TIME REQUIRED You will require 10-12 hours to complete this project. REQUIRED MATERIAL You will need the following material to complete this project: Xcode 10.x or higher Microsoft Word (for document preparation) In programming there are generally multiple possible solutions to the same problem. Your solution may not be identical to someone elses, but that does not mean that it is wrong. Your solution will not and should not look exactly like your colleagues solution. Any good solution is acceptable if produced following the principles and guidelines presented in this course. Copyright 2020 4 CA-IOSWT v1-0 Project 2020-0309 SPECIFICATIONS An application on iOS shares facilities with the operating system. One of these facilities is the calendar and the system database, events, and scheduling services. You have been asked to create an app that is capable of creating, editing, and deleting appointments that are visible in the system calendar. By interacting with the calendar service APIs the appointments you manage will be system wide. This will require asking the user for permission to use the device calendar so you can perform the CRUD operations necessary (create/read/update/delete). User Stories 1. I want to be able to create appointments that include the session name, start time, end time, location (physical location or a virtual online meeting - if available), and an optional description. 2. When I open the app I want to see a table list of all of my appointments. 3. As a user, I want to be able to edit, and delete an appointment. 4. The appointments I create should be visible in the iOS system calendar. 5. If any step or functionality fails I want feedback that explains what happened and what I should do next. You will need to import the EventKit framework into your project in order to leverage the functionality provided by the iOS system. Look at the documentation located at https://developer.apple.com/documentation/eventkit to begin. REQUIREMENTS: Model the Appointments App: Copyright 2020 5 CA-IOSWT v1-0 Project 2020-0309 Make sure you read through all of the user stories and extract the key pieces of information. Do not rewrite functionality that iOS already provides. A valuable skill when writing mobile apps is understanding what is provided by the system and leveraging the existing technology. Consider the various messages that the system is required to produce and document them. All messages should be localized by using the iOS Strings file. You are also dealing with date formatting so be cognizant of the fact that the format for a date will be different depending on the locale your app is being used in. For example, the U.S. tends to use month/day/year while in Canada they user day/month/year. Design the Program Logic You will create the various, user stories and user experience components to implement your appointments app: 1. User Stories Create a set of use cases for each of the main processes. Think in terms of user stories and how someone would use your app. Keep your user stories short and single purposed. For example, user stories for the appointment creation and reminder setting might be something like; User Story 1: As a user, I want to schedule an appointment. User Story 2: As a user, I want to set a reminder that informs me 15 minutes prior to the beginning of an appointment.' 2. User Experience (UX) Use post-it notes to design the UX flow of your app. Post-it notes are a valuable (and inexpensive) method for designing mobile applications. You can get post-it notes that are approximately the size of the mobile device and if you change your mind you can literally throw the design away and start again. When youre done, each of the main user interactions should be captured in a post-it note. Then, transfer these flows to the design document. Copyright 2020 6 CA-IOSWT v1-0 Project 2020-0309 3. User messages Document the possible informational and error messages that might occur during the operation of your app. This can also be done using post-it notes, initially, and then transferred to the design document upon completion of design. Be exhaustive and think about what you would want to know if you were a user and couldnt complete an operation. 4. Coding the program logic Using Swift and Xcode create the appointment app for iOS. This should make use of the autogenerated and included functionality from Xcode. GUI DESIGN This appointment app proposes different screens that the users will see at any given point in time. iOS is standardized in its layout and look and feel in order to provide users with a similar experience across applications. On a typical project a design team will create wireframes using a tool such as Sketch and then publish the design using a tool like Zeplin. This will include the various colours, buttons, error messages, and orientations. Given the scope of this project we will try to incorporate this stage with the actual development by using the storyboard. The storyboard that is part of the Xcode environment is both a development and a prototyping tool that can be used to iterate through design changes once you have your post-it notes stage complete. A weakness of the storyboard is in capturing the dialogue messages that might occur during runtime. Therefore, it is important to create the list of the