1 / 14

Exciting Computer Science Projects: Engage in Real-World Software Development

Welcome to CS162! In this course, you'll embark on thrilling projects that simulate real-world software engineering challenges. Collaborate in teams to build large-scale systems, apply engineering best practices, and focus on design, testing, and performance analysis. From a concurrency-oriented chat server to cloud technologies and distributed systems, each project will enhance your technical skills while pushing you to meet deadlines. Gain hands-on experience with tools like version control, build systems, and testing harnesses. Prepare for an exciting journey where you'll create software that users can rely on!

zan
Télécharger la présentation

Exciting Computer Science Projects: Engage in Real-World Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Computer Science 162Section 1 CS162 Teaching Staff

  2. Welcome • Computer systems are exciting! • Thousands of engineers in industry building huge systems at scale • You get to make real stuff that people can use

  3. Projects Overview • Goals of projects: • Learn to work in teams • Use good engineering practices • Requirements specification • Design Document • Implementation • Testing • [Performance, reliability, ...] analysis • Understand lecture concepts at the implementation level • Your TA will be your guide through this process

  4. A Good Project Lifetime • Day 0: Project released on course webpage • Day 1-13: Team meets, discusses and breaks up work on design and necessary prototyping • Day 14: Final design document due • Team reviews the document with the TA • Day 15: Implementation begins • Day 20: Implementation is finished. Team switches to writing test cases. Design doc has been updated to reflect the implementation. • Day 21: Iteration and performance analysis. • Day 23: Team puts finishing touches on writeup and gets to bed early.

  5. Way to Not have fun • Day 0: Project design • Day 13: Oops, we were busy. Throw something together and meet with the TA. • Day 14: Your TA is “concerned” in your design review. • Day 21: The l33t hacker in your group makes a pass on the implementation. It mostly works. • Day 22: Someone else fixes some bugs • Day 24: Run out of time debugging; don’t make it to analysis or updating design.

  6. Project 2 Project 1 Chat Group Manager Admission Control Chat Group Pool Clients User Manager Project 4 Project 3 • Load Balancer • Distribute chat groups • across machines • Synchronization/caching DB + Security

  7. Project 1: Concurrency • Topic: concurrency • People have wildly different experience with this • Most people cannot write correct concurrent code • That’s just a fact, sorry  • Individual portion • Questions about POSIX API • Solve a toy synchronization problem • Group portion • Design and implement the core of a parallel chat server • Define users, groups, messages • Implement message delivery respecting the desired semantics • Test your work

  8. Project 2: Network Communication • Allow clients to connect over the network • Design the protocol state machine • Connection and assignment to thread • Admission control and authentication • Steady state • Disconnection • Always “have an answer” – deal with failure – it can occur ANYWHERE in the protocol • Implement most of a server, and just enough of a client to fit the testing harness

  9. Project 3: Cloud Technologies • Deploy your chat server on an EC2 instance • Add user authentication and logging via MySQL • Add offline message support • This might be a “catch up” assignment if you have fallen behind: you will need your codebase to be relatively stable before working on #4.

  10. Project 4: Distributed Systems • Make your system scale by allowing your system to run on multiple servers • Design and test a failure protocol for your chat server • This is tricky • Evaluate your design using appropriate metrics and tools. • Are there any performance anomalies? Try to explain them and fix the bottlenecks • Make sure you drive your system off a cliff

  11. Optional Extra Credit • Can be added to any of assignment 2, 3, and 4 • Not worth all that much, we’re still working it out • File transfer • Management console • Additional desktop client support • Connection encryption • Something else fun...

  12. Tools • You will use appropriate tools • Revision control: svn, git, etc. • Build systems: make • Test harness: (we will provide) • In some cases we will ask you to implement to our interfaces so we can autotest your work • Feel free to use other tools you find useful • static analysis • debuggers • ci tools • etc... • You could also consider using a software engineering methodology to structure your work, e.g. agile development; only if it helps you.

  13. Questions about Projects?

More Related