Now that you know about the process of analysis and design and you have discussed the differences between Structured vs. Object Oriented approaches, I would like to step back and look at what we have learned in a slightly different way.
Sometimes when you read a textbook or a description of a methodology, you might get the impression that the design process is to fill out documents in the order that they appear in the text. Sometimes you need to separate thinking and writing. For example, you may need to do some thinking about what data the business might need in the future before you develop an interview questionnaire. You may have to discuss new business processes and the data they need to access before you actually write down the Entity Relationship Diagram. You might want to investigate what existing software packages do before you produce a Data Flow Diagram. The analysis and design process is far more iterative and chaotic that the texts would lead you to believe.
When you start a systems project, think about the first half of this course all at once. Write down all ideas for data, processes, and interview questions as they arrive in your mind. As the project progresses, you can organize your work into the documents called for by the methodology you are using. I have found that the documents help me think and collect ideas but I have never been able to do my thinking in the exact order shown in any methodology or textbook.