1. Sydney Meyers, Connor Coleman, Gabe Lattimer
Plan
Analyze
Systems Development Life Cycle
Design
The Brush and Brew
Sydney Meyers, Connor Coleman, Gabe Lattimer
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
System requirements – The online login server for Brush and Brew’s online market place allows customers to access their account information, and executives to track account logins and user demographics. The server is also a primary information security area which requires customers to authenticate and authorize access to their individualized account. A password login keeps all payment and personal information safe, and makes an order history available to customers and information management executives. This server will have a LAN network with a large capacity capability. It will be in an accessible format for easy customer operability and use. Individuals begin by using a company security approved password and username that authenticates their access to user information and authorizes access to a secure site. A firewall will also be present to hinder or eliminate possible malicious intruders.
Specific Function Requirements are allowing access to Brush and Brews purchase website, keeping updated customer information including payment and demographic information, storing customer login credentials, accessibility to customer information after authentication.
Design
Develop
Test
Implement
Maintain

3. Project Plan - (identify system for development, what is the problem or opportunity, develop the project plan, identify feasibility)
Plan
Specific non-functional requirement- The scope of this project is fairly extensive as it will store a large amount of information on our customers. It will need at least a year to complete as information will need to be entered into the database and firewalls, security procedures, and e-policy will need to be formed and implemented to ensure full customer security and trust.
Timeline:
December 30th Project budget and goals are formed. Project coordinators and directors are appointed to enforce project goals and deadlines are fulfilled.
January 15th Official start. Project coordinators begin on implementation of project goals and initial procedures.
January 30th Security procedures and e-policies are established and finalized.
February 15th Hire site manufacturers, developers, and designers. Train these team members in our established security protocols and inform of overall project goals.
March 29th Designers begin on creating data flow diagrams for each of the landing pages and security protocols.
June 10th Site manufacturers and developers begin to construct the site and implement security requirements. This step is rather extensive and will take a few months to complete.
August 1st Test the site by allowing a set number of users to register their credentials. This step will not allow users to input sensitive information, as we must first test our security systems to make sure they are up to company and project standards.
September 1st Fix all bugs and security concerns. Ready site for roll out in October.
September 18th Polish and fine tune all aspects of the sites look and design. Make sure no errors occur.
October 1st Website rollout. Make sure that technology support is present to oversee all issues that may occur with server and security errors.
October 15th Project reflection and re-assessment. Note progress and intended changes.
November 1st Implement changes and updates.
December 1st Project re-assessment and reflection.
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)
Schedule Feasibility- The Brush and Brew will begin by appointing project managers and project coordinators to form and maintain a project schedule and enforce project deadlines for the login system. These specialized team members will be highly organized and maintain a positive workflow to ensure that each objective is performed in a logical and sequential manner. A strict work timeline will be kept, maintained and updated as objectives are completed. Reflections on work that has been completed will be essential to ensure that quality standards are upheld in the limited one year timeframe set to complete the project.
Technical Feasibility- The Brush and Brew will hire responsible and knowledgeable designers, manufacturers and developers that have experience in building safe and secure data storage for other companies. These professionals will be responsible for the company’s technical ability to deliver a top of the line website sign-up and login process that is easy to use and responsible. Requirements will include a secure server, a firewalled database and other security measures to ensure that we are one of the safest marketplaces on the internet.
Analyze
Design
Develop
Test
Implement
Maintain

5. Analysis Plan Analyze Design Develop Test Implement Maintain
Brush and Brew’s business process steps will include logging into site taking demographic information, allowing users to create personal login credentials, purchase products and services, accessing purchase history, access to personal user information. Parties involved in these processes are the users, information technology personnel, an information technology coordinator, information analysts, an Information Management Coordinator (to coordinate analysts).
Analyze
Design
The user will be directed to a login page from the home page of the website. The login page will be on a secure site and will only include a form for a login ID and a login password to promote ease of use.
User will input their individualized and specific login information into the form and hit enter sending this information through the server to the database. The server will then access the database and find the user information specific to the entered login information.
User information will be sent through the server to the user for user access and availability.
Once login is authenticated, user is free to shop and interact with the rest of the site as an authenticated customer with product views and purchases sent to the database and stored for future access.
Develop
Test
Implement
Maintain

6. Customer Sign-up Process
Plan
Customer Sign-up Process
Analyze
Brush and Brew Website
Design
Sign-up link
Customer Storage
[press button]
Develop
Enter personal information
Return to Website
Customer will access the sign-up link off of the home page of the website.
This will send them to a sign-up page where they will input information. Name, age, location, gender, login ID, login password, password verification, and , will be the information collected. User will send information to the system database and confirmation will be sent for verification. User has the option to return back to website if they don’t wish to enter any information
User will verify through and will then be sent a link to the login page.
[press button]
Test
Automated System
Verified and sent
Implement
Login
Maintain
Prepared: March 2017
Prepared by: Brush and Brew

7. Customer Login-in Process
Plan
Customer Login-in Process
Analyze
Brush and Brew Website
Design
Login-in link
Customer Information
[press button]
Develop
Enter personal information
Return to Website
Customer Verification
Customer will access the sign-in link off of the home page of the website.
This will send them to a sign-up page where they will input their login ID, login password. will be the information collected. User will send information to the system database and database will verify user credentials. User has the option to return back to website if they don’t wish to enter any information or after account has been verified and accessed.
User can also access all account information upon verification.
[press button]
Test
Send
User Verified
Implement
Account Access
Maintain
Prepared: March 2017
Prepared by: Brush and Brew

8. System Model – website layout
Plan
Design phase
System Model – website layout
Analyze
Comments & Concerns
New Customer
Logo
Brush & Brew
Design
Develop
Home Coffee Art Videos Locations Login
News & Events
Photo of the week
Seasonal Deals
Test
Product of the month
Implement
Your Local store
Contact us
About Us
Privacy Policy
Maintain

9. Plan
System Model– Navigation
Analyze
Design
Develop
Test
Implement
Maintain

10. The Brush and Brew Seasonal Deals Your Local Store
Home Coffee Art Locations Log In
News & Events
New Store opening in Laramie Wyoming Soon
Check out our new Thanksgiving painting videos that the whole family would enjoy
All Stores will be closed thanksgiving day and open Friday
Photo Of The Week
Seasonal Deals
Your Local Store
About us - Contact us - New Customers - Comments & Concerns- Privacy Policy

11. Testing – Plan Analyze Design Develop Test Implement Maintain
User Acceptance Testing- Sample users navigate the website pages looking for design or operational flaws with the overall website. The company then fixes these flaws and moves to another round of user testing.
Development Testing- The website and system links are tested for bugs and possible dead ends. This would take place throughout the development process and continue into the testing process. This is a test that would test conditions that were pass or fail.
Integration Testing- Test and make sure that the site can communicate with the customer database and that the customer database can communicate with our registry, and our verification system. This will focus on making sure that our communication between systems is adequate.
Hacker Testing- Although this is not one that is mentioned in the book, we as a company believe that the best way to create a secure system and database of information is to bring in an expert hacker to see where our vulnerabilities lie and where our security policies and procedures can be strengthened.
Analyze
Design
Develop
Test
Implement
Maintain

12. Brush and Brew Home Page System
Plan
Testing –
Screen / Form Tested
Date Tested
Brush and Brew Home Page System to
Tester
BK and Tyler
Test Condition
Expected Results
Actual Results
(Circle one)
Log in
Pass Fail
Home
Art Videos
Location
Analyze
Design
It would take you to the log-in page
It took us to the log-in page
Develop
Refreshed or bring us back to the home page
It didn't’ to anything
Test
Play art videos that we uploaded
Videos did not have sound
Implement
Can locate the users location
It located my locations
Maintain

13. Implementation – Plan Analyze Design Develop Test Implement Maintain
Implementation of our project will take approximately two weeks after the testing phases are complete. Our staff members who work in information technology and our system analysts will be trained to operate our systems, on our company e-policies, recognition of data breaches, emergency procedures, and maintenance procedures. These trainings will be a combination of face to face lectures, online tutorials and labs. The face to face lectures will be more focused on understanding the importance of these procedures and the personal side of operating a security system. The online courses will be more focused on the technical aspects of operating our system and the labs will focus on the confidential or delicate aspects of the system operations.
Documentation needed to implement will be a user guide to be featured in the help button of our page, a set of e-policy documents that employees are responsible for knowing and implementing in their daily work, and a project and company mission statement that will keep a general sense of what is trying to be achieved through the implementation of this project.
The plunge system is the implementation system that we will require as we want all users to understand how our website works and where on the website they can access their user information. It also lets customers know that we are implementing a system that takes security seriously and will change to make sure that our customers are safe. Although this may anger some customers we feel like this is the best way to ensure the safety of our customer information.
Analyze
Design
Develop
Test
Implement
Maintain

14. Maintenance – Plan Analyze Design Develop Test Implement Maintain
We will use our information technology staff and our information management team to monitor daily operations while detailing any concerns or problems that the system may incur on more of an operational basis. We will also use our CRM as well to make sure that operational maintenance occurs at a more constant rate. In our project schedule we have also scheduled dates after implementation where company management will meet with IT and our system analysts to review the short term maintenance that will occur on a month by month basis. We have scheduled these meetings to be bimonthly in the months following our implementation to ensure the immediate success of the project. There will also be meetings with executives on a quarter by quarter basis to measure the overall success of the project and to decide whether the system is worth maintaining.
Adaptive-These are changes that will be implemented by our CRM system and our IT specialists. They will include making sure that our security measures are holding up and that they don’t need an extensive overhaul.
Corrective- This is also the IT department which will fix issues as they arise. If needed, system developers will be called in to address any large issues.
Analyze
Design
Develop
Test
Implement
Maintain

15. Maintenance – Plan Analyze Design Develop Test Implement Maintain
Perfective- This will be the maintenance that will occur during the short and long term maintenance meetings. This is the re-assessment of the entire project and what larger steps can be taken to make the system a better and more effective system for our customers.
Preventative- These are also changes that will be decided more in the monthly meetings as they will focus more on the near future and how the company can support the changing nature of technology.
Schedule of Maintenance-
Constant maintenance by the CRM that we purchased earlier.
Daily maintenance by the IT staff and system analysts.
Monthly Maintenance by Company Management and Information Technology Coordinators
Quarterly Maintenance by Company Executives and Company Managers
Analyze
Design
Develop
Test
Implement
Maintain

16. References
Batlzen, 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.
Baltzan, P. (2012). Business Driven Information Systems (5th ed.). New York, NY: McGraw Hill.