The goal of the project is to provide you with hands-on experience in applying systems engineering principles to design and develop a working application system. The project will be challenging and will require you to use a combination of agile and waterfall methodologies to develop the application system.
To meet the requirements of the course and to apply enterprise architecture (EA) concepts, you will need to complete the following:
Part 1: Operational Concepts
Prepare some elements of a Concept of Operations (ConOps) for the proposed system. Your abbreviated ConOps will contain the following sections:
Needs that motivate development of a new system (be brief and creative).
A brief description of your proposed system and how it is unique/different (be brief and creative).
Four or more user classes and their user characteristics.
Other stakeholders and their stakeholder characteristics.
Your document should be 3 to 4 pages in length (not including the cover sheet and the reference page). You should use GitHub for version control and project tasking and create a README for your team’s project. DO NOT use a Word document.
Part 2: Proposal
The proposal should clearly describe the motivation for the proposed work and the proposed solution along with its expected business value. You will need to:
Diagnose the problem
Prescribe a solution/treatment
Describe the work plan
Your proposal should also include initial (all possible) use cases/context diagrams for the client to review. You will need to incorporate the 10 tips for successful EA (https://resources.sun-associates.com/10tips.html) into your proposal. You should use GitHub for version control and project tasking and create a README for your team’s project.
Part 3: System Requirements Review (SRR)
You will need to complete a System Requirements Review (SRR) for your proposed system. The SRR will consist of a review of the system requirements with the client to ensure that they are complete, accurate, and meet the needs of the stakeholders. You will need to submit a report of the SRR to your professor. You should use GitHub for version control and project tasking and create a README for your team’s project.
Part 4: Preliminary Design Review (PDR)
You will need to complete a Preliminary Design Review (PDR) for your proposed system. The PDR will consist of a review of the preliminary design of the system to ensure that it meets the system requirements and is technically feasible. You will need to submit a report of the PDR to your professor. You should use GitHub for version control and project tasking and create a README for your team’s project.
Part 5: Application Development
Based on your proposal, system requirements, and preliminary design, you will need to develop a working application system using cloud computing technologies. You will need to choose one of the following application domains: healthcare or gaming. The project should include the following components:
Identify and organize cloud computing resources, tools, and services for your application system. This may include cloud compute, edge compute, and other cloud resources that can be used to support your application system. Real-world use cases for cloud and edge compute include:
Healthcare: Cloud and edge compute can be used to support telemedicine, health data analytics, and patient monitoring applications.
Gaming: Cloud and edge compute can be used to support online gaming, streaming, and virtual reality applications.
Develop the application system using any language you choose. The application system should be fully functional and meet the system requirements specified in your SRR and PDR documents. Use GitHub for version control, project tasking, and kanban. Create README’s for each team of students and for each project. Record Scrum sessions, which should be no more than 15 minutes each, and provide video recordings to your professor. Use scale-agile along with waterfall methodologies to develop the application system.
Your final application system will be evaluated based on the following criteria:
Functionality – Does the system meet the requirements specified in the SRR and PDR documents?
Usability – Is the system user-friendly and easy to navigate?
Reliability – Is the system reliable and performant?
Security – Does the system have adequate security measures to protect user data?
Scalability – Is the system able to handle a large number of users and data?
Your project will be graded based on the following rubrics:
Part Weight
Part 1: Operational Concepts 10%
Part 2: Proposal 20%
Part 3: System Requirements Review (SRR) 10%
Part 4: Preliminary Design Review (PDR) 10%
Part 5: Application Development 50%
TOTAL= 100%
Your final project is due on March 31, 2023. Be sure to provide all necessary documentation and deliverables in GitHub.
Good luck!
