California State Polytechnic University, Pomona
Expanded Course Outline (ECO)
2008-2009
Department Name: CIS
Prepared By: Larisa Preiser
Course Title: Rapid Systems Development
Course Number: CIS406
Date Prepared: 05/20/09
Date Approved By Undergraduate
Studies Committee:
SECTION A
I.
Catalog Description:
Rapid systems development methods and tools. Emphasis on the prototyping
approach to systems development and human/ergonomic factors in designing user
interfaces. Use of 4GLs, front/back-end CASE tools, code generators and similar
rapid development tools. Prerequisites: CIS 328 and CIS 338.
II.
Required Background or Experience:
A.
Prerequisites:
CIS328 Information Systems Careers and CIS338 Client/Server Applications
Development with Visual Basic.
B.
Prerequisites Justification:
CIS406 is an upper-division specialization course in systems analysis and
application software development. Students may choose to enroll in CIS406
after completing CIS328 (IS Careers) course in which they learn about
systems analysis / application development as one of several IS career
choices.
In CIS406 students develop a complex, multi-tier, integrated information
system utilizing the Visual Basic development environment. Since CIS338
teaches the fundamental techniques of Visual Basic .NET programming, it is
thus a prerequisite to CIS406.
1
C.
General Education Contribution:
Students must pass STA120 and ENG104 with a minimum of a “C” (2.0)
grade. It is expected that the students are able to express themselves
orally and in writing (ENG104) and use basic reasoning skills for problem
analysis (STA120).
III.
Expected Outcomes:

Students will demonstrate the development and management of software
requirements through Joint Application Design (JAD) and Evolutionary
Prototyping sessions

Students will develop relational database designs at the subject area and the
integrated database levels

Students will design and implement evolutionary prototypes of an information
system at a sub-system level utilizing Visual Basic programming environment
and a three-tier client/server architecture

Students will apply the principles and techniques of project management
through planning, estimation, scheduling, tacking and measuring the
development of evolutionary prototypes

Students will create test cases and implement an incremental testing strategy
to test their prototypes at the sub-system and the integrated system levels.

Students will demonstrate the skills of managing the systems development
project throughout all phases of the Systems Development Life Cycle – from
project inception through product implementation

Students will demonstrate collaborative skills by working within the team
environment to develop an assigned sub-system of a larger information
system

Students will demonstrate collaborative skills by working with other teams to
develop a fully-functional, integrated information system

Students will making professional presentations to the client about the project
status and system functionality

Students will develop user documentation for the sub-systems as well as the
integrated system
2
IV.
Text and References:
(Textbook Decision: By Instructor)
Karl Wiegers, Software Requirements, Microsoft Press, 2003. ISBN: 0-7356-1879-8
V.
Special or Unique Student Materials:
Check any materials, supplies, equipment, etc., which students must provide.
___Zip Disk
___Floppy Disk
___Calculator
___Graph Paper
___CD-Rom
___Writing Pad
VI.
___Camera
___Video
Camera
___Videotape
___Laptop
_x_Computer
___Other
Special or Unique University Facilities:
List the university facilities/equipment that will be required in order to offer this class,
such as gymnastic equipment, special classroom, A-V equipment, laboratories, etc.
___Computer Lab
__x_Computer Connection
___File Server
_x__Computer Projector
_x__Laser Pointer
_x__White Board/Markers
___VCR
___Printer
_x__Internet Connection
___Laptop Ports
VII.
___“Smart” Classroom (one
workstation)
_x_Overhead Screen
___Microphone
___Moveable
Classroom
Furniture
___Other ____________
Expanded Description of the Course and Instructional Methods:
A.
Expanded Description of the Course:
CIS406 is an advanced specialization course for CIS students. The key
objective of this course is to teach students how to develop a multifunctional, integrated, user-friendly information system utilizing the
techniques and methods of evolutionary prototyping and joint application
development. The specific learning objectives of this course are:

Eliciting client’s requirements for an information systems through a
series of structured Joint Application Design sessions;

Modeling data and graphical user interface requirements of the
client
3
B.

Designing subject area databases and an integrated database for
the system

Designing and incrementally developing application functions at a
sub-system and system levels utilizing the techniques of
evolutionary prototyping in the Visual Basic development
environment

Applying testing and quality assurance techniques at the subsystem and system levels

Managing the project from its inception to the delivery of the
system to the client

Making oral and written presentations of the project’s progress and
deliverables to the client.

Developing a theoretical understanding of rapid application
development techniques, prototyping, JAD and best practices in
software development
Instructional Methods:
The instructor will set up a course web site with all the requisite
requirements for the course, including the course information, course
deliverables and the course schedule. Instructional methods for this
course will be as follows:
 lecture presentations utilizing Power Point materials and the
white-board
 discussion and analysis of the assigned reading materials
 hands-on systems analysis, database design and
programming projects
 JAD and Prototyping presentations sessions for system
prototypes.
___Lecture
___Cases
_x_Lecture/Discussion
___Seminar
___Simulation
___Open Lab
___Videotapes
__x__Other
4
___Individualized
Instruction
___Cooperative Learning
___Distance Learning
VIII. Methods of Evaluating Outcomes:
Should be tied to the mission, goals and objectives of the program and to the
objectives of the particular course. Describe the methods to be used in
evaluating students' work, i.e. written exams, term papers, projects, participation,
quizzes, attendance, etc. These evaluation tools are to provide guidance to
faculty teaching the course. Individual instructor methods of evaluation may vary.
Remember that all classes taught at the College of Business require
writing by the students.
Recommended Evaluation Tools:
Individual Paper: ___%
Tests & Exams
_22__%
Individual Project ___%
Group Paper: _28__%
Quizzes ___%
Team Project _35__%
Individual Presentation
___%
Peer Evaluation
_7__%
Outside/Expert Evaluations
_4__%
Group Presentation ___%
Participation __4_%
5
Other: ________
___%
SECTION B
Week #
1
Theme/Topic
Introduction to the Course
 Course Overview, Objectives, Outcomes, Expectations;
Syllabus review; Team work within and across teams
Systems Analysis/ DB Design review
Group dynamics

2
Forming teams; Negotiating roles; Developing team memo
Software Requirements: What, why, and who




The essential software requirements
Requirements from the customer’s perspective
Good practices for requirements engineering
The requirements analyst
Sub-system assignments and case discussion / preliminary interviews
with the client
Project Management
 Principles and techniques
3
Software Requirements Development




Product vision and project scope
Understanding and documenting user requirements
Software quality attributes
Risk reduction through prototyping
Preparing for JAD 1 session
 Questions, clarifications of JAD1 requirements
4
Joint Application Development Session 1 (JAD 1.1)
 Team presentations – subject area databases
 JAD 1 Reports
5
Joint Application Development Session 1 (JAD 1.2)
 Database integration presentations
6

Database Integration Report
Software Requirements Management
 Requirements management principles and practices
 Change management
 Tools for requirements management
6
MIDTERM EXAM
Best Practice in Software Development:

Critical Success Factors in IT Implementations
7
PROTOTYPE I Demonstrations
 Team presentations
 Prototype I Report
8
Joint Application Development Session 2 (JAD 2)
 Team presentations – sub-system functions
 JAD 2 Reports
Best Practice in Software Development:

Critical Success Factors in IS implementations
Implementing Requirements Engineering

Improving requirements processes

Software requirements and risk management
9
PROTOTYPE II Demonstrations
 Team presentations
 Prototype II Report
10
Best Practices in Software Development:

11
Building High Quality IT-Business Working Relationships:
Lessons learned from research in the IT field
Final Prototype Presentations
Client Training
Project documentation and system’s software turned in to client
SECTION C
7
SECTION C: UNDERGRADUATE LEARNING GOALS (AACSB STANDARDS)
Foundation Knowledge and Skill Learning Goals
Goal
Written and oral communication skills as evidenced by an
ability to express complex issues orally and in proper written
English.
Analytical, and problem solving skills as evidenced by an
ability to organize and utilize quantitative and qualitative
information and appropriate methods to make decisions.
Teamwork and interpersonal skills as evidenced by an ability
to achieve common objectives in a diverse cultural
environment.
Information technical skills as evidenced by an ability to use
current information technology to convey information, solve
problems, and expedite business processes.
Demonstrate awareness of ethical responsibility to business
professions and society.
TOTAL
Class Contact Hours*
12
9
11
7
3
42
Management-Specific Learning Goals
Goal
Develop broad knowledge of critical areas of business,
including statistics, accounting and finance, economics,
information management, management, marketing, and
operations management.
Explain the impact of internationalization on the various
functional areas of business.
To be able to deal with business problems from the integrated
perspective of the business as a whole.
TOTAL
Class Contact Hours*
15
5
20
40
*Explanation of class contact hours: these hours are being collected as part of an AACSB
requirement and will be used to assess our undergraduate program.
Revised 05/20/09
8