Cohesion refers to how closely related and focused the responsibilities of a single module are, which, when high, results in systems that are more understandable and easier to maintain . Coupling, on the other hand, refers to the level of dependency between different modules. Low coupling is desirable because it reduces the impact of changes in one module over others, aiding maintainability and scalability . High cohesion and low coupling in software design enhance the system's adaptability to changes and its ease of maintenance, promoting long-term scalability .

Functional requirements define what the system should do, describing specific behaviors or functions, such as authentication, data processing, or user interaction, that the software must perform . Non-functional requirements, however, describe how the system performs a function, focusing on aspects like performance, usability, reliability, and security . For instance, a functional requirement might state that a software should process transactions, while a non-functional requirement might specify that this processing should occur within a certain time frame. Together, these requirements ensure comprehensive system development .

The Spiral Model uniquely incorporates risk assessment as a central activity within each cycle, unlike other models such as Waterfall or Prototype . At each iteration, potential risks are identified, analyzed, and mitigated before further development progresses, allowing the team to address uncertainty head-on and adapt as needed. This ongoing risk management process not only helps in handling unforeseen challenges but also provides flexibility to accommodate changes in requirements and technology. This makes the Spiral Model particularly useful for large, complex, and high-risk software projects .

A Data Flow Diagram (DFD) is crucial for visualizing the flow of data within a system, illustrating how data moves through processes, where it is stored, and how it interacts with external entities . This helps in understanding the system’s operations, identifying inefficiencies, and redesigning processes for improvement. For example, in a library management system, a DFD could depict how books are issued, returned, and cataloged, assisting stakeholders in grasping both the current setup and potential areas for optimization .

The COCOMO (COnstructive COst MOdel) model is used for estimating the cost, effort, and schedule for software projects. It helps in predicting the approximate amount of effort required to develop a software project based on the size and various project constraints . The model has three types: Basic, Intermediate, and Detailed. Basic COCOMO provides a rough estimate based on size (measured in lines of code), while Intermediate COCOMO includes details on software environment and product, hardware constraints, and team experience. Detailed COCOMO builds upon Intermediate by using a more sophisticated set of metrics for further refinement of cost estimation .

Requirement elicitation techniques like FAST (Facilitated Application Specification Technique), OFD (Objective Fact-finding and Documentation), and the Use Case approach are processes to gather and identify requirements from stakeholders for software development . They contribute significantly to project success by ensuring that all stakeholders have a shared understanding of the software’s desired functionality, helping to define precise specifications and reduce the risk of mismatched expectations. Proper elicitation leads to clear, comprehensive, and unambiguous requirements, minimizing the risk of extensive rework and project overrun .

Software Life Cycle Models like Waterfall, Prototype, Spiral, and Evolutionary were developed to mitigate the issues of the Software Crisis which included poor project management, budget overruns, and timelines overshooting . The Waterfall Model provides a structured approach, making it easier to manage and understand, but is rigid and not suitable for complex projects. The Prototype Model allows for early user feedback, flushing out requirements flaws early. The Spiral Model integrates risk management and iterative development, making it suitable for large-scale, high-risk projects. Evolutionary Models adapt to changes over time, making them flexible and responsive to user needs . These models aim to provide frameworks to improve predictability and control in software development.

The main disadvantages of the Waterfall Model include its lack of flexibility for changes as it is a rigid process where once a stage is completed, revisiting it is difficult . This model is also not well-suited for complex and high-risk projects because it does not accommodate changes well, making it hard to address evolving customer needs . Additionally, testing starts only after development is complete, which can lead to the late discovery of errors, thereby increasing project cost and timeline .

SRS stands for Software Requirement Specification, which is a comprehensive description of the intended purpose and environment for software under development . It serves as a fundamental document used throughout the software development process, detailing both functional and non-functional requirements . SRS is important because it provides a clear statement of what the software should do, ensuring all stakeholders have a common understanding, which helps in project planning and estimation, quality assurance, maintaining scope, and minimizing the risk of project failure .

Object-Oriented Design (OOD) offers several advantages over traditional design methods. OOD promotes reusability through the use of classes and objects, enabling code to be reused across different parts of an application or in different projects . It enhances maintainability since encapsulation allows changes to one part of the system to be made with minimal impact on others. OOD also supports better real-world modeling, making it easier to represent and manage complex systems . Additionally, it facilitates scalability, allowing systems to grow in complexity with ease due to its modular structure .