Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx

Systems Analysis and Redesign Project Phase 1 Grading Rubric
Criteria
Levels of Achievement
Content 70%
Advanced 90-100%
18 to 20 points
The introduction is succinct and

embodies the project’s primary
objectives and outcomes. The
Introduction and
introduction constructs the purpose
conclusion
of the system. A compelling and

justifiable conclusion is developed
that supports the key outcomes.
More than 5 scholarly sources and
500 words combined.
18 to 20 points

Problem statement is feasible
and addresses the key
deliverables of the project

including a highly innovative,
available, scalable, and secure
Problem statement
information systems solution
that can be implemented in the

cloud or a distributed
environment. Over 500 words
and 5 unique and relevant
scholarly journal articles that

justify the problem and need for
a solution.
92 to 100 points
Feasibility study and project
plan are more detailed and

higher quality than the textbook
examples in each of the core
Feasibility study and
objectives including at a
minimum the SDLC cycle,
project plan

updating the old information
system to the new cloud-based
system, a comprehensive /

detailed project charter, scope,
alternatives, schedule, tasks,
resource estimations, work
break down structure, financial
budget, cost, and benefit

analysis. Plan is over 2,000
words with over 10 relevant
supporting scholarly sources
justifying the methods,
standards, estimations, and
costs.

Structure 30%
Advanced 90-100%
APA, Grammar, and
18 to 20 points
Spelling
Properly formatted APA paper
with table of contents and
references pages. Correct spelling

and grammar used. Contains fewer
than 2 errors in grammar or
spelling that distract the reader
from the content and/or minimal
errors (1-2) noted in the
interpretation or execution of
proper APA format. Excellent

organization, headings, and flow of
the main concepts exist.
Overall Requirements
37 to 40 points
Over 2,000 words exist of original
student authorship that shows
excellent mastery and knowledge

of systems analysis and design.
Over 10 unique scholarly peer
reviewed journal articles from
well-respected IT journals exist
that directly relate to and
sufficiently support an operational

systems analysis and design.
Total Points
Criteria

Content 70%
Advanced 90
-
100%
18 to 20 points
The
introduction is succinct and

Introduction and
introduction constructs the purpose
conclusion

of the
system. A compelling and

500 words combined.
18 to 20 points

Problem statement

a
solution.

92 to 100 points
plan are
more detailed and

examples in each of
the core
project plan

system to the new cloud
-
based

Criteria

Content 70% Advanced 90-100%
18 to 20 points
The introduction is succinct and
Introduction and introduction constructs the purpose
conclusion of the system. A compelling and
500 words combined.

18 to 20 points
Problem statement

a solution.
92 to 100 points
plan are more detailed and

examples in each of the core
project plan
system to the new cloud-based

Proozy SWOT NotesStrengths
Opportunities
Weaknesses
Threats
Two sites, two brands; daily deals and full-price high end (Yeti,
Hydroplast) (need two sites to
get merch from brands.
Affiliate marketing-cost-effective--influencers get commission
for driving sales.
18-19 years of building network with buyers for brands and
stores (Nordstrom/TJ Maxx)
Making good use of micro-influencers (1,000 - 2,000
followers), local, trusted
Local events program (Hospital, Runs, Tent sale) helping with
local awareness.
Gym makes employees happy; partnership with Crossfit;
convinced Patagonia, Aloe, Yeti

Respect partners’ desires with unique discount system--use
codes and coupons rather than
cutting the price on the website too deeply. Don’t put brands on
Amazon.
Move products for partners; allow brands to experiment with
new products/test market
Sustainable in this way: sell goods that might otherwise be
trashed or burned (H&M)
Alternate channels (warehouse sales too) allow the company to
move stock
Low acquisition cost per customer (make $8)
Clear target customer (female 35-54-67%) and data on what she
wants (leggings, hoodies,
t-shirts, shoes) always can have/use more (continuity items)
wear for sports/home
Strong sales of fashion items in test expansion--Kenneth Cole,
Calvin Klein, Hilfiger, Birken-
stock.
Customer loyalty program
Managing quality within this system--hard to know why stores
have a surplus or cancel orders
(didn’t pass QA)
Sourcing can fall behind; house all of own inventory; need to
find fresh relevant new prod-
ucts--difficult to do/ Getting the amount of stock needed for
deals

Inventory turnover ratio--from 4-5 times a year to 3 times
Not enough personalization of targeted ads to new customers
Not much brand awareness locally
Could be better at keeping customers after the first purchase.
Most of business comes from
top 20-25% percent of customers; also, once customers have
been onthe list for over a year,
they become regular, loyal buyers
Confusion about difference between ‘deals’ page and
‘clearance’ page
Can’t figure out how to get Lululemon on board.
Home state (MN) worst state for brand recognition; mose
customers are in the big city; need
to take advantage of closer locations (Midwest)
Need to get deeper data earlier on (give gift cards/promotions;
use tracking and cart items)
Money is not unlimited; need to be careful about costs
Group of “mommy buyers” buying mostly for gifts and family
now-what do they want for
themselves? Deal hunter moms buy a lot at once (meme with
tons of boxes)
Mobile shopping increasing--developing an app as well, but
would have to appeal to younger
buyers to take full advantage

Customers want customized, curated content (which Proozy
provides some of and would
provide extensively on the app)
West Coast labor is cheap and plentiful; shipping less costly to
many buyers in this region (plan
is to become better known in Minnesota, expand to Midwest;
also to put a warehouse in the
West Coast; a location on the East Coast.
Sustainable customer might buy Proozy product if can show
where it was made, by whom, sup-
ply chain. (Do they want to do this for every product? Not
sure.) Would combine with some
type of cause marketing (like buy one, give one).
Local businesses may want to partner for deals; smaller
businesses could be ready to be ac-
quired; large department stores with no online experience often
want to acquire or partner
with businesses like Proozy
A lot of struggling retail stores offloading goods
Market for luxury goods expanding (Proozy Luxe-
Prada/Dior/Chanel)
Market for Yoga wear expanding
Besides fashion; expansion in markets: home goods, small
electronics; small appliances
Fighting against much bigger companies (Macy’s, Kohl’s, TJ
Maxx, Target)
West Coast real estate extremely expensive

Need to get repeat deals from brands to keep customers
(Columbia)
Many customers depart after the first purchase
Can’t find a good digital marketing firm; have no Instagram
person; paid ads are a “long-term
expensive game and are not timely enough for flash sales.
Customers never willing to pay for shipping; have to take that
into account when pricing/mar-
keting
Competitors are expanding to Canada and South America; so
they will have to.
Most brand ambassadors/influencers are too expensive for ROI
One bad comment on social media can ruin reputation
App costs $200,000-300,000--have to have the right timing and
plan for this investment
Labor in MN extremely expensive (#1 labor market)
Not Interested In:
Opening new bricks and mortar stores-Had stores in San
Francisco; Minnesota; Chicago; Michigan (Novi); collected
huge email list through
stores; moved online.
Heavily investing in social media--not too active; ROI is not

good enough--finding right partners is more important.
Return policy that is too lenient: want to prevent ‘buyer’s
remorse’ for overshoppers and people who buy (and get free
shipping for) lots of expen-
sive items and return a lot.
Selling a lot of hard goods: margin is lower.
Drop shipping: labor intensive and complicated; can’t guarantee
timeliness or control the customer experience; poor profit
margin.
Wants:
Sick of marketing to everyone else’s customer
Have relationships with UA, Nike, Nitroplast, Ray Ban--all with
different needs; Reebok will test products through this
company--want to do
more of that to have exclusive products to offer.
Marketing director loves the services/offers of the Chipotle app-
-how do they do this with non-food?
Characteristics of new app: exclusive deals; new drops; limited
quantity; profile prefs tailored to each user; products, but alos
other content tai-
lored to each user. Can provide input about what they want to
see.
Offering a better quality customer experience; more curated
emails.
Acquiring small companies; partnering with large retailer
needing more online selling experience.

Coupon site partners--always looking at where competitors are
going; looking at how they are partnering with others--make a
case for Proozy
deals matching audience and site.
Sustainable apparel; connection to a cause--not sure which
Other Information:
300,000 customers; 1.83 purschases a year; avg. $51 dollars;
free shipping over $50
Customer loyalty program has five levels of “Proozers” and
different rewards for each type (exclusive products at the top)
Deals--offer something new every day; goes for 7 days, but 80%
of items are sold during the first day, with weird colors and
small sizes left over.
More fun than TJ Maxx (What??)
Partnering with shipping company for 2-day air (UPS/Fed Ex)
$75 or more
Proozyfit is for hard-to-find full-price items.
Secondary type of customer: male 35-54 (33%); hardly any
younger customers
For Pricing: Alex Case experiments interpreting data results
from color/shipping strategy/name of code
Private label would be a small part of the business $1 million of
$56 million

BMIS 530
SYSTEMS ANALYSIS AND REDESIGN PROJECT – PHASE 2
INSTRUCTIONS
Recall the three stages of the project:
Phase 1: Introduction, problem statement, feasibility study, and
project plan
Phase 2: Methodology to compare the old and new systems and
the systems analysis
Phase 3: Results of comparison of the old and new systems and
the systems design
In phase 2 you will develop a methods section, similar to a
research methods section of a journal article, that highlights the
framework and standards you will use to compare the old
information system analysis and design to the new information
system that is cloud-capable, highly available, scalable, and
secure. You will use the methods section as a means to compare
the two systems.
Phase 2 Report Requirements
This report must contain the following elements:
I. See the grading rubric for all minimums.
II.Cover page
III.Table of Contents (TOC)
IV. Every section must be well supported with scholarly
information systems journal articles.

V. Introduction and conclusion sections
a. Please update your previous introduction and conclusion
sections as appropriate
b. A succinct, high quality, and well supported introduction and
conclusion should be written
c. It is necessary to highlight the objectives and conclusions of
the project
d. Introduce the primary goals of this particular phase, the
coinciding objectives, and the outcomes
e. The conclusion should be the last heading and conclude the
current phase and state the upcoming objectives and
deliverables in the next phase.
VI. Literature review and systems analysis and design
methodology
a. Constructs a well-supported review of literature related to the
problem
b. Develops a proper systems analysis and design comparison
methodology in which to benchmark and test the information
system
c. Details and supports the objective framework(s) and
standards that will be used to compare the old and new systems
d. Uses the frameworks’ process accurately
VII. Systems analysis diagrams

a. A minimum of two diagrams (2) are necessary for each
required type, one diagram represents the existing system and
one diagram represents the new re-designed and improved
system
b. The following systems analysis diagrams are required:
i. Use case diagrams for the old system and new system
ii. Written use cases (also known as use case descriptions) for
the old system and new system
BMIS 530
iii. Activity diagrams for the old system and new system
iv. Sequence diagrams for the old system and new system
c. Screenshots are required for each diagram with a visible
operating system date/time and unique desktop element showing
that indicates it is your computer
i. No credit will be given for diagrams without screenshots
ii. Include the screenshots in appendices in the project report
d. Describe the systems analysis as you complete it in a
narrative form and link in each associated diagram referenced in
the narrative using an appendix
e. Each diagram will be assessed according to UML standards
and a level of detail that excels beyond textbook examples
i. Note, textbook examples are simpler versions meant to learn
and not as complex as industry diagrams often

ii. Our textbook is a graduate version of systems analysis and
design. If you need more undergraduate textbook support we
encourage you to use Safari e-books from the Liberty Library.
Our undergraduate textbook develops the more foundational
SAD learning using the textbook:
1. Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems
analysis &design: An object-oriented approach with UML (5th
ed.). Hoboken, NJ:Wiley and Sons.
BMIS 530
S
YSTEMS
A
NALYSIS AND
R
EDESIGN
P
ROJECT
–
P
HASE
2 I
NSTRUCTIONS

Phase 1
: Introduction, problem statement, feasibility study, and project
plan
Phase 2:
Methodology to compare the old and new systems and the
systems analysis
Phase 3:
Results of comparison of the old and new systems and the
systems design
research methods section of a journal
article, that highlights the framework and standards you
will use to compare the old information
system analysis and design to the new information system that
is cloud
-
capable, highly available,
scalable, and secure. You will use the methods section as a
means to compare the two systems.
Phase 2 Report Requirem
ents
I.

See the grading rubric for all minimums.
II.
Cover page
III.
Table of Contents (TOC)
IV.
Every section must be well supported with scholarly
V.
Introduction and
conclusion sections
a.
Please update your previous introduction and conclusion
b.
A succinct, high quality, and well supported introduction and
conclusion should
be written

c.
It is necessary to highlight the objectives and conclusions of
the project
d.
Introduce the primary goals of this particular phase, the
coinciding objectives, and
the outcomes
e.
The conclusion should be the last heading and conclude the
current phase and state
the upcoming objectives and deliverables in the next phase.
VI.
Literature review and systems analysis and design methodology
a.
Constructs a well
-
supported review of literature related to the problem
b.

Develops a proper systems analysis and design comparison
methodology in which
to benchmark and test the information
system
c.
Details and supports the objective framework(s) and standards
that will be used to
compare the old and new systems
d.
Uses the frameworks’ process accurately
VII.
Systems analysis diagrams
a.
A minimum of two diagrams (2) are necessary for each
required type, one diagram
represents the existing system and one diagram represents the
new re
-
designed and
improved system
b.

The following systems analysis diagrams are required:
i.
Use case diagrams for the old system and new system
ii.
Written use cases (als
o known as use case descriptions) for the old system
and new system
BMIS 530
INSTRUCTIONS
Phase 1: Introduction, problem statement, feasibility study, and
project plan
Phase 3: Results of comparison of the old and new systems and
the systems design
research methods section of a journal
article, that highlights the framework and standards you will use
to compare the old information
system analysis and design to the new information system that

is cloud-capable, highly available,
scalable, and secure. You will use the methods section as a
means to compare the two systems.
I. See the grading rubric for all minimums.
II.Cover page
III.Table of Contents (TOC)
a. Please update your previous introduction and conclusion
b. A succinct, high quality, and well supported introduction and
conclusion should
be written
c. It is necessary to highlight the objectives and conclusions of
the project
d. Introduce the primary goals of this particular phase, the
coinciding objectives, and
the outcomes
e. The conclusion should be the last heading and conclude the
current phase and state
the upcoming objectives and deliverables in the next phase.

VI. Literature review and systems analysis and design
methodology
a. Constructs a well-supported review of literature related to the
problem
b. Develops a proper systems analysis and design comparison
methodology in which
to benchmark and test the information system
c. Details and supports the objective framework(s) and
standards that will be used to
compare the old and new systems
d. Uses the frameworks’ process accurately
VII. Systems analysis diagrams
a. A minimum of two diagrams (2) are necessary for each
required type, one diagram
represents the existing system and one diagram represents the
new re-designed and
improved system
b. The following systems analysis diagrams are required:
i. Use case diagrams for the old system and new system
ii. Written use cases (also known as use case descriptions) for
the old system
and new system
INSTRUCTIONS
The System Analysis and Redesign Project focuses on an

original private cloud-based solution for a company you
understand well. The purpose of this project is to ensure that
you know how to analyze an organization and its’ associated
systems. Therefore, the student is the architect. Successful
projects will have a brand-new design of a missing feature that
is not seen in existing information systems. The project should
highlight your advanced skills in information systems,
displaying your knowledge of all domains of our field.
A key objective of the project is to analyze and design a new
system that can function in a cloud-based and/or a distributed
computing architectural environment. This system should
replace an existing system at a company or a Church or another
organization that you understand well.
The re-designed system will be based upon at least one strong
and well-respected information systems and/or informatics
framework and several associated standards. The framework and
associated standards (e.g. COBIT, NIST) will be used to
benchmark the existing system to the new system and determine
if improvements were made. A summary spreadsheet should be
included in your final project phase that shows how the new
system meets improved framework guidelines and sub-
standards. Sub-standards that specifically identify how an
information system needs to be implemented are mandatory in
contrast to subjective designs.
All projects must use an original and new application/software
design diagrams and concepts. You must identify a new need
that has yet to be programmed/coded. Use of traditional
classes/databases/sequence diagrams such as what you see in
existing ERPs, CRMs, web forms, etc. will not be given credit.
For example, tables or classes like accounts, persons,
customers, employees, sales, orders, logins, movies/videos,
inventory, hotel reservations, restaurant orders, store fronts,
shopping carts, and many more will not count toward points in

this class. It is your responsibility to check to make sure what
you design is new and original. We want to see what you can
design; not what others have already designed. Thus, please do
not submit designs of existing information systems.
As you will find, the design must also result in a working
system that can be implemented. Designs that do not show
proficiency in parallel programming code (e.g. a working
object-oriented class implemented in Java, C++, Python, and/or
C#) are not very valuable at the more granular stage of design
and thus this requirement. Software engineers and/or developers
should be able to interpret your diagrams and accurately create
the designed system with the level of detail provided.
All phases require screenshots for credit that have details in the
screenshot showing your personal computer was used and
include an operating system date/time. You must use optimized
jpegs. All jpegs should be 50KB or less and/or the total Word
document file size should be less than 1MB. Word documents
that are too large cannot be checked by our plagiarism detection
tool and thus we cannot grade your work without this
validation.
Your project will be separated into 3 phases:
Phase 1: Introduction, problem statement, feasibility study,
project plan, and the conclusion
Phase 3: Benchmark results of the old and new systems and the
systems design

I. Please see the grading rubric for all minimums.
II.Cover page
III.Table of Contents (TOC) that uses proper headings for
automatic updating.
a. You will write an introduction and conclusion to the project
that is at least 500 words and well supported by scholarly
journal articles. Each phase requires these.
b. The conclusion should be the last heading and conclude the
current phase and state the upcoming objectives and
deliverables in the next phase.
c. This should include a description of the client organization
(including the organizational unit or functions served by the
system), motivation for the system (that is, why the
client organization wants the system, what problems it is
encountering, what opportunities would such a system provide),
the users of the potential system, and the general functionality
the client wants in the system (the users and general
functionality form a statement of scope for the project and
system).
VI. Problem statement
a. You must select either a business you work with or an
organization you know well and have expertise on that allows

you to re-design a new information system feature using your
knowledge.
b. At least 500 words should exist that supports an original new
software feature to be designed and the associated information
system problem(s) that will be addressed.
c. Note the problem must meet later project specifications.
Please assure it operates within an information system
environment that allows all diagram requirements to be met.
i. It must be able to be designed into an innovative, highly
available, secure, and scalable private cloud-based information
system.
ii. It must have key information system components due to
design requirements such as an associated storage area network,
database, local area network, wide area network.
iii. Use of any existing third-party cloud solutions like Amazon,
Google, Microsoft, RedHat and many others will not be
accepted. The student is the cloud architect and should therefore
design an original on-premise private cloud for the company
identified in the project problem that operates in their
datacenter.
a. Although phase 3 of the project stops at the design stage of
the SDLC, assure the feasibility study and project plan covers
the planning, analysis, design, implementation, and maintenance
aspects of the SDLC.
b. The plan should focus on updating the old information system
to the new private on-premise cloud-based information system.
c. Successful project plans will exceed the textbook examples
for each component.

i. Comprehensive project charter and plan documents.
ii. Project scope, alternatives, and feasibility documents.
iii. Project schedule, tasks, resource estimations, labor, time,
owners, and comprehensive work break down structure (WBS).
1. Use of Microsoft Project or alternative open source tools is
necessary for professional level documents.
iv. Financial budget, cost, and benefit analysis documents and
spreadsheets including line item pricing estimations.
v. The final outcomes should address these from a managerial
and strategic business perspective.
S
YSTEMS
A
NALYSIS AND
R
EDESIGN
P
ROJECT
–
P
HASE
1 I
NSTRUCTIONS

original
private cloud
-
based solution for a
company you understand well. The purpose of this project is to
ensure that you know how to analyze
an organization and its’ associated systems. Therefore, the
student is the architect. Successful projects
will have a bra
nd
-
new design of a missing feature that is not seen in existing
information systems. The
project should highlight your advanced skills in information
systems, displaying your knowledge of all
domains of our field.
A key objective of the project is to anal
yze and design a new system that can function in a cloud
-
based and/or a distributed computing architectural environment.
This system should replace an
existing system at a company or a Church or another
The re
-
design
ed system will be based upon at least one strong and well
-

respected information
systems and/or informatics framework and several associated
standards. The framework and
benchmark the existing system t
o the new
system and determine if improvements were made. A summary
spreadsheet should be included in
your final project phase that shows how the new system meets
improved framework guidelines and
sub
-
standards. Sub
-
standards that specifically identify how
an information system needs to be
implemented are mandatory in contrast to subjective designs.
design diagrams and concepts. You
must identify a new need that has yet to be programmed/coded.
Use of traditional
existing ERPs, CRMs, web forms, etc.
will not be given credit. For example, tables or classes like
accounts, persons, customers, employees,
sales, orders, logins, movies/videos,
inventory, hotel reservations, restaurant orders, store fronts,
this class.
It is your responsibility
to

check to make sure what you design is new and original. We
want to see what you can desi
gn; not
what others have already designed. Thus, please do not submit
designs of existing information
systems.
system that can be implemented. Designs
that do not show proficiency in parallel prog
ramming code (e.g. a working object
-
oriented class
implemented in Java, C++, Python, and/or C#) are not very
valuable at the more granular stage of
design and thus this requirement. Software engineers and/or
developers should be able to interpret
your diag
rams and accurately create the designed system with the level of
detail provided.
screenshot showing your personal
computer was used and include an operating system date/time.
You must use
optimized jpegs. All
jpegs should be 50KB or less and/or the total Word document
file size should be less than 1MB. Word
documents that are too large cannot be checked by our
plagiarism detection tool and thus we cannot
grade your work without this valida
tion.

Phase 1
: Introduction, problem statement, feasibility study, project
plan, and the conclusion
Phase 2:
Methodology to compare the old and new systems and the
systems analysis
Phase 3:
Benchmark
results of the old and new systems and the systems design
INSTRUCTIONS
original private cloud-based solution for a
company you understand well. The purpose of this project is to
ensure that you know how to analyze
an organization and its’ associated systems. Therefore, the
student is the architect. Successful projects
will have a brand-new design of a missing feature that is not
seen in existing information systems. The
project should highlight your advanced skills in information
systems, displaying your knowledge of all
domains of our field.
A key objective of the project is to analyze and design a new
system that can function in a cloud-
based and/or a distributed computing architectural environment.

This system should replace an
existing system at a company or a Church or another
The re-designed system will be based upon at least one strong
and well-respected information
systems and/or informatics framework and several associated
standards. The framework and
benchmark the existing system to the new
system and determine if improvements were made. A summary
spreadsheet should be included in
your final project phase that shows how the new system meets
improved framework guidelines and
sub-standards. Sub-standards that specifically identify how an
information system needs to be
implemented are mandatory in contrast to subjective designs.
design diagrams and concepts. You
must identify a new need that has yet to be programmed/coded.
Use of traditional
existing ERPs, CRMs, web forms, etc.
will not be given credit. For example, tables or classes like
accounts, persons, customers, employees,
sales, orders, logins, movies/videos, inventory, hotel
reservations, restaurant orders, store fronts,
this class. It is your responsibility to
check to make sure what you design is new and original. We
want to see what you can design; not
what others have already designed. Thus, please do not submit
designs of existing information
systems.

system that can be implemented. Designs
that do not show proficiency in parallel programming code (e.g.
a working object-oriented class
implemented in Java, C++, Python, and/or C#) are not very
valuable at the more granular stage of
design and thus this requirement. Software engineers and/or
developers should be able to interpret
your diagrams and accurately create the designed system with
the level of detail provided.
screenshot showing your personal
computer was used and include an operating system date/time.
You must use optimized jpegs. All
jpegs should be 50KB or less and/or the total Word document
file size should be less than 1MB. Word
documents that are too large cannot be checked by our
plagiarism detection tool and thus we cannot
grade your work without this validation.
Phase 1: Introduction, problem statement, feasibility study,
project plan, and the conclusion
Phase 3: Benchmark results of the old and new systems and the
systems design

Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx

Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx

Recommended

Recommended

More Related Content

Similar to Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx

Similar to Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx (20)

More from perryk1

More from perryk1 (20)

Recently uploaded

Recently uploaded (20)

Systems Analysis and Redesign Project Phase 1 Grading Rubric.docx