SE 2030 Software Engineering Tools and Practices Dr. Rob Hasker

Description     Syllabus     Policies     Quizzes     Lab info     Coding Standard     Grading     Blackboard     Sample Code

Credit: Much of this material was originally written by Dr. Mark Hornick

Course Description

As an SE major, you've previously taken CS or SE courses in computer programming and data structures. With this background, you have a basic understanding of how simple Java applications are constructed using Eclipse. But what kinds of tools are used to create "real" applications, and how do you use them together?

This course provides an introduction to the Software Engineering Tools and Practices - a look at a typical approach software engineers create applications in practice. Topics include requirements analysis, high-level design, detail-level design, UML modeling, code generation, application building, and revision management. Laboratory assignments provide an opportunity for students to develop an understanding of these tools and how how they are used in actual practice. 

Please consult the Course Catalog for detailed objectives.

Textbook

No official textbook. Instead, we have provided urls to internal and external websites. The Reading Assignments contain the links to these sites. In addition to those, an SE2030 Wiki and and Enterprise Architect Wiki have been created for this course.

Syllabus

Video: Sequence Diagrams with EA

Course policies

Detailed policies for this course are here.

Quizzes

A quiz will be given approximately once per week at the beginning of Lab. No make-up quizzes will be given.

Grading algorithm

Note that this algorithm indicates how a grade will be determined for students who have successfully demonstrated mastery of the course objectives. An acceptable level of success in meeting all course objectives is a prerequisite for a passing grade in the course.

^*All students must take the final exam to pass the course.

Your lab and report grades will be determined as described on the Lab Report page.

Code Commenting and Documentation Standard

All source code submitted must use JavaDoc commenting conventions and meet the minimum documentation standards below:

• The name of the file.
• A short description of the purpose of the class contained in the file.
• The date it was originally written.
• The original author.
• A modification log (when appropriate) which describes:
• What modifications were made.
• When the modifications were made.
• Who made the modifications.

Each class method should contain the following documentation:

• Explanatory notes regarding the overall usage of the method; that is, what the method does.
• The parameters passed in the formal argument
• What the method returns (if anything)
• Any sources other than the author (Web URL, fellow student, etc.) that aided in the design of the method (and what aid was provided).
• Explanatory notes regarding the internal workings and coding whose purpose is not immediately obvious to someone with your current level of programming knowledge

About Labs

Note that the labs constitute a significant part of your overall grade. Plan to devote a considerable effort in order to complete these labs successfully and professionally.

The labs for SE2030 are fairly simple programming assignments such as what you have been used to in courses such as SE1021. They are not particularly challenging from an algorithmic standpoint. Rather, they permit you to focus on their primary objective: to help you develop a familiarity with practices and tools used in professional software development.

Even so, as you begin to develop an understanding of using these elements, you will still have to expend a reasonable effort as you practice using these tools. You should probably expect to spend additional time outside of class to complete the assignments for the labs.

This page was last updated on 09/09/2013.