Chapter_1_Web Based Systems_cse_iubat.pptx

Chapter_1_Web Based Systems_cse_iubat.pptx

• 1.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 1 Web Engineering: A Practitioner’s Approach by Roger S. Pressman and David Lowe copyright © 2009 Roger S. Pressman and David Lowe
• 2.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 2 Web Development VS Web Engineering Aspect Web Development Web Engineering Focus Creation and implementation of websites Design, architecture, and lifecycle of web systems Scope Primarily technical (frontend and backend) Encompasses architecture, design, testing, and maintenance Process Focus on coding and delivering a functional product Structured methodology, system design, and ongoing maintenance Skills Coding languages, frameworks, version control Engineering principles, architecture design, optimization, management Goal Build working websites and applications Create scalable, maintainable, and efficient systems
• 3.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 3 Chapter 1: Web-Based Systems ■ In the early days of the Web, we built systems using informality, urgency, intuition, and art ■ Informality leads to an easy work environment—one in which you can do your own thing. ■ Urgency leads to action and rapid decision making. ■ Intuition is an intangible quality that enables you to “feel” your way through complex situations. ■ Art leads to aesthetic form and function—to something that pleases those who encounter it. ■ Problem is—this approach can and often does lead to problems
• 4.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 4 But Why? ■ As WebApps become larger and more complex, ■ Informality remains, but some degree of requirements gathering and planning are necessary ■ Urgency remains, but it must be tempered by a recognition that decisions may have broad consequences ■ Intuition remains, but it must be augmented by proven management and technical patterns ■ Art remains, but it must be complemented with solid design ■ We must adapt the old-school approach to the realities of a Web 2.0 world
• 5.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 5 And What’s the Response? Web Engineering
• 6.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 6 The Web ■ An indispensable technology ■ In virtually every aspect of modern living ■ A transformative technology ■ Changes the way we do things ■ Changes the way we acquire and share or spread information ■ An evolving technology ■ Bottom line—high impact on everyone in the modern world
• 7.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 7 How The Web Affects Us? ■ E-commerce (buying products online) ■ Portals (helping us understand the world) ■ Online media (getting news and updates) ■ Blogs (voicing opinions) ■ Entertainment (from music to online casinos) ■ Online learning (education via the Internet)
• 8.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 8 WebApps ■ The term Web application (WebApp) encompasses: ■ everything from a simple Web page that might help a consumer compute an automobile lease payment to a comprehensive website that provides complete travel services for business people and vacationers. ■ Included within this category are complete websites, specialized functionality within websites, and information- processing applications that reside on the Internet or on an Intranet or Extranet.
• 9.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 9 WebApps ■ A Web application (WebApp) is a software that takes raw information from different sources, organizes it, and presents it to you in an aesthetic and interactive way. It structures the information so that it’s easy for you to understand and use. ■ When you interact with a WebApp, you're either: ■ Passively consuming information (like reading a news article or browsing a website) without being able to change the content. ■ Actively engaging with the content (like customizing a product on an e-commerce site or interacting with a form) to tailor it to your specific needs.
• 10.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 10 What Web-based Systems Include? ■ Client hardware (your device, like a computer or smartphone) ■ Server hardware (the backend infrastructure storing and processing data) ■ Operating systems (software that manages your device and server) ■ Network software (connects you to the internet) ■ Web browsers (like Chrome, Firefox, Safari)
• 11.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 11 Evolution of Web Aspect Web 1.0 Web 2.0 Web 3.0 Web 4.0 Content Static Dynamic Semantic, Personalized Fully Immersive, Real-time User Interaction Very limited Active interaction Contextual, AI- powered Predictive, seamless Technology HTML, Basic CSS HTML5, CSS3, JavaScript Blockchain, AI, VR/AR IoT, Advanced AI, NLP Example Applications Simple websites Social media, blogs, e- commerce Decentralized apps, AI-driven services Real-time systems, virtual assistants Main Goal Provide information Enable user engagement Interconnect and decentralize data Seamless, predictive, real- time web Design Simple, text- based Rich, interactive UIs Data-driven, immersive UIs Fully immersive, intuitive
• 12.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 12 Webapps and Software Are Webapps really a software?
• 13.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 13 Yes, WebApps are software ■ Set of Instructions (Code-Based) ■ Data Handling ■ Functionality ■ User Interaction ■ Data Storage & Logic ■ Cross-Platform ■ Updates & Maintenance
• 14.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 14 How Webapps Differ From Conventional Software Aspect Web Applications (WebApps) Conventional Software Delivery Accessed via a browser, no installation needed Installed on a specific device, platform- dependent Updates Automatically updated on the server Manual updates by the user or IT department Internet Dependency Requires an active internet connection (unless offline mode) Can operate offline once installed Platform Platform-independent, accessible from any device with a browser Platform-dependent (e.g., Windows, macOS) Performance May be slower due to network dependency Generally faster as it runs locally on the device Maintenance Server-side maintenance and security updates Requires local management and security
• 15.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 15 WebApp Attributes ■ Network Intensive -Operate over wide area networks; must handle varying conditions. ■ Concurrency -Handle multiple simultaneous users efficiently. ■ Unpredictable Load -Manage fluctuating user traffic with scalable infrastructure. ■ Performance -Must ensure fast response times to maintain user satisfaction. ■ Availability -Require high uptime for constant access. ■ Data-Driven -Centralized, dynamic content with efficient data handling.
• 16.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 16 WebApp Attributes ■ Content Sensitive -Content quality impacts engagement; requires frequent updates. ■ Continuous Evolution -Rapid updates and new features with continuous integration. ■ Immediacy -Agile development cycles for quick deployment. ■ Security -Securely designed with strong data protection and encryption. ■ Aesthetic and UX-Focused -User interaction is critical, must be visually appealing and intuitive.
• 17.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 17 WebApp Types ■ Informational -Provide static or dynamic information to users. ■ Download -Allow users to download files or content. ■ Customizable -Offer user customization options for interface or features. ■ Interaction -Enable user interaction (e.g., chat, forms). ■ User input -Collect and process user input (e.g., surveys, forms).
• 18.
  These slides aredesigned to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009 18 WebApp Types ■ Transaction-oriented -Support transactions like online shopping or banking. ■ Service-oriented -Provide specific services, often in a microservices architecture. ■ Portals -Centralized access point for services and information. ■ Database access -Allow users to query and interact with databases. ■ Data warehousing -Manage large data volumes for analysis and reporting. (see http://digitalenterprise.org/models/models.html for examples)