M&IS 44044 - Systems Analysis II

Department of Management and Information Systems


Spring 2003


Name of Course: 

Systems Analysis II - M&IS 44044 - Section 001


Spring 2003 


110 BSA

Meeting Time:

5:30 - 6:45 TuTh 

Course Web Site:



M&IS 24060, 24070 (students without these prerequisites risk being deregistered from this class)

Catalog Description:

Physical system implementation: mapping logical data models and process models to physical data bases and system design; system coding, testing, installation, conversion, training and automated tools


Name of Instructor:

Dr. Alan Brandyberry

Office Address:

BSA A425 



Office Hours:

3:00-5:00 PM Tu Th (and by appointment)



Instructor Web Site:

Main Site: http://babbage.bsa.kent.edu/


Required Materials: 

Beginning ASP.NET with Visual Basic.Net (Kauffman, Miller, et al, Wrox Press, 2002, ISBN 1861007337) Amazon.com Link


Detailed Prerequisites: 

The prerequisite courses required to enroll in this course are M&IS 24060 & 24070.  Students are expected to have the following knowledge and skills developed before enrolling in this course.  If this set of knowledge and skills is not present prior to enrolling in this course it greatly reduces your probability of success.

  • General Knowledge of the Systems Development Life Cycle (SDLC).
  • Database Design
    • Entity Relationship Diagramming (ERD)
    • Normalization
    • Cardinality
  • Process Design
    • Dataflow Diagramming (DFD)
    • Flowcharts
  • Programming
    • Visual Basic Concepts
    • Event-Based Programming
    • Object-Based or Object-Oriented Programming

Course Objectives: 

  1. Give students experience in current languages and information technologies for microcomputer-based applications.
  2. Provide an opportunity for students to learn and apply new languages quickly and effectively.
  3. Provide an opportunity to participate in a team-based environment developing "real-world" applications.
  4. Reinforce concepts of systems analysis and design, and relational database design.
  5. Reinforce concepts of interface design, data access, storage, and maintenance.
  6. Introduce/reinforce project management concepts.



Description of  

Teams will develop business-oriented applications.  Applications will be problem-specific and client-server applications supporting enterprise computing will be given preference.  Applications must contain a component to read/write from a separate database.




Students will use ASP.NET to develop an interactive web-based application. In special circumstances I will consider proposals that use a different current development environment.  For practical considerations, tools and technologies supported by the university (i.e. is available in the campus labs) will likely be chosen.  Tools and technologies used that are not supported by the university must be provided by the student.




After the initial review of the systems development life cycle in the beginning weeks we will meet in the classroom once per week.  The other scheduled class meetings will be conducted in project groups.  ALL groups will meet during the class time.  Some of these groups will meet with me for part of this time each week.  This is class time and attendance is required whether your group meets with me that week or not.  The schedule of meetings with me depends on the final number of groups in the course.  My goal will be to have a scheduled meeting with me every other week (groups will meet only with their group members on other weeks).  Additional meetings with me during office hours or by appointment and consultation with me via email is strongly encouraged.  Additional meetings with your own group whether in person or via electronic means is also strongly encouraged.



At the beginning of each Thursday classroom meeting (excluding 01/16) there will be a short quiz on the material presented during the classroom meetings since the previous quiz.    You may not take the quiz and leave the class - your quiz will not be graded.  Excused absences will be dealt with on an individual basis.

GRADES: Grades will be based on the following:



Quality of Activity Log Entries (timeliness, completeness and content)


Quality of Analysis & Design of Application


Quality of Implementation of Application


Peer Evaluation of Individual Performance


Instructor's Evaluation of Individual Performance


Final Presentation


 The following scale indicates the minimum course percentage required for each letter grade:

Letter-grade determinations will be made on the following percentage basis:  A>90%; B>80%; C>70%; D>60%; F<60%.  A lower curve may be substituted at the discretion of the instructor. Grade curving is only done at the end of the term for final grades.  Do not try to anticipate the curve - target the score that will get you the desired grade on the straight scale above.  **Students are welcome at any time to inquire into their current grade status during office hours.

1. Quizzes: Each quiz counts the same amount and this grade will be based on the student's mean quiz score.  The lowest quiz score for a quiz that the student took will be dropped.  Quizzes missed due to unexcused absences will not be dropped. 

2. Quality of Activity Log Entries:  Each student will fill out an online activity log documenting meetings attended and project activities performed. Each student will also need to review their group members previous week's entry.  If you complete this task each week in a timely fashion and descriptions of activities are lucid and complete you should receive full credit for this portion.  If not, deductions will be taken by a subjective assessment by the instructor as to how serious the deficiencies are.  The type and number of activities performed is not a portion of this score (see peer and instructor evaluation). 

3. Quality of Analysis & Design of Application: All students on a team will be assigned the same score for this portion of the grade. Basic requirements and deliverables are:

4. Quality of Implementation of Application: All students on a team will be assigned the same score for this portion of the grade. Basic requirements and deliverables are:

5. Peer Evaluation of Individual Performance: You are free to organize and run your groups in any way you like subject to specific guidance below.  Evaluations will be absolutely confidential.  Evaluations will be made on these factors:

  1. Quality of work performed by the student.
  2. Level of effort.
  3. Participation in group meetings.

Evaluations will be done on a rating scale, ranging from 1 to 15, where one is pathetic and worthless, and 15 is perfect and invaluable. A score of 8 is considered minimally satisfactory.  It would be possible for a student to do superb work on a small part of the project (a 15 for quality but a 1 on effort) and receive a low overall grade due to effort level. As an additional measure students will rank their peers in each area from most valuable to least valuable.  I understand that you may feel all members were valuable so the "least valuable" may not be considered a poor outcome.  This is why both the rating and ranking are being done.  Students often resist this component.  The reason this is necessary is the only people that can evaluate a person's performance on a project such as this, with complete information, are the person's peers on that project.  In addition, it is common industry practice to use peer reviews, especially in project-oriented environments.  Most of you will have to, at some point, evaluate peers and/or subordinates in a business environment.  These evaluations may affect the person's career and livelihood.  Failure to be completely objective on these types of evaluations will likely eventually affect your career/livelihood.  This is good practice.

Evaluations in the third area will be based on the same scale, but reflect attendance at group meetings. A score of one means the person never attended a single meeting. A score of 15 means the person attended every meeting.

There are two rules in effect with respect to peer evaluations.

  1. No one should turn in a low evaluation (below 8) of another group member unless I have been notified that this person is not pulling his or her weight. This notification should occur as soon as the problem becomes apparent. This requirement corresponds to the requirement most organizations have that an individual must be counseled if their performance could lead to dismissal.
  2. Each member of the group must be allowed to play a significant part in the development and implementation of the project. If an individual feels that he/she is being shut out by the group, the individual must notify me early (the earlier, the better). This requirement does not mean that each group member must be involved in every aspect of the project, but it is meant to prevent one or two individuals from monopolizing the project and then giving poor evaluations later.

I will take care of any counseling necessary in response to problems of the types mentioned above.

6. Instructor's Evaluation of Individual Performance: Each student will receive two performance evaluation scores. The first performance evaluation will occur at midterm. The second evaluation will occur at the end of the semester. Both evaluation scores will be equally weighted.

7. Final Presentations: Each group will present their completed project to the class.  Well-designed, informative presentations should receive full credit.  Deductions are based on subjective assessment by instructor.



Class Meetings



Jan 14, 16

Course Introduction, Review of Systems Development Life Cycle (SDLC)

Bring Group Member Choices on Jan. 16 or email choices by 5PM Jan. 17.


Jan 21, 23

Groups Assigned - Individuals submit description of an appropriate application (see details). 
Groups meet in class and select an application from choices provided by instructor and team member's application descriptions. 
Weekly group meetings with instructor are scheduled.

Review of SDLC, DFD, ERD


Jan 30

Group meetings during class time (Tues.) begin on Jan. 28, Review of SDLC, DFD, ERD continues.


Feb 06

Systems Investigation Report Due

Brief description and tour of provided development environment - IIS (Microsoft) and Apache (Linux - available for other OS's) web servers, server side scripting, client side scripting, servlets/applets, stand-alone apps, Oracle DBMS.


Feb 13

SQL Review


Feb 20

Systems Analysis Reports Due

SQL Review, Oracle Development


Feb 27

HTML Overview / Introduction to ASP.NET


Mar 06

Systems Design Report Due

ASP.NET – How scripting (server & client-side) is adds to functionality.

The concept of maintaining state – why HTML by itself is “state-less”


Mar 13

Fundamentals of programming revisited - reminders, tips and tricks.

ASP.NET - basics, why string manipulation is the key to much of server-side scripting.



Mar 20

User Interface Design

Best Practices ASP.NET - data input, verification, database interaction.


Mar 27

Spring Break - No Class


Apr 03

ASP.NET continues


Apr 10

ASP.NET continues


Apr 17

ASP.NET continues


Apr 24

True Object Orientation: Best Practices


May 01

Implementation and Maintenance/Review Reports Due

Final Project Due



May 06, 5:45 - 8:00 p.m. Tues.

Final Presentations


The Following Policies Apply to All Students in this Course


A.     Students attending the course who do not have the proper prerequisite risk being deregistered from the class.


B.    Students have responsibility to ensure they are properly enrolled in classes.  You are advised to review your official class schedule during the first two weeks of the semester to ensure you are properly enrolled in this class and section.  Should you find an error in your class schedule, you have until January 24, 2003 to correct it with your advising office.  If registration errors are not corrected by this date and you continue to attend and participate in classes for which you are not officially enrolled, you are advised now that you will not receive a grade at the conclusion of the semester for any class in which you are not properly registered.


C.    Academic Honesty:  Cheating means to misrepresent the source, nature, or other conditions of your academic work (e.g., tests, papers, projects, assignments) so as to get undeserved credit.  The use of the intellectual property of others without giving them appropriate credit is a serious academic offense.  It is the University's policy that cheating or plagiarism result in receiving a failing grade for the work or course.  Repeat offenses result in dismissal from the University.


D.    For Spring 2003 the course withdrawal deadline is Saturday, March 22, 2003.  Withdrawal before the deadline results in a "W" on the official transcript; after the deadline a grade must be calculated and reported.


E.    Students with disabilities:  In accordance with University policy, if you have a documented disability and require accommodations to obtain equal access in this course, please contact the instructor at the beginning of the semester or when given an assignment for which an accommodation is required.  Students with disabilities must verify their eligibility through the Office of Student Disability Services (SDS) in the Michael Schwartz Service Center (672-3391).