Project ideation, requirement analysis and planningPetar Santor
1. Project initiation
During the first call client will present the problem, business needs, objectives, and vision of the product.
2. Analysis of functional and non-functional requirements
Client presents business needs, objectives, and vision of the product. Requirements are classified from high-level to detailed that correspond to business requirements, user requirements, and then system requirements that are the most important. The last is what the app does, how well the app performs, and whether it suits user goals and user point of view.
3. Planning
After analyzing all the requirements, project is estimated. Document is delivered with details about timeline, costs, resources needed, and many more. After we plan and estimate everything, it is crucial to make a first sketch of the future app to see how it feels.
What's included
Document describing requirements specifications, estimated cost, time and resources
This document should outline the goals and objectives of the project, the target audience, and the features and functionality required to meet the needs of the users. It should also include a timeline for the project, with milestones and deadlines for each stage of development.
Low fidelity clickable prototype
A low fidelity mobile app prototype is a simple, rough, and basic version of a mobile application that is used to communicate and test design ideas and concepts. It typically includes minimal details, such as basic shapes, colors, and layout, and lacks advanced functionality and features.
Contact for pricing
Tags
Flutter
Git
Google Docs
Miro
Business Consultant
Mobile Engineer
Software Engineer
Service provided by
Petar Santor London, UK
- 2
- Followers
Project ideation, requirement analysis and planningPetar Santor
Contact for pricing
Tags
Flutter
Git
Google Docs
Miro
Business Consultant
Mobile Engineer
Software Engineer
1. Project initiation
During the first call client will present the problem, business needs, objectives, and vision of the product.
2. Analysis of functional and non-functional requirements
Client presents business needs, objectives, and vision of the product. Requirements are classified from high-level to detailed that correspond to business requirements, user requirements, and then system requirements that are the most important. The last is what the app does, how well the app performs, and whether it suits user goals and user point of view.
3. Planning
After analyzing all the requirements, project is estimated. Document is delivered with details about timeline, costs, resources needed, and many more. After we plan and estimate everything, it is crucial to make a first sketch of the future app to see how it feels.
What's included
Document describing requirements specifications, estimated cost, time and resources
This document should outline the goals and objectives of the project, the target audience, and the features and functionality required to meet the needs of the users. It should also include a timeline for the project, with milestones and deadlines for each stage of development.
Low fidelity clickable prototype
A low fidelity mobile app prototype is a simple, rough, and basic version of a mobile application that is used to communicate and test design ideas and concepts. It typically includes minimal details, such as basic shapes, colors, and layout, and lacks advanced functionality and features.
Contact for pricing