Syllabus Information regarding the programme

• 
  None
  

• 
  Basic software development skills
  

• 
  Understanding and working with basic concepts in software engineering;
  
• 
  Capability of analysis and synthesis;
  
• 
  Proficient use of methodologies and tools specific tool software systems
  
• 
  Organization of software production processes.
  

• 
  Team work capabilities; able to fulfill different roles
  
• 
  Professional communication skills; concise and precise description, both oral and written, of professional results,
  
• 
  Antepreneurial skills;
  

be able to apply basic methods for software analysis and software quality assurance.

know the main features of the common software process models.

be able to represent the software processes using SPEM standard.

be able to create new software processes.

be able to use CASE tools for authoring, configuring and publishing software processes

know the principles of different software development methodologies: model driven development, agile model driven development, feature driven development, use case driven development, domain driven development, test driven development.

1. 
   Software Process Concepts. Definitions. Main concepts: role, work product, activity.
   

2. 
   Software Process Models. Typical tasks and life cycle of the more common software development models: ad-hoc development, waterfall model, v-model, iterative development, prototyping, rapid application development, exploratory model, spiral model, reuse model, unified process.
   

3. 
   Software and System Process Engineering Meta-Model (SPEM). Meta-model architecture and principles. SPEM UML profile. Core. Process structure. Process behavior.
   

4. 
   Software and System Process Engineering Meta-Model (SPEM). Managed content. Method content. Process with methods. Method Plugin. Process diagrams.
   

5. 
   Software Process Frameworks. Eclipse Process Framework Project (EPF).
   

6. 
   Software Process Frameworks. Eclipse Open Unified Process (OpenUP).
   

7. 
   Model Driven Architecture (MDA). Basic Concepts. MDA transformations.
   

8. 
   Model Driven Architecture (MDA). Query/View transformation (QVT). Model to text transformation (M2T).
   

9. 
   Agile Model Driven Development (AMDD). Agile modeling. Principles. Best practices. Approaches for applying AMDD on projects.
   

10. 
    Feature Driven Development (FDD). FDD process. Feature oriented software development (FOSD). FOSD phases. Software product lines.
    

11. 
    Use Case Driven Development. Goal driven view. Types of alternative courses. Use case fundamentals.
    

12. 
    Use Case Driven Development. Practical issues. Iconix process.
    

13. 
    Domain Driven Development (DDD). Ubiquitous language. Bounded contexts. Layered architecture. Aggregates. Factories. Repositories. Services.
    

14. 
    Test Driven Development (TDD). Fundamentals. Examples.
    

1. 
   Steve Adolph, Paul Bramble, Alistair Cockburn, and Andy Pols, Patterns for Effective Use Cases, Addison-Wesley, 2002.
   
2. 
   Scott W. Ambler, Agile Model Driven Development: The Key to Scaling Agile Software Development, 2009, http://www.agilemodeling.com/essays/amdd.htm
   
3. 
   Sven Apel and Christian Kastner, An overview of Feature-Oriented Software Development, Journal of Object Technology, vol. 8, no. 5, July-August 2009.
   
4. 
   Kent Beck, Test-Driven Development by Example, Addison-Wesley, 2002.
   
5. 
   Eric Evans, Domain-Driven Design, Addison-Wesley, 2004.
   
6. 
   Eclipse Process Framework Project (EPF), 2010, http://www.eclipse.org/epf/
   
7. 
   Eclipse Open Unified Process (OpenUP), 2010, http://epf.eclipse.org/wikis/openup
   
8. 
   OMG, Model-Driven Architecture, 2003, http://www.omg.org/cgi-bin/doc?omg/03-06-01
   
9. 
   OMG, Software & Systems Process Engineering Meta-Model Specification (SPEM) version 2.0, 2008, http://www.omg.org/spec/SPEM/2.0/
   
10. 
    Clay Williams, Matthew Kaplan, Tim Klinger, and Amit Paradkar, Toward Engineered, Useful Use Cases, Journal of Object Technology, vol. 4, no. 6, August 2005.
    

1. 
   (2^nd week) Establish the first practical project theme and allocate the papers to be discussed
   

2. 
   (4^th week) Discussion of the allocated papers
   

3. 
   (6^th week) Discussion of the allocated papers
   

4. 
   (8^th week) Project presentation and allocate the theme for the written critical essay
   

5. 
   (10^th week) Discussion of the allocated papers
   

6. 
   (12^th week) Discussion of the allocated papers
   

7. 
   (14^th week) Project presentation and Critical Essay evaluation
   

Students will use the following two tools for their two practical projects: MagicDraw and EPF.

Students will search for the papers in energy-aware programming domain.

• 
  The course respects the IEEE and ACM Curriculla Recommendations for Software Engineering studies;
  
• 
  The content of the course is considered by the software companies as important for average software development skills
  

- apply the course concepts

- problem solving

- be able to use tools for different software process concept

- be able to do a critical evaluation of research papers

- to be able to write a critical essay

-documentation

-portofolio

-continous observations

• 
  At least grade 5 (from a scale of 1 to 10) at both written exam and laboratory work.