SE6383 – Advanced Software Engineering Project

Spring, 2010

 

1. INSTRUCTOR:      Dr Kang Zhang, Room: ECSS3.227, Phone: 972-883-6351, kzhang@utdallas.edu

 

2. CLASS TIME:        4:00-5:15pm, MW, in ECSS2.203

                               

3. OFFICE HOUR:    3:00-4:00 pm, Wednesdays

 

4. PREREQUISITES: CS/SE6361 (RE), CS/SE6362 (SA), CO-REQUISITE: CS/SE6367 (STVV)

 

5. SYLLABUS:

 

This course is intended to provide experience in a group project that requires advanced technical solutions, such as distributed multi-tier architectures, component-based technologies, automated software engineering, etc., for developing applications, such as web-based systems, real-time systems, biomedical systems, legal systems, mobile adaptation, etc. Three to four students form a group to develop and maintain requirements, architecture and detailed design, implementation, and testing and their traceability relationships. Best practices in software engineering will be applied.

                                               

6. TOOL TO BE USED:        IBM Rational Rose                             

                            

7. ASSESSMENT:

 

Grades will be determined by a complete project, with weightings:

            Requirement analysis:                          10%

Architectural design/modelling:                       10%

            Testing and traceability:                                   10%

Technical challenges:                           10%

            Usability:                                             10%

            Functionality:                                       20%    

Presentation:                                        10%

            Documentation:                                               10%

            Class participation:                              10%    

Every student is expected to participate in all the classroom discussions and presentations, and also evaluate other groups’ projects.

 

8. SCHEDULE:

 

4th Week:                     Presentation of requirement analysis

6th Week:                     Presentation of the design and modelling

8th Week:                     Progress report

10th Week:                   Presentation/demonstration of the traceability

12th- 13th Week:                       Project demonstration

14th- 15th Week:                       Final presentation of the project

 

9. SUBMISSION:

 

Final submissions include all the source code, user manual, internal documents (requirement analysis, design and modelling, etc), and a 2-page report summarising all the achievements and limitations.

 

10. GENERAL RULES:

 

·         Cheating will not be tolerated. Those who are caught on cheating will be subject to the university’s discipline code.

·         Students are required to participate in all the discussions and presentations in the class, and also meet with industrial partners if applicable. Exceptional cases, such as illness and accidents, will be handled on an individual basis (Instructor must be notified and proof presented – otherwise an absence will be recorded).

·         Major announcements and all grades will be posted on eLearning

·         If you decide to stop attending class, be sure to drop the course officially.