Defining requirements

- The first step to any design process…is to gather your requirements.…Figure out what your application or product needs to do.…What's the problem you're trying to solve?…Why are you building the application in the first place?…At the core what are…the application's functional requirements?…Literally, what does it need to do?…What are the necessary features and capabilities?…In addition to those,…there may also be non-functional requirements…that place constraints…on how the application should function.…

For example, an application…that handles banking transactions,…or one that stores health care data,…will likely have to comply with certain regulations.…There could be performance requirements…such as response time,…or how many users can be supported simultaneously.…Support requirements, if there's an issue…with the application at two A.M. on a Sunday morning,…what needs to happen?…And security can be considered as either a non-functional…or functional requirement depending on the application.…

From my own experiences, one industry that loves…