Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 2: Requirements Engineering for Web Application - Coggle Diagram
Chapter 2: Requirements Engineering for
Web Application
DEFINITION
Process of analyzing, documenting and validating the requirements of the software
GOAL
To make a software requirements specification (SRS) document
RE PROBLEMS
Poor user acceptance
Unsuccessful plans
Complex architecture
RE BENEFITS
Avoid time slippages and cost overruns
Lack of experience people in Web projects
RE CHALLENGES
Satisfy the stakeholders
Reconciling stakeholder's objective
Different range of skills and experience of developers
TYPES OF REQUIREMENTS
Functional Requirements
To define a system's capabilities and services
For Examples:
Functionality
Maintainability
Traceability
Consistency
Unambiguity
Non-Functional Requirements
Define the desired level of quality. Range from user interface look and response time requirements to security issues.
Examples Issues:
Quality attributes
Constraints
Goals
Non-behavioral requirements
RE ACTIVITIES: Process, Planning and Design
Umbrella Activities
A procedure that web engineering team follows to maintain the progress, quality, change and risks of the overall development task
Activities
Elicitation
Documentation
Verification & Validation
Requirements management
RE SPECIFICS IN WEB ENGINEERING
Difference between RE in traditional / conventional Software Engineering (SE)
Multidisciplinary
Non-availability of stakeholders
Volatility of requirements
Dynamic operational environments
Affects of old system
Importance of quality factors
Quality of content
Lesser developer experience
Rigid delivery dates
Vulnerability issues
PRINCIPLES OF RE IN WEB APPLICATIONS
Analyze The Present Business Scenario
Stakeholders Feedback and Involvement
Iterative Approach of Requirements Definition
System Architecture
Risk Identification
TYPES OF REQUIREMENTS
Web Functional Requirements
Content Requirements
Quality Requirements / Non-Functional Requirements
Environment of System-based Requirements
GUI-related Requirements
Evolution Requirements
Constraints on the Project
NOTATIONS & TOOLS FOR RE
NOTATIONS
Stories
Unique Identifiers given to all of the requirements
Use case method (as given by Cockburn)
Standards like IEEE SRS Std. 830 (ISO also gives some standards)
TOOLS
Analysis Tools help software engineer in creating system models
Contain a model representation of data, function and behavior as well as classify it as data, architectural, procedural and interface design.
Analysis tools provide a quick and better solutions so that errors do not propagate into the design phase.
CONCLUSION
The process of gathering, analyzing, categorizing and modelling the requirements of web users are known as Requirement Engineering.
RE is mandatory otherwise, certain requirements are missed out and resulting in customer dissatisfaction.