Description

 SYSTEMS ANALYSIS AND REDESIGN PROJECT –

General Instruction

In addition to the project using a real company, which is required, there are two significant rules that must be followed in the projects.

SYSTEMS ANALYSIS AND REDESIGN PROJECT Instruction

The System Analysis and Redesign Project focuses on a 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. The project should highlight your advanced skills in information systems, displaying your knowledge of all domains of our field. This means your design should show proficiency in all stages of software development, parallel to the competency of a full-stack developer.

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 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 standards.

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 can be implemented. Designs that do not show proficiency in parallel programming code (e.g. a Class in Java, C++, and/or C#) are not very valuable at the more granular stage of design and thus this requirement. A full-stack developer should be able to take your designs and create the designed system.

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:

Stage 1: Introduction, problem statement, feasibility study, and project plan

Stage 2: Methodology to compare the old and new systems and the systems analysis

Stage 3: Results of comparison of the old and new systems and the systems design

Stage 1: Introduction, problem statement, feasibility study, and project plan

Stage 1: Report Requirements

This report must contain the following elements and every section must be well supported with scholarly information systems journal articles.

          a. Introduction and conclusion sections

                         1. You will write an introduction and conclusion to the project that is at least 500 words and well supported by more than 5 scholarly journal articles.

                         2. The conclusion should be the last heading and conclude the current phase and state the upcoming objectives and deliverables in the next phase.

                         3. 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).

                        4. Introduce the primary goals of this particular phase, the coinciding objectives, and the outcomes

              B. Problem statement

                        1. 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 an information system using your knowledge.

                        2. At least 500 words and 5 unique and relevant scholarly journal articles should exist in the problem statement that gives the precise information system problem, the specific information system you will address (e.g. an ERP, CRM, Supply Chain Management system, E-commerce system).

                  3. Note the problem must meet later project specifications so assure it is a comprehensive information system

                           i. It must be able to be designed into an innovative, highly available, security, and scalable 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. Enterprise Resource Planning systems (ERPs) are a great example of an information system that meets these requirements but there are many other systems as well, just be sure they cover all the objectives of all phases of the project so that you are successful

          c. Feasibility Study and Project Plan 

                        1. 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

     2.The plan should focus on updating the old information system to the new cloud-based information system

                  3. Comprehensive project charter and plan. Project plan components must parallel the assigned reading

                        4. Project scope, alternatives, and feasibility

            5. Project schedule, tasks, resource estimations, and comprehensive work break down structure (WBS)

                 6. Financial budget, cost, and benefit analysis i. The final outcomes should address these from a managerial and strategic business perspective

STAGE 2 INSTRUCTIONS: Methodology to compare the old and new systems and the systems analysis

In Stage 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.

Stage 2 Report Requirements

This report must contain the following elements and every section must be well supported with scholarly information systems journal articles.

1.      Introduction and conclusion sections

a. Please update your previous introduction and conclusion sections as appropriate with at least 500 words and 5 unique and relevant scholarly journal articles

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 stage 2, 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.

2.      Literature review and systems analysis and design methodology

a. Constructs a well-supported review of literature related to the problem. Write 2,000 words and 15 unique scholarly journal articles that justify the methodology, its reliability, and its validity in comparing and contrasting the information systems.

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

3. 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.

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. You can refer the 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.

Overall requirement for Stage 2

2,500 words and 15 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. and 8 diagrams exist of original student authorship that shows excellent mastery and knowledge of systems analysis and design.