Software Lifecycle

Software Lifecycle

Section 1: 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 the “Standards” section a couple weeks ago that you gave to me on 3/8/2017 . That section dealt with what standards and activities you should follow. These are deliverables, not activities. That said, there may be some tangential overlap to that section. This is allowable, but try to avoid it as much as possible, or add additional new information. In that section, the activity may have been to create a particular deliverable, and in this area there is simply a deliverable.

The example below shows that there are 2 deliverables per phase using a waterfall-type model. Use the Agile 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 2: 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.

"You need a similar assignment done from scratch? Our qualified writers will help you with a guaranteed AI-free & plagiarism-free A+ quality paper, Confidentiality, Timely delivery & Livechat/phone Support.

Discount Code: CIPD30

Click ORDER NOW..