CIS 340 Systems Implementation

1
CIS 340 Systems Implementation

• Assessment - Spring 2005

2
Content for Assessment

• Area Percent of Grade
• Chapter Reviews 05
• Zachman Work 05
• Mid-Term Test 15
• Panel I, II 10 (5 each)
• Exam 15
• Group Project 50

3
Class on Subject Areas

• Subject Area Class
• Chapter Reviews 91.67
• Mid-Term Test 77.10
• Panel I,II Zachman 96.61
• Exam 85.72
• Group Project 84.09
• Overall Performance 84.89
• I did not have as many good students as I usually
  do and some of the grades were very low, bringing
  the overall class average down to mid 80s.

4
Specifics on Mid-Term

• MC/TF 77.64
• Essays on Chapter Questions 88.62
• Zachman Framework 63.42
• I am not surprised by the results on the Zachman
  Framework questions. I did provide study guides
  and took questions from them, but I dont think
  they spent much time studying. But again, the
  caliber of student was lower than usual.

5
Specifics on Exam

• MC/TF/Fill ins 80.33
• Essays 91.11
• (Each Chapter plus Panel Discussions topic 2
  5 essays)

6
Specifics on Projects

• Milestones-timeliness (100) 87.08
• Programming Grade (200) 80.83
• Users Guide (200) 83.75
• Appointments/Effort (50) 88.17
• Presentation Evaluation (100) 86.25
• Project grade (650) 84.09

7
Milestone Evaluations (1)

• M1 Project Proposal
• All student groups turned in the proposal in a
  timely manner.
• M2 Systems Profile
• Interview material
• Some groups were delayed in getting this done due
  to real world time demands and others, just
  didnt do what they were supposed to do.
• UML material
• Charter Template, Actors, Event Table
• 2 of 5 groups had done in reasonable time, 3
  group procrastinated
• M3 Data Work Task List
• Data in 3rd Normal Form
• Much redo needed on this area - still having
  trouble seeing the relationships and how they
  overlap the group that had done the database
  class did the best work - understandable
• Entity Relationship Diagram
• Each group redid several times after consultation
  with instructor
• Processes to accomplish for project
• There is still a need to limit work. They start
  out ambitious they soon learn to restrict the
  scope of the project.

8
Milestones Continued (2)

• M4 Data Dictionary as defined in Visible Analyst
  (VA) Software
• Must correspond to rest of project work in VA.
  They often need to redo ERD
• M5 Data Flow Diagrams Use Case Diagram
• Context Level DFD, Level 0, 2 child diagrams
• Some difficulty with balancing and keeping names
  consistent. Often do three versions before they
  get it right.
• M6 Sequence Diagram in VA Use Case Templates
  for each Task listed in M3
• SDs are new and they need to practice. Concept
  is good and should be kept in course. UCTs are
  needed for each process not just a list of Happy
  Paths, Alternate Paths, Exception Paths. This
  forces students to think about preconditions and
  postconditions.

9
Milestones Continued (3)

• M7 The Design and Listing for the Database
• Should be completed by midterm. Students are
  slow in getting to this. Some are still working
  on it near the end of the semester.
• M8 Layout of Main Menu for Program
• They are reasonably good at this design. This
  process serves to emphasize the need for one
  entry point into the program.
• M9 Layout for Data Entry Screens
• Each table must have an input screen. They need
  to understand when two tables on one screen is
  appropriate.
• M10 Layout of Reports
• Need at least two standard reports and one group
  report. Make them report on what they claimed
  they were going to do. There is inconsistency
  here in doing what they said they would. The
  reports were not good this year. Very little
  labeling, groups not clearly defined, no use of
  concatenation.

10
Milestones Continued (4)

• M11 Security Specifications and Business Rules
  or Standards
• There is a lack of understanding about Business
  rules. They are doing ok on security (password)
  protection. We cover security in class, and only
  do business rules in passing. Emphasize more.
• M12 Working Program in Appropriate Software
• They start this too late to do a good job and end
  up having a system that doesnt work. Emphasize
  timing!
• M13 Users Guide and Manual
• Mostly very good work. I bring in other examples
  of student work from past semesters and they find
  this helpful.

11
Group Work

• In one of the projects the student worked alone
  as a result of his partner quitting school. His
  project was not very well done.
• Lighthouse Tavern
• One project had two student members.
• Campus Recreational Fitness
• Three projects had 3 members each.
• Elon Roller Hockey Club Sport
• Executives Cutting Edge
• Computer Services

12
Analysis of Groups

• In single worker projects there is no one else to
  motivate them. The student working alone did not
  do so by choice and he just didnt do what he
  should have. I am not sure he ever worked
  outside of class.
• The group of 2 were frequently behind on handing
  in the milestones. One person absent from the
  group meant the other had no one to confer with
  and work didnt get done. Again, not motivated.
• Two of the groups with 3 students were the most
  productive. It was rare that anyone in the group
  was absent. They worked well and the team work
  ethic showed.

13
Analysis of Groups Continued

• Reviewing Group Work
• This semester we once again held all meetings in
  the classroom rather than in my office. Students
  were required to come to class everyday and use
  the time to work on projects with my supervision.
  This was not entirely successful since many times
  group members were absent from 3 of the groups.
  Those 3 groups did not produce good projects.
• Im going to do this next year (S06) also and
  then make a decision as to whether or not we need
  to move these meetings back to my office. That
  office meeting tended to force them to be
  prepared. They are less prepared if they do not
  feel that pressure.

14
Student Evaluation of Class

• To a person, they liked the structure of the
  class. They like the organization and direction
  of the milestones, the working in class with me
  there, and the not having to meet me in my
  office. Some acknowledged that they should have
  worked harder and gotten things done earlier. I
  was not pleased with the results of 3 of the 5
  groups. Two sets of A and three sets of D is not
  a good semester. I think results depend upon the
  quality of students and this semester was not
  outstanding.