Professional Documents
Culture Documents
Se2 - Assignment 1
Se2 - Assignment 1
BSIT-3C
SOFTWARE ENGINEERING 2
To design and create high-quality software, development teams employ the software
development lifecycle (SDLC), a time- and money-efficient procedure. It delineates a
sequence of actions that separate the software development process into tasks that may
be given, finished, and evaluated. The objective is to reduce project risks while also
exceeding client expectations.
Planning
Scheduling, resource estimation, and resource allocation are all part of the planning
step. The software development team gathers stakeholder requirements to produce a
software requirement specification document that establishes standards and outlines
common objectives. The group has a well-thought-out plan to accomplish its objectives,
assesses costs, and develops a schedule.
Design
Software engineers examine specifications during the design phase to find the best
ways to build the software. They take into account integrating pre-existing modules,
selecting technologies, and choosing development tools. Additionally, they consider how
to incorporate the new software into any current IT infrastructure.
Implement
Test
To verify software for defects, errors, and client requirements, the development team
employs both automation and manual testing. The testing phase frequently occurs
concurrently with the development phase, and quality analysis includes checking for
faults and meeting customer requirements.
Deployment
The software development process' deployment phase entails moving the most recent
build copy to the production environment, including installation, environment
configuration, and packaging. This guarantees that users can keep using the software
while it is being modified or upgraded.
Maintain
The team performs a variety of duties during the maintenance phase, including bug
repairs, client issues, and software change management. In order to find new ways to
enhance the current software, the team also keeps an eye on system security, user
experience, and overall system performance.
Brainstorming
Document Analysis
Making an AS-IS process document and driving gap analyses for migration initiatives
can both benefit from reviewing the documentation of an existing system. Reviewing the
specifications that guided the development of the existing system is also crucial since it
enables us to check the completeness of the requirements and pose further queries.
Interview
Survey / Questionnaire
With limited resources and time, a survey or questionnaire can be used to gather
information from a large number of people. It may require users to rate something, make
a choice, or respond to open-ended inquiries. Survey design is challenging because
responders may be skewed by the questions.