CST438 Learning Journal 7

This week working on these assignments, quizzes, and labs, I learned more about how software development processes affect the way a project is planned, documented, developed, tested, and deployed. One major topic was the difference between Agile and Plan and Document, also known as Waterfall. Plan and Document focuses on completing detailed requirements and design documentation before implementation begins. For example, we learned how a System Requirements Specification (SRS) documents functional and non-functional requirements so that developers, testers, managers, and other stakeholders have a common understanding of the system. Agile is more iterative. Instead of trying to completely define the system at the beginning, developers create working versions, receive feedback, and improve the system during short iterations.

The SRS assignment helped me understand requirements more clearly. I learned how to create use cases with actors such as the Customer and Driver in our taxi service. I also learned the difference between a use case summary and an actual UML use case diagram. The UML diagram visually shows actors, system boundaries, use cases, and their relationships. We also worked with ER diagrams, where entities, attributes, primary keys, foreign keys, relationships, and cardinalities describe the logical database design. Another important lesson was that non-functional requirements should be measurable instead of vague. Requirements such as response time, availability percentage, and security requirements are much more useful than simply saying a system should be “fast” or “secure.”

The AWS lab provided practical experience with deployment. We worked with services such as RDS, MySQL, EC2, RabbitMQ, ECR, ECS/Fargate, load balancers, and S3. I also learned how Docker environment variables and ECS task definitions configure containerized applications. Overall, these activities helped connect software requirements, UML and database modeling, implementation, testing, containers, and cloud deployment into the larger software development life cycle.

Comments

Post a Comment

Popular posts from this blog

Computer Science BS Journal (CST334) : Week 3

  This week in CST334 our lectures covered: Address Spaces, C Memory API, Address Translation & Base-and-bounds, Segmentation, Free Space Management. We also started working on our first group project this week. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. 1. Address Spaces An address space is the range of memory addresses that a process can use. Each process has its own virtual address space, isolated from others, managed by the operating system. Key Takeaways: Provides process isolation . Helps with security and stability . Enables virtual memory and memory protection. 2. C Memory API The C memory API includes functions for dynamic memory allocation and deallocation: malloc() , calloc() , realloc() , and free() . Key Takeaways: malloc(size) allocates a block of memory. calloc(n, size) allocates and zero-initializes memory. realloc(ptr, new_size) resizes previously allocated memory. ...
Read more

Computer Science BS Journal (CST334) : Week 5

    This week in CST334 our lectures covered: Concurrency and Threads, Threads API, Locks, and Lock-based data structure. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. We also had our midterm this week and I didn't do as good as I wanted to, I definitely need to focus some more on my studies. Concurrency and Threads Concurrency is the ability of a system to handle multiple tasks at the same time. Threads are the smallest units of execution within a process. Concurrency allows threads to run independently, improving efficiency, especially on multi-core processors. Key Takeaways: Concurrency enables better CPU utilization. Threads share the same memory space within a process. Context switching allows threads to appear to run in parallel. Can lead to race conditions if not properly synchronized. Threads API Threads APIs provide the functions and mechanisms to create, manage, and synchronize threads....
Read more

Computer Science BS Journal (CST363) : Week 5

 This marks the 5th week of CST363 and things are going great so far. This week we designed a prescription database, practiced transactions on MySQL as well as practiced some SQL in our homework 3 assignment. I had fun making the database for the prescriptions, I still get a little confused when it comes to the 1:1 or 1:M relationships so I had to go back and review a bit to be sure I was correct. Homework 3 and Lab 15 were pretty straightforward but they were good material to practice what was taught to us thus far. The web site  "Use the Index Luke"  has a page on "slow indexes".    https://use-the-index-luke.com/sql/anatomy/slow-indexes If indexes are supposed to speed up performance of query,  what does the author mean by a slow index?      After reading through the article I can conclude a few things.  What is a "slow index"? A slow index is one that exists and is technically used by the query planner, but results in poor performanc...
Read more