Systems Development Life Cycle Plan Analyze Systems Development Life Cycle Design Name of Project Develop Test Implement Maintain

Plan Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility) Analyze The project plan should include specific information about the project, such as: System requirements – should identify and select the system for development (what are your needs, what is the system you are developing, etc. – give an overview of the system here). Assess project feasibility – include what types of feasibility studies you plan to use, why you chose those, and how you plan on performing them. Do two feasibility studies (p. 366) You should also include the project scope (with a timeline of when different parts will be completed) Design Develop Test Implement Maintain

Plan Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility) EXAMPLE: System Requirements: (how the users operate in the system) The eBookSharing system is an Internet-based application that allows a student (owner) to maintain a list of books they are willing to share. The list is browsed by other students (borrower) looking for specific books. A borrower begins by logging in (email address and a password). The book list will include: title, author, ISBN, edition, condition, and the course in which the book was used. If a student is interested in borrowing, they can submit an offer to the owner. The book owner browsers through the offers and may then accept an offer and arrange a place and time for an exchange. A critical success factor for eBookSharing is that the system should be able to handle requests from multiple users at once. Specific functional requirements: Log In Borrowing Offering Accepting Maintaining Booklist Analyze Design Develop Test Implement Maintain

Project Plan – System Development The No Worries, LLC system is an Internet-Based application that allows current and potential customers to schedule seasonal services for their vehicle. The system initially engages the customer by prompting a customer to click on the “Schedule Service” button. From here, an existing customer is prompted to login (Email and Password); a new customer is prompted to create a login. New Customers are then prompted to select their subscription (membership) they would like to purchase, which entails the type and frequency of services; existing customers may cancel or adjust subscription if desired. Customers then choose the time(s) they would like their car serviced by interacting with a scheduling calendar (Please note: The calendar only displays to the customer service timeslots that are open). Customers are then prompted by the system to enter their credit card information to pay the cost of their subscription. Customers are then prompted to “Check out” of the system after the payment step. After checking out, the system sends the customer a confirmation E-mail of the services they’ve requested, as well as request for the customer to drop a key off for their vehicles at their earliest convenience.   Specific functional requirements Log In Subscribing Scheduling Payment collecting

Plan Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility) EXAMPLE: Specific Non-Functional Requirement: The semester is coming to a close thus, an operational Internet-based application must be delivered by April 20, 2015 before book buy back begins. The following milestones will enable this deadline to be met (talk about the different milestones you believe need to be met to complete the project) Analyze Design Develop Test April 1 – Project Document and Business Requirements Completed. April 5 – Process and Database Models Completed delivered to programming April 9– Initial Prototype ready for beta testing April 11– Final product due from programming April 18 - User documentation due THIS IS JUST AN EXAMPLE . YOURS SHOULD BE SPECIFIC TO YOUR PROJECT. Implement Maintain

Project timeline The snow is starting to fly, and the fall semester is coming to a close. Our goal is to get our website up and running over the Christmas break, with the intent to be fully online by the start of the spring semester. Our website must be operation by January 23rd, 2016 The timing for this will be imperative, as we will rely on the busy schedules of professionals to kindle our amount of business.   January 1st – Create a route directory for our website, start bringing over coding for appropriate website layout. January 8th – Buy and integrate an SSL certificate into our website January 10th – Create sub pages for our website that contain our Web 2.0 technologies hyperlinked January 13th – Give the website a user friendly and attractive format January 15th – Test website, make sure all links are working, as well as all our Web 2.0 technologies are working. Run mock customer sign ups. January 18th – correct any coding issues or bugs. January 21st – Prepare for use

Plan Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility) EXAMPLE: Project Feasibility: (see TextBook page 366) Economic (cost are less than benefits) Legal (it is legal and ethical to do) Operational (fits company objectives) Schedule (project can be completed on time) Technical (it is possible to do with the tools available) Economic feasibility: A cost benefit analysis will be performed to determine the costs associated with creating the eBookSharing system along with the benefits for students using the system. A major benefit for students is an intangible benefit derived from satisfaction of others saving on the cost of textbooks. An economic analysis is used to garner support from the university administration to provide financial support for the project. Analyze Design Develop Test Implement Maintain

Feasibility Studies A technological feasibility study will be performed in order to assess that we have the tools we need in order to assure the integrity of our customers’ personal information, as well as the quality of our website development. An SSL certificate may be purchased from Thawte for data encryption of our customers’ personal information. Once we have a route directory and a URL for our website, simple coding research may be conducted and implemented by our development team in order to start building the website. An operational feasibility study will be conducted on our website in order to ensure it is properly aligned with out companies objectives. We need to ensure that our website is user friendly to our clientele, and achieves the main function of allowing customers to purchase subscriptions and set up schedules. We also must to ensure the confidentiality and security of our website which will be ensured through our SSL certificate.

Plan Analysis (gather detail business process steps, create process diagrams, perform a buy vs. build analysis) For this phase, include a detailed description of your business process steps, who is involved in this phase, Part of this phase includes creating process diagrams (which identify specific processes that occur on your website – both user and server side processes). Process diagram examples are on the next slides. You will also include a buy versus build analysis discussion as well as include process diagrams. Analyze Design After logging in, the user begins by viewing a list of current books. Either an Add or Update Function can be selected. Depending on the function selected the user can maintain any number of books in the database. (detail business process steps) Develop Test Implement Maintain

Analysis phase Current/Existing member user After logging in, the user begins by reviewing their current subscription and has the option to change it, cancel it, or leave it as-is. If they choose to change their subscription, they will be prompted to give the corresponding service times they desire, as well as pay any price increases their new subscription incurred over their old one. They will then be required to confirm this change and may then exit the system. If they choose the cancel it, they will be sent a confirmation email, and after confirmation, the user may exit the system. If they choose to leave it as it and simply review their current subscription and service times, they will have no charge and will not get a confirmation email if no alterations have been made. The user may then exit the system. Signup Process Once the new user has clicked on the schedule service button, they will be prompted to create a login. The login will require the users email, physical address, phone number and make/model of the car they want serviced. Once they have successfully entered in the required information, they will have the option to either add another car they would like serviced, or to move on to the subscription page.

Plan Process Diagrams - You should create at least two of these to identify two of the different processes that will occur. Process diagram (identify what process you are diagramming) NAME OF PROCESS HERE Analyze Design *Login Develop View booklist After logging in, the user begins by viewing a list of current books. Either an Add or Update Function can be selected. Depending on the function selected the user can maintain any number of books in the database. (detail business process steps) Test Select Function [add selected ] Add Book Implement BOOK Change Book [change selected ] [ exit selected ] Maintain Prepared: March 2015 Prepared by: Informatory Inc.

Current/existing user Process Plan After logging in, the user begins by reviewing their current subscription and has the option to change it, cancel it, or leave it as-is. If they choose to change their subscription, they will be prompted to give the corresponding service times they desire, as well as pay any price increases their new subscription incurred over their old one. They will then be required to confirm this change and may then exit the system If they choose the cancel it, they will be sent a confirmation email, and after confirmation, the user may exit the system. If they choose to leave it as it and simply review their current subscription and service times, they will have no charge and will not get a confirmation email if no alterations have been made. The user may then exit the system. (detail business process steps) *Login Analyze Cancel subscribtion Subscription Design Service time Develop Website Payment Test Confirmation Implement [ exit selected ] Maintain

Continue to Current/Existing user Plan Signup Process Analyze *Create Login Signup Once the new user has clicked on the schedule service button, they will be prompted to create a login. The login will require the users email, physical address, phone number and make/model of the car they want serviced. Once they have successfully entered in the required information, they will have the option to either add another car they would like serviced, or to move on to the current/existing user process. (detail business process steps) Design Personal Information Website Develop Make/Model [add selected ] Add vehicle Test Continue to Current/Existing user Implement Maintain

System Model – website layout Plan Design phase System Model – website layout Analyze Login Scheduling Packages Pymt Options Cancel Policy Contact Us Home Comments Facebook link IM App No Worries LLC. Design Logo Develop Background (Company Project Pt 1) Test Implement Privacy Policy Maintain

Plan System Model– Navigation Analyze Design Develop Test Implement Maintain

Plan Develop – (develop the database (in your case website) and programs (in your case you will not have any programs) Create Prototype Analyze No Worries LLC. Design No Worries, LLC is a small service company based out of, and exclusive to, Laramie, Wyoming. Our company was founded by three business students at the University of Wyoming who were apt to capitalize upon the harsh climate and environment of Wyoming. Our mission is to optimize the safety and convenience of our customers by ensuring their vehicles are free of pesky elements of the Wyoming environment. These elements include ice, snow, bugs, bird feces, mud, as well as any other inconveniences we can take care of for our customers and their vehicles. Develop Test Implement For this section, you should give an example of your prototype for your homepage. The prototype may be created in PowerPoint, or HTML in a UW Student website. If you use a UW website, the links do not have to work, but you do need to show them. You should also give an overview of why this is your choice for your prototype design. You do not need to develop the IT infrastructure for this project but you would do that if you were developing a system in business. Maintain

Testing – (write the test conditions and perform the system testing) Plan Testing – (write the test conditions and perform the system testing) Analyze There are two parts to the testing phase, which involves bringing all the project pieces together into a special testing environment to test for errors, bugs, and interoperability, in order to verify that the system meets all of the business requirements defined in the analysis phase. For the testing phase, you should come up with some sample tests that you could perform (see Text Book Chapter 9). Include at least one test that checks for a failure or error message. You may use the graphic on the next sheet as the template for displaying your test conditions. Design Develop Test Implement Maintain

Plan Testing – write the test conditions and perform the system testing (see Textbook Chapter 9). Screen / Form Tested Date Tested Company Website 11/25/16 Tester Nathan Grossmann Test Condition Expected Results Actual Results (Circle one) Alpha Test to see if users can log in. Pass Pass Fail Development Test to see If an error message pops up when using footer links. Alpha test to see if users could successfully Cancel a subscription Error Message User Acceptance Test to see if users could Pay for a subscription Fail Analyze Design Develop Test Implement Maintain

Plan Implementation – (perform system training and determine implementation method) For this phase, you will discuss how you will implement the system. What kinds of training will occur? What types of user documentation will you create? i.e. user manual? What type of implementation? Give a detailed description of what you will be doing during this phase. Analyze Design Develop Test Implement Maintain

Plan Implementation – In Implementing our new system we will start with hiring professionals with experience using similar systems that will come in and host mandatory workshops for all No Worries LLC employees. Along with these workshops we will create an employees manual that details all of the processes that we will be using and how to properly use them. From the User standpoint, we will launch our systems for customers using a pilot implementation. We will select a small group of people to start using the system. There will be a user manual to assist the small group of users with navigating the system as well as troubleshooting information. Along with the manual we will have a customer service line established to help customers with any unforeseeable issues that may occur. Once the small group has confirmed that the system is operating correctly we will launch it to the public andc migrate all users the system. Analyze Design Develop Test Implement Maintain

Plan Maintenance – (involves performing changes, corrections, additions and upgrades to ensure the system continues to meet the business goals) What do you plan to do to maintain the system/website? Explain the maintenance process as well as plans for future maintenance. How are you going to perform the different types of system maintenance: adaptive, corrective, perfective, preventive (see TextBook Chapter 9). Also include a maintenance schedule. Analyze Design Develop Test Implement Maintain

Plan Maintenance – In this phase we will be performing corrective maintenance during the Pilot Implementation phase. Most, if not all, corrections to the systems shall be made before we have migrated all of our customers to the system. This maintenance will be performed by professional technicians who will monitor the system throughout the implementation phase. Once most of the corrective maintenance has taken place, we will set up a preventive maintenance plan. This maintenance will include making changes to the current system in order to help prevent these issues from reoccurring. This maintenance will provide current and constant reports on the system to help us confirm that the system is operating correctly. Analyze Design Develop Test Implement Maintain

References Should also include a reference page that lists the textbook reference as well as a reference for all other websites visited and any other applicable references. These should be in APA style. Add additional references to your business’s ongoing reference list (remember to alphabetize). Baltzan, P., & Phillips, A. (2011). Appendix D: The Systems Development Life Cycle Basics. In P. Baltzan, & A. Phillips, M: Information Systems (pp. D1-18). New York: McGraw-Hill. Business Driven Information Systems, 5th Edition, Paige Baltzan, Amy Phillips, 2016 McGraw-Hill Higher Education, ISBN-13: 978-0073402987 Doherty, M. J. (2014). About Informatory Inc. - eBookSharing. Retrieved May 2014, from Introduction to Information Management: http://www.uwyo.edu/imgt2400/eBookSharing/default.asp Haag, S., & Cummings, M. (2013). Management Information Systems for the Information Age. New York: McGraw-Hill .