INFM 603 - Information Technology and Organizational Context
Project Three:   Final Project and Implementation (due Dec. 6, 2018)

Overview:   It is of course no surprise that your final project is to get your team together to implement the application that you’ve designed in project 1 and project 2.   The goals of this phase of the project are (a) experience what it’s like to build and “debug” a working system in a team environment, (b) understand the relationship between design and reality, and (c) solidify your grasp of the different pieces of web technology (i.e., HTML, databases, and scripting) that we’ve learned about in this class.


Project Three will be worth 15 points total, equal to the combined total of project 1 and project 2.    This gives you a chance to make up for any deficiencies up to this point, to impress “management” that you’ve solved the problem you set out to solve and acquired some valuable skills along the way.

You will complete work on the project and will turn in, as described below, a short “user guide”, a short paper covering lessons learned and the other points below, links to and/or copies of pages and scripts used, and a presentation to be covered in class.    You will have just about 15 minutes for the in-class presentation, so if you plan to show a demo of your project, it has to be set up carefully and it has to be short.    The demo will be included in your 15 minutes.    Questions are not; you can expect a few minutes of questions.


            Here is what you’re expected to turn in and to cover in your presentation:

             a) Implementation (5 points).   You should try to implement all the major capabilities of the project.    At the very least, this should include some basic web pages with text and graphics, forms for entering data into the database, and server-side scripts for querying and updating the database and displaying information to users.    For this part, turn in no more than a few pages of “user guide” (what the system does, and how to use it) and a pointer to the starting point(s) (URLs) for your demo.

               b) Lessons learned (2 points).     Write a short report (again, a few pages) on what you had to do to make it all work, any changes required of the design and/or database as you completed the implementation, major issues encountered and any great ideas you had.

               c) Security (1 point).    If this were a real system, what would be the security issues?      How would you address them?

               d) System scale, concurrency, and reliability (1 point).   Let’s say your system takes off, and you have thousands of users who depend on it on a regular basis.   Explain some of the issues and challenges you might have, and how these would be addressed.     How has your design been separated from the hardware and software infrastructure?    Are there any ways the implementation now depends on any particular infrastructure (examples – operating system, hardware configuration, specific machines or architectures)?

               e) Future work (1 point).     If you had a few more weeks to work on the project, what would you do with them?     What results would you expect to see?

              f)  The presentation itself (5 points).    Usually it’s a Powerpoint, and you’ll have about 10 minutes in class to present it.   You’ll also be expected to turn in a copy of whatever you present in class.   The presentation should have an introductory, some meaty examples (with coverage of the issues above) and a summary.    Since it’s very short, the success depends on being able to hit the key points clearly and succinctly and to tie them together with examples.