- https://utk.campuslabs.com/courseeval/ The site will be available until midnight on Monday, April 30
- Note on the future of the final project repositories
I have no plans to remove or modify this repository, so you can continue working on it if you chose to do so. I create a separate github organization for each class I teach, so nothing will be changed or overwritten (by me) and your ownership of the repo will remain. It the code produced might be of wider use, I'd recommend you add a suitable license to it (e.g., gpl, apache, or mozilla) to clarify the terms of use.
Furthermore, I'd like to make these projects public (if you have not made them public yet), but this can only be done if everyone on your team agrees to do so for your project. You can keep it private, copy it to another organization (after the end of semester) if you wish, however. I enabled administrative privileges on your repo for all team members, so you can make it private/public add/remove team members, etc.
Longer term, the projects will stay here as long as GitHub keeps them, and I'll try to find alternative home if GitHub decides to end its hosting.
- PhoneGames
- Quantum Stock Optimization
- Unity Simple Role Playing Game
- Crypto-Currency-Sentiment-Analysis
- GiftLink
- WaitList
- Growlist
- QuantifyingCorruption
- MitosisSimulation
- Select-A-Spot
- work on finishig the remaining presentations
- DnD_Town_Generator
- Arc&Arcana
- OoT_Randomiser
- Work on final project
- If you want to change presentation times talk to another team that might be willing to switch
- If all else fails, it is possible to fall back to the final exam time slot
- Final Project Report is due May 1!
- A part of the Final Project Report will be your individual reflections about the final project. It is an assignment on Canvas, separate from the FINAL_REPORT.md that should be in your teams repository. Both are due May 1, 2018.
- OSS "Sprint 6: Make and document your contribution" is due
- Work on final project
- OSS "Sprint 5: Select the first task" is due
- Spring Recess
- Minimum viable system demo/Project Status due
- Please use TA office hours or class time or schedule (at least 15min) separately with TA
- Project numbers
- Archery_and_arcana.md
- Cryptocurrency_Sentiment_Analysis
- DnD_Town_Generator
- Gift_Planner.md
- Growlist App - Team TBA
- Mitosis_In_Unity
- OoT_Randomizer
- PhoneGames
- Quantifying_Corruption
- Quantum Stock Optimization
- Select-A-Spot
- Unity Simple Role Playing Game
- Waitlist_AppIntroduction (10 points)
- Grading rubrik for status report (in your projectrepo/STATUS.md)
- Customer Value (5 points)
- Technology (15 points)
- Team (10 points)
- Project Management (10 points)
- Reflection (10 points)
- Tone, Grammar,Formatting, Readability (10 points)
- Demo (30 points)
- Demo has to match requirements on what is to be implemented in the status report
- Total (out of 100 points)
- ACM Webinar: Risky File Analysis
- The event will be online
- It will start at 12:00 PM Eastern Daylight Time
- Register, listen, and, for extra credit, submit a question
- Work on final project
- Present a demo
- Software Patterns: continued
- Work on final project
- Present a demo
- OSS "Sprint 4: Develop a plan for contribution" is due
- Minimum viable system demo/Project Status introduced
- Software Patterns
- Work on final project
- Validation and verification (continued)
- Validation and verification (continued)
- Validation and verification (continued)
- Validation and verification
- Finish OSS Sprint 2: make sure all sources are specified and (if not available) explained.
- Finish OSS Sprint 2: guidlines on scoring sprint 1 and 2
- Please have an issue assigned to you for your course project
- Work on Final Project and OSS contribution
- Benjamin Klein will run a workshop on Git Workflows
- Work on Final Project and OSS contribution
- Work on Final Project and OSS contribution
- Final OSS projects selected and submitted in (by editing the same oss/yournetid.md file)
- Make sure you have no past due isues https://github.com/COSCS340/oss/issues?q=is%3Aopen+assignee%3Ayourghid
- If so, do what is requested and add "Ready to review" label once done
- Work on Final Project Sprint 1 due
- Work on selecting OSS project
- Clarification on how to use issues assigned to you (OSS):
- Pay attention to the due date
- Add 'ready to review' label when the changes are done: then somone else will close the issue
- Each final project needs a milestone for each sprint and a backlog
- Issues that are worked currently belong to current sprint
- Each person needs to be assigned to at least one issue from the current sprint
- Each issue can not have more than one person assigned to it.
- When the sprint ends and the issues's story is implemented and tested issue gets label 'ready to review'
- Another person from the project then clrevies and, if satisfied, closes
- If the story is incomplete, the issue is moved to the next sprint
- ** Only criteria for project selection are needed *** Actual projects are due next week for options see Section A. The instructions on how to submit are here
- An issue for each one of you has been created regarding this assignment
- I will create another issue for the project selection
- Continue lecture on software architecture
- Please make sure you have only one person assigned to an issue at one time, I will not count additional assignees as working on the issue. Also, assign only to issues that are in the ** current ** sprint with a due date. Current report
-
Will decide upon criteria to be used for OSS project selection
-
Final opportunity to finish Assignment 1: [see details: thanks @robobenklein]https://github.com/COSCS340/How-to-Gcloud/blob/master/README.md) or original instructions
-
Ensure all projects have milestones and all members are assigned an issue (for the current sprint milestone)
- Create a milestone "Backlog" (or whatever name) with no due date : it will be your backlog
- Create a milestone per Sprint with a due date
- Create issues in milestone "Backlog"
- Create two labels "Ready to review" and "In Progress"
- Add an estimate of effort [x] in points in the issue title, for example: "Restructure data [3]" (use 1 2 or 3)
- Create Pull Request in sprint milestone with tag "Ready to review"
- If you'd like you can use zenhub
-
Will start lecture on Architecture
- Chose an Open Source project to contribute to
- Will work on finishing Assignment1: Create a docker container, deploy to GC, provide IP adress of the machine so that I can check if the web service is running: see recent status (as of last commit) in results.md Thank you @bobzap66 for the presentation in class
- Please take a look at your team status, milestones and assignees are still missing.
- Software Process
- Contributing to an Open Source Project
- Software Process
- Contributing to an Open Source Project
- Asignment1 due on Friday
- Finalize sprint implementation as issues for your project
see QC Project as an example - Software Process
- GC assignment: create a docker container automatically built by dockerhub, deploy to GC, provide IP adress of the machine so that I can check if the web service
- Continuous build (dockerhub)
- Google cloud
- Create sprint issues for your project repository
- Project proposal is due
- See requirements in https://github.com/COSCS340/lectures/blob/master/project_proposal.pdf
- Issue trackig / sprints
- Version Control (continued)
- Introduction to Software Engineering
- Not all project ideas are submitted to https://github.com/COSCS340/students
- Please submit if you have not done so
- Please chose one of the projects if you have not done so (many are looking for participants)
- Discuss project proposals (as opposed to ideas)
- Please accept the invitation to github organization for the class (you got invite in the email, but, if you misplaced it, you can accept invite at https://github.com/COSCS340 there will be a line at the top suggectin to accept the invite)
- Project options
- Please submit project idea as a pull request to students repository (in an A_prjname.md file, please prepend A_ to project name to differentiate from netid.md files)
- Title
- Basic idea
- Technology used
- Members (and if additional members are needed to get up to four)
- Version Control slides
- Introductions
- Course: [COSCS-340]
- ** MK404 MWF 12:20PM-01:10PM (Min Kao 404) **
- Instructor: Audris Mockus, audris@utk.edu office hours MK613 - on request
- TA: Andrew Valesky, avalesky@vols.utk.edu office hours MK204 Mon&Wed: 1:15 to 2:15
- TA: Walton Macey, wmacey@vols.utk.edu office hours MK618 Tu&Th 9:30 to 11:00
- Need help?
Simple rules:
- There are no stupid questions. However, it may be worth going over the following steps:
- Think of what the right answer may be.
- Search online: stack overflow, etc.
- code snippets: On GH gist.github.com or, if anyone contributes, for this class
- answers to questions: Stack Overflow
- Look through issues
- Post the question as an issue.
- Ask instructor: email for 1-on-1 help, or to set up a time to meet
The course will provide basic software engineering approaches with a focus on intense practice.
- Version control and issue tracking
- Basic software project management
- Build (cmake)
- Test
- Deploy to the cloud
- Participate in open source projects
Upon completion, students will be able to work in teams, break work into iterations, write tests, deploy their software to the cloud, and participate in open source projects.
All the assignments and projects for this class will use github - no exceptions.
The work will have to be described via issues on github that will be used to define and track progress.
The resulting program will be deployed via docker container to google cloud.
Each student will submit at least one contribution to an open source project.
While we have strived to make the programming component of this course straightforward, we will not devote much time to teaching programming. You should feel comfortable with:
- How to look up syntax on Google and StackOverflow.
- Basic programming concepts like functions, loops, arrays, dictionaries, strings, and if statements.
- How to learn new libraries by reading documentation and reusing examples
- Asking questions on StackOverflow or as a GitHub issue.
These apply to real life, as well.
- Must apply "good programming style" learned in class
- Optimize for readability
- There is no required programming language or framework: the project should choose the most relevant technology for its objective (i.e., the technology that would require least effort to implement the desired system). For example, it could be analytics/deep learning application on top of gensis/tensorflow/caffe, a mobile app, a web service, an algorithm library, ....
- There is no specific domain the project should focus on, but it has to solve a real or perceived problem. In other words, its important to motivate the project. There is no need to choose from a list of example topics, such as this or this.
- Best results are typically achieved if you work on a problem that you deeply care about. I would recommend, therefore, to choose a problem primarily based on your interests.
- Agree on an editor and environment that you're comfortable with
- The person who's less experienced/comfortable should have more keyboard time
- Switch who's "driving" regularly
- Make sure to save the code and send it to others on the team
-
Class Participation – 25%: students are expected to read all material covered in a week and come to class prepared to take part in the classroom discussions. Responding to other student questions (issues) counts as classroom participation. Class time will be also used for teamwork on the course project.
-
Assignments - 25%: Each assignment will involve writing (or modifying a template of) a small Python program or a documentation of an open source contribution.
- Deploying to Cloud: (5% of total course grade)
- OSS Sprint 1 and 2: (5% of total course grade)
- OSS Sprint 2 and 3: (5% of total course grade)
- OSS Sprint 4 and 5: (5% of total course grade)
- OSS Sprint 6: (5% of total course grade)
-
Project - 50%: one original project a group of 4 students. The project will explore one or more of the themes covered in the course that students find particularly compelling. The group needs to submit a project proposal (2 pages IEEE format). The proposal should provide a brief motivation of the project, detailed discussion of the data that will be obtained or used in the project, along with a time-line of milestones, and expected outcome.
Course Project: You will work in teams to propose, design, implement, and present a semester-long software project. Your project work must be done in groups of 4 (or 3 if a fourth member cannot be found). This work accounts for a major portion of your course grade (50%), so choose your teammates wisely. The course project consists of a series of presentations and deliverables that will be assigned throughout the semester. The grade breakdown is shown below:
- Project Proposal (10% of total course grade)
- Status Report (around Sprint 3) (15% of total course grade)
- Final Project (Report + Demo) (25% of total course grade)
Each student in the group should have a role and be able to explain their individual contribution to the project. We will take into account student feedback on the project and on their teammates at the end of the semester, but for the most part, teammates will receive the same project grades.
As a programmer you will never write anything from scratch, but will reuse code, frameworks, or ideas. You are encouraged to learn from the work of your peers. However, if you don't try to do it yourself, you will not learn. Deliberate practice (activities designed for the sole purpose of effectively improving specific aspects of an individual's performance) is the only way to reach perfection.
Please respect the terms of use and/or license of any code you find, and if you re-implement or duplicate an algorithm or code from elsewhere, credit the original source with an inline comment.
http://www.ece.rutgers.edu/~marsic/books/SE/projects/
http://nevonprojects.com/web-based-project-ideas-topics/
** There is no required textbook for the course ** several optional textbooks/online materials are listed.
-
Bash
-
Regular expressions
-
Databases
-
IEEE's "Software Engineering Body of Knowledge (SWEBOK)" version 3.0.
- Git and GitHub
- GitHub Pages
[Academic Dishonesty / Plagiarism]
Cheating and plagiarism are serious offenses and are grounds for dismissal from the course and an automatic F grade. Please read UT's honor statement. for more information on what constitutes plagiarism and what actions may be taken if the honor statement is violated. I have written a helpful guide to avoiding plagiarism. The guide is from my COSC102 course, but it is still relevant.
Any plagiarism/cheating on an exam will be an automatic F for the course and a referral. Any plagiarism/cheating on homework will result in a 0 for that homework or assignment.
Any repeat offenses in plagiarism/cheating will be an automatic F for the course.
Bottom line: It isn't worth it.....PLEASE don't do it!
Any cheating, plagiarism, etc. will be punished in accordance with the current version of Hilltopics. For more information see http://studentconduct.utk.edu/students/current-students/
[Grading]
See above
[MiniTasks]
Good quality commit messages
Issues that describe what is needed in a sprint
How to get a contribution accepted in an oss project
How to find project to learn from
The project quality index