---

Brian J. Reithel, PhD, CDP
Holman Hall 240
(662) 915-5469
Office Hours: MWF 10-11 a.m.

Email: breithel@bus.olemiss.edu

Homepage: http://faculty.bus.olemiss.edu/breithel/

Software Engineering: A Practitioner's Approach, 5th edition

by Roger S. Pressman
McGraw-Hill, 2001.

An Introduction to Object Oriented Analysis (Objects and UML in Plain English) 
        by David William Brown 
        Wiley, 2002, 2nd edition.

RECOMMENDED TEXTS:

Beginning Visual C++ 6
        by Ivor Horton
        Wrox Press, 1998

Code Complete
        by Steve McConnell
        Microsoft Press, 1993

An applications course which builds on the concepts and techniques developed in MIS-307 to enable students to design and implement systems in "real-world" organizations. Prerequisite: MIS-307, MIS-309,  or consent of instructor.

MAJOR OBJECTIVES OF THE COURSE:

The purpose of this course is to allow the student to:

• Gain further understanding of, and experience with, the systems development process.
• Be able to use UML for analysis, design, and documentation of information systems.
• Learn to apply advanced software/systems engineering principles and tools to the systems development process.
• Create multiple information systems and user documentation using rapid prototyping techniques in a Visual Programming Environment using Microsoft Visual C++.
• Become familiar with rapid development using pre-existing class libraries.
• Become familiar with current issues and future approaches to information systems development discussed in the software engineering literature.
• Solidify understanding of object-oriented systems analysis, design, and implemenetation.
• Develop the ability to uncover and use advanced reference materials via the Internet.

As an MIS professional, the student is expected to have read assigned materials and to have completed assigned homework/project exercises prior to each class. The class discussions/lectures are intended to emphasize the primary concepts from each reading and to provide an opportunity to answer any questions that may result from the readings and/or assignments.

There are NO make-up exams. Students missing one midterm exam due to a PRE-ARRANGED excused absence will be allowed to count the final as 55% of his/her grade.

System project package number 3 will NOT be accepted after May 3rd. Homework assignments and projects number 1 and 2 must be handed in within 3 working days of the assigned due date.  A 25 point per day penalty will be imposed on late homework.

Poor performance is not an acceptable reason to request an incomplete grade.

The academic discipline policy of the University of Mississippi will be strictly followed in this course. Any academic misconduct or dishonesty will result in a grade of "F" in the course. The student should refer to the "M" book for definitions of academic misconduct.

Class participation is an important part of the learning experience. Many topics discussed in class will not be in the text; thus, missing classes implies missing knowledge which leads to missing opportunities to perform well on examinations and on the job after graduation.

Students should anticipate spending a significant amount of time EACH WEEK in the computer laboratory (or using a personally-owned computer if the student has the necessary software development tools/packages). This is the only way that true proficiency in the usage of modern program development tools can be attained.

Grades can be retrieved via the campus BlackBoard server.  Also, your homework assignments must be submitted via the Digital Drop Box feature of BlackBoard.

Project Mastery Requirement: Your semester letter grade will not be allowed to exceed the letter grade you earn from the projects. For instance, if you earn a final grade of "B" on your projects, that will be the maximum letter grade that you can receive for the semester.

---

Homework assignments will be given periodically throughout the semester. The purpose of the homework is to give the student an opportunity to apply the concepts from the readings and to help the student prepare for the exams. homework assignment grades will be either satisfactory (100 points) or unsatisfactory (0 points), less any late penalties.
 

You also need the latest version of the Real Video Player.  If you do not have the latest version of the Real Video Player, you can click on the link below to download it onto your computer.  Once you have the Real Player installed, you can simply click on the video camera icon next to the lecture that you would like to view.

Note: these videos are currently working on campus.
Some difficulties have been reported with off-campus access; 
the primary source of difficulty has been traced
to the version of RealPlayer that may be installed.  If you
are having problems, please be sure that you have
the latest version (version 8) of the RealPlayer
installed on your computer.

• Together/C++ UML Modeler  
• Rational Rose

MIS-495 Tentative Schedule Spring 2001

**Note:  Due to a problem with the program used to digitize class films, for the mean time each class period will be divided into two segments.

DATE	Class Video	DISCUSSION TOPIC AND RELATED LINKS
January 7		Course introduction, event-driven programming
9		Microsoft Foundation Classes Programming Assignment #1
11	*No Class	Programming using MFC  Steps in Generating an MFC Application Sample Code for a Very Simple Windows Employee Tracking Program K and R Trucking C++ Files Example to be converted to Win API Class Diagram PowerPoint File Chapter 5 from Brown on Objects and Classes Chapter 6 from Brown on The Object-Oriented Development Life Cycle
14
16
18
21	*No Class	HOLIDAY - Martin Luther King, Jr. Day
23		Programming using MFC (reading only Pressman Ch. 20 - Object-Oriented Concepts and Principles)  Dialog Box Activation C++ Snippet Programming Assignment #2 Also, Shift-click on this link to download C++ Source Code -- collect.cpp  for the homework assignment to draw a class diagram.  Bring your diagram to class on Friday.  Here is the collect.h header file in case you want a copy of it for reference purposes.
25	*No Class	MFC-continued  (reading only Pressman Ch. 21 - Object-Oriented Analysis)  Docexamp.cpp  DocexampDoc.cpp  DocexampView.cpp
28		Programming Assignment #3 Sample code:   CView-derived code   CDocument-derived code
30		Making the transition from the DOS API to the WINAPI (continued).
February 1		MFC-continued  (reading only Pressman Ch. 22 - Object-Oriented Design)  Sample Code for a Windows Program with a listbox and File dialog boxes
4		MFC-continued  (reading only Pressman Ch. 23 - Object-Oriented Testing)
6		MFC-continued  (reading only Pressman Ch. 24 - Technical Metrics for Object-Oriented Systems)
8		MFC-continued   Unified Modeling Language (see the useful UML links in the UML Resource Center; see also the Together/C++ site for another useful UML tool)  K and R Trucking Example 1 Another C++ Example  -- K and R Trucking port -- another version UM Inventory Sample Code from class
11		MIDTERM EXAM ONE (Note: Feb 11 is last day to withdraw)
13		Pressman Ch. 1 - The Product,  Brown Ch. 7 - Building the Requirements Model
15
18		Pressman Ch. 2 - The Process             The Personal Software Process              Software Process Dashboard Initiative             (note: there are four different links for this date, click carefully)             (Last day to withdraw from the course is February 14)
20		Pressman Ch. 3 - Project Management Concepts  Brown Ch. 8 - Properties of Objects and Classes Brown Ch. 9 - Finding Objects and Classes in the Real World
25		Pressman Ch. 4 - Software Process and Project Metrics Brown Ch. 10 - Object States and the Statechart Diagram Payback Period Example Spreadsheet (Excel)
27		List of potential project metrics (from class) Function Point Workbench  Scientific American Article on Function Points
March 1	* Watched Video *	Project Management Spreadsheet (PERT/Gantt due on the Wednesday) Pressman Ch. 5 - Software Project Planning  COCOMO II Pressman Ch. 6 - Risk Analysis and Management Object Diagram Example on the Doc/View Model  Doc file with array View file with array
March 4		Pressman Ch. 7 -Project Scheduling and Tracking  Pressman Ch. 8 - Software Quality Assurance  Pressman Ch. 9 - Software Configuration Management Brown Ch. 11 - Examining Execution Sequences Project example:   Project Mgmt Spreadsheet   Gantt Chart View   PERT Chart View
6	* Watched Video *
8		MIDTERM EXAM TWO
11-16		SPRING BREAK HOLIDAY
18		Doc/View handler Code segment that shows how to initialize and retrieve data values in simple controls Pressman Ch. 10 - System Engineering  Pressman Ch. 11 - Analysis Concepts and Principles  Pressman Ch. 12 - Analysis Modeling
20
22		Pressman Ch. 13 - Design Concepts and Principles Brown Ch. 12 - Subsystems Brown Ch. 13 - Object-Oriented Design
25
27		Pressman Ch. 14 - Architectural Design Pressman Ch. 15 - User Interface Design Document/View Diagram     Pressman Ch. 16 - Component-Level Design Pressman Ch. 17 - Software Testing Techniques  Pressman Ch. 18 - Software Testing Strategies
29	No Class	GOOD FRIDAY HOLIDAY
April 1		Pressman Ch. 19 - Technical Metrics for Software Here are two different approaches for handling a menu choice to add a record to a database. The database contains three columns (Author ID: AU_ID, Author Name: AUTHOR, Year Born: YEAR_BORN). Both approaches assume that a menu choice to "Add Record" has been added to the menu. Simple addition of a blank row in a single handler Cooperative message handlers featuring redefined OnMove() function -- (.cpp file) -- (.h file). In the header file, the only extra line is the line used to add the protected boolean variable "m_bAddMode". Sample code to change the SQL statement that is retrieving data from the database.
3		Pressman Ch. 25 - Formal Methods Brown Ch. 14 - OOPLs and OODBMSs Sample Client/Server code (in Zip file) from class
5	* Watched Video *	Video Day
8		CSocket Client/Serve Diagram
10	* Watched Video *
12		Pressman Ch. 26 - Cleanroom Software Engineering Brown Ch. 15 - Object-Oriented Techniques
15		Pressman Ch. 27 - Component-Based Software Engineering Pressman Ch. 28 - Client/Server Software Engineering
17
19
22		MIDTERM EXAM THREE Bonus Round for Midterm Three
24		Pressman Ch. 29 - Web Engineering Pressman Ch. 30 - Reengineering Brown Ch. 16 - The People Side of Systems Development clientserverView.cpp Pseudocode for Client/Server Application Here is another clientserverView.cpp file that forces serialization Yet another example
26
29		Pseudocode for multi-transaction client/server application-level protocol
May 1		Sample code for a more complex client/server application that interacts with a database on the server side
3		SEMESTER PROJECTS DUE TODAY BY 4PM (Last class day)
7		FINAL EXAM (4 PM)

---

TOPIC COVERAGE SUMMARY:

                                                 Hours

     Prototyping and C++                           11    
     CASE/Development tool usage                   10
     Software/Systems Engineering                   8
     Object-Oriented System Development             7
     Causes of Systems Success/Failure              4
     Software Metrics                               3
     Future Development Issues                      2
                                                   --
                               Total               45

Comments: reithel@bus.olemiss.edu