1. Requirements

2. Terminology: Requirements XYZ Requirements gathering (also known as “requirements elicitation”) : what is to be accomplished, how the system will fit into the needs of the business, and how the system will be used on a day-to-day basis. The customer statement of requirements is rarely clear and complete enough for the development team to start working on the software product. Requirements analysis involves refining and modifying the requirements initially received from the customer during requirements gathering. Analysis is driven by the creation and elaboration of user scenarios that describe how the end-user will interact with the system. Negotiation with the customer will be needed to determine the priorities, what is essential, and when it is required. A popular tool is the use cases. Requirements specification represents the problem in a semiformal or formal manner to ensure clarity, consistency, and completeness. It describes the function and performance of the planned software system and the constraints that will govern its development. A specification can be a written document, a set of graphical models, a formal mathematical model, a collection of usage scenarios (or, “use cases”), a prototype, or any combination of these. The developers could use UML or some other symbolic language for this purpose. It is important to ensure that the developers’ understanding of the problem coincides with the customers’ understanding of the problem.

3. Software development methodologies Structured analysis and design (SAD) Object-oriented analysis and design (OOAD) Agile software development (ASD) Aspect-oriented software development (AOSD)