|
CIS 8030 -
Software Requirements Management
PREREQUISITES:
This course is part of a series of courses designed to teach systems analysts and designers of tomorrow. As such, it requires a good background in computers. A student must fulfill the following course prerequisites as listed in the Catalog description: CSP:
I, II, III, IV, V, VI, CIS 3210 or CIS 3215 or CIS 3260 or CIS 3270.
COURSE MATERIAL:
- Recommended Text: Craig Larman, Applying UML and patterns, Prentice-Hall, Englewood Cliffs, NJ, 1998. Please note that there is no required text for this course.
- Class handouts / overheads
- Readings in Pullen Library reserve: Rambaugh, J., M. Blaha, W,. et al, Object Oriented Modeling and Design, Prentice-Hall, 1991. (chapters 3 & 4)
COURSE DESCRIPTION:
This course provides an introduction to the fundamentals of
software requirements management. Topics covered include requirements gathering,
system modeling and software specifications. The major emphasis is on using a
variety of modeling tools and techniques to define a system specification.
Students are also exposed to emerging topics such as components, patterns and
reuse that promise major improvements in software development productivity.
Information systems development is a process in which technical, organizational and human aspects of a system are analyzed and changed with the goal of creating an improved system. In spite of the advanced technology that surrounds computer-based information systems, the process of systems analysis and design is still largely an art. There is high dependence on the skills of individual analysts and designers even though there are established principles, methods and tools. This course will give students an understanding of the most common tools, techniques, and theories currently used in object-oriented systems analysis.
DETAILED COURSE OBJECTIVES
Understand different perspectives about the systems development process
·
Understand the role and importance of requirements analysis and
specification
·
Understand the role and importance of requirements analysis and specification
·
Acquire a working knowledge of system modeling techniques
·
Understand the basis principles of object-orientation
·
Learn to use a Computer Aided Software Engineering (CASE) tool for
requirements management
·
Learn to recognize and overcome the obstacles in requirements
analysis
·
Understand the role of requirements management in agile software development
·
Become aware of the emerging ideas relevant to requirements management
·
Create commonly expected "deliverables" of systems design including models of structure, behavior and dynamics
EVALUATION POLICY
|
Project 1 |
Draft Design
Design Review
Final Design |
50
20
130 |
200 |
|
Project 2 |
Draft Design
Design Review
Final Deliverable |
75
40
135 |
250 |
|
Tests |
Test 1
Test 2
Final |
175
175
150 |
450 |
|
Participation |
Attendance
Participation |
15
35 |
50 |
|
Total |
|
|
1000 |
Withdrawing
A 'W' grade will be
assigned if a student withdraws before the middle of the semester while
maintaining a passing grade. A 'WF' will be assigned if a student withdraws
before the middle of the semester while doing failing work OR after the middle
of the semester. Missing more than two consecutive classes without the
instructor's permission will be considered a voluntary withdrawal. The grade of
'W' or 'WF' will depend upon whether the student stopped actively attending
prior to the mid-point of the semester.
Class
participation
All students are
required to attend all classes. If one or more class is missed, it is the
student's responsibility to determine the specific material covered during their
absence and make the necessary arrangements for making up what is missed. Class
discussion is strongly encouraged. More than two missed classes in a row
without the instructor's permission will be considered a withdrawal on the part
of the student.
GENERAL CLASS POLICIES
-
Prerequisites are
strictly enforced. Students failing to complete a prerequisites with a grade
of “C” or higher will be administratively withdrawn from the course in which
they are in violation with a loss of tuition fees. There are no exceptions.
-
Students are expected to attend all classes and group meetings, except when
precluded by emergencies, religious holidays or bona fide extenuating
circumstances.
-
Make-up exams will not
be given. However, if a student has a planned absence, he or she may take the
exam earlier with the permission of the instructor.
-
Students who, for
non-academic reasons beyond their control, are unable to meet the full
requirements of the course should notify the instructor. Incompletes may be
given if a student has ONE AND ONLY ONE outstanding assignment.
-
A “W” grade will be
assigned if a student withdraws before mid-semester while maintaining a
passing grade. Withdrawals after the mid-semester date will result in a grade
of “WF”. Refer to GSU catalog or Registrar’s office for details.
-
Spirited class
participation is encouraged and informed discussion in class is expected. This
requires completing readings and assignments before class.
-
Unless specifically
stated by the instructor, all exams and lab assignments are to be completed by
the student alone.
-
Within group
collaboration is allowed on project work. Collaboration between project groups
will be considered cheating unless specifically allowed by an instructor.
-
Copy work from the
Internet without a proper reference will be considered plagiarism and subject
to disciplinary action as delineated in the Student Handbook.
-
Any non-authorized collaboration will be considered cheating and the
student(s) involved will have an Academic Dishonesty charge completed by the
instructor and placed on file in the Dean’s office and the CIS Department. All
instructors regardless of the type of assignment will apply this Academic
Dishonesty policy equally to all students. See excerpt from the Student
Handbook below:
ACADEMIC HONESTY
(Abstracted from GSU’s
Student Handbook Student Code of Conduct “Policy on Academic Honesty and
Procedures for Resolving Matters of Academic Honesty” -
http://www.gsu.edu/~wwwcam/academichonesty.html)
Students are responsible for the information contained in this website.
As members of
the academic community, students are expected to recognize and uphold
standards of intellectual and academic integrity. The
University assumes as a basic and minimum standard of conduct in academic
matters that students be honest and that they submit for credit only the
products of their own efforts. Both the ideals of scholarship and the need for
fairness require that all dishonest work be rejected as a basis for academic
credit. They also require that students refrain from any and all forms of
dishonorable or unethical conduct related to their academic work.
Students are expected to
discuss with faculty the expectations regarding course assignments and standards
of conduct. Here are some examples and definitions that clarify the standards by
which academic honesty and academically honorable conduct are judged at GSU.
Plagiarism.
Plagiarism is presenting another person’s work as one’s own. Plagiarism includes
any paraphrasing or summarizing of the works of another person without
acknowledgment, including the submitting of another student’s work as one’s own.
Plagiarism frequently involves a failure to acknowledge in the text, notes, or
footnotes the quotation of the paragraphs, sentences, or even a few phrases
written or spoken by someone else. The submission of research or completed
papers or projects by someone else is plagiarism, as is the unacknowledged use
of research sources gathered by someone else when that use is specifically
forbidden by the faculty member. Failure to indicate the extent and nature of
one’s reliance on other sources is also a form of plagiarism. Failure to
indicate the extent and nature of one’s reliance on other sources is also a form
of plagiarism. Any work, in whole or part, taken from the internet or other
computer based resource without properly referencing the source (for example,
the URL) is considered plagiarism. A complete reference is required in order
that all parties may locate and view the original source. Finally, there may be
forms of plagiarism that are unique to an individual discipline or course,
examples of which should be provided in advance by the
faculty member. The student is responsible for understanding the legitimate use
of sources, the appropriate ways of acknowledging academic, scholarly or
creative indebtedness, and the consequences of violating this responsibility.
Cheating on Examinations.
Cheating on examinations involves giving or receiving unauthorized help before,
during, or after an examination. Examples of unauthorized help include the use
of notes, texts, or “crib sheets” during an examination (unless specifically
approved by the faculty member), or sharing information with another student
during an examination (unless specifically approved by the faculty member).
Other examples include intentionally allowing another student to view one’s own
examination and collaboration before or after an examination if such
collaboration is specifically
forbidden by the faculty member.
Unauthorized
Collaboration. Submission for
academic credit of a work product, or a part thereof, represented as its being
one’s own effort, which has been developed in substantial collaboration with
assistance from another person or source, or computer honesty. It is also a
violation of academic honesty knowingly to provide such assistance.
Collaborative work specifically authorized by a faculty member is allowed.
TENTATIVE SCHEDULE
The course syllabus provides a general plan for the course;
deviations may be necessary.
|
Class |
Topic |
Readings |
Deliverables |
|
1 |
Introduction
Software Requirements Specifications |
Larman 1,2 |
Profile |
|
2 |
Rational Unified Process and process tailoring |
Rational Unified Process:
Best Practices for Software Development Teams
The Ten Essentials of RUP |
|
|
3 |
OO Basics
|
Larman 3 |
|
|
4 |
OO Basics |
AOS case |
|
|
5 |
Multiple Views
|
|
|
|
6 |
Object Modeling |
Rambaugh 3,4 |
Case for Project 1 |
|
7 |
Object Modeling
Case tool demo |
Design review
Rambaugh 4
Larman 5, 9-12
AOS specification, and models
|
|
|
8 |
Test 1 |
|
Project 1 draft |
|
9 |
Use Case Models |
Larman 6,7,8 |
Project 1
Design review |
|
10 |
Modeling Dynamics:
State Diagram
Sequence / Collaboration Diagrams |
Larman 33
Larman 13,17
Larman 18,19
Project2-sample
Project2-sample solution
course handler system, model |
Project 1 Due (end of week)
|
|
11 |
Development Methodology (1)
OO Methodology 2
Analysis Patterns |
Coad Handout
|
|
|
12 |
Agile Software Development
eXtreme Programming
|
Formal Specification: A Roadmap
Axel van Lamsweerde |
Project 2 Draft |
|
13 |
Activity Diagrams
Logical View
Traceability
Analysis and Design with UML - System Specifications Exercise |
Survey Manager system,
model |
Project2 Design review
|
|
14 |
Test 2 |
|
|
|
15 |
Wrap up
UML to Java
Component Diagrams
Deployment Diagrams
Project 2 presentations |
|
Project 2 Due
Take home finals due during finals week
|
|