Requirements Capture
AllPages
RecentChanges
Links to this page
Edit this page
Search
Entry portal
Advice For New Users
A systems engineering perspective
on requirements analysis.
(From Wikipedia)
In the "Full Stack Developer" path, the place to start in any project is with Requirements Capture. Here we look at all the competing forces acting on the project as a whole, and try to capture them in some sort of structure that lets one expand, sort, prioritise, and generally use them to decide what to do, when to do it, and how much time and money to spend.

It is the Requirements Capture that should drive the project, and allows one to start the User Experience Design process.

User requirements capture is a process used to understand what typical users will need from a service which is about to be designed. Users are observed using similar services and interviewed about the ways they go about planning and completing their goals. This information is used to identify a list of content, features and functionality the new service must have in order to satisfy the needs of its users.

Lower level:
 Root node:
 Higher level:
Links to this page / Page history / Last change to this page
Recent changes / Edit this page (with sufficient authority)
All pages / Search / Change password / Logout