Impact of Feedbacks on Developing Software Development Life Cycle

This report provides an analysis of the impacts of feedbacks on developing a Software Development Life Cycle (SDLC). It summarizes the entire software life cycle model and emphasizes the importance of tracking work in a log book. It discusses the need to compile feedbacks received, describe them with examples, and analyze their effectiveness in system development. The report also evaluates a sample system design document, highlighting its strengths and areas for improvement, particularly in comparison to the NG-911 document. Furthermore, it addresses ERP implementation, focusing on problem statements, proposals, objectives, deliverables, methodology, and risk management. The impact of feedbacks on project development is emphasized, noting how weekly reports and assignment feedbacks help in identifying areas for modification and improvement, particularly in adopting agile scrum methodologies. The goal is to implement a high-quality SDLC methodology that includes all stages of the life cycle, from system planning to implementation, meeting the requirements of end-users through product backlog creation, sprint planning, scrum meetings, product demonstration, testing, and retrospective planning.

Running head: FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
Name of the Student:
Name of the University:
Author Note:

1
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
Software Life Cycle Model
Summary of entire software life cycle model is overall good. General instructions about
keeping the track of the work in log book is given. In week 6 and 7 journal assignment compiling
all feedbacks which are received from journal 2 are needed to be done. Feedback needs to be
described with the example and the effectiveness of those feedback in developing the system is
needed to be discussed.
Sample document of system design
The document was considered an excellent work which contains comparison and
contractions of the desired design template with design of NG-911 document (Alsalemi & Yeoh,
2015). Sufficient number of examples are provided in each section and additional sections which
are not included in NG-911 document are also disused.
ERP implementation
Problem Statement: Identification of the target organization and its inefficiencies are
appreciated. However providing more information about the type of business of company,
number of employees and working condition of back office process can be beneficial for project.
Proposal: The feedback in this section is same as the feedback from the problem
statement section.
Proposal Objectives: Identification of the business process to be automated will help to
set the objectives and goals of the organization.
Deliverables: Providing details about the each deliverables is appreciated. In case of data
migration discussion about the current system and identification of parts of new ERP which

2
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
require data migration will be beneficial (Rani,2017). The way of evaluating the ERP and the
timeline of the evaluation is important.
Methodology: The way of work is appreciated however the approach towards the
methodology and reason for choosing the methodology will be helpful for the project.
Risk: The work done in this portion is satisfactory however specification of budget and
the solution regarding to the implementation of ERP.
The impacts of feedback on the development of the project:
The feedbacks and weekly reports those were given about implementation of system is
very helpful for updating the students and the instructors. Status and the feedback report on the
various assignments are helpful in identifying the areas for the modification and improvement. I
will work on the modifications according to the feedback regarding the SDLC using agile scrum.
I will work with the fictitious organization to apply this methodology and will explain the type of
work organization is doing and the virtual requirements needed for the organization. This will
improve the effectiveness of my suggested approach.
I will try to implement feedbacks which I was received during my first and second week
assignment in order to enhance the performance of SDLC.I will try to implement a high quality
SDLC methodology that will include all stages of the life cycle. This will include the specific
approach towards the starting of the system plan, deliverables of the system, system
implementation specification that will meet the requirements of end users.
My first objective will be creation of product blockage and after that creation of sprint
backlog and sprint planning. The compilation of these objectives will followed by the execution
of scrum meetings which explains the working principal of sprint manner for the positive result.

3
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
The next thing to do after this is to demonstrate and test the product. The last step of the process
will be the retrospective planning of next sprint in order to deliver a simple SDLC.

4
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC
References
Alsalemi, A. M., & Yeoh, E. T. (2015, December). A survey on product backlog change
management and requirement traceability in agile (Scrum). In Software Engineering
Conference (MySEC), 2015 9th Malaysian (pp. 189-194). IEEE.
Rani, S. B. A. S. U. (2017). A detailed study of Software Development Life Cycle (SDLC)
Models. International Journal Of Engineering And Computer Science, 6(7).

5
FEEDBACKS AND ITS IMPACTS ON DEVELOPING SDLC