¾Ã¾ÃÈÈÊÓƵ

Catalog description: 

General principles and techniques for disciplined detailed software design.  Basic theory of grammars and parsing.  State-transition and table-based design.  Formal specification languages and program derivation. Techniques for handling concurrency and inter-process communication. Tools for model-driven construction. 

Prerequisite: 

CSE 301 and (MTH 231 or MTH 331)

Required topics (approximate weeks allocated):

• Basics of formal languages, syntax and semantics (1.0) 
• Grammars & parsers  (1.0)
• Modeling (3.0)
  
  • FSM 
  • UML 
  • state charts 
• Pre- and post-conditions  (2.0) 
• Program derivation  (2.0) 
• Using API Contract programming, e.g. Spec#  (3.0) 
• Concurrency  (1.0) 
• Inter-process communication (1.0)
• Analyzing concurrent designs (1.0)
• Tests and final exam (1.0) 

Learning Outcomes

• Identify and use Backus-Naur Form (BNF) notations
• Explain the basic theory of grammars and parsers
• Use formal methodologies during software development
  
  • The ¾Ã¾ÃÈÈÊÓƵ can apply a wide variety of software construction techniques such as model-driven construction
  • The ¾Ã¾ÃÈÈÊÓƵ can use tools that support the construction of software
  • The ¾Ã¾ÃÈÈÊÓƵ can apply state-based and table-driven approaches to low-level design of software
• Create simple formal specifications of low-level software modules
  
  • The ¾Ã¾ÃÈÈÊÓƵ will create pre and post conditions in additional to ensure clauses for low-level software modules
  • The ¾Ã¾ÃÈÈÊÓƵ can check the validity of these specifications
  • The ¾Ã¾ÃÈÈÊÓƵ can generate code from the specifications using program derivation methods or appropriate tools
  • The ¾Ã¾ÃÈÈÊÓƵ can generate ensure clauses when using Middleware
• Explain the issues associated with concurrent programs