eBookSharing System Development Project Plan

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

2. 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. You should also include the project scope (with a timeline of when different parts will be completed) Design Develop Test Implement Maintain

3. 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

4. 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

5. Plan Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility) EXAMPLE: Project Feasibility: (see Baltzan & Phillips, 2011, pp. D4-5) 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

6. 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 (see Baltzan & Phillips, 2011, pp. D6-8) 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

7. 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 Book [add selected ] Implement BOOK Change Book [change selected ] [ exit selected ] Maintain Prepared: March 2015 Prepared by: Informatory Inc.

8. Plan Design phase (identify the IT infrastructure (client/server, cloud hosted) … ; design the system models) System Model – website layout Analyze Logo Business Name Design Develop Login Instructions Scheduling Menus Pricing Pymt Options Cancel Policy Contact Us Home Body Test Implement Privacy Policy Maintain Comments Contact Us

9. Plan System Model– Navigation (this graphic depicts how navigation occurs on your site – you only need to draw the navigation scheme for your homepage. ) Analyze Design Develop Test Implement Maintain

10. Plan Develop – (develop the database (in your case website) and programs (in your case you will not have any programs) Create Prototype Analyze Design 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

11. 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 Baltzan & Phillips, 2011, pp. D9-12). 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

12. Screen / Form Tested Date Tested Tester Test Condition Expected Results Actual Results Pass Fail (Circle one) Pass Fail Pass Fail Pass Fail Plan Testing – write the test conditions and perform the system testing(see Baltzan & Phillips, 2011, pp. D9-12). Analyze Design Develop Test Implement Maintain

13. 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

14. 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 Baltzan & Phillips, 2011, pp. D15). Also include a maintenance schedule. Analyze Design Develop Test Implement Maintain

15. 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. 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 .