Warda Abbas

19-ARID-490
Software Engineering
Assignment # 2
Submitted to Sir Usman Karim

Table of Contents
The Spiral Model …………….……………………………………………………………….....2
Objective setting ………………………………………………………………………………...2
Objective .………………………………………………………………………………………...2
Alternative Solutions ….………………………………………………………………………...2
Risk assessment and reduction ……………………………..……………………………….….2
Risk of Google Chrome….………………………….…………………………………………...2
Solutions of risks in Google Chrome….………………………………………………………...2
Development and validation ………….………………………………………………………...2
Requirement for Google Chrome….………….………………………………………………...2
System design for Google Chrome….…………...……………………………………………...2
Implementation for Google Chrome….………………………………………………………...3
Testing for Google Chrome….……………………………..…………………………………...3
Installation for Google Chrome….……………………………………………………………...3
Maintenance for Google Chrome….……………………….…………………………………...3
Review &Planning …..………………………………………………………………..………...4
Google Chrome User Ratings………………………………………………………..……….....4
Google Chrome upcoming versions……………………………………………..………............5

1
 The Spiral Model

1) Objective setting
Specific objectives for the phase are identified.
Example:
Objective: Organize the world's information and make it universally accessible and useful.
Alternative Solutions: Google Chrome.
2) Risk assessment and reduction
Risks are assessed and activities put in place to reduce the key risks.
Example:
Risks of Google Chrome:
 Can access not just to your search history, but also your browser history.
 Serves annoying ads via Chrome, ads may contain virus.
 Could choose to sell the data they collect instead of protecting it.
 Could use your webcam/microphone to spy on you, or collect more data.
Solutions of risks in Google Chrome:
 Avoid dangerous websites.
 Always have the latest security.
 Security for now, and the future.
3) Development and validation
A development model for the system is chosen which can be any of the generic models.
Example:
Requirement for Google Chrome:
Browser for accessing the World Wide Web and running Web-based applications.
System design for Google Chrome:
 OS:
Win Xp 32

2
  Processor:
Intel Celeron 1GHz / AMD Duron 2.0GHz
 Graphics:
AMD Radeon Xpress 1200 Series or NVIDIA GeForce FX 5200
 System Memory:
128 MB RAM
 Storage:
100 MB Hard drive space
 DirectX 9 Compatible Graphics Card
 Windows:
Windows 7, Windows 8, Windows 8.1, Windows 10 or later.
An Intel Pentium 4 processor or later that's SSE3 capable.
 Mac:
OS X El Capitan 10.11 or later
 Linux:
64-bit Ubuntu 14.04+, Debian 8+, openSUSE 13.3+, or Fedora Linux 24+
An Intel Pentium 4 processor or later that's SSE3 capable
 Android:
Android Lollipop 5.0
Implementation of Google Chrome:
 Engines: WebKit
 Operating systems: Android, Microsoft Windows, Chrome OS,Linux,Mac.
 Programming languages: Java, C, C++
Testing of Google Chrome:
General test for following:
 One box for everything (separated or combined search box and the URL bar)
 New Tab page
 Application shortcuts
 Dynamic tabs
 Incognito mode
 Safe browsing
 Instant bookmarks
Installation of Google Chrome:
1. On your Android phone or tablet, go to Chrome on Google Play.
2. Tap Install.
3. Tap Accept.
4. To start browsing, go to the Home or All Apps page. Tap the Chrome app.
Maintenance of Google Chrome:
Clear history, cache, and cookies to make sure Google Chrome does not get slowed down.
Updated versions:
1. Version 8.9:
 "A number of fixes and improvements."

3
  WebHID, WebNFC, and Web Serial are now available
 Closed a loophole a few developers used to skirt the PWA installability checks
 The arrival of Web Share and Web Share Target
 Chrome now allows top level await within JavaScript modules
 Updated icon shown in the omnibox for installable PWAs
 Allowed users to sign up for the Digital Goods API origin trial if they have used a
Trusted Web Activity to make their PWA available in the Play Store for Chrome OS
 Removal of legacy prefixed events (webkitprerenderstart, webkitprerenderstop,
webkitprerenderload, and webkitprerenderdomcontentloaded) dispatched on <link
rel=prerender>
 Stopped cloning sessionStorage for windows opened with noopener number
 Dropped support for older x86 processors that don't support SSE3
Android version:
 "Stability and performance improvements."
2. Version 8.8:
 "A number of fixes and improvements."
 Users can now upload extensions using manifest v3 to the Chrome Web Store
 CSS aspect-ratio property
 Heavy throttling of chained JavaScript timers
 Play billing in Trusted Web Activity
 To conform to a change in the HTML standard, anchor tags with target="_blank" will
now imply rel="no-opener" by default
 Pointer Lock API allows users to disable mouse acceleration
 addEventListener now takes an Abort Signal as an option
 No popups during page unload (enterprises)
 Web Components v0 removed
 Dropped support for OS X Yosemite
 FTP support removed
Android version:
 "Stability and performance improvements."
iOS version:
 Chrome 88 has been skipped over due to many Google products not updating in iOS
since November 2020.
4) Planning
The project is reviewed and the next phase of the spiral is planned.
Example:
Google Chrome User Ratings:
 Ease of Use: 9.5
Browser Average: 9.1
 Quality of Support: 8.9
Browser Average: 8.0
 Ease of Setup: 9.2
4
 Browser Average: 9.0
 Performance 75 %
 Features 90 %
 Security 95 %
 Privacy 40 %
Google Chrome upcoming versions:
 Current Canary channel 9.1
 Current Dev channel 9.1
 Current Beta channel 9.0