System analysis and design conclusion

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.