1 / 10

Chapter 18 Analysis for WebApps

Chapter 18 Analysis for WebApps. 18.1 Requirements Analysis for WebApps. Major Tasks Formulation Requirements Gathering Analysis Modeling. 1/9. SafeHomeAssured.com user. guest. registered user. customer service staff. new customer. existing customer.

audra
Download Presentation

Chapter 18 Analysis for WebApps

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. Chapter 18Analysis for WebApps

  2. 18.1 Requirements Analysis for WebApps • Major Tasks • Formulation • Requirements Gathering • Analysis Modeling 1/9

  3. SafeHomeAssured.com user guest registered user customer service staff new customer existing customer 18.1 Requirements Analysis for WebApps • Formulation: goals & objectives + categories of users The User Hierarchy 2/9

  4. Describe home layout Peruse descriptive content <<include>> Customize SafeHome Select SafeHome components <<include>> Save configuration <<include>> Log-in to SafeHomeAssured.com new customer Customization functionality View Shopping cart <<include>> Purchase configuration Provide Purchase data <<include>> Recalled saved configuration Complete SafeHome order <<include>> E-commerce functionality 18.1 Requirements Analysis for WebApps package • Use-Cases: for each user category (informal) Comprehensible, cohesive, loosely coupled, and hierarchically shallow 3/9

  5. 18.2 The Analysis Model for WebApps • Content Analysis. The full spectrum of content to be provided by the WebApp is identified, including text, graphics and images, video, and audio data. Data modeling can be used to identify and describe each of the data objects. • Interaction Analysis. The manner in which the user interacts with the WebApp is described in detail. Use-cases can be developed to provide detailed descriptions of this interaction. • Functional Analysis. The usage scenarios (use-cases) created as part of interaction analysis define the operations that will be applied to WebApp content and imply other processing functions. All operations and functions are described in detail. • Configuration Analysis. The environment and infrastructure in which the WebApp resides are described in detail. 4/9

  6. MarketingDescription Photograph partNumber TechDescription partName Schematic component partType Video description price WholesalePrice RetailPrice 18.3 The Content Model • Content Objects: extracted from use-cases • Content Relationships and Hierarchy: ERD or … Data Tree • Analysis Classes: grammatical parse for each use-case 5/9

  7. 18.4 The Interaction Model • Composed of 4 elements: • use-cases • sequence diagrams • state diagrams • a user interface prototype 6/9

  8. 18.5 The Functional Model • Processing Elements of the WebApp • user observable functionality that is delivered by the WebApp to end-users • the operations contained within analysis classes that implement behaviors associated with the class • Tool: activity diagram 7/9

  9. 18.6 The Configuration Model • Server-side • Server hardware and operating system environment • Interoperability considerations • Appropriate interfaces, communication protocols and related collaborative information • Client-side • Browser configuration issues • Testing requirements 8/9

  10. 18.7 Relationship-Navigation Analysis • Relationship-Navigation Analysis (RNA) • Stakeholder analysis—identifies the various user categories and establishes an appropriate stakeholder hierarchy • Element analysis—identifies the content objects and functional elements that are of interest to end users • Relationship analysis—describes the relationships that exist among the WebApp elements • Navigation analysis—examines how users might access individual elements or groups of elements • Evaluation analysis—considers pragmatic issues (e.g., cost/benefit) associated with implementing the relationships defined earlier 9/9

More Related