Software Development Quiz

The Waterfall lifecycle consists of sequential stages: analysis, design, implementation, testing, and maintenance. Each stage must be completed before moving on to the next. It is most suitable for projects with clearly defined requirements that are unlikely to change, as its rigid structure makes adapting to new requirements difficult. 

Agile methodologies focus on iterative development, continuous feedback, and collaboration between developers and stakeholders. Unlike Waterfall, Agile allows changes to be made throughout development, making it more flexible and responsive to evolving requirements. 

Extreme Programming (XP) is an Agile methodology that emphasises short development cycles, frequent releases, and strong customer involvement. It promotes practices such as pair programming and continuous testing, which improve code quality and adaptability. However, it requires significant commitment from both developers and clients. 

The Spiral model combines iterative development with risk analysis. Each cycle of the spiral involves planning, risk assessment, development, and evaluation. By identifying and addressing risks early, it reduces the likelihood of project failure, although it can be complex and expensive to implement. 

Rapid Application Development (RAD) focuses on rapid prototyping and user feedback. It is most suitable for projects where requirements are not fully understood at the start and where quick delivery is prioritised. However, it may lead to less robust systems due to reduced emphasis on planning and documentation. 

Waterfall provides a clear structure and is easy to manage, but it lacks flexibility and struggles with changing requirements. Agile is flexible and encourages collaboration, but it can be harder to manage in large projects and requires strong communication within teams. 

Writing clear and efficient algorithms is essential because algorithms define the logic of a program. Well-designed algorithms improve performance, reduce errors, and make code easier to understand, maintain, and translate into programming languages. 

Procedural programming focuses on step-by-step instructions, object-oriented programming models real-world entities using classes and objects, functional programming treats computation as mathematical functions, and declarative programming focuses on specifying what the program should achieve rather than how. 

Procedural programming languages use sequences of instructions, variables, and control structures such as loops and conditionals. Examples include Python and C. They are widely used for general-purpose programming due to their simplicity and efficiency. 

Assembly language is a low-level language that uses mnemonic codes to represent machine instructions. It provides greater control over hardware but is more complex to write. The Little Man Computer (LMC) is a simplified model that helps learners understand how instructions are executed at a low level. 

Immediate addressing uses the actual value within the instruction. Direct addressing specifies the memory location of the data. Indirect addressing uses a pointer to another address where the data is stored. Indexed addressing uses an index register to modify the address, useful for accessing arrays.  

A class is a blueprint for creating objects, defining their properties and behaviours. Objects are instances of classes, representing specific entities with their own data and methods. 

Inheritance allows a class to inherit attributes and methods from another class, promoting code reuse. Encapsulation restricts access to data and methods, improving security and organisation. Polymorphism allows methods to be redefined in different classes, enabling flexibility and reuse. 

Object-oriented programming improves software design by promoting modularity, reuse, and maintainability. By organising code into classes and objects, it becomes easier to manage complex systems and update individual components without affecting the whole program. 

For large, complex projects, Agile methodologies may be suitable due to their flexibility, but they require strong coordination. The Spiral model is also appropriate because it focuses on risk management. Waterfall may be less suitable due to its rigidity, while RAD and XP may struggle to scale effectively.