by

Octave Mini Projects

14:332:423 Computer and Communication Networks

Octave Mini Projects -


There are two types of projects in this course:

  • Wireshark labs, described on another webpage.
  • TCP congestion simulation project, described below.
See example reports for student TCP projects. More examples of student project reports will be made availableto course instructors upon inquiry.

A modern interface to the Octave bug tracker is given by SavannahAPI. Discuss with the developers there how to fix that bug or upload a patch there. Some bugs have already patches attached. Help testing those patches. Help updating outdated patches to the latest development version (this requires some Mercurial knowledge). Machine learning projects with source code, machine learning mini projects with source code, python machine learning projects source code, machine learning projects for.net developers source code, machine learning projects for beginners with source code. The world's number one cellular module vendor provides simple, scalable, and secure ways to add wireless to any IoT or M2M system with 5G, LPWA, 4G LTE, 3G and 2G solutions.

The purpose of this project is to provide the students withhands-on experience with computer networks. I believe that hands-onexperience leads to deeper understanding of the class material.

There are three deliverables for this project:

  1. Document describing the software design
  2. Live demonstration of the software
  3. Final report describing the software and simulation results.
The due dates for project deliverables are listed here.
♠ ♥ ◊ ♦Octave mini projects pdf

1. Simple TCP Protocol Simulator

First go to this web site and download the TCP protocol simulation software and its PDF documentation. To run the software, follow these simple instructions.

This software, written in the Java programming language, implementsa simple network simulator which simulates the TCP protocol. Seethe lecture notes for description of the TCP protocol. Curently the simulatorsupports Tahoe, Reno, and NewReno versions of the TCP congestion control algorithm.

2. Project Teams

Each team consists of ≤5 students. All students in a team areworking on the same project. Requests for working individually or with a smaller team cannot be accommodated due to the staff shortage.

You should form the team by the date given here and notify by emailboth the TA (if any) and the instructor about the team member names and their email addresses.

All team members must take part in all project activities, althoughresponsibilities may be divided so that different members take lead indifferent activities. But, no activity should be doneexclusively by a single person. While the volume of work of eachgroup member on each project component may not be equal, theircontribution to the overall project should equal out.

Many students find team work difficult due to different personalinterests and working habits. Therefore, each student should keeptrack of his or her contributions to the project. The exact breakdownof individual contributions must be provided to the instructor for each deliverable, so the individual grades can be fairly assigned.

3. Team Work

Here are some suggestions (none of this is required!) about team work:
  • Choose the team leader to serve as a focal point. Discussindividual skills and strengths (algorithm design, coding, reportwriting, etc.) and decide who will lead which part of work
  • Set the meeting agenda and time limits. Students are encouragedto confer frequently and work together on solving the problem
  • Decide how will the team communicate, e.g., email, Twitter, Facebook, blog, ...
Saying that “nobody asked me to do this or that, or, I did everythingthat I was asked to do” is an unacceptable excuseOctave Mini Projects. Each teammember should be proactive and not wait passively to beassigned responsibilities. Do not ask others what shouldbe done; rather, take initiative and suggest what should be done tomake your project successful. Take every opportunity to redistributeand/or rotate the responsibilities, make your personal suggestions beheard! Many times defining the problem and determining what needs tobe done is more difficult than actually doing it. Hence, problemdefining and task assignment must be contributed to by all teammembers, rather than by the team leader alone.

What is the role of a team leader?

First, keep in mind that having a team leader is optional.You should elect the team leader only if you believe this wouldfacilitate your group work.

The role of a team leader should not be misunderstood. The teamleader is expected to provide organizational and logisticalsupport, that is, to organize team meetings and keep track aboutwork progress. The team leader is not expected to setthe objectives, partition the tasks, and devise solution strategies.These responsibilities must be shared equitably by all teammembers.

It is a good idea to select the team leader based on his or hersocial/personal skills, rather than their technical skillsand knowledge. Past experience has shown that people with poor socialskills turn out to be poor leaders and their teams end up beingdysfunctional, regardless of their technical knowledge.

There are neither benefits nor responsibilities for theteam leader. The leadership is a voluntary responsibility, just tofacilitate the team work: help organize the meetings and remind theteam members about commitments and deadlines. The team leader willnot receive any rewards (e.g., higher grade) for serving inthis capacity. The leader is also not accountable for “failing to lead” and cannot be blamed for the lack of communication skills orgeneral lack of success of the team’s project. For example, theleader has no such responsibilities as “knowing what needs to bedone,” assigning work loads (fairly or otherwise), or distributing theresponsibilities. This must be agreed upon by consensus. Mostimportantly, each team member must be proactive, rather thanwaiting to be assigned the duties by the team leader or anybodyelse.
Remember, All team members are equallyresponsible for all aspects of the project. Each deliverable will be graded as a whole so all team members should ensure that a bad part does not downgrade the whole.

What if your team is not functioning well?

If you notice that your team does not function well or the teamleader tries to misuse his or her role, and this could negativelyimpact your project performance, you should make every effort todiscuss this with other team members. If the “problematic” teammembers (including the team leader) refuse to cooperate, you shoulddiscuss your concerns with the instructor, the sooner the better.
Complaints about poor team functioning expressedat the end of semester will be ignored.

4. Software Design Document

For this deliverable, every team is expected to submit a document describing the design of the software for their project. The due date is given here.

Projects

The design document should contain the following:

  1. Cover page using the same format as the final report.
  2. Breakdown of individual contributions to the project for each team member as specified for the final report.
  3. Flowchart of the program that you will develop to completethe assignment:
    It makes sense, although it’s optional, to split the chart in three parts, to reflect the structure of the simulatednetwork:
    1. Flowchart of the algorithm running on the sender
    2. Flowchart of the algorithm running on the router
    3. Flowchart of the algorithm running on the receiver
    Here is a partial flowchart forthe reference example.
    To learn what a flowchart is, grab an intro book on programming or visit the Wikipedia flowchart webpage.
  4. Brief textual description of the flowchart:
    1. Briefly explain the algorithm
    2. Define each variable or parameter used in the flowchart
    3. State what programming language and the development environment you’ll use; etc.
Submit the flowcharts only for the modules that you will develop anew or modify from the existing simulator implementation. Do not submit flowcharts for the existing modules that you will use unmodified.

Octave Mini Projects Free

Where to find information about TCP:

  1. Lecture notes (Chapter 2), available here
  2. The Internet requests for comments:
  3. The course textbook, Peterson & Davie, Sections 5.2 and 6.3

Email your algorithm design as a single PDF document on or before the due date (get a PDFwriter you can use from Windows).
Submit only one design document for each team.

5. Project Demo

For this deliverable, every team is expected to give a live demonstration of the software they developed for their project. The presentation date is given here.

The project demo will be held during a class period in the regularclassroom. Each demo shall last no more than 15-min. If youhave preferences regarding the order of presentation, please send ASAPan email to the TA to schedule your demo.
If you cannot bringyour own notebook/laptop, please contact the TA immediately to arrangea computer to demo your software. In this case you should bring yourpresentation software and slides on a USB thumb memory card.

Each group should email us at least one day before the demo, stating explicitly that they will present their project. Do this even if you will use your own computer and do not care about the presentation order.
We need this notification to plan the presentations. If we do not receive an explicit notification, we will assume that this group does not plan to present and will not be able to accommodate last minute requests.
The students who did not send this notification will not be allowed to present.
All team members should attend the demo presentation. We will assume that theabsent students were not involved in the project work.
The studentswho cannot make it should send email before the demo, with thereason for their absence explained.
The demo should include:

  1. brief (no more than 3 slides!) introduction to your project
  2. live demonstration of your program
  3. slide presentation of different charts obtained by running yoursoftware with different input parameters (see the statement of yourprogramming assignment in the lecturenotes as to what charts to prepare.
Please bring a printed copy of your slides handouts for the TA and the instructor.
Note: Do not prepare any report for the demo. The report will be required as described next.
Make sure to email us the breakdown of individual contributionsimmediately after the demo. If you don’t, we will assume that all team members contributed equally to the demo.

6. Final Report

For this deliverable, every team is expected to submit a document describing the design, implementation, and experimental results. The due date is given here.
Only one report is required for the project, to be submitted by thewhole team (one report per team). This report should be aself-contained document, including any and all flowcharts orother documents that you handed in earlier in the semester.

Example reports from past years can be found here.

Every report must have a cover page containing:
.the course title,
. group number,
. project title,
. submissiondate, and
. all team-member names.
Negative pointswill be assigned to reports missing- or having an incomplete cover page.

The second page of each report must detail the breakdown ofindividual contributions of each team member to the project.Quantify, as a percentage, each student’s contribution to the projectcomponents:
. algorithm design,
. coding,
. debugging,
. analysis of results
. report preparation,
. Other: any other project-related effort.
The reports missing- or having an incomplete contributions breakdownpage will be returned for revision before grading.
If all team members feel that everyone contributed equally to the project, just write “equal contributions”.

The rest of the report must contain the following sections:

  1. Introduction:
    State the objective of your project (you can copy your assignment andelaborate as needed -- remember to include the revisions of theassignment, if any);
    Provide some background information.
  2. Software Design:
    Provide a block diagram of your system before presenting the detailedalgorithm flowcharts;
    Describe in detail youralgorithm, as a pseudo-code or via a flowchart. For any detail ofthe flowchart that needs additional explanation, put a footnote labelon the flowchart, and provide the footnote text on a separatepage;
    Specify exactly the user-controllable parameters to beentered when running your program: what are the allowed values, whatare the recommended values, are there any values that should beavoided?, etc.
  3. Implementation:
    Specify the programming language and any other tools used for thedevelopment;
    Describe briefly the content of each source-code file (describe only the files that you modifiedsignificantly from the original, or the new files that you introduced);
    Provide a brief user’s manual (a README.txt document) describing how to run your program and modify the user-controllable parameters.
  4. Results and Discussion:
    Present your experimental results in graphical charts and tables (you can use Microsoft Excel for this, see example);
    Each chart/table shouldhave a caption and should be referenced and described in the text;
    Calculate the sender utilization, whereapplicable (state explicitly the exact formula you used to calculate the sender utilization).
    Discuss the results in detail, provide technicalexplanations and comments on the system performance, etc. Explainany unexpected or non-obvious results.
    Cite the literature or websources where the reader can find more information about the theory ofthe observed phenomena.
    Reports that contain only charts but without description andexplanation will receive a poor grade. Technicaldiscussion and explanation of the results is critical.
  5. References:
    List all the references (books, journal/conference papers), web pages(include URL and webpage title) that have been used in the project.

When you get your program working, run it and plot the chartssimilar to those in the class notes. Calculate the senderutilization, where applicable.

Email your report as a PDF file (get a PDFwriter you can use from Windows).
NOTE: Do not mail any other formats, such as Microsoft Word.

Mini Projects In Ece

7. Project Grading Policy

Octave Mini Projects

Each student must be aware that a major part of his or her finalgrade depends on the team project. The failure to cooperate andinvest equitable amount of effort may lead to undesirable outcomes.To help us assign the grades fairly, you are required to exactlyspecify the individual contributions to the project (as described above).

Mini Projects For Cse

Each report will be graded as a whole and the grade will beassigned. Next, the total grade will be divided up to individual teammembers, based on the reported contributions breakdown and the judgedquality of the components of the project. Hence, it is quite possiblethat members of the same team receive different grades.

Late reports will be levied a latepenalty of 10% per day, up to 3 days late. After that, no credit willbe given, unless more than 40 % of team members (e.g., at least3 out of 6) provide a written excuse from a physician. Since thedeadlines are known well ahead, there will beno extensions for any of the deadlines. Please don’t botherasking.

See also the overall course grading policy here.

Contact the instructor immediately should you have any questionsor concerns about the grading policy.


BACK TO:

Octave Mini Projects Free

Ivan Marsic
Thu Oct 6 00:11:52 EDT 2011