Handling Requirements for Web-Based Applications, Explained

UPI Study › Courses › Software Engineering › Free lessons › Lesson 7.5 Free with a free account

Handling Requirements for Web-Based Applications

Software Engineering · Chapter 7: Behavioral Models and Requirements AnalysisSection 7.5 · lesson 51 of 1036 min · free with a free account

← Breaking Down Requirements: Classes, Functions, and BehaviorsNext lesson: Visualizing Object Interactions with UML Sequence Diagrams →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Content, interaction, navigation, and configuration.

  • Explain why web applications need their own requirement categories
  • Describe content and interaction requirements
  • Explain why navigation carries extra weight on the web
  • Separate configuration requirements from implementation

Transcript

Everything said in the video, section by section (825 words). Read along, or search it.

Behavioral Models and Requirements Analysis

Handling Requirements for Web-Based Applications

A web application has to define what it presents, how people interact with it, how they move around inside it, and what conditions it has to keep working under. A general requirements conversation can easily gloss over all four. This section covers the four categories used to make sure a web application does not.

Why Web Is Different

What General Elicitation Misses

Several things about web applications do not surface naturally through general elicitation on its own. Content has to stay organized and current. Interaction patterns are shaped by the browser itself. The navigation structure has to be deliberately designed, rather than assumed. And behavior has to hold up across environments the team does not fully control. So web requirements are commonly organized into four categories. They are an additional lens, applied on top of general elicitation, not a replacement for it.

The Categories

4 Complementary Categories

Here are the four categories. Content covers what is presented, and how it is kept current. Interaction covers how users provide input, and manipulate content. Navigation covers how users move through the application. And configuration covers what environments and conditions the application must handle. Each one catches something a general requirements pass tends to miss.

Content Requirements

What the Application Presents

Content requirements cover the text, images, video, and data an application actually presents. They also cover where that content comes from, how it is organized, and how it stays current. They ask questions a general pass can easily skip. Where does this content come from, and who is responsible for keeping it accurate? How is it categorized or structured? And what should happen when content is temporarily unavailable, out of date, or missing entirely?

Interaction Requirements

What Users Can Do

Interaction requirements describe how a user engages with the application. That means the forms, buttons, search boxes, and any other way they provide input, or manipulate what is on the page. For the web, this has to cover a wide range of input methods. Touch, mouse, and keyboard. It also has to cover behaviors that only make sense inside a browser. What does the back button do? What happens on a page refresh? And what should happen if the same application is open in two tabs at once?

Navigation Requirements

Close to the App's Actual Structure

Navigation requirements capture how a user moves between different parts of an application. For the web, navigation is close to being the application's actual structure, not just a way of getting around it. These requirements specify what paths must exist, how a user finds their way back, and what happens when someone lands on a page out of sequence. Navigation carries unusual weight here, because a user can arrive at almost any page directly. Through a search result, a shared link, or a bookmark. A desktop application rarely has to plan for someone arriving at a random internal screen from outside.

Configuration Requirements

An Environment You Don't Control

Configuration requirements capture a reality most other software faces far less. A web application has little control over the environment it runs in. These requirements define which browsers and versions must be supported. They define what should happen under poor or variable network conditions, and any behavior that differs across deployments. What is captured here is the requirement itself. What has to work, and under which conditions. The technique for adapting a layout across screen sizes is a separate, later topic.

Table 1

The 4 Categories at a Glance

Here are the four categories, each with an example. Content asks where something comes from, and who keeps it current. For example, product descriptions sync nightly from the inventory system. Interaction asks how a user gives input. For example, search results update as the user types, without a page reload. Navigation asks how a user moves through the app from any starting point. A product page reached from a search link still shows full site navigation. And configuration asks what conditions it must work under. It stays usable on an older phone browser, with a slow connection.

Why This Matters

What Must Be True, Not How to Build It

All four categories describe what must be true, not how to build it. For example, a configuration requirement might say a layout must stay usable on a small screen. The technique for actually building that adaptive layout is a separate, later concern.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. A content requirement covers what information or media an application presents, where it comes from, and how it stays current. An interaction requirement describes how a user provides input or manipulates the application, across devices and browser behaviors. A navigation requirement specifies how a user moves through the application, including arriving from outside its expected sequence. And a configuration requirement defines the environments and conditions, like browsers, devices, and network quality, it must work under.

Key Takeaways

What to Carry Forward

To pull this together. Web applications add four requirement categories on top of general elicitation. Content covers sources, structure, and keeping things current. Interaction covers input methods, and browser behaviors like the back button. Navigation matters more on the web, because users can arrive at almost any page from anywhere. Configuration covers browsers, networks, and deployments the team does not control. And all four state what must be true. Implementation comes later.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Handling Requirements for Web-Based Applications

What are the four categories of requirements for web applications?
Web application requirements are commonly organized into content, interaction, navigation, and configuration. Content covers what is presented and how it stays current. Interaction covers how users provide input and manipulate content. Navigation covers how users move through the application. Configuration covers the environments and conditions it must work under. These categories are applied on top of general requirements elicitation, not as a replacement for it.
What is the difference between content and interaction requirements for a website?
Content requirements describe the text, images, video, and data an application presents, where they come from, how they are organized, and who keeps them current. Interaction requirements describe how users engage with that content through forms, buttons, and search boxes across touch, mouse, and keyboard. Interaction also covers browser behaviors, such as what the back button does, what a refresh does, and what happens with two tabs open.
Why is navigation especially important in web application requirements?
Navigation matters more on the web because a user can land on almost any page directly, through a search result, a shared link, or a bookmark. Navigation requirements therefore specify what paths must exist, how users find their way back, and what happens when someone arrives out of sequence. On the web, navigation is close to being the application's actual structure, not just a way of getting around it.
What is a configuration requirement for a web application?
A configuration requirement defines the environments and conditions a web application must work under, such as which browsers and versions to support, how to behave on poor or variable networks, and differences across deployments. It states what must be true, not how to build it. For example, "stays usable on an older phone browser with a slow connection" is a requirement, while the responsive layout technique that achieves it is a later implementation concern.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →