The life cycle starts with preliminary investigation which all the available information needed for the system elements and allocation of the requirements to the software are gathered. Next is the analysis of the requirements. This involves the analyst understanding the functions of the software which is required for the system based off the gathered information. Then is the system design in which the analyst designs and finalizes the best suited design for the system. The difficult step of system coding or development comes next which is where the analyst translates the design and programs into code for the computer. After the previous steps next are the testing phase where the system is testing to see if it works as intended or not. Then is implementation where the system is given to the customer and feedback is returned to insure the program works as intended. And finally system maintenance is the last step, here the analyst insures the system remains working within the proper bounds and functions appropriately and fixes any problems.
I think this relates to database development in a number of ways. One is how it starts, gathering information and finding the intent of the system. Next you must plan out how to set up the database, which is the vital information? What are the minor details? Then you set up your database fill in some test information insure it works properly and make needed adjustments. Finally you implement your database design where in it works properly you merely maintain and fix any errors.
2. Look up “Requirement Analysis” on the web. What kinds of topic heading do you find?
I found headlines like “Business Requirement Analysis” and “Software Requirement Analysis”. They referred to initializing the first steps towards the development process.