Software Design and Engineering (SDE)

December 17-18, 2024

December 12

THE LAST DAY OF THIS CLASS SESSION!

December 5, 2024

Sir Carl initiated the session with a quiz on key topics from prior weeks, including ISO standards, software reliability and quality management, and the fundamentals of APIs. Following the quiz, he offered a concise overview of data mining, illustrating how businesses utilize data analysis to enhance their understanding of clients, anticipate their needs, and refine their products and services. We subsequently completed a 10-item in-class assignment to assess our comprehension, followed by group work on the Target Market Activity. This marked our final session before the finals.

November 21, 2024

Seatwork about API's which covers a lot in Lesson 7. It was our task to determine the necessary API endpoints, define HTTP methods, and create safe requests while taking important security and functionality considerations into account.

Nov 7 to 14 2024

In our lesson with Sir Carl, we delved into Topic 6, Software Reliability and Quality Management, and completed a brief assessment. This topic underscores the importance of ensuring software reliability, intended functionality, and compliance with strict quality standards. It encompasses processes such as testing, debugging, and adherence to industry standards. Additionally, we engaged in an activity where we analyzed case studies to identify software quality issues and propose enhancements for improved program reliability and effectiveness.

From October 10 - 17 2024

10-05, 2024

September 26, 2024

I am deeply ashamed for my behavior, for being lazy, not sociable and less attention to surroundings. ( I deeply atone for my actions which it'll cost me a semester gap. (You already did). I, myself, have face too many problems in life, stacking one another. (personal problems, family maybe, 'cause i got kicked at house, living alone) I was not fully committed about my school academics but I was willing to do anything. ( guy posting thinks he can do it alone, he can't) I'll try to unf*ck my life and start anew (OA) This post was not intended to post on this social platform nor to make public. But I did it anyway. For the love of God, please. Sir. (He's so desperate) Please accept my tumblr link. I don't know if you deduct points nor do I care. I know passing this late have consequences but accepting this work is your own decision. (...) Second semester, better be good (no more goofing around) If someone is reading this, don't mind it. Brush it off. This doesn't mean that I'm over dramatic in anyway but rather, to express something. (I don't know man. I don't know if you read this or not, but i want you to put some holy water in your eyes or something)

Friday was the deadline for PIT rechecking, and our group was still unable to achieve the desired progress in the system. The core functionality of our system—trading—was still missing during the review. However, there was some progress as the PIT's Firebase connection was successfully established. The login, signup, and sign-in features were functional in Firebase. When incorrect user credentials were entered, an error message was displayed, and a dialogue box popped up. After multiple incorrect attempts, the input was disabled, requiring the user to refresh the system to try again. Upon deleting an account from Firebase and attempting to log in, the system correctly prevented the deleted user from signing in.

The user dashboard had some updates but was still incomplete. There were three pages available for user navigation, but the trading functionality was still absent. Additionally, the user's name displayed on the dashboard did not match the username used during sign-in, indicating a synchronization issue.

I was not informed (less friends to begin with) But It was announce in a different section which I'm not enrolled I was late, I did not study, I did not pass the paper (because u know. I'll fail anyway) Timed! Everyone got out of the room I pretend nothing happen Cold chills on a cold weather! The End justify the means!

Week 3 was focused on completing the first assigned activity given by our professor. Our group also worked on the front-end development, which was managed by our code developer.

Week 4 was dedicated to class discussions, with some faculty members observing our sessions. During this week, our professor covered several critical topics such as design principles and patterns, software design methodologies, system implementation, and implementation strategies including coding standards, modularization, code review, and refactoring, as well as integration and deployment. In addition to these topics, the professor discussed our software design in detail, explaining the purpose of our software and how it functions.

After the lecture, the professor divided the class into four groups for a collaborative activity. Each group was assigned a specific scenario. Our group's scenario involved designing an online bookstore, which required us to create a user interface, develop pseudocode, and identify the design pattern to use. With the limited time provided, we worked efficiently to ensure that we could meet all the objectives and effectively present our work. Each group then selected representatives to present their findings and discuss the given task in detail.

I was very very late for posting this. I swear, I was there for the discussion. Here is my info and learning about Week #2: In Week 2, we began our introduction to Software Design and Engineering. During this period, our professor covered a range of foundational topics including Software Development Projects, Human Cognitive Limitations, the Emergence of Software Engineering, Fundamental Skills of Software Engineers, and Quality in Software Engineering. Additionally, we discussed McCall's Quality Factors, application responsiveness, different types of applications, the ACM Code of Ethics, the Software Life Cycle, the Software Development Cycle, the Waterfall Model (along with its extensions), and various Software Development Tools.