MIST 4620 System Analysis and Design by dcc48652


									                                 MIST 4620: System Analysis and Design

                                                        Summer 2003
                                                    01:00p-2:00p MTWRF
                                                     Room: Sanford 112


        Saurabh Gupta
        Management Information Systems Department
        Terry College of Business
        The University of Georgia
        Athens, GA 30602-6273

        Office: Brooks 111
        Email: Gupta@terry.uga.edu (include ‘MIST 4620” in the subject line)
        Phone: (706) 542-3746 (department)
        Fax: (706) 583-0037
        Office Hours: Monday from 10:30 am to 11:30 pm; Thursday from 10:30 am to 11:30pm; and by appointment. (My
        calendar is online and can be viewed at http://calendar.yahoo.com/gsaurabh )
        Home page: http://www.arches.uga.edu/~gupta
        Instant messaging: Please use my website to send me an instant message.

Teaching Philosophy

    To learn is to gain knowledge or understanding and skill in a subject area via study, instruction or experience. In this class,
    we will use classroom instruction, project experiences and peer experiences to have a better understanding of the systems
    and their development. An understanding comes from integrating the concepts of the course for use in everyday life. With
    the ever-changing field of information systems, we will use both exploration as well as education as a media to gain more
    insight. The following metaphor best describes my teaching philosophy: give a person a fish and you have fed them for a
    day; give them a fishing pole and you have fed them for life. To enhance the educational experience, we will use
    technology to assist learning.

Catalog Description

    Structured systems analysis and design with emphasis on the development of business application systems. Methods of
    systems documentation are examined through the use of tools and techniques for describing process flows, data flows, data
    structures, system objects, file designs, input and output designs, and program specifications.

Course Description

    This course should be viewed as the cornerstone upon which all subsequent MIS activities are based. Skills you learn in
    this class will be applied again and again throughout your college and IS careers. Consequently, you should expect to work
    hard in this course to develop these skills. It is expected that students will spend at least 7-10 hours per week reading and
    working on assignments and projects (less time early in the semester, more time as the semester progresses). This course
    introduces the concepts and methods of information systems analysis and design, with an emphasis on systems analysis
    methods and tools. A major focus of the course is a group project.

        A systems analyst shall be responsible for studying the problems and needs set forth by an organization and for
        determining how people, methods, and computer technology can best accomplish improvements. When computer
        technology is used, the analyst shall be responsible for the efficient capture of data from its business source, the flow
        of that data to the computer, the processing and storage of that data by the computer, and the flow of useful and
        timely information back to business users.

    The course focuses on the issues and management techniques involved in the analysis, design, and implementation of
    information systems. Most businesses expect their systems analysts to be knowledgeable in three general areas:

        •    Interpersonal skills: The systems analyst should be effective in both verbal and written communications, should
             be able to facilitate meetings, and should be a competent change agent.
        •    Information Systems: The systems analyst should be familiar with the general IS concepts such as the Systems
             Development Life Cycle, CASE tools, prototyping, process and data modeling tools and techniques, rapid and
             joint application development, and programming.
        •    Functional Business Areas: The systems analyst should be familiar with the accounting, marketing, and customer
             service areas.

    This course will focus on helping you develop interpersonal skills and conduct IS system analysis and design. Upon
    completion of this course, you should be able to effectively:
        • understand the concepts and principles of the systems development life cycle (SDLC), including systems
            planning, project management, and computer-aided systems engineering (CASE) tools.
        • use the tools and techniques of the structured systems analysis methodology to model systems requirements,
            including an addition to structured analysis called essential systems analysis.
        • design and prototype forms, reports, screens, and user-computer dialogs which convey the look and feel of a new
            systems to end-users.
        • be familiar with trends affecting the analysis and design of information systems, including alternative
            methodologies such as object oriented analysis and design.
        • understand object oriented analysis concepts in terms of utilization, design, and implementation.

    Specifically, upon completion of this course, you should be able to effectively:
        • define the systems analyst’s role and responsibilities in a typical organization.
        • define systems planning, systems analysis, systems design, systems implementation, and systems support.
        • describe a phased approach to information systems development and describe cross-life activities that overlap the
             entire life cycle.
        • compare and contrast the systems development life cycle and system development techniques, including
             structured programming, modern structured analysis, structured design, information engineering, and prototyping.
        • define and perform data modeling and process modeling, and explain why they are important.


    These prerequisites are designed and required to ensure your success. Past results indicate that if you don't have them, you
    will not do well in this course. YOU MUST DROP this course if you don't have the prerequisites:

    •   MIST 2090: Introduction to Information Systems in Business (or equivalent)
    •   MIST 4600: Intro to VB (or another programming class)
    •   MIST 4610: Database Management (or equivalent) – You can take this class in parallel.

    These prerequisite topics, and others, will be assumed by the Instructor, since you are registered in this course.
    Since we will be working with the Microsoft Access database, having a basic working knowledge about this software is
    essential. A basic working knowledge familiarity with the menus and ability to create tables.

Textbook and Technology

        1.   Dennis, A., and Wixom, B.H. Systems analysis design, (2nd ed.) J. Wiley, New York, 2003, pp. xx, 537
        2.   Blackboard http://terry.blackboard.com/
        3.   Other software’s will be used in the class and will be discussed at that time. (Refer Blackboard)

General Course Philosophies & Policies

•   Active class participation is expected.
•   Announcements will be made via Blackboard.

•   A "W" grade will be assigned if a student withdraws before Jul 9 while maintaining a passing grade. Withdrawals after
    this date will result in a grade of "WF".
•   Unless stated otherwise on the “Tentative Schedule of Classes” or through email, all classes will be held in our regular
•   Make-up examinations may only be given for valid (and documented) reasons, at the discretion of the instructor. An
    unexcused absence for an examination will lead to zero point earned on that examination.
•   I do not take attendance. As far as I am concerned, you are an adult and it is your decision whether or not you attend class.
    However, freedom comes with responsibility: if you are absent, you are responsible for obtaining the information you
    missed from your student colleagues.
•   Late assignments will lose 10 percent of the total points for each day (24 hour period from the time due) they are late, up
    to four days. After four days, late assignments will not be accepted.
•   Backup Policy: Floppy disks are not reliable storage media. Back your work up early and often. Certainly you should back
    up anything that is important and irreplaceable. Always keep a copy of all material turned in for grading. Good disks do go
    bad from time to time, and individual files on a disk can become corrupted. Make copies of your disks and files, and keep
    the copy in a place other than where the original is. Also, if you have a home PC, do back up your hard disk from time to
    time, or copy all working files to floppies, a zip disk, or a R/W CD-ROM. Please BE CAREFUL!
•   Computer Virus Policy: Computer viruses can also infect disks and make the files unusable. You may occasionally hear of
    a virus on the network. If you do, disinfect your disks. Software is available on the network to do so.
•   If you have any problem(s) that might impede your performance in this course, please bring it to the attention of the
    instructor immediately.

Grading Information

Here is the breakdown of how the points are to be distributed for the course grade
                                      Indvi     Team        Total Comments
    Mid-term Examination               20%         0%       20% Multiple choice: Refer to Schedule of Lectures for date.
    Final Examination                  25%         0%       25% Case study. Refer to Schedule of Lectures for date.
    Homework                            7%         0%         7% Will be given in class
    Element K assignments               3%         0%         3% Refer to the description below
    Major group project                 0%        35%       35% Refer to the description below
    Chapter presentation                0%         5%         5% Each group presents a chapter. (Chapter choice 7/9/11)
    Participation + Survey              5%         0%         5% Online and in Class
    Total                             60%        40%       100%

Grading Scale: Typically, grades in this class cover a wide spread. Letter grades will be assigned according to the weighted
average of points accumulated on quizzes, exams, assignments, projects, and those that are instructor determined. Grades will
be assigned based on your performance alone. You will NOT be competing with other class members for a fixed number of
A’s, B’s, C’s, etc. Grading is on a traditional scale with 89.5% and up being an A; 79.5% through 89.4% a B; 69.5% through
79.4% a C; 59.5% through 69.4% a D; and less than 59.5% is a F. At the instructor’s discretion, these boundaries may be
moved downward, but will under no circumstances be moved upward. NOTE:- You will need to have a passing grade (60%) in
the individual grade to be eligible for a passing grade in the class.

Grading Issues: I want all grading in the course to be fair, accurate, and objective. My policy on contesting grades and/or
scores received on any assignment, project, or exam, etc., is the following: All questions about grades that potentially involve a
change in points must be submitted, in writing, within 5 working days after the assignment is returned or grade is posted,
whichever comes first. The write-up must include details about the requested change, your name, and a copy of the returned
assignment or exam. You must also sign the request. Verbal and emailed requests or requests after 5 working days will not be
considered. Furthermore, I reserve the right to re-grade the entire exam/paper and not just the part requested. This may in some
cases result in a lower grade.

Grade Reporting: Grades will only be sent electronically to Blackboard only. I will not give grades out over the telephone
or verbally in class or in the office. Keeping your username and password secured is students’ responsibility.

Groups / Teams

•   We will have two team activates: Grand project and chapter presentation. Specific instructions will be provided to you
    when these assignments are actually made.
•   Each team must have 5 members. Each team will be required to define, elect or volunteer a team leader as the point of
    contact for the team. A different team leader for each of the assignments would be preferred. The team leader is
    responsible for project management activities.
•   An email including the name and contact information of each team member, team name and team leader must be sent to
    the instructor no later than June 11th, 2004. Please specify the e-mail address of each team member, as well as the phone
    number where the team leader can be reached.
•   Most of you will work effectively in teams, each contributing your best effort and proving to be a reliable, productive team
    member. However, because experience has proven that team projects always raise the possibility that some team members
    may not carry their fair share of the load, a confidential peer evaluation will be conducted at the end of the semester. This
    evaluation will impact your grade. You grade on the Team part of your grade will be directly factored by the response of
    your peers.

ElementK Assignment

You have to go through Microsoft project 2002 Level 1 and Leve2 courses in ElementK. These are to be done individually.
Optional assignments are in the project management area. These are Project Management Fundamentals, Part one and Part two

Grand Project

In this project, your group is to identify a real world system. Then, you will need to introduce computerized subsystems to
make the system more efficient or effective. This is an opportunity to help an organization faced with a problem, to enhance
your skills in developing system solutions and identifying requirements, and to show your creativity. The exact nature of the
deliverables will vary depending on the project selected.

The deliverables, carefully designed to keep your group on schedule, are:

•   Deliverable 1 (14-jun): Topic Approval: Half a page: Include the name of the organization, the decision maker, and the
    nature of the problem. Discuss with me during my office hours.
•   Deliverable 2 (21-jun): Detailed Project proposal: Include a detailed description of the problem you are going to assist
    with. What are the overall user requirements and how will you meet these with a system?
•   Deliverable 3 (13-jul): The exact nature of this deliverable will vary by group. Basically, however, it will, depending on
    the project, consist of a few of the following: ERDs, DFDs, screen designs, storyboards, influence diagrams, induction
    tables, block diagrams, dependency diagrams, etc. I will let each group know what I expect.
•   Deliverable 4 (26-jul): A limited working prototype of the system--you need to have the basic functionality in place. I will
    let each group know what I expect.
•   Deliverable 5 (3-Aug): Final Project Presentation: You need to cover the following:

        § what is the problem that you are addressing;
        § what were some design choices you made (e.g., in functionality and in selection of software/hardware, in the design
        of your DBMS, etc) and why
        § Demo your system: please also have a backup in case technology fails (i.e., screen shots of your system)
        § Evaluate your system: i.e., what are you really proud of and what, given more time and/or expertise, could you
        improve upon
        § Lessons learned: what have you learned through all this?
        Everybody in the group needs to present. Professional attire, please.

•   Deliverable: Final Project Report. You need to turn in your projects in a binder. The binder should have dividers that
    separate deliverables 1 and 2 and the final project. Here is what I expect you to turn in:

        1. Cover page---Team name, Name of Project, names, emails, phone numbers for each member of team. Oftentimes,
        your system may not run right on my computer and I need to get in touch with you so that we can resolve the issue.

         2. Table of contents
         5. Main project--divide this into sections with tabs

                  § problem statement
                  § design statement -- what were the design issues you have faced; how did you resolve them
                  § design documentation--- your updated (correct) ERDs, DFDs (up to level 1), and menu hierarchies (story
                  § user manual --- here include screen shots of every screen and report of your system as well as detailed
                  instructions for every screen and report. To begin the section, also indicate any system requirements in terms
                  of hw/sw, and how one goes about starting the system. Does it need to be in a special directory? What does
                  one click on? Is there a password? If so, what is it? For each report, describe what type of question the
                  report answers.
                  § code documentation-- a printout of your code, properly documented
                  § system evaluation -- what are you proud of, what could be improved upon given more time and/or more
                  § Decision Maker reaction: Describe the reaction of the decision maker to your system. Will he/she use the
                  model in the future? Why or why not? You must include a letter from the decision maker with whom you
                  § lessons learned

Credit for team projects will be awarded only if you have a passing grade on the exams (taken together).

Participation + Survey

Participation is counted on two ends – Online and in Class. Online participation is based on participation in the discussion
boards. In class participation will be evaluated based on classroom participation. In both cases content will also be evaluated.
This would be based on instructor’s discretion.

Academic Honesty

I take academic honesty seriously. It is the responsibility of each student to know the University of Georgia policy relating to
academic dishonesty, as contained in the Student Handbook and the Official Guide to Academic Honesty. The UGA academic
honesty policy is online at: http://www.uga.edu/ovpi/academic_honesty/culture_honesty.htm

It is the responsibility for each student to be informed about the policy of academic dishonesty at the University of Georgia.
This means that each student must to read the policy and comply with it. It's no defense to a charge of academic dishonesty to
say 'I didn't know that was prohibited.'

Acts of dishonesty will be handled strictly according to University policy. In particular, it is a violation of the academic
honesty code to put your name on a project when you have not contributed to the project or to give a fellow team member
credit for participating when he or she did not contribute.

On individual assignments and projects, you are expected to do your own work and to not allow others to view or copy your
work. Of course, you may discuss specific problems or issues with classmates. You may not ask a classmate (or other team) to
show you their assignment. Copying all or part of another student (team)'s assignment, having someone else to write part of the
code for your assignments, and taking code from other places without attribution, thus presenting the code as your own, will all
be considered violations of the University of Georgia Policy on Academic Honesty and will be referred to the appropriate
persons for review.

Procedures for handling allegations of academic dishonesty can be found online at:

If you have questions about specific acts and whether they are academically dishonest, please contact me or the Office of Vice
President for Academic Affairs at one of the above links. In general, if you think it is dishonest, it probably is.


To top