|
Text Book:
Software Engineering (9th
edition) by Ian Sommerville, Addison
Wesley, 2011.
Reference Book:
Introduction to the Team Software Process by
Watts S. Humphrey, Addison Wesley, 2000.
Course Description:
Examines
software development processes and management, visual modeling and Unified
Modeling Language, requirements capture, use case analysis, system design and
implementation, components, forward and reverse engineering, software
engineering tools, testing techniques, configuration management, and project
management.
Course Work and Marking Scheme (final marks)
- 30%
Assignments
- 50%
Team Project
- 20%
Midterm: close book, in class on Mar. 31
Course Information
o Description:
1 2 3
o Submission:
1 2 3
o Sample
answer (partial): 1 2
- Project
- Project
idea presentation (5-10min, in lab time on Jan. 11)
- Propose
a smart home and robotics related application with computers,
wired/wireless networks, Internet/Web, mobile/wireless devices,
cameras, and/or sensors.
- Presentation slides submission (ppt, pdf, or doc file)
(by 12pm, Jan. 11)
§ Presentation submission
§ Presentations:
1
2a 2b 3 4 5 6 7
§ Application
subsystem use cases: 1 2
o Feasibility
report (due: Feb. 3)
§ Feasibility report template
§ Technology constraints and options
§ Submission
o Subsystem prototyping requirements (due: Thu. Feb.
17)
o Software Requirement Specification (SRS) (due: Fri. Mar.
4)
§ Submission
o Software Design Description (SDD) (due: Mon. Mar. 28)
§ Submission
o Subsystems Integration Demo Schedule
o Software test Description (STD) (due: Thu. Apr. 7)
§ Submission
o Project
submission requirements: (due: Apr. 15)
§ Each
team only needs to make one submission in form of a single zip file after the
corresponding demo is done or on the due day.
§ Each
submission must include a README (text) file to describe each
component/package in the submission.
§ The
following are required submission contents for each team/subsystem:
·
Robot control subsystem: source code, API
document for local server subsystem to use.
·
Robot arm control subsystem: source code, API
document for local server subsystem to use.
·
Camera control subsystem: camera-side source
code, server-side source code, API document of server-side code for local
server subsystem to use.
·
Petbot subsystem:
source code for 2 or more use cases, API document for local server subsystem
to use.
·
3D mapping subsystem: source code and usage
guide for onboard computer, document describing onboard computer/local server
communications,
client software (link or code) and usage guide.
·
Local server subsystem: source code and usage
guide, document describing local sever/onboard computer and local server/web
server communications.
·
Web server subsystem: web server source code and
usage guide, document describing web server/local server communications.
§ Submission
Reference Information
· Bill Gates: A Robot in Every Home
· IEEE
Recommended Practice for Software Requirements Specifications
· IEEE
System and Software engineering – Recommended practice for architectural
description of software-intensive systems
· IEEE
Standard for Information Technology – Systems Design – Software Design
descriptions
· IEEE
Standard for Software and System Test Documentation (summary)
· iRobot documents: manual, open interface specification, sample program
· Introduction to UML 2.0: 1 2
· Introduction to OCL: 1
2 3 4
· Enterprise Architect UML
Tool (trial version)
· Papyrus
UML Tool (open source)
Lecture Notes and Schedule (subject to change)
|
No.
|
Week
|
Tue
|
Thu
|
|
1
|
01/03-01/07
|
|
Software engineering concepts
|
|
2
|
01/10-01/14
|
Software engineering concepts
|
Software engineering concept review
|
|
3
|
01/17-01/21
|
Software engineering concepts
|
Software engineering concepts
|
|
4
|
01/24-01/28
|
Software engineering concepts
|
Software engineering concepts
|
|
5
|
01/31-02/04
|
Software engineering concepts
|
Software engineering concepts
|
|
6
|
02/07-02/11
|
Dependability and security
|
Team Software Process (TSPi)
|
|
7
|
02/14-02/18
|
Dependability and security
|
Team Software Process (TSPi)
|
|
8
|
02/21-02/25
|
Dependability and security
|
Team Software Process (TSPi)
|
|
9
|
02/28-03/04
|
Dependability and security
|
Team Software Process (TSPi)
|
|
10
|
03/14-03/18
|
Dependability and security
|
UML 2.0
|
|
11
|
03/21-03/25
|
UML 2.0
|
Object Constraint Language (OCL)
|
|
12
|
03/28-04/01
|
Advanced software engineering
|
Midterm
|
|
13
|
04/04-04/07
|
Advanced software engineering
|
Advanced software engineering
|
Course Policy
· Using electronic devices, such as laptops,
cell phones, iPod and iPad, is allowed in classes
only for class related activities.
VIII. ACADEMIC OFFENCES (from UNB 2010-2011 Calendar)
Note:
Consideration of a request to withdraw from a course or courses involved in
an academic offence will not be given until the case is resolved
Academic
offences include, but are not limited to, the following:
A. PLAGIARISM
Plagiarism
includes:
- quoting verbatim or
almost verbatim from a source (such as copyrighted material, notes,
letters, business entries, computer materials, etc.) without
acknowledgment;
- adopting someone
else's line of thought, argument, arrangement, or supporting evidence
(such as, for example, statistics, bibliographies, etc.) without
indicating such dependence;
- submitting someone
else's work, in whatever form (film, workbook, artwork, computer
materials, etc.) without acknowledgment;
- knowingly representing as one's
own work any idea of another.
NOTE: In courses which include
group work, the instructor must define and warn against plagiarism in group
work. Unless an act of plagiarism is identified clearly with an individual
student or students, a penalty may be imposed on all members of the group.
Procedures
In
the case of plagiarism, the instructor must make every reasonable effort to
discuss the case with the student or group and follow one of two courses of
action.
- If the instructor is
satisfied that the plagiarism was the result of a genuine misunderstanding,
the instructor shall complete an academic offence incident report, and
the instructor or the instructor's representative shall submit the
academic offence incident report and attached information to the
Registrar. Where applicable, the Registrar shall advise the appropriate Dean, and the Chair of the student's program or
Department where applicable. The Registrar shall notify the student by
registered letter of the regulations governing plagiarism, the possible
consequences, the student's right to appeal, the right to appear before
the appropriate Committee, and the procedures involved. The Registrar
shall also include, with this registered letter, a copy of the academic
offence incident report and attached information. While a case of genuine
misunderstanding will not be considered a student's first offence, a
second plea of ignorance by the student will be so considered. A student
appealing the instructor's decision must do so in writing within three
weeks of the date of the Registrar's notification. The student is urged
to submit to the appropriate Committee a written statement regarding the
case.
In the case of plagiarism resulting from genuine
misunderstanding, the instructor may permit the student to submit a genuine
piece of work to be graded in place of the one plagiarized. If the student
does not appeal, the time allowed for submission of work is three weeks from
the date of the Registrar's letter of notification. In the case of an appeal,
where the instructor's decision is upheld, the period of time allowed for
submission is as determined by the appropriate Committee.
- If, in the view of the
instructor the plagiarism was deliberate, the instructor shall complete
an academic offence incident report, and the instructor or the
instructor's representative shall submit the academic offence incident
report and attached information to the Registrar. Where applicable, the
Registrar will advise the Dean, and the Chair
of the student's program or department where applicable. The Registrar
shall notify the student by registered letter of the regulations, the
right to respond, the right to appear before the appropriate Committee,
and the procedures involved. The student is urged to submit to the
Committee a written statement regarding the case. A student responding
to the instructor's academic offence incident report,
must do so in writing within three weeks of the date of the Registrar's
letter of notification. At the discretion of the Registrar, cases may be
referred to the appropriate Committee for review and action. The
Registrar shall inform the student by registered letter of the referral
to the Committee, and the wish of the Committee that the student be
present when the case is heard. The Registrar shall also include, with
this registered letter, a copy of the academic offence incident report
and attached information.
Penalties for Deliberate
Plagiarism
In
a case of deliberate plagiarism, the penalties are:
First
Offence:
If the student does not appeal, or if, on appeal, the Committee upholds the
instructor's decision:
- A notation will be
placed on the student's transcript of academic record concerning the
academic offence. The length of time the notation appears on the
student's transcript of academic record is to be decided when the
penalty is imposed and will depend on the severity of the offence.
- The student may be
required to submit a satisfactory and genuine piece of work to replace
the one involving plagiarism. If the assignment is not resubmitted or is
unsatisfactory, the student will receive a grade of F(zero)
in the course. Note: If this penalty is assessed, the period of
time allowed for the submission of the work will be determined by the
Registrar in consultation with the faculty member making the charge,
and, where appropriate, the Committee.
- The student will
receive a grade of F (zero) on the piece of work and, depending on the
severity of the offence, may receive a grade of F for the course.
- Other penalties as
outlined in penalties for Other Academic Offences may be imposed.
Subsequent
Offence:In cases where the Committee
considers that the student has plagiarized again:
- the student will receive
a grade of F in the course and a notation of the academic offence will
appear on the student's transcript of record. The length of time the
notation appears on the student's transcript of academic record is to be
decided when the penalty is imposed.
- Other penalties as
outlined in penalties for Other Academic Offences may be imposed.
B. OTHER ACADEMIC OFFENCES
- Cheating on
examinations, tests, assignments or reports.
- Impersonating a
candidate at an examination or test or in connection with any assignment
in a course or availing oneself of the results of impersonation.
- Obtaining, through theft,
bribery, collusion, purchase or other improper manner,
- an examination or
test paper prior to the date and time for writing the examination or
test;
- academic materials belonging
to another person, e.g. laboratory reports, assignments, papers, computer
materials, datasets.
- Falsifying or
knowingly submitting false assignments or credentials, records,
transcripts, or other academic documents.
- Submitting a false
health or other certificate.
- Submitting identical
or substantially similar work for one course or program of study, which has been or is being submitted for another course or
program of study, without the prior express knowledge and approval of
the instructors.
- Interfering with the
right of other students to pursue their studies.
- Knowingly aiding or
abetting any of the above offences.
- Tampering with, or
altering, in any deceptive way, work subsequently presented for a review
of the grade awarded.
Procedures
The
instructor and, where applicable, the invigilator or other appropriate person
shall, where practical, discuss the matter with the student concerned.
The
instructor or the instructor's representative, satisfied in their view that
an academic offence has been committed shall complete an academic offence
incident report, and the instructor or the instructor's representative shall
submit the academic offence incident report and attached information to the
Registrar. Where applicable, the Registrar shall report it to the Chair of
the Department and the Dean of the Faculty concerned. Each case will be
referred by the Registrar to the appropriate Committee for review and
appropriate action. The Registrar shall inform the student by registered
letter of the referral to the Committee, the student's right to respond and
the wish of the Committee that the student be present when the case is heard.
The Registrar shall also include, with this registered letter, a copy of the
academic offence incident report and attached information. The student is
urged to submit to the Committee a written statement regarding the case. A
student responding to the decision, shall do so in
writing within three weeks of the date of the Registrar's letter of
notification.
Penalties
A
student who is found guilty of an academic offence will have two penalties
imposed:
- Notation on the
student's transcript of academic record concerning the academic offence.
The length of time the notation appears on the student's transcript of
academic record is to be decided when the penalty is imposed.
- A failing grade in an examination,
test or course.
One of the following penalties may also be imposed:
- Recommendation to the
President for suspension for a specified period. The recommendation is
to include the length of time the notation is to appear on the student's
transcript of academic record.
- Recommendation to the
President for expulsion from the University. If the student is expelled
a permanent notation will appear on the student's transcript of academic
record.
C. GENERAL
- Consideration of a
request to withdraw from a course or courses involved in an academic
offence will not be given until the case is resolved.
Students on the Fredericton Campus will submit appeals to the Senate
Student Standings and Promotions Committee; on the Saint John Campus, appeals
will be submitted to the Student Appeals Committee.
|