Target Audience, The people/audience that will be using the product once it is made and deployed, Timescales, Key dates and time periods where work/development must be completed, Purpose, what the product is designed to do and why, Content, what needs to be included in the product - could be textual, functional, visual, security features and so on, Budget, requirements set out and agreed about how much money can be spent, often agreed between the development team and the client, Style/ Visuals, how the product is going to look - a development team may include a designer who would take the lead and discuss this with the client, taking on board the clients ideas too, Business overview and goals, A description of the business the client owns (the one which requires the software product). They may outline the goals of this product, how they define success, and what problem they are trying to solve with the software product. Asking these questions allows developers more scope than just 'what features does it need?' - which often leads to unclear/inaccurate responses, Client, The person/ company who is paying for the software product, Milestones, Check in points at key phases in the development process.

Client Requirements - Software Development

autors:
Drukāt
Iegult

Līderu saraksts

Vizuālais stils

Iespējas

Pārslēgt veidni

)
Atjaunot automātiski saglabāto: ?