PORTFOLIO ASSIGNMENT

ASSIGNMENT INSTRUCTIONS

This assignment will bring together the learning from the previous assignments. Collect together all your work thus far and put it into a coherent unified high-level design for the system. You are welcome to use previous assignments verbatim where appropriate although you should be sure to incorporate the feedback on them. You should also incorporate code from the previous assignments as necessary to illustrate your designs. If you use small snippets, then they can go in the document, otherwise, you should organize the code in a coherent package structure and submit it with the document in a zip file.

 

Don't use plagiarized sources. Get Your Custom Essay on
PORTFOLIO ASSIGNMENT
Just from $13/Page
Order Essay

 

FORMATTING AND STYLE REQUIREMENTS

  • Refer to the UCOL Format and Style Requirements(Links to an external site.) on the Course Homepage, and be sure to properly cite your sources using Turabian Author-Date style citations (Links to an external site.).

SAMPLE OUTLINE

Below we include a sample outline that you may use for inspiration. It is not required that you follow this outline; this is provided merely as a guide. Should you use it you must remove all the text that describes the purpose of the relevant section.

INTRODUCTION

Describe the payment processing system from a high level in your own words.

REQUIREMENTS

Provide the basic requirements that your system will satisfy. Include a section on “non-requirements” as appropriate. The latter would be a good place to mention that you won’t support payment types other than credit cards.

HIGH-LEVEL DESIGN

Capture the major components of the system and how they interact with one another. A mixture of text and diagrams would be best here. Make sure you cover the full control flow, starting from the user and ending at the credit card processor.

COMMUNICATION

Document the communication protocol you will use across the entire system. It’s possible, even likely, that different parts will use different protocols (e.g. HTTP between the user’s web browser and the payment system; JSON internally to the system; proprietary database driver to communicate with the backend.

RESOURCE PLANNING

Include your resource plan for the system along with how it will scale as your user base grows.

DEPLOYMENT

Describe the environment within which the system will run, including and services it will depend on.

IMPLEMENTATION

Include any implementation details you consider necessary to complete this work.

APPENDIX

We covered many topics in this class. Consider whether any of these belong in your design:

  • Privacy
  • Security
  • Reliability
  • Replication
  • Specific cloud providers

ORDER NOW »»

and taste our undisputed quality.