Prior to this phase, subsystems which make the system have been defined. Requirements and verification tests for the subsystems are laid down. Functions for each of the subsystems are identified and suitable concepts have been selected in order to achieve these functions. In the development phase, these concepts are further refined, specifically for the system to be designed. Details regarding the realization of the system have to be finalized, in this phase.

==Flow Diagrams==

<br/>

Note that the output from power regulation is passed on to relevant sections of the system. At the end of power regulation, 1 A current should be available at 5 V. This is the power of 5W. Let the power generation block give an output of yA at xV and this is to be converted to 1A at 5V by the power regulation block. Please note that, until this stage, we have not selected concepts for each of the blocks. Several concepts of power generation have been discussed [[Power Generation | here]]. Based on the analysis, let solar power be selected as a concept for the power generation. Solar power is harnessed by using solar panels. The amount of power generated will depend on the following factors:

*To supply power to power regulation block if power from solar panels is insufficient

This power cannot be generated out of nothing. One way to arrange for this is to store power when it is available in excess and release this power when solar power is insufficient. One of the ways to achieve this is by use of a [[battery]]. Typically, a dedicated circuitry is needed to handle the charging and discharging of the battery. This is represented as the “power storage management” in this updated schematic.<br/><br/>

<br/><br/>

The discussion on this example is paused at this point to share some insights on the process followed. While discussing this example, a schematic was created, keeping in mind only the power aspect. The subsystem was broken down to blocks. Concepts required to realise these blocks were understood in detail and requirements were further defined for these blocks. In the process, an updated schematic was also created. Such schematics can be developed for other subsystems as well. Each schematic is designed keeping in mind one or more perspectives, like the flow of power, the flow of data, based on mechanical interfaces etc. These schematics or representations are called system architecture. There could be more than one system architecture which meets the requirements. These alternatives are to be evaluated by further system analysis. <br/> <br/>

==Payload Data Management==

Planning of the development of payload data management systems is also an integral part of developing a satellite. This involves setting up a ground station (the reason to do so is given [[Role of Communications | here]] and the infrastructure required to build one is given [[Obtaining the required Infrastructure| here]]) along with a plan for the management of any data downlinked by the satellite. Such data can include health monitoring data or sensor measurements. Planning how to analyze the data beforehand can streamline the whole process of finding faults or achieving the mission. For example, Pratham’s payload of collecting data on the total electron count required the team to create a map of the electron count over the city of Mumbai after the data had been collected.