Wash U DARPA PCES PI Meeting Report

1
CSE 436Intro Lecture
Burchan Bayazit http//www.cse436.org
2
Software Engineering

• Unusual field
• Inconsistent messages, discrepant terminology
• Important field
• Considered pivotal to addressing the software
  crisis
• Diverse field
• Theoryformal requirements, specification
  languages
• Practicetesting, software development models,
  processes, project management

3
Software Engineering

• Unusual field
• Inconsistent messages, discrepant terminology
• Important field
• Considered pivotal to addressing the software
  crisis
• Diverse field
• Theoryformal requirements, specification
  languages
• Practicetesting, software development models,
  processes, project management

4
Software Engineering

• Unusual field
• Inconsistent messages, discrepant terminology
• Important field
• Considered pivotal to addressing the software
  crisis
• Diverse field
• Theoryformal requirements, specification
  languages
• Practicetesting, software development models,
  processes, project management

5
Software Engineering

• http//www.chc-3.com/pub/notbs_ddj.htm
• "creating high-quality software systems in an
  efficient and predictable manner"
• No firm definitions of what high-quality,
  efficient and predictable mean
• Software Engineering Is At An Early Stage
• Software Engineering Is Hard
• There are many tools and methods that help in one
  context, but gum up the works in another.
• Trivial individual components, but hard to
  control and predict if there are thousands
• The Gains Will Be Huge

6
Course Description

• Explores concepts and issues related to
  large-scale software systems development
• Teams will be formed, to emulate industrial
  development
• Projects cover life-cycle phases from
  requirements analysis, to software design, and
  implementation
• A studio course
• Lecture material each week, 25 or less of
  classroom time
• Most of the time will be given to open discussion
  and work
• Teams should be prepared to present and discuss
  each time
• Prerequisites Familiarity of algorithms and high
  level languages

7
Course Goals

• This is a capstone course, meaning that you will
  draw from all your experiences in other courses
  to complete the work in this course.
• Design skills, to arrive at a clean, effective
  design for your project.
• Coding skills, to implement your project in the
  best way possible.
• Programming language skills,
• Debugging skills, to find and fix bugs.
• Testing skills, to search for the presence of
  bugs.
• Theory skills, to prove the absence of bugs.
• Writing skills, to develop clean, effective prose
  describing requirements and project activities.
• Presentation skills, to communicate the important
  aspects of your project at different levels
  (management, customer, team)

8
Course Topics

• Software Requirements
• Interviewing the customer
• Use-cases
• Specifications
• Validations
• Analyzing Requirements
• Data Modeling
• Object-Oriented
• Scenario-Based
• Flow-Oriented
• Class-Based
• Behavioral Models

9
Course Topics

• Designing
• Basic Concepts
• Architecture
• Interface
• Component Level
• Deployment Level
• Patterns
• User Interface Design
• Testing
• Product Metrics
• Agile Development
• Software Engineering for Web Applications

10
What to expect in my CSE 436

• Implementation and Documentation
• Documentation required
• But implementation is equally important
• Testing
• Methodologies in lecture
• Teams practice testing at all levels
• Unit testing
• Application testing, white- and black-box
• Regression testing
• Emphasis on presentations
• Everybody presents
• Everybody critiques
• Everybody improves
• Study of software failures

11
Grading

• 50 Process and product documents from teams
• Requirements
• Software architecture
• Design and implementation
• 20 two individual exams (both take-home)?
• Midterm 10 of grade
• Final 10 of grade
• 30 full-circle review of contributions
  participation
• Feedback from teammates, other teams, professor,
  Tas,
• For each assignment, team members will have 100
  points to distribute among the team members.
• Deadlines are firm, what is handed in gets graded
• Communicate problems and concerns early, get help
• .

12
A Friday in the Life of CSE 436

• Team members, professor, and assigned TA attend
  regularly scheduled 1 hour team sessions
• Let professor and your team members know as early
  as possible if you have a conflict, illness, etc.
• Team, professor, TA discuss progress
• A chance for detailed review, discussion,
  feedback
• Working session on next project topics
• A chance for teams to solicit guidance, pose
  ideas

13
Course particulars

• Take a look at the web space for course
• http//www.cse436.org

14
Key Resources

• Lecture and lab sessions (attendance mandatory)?
• Each other (except on exams)?
• Professor (Burchan Bayazit, bayazit_at_cse.wustl.edu)
  ?
• Teaching assistant (TBA)?
• External Customer (if you have one)?
• Team wiki, cvs, server (we may provide) or other
  resources you may set up
• Course web page (under construction, cse436.org)?
• Course forum (under construction,
  cse436.org/forum)?
• Outside sources of information you can find
• Especially books (on the class site), papers,
  journals, Google, etc.

15
Projects (can be commercial)?

• System Dynamics Analysis Toolkit
• Use system dynamics to simulate social issues
• Integrate to an existing library (C,TCL)?
• Strive for College
• Increasing functionality of an existing website
• Ruby on Rails
• Ultrasound Imaging (Not confirmed Yet)?
• Application for an USB connected ultrasound
• Easy Programming Interface for Robots
• Similar to NTX-G
• Control simulated robots over internet
• Agent Based Drug Market Simulation
• Simulate drug users, dealers, police and their
  interactions

16
Projects (can be commercial)?

• Emergency Evacuation
• Plan for large-scale evacuation
• Emphasis on planning but also adaptation
• Online Radio
• Peer2Peer
• Register on a website, receive files from the
  other users
• Online Strategy Game
• Fantasy/Sci-Fi/Historical
• People control units (hierarchical)?
• Play against others over the internet
• Additional projects (in consideration)?
• Magic House
• Science Center

17
Team Formation

• Q/A on projects
• Team formation
• Social aspects
• Logistics must be able to meet me as a team
  between 9am2pm on Fridays
• Interest in project
• Id like to have Web 2.0 projects
• Wouldnt mind having two teams do same project
• You can suggest your own until Wednesday
• Looking for 6-7 teams of 45 people each
• Form teams
• Each team works on questions and send the to me
• No official team meetings for this Friday, the
  teams discuss themselves the questions.

18
Questionnaire Items (from website)?

• Your name
• Anything I should know about you
• What do you want to learn from this course?
• Where do you intend to go from here?
• Teams you are thinking of joining/forming
• Who else might be on that team?
• Rank the projects Ive proposed
• First choice, second, third
• Propose a project that interests you
• Fill out after Wednesday (once everything is
  finalizes)?

19
First Assigment

• After teams are created
• Familiarize yourself with Project.net
• Watch
• You would be asked a few random questions from
  the demo
• Create an account on Project.net and inform me.
• Create a discussion message on Project.net
• Create an account on the class forum and inform
  me.

http//www.project.net/overview/pnet_overview.html