[lordkrandel]

Start by learning what the system actually is, interview its future users and address their requirements. Then look for systemic requirements like persistance, safety, security, realtime work, reliance, etc. Once you got all these questions, you start thinking about how your program is going to handle the system. There is a book called System analysis and design, google it, it look promising.