CST 438 - Software Engineering - Week 7

-

 


Describe some of the differences between using an Agile process and using a  Plan and Document (or Waterfall) process.

    One big difference between agile and plan and document or also known as waterfall process is how flexible they are. With agile, the team works in short cycles and gets feedback quickly, so it is easier to make changes along the way. This is really helpful when the project is still evolving or when the client’s needs are not really clear from the start. On the other hand, the waterfall approach is more structured, you plan everything upfront and follow each step in order. That can work well for projects where the requirements are stable and unlikely to change, but it can also be frustrating if something needs to be changed later, because you'd have to go back and redo earlier steps. Agile feels more collaborative and adaptable, while waterfall is more rigid and focused on sticking to the original plan.

Comments

Post a Comment

Popular posts from this blog

CST 462S - Race Gender & Class Digital World - Week 8

-
Image
  My service learning experience was great overall. I had the opportunity to work with a classmate to create a tool for The Furnace Teen Center . The project was to build a sign-in form that students could use before starting an activity. For example, if a student wanted to do some reading, they would scan a QR code that took them to a form where they entered their info. That info was then sent to a spreadsheet so the site supervisor could track who was participating and when. One thing I think could be improved is making the tool work more like a gym check-in system. Each student could have a membership card that, when scanned, would automatically log their activity into a database. But to do that, we would need to build Android and iOS apps, which takes way more time than the 25 hours we had. This kind of project really needs someone with experience in app development and a longer timeline to do it right. One of the biggest challenges was the time limit. Since we only had 25 hour...
Read more

CST 311 - Intro to Computer Networks - Week 2

-
Image
This week in CST 311, I learned more about how the internet operates from both a technical and service perspective. I learned about the structure of the internet, where billions of computing devices are connected through communication links such as fiber, copper, and satellite. One important concept for this week is the role of protocols like TCP, IP, and HTTP in controlling how messages are sent and received between these devices. I also found it interesting how packet switching allows messages to be broken into smaller packets for more efficient transmission, even though it may result in packet loss or delay if the network becomes congested.  Also, we learned about the importance of network protocols and the five layers of the internet protocol stack: application, transport, network, link, and physical. The application layer, for example, includes protocols like HTTP, which is important for web browsing, while the transport layer is responsible for process-to-process data transfe...
Read more

CST 334 - Operating Systems - Week 6

-
Image
  This week in CST 334, we learned about the concept of semaphores, a fundamental synchronization primitive in operating systems. Semaphores manage access to shared resources using an integer value, which can be incremented or decremented by operations like `sem_post()` and `sem_wait()`. These operations allow semaphores to control resource access, ensuring that threads wait when the resource is unavailable and proceed when it becomes available. A key form of semaphore is the binary semaphore, which functions similarly to a lock by permitting only one thread access at a time, ensuring mutual exclusion.  In addition to basic semaphore usage, we explored various common concurrency problems that semaphores can help solve. For example, in the Producer-Consumer problem, semaphores signal the state of a buffer, preventing data corruption or loss. Similarly, the Reader-Writer problem uses semaphores to manage access, allowing multiple readers or a single writer to use the resource, b...
Read more