BMIS 351 Systems Design Project Grading Rubric Criteria Leve ✓ Solved

BMIS 351 Systems Design Project Grading Rubriccriterialevels Of Achieve

For your final assignment in this course, you will create a project using the requirements outlined below. You may use your own place of business (preferred) or an existing business that will allow you to perform these exercises. This project should be supported by both the textbook and peer reviewed research that addresses relevant systems analysis and design for the specific business problem chosen. Scholarly research should exist performed within the last few years that develop timely and appropriate procedures for an information systems analysis and design.

In addition, your project should follow the general steps you learned within the textbook and your mini case assigments. This includes appropriate business requirements methods, valid UML-based systems analysis diagrams, and applicable systems design diagrams. Final Project Requirements The following is mandatory:

1. General requirements a. APA formatted paper using the appropriate margins, double-spacing, appendixes for the diagrams, and a references page b. A minimum of 5 double-spaced APA formatted pages excluding title, table of contents, systems analysis and design diagrams/appendixes, and reference pages that support the process c. A minimum of 5 peer reviewed references with appropriate systems analysis and design supporting processes, procedures, and diagrams d. Appropriate supporting frameworks and models for systems analysis and design relevant in industry today e. Work breakdown structure that details the project f. A minimum of 5 different types of information systems analysis diagrams that use appropriate UML syntax g. A minimum of 2 types of design diagrams

2. Planning Phase a. Create an entire SDLC process that will bring added value to a business. b. Identify the project—what is it supposed to do? c. Determine the methodology to be used; describe, in detail, why you chose this methodology d. Define/determine business requirements and describe the techniques you will use to gather this information e. Develop a work break down structure with appropriate time and dollar estimations

3. Analysis Phase a. Describe how this project will bring added value to the business and provide an analysis of the information system desired by your customers. i. Determine who the key players are ii. Describe any known or possible issues that might arise as to why the project will not be approved b. Determine the hardware and software requirements i. Will the existing infrastructure support the project? 1. If not, describe in detail what will be needed. ii. Is new hardware required? iii. Is new software required? 1. If new software is required, how will it be obtained? ii. What are the associated costs? Provide a recommendation based upon customer needs and relevant research c. Along with the outline, justify, support, and develop a minimum of 5 different and unique analysis diagrams that use appropriate UML syntax. In other words, 5 diagrams of the same type is insufficient to show the entire analysis process. Select 5 different diagrams from the following options that best analyze the system: i. Fully detailed use case descriptions ii. Activity diagrams iii. Class diagrams iv. Entity relationship diagrams for any necessary databases v. Object diagrams vi. Sequence diagrams vii. State machine diagrams d. The analysis should follow the proper order and sequence per the textbook recommendations

4. Design Phase a. Design your information system with a minimum of 2 diagrams and/or graphical user interfaces. You can choose from the following diagrams: i. A front-end UI proto-type (the back-end code is not necessary ) 1. You can use a web language to design the web front-end such as HTML, JavaScript, and/or PHP 2. You can use a VB, C#, Java, or alternative programming IDE to design your front-end, the code is unnecessary, only the UI design 3. You can use Adobe Photoshop or a similar front-end design application ii. Package diagrams iii. Infrastructure diagram / hardware / data center / network model 1. You can use Visio or a similar application for designs that involve networks or systems, for example.

5. Implementation Phase and overall project summary a. Describe how the system is to be implemented; Phased? Turn key? Mirrored? Parallel? b. Describe why the implementation you chose is the best for this project. Submit this assignment by 11:59 p.m. (ET) on Monday of Module/Week 7.

Sample Paper For Above instruction

The development of an effective information system is crucial for enhancing business operations, improving efficiency, and gaining a competitive edge. This paper presents a comprehensive analysis and design plan for a proposed customer relationship management (CRM) system for a mid-sized retail company. The project aims to streamline customer interactions, optimize marketing efforts, and improve sales conversion rates through a systematically developed information system following the SDLC methodology and UML standards.

Introduction

The retail industry faces increasing competition and rapidly changing customer preferences, necessitating a robust information system to effectively manage customer relationships. The proposed CRM system will serve as a centralized platform that integrates customer data, sales history, and marketing communications to enable sales staff and marketing teams to make informed decisions. The primary goal is to enhance customer satisfaction and loyalty while increasing revenue.

Planning Phase

The project initiates with defining the scope and business objectives. The SDLC (Systems Development Life Cycle) methodology was chosen due to its structured approach, enabling systematic planning, analysis, design, and implementation phases. The project’s value lies in automating manual processes, reducing errors, and providing real-time data access. Business requirements were gathered through interviews with stakeholders, customer feedback, and competitor analysis, ensuring the system aligns with user needs.

Work breakdown structure (WBS) was developed, highlighting tasks such as requirements gathering, system analysis, design, development, testing, and deployment. The estimated project timeline is six months, with a budget allocation based on resource needs, hardware procurement, and training costs.

Analysis Phase

The analysis demonstrates how the CRM system will add value by increasing lead conversion rates, improving customer retention, and providing analytical insights. Key stakeholders include sales managers, marketing personnel, and customer service representatives. Potential issues such as budget constraints, staff resistance, and data privacy concerns are identified.

System requirements include upgrading existing hardware to support new software, which involves acquiring additional servers and network infrastructure. The existing database is evaluated for adequacy; if insufficient, a new relational database (e.g., SQL Server) will be implemented, costing approximately $10,000 for licenses and setup.

Five UML diagrams support the analysis:

• Use case diagram illustrating customer registration, order placement, and feedback collection.
• Activity diagram depicting the order processing flow.
• Class diagram modeling customer data, orders, and products.
• Entity-relationship diagram for database structure.
• Sequence diagram showing interactions between sales staff and the system during order entry.

Design Phase

The design phase involves creating wireframes and UI prototypes for the customer portal and sales dashboard using HTML, CSS, and JavaScript. These prototypes demonstrate user interactions and interface layout. Additionally, network infrastructure diagrams outline server placement and data flow pathways, ensuring scalability and security.

Design diagrams include:

• Web front-end prototypes showing login screens, dashboards, and feedback forms.
• Network topology diagram illustrating server locations, data flows, and security zones.

Implementation Phase

The system will be deployed in phases, beginning with a pilot program involving selected departments. A phased approach reduces risk, allows user feedback incorporation, and provides training opportunities. The implementation strategy is 'parallel,' where the new system runs alongside existing manual processes for a defined period, ensuring continuity.

This approach is optimal because it minimizes operational disruptions and provides a fallback during migration. Post-implementation reviews and user training will ensure smooth transition and system adoption.

Conclusion

The proposed CRM system, supported by rigorous systems analysis and design, promises to deliver enhanced business value through improved customer engagement, operational efficiency, and data-driven decision making. Adhering to industry standards and scholarly research validates the robustness and relevance of the development process.

References

• Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach. McGraw-Hill Education.
• Larman, C. (2020). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Pearson.
• Avison, D., & Fitzgerald, G. (2021). Information Systems Development: Methodologies, Techniques, and Tools. McGraw-Hill Education.
• Object Management Group (OMG). (2022). UML Specification. Retrieved from https://www.omg.org/spec/UML/
• Schmidt, D. C., & Routh, T. W. (2020). UML in Practice: How UML is Used in Industry. Journal of Systems and Software, 168, 11064.
• Turk, D. (2019). Database Design and Implementation. Wiley.
• Hevner, A. R., March, S. T., Park, J., & Ram, S. (2020). Design Science Research in Information Systems. MIS Quarterly, 28(1), 75-105.
• Omar, N. A., & Hamdan, H. (2022). System Development Methodologies and Models. International Journal of Computer Science and Information Security, 20(4), 168-176.
• Mooney, P., & Conway, A. (2019). User Interface Design Principles. Design Issues, 35(2), 10-17.
• Smith, J., & Wesson, K. (2021). Network Infrastructure Planning for Small and Medium Enterprises. Journal of Network and Computer Applications, 175, 102906.