CSC4081/2 Computer Applications Practicum

Course Description:

Part one of an independent software development project selected in conjunction with the instructor. Includes the project planning, requirements specification, and design phases of a significant software system. Prerequisite: CSC3004 (Software Development), and senior standing or instructors permission.

CSC4081-CAP-syllabus-FA15.doc: Syllabus

Method of evaluation:

  1. Deliverables: Each deliverable will be graded. Each deliverable may be turned in one week prior to the due date for a pre-evaluation. Deliverables for the first semester include the project proposal, system specification, software requirements specification, and a system design.
  2. Activity Log: Students will turn in a weekly log of all hours worked and description of project activity. The expectation is that the student will work 2-4 hours per week in the fall, and 5-7 hours per week in the spring. The log for each week should be entered as a Word document, using the format provided by the instructor. These will be submitted as Blackboard Assignments each Monday for the preceding week. The cumulative log will be included in your project workbook. You must work at least 2 hours each week on the project. Any week with less then 2 hours will not receive work credit for that week. The log for the preceding week must be posted to the course web site every Monday.
  3. Weekly Meetings: Students will meet individually with the instructor for 15-45 minutes each week, to review work in progress, discuss the deliverables, and any problems that need to be resolved.


Project Information


Project Ideas

  • Solar Data Display for the Belize Solar project. A basic viewer of the data is here: Needs to be developted into a more complete, general purpose, and efficent system.
  • Internet of Things project. A wide range of very inexpensive (<$10), wifi and bluetooth enabled boards available. These little cards (about the size of your thumbnail) can be interconnected to a wide range of inexpensive devices and sensors (In: sense light, voltage, temperature, movement, position, humidity, etc., Out: control lights, relays, motors, etc.) These boards will have a SDK, and programs can be written for whatever purpose you wish to achieve. MVNU can provide the basic hardware, you come up with an application (sense the openning of a door and send an alert to a smart phone, for example), and build it! Particle, gridconnect. May be two projects for one application (embedded side and smartphone side)
  • A computer langauage learning extension for the learning system being developed at MVNU. This system would present a learner with a simple programming problem in one of several common languages (C++, Java, JavaScript , PHP, etc.). The student would enter a possible solution. The system will run the code entered, evaluate the result, giving suggestions and allowing for additional attempts.
  • An iPhone or Android app for managing and planning a CS major at MVNU. This app would allow a student to select a CS major, and show the required classes, and the year/semester they should be taken. Each course coould be "checked" off as completed. If the student could do a what-if, and select a different track, and see the resulting schedule change. The app would look up the schedule and major information on a CS server so that changes, and additional information would show up in dynamically over time on the app (for example, as specific class times were set for future classes, or if requirements change, they would be updated in the app. Two students could work together, one on each platform.
  • An iPhone or Android app that automatically manages all important dates and times for CS students. The professor would use a simple web interface to push (and revise) assignments to a database server, due dates, test dates, etc. The app on the smart phone would run, grab these from the serve, and populate the information into the devices calander. This could all include two students, one for each platform.
  • A smart phone poll instant quiz/poll system. A web interface would allow a faculty to create a multiple choice question either before class, or right in class. Students with the app could answer the question, and submit. The faculty would see, and could display for class, a pie or bar chart of answers fro ma web page. They could also view specifc answers by specific students on their smart phone (to keep this information private from the class). This project could involve 2-3 students to work on each phone platform, and to build the web/database backend.


Milestone Date
Project Proposal Sept 17
System Requirements Specification with prioritized requirements Oct 31
Research results on possible solutions/designs (with requirements matching table) Oct 7
High level architectural design proposal Oct 21
Design proposal (with justification) Nov 5
Equipment and materials specification Nov 12
Complete design Nov 26
End of Fall Semester Writeup Dec 11
System documentation Mar 11
System test specification Mar 18
Systems test results Apr 1
End of Spring Semester Writeup April 7
System presentation and demonstration 1-4pm Apr 28
Final Deliverables Apr 29

Work Cycle

Spiral Model

Cycle completion Deliverables and Expectations

  1. A demo of the current work (with code)
  2. A (revised) set of objectives and specifications.
  3. A risk analysis of the current project, along with a choice for the next (highest risk) aspect to implement
  4. A revised design and plan for next iteration *
Topic attachments
I Attachment Action Size Date Who Comment
Docdoc CSC4081-CAP-syllabus-FA15.doc manage 40.0 K 2015-09-14 - 18:10 JimSkon Syllabus
Topic revision: r13 - 2016-03-31 - JimSkon
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback