SWE 410 Colorado Technical University Online Software Processes Project

User Generated

Utngrf34

Programming

SWE 410

colorado technical university online

SWE

Description

I will submit the paper you will add to


Key Assignment

It is time to finalize your Key Assignment (Software Development Quality Plan).

Update all of the sections where you have received feedback from your peers and instructor.

These sections should already be complete, and may only need to be updated:

  • Project goals and scope
  • Project management process
  • Requirements management
  • Process and product quality assurance
  • Software development methodology
  • Standards
  • Project quality
  • Product quality

The following new sections are to be added to your project for this week (2–3 pages):

Section 9: Quality Checklist

Create a table that includes the following:

  • List 10–12 deliverables that would be required throughout the entire software development life cycle.
  • Include a key statement that describes the quality review definition.
  • This would be used as a running list of deliverables and will review the criteria for the entire project. It should contain 4 columns:
    • Phase, or area of methodology where this deliverable is created
    • Deliverable name
    • Deliverable description
    • Description of quality
  • Include an introductory paragraph describing what the reader is looking at, and how to use the table.

Note:

This is different from Section 6. Section 6 dealt with what standards and activities you should follow. These are deliverables, not activities. That said, there may be some tangential overlap to Section 6. This is allowable, but try to avoid it as much as possible, or add additional new information. In Section 6, the activity may have been to create a particular deliverable, and in this area you simply have the deliverable.

The example below shows that there are 2 deliverables per phase using a waterfall-type model. Use the model you selected earlier and the terms that your particular methodology uses. Although your quality checklists may vary, here is an example:

Phase

Deliverable Name

Deliverable Description

Description of quality

Requirements

Requirements document

2–3 sentences to describe this

What will you look for to make sure this is a quality deliverable? 1–2 sentences

Requirements

Design

Design

Development

Development

Testing

Testing

Deployment

Support

Etc.

Section 10: Maintenance and Support

Describe the maintenance and support plan for this software application. Indicate the following:

  • Show how the changes will be dealt with, whether they are defects or enhancement requests. Create a diagram showing the flow.
  • Create an overall maintenance release schedule that shows the next 4 releases and indicates the cut-off dates for changes, etc.
  • Write 1–2 paragraphs detailing the user support plan. This should indicate what the users can count on regarding support. Include any documentation that the users may have available to them, as well as detailing first- and second-level support procedures.

Be sure to update the table of contents, and ensure that all formatting (such as the APA reference sheet) is done correctly.

Please submit your assignment.

User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached. Please let me know if you have any questions or need revisions.

SOFTWARE MAINTENANCE AND SUPPORT OUTLINE


Corrective measures are the most straightforward kind of servicing to recognize.

Whenever there is a complaint about a feature of the program not working as planned, then
corrective measures will be essential to be used by the development team to deal with the
program bug.


Following our roll-out of production, we assume that consumers will be satisfied with the

feature, and the acceptance will be expanded day by day. Our device's usability will be used in
every possible way, and often in unthinkable ways, too.


Our framework for handling Department handling business inventory processes is

becoming increasingly influential. Other agencies are beginning to note. They quickly recognize
possible synergies as well as ask for their Configuration file. I direct them to our Open API
online website, of course.


Your device is now becoming something of all clients' day-to-day workflow, and data is

beginning to collect. And as more information is recorded in the data backend system, some
areas are beginning to slow down. The site that used to launch in less than 1 sec currently takes 5
seconds to open.


The program is still functional, but consumers are starting to worry about its efficiency.

Fixing problems relating to the efficiency of your device is a regular expression of significant
upkeep.


The architecture of our device has an integral role to play in its general upkeep.

Identifying the design, establishing development objectives and requirements to be pursued, and
final assembly implementation options can all lead positively or negatively to future
sustainability.



Preparing for software maintenance involves worrying about the tasks that must occur

during the maintenance phase and ensuring that all personnel and the services needed are
accessible.


Running Head: SOFTWARE MAINTENANCE AND SUPPORT

Software Maintenance and Support

Student’s Name
Instructor’s Name
Institutional Affiliation
Date

1

SOFTWARE MAINTENANCE AND SUPPORT

2

Quality checklist
Phase

Deliverable name

Deliverable description

Description of quality

Requirements

SMART goals

Objectives should be
appropriately vested.

Requirements

CLEAR goals

Highlighted as it is
more current
and represents
developments in the
corporate world.

Design

Configuration

Design

Testing

achieving the preset
standards
achieving the preset
standards

Development

Statement of work

Response and risk
mitigation and
personnel engagement,

Development

Work breakdown
structure

Testing

Status reports

The protection of the
project as a result
of the infringement is
reduced to a particular
portion.
Measurement of
project progression.

Enables the decisionmaking entity to track
threats while they
arise and to establish
risk assessment
techniques to reduce
them.
Enables the decisionmaking entity to track
threats while they
arise and to establish
risk assessment
techniques to reduce
them.
securing the system
and its contents
noncompliance issues can
be identified and
tracked
Converse any
modifications and big
improvements within
the quickest time
frame.
Effectiveness of the
risk management
strategy implemented.

Testing

Development updates

achieving the preset
standards

Deployment

Training

measuring team
performance

Support

Project management

The cumulative effect
determines the
success or failure of
the process.

noncompliance issues can
be identified and
tracked
noncompliance issues can
be identified and
tracked
Effectiveness of the
risk management
strategy implemented.
The leadership team
was presented
with exposure to the
project.

SOFTWARE MAINTENANCE AND SUPPORT

3

Maintenance and support
After creating the software as developers, we have to ask ourselves the following questions,
but can our inventions continue forever? Have you pictured a major street with no pavement? A
vehicle all without heading to a repair provider? What about a metal bridge that is never treated
for rust? While the software does not appear in the form of sheets entity, it is decayed and needs
to be preserved to remain operational. The following measures will be applied whenever
necessary;
Corrective maintenance
Corrective measures are the most straightforward kind of servicing to recognize. Whenever
there is a complaint about a feature of the program not working as planned, then corrective
measures will be essential to be used by the development team to deal with the program bug.
Maintenance tasks are to make adjustments to the structure to match it with its initial standards
and needs, (Gupta et al., 2019). It is an integral part of the contract that we have agreed with our
customers in the context of a specific guarantee.
Preventive maintenance
Following our roll-out of production, we assume that consumers will be satisfied with the
feature, and the acceptance will be expanded day by day. Our device's usability will be used in
every possible way, and often in unthinkable ways, too. These edge cases leave us wondering how
the code would act in situations we have never checked during creation, after rolling up our local
dev.-instance to test it out only to find a particular combination of user behavior that no other has
ever conceived of doing before will contribute to a mistake. We will have to improve this possible
mistake before it can even show itself to our customers. Here is where predictive maintenance is
coming into effect. As the name means, this is the sort of maintenance you do to eliminate anything

SOFTWARE MAINTENANCE AND SUPPORT
from occurring. Suppose our system testing has detected various behaviors that may not
manifest in the expected behavior. In that case, we will choose to fix this possible problem
before consumers are impacted by it in manufacturing as it is time for maintenance work.
Adaptive maintenance
Our framework for handling Department handling business inventory processes is
becoming increasingly influential. Other agencies are beginning to note. They quickly
recognize possible synergies as well as ask for their Configuration file. I direct them to our
Open API online website, of course. They return several days later, informing us they
would love to incorporate with our program, but they do need specific intermediate data
sources in our API. We roll up our sleeves and brace for a new update, all parts of our
adaptive maintenance. Adaptive maintenance requires any modifications to the framework
which were not similar to the original criteria and configurations. Adaptive changes
increasing arise from the need for, for instance, an imminent update to the underlying
infrastructure that could impact our system or from users asking for new specifications to
be introduced.
Perfective maintenance
Your device is now becoming something of all clients' day-to-day workflow, and
data is beginning to collect. And as more information is recorded in the data backend
system, some areas are beginning to slow down. The site that used to launch in less than 1
sec currently takes 5 seconds to open. The program is still functional, but consumers are
starting to worry about its efficiency. Fixing problems relating to the efficiency of your
device is a regular expression of significant upkeep. Perfect servicing may also lead to

4

SOFTWARE MAINTENANCE AND SUPPORT

5

potential maintenance, for instance, by developing or upgrading the records of subcomponents,
external systems, and components.
Designing for software maintenance
The architecture of our device has an integral role to play in its general upkeep. Identifying
the design, establishing development objectives and requirements to be pursued, and final
assembly implementation options can all lead positively or negatively to future sustainability? As
an accomplished software engineer, it is my responsibility to consider sustainability as part of the
program's specified plan, (Gupta et al., 2017).
Maintenance contributions
Specialists

Table driven

Base code
complexity

data

High-level
programming
language

Complexity
analysis tools

Defect
tracking tools

Code
complexity

Staff
experience

Refactoring
tools

Reverse
engineering

Reengineering
tools

Code
inspections

tools
Helpdesk
automation

CVCD
tools

Quality
measurements

Team
morale

Regression
tests

Management
experie...


Anonymous
Excellent resource! Really helped me get the gist of things.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Similar Content

Related Tags