|
Instructor: |
Robb Klashner, Assistant Professor |
|
Office: |
Room 4206 GITC, |
|
Email: |
klashner@njit.edu [most dependable] |
|
Phone: |
(973) 596-5481 [least dependable] |
|
Office Hours: |
Fridays 1:00 – 2:20 pm, 5:30-6:00 pm; also by appointment |
|
Website: |
|
|
Text: |
Sommerville, Ian. (2001) Software Engineering (6th edition), A-W Pub. |
|
Prerequisite: |
Permission of the Instructor |
|
Hours: |
Fridays 2:30 – 5:25 pm |
|
Location: |
KUPF 107 |
|
Section: |
1 |
|
Materials Available |
|
|
Week # |
General Descriptions |
Reading |
|
Week 11 |
Review all aspects of project in individual group meetings and make recommendations, adjustments, and create new list of changes. |
|
|
Week 10 |
Bind requirements and
analysis in the RUP process through a workflow perspective. Integrate architectural
concepts into the analysis model. |
|
|
Week 9 |
Look at software architectures and processes more carefully focusing on the elaboration phase of our new hybrid RUP approach. |
Chapter 12 |
|
Week 8 |
Introduction to Rational Unified Process and using a Rich Picture to launch a use-case based, software architecture-centric process. Examine the requirements workflow in greater detail based on the Sommerville approach. |
Chapter 10, 11 |
|
Week 7 |
Introduction to software requirements, modeling systems, and prototyping. We discuss many of the fundamental concepts used in later process execution. |
Chapter 7 & 8 |
|
Week 6 |
Project groups meet with professor individually Oct. 11 to review progress & clarify approaches. Meet back in class for short presentations regarding process improvement, including student presentation of CMM. |
Chapter 25, 5, & 6 |
|
Week 5 |
Complete the discussion of management and move into costing the project. The paper is fairly dense, but do your best to gleen the important aspects before coming to class. |
Boehm95cost |
|
Week 4 |
"Management" will be engaged selectively to enhance the project group interactions and draw out real world scenarios. The treatment in the book is satisfactory, but we do not have time to examine these chapters at length. |
Skim Part 6 |
|
Week 3 |
Review various software process models then compare and contrast their applicability. Examine how to plan and execute a project. Discuss using MS Project with to facilitate the expression of the project in graphical representations. |
Chapter 3 & 4 |
|
Week 2 |
Course Overview: Course audience and demographics, Administrative matters, Foundational concepts, Course Topic 1: System Life Cycle and Enterprise Architectures |
Chapter 1 & 2 |
|
Week 1 |
Introductions: An informational process as
part of forming groups. Provide a current resume’. Please introduce yourself
to the class by providing the basic synopsis of who you are, what you do,
i.e. your specialties, what is your technical background
with computers, what experiences do you have, i.e. how much have you worked
directly with users to: gather requirements, train users, evaluate the systems
they are using, and/or design and implement real applications? Try to keep
this to a page or less. Make sure you do not double space your lines. Break into Groups |
Summary: This course focuses on the systems analysis and design
techniques employed in the development of software applications. Topics include
software process and process models including the Rational Unified Process
(RUP), project management, structured and object oriented analysis, system
design, quality systems including the Capability Maturity Model (CMM), Joint
Application Design (JAD), system and software architecture, PLA, design patterns,
re-use and component-based design, change control and configuration management.
Analysis and design will be covered primarily from an object-oriented perspective.
Students will read selected material from the literature, actively participate
in discussions, labs and exercises in addition to participating in projects
that involve analysis and design for real-world problems. We will spend
a considerable amount of time interacting and learning through discussion
of assigned readings and other material.
Note about Demographics of Class: The class is expected to be comprised of several different groups of individuals. For example, students attending class will be both Masters and Ph.D.; both very experienced and inexperienced; both technically oriented and socially-aware, and; computer science, information systems, or management. This situation is requires that we search for learning opportunities together. One solution to this situation is to slightly modify the course for individuals to meet their backgrounds and goals. Specifically, Masters and Ph.D. students will have slightly different curriculum. Also, group projects should demonstrate the degree of technical expertise demonstrated by the members of that group.
Expectations and Conduct:
Regular attendance is expected, but not required. However, absences will affect the student’s participation grade. The conduct in the classroom will be consistent with a learning atmosphere that is acceptable for everyone enrolled.
Students have the responsibility to know and observe the requirements of the NJIT Honor Code of Student Academic Integrity. This code prohibits cheating, fabrication or falsification of information, multiple submissions of academic work, plagiarism, abuse of academic materials, and complicity in academic dishonesty. These standards of academic integrity will be enforced in this course. Academic conduct and policies can be reviewed in the student handbook, ( http://www.njit.edu/handbook/Main.htm ). Violation of these policies will be dealt with in a manner consistent with normal NJIT procedures and policies.
Grading:
Since I am new to NJIT, I intend to explore various options . Essentially, my aim is to gear the grading schema to fit the demographic makeup of the class. This approach means that the class will initially have some input into the process. The presentation of possible choices is not meant to infer that the grading policy will be “adapted” to any particular student or group of student’s personal needs or preferences. Rather, I hope we will work together in striking an appropriate balance based on the configuration of the participants.
Grading Details and Assignments:
The nature of the situation mandates flexibility.
Although this course focuses on the systems analysis and design techniques employed in the development of software applications using a software engineering perspective, I intend to explore other, less conventional research streams regarding this area.
Topics include, but are not limited too::
Students will read selected material from the literature, actively participate in discussions, labs and exercises in addition to participating in projects that involve analysis and design for real-world problems. Project work is challenging and will constitute a great deal of the student’s grade.
We will spend a considerable amount of time interacting and learning through discussion of assigned readings and other material.
Exams:
The exam(s) will cover all lectures, readings, class discussions, and software usage. They will call upon your knowledge of the material covered in class as well as application and extension of the material to the real world.
Project:
The Project is an opportunity for you to apply the concepts we will discuss throughout the semester to solve “real-world” problems. Working as a team, you are to demonstrate your mastery of the concepts, methods, tools, and techniques covered in class to elicit and document requirements, develop appropriate models for analysis and create a design for a system of your choice, pending instructor approval.
Class Exercises and Discussions:
Your overall grade for this component will be based on the quality of your effort in leading and participating in class discussions and exercises