1. At the bottom of the project use-case documentation, add a signature page for all required manager signatures. Make sure the signature page looks and feels professional which should include the date of when a manager signed the use-case documentation for approval. You have more objectives in the course to build and integrate into your documentation but this should always be the last page of the document.

2. Next document a typical scenario that might actually be a good reason to change the scope of a project. For instance, the documentation might not include form validation controls. As the users are testing, the validation is always necessary to keep the data clean in the database. Create your own scenario that could change the scope of the project and would cause the managers to agree and accept the change request.

3. Document the change request procedure. This professional procedure would be used in a business when a tester found an issue that requires a project change and the requestor would need to follow through each step before the change would even be considered. Document the procedure in a chronological order as if each step was a checklist.

Project Summary As the developer of a large enterprise wide application, which the entire company uses every day, the users want to make a change to improve validation within one of the application forms, so that a user cannot enter unformatted dates into a form field that accepts dates. The users want stricter validation since the unformatted date values are causing too much data cleanup problems. It is the goal of this project to be able to improve the validation while limiting the amount of downtime and disruption of day to day activities for the application. Project Risks As with any project, there are several risks involved when it comes to making changes to an application. One risk would be possibly corrupting or losing data while making the changes to the application. It would be vital to have a backup in a separate location just in case there was an issue or some of the data was lost during the changes. Another risk would be making these changes to the application during normal working hours and causing downtime. This could be avoided by making the changes after hours but that could cause another issue with having to have staff stay late to make this accommodation. There are also risks when it comes to the software itself. If it hasnt properly been tested and prepared before the changes plan to be made, it could cause data to be corrupted or longer downtime for the problem to be corrected. Business Rule The first rule will be the formatting that will be accepted by users as an input. There will be an example for the user to follow to enter the date mm/dd/yyyy. This will help users know what format to enter the date in and there will be a catch in the application itself that will not allow the user to continue until the date has been entered in the proper format. This will help with the data clean up issues. Another rule will be for the database table columns for First_Name, Last_Name and Telephone number. The columns for the first name and last name are fairly straight forward but there will be an example for users to follow for the telephone number xxx-xxx-xxxx. This will help users know what format to use for the telephone numbers even though most numbers have the same number of digits. There will also be a catch in the application at this point as well that will not let the user continue until they have correctly formatted the telephone number. System and software feature The user will need to properly enter the date, first name, last name, and telephone number in order for the application to accept the information and allow the user to continue. These changes will need to be made to the application while the application is not in use to reduce the risk of data corruption or losing data. After the update to the application is made, whenever the user tries to enter information for the date or telephone number that does not match the formatting, they will encounter a message that informs them that the information they entered is not formatted correctly. They will be given an example of how the information should be entered and will not be allowed to continue entering information until they have properly formatted the information. Prioritize the requirements The most important part of this change will be to back up the data in a separate location before the updates are made so that the data will not be corrupted or lost if something goes wrong during the update. The next important would be making sure that the update is made while the application is not in use. This may require the updates to be made outside of regular work hours to ensure that it is not being used during the update. The next important requirement is that the application has the catch to stop the user from submitting unformatted information and making sure to give them an error message to inform them that the information is not formatted properly and to give them an example of how to enter it correctly. Why you need the cloud service Different cloud-hosting providers have different application model requirements. Some adopt a virtual machine approach, where the application is developed and packaged along with its operating system image and the dependent runtime frameworks. Others utilize an application model that provides higher level abstractions for data access and storage, and for computation and communication. Each of these approaches provides distinct advantages and disadvantages. Benefits Architectural Flexibility. Vendors can offer their customers a range of deployment options, including hosting for the services they require, and allow users to choose from a range of prebuilt features or choose which features of the application they will implement themselves. This can reduce the architectural liabilities for end users who are developing services Rich User Experience. ISVs and service providers can offer richer experiences to their customers by leveraging existing specialized services. Hosters can combine their offerings with other cloud services obtained elsewhere to offer additional value propositions, and make it easier for end users to integrate services. Ubiquitous Access. Services in the cloud persist user data and state, and resynchronize when the user reconnects from any location. This supports both offline and occasionally connected scenarios, which is especially useful for mobile devices where a constant connection or bandwidth cannot be guaranteed. Benefits for Enterprise Service Consumers Architectural Flexibility. In-house developers can create complete solutions that compose services in the cloud with local application code and their own services. IT departments can choose which features of the application they will implement themselves, and buy in other services that they require. Cost and Time Savings. IT departments can select the best cloud-based service for each task, and combine them to expose fully functional applications with shorter development times, and at a reduced cost. In addition, the reduction in the requirements for in-house IT infrastructure simplifies management, security, and maintenance costs. Economies of Scale. Companies can leverage economies of scale for industry average capabilities, and focus on their core activities. The economies of scale available from hosted applications arise from a range of factors, including reduced in-house infrastructure costs to better utilization of hardware that offers opportunities for reduced running costs. However, the gains in economies of scale must be balanced with the loss of control inherent with moving from on-premises to fully hosted applications. Offline Capability. The cloud can act as hub for roaming users. User data and state can be stored in the cloud and resynchronized when the user reconnects. Users can move between desktop and mobile clients seamlessly with fewer network configure Performance Cloud-hosted applications must be scalable to support increasing numbers of services, and increasing load for each service and tenant. When designing services, consider the following guidelines for scaling applications: Design services and components to be stateless where possible. This minimizes memory usage for the service, and improves the opportunity to scale out and load balance servers. Investigate the capabilities of the hosting platform that can improve performance. For example, in Microsoft Azure, use queues to manage requests and worker processes to carry out background processing. Use resource pooling for threads, network, and database connections. Maximize concurrency by using locking only where absolutely necessary. Data Storage and Extensibility Table Storage Services provide structured storage in the form of tables, but these tables have no defined schema; instead, they contain entities, each of which holds a number of properties. Table Storage Services focuses on providing massively scalable tables at a very low cost. However, it is not a relational database and lacks many of the features you would expect to find in an RDBMS such as joins and foreign keys across multiple tables. Blob Storage Services offers storage for binary data stored in user-defined containers, which organize sets of blobs within a storage account. Queue Services store messages that may be read using queuing semantics by any client that has access to the storage account. Procedure for developer Announce a maintenance window. Stop all setup changes on production. Create a staging environment. Migrate changes to the staging environment. Change environmental dependencies and services from testing settings to production values. Lock users out of the application. Test the deployment using the Metadata API. Deploy to production. Unlock the production org. The meaning of scope creep and how scope creep affects a project Scope creep is what happens when that outline doesnt quite go as it was planned. Maybe the client requested extra work not in the original proposal, or maybe they changed an objective entirely, or improper resources. Regardless of the reason, the project has taken a different path that may affect the budget and deadline. Timelines and budgets are just two examples that would have a direct impact on a project and could cause scope creep. A timeline is a vital aspect in project management and it is important for the timeline to be planned properly. Timelines are designed by the project manager from the start to end of a project. Using timelines, we can track the growth of the project and monitor how a project is doing along the way. Timelines may change if any new requirements are received and extra features need to be added to a project. Timelines are described based on tasks and sub-tasks. The timelines consists of details about when a task will be completed, duration of a tasks and dependencies. It is important to have a detailed timeline with realistic goals otherwise it will be very easy for the timeline to be affected by scope creep if there is no planning for errors in the timeline. A budget is another vital part of project management and needs to be carefully planned so that it is not affected by scope creep. The budget of a project is quoted based on the projects functionality and difficulty in using the technologies and what resources are needed to insure that the technology will operate the way it was designed to. It is easy for a budget to go over the allotted amount of money so it is important for the project manager to plan appropriately to insure that they do not use all of their financial resources on one particular portion of the project leaving them short for other areas. The purpose of a project kickoff meeting Project kick-off meeting is the initial meeting before developing a project. The project kick-off meeting is conducted between the client and project team where various factors are discussed during this meeting regarding the project scope. The purpose of a project kickoff meeting is to introduce the team, understand the project background, understand what success looks like, understand what needs to be done, and agree on how to work together effectively its a chance to level set and get the team and client on the same page. The factors discussed in this meeting are explained below: Introduction Introduction of project team and client will take place. This creates a good rapport between the two parties to understand them each other. Client We need to understand the client background, is the client old one or new to the market, who is the CEO etc. Their nature of work and how they sustain themselves in the market. Project We need to understand why we are doing this project and how this is going to help the client in their growth. Scope What we are doing in this project and how this project differs from other competitors projects if available. Approach How we are going to approach this project. What are the things we need to follow to achieve the project completion. Roles Roles will be allocated to each resource and will be made clear. Who will perform which task under the given role. Teamwork Here we need to discuss how the team should collaborate and work. The communication between the teams should be discussed. Everyone should be defined as the master of the team. Kick-off Meeting with the client about the agenda and the project management. Next We should keep the momentum going so we need to discuss the clear plans of what is going to be executed next in the project. Q & A An open session will be conducted and people are invited to ask their questions.