Course: Messiah College CIS 411, Fall 2018 Instructors: Joel Worrall & Trevor Bunch Name: YOUR NAME GitHub: YOUR_HANDLE (if appropriate) Collaborators: [Names of colleagues you worked with on this assignment]
See the lecture / discussion from CIS 411. You'll need to be familiar with the content from this lecture to complete this assignment.
Note: you are free to work with classmates on this assignment. Good architecture is born out of collaboration - not reclusive mad-scientist behavior. However, if you work with colleagues:
- You must specifically note your collaborators by name at the top of your report.
- You may not completely copy each others work (diagrams and descriptions, even if your solutions are identical).
Review the proposals for the Serve Central project. Let's imagine that the project has been granted (relatively) unlimited resources if they can deliver a version 1 release in 120 days. As a result, the team decides to implement an MVC architecture for its version 1 release, delivering functionality through a responsive web application.
Based on the this and this presentation:
- Document two use cases of your choosing
| Use Case #1 | |
|---|---|
| Title | |
| Description / Steps | |
| Primary Actor | |
| Preconditions | |
| Postconditions |
| Use Case #2 | |
|---|---|
| Title | |
| Description / Steps | |
| Primary Actor | |
| Preconditions | |
| Postconditions |
- Highlight a table of at least four models, views, and controllers needed to produce this project.
| Model | View | Controller |
|---|---|---|
- Generate and embed at least one diagram of the interaction between an Actor from the Use Cases, and one set of Model(s), View(s), and Controller(s) from the proposed architecture, including all the related / necessary services (ex: data storage and retrieval, web servers, container tech, etc.)
Note: You are free to use any diagraming tool and framework that you want as long as it clearly communicates the concept. I typically use a UML System Use Case or UML Sequence Diagram. If you do not have a preferred diagramming tool: draw.io or lucidchart are good cloud-based options.
After an initial release and a few months of operation, Serve Central encounters a tremendous growth opportunity to extend their service and provide a volunteer recuitment and management interface to four of the primary volunteer entities in the United States. As such, a reevaluation of the architecture is required, one that allows:
- Thirdparty services to both input and retrieve data from the Serve Central model/datastore. (For instance, receiving volunteer opportunities from United Way chapters across the country.)
- Building organization-specific interfaces on top of the Serve Central business and data logic. (For instance, allowing the registration services of Serve Central to be embedded in the website of local churches, ah-la Stripe embedding.)
To support these objectives:
- What architectural patterns (either of those presented in class on based on your own research) are appropriate? Justify your response, highlighting your presumed benefits / capabilties of your chosen architecture(s) as well as as least one potential issue / adverse consequence of your choice.
- Using your preferred diagramming tool, generate a diagram of the new Serve Central architecture that supports these two new requirements.
18 months into the future, Serve Central is experiencing profound growth in the use of the service with more than 100k daily, active users and nearly 1M event registrations per month. As a result, the Gates Foundation has funded a project to build and launch a mobile application aimed at encouraging peer-to-peer volunteer opportunity promotion and organization.
In addition to building a new mobile application interface, the grant requires that the project prepare for the following future needs:
- Consuming bursts of 10k+ new volunteer opportunities per hour with a latency of less than 15 seconds between submitting an opportunity and it's availability in the registration service.
- Supporting a volunteer and event data store that will quickly exceed 50TB of data
- Allowing authorized parties to issue queries that traverse the TB's of data stored in your datastore(s).
- Enabling researchers to examine patterns of volunteer opportunities as a way of determining future grant investments.
What archictural pattern(s) will you employee to support each of these needs? What will the benefits and consequences be? Why are changes needed at all? Justify your answers.
- Create and embed a comprehensive diagram of your final architecture (i.e. one that meets all the requirements of this lab, including Step 3).
- Augment/improve the assignment. Suggest meaningful changes in the assignment and highlight those changes in the extra credit portion of your lab report.