Software Engineering Coursework

1
Software Engineering Coursework

• Software Engineering
• M.Sc Computing Science
• Department of Computer Science
• and Information Systems
• Birkbeck College, University of London
• Deadline 26 April 2006
• Penalty for delay Grade Grade 5
  DaysOfDelay

2
Software Engineering Coursework

• General assumption In the course of the S/E
  lectures, you have already done some group work
  in which you edited the use cases and composed
  the domain model for a specific software
  development application. Continue the software
  development of this application by completing the
  following tasks.
• Task 1 Design a System Sequence Diagram (SSD)
  for the use case written so far.
• Task 2 Write Contracts one for each external
  system operation in the SSD.
• Task 3 Design interaction diagrams, one for each
  external system operation in the SSD. Include
  annotations of design patterns applied. Half of
  the diagrams should be collaboration and half
  sequence.
• Task 4 Design a DCD that includes the classes of
  all software objects included in the interaction
  diagrams of Task 3.
• Task 5 Select five software classes and write
  class definitions (attributes and method
  signatures) and method definitions (a few
  commands per method not working code) based on
  the interaction and design class diagrams (Tasks
  3 and 4).

3
Remarks

• Comments that will strengthen your work and other
  remarks
• Try to justify and comment on analysis and design
  decisions. Discuss informally what led you to
  analyze and design part of the system in a
  specific manner.
• Describe briefly the methodology used to perform
  a task, based on the output of previous tasks.
  For instance, mention a few points about how one
  can derive different parts of the Implementation
  Model based on Interaction Diagrams or DCDs.
• Approach this work in an iterative manner, and
  record your experience on identifying changes and
  adapting requirements, analysis and design
  through iterations. Feel free to revise the
  original use case(s), and the domain model, based
  on your experience from developing the system.
• Please, include the use cases and domain model at
  the beginning of your work although you will
  not be marked on it.
• The choice of software for designing diagrams is
  free. Hand-designed diagrams are equally
  acceptable as long as they are easy to read.

4
Issues to reflect on

• Remember, there is no perfect solution!
• Which important elements of the architecture are
  still needed in order to create a fully-fledged
  system?