From be317632c0b8a9caaba0e81e7cbbecdd537bc4cf Mon Sep 17 00:00:00 2001
From: IshmaelPaps <125602964+IshmaelPaps@users.noreply.github.com>
Date: Thu, 16 Feb 2023 20:55:48 +0000
Subject: [PATCH] Add files via upload

---
 Groups/300 A/Abakah_5201040063.txt | 96 ++++++++++++++++++++++++++++++
 1 file changed, 96 insertions(+)
 create mode 100644 Groups/300 A/Abakah_5201040063.txt

diff --git a/Groups/300 A/Abakah_5201040063.txt b/Groups/300 A/Abakah_5201040063.txt
new file mode 100644
index 00000000..8f358039
--- /dev/null
+++ b/Groups/300 A/Abakah_5201040063.txt	
@@ -0,0 +1,96 @@
+Please make sure to read every bit of instruction in the "instruction.txt" file
+before you start answering these question.
+
+Questions
+1. What is a software process model and why is it important in software development?
+
+//Answer to Question 1
+A software process model is an abstract representation of a process. It is important 
+because, it provides a structured approach to software development that helps ensure
+quality, consistency, and efficiency in the development process and also provides a
+framework for managing the development processes. 
+
+
+
+
+2. Compare and contrast the Waterfall and Agile software process models. 
+What are the key differences between the two models and 
+what are the benefits and drawbacks of each?
+
+//Answers to Question 2
+Differences
+1. The Waterfall model is a linear sequential process model, where each phase of the 
+software development process is completed before the next phase begins. While,
+the Agile model is an iterative and incremental process model, where software is 
+developed in short, iterative cycles that involve continuous feedback and 
+collaboration between the developers and stakeholders.
+
+2. Waterfall is plan driven, while Agile is value and product driven
+
+3. Waterfall is suited for projects with well-defined requirements and a fixed
+timeframe, while Agile is suited for projects with changing requirements and no
+fixed timeframe.
+
+Benefits
+1. Waterfall
+Well-defined requirements and scope
+Clear project phases and deliverables
+Predictable timeline and budget
+
+2. Agile
+Continuous feedback and adaptation
+Very Flexible and adaptable to constant changing requirements
+Higher collaboration between developers and stakeholders
+
+Drawbacks
+1. Waterfall
+Limited feedback
+Less or no adaptability hence high risk of project failure if requirements change
+Very difficulty in accommodating changes during development
+
+2. Agile
+Uncertainty in project scope and timeline can increase cost
+Project management is complex
+Potential for scope creep
+
+
+
+
+3. What is Rational Unified Process (RUP), and 
+how does it differ from other software development process models? 
+What are the key phases and activities involved in RUP, and 
+what are the benefits and drawbacks of using this approach in software development projects?
+
+//Answer to Question 3
+Rational Unified Process (RUP) is a software development process model that provides a
+framework for developing software in a disciplined and controlled manner.
+It differs from other software development process models in that it is an iterative, incremental,
+and use-case-driven process that focuses on architecture, design, and testing
+
+The key phases of RUP include;
+1. Inception: Defining the scope, reasons for the project and risks of the project
+2. Elaboration: Developing the system strecture and refine the project plan if need be
+3. Construction: Building the system and performing tests
+4. Transition: Deploying the system and maintaing the system
+
+The benefits of using RUP include;
+1. Provides a controlled approach to software development which increases efficiency
+2. It gives adequate time to building architecture, designing and testing
+3. There's is a structure to manage risks invovled in projects
+
+The drawbacks of using RUP include;
+1. It can be complex and time-consuming when working on smaller or less complex projects
+2. It requires a skilled and experienced development team to carry out the phases involved
+3. It can be inflexible in accommodating changes in project requirements
+
+
+
+
+
+
+
+
+
+
+
+