University of Arkansas at Monticello
School of Computer Information Systems
CIS 4634 –Application Software
Development Project – 4 hours credit
Course Syllabus – Spring 2012 – MWF 8:00
Instructor:
Angela Marsh
Office:
BBC Room 118
Phone:
Direct – 870.460.1341
CIS Office – 870.460.1031
Email:
marsh@uamont.edu
Office Hours:
10:00 a.m. – 12:00 p.m. MW
9:30 a.m. – 11:00 a.m. TT
12:30 p.m. – 1:30 p.m. TT
Other hours by appointment
Web Site:
http://www.uamont.edu/FacultyWeb/Marsh/
Course Title & Credit Hours:
CIS4634 Application Software
Development Project – 4 hours credit
Project Log:
CIS4634 Application
Software Development Project Log
Course
Description:
System
simulation techniques; their application to business systems using an
appropriate simulation language; systems design and development; extensive use
of computers.
Course
Prerequisite:
CIS 3523 Systems Analysis and
Design and CIS 4623 Database Management Systems
Course Text:
None
Supplemental
Materials:
Each student should have at least
two memory sticks to process, store, and backup data. Students will also need a
three-ring binder and section dividers for documentation manuals.
Student
Learning Outcomes:
The student who successfully
completes this course will analyze, design, code, test, document, and present
an information system, obtain experiences which better enable the student to
enter the job force with confidence, and demonstrate higher-level communication
skills.
Attendance:
Students are expected to meet weekly
with the instructor for system updates. Students are expected to be in class on
Wednesday for work on communication assignments.
Course
Content:
System Analysis and Design -
An investigation identifying the nature and scope of the system. Used to determine and document not only what
input, processing, output, and testing is needed but also how best to construct
the system to satisfy those needs. A manual will be created and a presentation
given at the end of this phase.
Programming -
The point where the system is actually constructed. Programs are written,
internally documented, and tested. Databases are created and web pages are
published. A working system will be produced in this phase.
Programming Review Memo – A
correctly formatted memo submitted to the instructor comparing the programming
in your system to the programming requirements detailed in the syllabus. Extra
features you added to the basic requirements should be included.
Knowledge Contributions –
Relevant knowledge shared with the class which can be viewed via the Book of Knowledge links from the
instructor’s web site. For credit, all contributions must be received by the
final day of the programming phase.
Documentation Manuals –
Both a system manual and a user manual are created. The two manuals should be
submitted in one physical manual. Your working system on a storage device
should also be included with this documentation.
System Presentation
- An oral presentation of your system is given. A hard copy of the presentation
will also be provided.
Status Reporting
– Weekly reporting of your system that includes a status report and Gantt
chart.
Communication Assignments –
Assignments designed to enhance the student’s understanding of their strengths
and weaknesses and to advance their professional communication skills.
Course
Calendar and Guidelines for System Deliverables
I.
Systems Analysis and Design
A.
Contents
1.
System Requirements and Narrative
List
of requirements needed by your system translated into a system narrative
written in layman’s terms (no CIS terms) describing the features of your system
2.
System Design
Context Diagrams, Data Flow Diagrams,
System Flowcharts, Use Cases Diagrams and Scenarios, Technical Specifications,
and/or other appropriate diagrams and documents
3.
Input Design
Source Documents, Screen
Designs, Web Page Design
4.
Output Design
Report
Layouts, Screen Designs, Web Page Design
5.
Database Design
File/Table Layouts, Data
Dictionary, Relationships
6.
Testing Procedure
Test Plans, Testing
Conditions and Error Messages for each form/screen
B.
Evaluation Criteria
1.
Clarity
2.
Contents
3.
Organization
4.
Presentation
C.
Deliverables with Due Dates
1.
Week 1
System
Requirements and Narrative & SAD Manual with sections
2.
Week 2
System
Design & Updated SAD Manual
3.
Week 3
Input
and Database Design & Updated SAD Manual
4.
Week 4
Output,
Web Page, and Database Modification & Updated SAD Manual
5.
Week 5
Test
Plan, Error Messages, & Updated SAD Manual
6.
Week 6
System
Analysis and Design Manual
Project
Presentation with hard copy
II.
Programming
A.
Contents - Minimum
1.
Two files/databases/tables (you should be able to create, read,
update, and delete [CRUD] all data fields and/or records)
2.
Extensive use of one programming language (programmer-generated internal program documentation is expected)
3.
A password system
4.
A GUI allowing user-friendly navigation and appropriate access of
your system
5.
One detail report, one summary report, and one exception report
6.
One web page showing basic information about your system published
to the Internet. The web page should
contain at least your system name and logo, a hypertext link, a graphic, and
text.
B.
Evaluation Criteria
1.
System Design
2.
User Friendliness
3.
System Performance
4.
Internal Program Documentation
5.
Extras
Special
Note – If your system correctly
performs the minimum contents listed above, the equivalent of 80% (B) or 24/30
points will be awarded. To earn more
points, additional technical features will be required. To verify an extra is sufficient to earn a
point, check with your instructor. You
are expected to specify your system extras in the Programming Review memo in
order to receive additional points.
C.
Deliverables with Due Dates
1.
Week 7
Menu
and password system working
2.
Week 8
CRUD
programming
3.
Week 9
CRUD
working
4.
Week 10
Reports
working
5.
Week
11
Web
page working
6.
Week 12
Testing
& Preliminary Presentation
7.
Week 13
One-on-one
system presentation to instructor & Programming Review Memo
III.
Documentation Manuals
A.
Contents
1.
System Manual - Written with the computer programmer in mind and
containing minimally the following information:
a.
Table of Contents
b.
System Narrative
c.
Technical Specifications including Operating Systems, Computer
Applications, and Programming Languages
d.
Test Plan
e.
System Design Section showing System Flowcharts, Data Flow
Diagrams, Decomposition Diagrams, Use Cases, and other appropriate diagrams and
documents
f.
Data Dictionary Section listing files, databases, tables,
relationships, data names, field descriptions, field characteristics, etc.
g.
Program Section
(1)
Program narrative
(2)
Sample program output
(3)
Program hard copy
h.
Copy of system on appropriate media
2.
User Manual - Written with the end user of your system in
mind. Your approach should be
user-friendly and detailed. This manual
should minimally contain the following information:
a.
Table of Contents
b.
System Narrative
c.
Screen Section
(1)
Screen narrative
(2)
Sample screen
(3)
Screen field identifications and definitions
(4)
Error messages and corrections
d.
Report Section
(1)
Report narrative
(2)
Sample report
(3)
Report printing procedure
e.
Web Section
(1)
Web narrative
(2)
Sample web page
f.
Balancing Procedures (if applicable)
B.
Evaluation Criteria
1.
Contents
2.
User Friendliness
3.
Organization
4.
Presentation
C.
Deliverables with Due Dates
1.
Week 14
System
Manual and User Manual - rough draft
2.
Week 15 (by last day of classes)
System
Manual and User Manual – Both manuals physically reside in one notebook along
with your system on a storage device
IV.
System Presentation
A.
Contents
1.
Oral presentation of your system
a.
System name, logo
b.
System narrative (bullets)
c.
Two (2) screen shots which illustrate your design
d.
Two (2) things in your system of which you are proudest
e.
Two (2) things that you learned about yourself
2.
Hard copy of presentation
B.
Evaluation Criteria
1.
Contents
2.
Organization
3.
Clarity
4.
Grammar
5.
Presentation
C.
Deliverables with Due Dates
1.
Wednesday, May 2 – 3:15 – 5:15 -
Finals Week
a.
Formal system presentation
b.
Presentation hard copy
V.
Status Reporting
A.
Contents
1.
Status Report - must minimally contain the following information:
system name and/or logo, student name, week number, date submitted,
accomplishments this week, plans for next week, things that went well, problems
encountered, and what you learned.
2.
Gantt Chart – updated weekly and printed on one page
B.
Evaluation Criteria
1.
Design
2.
Contents
3.
Clarity
4.
Grammar
5.
Presentation
C.
Deliverable with Due Dates
1.
Due Weekly
a.
Starting Week 1
b.
Ending Week 12
Course
Calendar for Communication Deliverables
1.
Week 1
Know
Yourself - Myers Briggs and another test
2.
Week 2
Work
Situation Summary
3.
Week 3
Resume
& Reference Sheet v.1
4.
Week 4
Resume
& Reference Sheet v.2
5.
Week 5
Cover
Letters – Ad and Blind v.1
6.
Week 7
Cover
Letters – Ad and Blind v.2
7.
Week 8
Interview
Answers
8.
Week 9
Interview
Answers continued
9.
Week 11
Interview
- Phone
10.
Week 12
Interview
- Person
11.
Week 15
Thank
You Note
Grading
Policy:
1. The grade will be awarded based on the extent
to which the student is able to accomplish deliverables and produce a quality
product. All deliverables must be completed to successfully complete this
course. The following table explains the
scoring.
|
Deliverable |
Points |
|
Systems
Analysis & Design Manual |
12 |
|
Systems
Analysis & Design Presentation |
5 |
|
Working
System |
30 |
|
Programming
Review Memo |
2 |
|
Knowledge
Contributions |
4 |
|
Documentation
Manuals |
20 |
|
System
Presentation |
5 |
|
Weekly
Status Updates & Deliverables |
22 |
|
Know Yourself - Myers Briggs / In The Work Place |
5 |
|
Work Place Summary |
5 |
|
Resume & Reference Sheet v.1 |
5 |
|
Resume & Reference Sheet v.2 |
5 |
|
Cover Letters - Ad & Blind v.1 |
5 |
|
Cover Letters - Ad & Blind v.2 |
5 |
|
Interview Answers |
5 |
|
Interview Answers Continued |
5 |
|
Interview - Phone |
5 |
|
Interview - Person |
5 |
|
Thank You Note |
5 |
|
Total |
155 |
Your total earned points are accumulated, converted
to a percentage, and applied to the following scale to produce your final
grade.
A = 90%
- 100%
B = 80%
- 89%
C = 70%
- 79%
D = 60%
- 69%
F
= 0% - 59%
2. Late work is defined as work presented to
the instructor after the end of the week of the assignment’s due date and will
carry a 10% penalty.
3. To receive the two points for Weekly Status
Updates & Deliverables each week, you must provide the instructor with a
status report and Gantt chart, and show evidence that progress is being made on
the weekly deliverable. To receive the weekly points, all data is required by
noon on Friday.
4. Academic
dishonesty is not tolerated. Do you own work.
Cheating, collusion, duplicity, or plagiarism will result in a grade of zero
for all involved.
5. A student must be
current with course work assignments and/or examinations and must have
completed at least 75% of all required course work assignments and/or
examinations to be considered for a grade of Incomplete (I).
Special Dates
of Concern:
January 16.......................... Martin
Luther King Holiday
February 24........................ Deadline
to file for graduation
March 19 - 23..................... Spring
Break
April 4................................ Last
day to drop with a “W”
May 1................................ Last
day of classes
May 2 - 8............................ Final
exams
Students with
Disabilities:
It
is the policy of the University of Arkansas at Monticello to accommodate
individuals with disabilities pursuant to federal law and the University’s
commitment to equal educational opportunities. It is the responsibility of the
student to inform the instructor of any necessary accommodations at the
beginning of the course. Any student
requiring accommodations should contact the Office of Special Student Services
located in Harris Hall Room 121; phone 870 460-1026; TDD 870 460-1626; Fax 870
460-1926.
For
assistance on a College of Technology campus contact:
McGehee:
Office of Special Student Services representative on campus; phone 870
222-5360; fax 870 222-1105.
Crossett: Office of Special Student Services
representative on campus; phone 870 364-6414; fax 870 364-5707.
Student Conduct Statement:
Students at
the University of Arkansas at Monticello are expected to conduct themselves
appropriately, keeping in mind that they are subject to the laws of the
community and standards of society. The
student must not conduct him/herself in a manner that disrupts the academic
community or breaches the freedom of other students to progress academically.
Academic Dishonesty:
For any instance of academic
dishonesty that is discovered by the instructor, whether the dishonesty is
found to be cheating, collusion, duplicity, or plagiarism, the result for the
student(s) involved will be a zero for all concerned.