University of Dayton
School of Business Administration
Fall, 2018

MIS 465
Systems Analysis & Design in Teams
(MIS Senior Project I)

FINAL VERSION (PENDING ANY NECESSARY CHANGES)

Any substantive changes to this document will appear with Light Pink Highlight.

Something interesting to read about grades. 

Get your grades (available on Isidore), and teams
Jump to course schedule

This page was last modified on Monday December 03, 2018

INSTRUCTORS:
OFFICES:
PHONES:
EMAILS:
WEB PAGES:

CLASS MEETINGS:
OFFICE HOURS:
Dr. David Salisbury/Mr. Stephen Hall/Mr. Dev Nanda
Anderson Center, Room 104/Room 106/Room 125
937.229.2938 (department office)
salisbury@udayton.edu/shall2@udayton.edu/snanda1@udayton.edu
http://www.davesalisbury.com/classtuf/MIS465_475/default_465.htm
http://isidore.udayton.edu (follow links on Isidore)
M/W/F 125PM-320PM, MH 102 (except on special days as noted in schedule)
Salisbury - 10-12 MW, 5-6 M, 10-12 R (email usage is encouraged) or by appointment. 
Hall and Nanda - contact to obtain their hours.
Hours subject to change due to unforeseen circumstances. Any changes will be communicated to students via email.

PLEASE NOTE:  IN THE EVENT YOU ARE TAKING THIS (OR ANY OF MY CLASSES) ONLINE, YOU ARE RESPONSIBLE TO HAVE A FUNCTIONAL INTERNET CONNECTION.  NO ACCOMMODATION WILL BE MADE DUE TO MISSED EMAILS, INABILITY TO STREAM VIDEO/AUDIO, OR TO ACCESS COURSE RESOURCES ON THE ISIDORE WEBSITE.  BY TAKING ANY CLASS ONLINE YOU ARE AGREEING TO THESE TERMS.  THIS STATEMENT WILL APPEAR ON ALL MY SYLLABI REGARDLESS OF NEED.

Course Overview

This course is the first of two offered to students majoring in MIS as a capstone learning experience.   In this course you will create deliverables for a live client with a live project that their organization needs to have completed.

This capstone course affords you an environment in which you may draw upon your learning in previous MIS courses and apply these concepts and current best practices for the analysis, design, implementation, operation, control, and evaluation of information systems. This course features project teams of students doing systems analysis, design, and implementation of a real world MIS project. In addition, students will manage projects, maintain client relationships, assist with organizational and technology change, apply various methodologies and tools, learn to allocate time and other resources, manage project risk, work closely with team member and clients, and communicate about the development effort via written and oral means.

Course Objectives

The overall goal is to broaden and deepen each student's knowledge and skills in the development and delivery of management information systems.   Specifically students will be taught to:
  • Recognize that successful systems development is firmly rooted in responding to identified business needs within an organizational context. Successful systems analysts must have a broad understanding of and consider their clients' organizational structures, culture, human factors, and processes.
  • Apply the technical fundamentals of successful information system analysis, design, and implementation by using accepted methodologies and techniques as appropriate. 
  • Apply the principles of modern project management to planning and controlling the development of information systems, considering technical and behavioral issues.
  •  Demonstrate the ability to be an effective contributor in an information systems team setting and in interacting with clients and supervisors. 
  • Demonstrate oral presentation and written communication skills in applicable areas such as project presentations and status reports, client relationships, systems documentation, project management, team management and systems development and acquisition strategies.
As with all courses in the School of Business Administration at the University of Dayton, this course attempts to advance the University and School mission, to wit: The School of Business Administration is a learning community committed in the Marianist tradition to educating the whole person and to connecting learning and scholarship with leadership and service in an innovative business curriculum designed to prepare students for successful careers in the contemporary business environment. 

Course Text & Documents

Some of you may choose to get the books at the UD bookstore.  However, it is anticipated that some will engage in whatever searches are necessary to secure the appropriate books at the lowest cost.  I am not responsible for books that do not match.   

Valacich, J. S. and George, J. F.  (2017).  Modern Systems Analysis and Design, 8th edition, Upper Saddle River, NJ: Prentice Hall Publishing (hereafter Valacich & George).  Please be aware that this is the same text as used in MIS 380.  

Readings and other documents are available at Isidore

Other materials will be distributed as necessary, either electronically (on Isidore) or in class.  Students are expected as part of their professional development (and class participation) to be active consumers of content that may aid in their growth as IS professionals.  In addition to articles identified and provided by the instructors, it is expected that students will also identify and recommend resources to the class.

All students should have a functional laptop computer with appropriate software

Course Procedures

Key concepts and accepted practices of MIS will be developed and applied through assigned readings, class discussion and project assignments. In addition, participation in a project team will offer each student the opportunity to utilize this knowledge and other applicable experiences in the enhancement/development of a real world MIS project for an organizational client. Further, students will have the opportunity to learn from the experiences of other project teams through their role of being active members of the audience during project-related presentations. 

In support of this methodology, project assignments are to be completed and handed in for review and evaluation as scheduled. All project assignments will be discussed in class.

Each project team will be expected to develop and maintain a documented Project Portfolio as their MIS project progresses through the applicable phases of the Systems Development Life Cycle (SDLC) or of an alternative methodology acceptable to the instructors. Suggested contents of this portfolio would include defined products, outputs, and deliverables of the phases of the selected methodology and other documentation that communicates the progress of the assigned MIS project. This Project Portfolio will be evaluated and is expected to be a key source for the variety of designated project reports.

The use of Information Technology is an important element of this class's methodology. The classroom's podium supports needed software including multimedia. Anderson Center and Miriam Hall provide both computer labs and project team cubicles. The U.D. Learning Village and remote access capabilities provide connections from student residences. Each team will decide the best way to share documents between themselves and their clients.  The Isidore site will be used to share documents with instructors.

Student & Instructor Roles

Course participant roles will be modeled as in the prototypical consulting services organization. The roles of students and instructors are similar to those of systems analysts/consultants and systems development managers/managing partners, respectively. Students, within teams, organize, run, and conduct projects. Each team is self-organized (with defined roles) and led, and members utilize a peer evaluation to measure each team member's contributions to their project. Work is defined, assigned, and finalized via decisions made within each team. Instructors assign teams and projects. Instructors serve as course organizers and resources for teams on the term projects. Instructors are also evaluators who assess student performance (both team and individual). Please be advised that the instructors reserve the right to grade Project Team Elements (see below) differentially based on the instructors' judgment and on individual evaluations done by each team member.  Instructors review the progress of both projects (including teams) and individuals through scheduled reports, presentations, and meetings. They assess the quality of team submissions and processes, and provide advice and guidance when requested or as required by the course syllabus.

Course Assignments

A large proportion of each student's grade in this course will be assessed on the basis of the student's performance on various assignments that are expected to be completed through the semester. All assignments are to be completed by your assigned teams unless otherwise stated on the assignment. All assignments for this course are to be made via the World Wide Web, at the URL noted above, or on Isidore

Timeliness of Assignment Submission

It is important to submit assignments on time. All assignments are due on the assigned date. Late assignments will not be accepted save in the case of prior arrangement or provision of acceptable evidence (in the instructor's judgement) that justifies the absence or delay.  In any case, late assignments are subject to penalties as deemed appropriate by the instructor.

You should also be aware that your team is responsible to see that assignments are submitted properly. I am not going to be chasing people down to make certain that they have submitted their work. In addition, due to the number of assignments in a class like this, your team is also responsible to keep backups of all submitted work in case something gets lost in the shuffle.  Finally, marks which have been posted for one week are final.  Hence, you should keep track regularly of your course marks.

Finally, to discourage procrastination, I will offer no assistance on class assignments within two business days of when they are due. This policy will be strictly enforced.  If an assignment is due on Wednesday (as an example) the last assistance I will render ends at 2PM on Monday. 

Class Attendance/Participation - Class  & Meeting Decorum

While there are a relatively limited number of class meetings, you should be aware that your actions in the classroom environment should demonstrate intellectual engagement in the course content, and as well respect for your classmates and for your instructor.   As such, talking audibly, passing notes, and other similar juvenile behavior simply have no place in a university classroom. If you find yourself unable to avoid chatting with the person next to you, you should consider sitting elsewhere in the class. Expect to be called out when such behavior is observed.

You should also be aware that how you interact with clients reflects on you, your instructors and the MIS program.  Hence, you are expected to act in a professional manner in your interactions with clients.  Examples include but are not limited to being dressed appropriately for class (when clients or guests attend as scheduled on the syllabus, slacks and a nice shirt is the
minimal appropriate dress), scheduling meetings well in advance so that those who need to be present can be, and communicating using appropriate media.  Texting and email are not conversational tools; use a phone or schedule a meeting if you need to have a conversation.  Emails should also be answered in a timely fashion. You should NOT cancel a client meeting unless there is an emergency.  Examples of emergencies that may keep individuals away from a meeting include death in the family, road accidents, and serious illness.  This list is not exhaustive, but is intended to indicate the importance of keeping a meeting.

Other behaviors that are disruptive to others' learning involve various electronic devices. Cell phones, pagers and similar electronic communication devices should be turned off and stowed below the desk in a case or bag during all classes. While these devices are useful in their appropriate context, they create a disruption to the learning environment when they go off in class. Further, leaving the room to take a cell phone call is both inappropriate and rude, and also causes a disruption to the learning environment. As a consequence, failure to comply with this policy will result in appropriate disciplinary action, up to and including referral to university judiciaries.

Related to class attendance, even though classes will not meet every day you should assume that the block of time from 1200-150 on MWF is class time.  As such, scheduling work hours or other non-class commitments during class time is forbidden and will have a negative impact on your grade.  The reason we don't meet every day is to give you more time to schedule team and client meetings; it is not free time. 

Relevant to computer use (either in laptop required sections or in the lab), engaging in IM sessions, web-browsing, reading your email and other behavior of this type means that you are not paying attention to the material being discussed, and which will unfavorably affect your participation mark. Almost invariably this results in disruption to the learning environment as students who have not been paying attention find themselves behind and ask questions that have already been addressed. When you are in the classroom, you are expected to be engaged intellectually.

The instructor reserves the right to limit or prohibit use of any programmable devices (e.g. programmable calculators, laptop computers) and devices for communication and data storage (including but not limited to camera phones, cell phones, pagers, storage media or PDAs) at any time in the classroom. Refusal to comply with a request of this nature will result in sanctions being assessed as appropriate.

Please do not leave the class once you have chosen to attend -- it tends to be distracting for the rest of the class. If you must leave early, please sit near the door to make your departure unobtrusive, or do not attend at all. Please do not be late when you attend. Too many people coming after class starts creates a real disturbance. I reserve the right to take corrective action if it becomes a problem.

You should also be aware that being late for classes is no excuse to receive extra time on in-class activities or assignment submission deadlines. To arrive late disrupts the learning environment and, unless there is ample reason (see approved reasons, below) also demonstrates lack of respect for your classmates.  If you are late for class on a day with a required in-class activity you will have less time to complete this. Finally, when assignments are due at the start of class, arriving late to class (i.e. significantly after the assignment has been taken up) is grounds for the assignment due that day to be considered a late submission.

Please also be aware that we will have guests and clients in class from time to time.  On these days minimal dress code will be nice slacks/skirt and shirt/blouse. 

The instructor reserves the right to take corrective action if these issues create problems.

Please know that the intent of these policies is not to be unreasonable; from time to time a student may have reasonable need to leave the classroom prior to the end of class, or may have a legitimate reason that they are late. For example, he/she may be ill, may need a drink of water, may need to avail him/herself of the restroom facilities, or in winter for those driving weather can be a challenge. Further, there are emergency situations in which constant availability via electronic communication may be necessary. In this case, simply notify the instructor of the situation and a reasonable accommodation can be made.

Readings and Deliverables

While there is not a large amount of material to be covered through this course, there is a lot of stuff to do.  Hence, it is rather easy to fall behind. Please ensure that you stay current in your readings and deliverables -- it is expected that you will have read in advance the material to be covered in class on a given day, and be able to discuss it.

Communication with the instructor

While we are around a lot, nobody is in the office perpetually. Consequently, much interaction with your instructor will be through e-mail (salisbury@udayton.edu/shall2@udayton.edu/snanda1@udayton.edu).  To facilitate communication with you, be certain that the email address your instructor has via UD is one where you can get mail, either directly or via forwarding.  Please be aware that you should review emails from your instructor regularly as you are responsible for anything communicated via email or in class. If you miss an assignment due date or other changes because you were not in class (or don't get it via email), it is your problem.

Grading Scale and Course Components

The grading scale and grading components are presented below. If you make any of the cut-offs, you will receive that mark. For example, if you earn 930 points, you will receive an "A" for the course, or if you receive 885 points, you will receive a "B+" for the course.

MIS 465 Grading Scale

Grade Assignment

Grade Components

(A)
(A-)
(B+)
(B)
(B-)
(C+)
(C)
(C-)
(D)
(F)

>=930
>=900 <930
>=870 <900
>=830 <870
>=800 <830
>=770 <800
>=730 <770
>=700 <730
>=600 <700
<600 (failure)

Individual Assignments/Exercises (400/1000 points)
Baseline Project Plan Presentations
Deliverable2/System Requirements Specification Presentation
Deliverable3/System Design Specification Client Presentation
Course Participation
PMI Baseline Project Plan Document & Schedule Review
Overall Client Individual Evaluation
Project Team Elements (600/1000 points)
Status Reports (3 per team @ 40 points each)
Baseline Project Plan
Deliverable 2/Systems Requirements Specification
PMI Baseline Project Plan Document & Schedule Review
Deliverable3/System Design Specifications
Overall Client Team Evaluation
Total


50
50
50
150
50
50

120
100
140
50
140
50
1000

Since the marks in my classes over the long term tend to look like a normal curve, I tend not to force an artificial curve. On the odd chance that there is a curve it will be applied only on the overall grade in all sections I teach. Thus, no question of curving will be entertained until after the final. In addition, no extra credit assignments will be offered; if you are unable to perform well on what has already been assigned, I don't wish to burden you with extra work.  Finally, I encourage you that if you are in trouble, try to demonstrate an effort to improve and ask for help. Do not fail in silence.

To provide more detail, the following is offered:

INDIVIDUAL ELEMENTS

The individual component of the course evaluation will be based upon the four following elements, totalling 400/1000 points:

1. Oral Presentations (150 points)

Each student will be required during the term to present project-related materials to the class and clients. Three of these will be graded and are associated with project requirements (see items 4.2.1, 4.2.2, 4.4.4, and 4.5.8 in the separate MIS 465 Project Guidelines document). The instructors, other students, and the clients will have opportunities to critique your oral presentation skills. At least two of your presentations will be recorded and you will be expected to hand in an individual self-critique, as part of a team Presentation Review Document (see item in the separate MIS 465 Project Guidelines document), for each of these oral presentations within a week following your presentation.

2. Attendance & Participation

Attendance, general participation, peer evaluations, and generalized faculty observations are explained below.

Attendance:  (40/150 points)

This mark is based on the fairly simple premise that if you don't show up you can't participate.  There are plausible reasons for missing, but these are limited in number and significant in impact.  I refer you to the the course policies on absence, below.  If it's not on the list it had better be something good and it had better be taken up with the instructor in advance.

Generally Acceptable Excuses for Rescheduling Exams, Late Assignments, etc.

  • Verifiable Illness
  • Death/Major Illness in the immediate family.
  • Required attendance at another university event.

General participation:  (40/150 points)

Participation is an important part of this class, given the emphasis on project-based activities, discussion, and review of peer work. Class participation will be observed and graded. Everybody starts at 75 (C), after which individual participation in class meetings (when held) will be scored thusly; -5 for missing, 0 for simply attending, 2 for saying something interesting or participating in a meaningful way.  The minimum possible points earned by a student are zero (0) points.   Please be advised that these sorts of scorings are not absolute - coming into class and saying something just to get the points is not particularly helpful.  Be active and engaged, show up when you're supposed to, keep up with things, and speak up when you have something to say  and your class participation will turn out fairly well.

Participation includes, but is not limited to, the following examples:

  • Answering questions, whether specifically called upon or not.
  • Making meaningful contributions to class discussions and course activities.
  • Attentiveness during class.
  • Asking relevant questions and/or making meaningful comments during team presentations.
  • Offering assistance to other teams.
  • Completing documentation and being present at critical points in the term (e.g., student profile sheets, draft documents, project preference sheets, attending client presentations, attending class devoted to team assignments, presentation reviews etc.)
  • Turning in all required, non-graded documents in a timely fashion. 
  • Responding to email communication in a timely manner.  Please note that failure to respond to email in a timely manner (i.e. that day sometime) will reduce your participation grade.
  • Identifying and offering useful class resources such as Websites, and other media.

Peer Evaluations: (50/150 points)

Each team will be expected to use a group peer evaluation form to measure each member's (including their own) level of participation and contribution to his or her team. As part of the preparation for each scheduled status report (see below for description), team members will be required to use their peer evaluations to develop a personal evaluation (e.g., a log of individual contributions, strengths, and areas for development) for inclusion in the written assessment. These group peer evaluations will be used as an input in determining individual participation grades as well as the Project Team elements of the grade.

General Faculty Evaluation: (20/150 points)

Please be aware that the faculty are reasonably observant and tend to notice things such as who does the most speaking in a meeting, who seems prepared, who comes by the office when the team needs something, who answers emails sent to the team, etc.  These sort of generalized observations will impact on individual participation grades. 

3. BPP Document & Schedule Review (50 points)

Each team will participate in a review where an external review team assesses their work. See item 4.4.5 in the separate MIS 465 Project Guidelines document. There will be an individual grade assigned to each individual in the team.

4.Client Individual Evaluation (50 points)

During the middle and end of the term, the client will be asked to evaluate each project team member relative to the project deliverables, conduct, and communications of the project's execution during the Fall term.  These forms are available in the course's Isidore site.

PROJECT TEAM ELEMENTS

The individual component of the course evaluation will be based upon the four following elements, totaling 600/1000 points:

1.  Graded Status Reports & Meetings (120 points)

There are 3 graded status reports (see item 4.1 in the separate MIS 465 Project Guidelines document).  These are generally due via a printed copy and electronically (i.e., posted to the Isidore site) not later than 1 pm the class day before scheduled Instructor-Team Meetings. These status reports are similar to reports that a professional consulting/project team would submit to its development manager, regarding progress, scheduled activities, issues to address, team dynamics, and a record of client communications.

2-4       Reports (380 points)

Teams are assessed based on the quality of the project work products (e.g., such as any prototype and document deliverables) reflected in the three main written project reports (see items 4.2, 4.4, and 4.5 in the separate MIS 465 Project Guidelines document, which are expected for your information system analysis and design project.  These reports are to be professionally written for both your clients and your instructors.  All project team reports must be submitted electronically (i.e., posted to the Isidore site) as well as in one hard copy. Also, your client will have an opportunity to not only "sign-off" on the acceptability of these reports, but will also be given an opportunity to provide the instructors with formal feedback on them.

As a general rule, it is a good practice to proof documents before submission.  Poorly written documents shot through with errors give a bad impression of you, your instructors and your program.  Further, documents should be formatted in such a manner that they read well when printed to paper.  Failure to do these things will have a negative impact on your grades. 

5.  BPP Document & Schedule Review (50 points)

Each team will participate in a review where an external review team assesses their work. See item 4.4.5 in the separate MIS 465 Project Guidelines document. There will be a group grade assigned to each group member.

6. Client Evaluation of Team (50 points)

During the middle and end of the term, the client will be asked to evaluate the project team relative to the project deliverables, conduct, and communications during the project's execution during the Fall term.  The form is available in the course's Isidore site.

INDEPENDENT SESSIONS

There will be various times throughout the term where you will have independent team sessions for part of or the whole class period.  These sessions are meant for you to work on your project either on campus or at your client's site.  If you will be working on campus you will be expected to arrange for a place to work.  You can reserve cubicles in the team rooms in AN 128 for this purpose.  MH 209 (Fridays only), the classroom assigned for this course, may also be available.  Check with Dr. Salisbury regarding availability.

NOTES

1. The group team member peer evaluations must be submitted by the team members to the instructor.  Each team member will submit to the instructor separately his/her individual peer evaluations on the same date as each status report submission. In the event a team member is evaluated poorly, a meeting between the team and the instructor (as observer) should be anticipated, during which the team will resolve any inconsistencies in the evaluations, and the member(s) of concern will be constructively confronted, with proposed remediation devised.  Evaluations are meaningless if they cannot be used to create improvement, so we expect you to provide sufficient feedback to team members over the semester as well as prepare peer evaluations that will have a positive impact on team performance as well as help address/resolve concerns. If the peer evaluation results indicate a peer is performing poorly, the group needs to constructively confront the poorly performing team member, verbally and before the status report meetings, and encourage him/her to improve participation.  The poorly performing team member must indicate in their personal evaluation what he/she is going to do to correct the poor performance.  In addition, the team member will be given a lower grade than the rest of the group on the project team elements that were due during the period covered in the status report (e.g. as low as 0 % on project team elements during this period).  If there is no improvement the instructor will intervene as appropriate. 

2. All teams and individuals must turn in written assignments as scheduled; otherwise they will be penalized at the instructor's discretion.

3. Teams scheduled to make their project presentations are expected to dress and conduct the presentations as though they were actually making a presentation in a business setting.  The presentation and audience response should be thoroughly professional.

4. Each team is required to turn in a document reviewing each of its own recorded presentations within a week following the presentation. This review should consist of an individual self-critique by each team member of his/her own performance as well as a group assessment of the overall performance. This critique is most easily accomplished while viewing the recording of the presentation and considering feedback provided by the audience. The critique should, at a minimum, describe your presentation's purpose and desired results and address the things you did well; areas needing improvement; and planned self-improvement efforts.  The instructors will provide appropriate feedback.

5. Failure to turn in any required, ungraded items (such as presentation reviews and peer evaluations) on time will result in penalties. Failure to turn them in by the end of the term will result in zero points on Course Participation.

6. MS Project is available on the SBA network and on Microsoft Imagine. All teams are required to use MS Project (or equivalent software) to support the documentation of their project schedules.

7. All students are encouraged to use a CASE tool (e.g., Rational Rose), for the MIS team project.  If the tool you prefer to use is not available on the network, please use the Technology Request workbook to coordinate making it accessible from the Team Lab (Anderson Room 128). You are urged to learn how to use all of the features of your selected CASE tool early in the semester.  Check the labs for other available tools.

8. PowerPoint is available on the SBA network. You are urged to use PowerPoint (or some other presentation graphics) for your formal presentations. For presentations, a projection unit is available in the classroom.  Plan ahead. Rehearse your presentations and be sure you are familiar with the operation of the audio/visual equipment you will be using.

Academic Dishonesty

I refer you to the UD Honor Pledge:

I understand that as a student of the University of Dayton, I am a member of our academic and social community; I recognize the importance of my education and the value of experiencing life in such an integrated community.  I believe that the value of my education and degree is critically dependent upon the academic integrity of the University community, and so in order to maintain our academic integrity, I pledge to:

In doing this, I hold myself and my community to a higher standard of excellence, and set an example for my peers to follow.  Instructors shall make known, within the course syllabus, the expectations for completing assignments and examinations at the beginning of each semester. Instructors shall discuss these expectations with students in a manner appropriate for each course.

I will vigorously pursue the prosecution of academic dishonesty. It is understood and that students often learn and work together; consequently you may be asking questions or getting help from others. Be very clear, however, that there is a reasonably obvious distinction between getting help and getting one's work done by somebody else. In instances where such misconduct is proven, I will invoke University of Dayton policy to the fullest extent, which is to say that, at minimum I will assign a zero to the relevant assignment, and, in more serious instances will assign the letter gread of "F" in the course. Please consult the most recent edition of the "Student Handbook" for further information on Student Code of Conduct and Academic Policies.

You should also note that the way individuals carry out their roles as a members of a project team could jeopardize the other members of the team with respect to academic misconduct. Specifically, if a team member fails to participate in the manner called for, and appends his/her name to the team's final product, each member of the team is deemed to have been academically dishonest. Thus, it is in each team member's interests to make certain that all team members participate appropriately, and to bring any occurrences of inadequate participation on the part of other members to my attention. Please be aware that the team defines adequate participation; it is reasonable to assume that on a given portion of the assignment some members will contribute more than others. However, this should balance out, and on the bulk of the assignments the level of participation should be equitable for all so that all team members receive a good educational experience.

On a related note, you should be aware that the nature of this course means that your faculty advisor will depend on the veracity of various reports that will be submitted by your teams.  Evidence of knowingly falsifying documents such as hours reported, periodic status reports, peer evaluations, client communication logs, meeting minutes, et cetera constitute grounds for an academic misconduct charge. 

Intellectual Property Rights

The advent of websites such as Course Hero forces your instructor to issue a reminder regarding the intellectual property rights of various persons or organizations, including but not limited to your instructor, clients, any guest speakers and course text author's rights. You should be aware that ALL assignments, examinations, worksheets, problems, projects, documents, recordings, or other materials distributed or used in this course cannot be reproduced, distributed, or transmitted in any form or by any means, including but not limited to scanning, photographing, copying, uploading, or other electronic methods, without the prior written permission of the instructor or copyright holder. Any violation of this notice may result in a charge of academic dishonesty, academic penalties, other University disciplinary action, and/or legal recourse.

Additional Learning Support for Students

The University of Dayton and your instructor are committed to providing equal access to its educational opportunities for all our students, including those in need of accommodation due to disability. Students who believe they have such need are invited to meet with your instructor privately to discuss specifics. Formal disability-related accommodations are determined by the Office of Student Learning Support using specific guidelines.  As a consequence, it is important that a student needing accommodation be registered with SLS and notify your instructor of your eligibility for such accommodation with a signed SLS Self-Identification Form. With this, and in consultation with the SLS, your instructor will devise the appropriate accommodation(s) for your need.

Even if you do not have special needs per se, you may find resources provided by the Office of Student Learning Support helpful, with a variety of services to assist you in achieving academic success at the university, including study skills classes and workshops, tutoring and consultations, et cetera. 

Five Easy Ways to Raise Your Grade

Some general stuff, and things we've found that apparently need elaboration over the years

Changes to the Syllabus

Since the main objective of this class is for you to learn relevant and useful stuff. I reserve the right to alter the syllabus as necessary to meet this goal. Any such changes will be announced, in class, and will be explained.

Finally

I took this position because I enjoy teaching. I genuinely care about you and your progress in the class. If you have a problem, complaint, comment, concern, etc., please schedule an appointment or drop in during open office hours.

Schedule--Subject to review and change.
Any documents and templates may be found on Isidore

Please note that Status Meetings for Mr. Hall's and Mr. Nanda's Teams will be scheduled by them and may not appear here.

Class Date

Anticipated Topics

Speakers, Topics & Items Due Student - Client - Instructor

August

W 22 Course Introduction & Overview NDAs to be signed in class, Student Profiles Due on Isidore site by 5PM
F 24 Client Presentations (River Campus, Room 2265)

All clients attend; all students attend
Project & Team Member Preferences due @ 5PM

M 27 Team Assignments, Client Presentation Feedback,  Review of Next Steps, Prepare for August 31 Session with Client, Discuss/Review Status Report Required Information, BPP Preview Team Assignments announced
W 29 Independent Team Session Agenda for Client Meeting on August 31 by 5PM
F 31 Client-Team Meetings (River Campus, Room 2380) All students attend
All project client coaches attend

Client project timeline and client(s) contact information due @ start of class (i.e. this will be gathered as part of the client meeting)
September
M 3 Labor Day (no class)  
W 5 Review of Client-Team meetings  (teams meet with faculty advisors - Salisbury teams will meet in 104 Anderson - my office). "One sentence" and "One/two Paragraph" project descriptions due BY START OF CLASS to Dr. Salisbury (all teams).  Submissions should be placed in your team Google Drive (under the "deliverables" folder as ONE FILE with a DESCRIPTIVE NAME (e.g. Sentence_Paragraph_Descriptions). 
F 7

Session on Development Methodology Selection

Guest Session on Project Management and Methodology Selection, PMI
Dev Nanda, TBD
Student resumes due NLT 5PM (emailed to Dr. Salisbury)
M 10 Independent Team Session
 
W 12 Independent Team Session  
F 14 Job Search Prep & Resume Review
Teams come at scheduled times - be there ON TIME, both for the opening and your team session

125-140 - General introduction / overview
140-200 - Teams 1 & 2
200-220 Teams 3 & 4

220
-240 - Teams 5 & 6
240-300 - Teams 7 & 8
300-320 - Teams 9 & 10
Guests on Resume Development TBD
M 17 UD Career Fair - 1-5 PM @ the UD RecPlex Status Report 1 due @ 5PM on Monday, September 17 (or 1 day before status report - which ever comes later).   Note that we are on a business day clock -  Monday meetings mean the status report stuff (see form in Isidore Resources) is due the Friday before - i.e. one business day before. 


W 19 Instructor-Team Status Meetings 1 / Independent Team Session.
 
 Salisbury m
eetings in 113 AC. 
125 Team 1 - 125
145 Team 2 - 145
205
Team 3 - 205


Mr. Hall and Mr. Nanda's teams (Teams 4-10) will meet on their schedules.
Status report previously delivered at least one business day before.
Client either comes in or calls in.   
F 21 Instructor-Team Status Meetings 1 / Independent Team Session.
 
Status report previously delivered at least one business day before.
Client either comes in or calls in.   
M 24 BPP Client Presentation Rehearsals
125-145 Team 10
145-205 Team 9
205-225 Team 8
225-245 Team 7
245-305 Team 6
Baseline Project Plan Draft & current Project Schedule (both optional) @ 12PM; electronic copies only

Presentation Slides Hard Copy due in class (one copy per faculty)
All teams must attend
W 26

BPP Client Presentation Rehearsals
125-145 Team 1
145-205 Team 2
205-225 Team 3
225-245 Team 4
245-305 Team 5

Presentation Slides Hard Copy due in class (one copy per faculty)
All teams must attend
F 28 Independent Team Session  
October M 1 Independent Team Session Read (for October 8) Wilco Construction Company, Parts 1 & 2 (available on Isidore under Wilco folder)Prepare as a team a review of this case including but not limited to ERD and DFDs (to Level 0  at least), decomposition chart & context diagram.  This can be done on paper and brought to class; it's for class discussion/practice.
Notification to Client of BPP Evaluation sent out
W 3  Alumni Panel on Career Planning, Client Relations Guest UD MIS recent grads TBD
Presentation Review due @ 125PM (put it in Google Drive in BPP folder) - one per team.
 
Final versions of one-sentance/1-2 paragraph descriptions due start of class.
F 5 Mid Term Break (no class)  
M 8 Requirements Determination Review including DFDs & ERDs Wilco Constrution Company Case Review due (for class review)

Baseline Project Plan (and current Project Schedule) due @ 125PM
Client receipt of BPP due @ 5PM
W 10 Client BPP Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session during class time
Held with client (not instructor) at site determined by client
Client evaluation of presentation due 10/12 @ 5PM
F 12 Client BPP Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session
during class time
Held with client (not instructor) at site determined by client
Client evaluation of presentation due 10/12
@ 5PM
Status Report 2 due @ 5PM or one business day prior to Status Meeting (whichever comes later)

Client BPP Presentations Complete NLT 5PM
Client Requested Changes for BPP due @5PM to team and faculty members
M 15 Instructor-Team-Client Status Meetings 2 / Independent Team Session.
Salisbury meetings in 113 AC.

150-215 Team 1

Mr. Hall and Mr. Nanda's teams (Teams 4-10) will meet on their schedules.

Status report previously delivered at least one business day before.
Clients attend in person or via phone

W 17 Instructor-Team-Client Status Meetings 2 / Independent Team Session.
Salisbury Team 2 - 130-200 in Salisbury's office (104 Anderson).
Status report previously delivered at least one business day before.
Clients attend in person or via phone
F 19 Instructor-Team-Client Status Meetings 2 / Independent Team Session.
Salisbury meetings in 113 AC.

125-150 Team 3 site TBD (likely Salisbury's office - 104 Anderson).
 
M 22 Independent Team Session  
W 24 Independent Team Session

 

F 26 Independent Team Session  
M 29 Deliverable 2 Presentation
125-145 Team 4
145-205 Team 5
205-225 Team 6
225-245 Team 7
245-305 Team 8
Notification to Client of Team Evaluation #1
Presentation Slides Hard Copy due in class

All teams must attend session
Deliverable 2 draft (optional) and Project Schedule (not optional) due @ 3; electronic copies only.
W 31 Deliverable 2 Presentation
125-145 Team 9
145-205 Team 10
205-225 Team 1
225-245 Team 2
245-305 Team 3
Presentation Slides Hard Copy due in class
All teams must attend session
November F 2 Independent Team Session  
M

5

Client Deliverable 2  Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session
during class time
Presentation Review due @ 5PM for teams 4,5,6,7,8. 
W 7

Client Deliverable 2  Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session
during class time

Updated/corrected BPP and schedule due for PMI review by 5PM.
Presentation Review due @ 5PM for teams 9,10,1,2,3. 
F 9 Client Deliverable 2  Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session
during class time

 

M 12 BPP & Scheduling Reviews w/PMI
(113 AC and 102 MH)
(125, 155, 225)
Teams 1, 2, 3, 4, 5


Independent Team Session for all other teams.

Guests PMI
Deliverable 2 DUE @ 12PM; electronic copies only (all teams)

Client notice of receipt of Deliverable 2 due @ 5PM (all teams)

W 14 BPP & Scheduling Reviews w/PMI
(113 AC and 102 MH)
(125, 155, 225)

Teams 6, 7, 8, 9, 10
Independent Team Session for all other teams.
Guests PMI
Client Team Evaluation #1 due by 5PM (all teams)
Status Report 3 due @ 5PM or one day prior to status report (all teams).
F 16 Instructor-Team-Client Status Meetings 3 / Independent Team Session.
Salisbury meetings in 113 AC. 

125 Team 2

145 Team 1
205
Team 3


Mr. Hall and Mr. Nanda's teams (Teams 4-10) will meet on their schedules.
Review peer evaluations & interim client evaluation of team
Clients attend in person or via phone
Client request change for Deliverable 2 due @5PM to students & faculty

Status Report 3 due @ 5PM or one day prior to status report (all teams).
M 19 Instructor-Team-Client Status Meetings 3 / Independent Team Session. Review peer evaluations & interim client evaluation of team
Clients attend in person or via phone
BPP and Schedule Review Notes due @5PM
Status Report 3 due @ 5PM or one day prior to status report (all teams).
W 21 Thanksgiving (no class)  
F 23 Thanksgiving (no class)  
M 26

Deliverable 3 Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session in class

Held with client (not instructor) at site determined by client
Client evaluation of presentation due 12/5 @4PM
W 28 Deliverable 3 Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session in class
Held with client (not instructor) at site determined by client
Client evaluation of presentation due 12/5 @4PM
F 30 Deliverable 3 Presentation (not necessarily during class time; by mutual arrangement with client)
Independent Team Session in class
Client deliverable 3 presentation done NLT 5PM
December
M 3 Independent Team Session  
W 5 Independent Team Session Client evaluation of presentation due @4PM
Deliverable 3 Report Due to Client by 2PM
Client notice of receipt of Deliverable 3 Report due NLT 5PM

Notice to Client of Team Evaluation #2
F 7 Feast of Immaculate Conception/Christmas on Campus (no class)  
R 13 Course Feedback, Implementation Preview, MIS 475 Introduction (NOTE - A THURSDAY) Class meets from 1220-210 PM (finals period for 125-215 classes.)
Deliverable 3, updated Deliverable 2, BPP, Project Schedule Schedule and Group Peer/Personal Evaluations (can be done on the same form) due by 1220 PM.
Client Team Evaluation #2 due @ 5PM
F 14 Client Request Changes for Deliverable 3 due @ 5PM to team & faculty