Systems Analysis and Design II
Prof. Sotirios Liaskos
Phone #: 416 736 2100
This page contains
general information about the course; nothing more
will be posted here throughout the term.
Registered students should use for current
Please follow this link to
login to Moolde.
Use your Passport York to Login
Overview and Learning
ITEC4010 is an
advanced course on the Analysis and Design of Information Systems. We
start with topics on project management including project planning and
system lifecycle models. We then look at requirements elicitation and
analysis practices, focusing on the Object-Oriented approach. The rest
of the course is concerned with Design: design principles,
architectural styles, design patterns, principles of architectural
documentation and modeling, UML as a language for representing and
documenting software designs, relationship between design and
implementation. At the end of the course we will also discuss quality
assurance (testing) and other issues pertaining to software engineering
as a process such as version control and estimation.
This section of the course is
largely practice-oriented and course meetings ("lectures") rely on
students collaboratively working on given examples. Coursework involves
two (2) exams and a group term project featuring, among other things,
three (3) major deliverables and, potentially, a group presentation.
At the end of the course, students will have a deeper knowledge of
issues pertaining to analysis and (mostly) design of large information
systems that are essential for entering the IT development and
consulting industries. The term work is highly important as it will
help students consolidate the theory and build experience and
confidence in dealing with complex projects.
content, schedule and evaluation scheme change frequently PLEASE refer
to the MOODLE page for current up-do-date information.
Bernd Bruegge and Allen H.
Dutoit. Object-Oriented Software
Engineering - using UML, Patterns and Java, 2nd ed. Prentice
Hall, 2004. (ISBN: 0130471100)
2010 Textbook: John W. Satzinger,
Robert Jackson and Stephen
Analysis and Design in a Changing World. (4th Edition or later) Course
prerequisites - AK/ITEC 1000 3.0, AK/ITEC 1010 3.0, AK/ITEC 1620 3.0,
AK/ITEC 1630 3.0, AK/ITEC 2010 3.0, AK/ITEC 2620 3.0; AS/AK/ITEC 3220
3.00 or AS/AK/ITEC 3421 3.00 or AS/AK/SC/COSC 3421 3.00 or AS/AK/SC/CSE
3421 3.00. Course credit exclusion: GL/ITEC 3800 3.00.
A typical evaluation
scheme is as follows:
- Project (60% -
Teams of four)
- Deliverable 1
(15%): Requirements Analysis
- Deliverable 2
(15%): Design Document
- Deliverable 3
(15%): Implementation and Testing.
Management and Reporting (15%)
- Exams (40%):
- Midterm (20%)
- Final (20%)
A typical term is organized as
Week 1. Project Organization and Management and Software Lifecycles
Week 2. Requirements elicitation and modeling. Use cases, activity
Week 3. Requirements Modeling: Sequence Diagrams, Class Diagrams,
Week 4. Three-layer designs. Producing three layer designs using
sequence diagrams. Three-layer architectures and Enterprise Java Beans.
Week 5. Issues on Design and Architecture: system decomposition,
deployment environment, architectural styles, design goals and criteria.
Week 6. 1st Tutorial on Case Tool
Week 7. Design Patterns.
Week 8. More Design Patterns.
Week 9. 2nd Tutorial on Case Tool
Week 10. Testing.
Week 11. Estimation.
Week 12. Recap and Presentations.
Other topics may include:
Service Orientation and Web Services, Configuration Management,
Structured Inspections, Architectural Modeling, Aspect-Oriented
Programming, Generic Programming.
Students are referred to
the departmental course
pages with official
policies and directions regarding exam deferrals, special accomodations
Communicating with the Instructor
(Registered Students PLEASE ATTEND):
- Student questions about lectures, material,
additional information etc. should be posted publicly on Moolde so that
other students benefit from the answers. Students who want to
answer to their colleagues' posts on Moodle are encouraged to do
- Use private e-mail for administrative issues or
when your message
contains information your colleagues should not see (e.g. implies bits
solution). All correspondence MUST be named and the instructor must
be able to
confirm you are in the course list; anonymous messages will of course
be ignored, unless good reason provided..
- Make sure you use office hours and
opportunities to talk to me
directly, for quick responses.
- Also, please use phone only in cases of
emergency and DON'T use voicemail
if you can send
e-mail (I will check the latter sooner). Use both to be on the safe
side; all this in case of emergency.
Please show professionalism
in all your correspondence.
you in class!! (and Moodle)