Activity 2
Write your reflection or realization on the video viewed. It should be written or typewritten in a long
bond paper. The submit the screenshots of the activity here!
I have learned about software engineering. Software engineering education has evolved over the past
ten years as understanding of the issues related to the practice of developing software systems has
increased. I learned about stage of software development, the first stage is requirements gathering and
analysis. To understand the customers wants is to provide list of requirements. List could be long, yet
not useful for development. List that can be use in requirement gathering are surveys, interviews, focus
groups, observations and use case analysis. Use case analysis is describe a real usage scenario. No
jargon, no technical info. Written as a list, emphasizing end result and steps taken. Here is the sample on
using use case analysis. We use it on record a sale onto the system. The sale staff is the user and the
main success scenario are: (1) user initiates an “Add Sale” operation. (2) The software request for the
name and quantity of item sold. (3) The user inputs name and quantity, and confirms the action. (4) The
software stores the new entry into the system. We put extension in another scenario like this. The user
has input a quantity less than 1. The software indicates to the user that the amount is invalid. The use
case returns to step 2. There is precondition that the user is signed in as sales staff. The post condition
that is success when the entry is stored in the system. A simpler (though less detailed) formulation of
requirements. “As a sales staff, I want to be able to add new sales to the system so as to have a record
of all transactions”. The requirements analysis has two types these are: functional requirements and
non-functional requirements. Functional requirements are the function of the system like for what are
the system does. For example: the customer must be able to store and retrieve information about their
sales. Conversely, the non-functional requirements are usually a characteristic or property of the
system. For example, record must be retrieved within 3 seconds. Prototyping is building a (usually a non-
functional) system that represents the visual layout and linkage of features. The planning stage is the
next step. Although this stage of the software development life cycle appears to be self-evident, it is
worth investigating. A project's scope and aim will be unclear without proper planning. At this point, the
goals, costs, and team structure are all established. Furthermore, regular feedback from the target
group, developers, and other stakeholders is encouraged at the planning stage (and at all subsequent
stages). The team goes on to the analysis step after the planning stage is completed and the overall
purpose of the application is defined. Development is the third stage. To begin with, you should be
aware that the initial deployment is always difficult. After the testing is completed, it's time to release
the program and make it available to users or customers. This is an important time to improve scenarios
based on real-life scenarios. Despite the fact that this procedure is automated (as a rule), you and your
team should remain vigilant because deployment is a complex process. Several systems and devices
must frequently be integrated, and completing this stage correctly may necessitate extra time and effort
in some circumstances. At first glance, the deployment stage appears to be the final step. Nothing could
be further from the truth; this is simply the beginning. Testing is the fourth stage. Before the product is
released to users, this step must be finished. The majority (if not all) of your tests should be automated,
especially if you've set up a CI/CD pipeline. The testing phase's purpose is to confirm that all features
