SE 6354 Advanced Software Engineering The University of Texas at Dallas Fall 2003 Dr' Kendra Cooper

1
SE 6354 Advanced Software EngineeringThe
University of Texas at DallasFall 2003Dr.
Kendra Cooperkcooper_at_utdallas.edu
2
Lecture Overview

• General Introduction
• Project Description
• Course Evaluation
• Readings and Tasks

3
Advanced Software Engineering SE 6354

• Instructor Kendra Cooper
• Joined UTD faculty in 2001
• Member of the software engineering group at UTD
• Research focus is on requirements engineering and
  software architecture
• Home page www.utdallas.edu/kcooper
• Office hours
• Tuesday 12 - 2 p.m. or by appointment
• send an e-mail to make an appointment
• office is ES 3.206

4
Software Engineering

• Software systems are complex
• Impossible to understand by a single person
• Many projects are never finished "vaporware"
• The problem is arbitrary complexity
• 1968 Definition
• Software Engineering means the construction of
  quality software with a limited budget and a
  given deadline
• Our definition
• Software Engineering means the construction of
  quality software with a limited budget and a
  given deadline in the context of constant change
• Emphasis is on both, on software and on
  engineering

5
Course format for Advanced Software Engineering

• Lectures
• Application of topics in software engineering
  (textbook chapters 1-12)
• B. Bruegge and A. Dutoit, Object-Oriented
  Software Engineering Conquering Complex and
  Changing Systems, Prentice Hall, 1999.
• Current topics in Software Engineering Research
• selected papers from the literature
• Individual Assignments
• Build technical skills (software engineering,
  UML, JAVA)
• Build managerial and soft skills (time
  management, risk management)
• Group Project
• Build technical, managerial, and soft skills
• Deliverables include group web site,
  configuration management repository, proposal,
  requirements specification, architecture, design,
  construction, test cases, and two presentation
• project management and quality assurance plans
  (including configuration management,
  traceability, etc.)

6
Objectives of this course

• Acquire technical knowledge
• Develop a product from start to (initial)
  delivery
• Covers many phases of software development
  lifecycle
• Acquire soft skills
• Communication, negotiation, team building, time
  management, risk management, leadership, etc.
• Acquire managerial knowledge
• produce a high quality software system within
  budget time
• while dealing with complexity and change

7
Assumptions

• Assumptions
• You are proficient in object-oriented code
  construction and the use of a graphical debugger
• You have a basic knowledge of JAVA
• You have a basic knowledge of UNIX
• You have a basic knowledge of UML
• You have the pre-requisite course and have an
  understanding of the theory of
• Requirements elicitation, specification, and
  management, Analysis, Detailed Design,
  Architecture, Quality assurance (validation,
  verification), Construction, change
  control/configuration management, GUI design
• Project management
• Lifecycle models
• Formal specification and verification

8
Assumptions

• Preparation exam is a breadth exam that covers
  the topics in the pre-requisite course, CS 5354
• See list of topics on previous slide
• The purpose is to determine how well prepared you
  are for the course
• Well known books for this material include
  software engineering textbooks by Sommerville or
  Pressman

9
Resource Requirements

• Resource requirements for this course
• If you have a good background in software
  engineering from your pre-requisite course, then
  plan on 13-15 hours per week
• Otherwise, gtgt15 hours/week

10
Project Description

• Description posted on website
• www.udtallas.edu/kcooper
• Discussion of project (handout)

11
Teams

• Formation and Size
• Students form their own teams
• Teams range in size from 6 to 8 members
• If you are not in a team by August 29, 2003, then
  send me an e-mail and I will place you in a team
• Deadline Teams must be formed by Friday August
  29, 2003
• send me an e-mail with the names and student
  identification numbers of the team members

12
Project Milestones

• External Milestones (with client/auditor)
• Website established by Sunday, August 31
• Proposal Document due (on website) Thursday,
  September 11
• Client Presentation September 11, September 13
• 30 minute presentation
• Client AcceptanceTest November 20, November 22,
  November 25
• 45 minute demonstration
• Internal Milestones (with project management)
• Delivery dates for the following are defined
  by each team in their proposal
• set up configuration management repository
• deliver baselined project management plan,
  quality assurance plan
• deliver baselined requirements specification,
  architecture, analysis, design, system test
  cases, construction of features, user
  documentation

13
Grading

• Project 45
• Acceptance Testing by Customer (half, 22.5)
• Completeness, correctness, consistency,
  timeliness, and presentation of deliverables
  (half, 22.5)
• Assignments 10
• 4 assignments, 2.5 each
• Preparation exam 10
• Final 35

• Standards
• A 90
• B 75-89
• C 56-74
• D 40-55
• F less than 40

14
Proposal

• Description posted is intended to identify the
  content, not necessarily the format of the
  proposal.
• Go through the proposal description now

15
Risks

• What are some people, development system, product
  development risks?
• What can you do to reduce the risk?
• What are you going to do is something bad happens?

16
Project Management

• Approx. how much time would you allocate for each
  internal deliverable?
• Configuration Management repository
• Requirements Model
• Analysis Model
• Architecture Model
• Design Model
• Integration, System Testing
• Construction (with unit testing)
• User documentation
• Who is going to do what? How do you know when it
  is done? Subteam to develop model, subteam to
  review model
• Which activities can be done in parallel?

17
Software Quality Assurance

• How will you ensure a high quality product is
  being developed?
• What tools and techniques will you use?
• What communication mechanisms and modes will be
  used?
• What kind of reviews on the deliverables will be
  done?
• What checklists will be defined for the reviewers
  to use?
• What kind of meetings will be held?
• How often is the website updated?
• IEEE Std 730-1998 IEEE Standard for Software
  Quality Assurance Plans

18
Readings and Tasks

• Required Reading (first 2 weeks)
• Assigned reading
• Text Chapters 1,2, 3,10,11,12
• Papers RUP, SQA, lifecycle
• prepare to build your proposal
• Check your UTD account
• Logon to your account
• 2nd floor, open labs in the ES building
• Account problem?
• Call 2911 or send e-mail to cs-tech_at_utdallas.edu
• Check the homepage for notes, etc.
• www.utdallas.edu/kcooper
• Next lectures are on umbrella activities
• project management, quality assurance

19
Advanced Software Engineering Fall 2003

• Buckle up.