Programming Question

Syst
ems Analysis and Redesign Project: Phase 3 Assignment

I did add more points of the designs as they are moving in the right direction, nice work. Remember,
logins are out of scope. In the activity diagram, “user logs into system” can be removed along with
the next few activities. Assume a login session already exists. No need to re-invent the wheel or
include a part of a system already well designed. To reiterate, you do not need any existing system
functionality. Assume these systems area already designed and functional. Let me give you an
example of a detailed industry diagram of a login, please reference this sequence diagram for CAS:
https://apereo.github.io/cas/6.6.x/protocol/CAS-Protocol.html This also helps you see a detailed
design and your goal in these diagrams. In the second diagram, there is the server followed by the
proxy and the app. The user connects to the browser, which begins the communication with the CAS
server. Note, these are only prototypes. Even these diagrams will have more detail depending on
what system CAS is integrated with. Reference: https://apereo.github.io/cas/6.6.x/protocol/SAMLProtocol.html Thus, additions may be connecting APIs for the authentication protocols, database
servers, database tables, storage arrays, routers, etc. What I want you to focus on for the next project
is to identify all the primary system components. For example, the GUIs, servers, middleware, and
back-end elements. You have a database but what database tables are necessary and what other
elements does a database table need to support it? Each of these would be elements in the swim
lanes at the top of your activity diagrams. They will be needed in the other diagrams as well from the
class diagrams to the architectural diagrams. I hope this helps and keep moving forward!
In the final phase of the project, we deploy our methodology outlined in the previous phase. The
methodology is objective. It important to design using supported standards and at least one
modern framework. This is your blueprint and we should see this blueprint as you develop this final
aspect of the project. For example, the sub-headings in your systems design should mirror those of
the frameworks and standards you are following to design your information system. Map specific
sub-standards to your design diagrams. Show the audience your designs are well supported!
Entity Relationship Designs
The entity relationship diagram (ERD) should use proper notation such as crow’s foot. Depending on
the type of database, the proper associated standard for design is necessary. In traditional RDBMSs,
the goal is third normal form. Similar 3NF is possible in many NoSQL databases. For entity
relationship diagram tools I suggest Oracle SQL Modeler, Microsoft’s modeler, or MySQL
workbench: https://dev.mysql.com/doc/workbench/en/wb-creating-eer-diagram.html (Links to an
external site.) from https://dev.mysql.com/doc/workbench/en/wb-getting-started-tutorial-creatinga-model.html.
Oracle and Microsoft ERD tools provide the ability to forward and reverse engineer diagrams into
SQL table creation scripts, allowing you to check your designs to ensure they are accomplishing
what you intended. A proper ERD should have correct naming conventions, field types, relationship
descriptions, entity integrity, primary and foreign key constraints, be in third normal form or higher
and so on.
Class Diagram Designs
It is essential to understand object-oriented programming (OOP) prior to designing OOP classes. If
you need a refresher on OOP here is a good
article: https://www.oracle.com/java/technologies/oop.html.
Each diagram is critical for another in the design process and we should see integration between
different types of diagrams. For class diagrams please consider the sequence diagrams here
first: https://www.ibm.com/developerworks/rational/library/3101.html. Once you go back and rereview the sequence diagrams you will see a link to class diagrams at the bottom of the latter
article. Class diagram examples are found here: https://developer.ibm.com/articles/the-classdiagram/. The goal is for you to see how the sequence diagrams and class diagrams interact. Like
the industry example in this URL, our textbook teaches object-oriented (OOP) design. Please ensure
your classes use OOP or a subsequent well supported design standard.
As you will see in detailed class diagrams proper attributes and data types are necessary. Once
established, ensure they parallel the type of class. For example, are your classes abstract, concrete,
final, and/or static and do your attributes and access levels compliment this class type? Establish
the class relationships and associations. Verify the multiplicity values are correct and logical.
Add proper methods to your classes once designed. Start with correct attributes. Methods should
include accessors and mutators or getters and setters. Proper variables and attribute types should
be passed to the methods for them to function properly. Again, methods should associate with your
design standard. For example, an abstract class may or may not benefit from abstract or nonabstract methods. Consider method overriding and overloading. This should be justified.
Beyond this, read up on the other concepts mentioned if necessary.
User Interface Designs
For UI designs most applications today need to be accessible by many different types of devices. A
suggestion is to use a proper UI design tool that works well with mobile and web languages. For
standards/industry guides see: https://www.usability.gov/what-and-why/user-interfacedesign.html and https://xd.adobe.com/ideas/process/ui-design/. For your UI design tool I
encourage you to use a tool like Adobe Photoshop. If you do not have access to Adobe, GIMP is an
open source and free software similar to Photoshop, go to: https://www.gimp.org/. For HTML5,
good web-based IDEs we teach with include Eclipse and Microsoft Visual Studio. Lightweight IDEs
can be used as well such as Sublime Text or even Notepad++. Note, you do not need to program a UI
from scratch if you do not have this prior knowledge. Instead, you can create
pictures/mockups/boilerplates of your UIs in Adobe Photoshop. However, you want to ensure any
designs created would be feasible in a current web/mobile language.
A proper user interface design should first and foremost be designed with the ability of all users to
use the UI, be visible on most screen sizes, have correct navigation, consistent navigation, clean
designs with easy to read content, visual appealing graphics, proper form elements, strong form
validation, sufficient information security, and so on.
Network and System Architecture Designs
For your distributed computing and parallel processing designs in a private (not public) cloud
architecture please remember that you cannot use a third party cloud service. This is off limits per
the instructions because we want to see what you know and what you can design not what Amazon,
Google, and/or Microsoft can design. You are the cloud architect and thus the private cloud
requirement. We cannot give you credit for an AWS or other cloud design.
For tools you can use Cisco Packet Tracer if you took 520. Some students do not take 520 but you
can register and get Packet Tracer free from Cisco Networking Academy
here: https://www.netacad.com/ . You can also use Microsoft Visio or the open source version of
Visio called LibreOffice Draw: https://www.libreoffice.org/. There are also online design applications
that do not even require an installation such as https://app.diagrams.net/.
Here are a few good articles to get you started on your network and systems architecture
design: https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DC_Infra2_5/DC
Infra_1.html and https://docs.oracle.com/en/solutions/design-hyperion-oci/cross-regiondeployments1.html#GUID-C0D2CD20-F73A-4D84-9B98-237865941D3B.
In summary, the systems analysis and design process is very logical, it flows and integrates. In other
words, diagrams are not created in isolation of one another and reviewers should be able to follow
things like OOP inheritance, composition, etc throughout your systems design. I am here to help and
will gladly review your work. If you would like advice, please send me an email and explain what
strategy you are using so I can better understand the class and methods and how they should be
designed.
BMIS 530
SYSTEMS ANALYSIS AND REDESIGN PROJECT: PHASE 3
ASSIGNMENT INSTRUCTIONS
OVERVIEW
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 3 you will use the methodology developed in Phase 2 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 scholarly supported computing framework and standards (e.g. ANSI,
COBIT, ISO, ITU, NIST, HIPAA, PCI) to benchmark the systems analysis and design of the old and
new system. Once you perform this comparison, you will detail the results.
INSTRUCTIONS
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.
Systems analysis and design results
a. Follows a well-supported methodology including at least one framework and
appropriate standards from scholarly journal articles
b. Uses objective standards accurately to benchmark the old system and the new system
c. Minimal comparison elements should include system:
i. Cloud/distributed computing capabilities
ii. High availability
iii. Scalability
iv. Security
v. Note, these are projected based upon the comparative benchmarked standards
d. A final updated financial analysis that projects associated costs of both systems once the
final design is completed
e. Discuss the managerial implications of the results
f. Uses excel spreadsheets, graphs, figures, and tables to show the objective comparisons
of the systems
Page 1 of 2
BMIS 530
VII.
Systems design 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 design diagrams are required that compare the old and new
systems:
i. Entity relationship data model diagrams
ii. Class diagrams
iii. User interface forms
iv. Distributed computing network and system architecture diagrams
1. Design the complete information system architecture environment for the
old and new environments
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.
Note: Your assignment will be checked for originality via the Turnitin plagiarism tool.
Page 2 of 2
Systems Analysis and Redesign Project: Phase 3 Grading Rubric |
BMIS530_D01_202340
Criteria
Introduction
and
conclusion
Ratings
Points
10 to >9 pts
9 to >7 pts
7 to >0 pts
0 pts
Advanced
Proficient
Developing
Not Present
The introduction is
succinct and embodies
the project’s primary
objectives and
outcomes. The
introduction constructs
the purpose of the
system. A compelling
and justifiable
conclusion is
developed that
supports the key
outcomes. More than
5 scholarly sources
and 500 words
combined.
The introduction and
conclusion are succinct
and embody most of the
project’s primary
objectives and
outcomes, and/or the
introduction constructs
an unclear purpose of
the system. Justified
conclusion developed.
Minimum of 5 scholarly
sources and 500 words.
The introduction and/or
Substantially
conclusion are
unmet or not
generalized and embody present
some of the project’s
primary objectives and
outcomes and/or has
less than the minimum of
5 scholarly sources and
500 words and/or is not
defensible.
10 pts
Systems Analysis and Redesign Project: Phase 3 Grading Rubric |
BMIS530_D01_202340
Criteria
Systems
analysis and
design
comparison
results
Ratings
Points
40 to >36 pts
36 to >33 pts
33 to >0 pts
0 pts
Advanced
Proficient
Developing
Not Present
Systems analysis and
design results compare
key benchmarks
including cloud
computing capabilities,
high-availability,
scalability, and level of
security of the old and
newly designed
information systems
using relevant graphs,
tables, and figures. A
detailed process that
follows the selected
computing
methodology,
framework, and uses
the appropriate
standards exists.
There are scholarly
supported comparison
methods to contrast the
systems. Financial
analysis is included
that compares the two
system designs from a
managerial standpoint.
Over 1,500 words and
10 unique scholarly
journal articles from the
literature review that
justify the results and
validity of the
comparative analysis.
Systems analysis and
design results compare
some benchmarks
including cloud
computing capabilities,
high-availability,
scalability, and level of
security of the old and
newly designed
information systems
using relevant graphs,
tables, and figures
and/or processes that
follow the selected
computing methodology
exist with some
scholarly supported
comparison methods to
contrast the systems
and/or financial analysis
is included that
compares the two
system designs from a
managerial standpoint
and/or there is a
minimum of 1,500 words
and 10 unique scholarly
journal articles from the
literature review that
justify the results and
validity of the
comparative analysis.
Systems analysis and
design results miss
benchmarks including
cloud computing
capabilities,
high-availability,
scalability, and level of
security of the old and
newly designed
information systems
using relevant graphs,
tables, and figures
and/or processes do not
follow the selected
computing methodology
and/or there is
insufficient scholarly
supported comparison
methods to contrast the
systems and/or financial
analysis does not
adequately compare the
two system designs from
a managerial standpoint
and/or there is not a
minimum of 1,500 words
and 10 unique scholarly
journal articles from the
literature review that
justify the results and
validity of the
comparative analysis.
Substantially
unmet or not
present
and/or
quotes more
than 5% of
the writing or
use of
existing
information
system
40 pts
Systems Analysis and Redesign Project: Phase 3 Grading Rubric |
BMIS530_D01_202340
Criteria
Systems
analysis and
design
Ratings
Points
90 to >82 pts
82 to >75 pts
75 to >0 pts
0 pts
Advanced
Proficient
Developing
Not Present
ER data model (2),
class diagrams (2), UIs
(2), and architecture
diagrams (2) are more
thorough and detailed
than the textbook
examples, follow
appropriate and
advanced UML
techniques, and meet
comparative industry
best practices and
standards. Diagrams
show an extensive
knowledge of the
system being
designed. ER data
model diagrams meet
3NF, have at least 5
tables each, have
accurate primary and
foreign keys, accurate
field types, and proper
cardinality. Minimum of
5 classes and 15
functions and methods
exist in each class
diagram. UIs follow
industry HCI standards.
Architecture diagrams
include accurate
routers, switches,
firewalls, load
balancers, servers,
databases, storage
area networks,
middleware, and other
appropriate systems for
cloud computing.
ER data model (2),
class diagrams (2), UIs
(2), and architecture
diagrams (2) are as
detailed as the textbook
examples, mostly follow
appropriate and
advanced UML
techniques, and meet
comparative industry
best practices and
standards and/or
diagrams show an
knowledge of the
system being designed
and/or ER data model
diagrams meet 3NF,
have at least 5 tables
each, have mostly
accurate primary and
foreign keys, accurate
field types, and proper
cardinality and/or a
minimum of 5 classes
and 10 functions and
methods exist in each
class diagram and/or
UIs follow some industry
HCI standards and/or
architecture diagrams
include mostly accurate
routers, switches,
firewalls, load balancers,
servers, databases,
storage area networks,
middleware, and other
appropriate systems for
cloud computing.
ER data model (2), class
diagrams (2), UIs (2),
and architecture
diagrams (2) are not as
detailed as the textbook
examples and/or do not
follow appropriate UML
techniques and/or meet
comparative industry
best practices and
standards and/or
diagrams do not show
knowledge of the system
being designed and/or
ER data model diagrams
fail to meet 3NF, have at
least 5 tables each, have
mostly accurate primary
and foreign keys,
accurate field types,
and/or proper cardinality
and/or less than a
minimum of 5 classes
and 10 functions and
methods exist in each
class diagram and/or UIs
do not follow industry
HCI standards and/or
architecture diagrams do
not include accurate
routers, switches,
firewalls, load balancers,
servers, databases,
storage area networks,
middleware, and other
appropriate systems for
cloud computing.
Substantially
unmet or not
present or
proper
screenshots
do not exist
for each
diagram or
use of
existing
information
system
90 pts
Systems Analysis and Redesign Project: Phase 3 Grading Rubric |
BMIS530_D01_202340
Criteria
APA,
Grammar,
and Spelling
Ratings
Points
20 to >17 pts
17 to >16 pts
16 to >0 pts
0 pts
Advanced
Proficient
Developing
Not Present
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.
Paper contains fewer
than 5 errors in
grammar or spelling that
distract the reader from
the content and/or some
errors (3-7) noted in the
interpretation or
execution of proper APA
format and/or
inadequate organization,
headings, and flow of
the main concepts exist
and/or notable absences
in required APA
formatting elements
such as: Title page,
running head, font type
and size (Times New
Roman 12 point), and
line spacing.
Paper contains fewer
than 10 errors in
grammar or spelling that
distract the reader from
the content and/or
numerous errors (7+)
noted in the
interpretation or
execution of proper APA
format and/or inadequate
organization, headings,
and flow of the main
concepts exist and/or
notable absences in
required APA formatting
elements such as: Title
page, running head, font
type and size (Times
New Roman 12 point),
and line spacing.
Paper
contains
more than 10
errors in
grammar or
spelling that
distract the
reader from
the content
and/or
numerous
errors (10+)
noted in the
interpretation
or execution
of proper
APA format
and/or
inadequate
organization,
headings,
and flow of
the main
concepts
exist.
36 to >33 pts
33 to >0 pts
0 pts
Proficient
Developing
Not Present
Minimum of 2,000 words
and 8 diagrams exist of
original student
authorship that shows
mastery and knowledge
of systems analysis and
design and/or a
minimum of 10 unique
scholarly peer reviewed
journal articles from
well-respected IT
journals exist that relate
to and sufficiently
support an operational
systems analysis and
design.
Less than 2,000 words
and 8 diagrams exist of
original student
authorship that shows
mastery and knowledge
of systems analysis and
design and/or there are
less than 10 unique
scholarly peer reviewed
journal articles from
well-respected IT
journals that relate to
and sufficiently support
an operational systems
analysis and design.
Substantially
unmet or not
present or
proper
screenshots
do not exist
for each
diagram or
use of
existing
information
system
Overall
40 to >36 pts
Requirements
Advanced
Over 2,000 words and
8 diagrams 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.
20 pts
40 pts
Total Points: 200