CSE 5324 (Spring 2015)

Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
  • CSE 5324 - Software Engineering: Analysis, Design, and Testing (Spring 2015)
  • Section 001
  • Class Number 21958

Class Meetings

  • Time: Monday and Wednesday, 5:30 pm - 6:50 pm
  • Location: NH 111

Instructor

TA

  • TBD

Syllabus

TBD

Description of Course Content from Course Catalog

Motivations, principles, and goals of software engineering; technical aspects of software projects, including: review of structured analysis and structured design, emphasis on object-oriented methods of requirements analysis and specification, design, and implementation; software testing concepts; team project.

Project Requirements

  1. Every aspect of your software project has to be fully family friendly. This means, no violence, etc. When in doubt, make it more family friendly or ask the instructor.
  2. Your software should run on the Google Android platform. This means, with your instructions, I should be able to run your code on the standard Android emulator I have installed on my machine. Similarly, with your instructions, your test cases should run on my standard JUnit installation, etc.
  3. Your software should be new and exciting.
    • New means that your software has to have some aspect that is completely novel. It is not enough to just copy and paste an example project from somewhere else. This does not mean you cannot re-use any existing code. Most real-world software engineering builds on some existing code. But it is important that you clearly document which parts are yours and which parts you re-use from another source.
    • Exciting means that your software should have some aspect that is exciting. Examples include that you write a game that is fun to play or you write some utility that is appealing in some form.
    • In the ideal case, the exciting aspect of your software is also new. In this case, you may become rich and famous :)

Timeline

  • All deadlines are Monday 9 am.
  • (CL X) = X in Craig Larman textbook.

Day Tentative Class Topic Deadline
1/21 Overview, syllabus  
1/26 Motivation, introduction UML in practice Form teams
1/28 Iterative process (CL Part 1, How to be a program manager), Inception (CL Part 2)  
2/02 Presentation, feedback Incept project
2/04 Buffer  
2/09 Presentation, feedback Revise inception
2/11 Walkthrough and review (BillG, Simonyi)  
2/16 Basics, requirements Review inception
2/18 Quiz, more requirements  
2/23 Use-Cases (CL Chapter 6)  
2/25 Domain models (CL Chapters 9, 31)  
3/02 Presentation, feedback Iteration 1
3/04 More requirements (CL Chapters 10, 11, 32)  
3/09 Spring Vacation  
3/11 Spring Vacation  
3/16 Architecture (CL Chapters 13, 33) Review iteration 1
3/18 Quiz, Tools  
3/23 Dynamic design models (CL Chapters 14, 15) Homework 1
3/25 Static design models (CL Chapters 16, 19)  
3/30 Presentation, feedback – Code walkthrough Iteration 2
4/01 Design: Grasp principles (CL Chapters 17, 18, 25)  
4/06 Design by Contract (Meyer92Applying) Review iteration 2
4/08 Quiz, more Design by Contract  
4/13 Overloading and overriding Homework 2
4/15 Design patterns  
4/20 Presentation, feedback – Code walkthrough Iteration 3
4/22 Presentation, feedback – Code walkthrough  
4/27 Testing and debugging (AA) Review iteration 3
4/29 Quiz, more testing, Student Feedback Day  
5/04 Final presentation Final deliverables
5/06 Final presentation  

University Academic Calendar

Resources

UML
Java
Android
Other
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.