Dr. Sridhar Nerur

 Home > Courses > 3305

Syllabus

INSY 3305-001

Information Systems Analysis & Design

Spring 2009

 

Instructor

Dr. Sridhar P. Nerur

Office

COBA 518

Office Phone:

817-272-3530

Email:

snerur@uta.edu

URL:

www.uta.edu/faculty/nerur

 

 

Section Information

Class Number

21247

Meeting Time:

MW 11:00-12:20 pm

Room:

COBA 255

Office Hours:

Monday/

Wednesday

 

10:00 a.m. – 10:55 a.m.

and by appointment

 

 

Course Description

 

INSY 3305. INFORMATION SYSTEMS ANALYSIS AND DESIGN (3-0) 3 hours credit. This is a survey of the concepts and methods of information systems analysis and design, system development life cycle (SDLC) and methodologies associated with the SDLC. Course covers feasibility analysis, requirements definition, systems design, data design, coding design, programming, and implementation. Prerequisite: INSY 3304


 

Learning Outcomes

 

 

Competency

Measurement

    1.

 

You will learn the difference between the traditional systems development life cycle and agile development methodologies. 

Test

2.

You will learn the Agile Manifesto.

Test

3.

You will learn how to write simple use cases.

Project and Test

4.

You will learn about object-oriented concepts.

Test

5

You will learn how to draw class diagrams.

Project and test.

6

You will learn how to draw interaction diagrams.

Project and test.

7

You will learn the importance of refactoring and how to use it.

Test

8

You will learn how to use test driven development.

Test/participation in experiment

9.

You will learn the concept of patterns.

Test

10.

You will learn how to draw Activity Diagrams.

Test

11.

You will learn how to draw State Machine Diagrams.

Test

   12.

 

You will learn and be able to use the open-close principle.

Test

13.

You will learn and be able to use the Liskov substitution principle.

Test

14.

You will learn and be able to use the dependency-inversion principle.

Test

15.

You will learn the interface-segregation principle.

Test

 


 

Textbooks

 

There is no prescribed text for the course. Lecture notes and/or slides will be made available to students.

Additional Information: OO programming is a prerequisite for this course. All examples will be presented in Java. The student is expected to have a reasonably good grasp of object-oriented programming concepts. Although the primary emphasis of this course is on analysis and design principles, there will be a fair amount of programming involved.

 

Software

[Eclipse]           Eclipse is an open source community whose projects are focused on providing a vendor-neutral open development platform and application frameworks for building software. The Eclipse Foundation is a not-for-profit corporation formed to advance the creation, evolution, promotion, and support of the Eclipse Platform and to cultivate both an open source community and an ecosystem of complementary products, capabilities, and services.

Eclipse has formed an independent open eco-system around royalty-free technology and a universal platform for tools integration. Eclipse based tools give developers freedom of choice in a multi-language, multi-platform, multi-vendor environment. Eclipse provides a plug-in based framework that makes it easier to create, integrate and utilize software tools, saving time and money. By collaborating and exploiting core integration technology, tool producers can leverage platform reuse and concentrate on core competencies to create new development technology. The Eclipse Platform is written in the Java language and comes with extensive plug-in construction toolkits and examples. It has already been deployed on a range of development workstations including Linux, HP-UX, AIX, Solaris, QNX, Mac OS X and Windows based systems. A full description of the Eclipse community and white papers documenting the design and use of the Eclipse Platform are available at http://www.eclipse.org.

OR

Netbeans 6.X from Sun (www.sun.com ).

OR

Any other UML compliant software.

 

Grading Policy

 

Exam 1

15%

Exam 2

20%

Final Exam

25%

Group Project – analysis & design **

        20%

Implementation (individual)

       10%

Quiz ***

       10%

Total points

    100.%               

 

** Use case – 5%, class diagram and sequence diagram – 15%

*** Quiz will test your understanding of object-oriented analysis, design, and programming concepts.

Grades: 90-100 = A, 80-89.99999 = B, 70-79.99999 = C, 60-69.999999 = D, 0-59.99999 = F

 

TENTATIVE SCHEDULE

 

Week Starting

Topics

Jan. 19

Course Introduction – UML concepts & notations, OO Concepts

Jan. 26

Course Introduction – UML concepts & notations, OO Concepts

Feb. 2

Requirements analysis using use cases

Feb. 9

Requirements analysis using use cases; Exam 1 (UML concepts, OO concepts, use cases, actors, <<include>>, <<extend>>,..) on Feb. 11

Feb. 16

Class diagrams

Feb. 23

Project use case diagram and specifications due on Feb. 23; Class Diagrams

March 2

 

Class Diagrams; OO principles

March 9

Interaction Diagrams

March 23

Interaction Diagrams; Project Class diagrams due on March 25

March 30

Interaction Diagrams

 

April 1

Exam 2 on April 1 (comprehensive); Project implementation; Exam 2 (use cases, class diagrams, interaction diagrams)

 

April 6

 

Project Sequence Diagrams due on April 8; Project implementation examples

April 13

Activity Diagrams; Package Diagrams; Statecharts

April 20

Statecharts

April 27

Emerging trends; Quiz on April 29

May 4

Emerging trends; project implementation demos; Review for finals. Finals will be comprehensive

May 11

Final exam week (please check final exam schedule for the date and time of your finals)

 

 

NOTE:  THIS SCHEDULE IS SUBJECT TO CHANGE.  STUDENTS ARE RESPONSIBLE FOR BEING AWARE OF ANY CHANGES ANNOUNCED IN CLASS AND/OR VIA E-MAIL.

 

Important Dates:

Jan 20 First Day of Classes

--Feb 04 Census Date

--Mar 16-20 Spring Vacation

Apr 03 Last Day to Drop Classes

--May 08 Last day of classes

See Tentative Schedule for exam dates

 

Specific Course Requirements:  The course will feature a combination of lectures, assignments/project, and exams.  Students may be tested over anything that is covered by the instructor in class.  Students will apply their understanding of OO analysis and design concepts to a project.

 

You are required to use a computer for all assignments, and all documentation and system components are expected to have a neat and professional appearance.  All assignments are due at the beginning of class on the due date either specified in the course schedule or announced in class. Please staple your sheets before you turn them in.

 

Group Project details:

Students will work in groups of three to complete a project that will be handed out in class. You may form your own groups. You may not abandon your group and join another one after the project is handed out. Groups will be responsible for the analysis and design phases of the project. Details of the project will be given in class.

Project Implementation: Each student will implement a scaled-down version of the project. The scope of the implementation will be provided in class. Note that this is an individual assignment and you cannot copy someone else’s implementation. Although the preferred language for implementing the system is Java, you may use any object-oriented language to develop the application. The implementation is due on May 4, 2009. Under no circumstances will I accept it after the due date. In addition, each student will demo the project in my office during the week starting 5/4/2009. A sign-up sheet will be provided to enable you to choose a day and time that is convenient for you.

 

WebCT:  All communications will be handled through WebCT. Please be sure to login to WebCT and check your mail and course content for updates. Please contact UTA’s helpdesk if you are unable to access my WebCT.

 

If you need assistance academically, personally, or socially The University of Texas at Arlington supports a variety of student success programs to help you connect with the University and achieve academic success.  They include learning assistance, developmental education, advising and mentoring, admission and transition, and federally funded programs.  Students requiring assistance academically, personally, or socially should contact the Office of Student Success Programs at 817-272-6107 for more information and appropriate referrals.

 

University and College Policies

 

Academic Dishonesty.  All students are expected to pursue their scholastic careers with honesty and integrity.  It is the philosophy of this Department, this instructor, and the University of Texas at Arlington that academic dishonesty is a completely unacceptable mode of conduct and will not be tolerated in any form.  All persons involved in academic dishonesty will be disciplined in accordance with University regulations and procedures.  Discipline may include suspension or expulsion from the University.

 

“Academic dishonesty includes, bust is not limited to, cheating, plagiarism, collusion, the submission for credit of any work or materials that are attributable in whole or in part to another person, taking an examination for another person, or any act designed to give unfair advantage to a student or the attempt to commit such acts.”  Regents Rules and Regulations, Part One, Chapter VI, Section 3, Subsection 3.2, Subdivision 3.22.  Institutional procedures regarding charges of academic dishonesty are outlined in Part II, Chapter 2, of the Handbook of Operating Procedures of the University of Texas at Arlington.  Copies of the Handbook are available at more than 75 locations on campus, including the Student Congress office, the Library, and the Accounting Department Office (Davis Hall).

 

What Constitutes Scholastic Dishonesty?

Cheating

·         Copying another's test of assignment.

·         Communication with another during an exam or assignment (i.e. written, oral or otherwise).

·         Giving or seeking aid from another when not permitted by the instructor.

·         Possessing or using unauthorized materials during the test.

·         Buying, using, stealing, transporting, or soliciting a test, draft of a test, or answer key.

Plagiarism

·         Using someone else's work in your assignment without appropriate acknowledgement.

·         Making slight variations in the language and then failing to give credit to the source.

Collusion

·         Without authorization, collaborating with another when preparing an assignment.

Grade Grievances.  The procedure in the 1997 catalog is the following:  “The student has one calendar year from the date the grade is assigned to initiate the grievance.  The normal academic channels are the department chair or program director, academic dean, and the Provost….”

 

Americans with Disabilities Act (ADA).  The University of Texas at Arlington is on record as being committed to both the spirit and letter of the ADA to make reasonable adjustments in the classroom necessary to eliminate discrimination on the basis of disability.  Students should meet with the Instructor during the first week of class to discuss their special needs and advise the instructor of any special needs, abilities or limitations and to discuss the instructor’s expectations in class participation, performance and work standards.  Any disclosure by the students of their need for accommodations is recognized to be extremely sensitive and all conversations and other communications will be kept protected and confidential and disclosed on a need-to-know basis only.

 

Students are responsible for contacting and consulting with the University’s Office for Students with Disabilities prior to contacting the instructor about any disabilities.  The student should provide the instructor with some form of written documentation of the disability from an acceptable external source (such as a doctor, psychiatrist, etc.) and from the Office for Students with Disabilities.

 

Absences Based on Religious Beliefs.  A student who misses and examination, work assignment, or other project due to the observance of a religious holy day will be given the opportunity to complete the work missed within 15 days following the due date of the assignment, test, or other project missed.  To be eligible for such a make-up, the student must notify me in writing of classes scheduled on dates he or she will be absent to observe a religious holy day.  Notification must be made within the first 15 (fifteen) class days through either a written correspondence, personally delivered, acknowledged and dated by me or written correspondence, sent certified mail, return receipt requested to me.  Failure to follow the rules provided above within the time frames listed will result in the absence being considered unexcused.

 

Bomb Threats.  Effective April 8, 1997, the College of Business Administration has adopted a policy to deal with the classroom disruption caused by bomb threats in the building.  (A) Section 22.07 of the Texas Criminal Law Statutes governs terrorist threats and classifies bomb threats as Class A misdemeanors.  Section 12.21 of the Texas Criminal Law Statutes states that a Class A misdemeanor is punishable by (1) a fine not to exceed $4,000, (2) a jail term of not more than one year, or (3) both such a fine and confinement.  (B) If anyone is tempted to call in a bomb threat, be aware that UTA will soon have technology to trace phone calls.  (C) Every effort will be made to avoid cancellation of presentation/tests caused by bomb threats to the Business Building.  Unannounced alternate sites will be available for these classes.  If a student who has a class with a scheduled test or presentation arrives and the building has been closed due to a bomb threat, the student should immediately check for the alternate class site notice which be posted on/near the main doors on the south side of the Business Building.  If the bomb threat is received while class is in session, your instructor will ask you to leave the building and reconvene at another location.  (D) Students who provide information leading to the successful prosecution of anyone making a bomb threat will receive one semester’s free parking in the Maverick Garage across from the Business Building.  UTA’s CrimeStoppers will provide a reward to anyone providing information leading to an arrest.  To make an anonymous report, call 817-272-5245.

 

Tuition.  Students who have not paid by the census date and are dropped for non-payment cannot receive a grade for the course in any circumstances.  Therefore, a student dropped for non-payment who continues to attend the course will not receive a grade for the course.  Emergency loans are available to help students pay tuition and fees.  Students can apply for emergency loans by going to the Emergency Tuition Loan Distribution Center at E. H. Hereford University Center (Near the southwest entrance).

 

Attendance and Drop Policy.  Students are required to read and be prepared to discuss the assigned textbook chapters and workbook exercises on the scheduled class days.  Class attendance and lateness policies will be discussed during the first week of class.  Those policies include by reference all provisions for grade adjustment or drop policies included in the applicable Graduate or Undergraduate Catalog in effect at the start of the semester.  NO STUDENT WILL BE DROPPED FROM THE CLASS ROLLS FOR NEVER ATTENDING OR EXCESSIVE ABSENCES.

 

A student dropping a course after the Census Date but on or before the appropriate final drop date will receive a grade of “W” only if at the time of dropping, the student is passing the course (has a grade of A, B, D, or D); otherwise an F will be received.

 

Regulations for International Students

 On December 11, 2002, new F-1 regulations were implemented.  These new INS regulations and International Office procedural changes to accommodate the new regulations may have a direct impact on your current status, your academic program and your future plans for employment, travel, or change of status. For more information, check International Office Website at  www.uta.edu/io.

 

Evacuation Procedures

 

In the event of an evacuation of the College of Business building, when the fire alarm sounds, everyone must leave the building by the stairs.  With the fire alarm system we now have, the elevators will all go to the first floor and stay there until the system is turned off.

 

All those in the North tower side of the building should proceed to the fire escape stairs located on the East and West sides of that wing. 

 

FOR DISABLED PERSONS…..please go to the Northeast fire stairs.  We have an evacu track chair located on the 6th floor stairwell. We have people trained in the use of this chair and there will be someone that will go to the 6th floor to get the chair and bring it to any lower floor stairwell to assist disabled persons.

 

Should this be a real emergency, the Arlington Fire Department and UTA Police will also be here to help. 

 

Useful References

The Unified Modeling Language User Guide by Grady Booch, James rumbaugh, and Ivar Jacobson, Addison-Wesley, 1999

Design Patterns: Elements of Reusable Object-Oriented Software by Gamma, Helm, Johnson, and Vlissides, Addison-Wesley, 1995

Object-Oriented Software Construction by Bertrand Meyer, Prentice Hall, 1997

UML Distilled: Applying the Standard Object Modeling Language by Fowler and Scott, Addison-Wesley, 1997

Applying Use Cases: A Practical Guide by Geri Schneider and Jason P. Winters, Addison-Wesley, 1997

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process by Craig Larman, Prentice Hall PTR, 2002

Refactoring: Improving the Design of Existing Code by Martin Fowler, Addison-Wesley, 1999

Analysis Patterns: Reusable Object Models, Addison-Wesley, 1997

Object-Oriented Software Engineering by Jacobson, Christerson, Jonsson, and Oevergaard, 1992.

In addition to the above, the following URL provides links to useful tutorials/demos on Netbeans. Students are strongly encouraged to refer to these resources.