Problem statement
We did our best to fulfil and meet the technical standards of writing a proper problem statement. First we started with a short brief introduction to explain the problem and how we plan on solving it. Second we moved on to explaining the problem itself in depth, Third was the proposal on how we plan to fix that problem, Fourth was The functional and non-functional requirements, Next comes the Target and development environment that defines the tools we will use to make the platform and lastly was the deadlines and methodology used for development.
Click To View
Discovery Phase
The Domain search
Domain search is the process of studying our competitors, what they provide then explaining what value our platform adds compared to them and if we can improve on what they provide.
The Feature map
The feature map explains in detail exactly what each and every user is able to do on our platform and their interactions starting from when they visit for the first time to when they use our service often.
The Technical requirements and specification
The Technical requirements and specification defines and explains every technology, tool and methodology we use and why we use it.
Click To View
Analysis Phase - Context Diagram
It is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it.
Click To View
Analysis Phase - Data Flow Diagram (DFD)
It is a way of representing a flow of data through a process or a system. The DFD also provides information about the outputs and inputs of each entity and the process itself.
Click To View
Analysis Phase - Use case Diagram
At its simplest is a representation of a user's interaction with the system that shows the relationship between the user and the different use cases in which the user is involved.
Click To View
Analysis Phase - Activity Diagram
It is a graphical representation of workflows of stepwise activities and actions with support for choice, iteration and concurrency.
Click To View
Database schema
The database schema of a database is its structure described in a formal language supported by the database management system. The term "schema" refers to the organization of data as a blueprint of how the database is constructed.
Click To View
API documentation
API documentation is a technical content deliverable, containing instructions about how to effectively use and integrate with an API.
Click To View
Wireframes
A website wireframe, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a website. Wireframes are created for the purpose of arranging elements to best accomplish a particular purpose.
Click To View
Demo video
This demo is a video that navigates the wireframes to show how the users interact with the platform.
Click To View
Teaser Page
A web page has been made and deployed as a teaser to our project, this web page is a teaser for the project that shows alot of data about the project, the teams working on the project, and it describes each member of the team. A timeline of every document and data made for the project and links to said documents and data.
Click To View
