IFSM461 Stage 05: Change Control Board Memo Instructions

IFSM 461: Systems Analysis and Design
Stage 05: Change Control Board Memo Instructions
Introduction
Before you begin this assignment, be sure you have read the “Udo, Marian, & Uduak Corporation () Case Study” and your completed Stage 1 – 4 assignments.
Purpose of this Assignment
This assignment gives you the opportunity to apply the course concepts to develop a System Change Request for one aspect of the new billing and payment system. This assignment specifically addresses the following course outcomes to enable you to:
• Plan, build, and maintain systems that meet organizational strategic goals by applying enterprise architecture and enterprise governance principles and practices
• Achieve successful systems design, development, and implementation by effectively applying the role of systems engineering and integrating with project management
• Effectively communicate with stakeholders to determine, manage, and document business requirements throughout the SDLC
• Translate business requirements into systems by applying appropriate SDLC methodologies and incorporating industry best practices
The Deliverable
Using the Udo, Marian, & Uduak Corporation () Case Study and the Requirements Document you developed in Stage 1, write a Change Control Board (CCB) Memo to recommend a change to one of the system requirements you proposed in your systems requirements checklist (Stage 1 – Requirements Document). Some changes might include: upgrading hardware/software versions, installing a security patch, adding security features, or making a change to be more efficient or cost effective.
Create a memo that includes the following:
• The memo should be 2 – 3 pages single-spaced and must use a Microsoft Word Memo formatting feature.
• Your name must be placed on the “From:” line.
• “Change Control Board” must be placed on the “To:” line.
• “System Change Request: and a descriptive title” must be placed on the “Subject:” line.
Page 1 of 5
IFSM 461: Systems Analysis and Design
Stage 05: Change Control Board Memo Instructions
• There must be a date on the “Date:” line. This is the document date.
• Do not include a Cover page. This is a business memo.
• Provide a Works Cited page to correctly cite and reference any sources you use with APA format. The Works Cited page is not part of the page count.
• Use the Grading Rubric to be sure you have covered everything.
• Submit your paper via your Assignment Folder as a Microsoft Word with your last name included in the filename.
• Description
o Provide a short, descriptive title of the System Change Request (SCR) and concise description (less than one-half page single spaced) of the concept or issue that you would like to change.
• Priority
o Select and explain the appropriate priority 1 through 5, where priority 1indicates an emergency request, 3 a time sensitive request, and 5 a normal request.
• Justification
o Be persuasive and provide a clear and well-supported justification for the change. This should be less than a single page single spaced. Typically some of the main drivers behind System Change Requests (SCR) include:
Improved Services Better Performance
Support for New Products and Services More Information
Stronger Controls Reduced Costs
• Cost
o Identify any costs (labor, materials, equipment, training, etc.) to implement the proposed system change. Give some best guess estimates. This should be about one-half page single spaced.
• Benefit/Risks
o Identify the benefits and the risks of implementing the proposed system change, using quantitative terms, where possible. This should be about one-half page single spaced.
Page 2 of 5
IFSM 461: Systems Analysis and Design
Stage 05: Change Control Board Memo Instructions
Helpful Resources
• Textbook, Systems Analysis and Design, Pages 516 – 517.
• Concepts – Change Request Management http://www.upedu.org/process/artifact/ar_crqst.htm
http://www.upedu.org/process/gcncpt/co_revno.htm http://www.upedu.org/templates/cs/CCM/upedu_ex_crqst.pdf
• Memo Templates – Office.com (Use must search using “Change Reqeust”) http://office.microsoft.com/en-us/templates/CT010117259.aspx
Page 3 of 5
IFSM 461: Systems Analysis and Design
Stage 05: Change Control Board Memo Instructions
Change Control Board Memo Rubric
Criteria |
Superior to |
Substandard to Good |
Inadequate |
Points |
Outstanding |
||||
Description |
A short descriptive |
A title is not descriptive or the |
No descriptive title |
1 |
title and detailed |
explanation of the issue is not |
and explanation |
||
explanation of the |
easily understood or is not |
provided. |
||
issue is provided |
detailed enough. |
|||
and is easily |
||||
understood. |
||||
Priority |
An appropriate |
The priority level selected may |
No priority level is |
1 |
priority level is |
not be appropriate and/or not |
selected or justified. |
||
selected and |
fully justified. |
|||
justified. |
||||
Justification |
Justification is clear, |
Justification may not be clear, |
No justification is |
3 |
well-supported and |
well-supported or persuasive. |
provided. |
||
persuasive. |
||||
Cost |
Costs including |
Costs including labor, |
No costs required |
2 |
labor, materials, |
materials, equipment, etc. |
to implement the |
||
equipment, etc. |
required to implement the |
proposed system |
||
required to |
proposed system change are |
change are |
||
implement the |
partially described or |
described and |
||
proposed system |
somewhat estimated |
estimated |
||
change are |
appropriately. Appropriate |
|||
described and |
best guesses on costs may be |
|||
estimated |
used. |
|||
appropriately. |
||||
Appropriate best |
||||
guesses on costs |
||||
may be used. |
Page 4 of 5
IFSM 461: Systems Analysis and Design
Stage 05: Change Control Board Memo Instructions
Criteria |
Superior to |
Substandard to Good |
Inadequate |
Points |
Outstanding |
||||
Benefit/Risk |
Benefits and Risks |
Benefits and Risks of |
Benefits and Risks |
2 |
of implementing the |
implementing the proposed |
of implementing the |
||
proposed system |
system change are not fully |
proposed system |
||
change are |
addressed or do not use |
change are not |
||
addressed using |
quantitative terms, where |
addressed. |
||
quantitative terms, |
possible. Benefits and risks |
|||
where possible. |
may be somewhat appropriate |
|||
Benefits and risks |
or applicable to the proposed |
|||
are appropriate and |
system and to the Case |
|||
applicable to the |
Study. |
|||
proposed system |
||||
and to the |
||||
Case Study. |
||||
Memo |
Memo is business- |
Memo may not be business- |
Memo is extremely |
1 |
Format |
focused and |
focused, concise and/or clear. |
poorly written and |
|
concise and clearly |
Memo may not be properly |
does not convey |
||
provides the |
formatted, well organized, or |
the information. |
||
information. Memo |
well written. Memo may |
|||
is formatted |
contain grammar and/or |
|||
properly using a MS |
spelling errors. Any references |
|||
Word Memo |
used may not be appropriately |
|||
template, is well |
incorporated and/or cited using |
|||
organized and well |
APA style. |
|||
written. Grammar |
||||
and spelling are |
||||
correct. Any |
||||
references used are |
||||
appropriately |
||||
incorporated and |
||||
cited using APA |
||||
style. |
||||
Total Points: |
10 |
Page 5 of 5

-
Rating:
5/
Solution: UMUC IFSM461 Stage 05: Change Control Board Memo Instructions