Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
About
People
Publications
Teaching
Resources
Research Blog
Wiki Functions
Recent changes
Help
Licensing
Page
Discussion
Edit
View history
Editing
Software Engineering (Winter 2026)
(section)
From CommunityData
Jump to:
navigation
,
search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== Bot Project Task #4 ==== ;Task: Analyze the architecture of your assigned bot ;Due: Friday, February 6, 11:59 p.m. Pacific time. ;Deliverables: You are done with Task 4 if your group has written an architectural guide and added it to your main repository on GitHub (ARCHITECTURE.md). All group members should have made at least one substantive commit to the guide to receive credit. See list of steps for all the items you'll be graded on. ;Turn in: No need to turn in something for this; Dr. Champion should be able to grade your work right out of GitHub. '''Steps''' # Think about the levels or facets of system architecture involved in your project. # Identify a layer or aspect for each group member to cover. # Each team member should do at least one diagram from the following types: [https://en.wikipedia.org/wiki/Data-flow_diagram data flow diagram (DFD)], [https://en.wikipedia.org/wiki/Activity_diagram activity diagram], [https://en.wikipedia.org/wiki/System_context_diagram system context diagram], [https://en.wikipedia.org/wiki/Computer_network_diagram network diagram], [https://en.wikipedia.org/wiki/Control-flow_graph control-flow graph], [https://en.wikipedia.org/wiki/Class_diagram class diagram], [https://en.wikipedia.org/wiki/Use_case_diagram use case diagram]. If your chosen diagram is trivial, you should do more than one to receive full credit. # Be concise and accurate in your description and clear in your diagrams. Follow the linked instructions as best you can; [https://www.miro.com Miro] is a good tool for this, but you can use whatever tool you like; it's also possible to write diagrams in markdown in GitHub. ;Tips: * Divide up the work so that everyone has a piece to contribute * Include both system architecture and code architecture. * If you are short on ideas, here are a few: what patterns does your code use? If someone wants to add new functionality, how should they do that? How is npm involved? How does Codespaces work? How does your code make things happen in Discord? How is the network functioning? * Consider different audiences: your future self, a curious customer for your bot, a future employer * Feel free to use AI tools as a tutor or source for debugging any issues that come up, however you are responsible for the accuracy of the content.
Summary:
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see
CommunityData:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Tools
What links here
Related changes
Special pages
Page information