1 / 29

Web Systems I

Web Systems I. ITWS 2110 & CSCI 4961 - Fall 2013. Who?. Instructor : Richard M. Plotka Office location: Amos Eaton Room 133 Telephone number: (201)-214-6061 Office hours: Mondays 6-8 PM, Thursdays 2:30-3:30 PM E-mail address: plotkr2 @rpi.edu Skype : shen.lung

mikayla-washington
Télécharger la présentation

Web Systems I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Systems I ITWS 2110 & CSCI 4961 - Fall 2013 Web Systems I - Fall 2013

  2. Who? • Instructor: Richard M. Plotka • Office location: Amos Eaton Room 133 • Telephone number: (201)-214-6061 • Office hours: Mondays 6-8 PM, Thursdays 2:30-3:30 PM • E-mail address: plotkr2@rpi.edu • Skype : shen.lung • LinkedIn & FB & G+ : rplotka@tsi400.com • Teaching Assistant: KarthikAbimanyu • TA office location: ITWS Lab – Lally 205 • TA office hours: Wed 2:00-4:00pm • TA e-mail: abimak@rpi.edu Web Systems I - Fall 2013

  3. What? Where? • Web Systems I : ITWS 2110 & CSCI4961 • Lally Hall Room 104 Web Systems I - Fall 2013

  4. When? How? • Mondays and Thursdays from 4:00 PM to 5:50 PM • New format – 2 1:50 classes – separate lab is no more! • Mondays : Lectures (generally) • Thursdays : Labs (generally) • Labs must be submitted by midnight before next Thursday class. • Labs will be done individually, but you may collaborate with your group : more on this... • Homework • 2 Quizzes – No Final • Term Project – group presentations : more on this ... Web Systems I - Fall 2013

  5. Introduction to the course • Syllabus • Course Structure • Requirements/Expectations • Course Content • Term Project • Groups Web Systems I - Fall 2013

  6. Introduction to the course • Course Structure • Lectures • Labs/Homework • Quizzes • Final Projects • Discussion Board Web Systems I - Fall 2013

  7. Expectations • Come to class prepared • Participate • Contribute to your groups/teams • Laptops a must. We will be loading and configuring software tools to facilitate the labs, homework and quizzes • Collaboration vs. Plagiarism – Ethics – give credit where credit is due • Remember – Individual assignments (quizzes) are not collaborative – but will be open Internet. Web Systems I - Fall 2013

  8. Content • How Web servers work • Data on the Web (HTML ,XHTML, XML, JSON) • Presentation on the Web (CSS, JavaScript, jQuery, AJAX) • Front-end development workflow • Back-end (server-side) programing (PHP, MySQL) • Back-end development workflow • Tying it all back together (Web Services, APIs, Security, etc) Web Systems I - Fall 2013

  9. We will touch on • Modern Web architecture • Development tools and technologies • Development methodology • Software versioning • Entrepreneurship Web Systems I - Fall 2013

  10. Tools • Tools • Applications or browser add-ons which aid in the development process • Good tools tend to stick around, bad ones disappear quickly. • All tools and technologies evolve • We will cover the technologies, but also what they are intended to do Web Systems I - Fall 2013

  11. Some tools we will use in this class • AMP – (Apache, My SQL, PHP) – common suite of applications which allow for web application deployment – but the theory used here is applicable to other web suites. • Chrome • Chrome developer tools Web Systems I - Fall 2013

  12. Term Project Assignment • Google. Facebook. Reddit. Many of the ubiquitous websites we use today have one thing in common: a small team of dedicated individuals decided to put their skills to the test and bring their vision from concept to completion. Now, it's your turn. • Rather than developing a project according to a spec that we provide, you will be providing the concept for a new website that meets a general set of guidelines as a project proposal (by the time this proposal is due, you will have the skills you need to begin development, along with a plan on how to proceed).

  13. Term Project Assignment • Your proposal must provide: • The name of your team, and the names of its members (Teams have been randomly assigned in groups of 5). • Summary of your proposed project • Description of each type of user and stakeholder, and how the site generates value for each • A summary of the technologies you intend to use • Any functional and non-functional requirements • An estimated project schedule • A site map demonstrating the basic structure of your site • Two wireframes of pages that help to demonstrate the intended functionality • Term Project Proposals: Due Monday, November 4, 2013, 11:59:59pm

  14. Term Project Assignment • At minimum, your project must meet the following requirements: • Functional (not necessarily identical) in the following browsers... • Chrome (latest) • Firefox (latest) • Safari (latest) • Internet Explorer (7, 8, 9) • Compatible with PHP 5.3, MySQL 5.x, Apache 2.2. Other stacks must be approved in advance.

  15. Term Project Assignment • Your application must make use of the following in a non-trivial way... • Valid semantic markup (HTML 4.01 Strict, XHTML 1.0 Strict, HTML5) • Valid CSS (browser prefixes excepted) • Client-side scripting (JavaScript) • Server-side programming (PHP) • Database Connectivity • Your application must support the notion of authentication and authorization (logging in and user roles/permissions). • Your application must provide an easy means for administrative users to maintain it, without knowledge of the underlying technology. • Your application must be easy to install, maintain and extend by future developers • Your site must address all seven of the facets of user experience as discussed in class. Things like making the experience visually desirable and ensuring find ability do count!

  16. Term Project Assignment • Resubmitting Proposals • If your proposal received less than full credit and has issues that need to be addressed, your team may resubmit one week after receiving it with the appropriate changes. The proposal will be re-graded, and the new grade will replace the old. • Term Project Presentations: In Class, December 2nd & 5th, 2013 • During the last week of classes, teams will demonstrate their projects for the rest of the class, fielding questions from the instructors, TAs and fellow students about the site and its underlying implementation. Signups for presentations will occur in the order in which proposals are approved (so the team that gets their proposal approved first may choose their presentation time slot first). • Presentations are limited to 15 minutes, and should include a brief introduction to the project, the specifics of the underlying implementation, and a brief demonstration of its functionality.

  17. Term Project Assignment • Completed Term Project & Documentation - Due Thursday, December 5, 2013, 11:59:59 PM • In addition to all of the code, your team must provide documentation for future developers of the site. This documentation must provide a complete breakdown of the various different components of your site and how the project is organized. An equally skilled developer should be able to reference this documentation to determine where and how to make changes to different aspects of the site if necessary. This documentation should also include any installation and configuration instructions - we will be following it when grading your projects. • Finally, the final submission should include a listing of each team member's contributions to the project (in Word, OpenOffice, or plain text format) called CREDITS. • Grading • All team members will receive the same grade for the project. Team members who do not significantly contribute to the project will not receive a grade. • Project Proposal – 20% • Functionality, UX and Overall Execution - 30% • Quality of Code & Markup - 30% • Documentation - 10% • Final Presentation - 10%

  18. Term Project - Dates • Teams of 5 persons have been randomly assigned • Teams submit proposal by Nov 4th. • Teams make Term Project Presentations on Dec 2 and Dec 5 • Teams submit Term Project Final Report on Dec 5

  19. Groups • Randomly assigned • Work in teams to define and create term project • Suggest you work together for labs Web Systems I - Fall 2013

  20. Groups Web Systems I - Fall 2013

  21. Let’s get started • What is Web Development? • All of the work involved in the planning, development and maintenance of systems designed to operate over Hypertext Transfer Protocol (HTTP) • This is very broad Web Systems I - Fall 2013

  22. Web Development is Multidisciplinary • A full team is often involved in the development of a website • Involved from Planning, development, delivery and maintenance – beginning to end • What are some of the disciplines involved in Web Development? Web Systems I - Fall 2013

  23. Disciplines... • System Administration • Socket Programming • Data Modeling • Information Architecture • Content Strategy • Usability Engineering • Database Administration • Analytics • Information Security • Information Design • Content Creation • Search Engine Optimization (SEO) • Server-side Programming • Client-side scripting • Network Administration • Quality Assurance • Marketing • Visual Design • Project management • Systems programming • Data Science/Big Data • Network performance • Data Performance • Subject Matter Expertise Web Systems I - Fall 2013

  24. It is Complicated • Many disciplines involved to get it right • Many Players/Stakeholders involved (Project management, business, technology, end users, etc...) • Many tools to choose from – always changing • Many competitive technologies to choose from – very dynamic • Many different platforms – different experiences • Mac vs Windows vslinux • iOSvs Android vs ? Web Systems I - Fall 2013

  25. Disruptive Technology • What is disruptive technology (or disruptive innovation)? Web Systems I - Fall 2013

  26. Disruptive Technology • Innovations cause disruption • What is disruptive innovation? • A disruptive innovation is an innovation that helps create a new market and value network, and eventually goes on to disrupt an existing market and value network, displacing an earlier technology” http://en.wikipedia.org/wiki/Disruptive_innovation • What gets disrupted? • Social • Economic • Cultural • Political • Ethical Web Systems I - Fall 2013

  27. Examples of Disruptive Innovation Web Systems I - Fall 2013

  28. Examples of Disruptive Innovation • Cable TV • New economy for non-network content prviders • Duck Dynasty? • High Speed Internet • Old Dial-ups disappear • Cable companies struggle to keep up with Fiber • iPod/iPhone/iPad/iTunes? • Pay a subscription fee to hold your music • Google Play Music? • Pay a subscription fee to get any music you want Web Systems I - Fall 2013

  29. Questions? Web Systems I - Fall 2013

More Related